Events · a cadence, not a calendar of promises
Two recurring sessions, honestly empty
Event pages fill up fast with “50+ builders attended!” and dates that never happened. This page publishes a recurring cadence and computes the next real dates from today. No session has run yet, so the past section is genuinely empty — the first one will be recorded and posted with the parts where things broke left in.
First Thursday, monthly · 16:00 UTC · 60 minutes
Build-along
We build one catalog component from an empty file, live, with the audit gates running in a second window. The unedited recording goes up afterwards, including the parts that break.
Hosted by the studio
next session
2026-10-01
computed from today's date
Third Tuesday, monthly · 15:00 UTC · 45 minutes
Contributor office hours
Bring a submission in progress. We read it against the audit criteria and say what a reviewer would say, before you send it.
Open to anyone in the sample roster or the wider queue
next session
2026-09-15
computed from today's date
Past sessions
0 recordedNothing yet. The cadence above is published and the next dates are real, but the first session has not run — when it does, its recording and the questions asked go here, and we will not backfill this list with sessions that did not happen.
Why publish a cadence
A recurring slot is a commitment. Publishing the rule makes it checkable: if three first-Thursdays pass with no session, you can say so with the dates in hand.
What we will not do
No invented attendance numbers, no “65 people registered” counter, no recordings of sessions that were not held. The roster of 9 personas is sample data and stays on the pages that label it.
How to attend
There is no booking system in this build, and we would rather say that than collect an email address for a session we cannot yet host. The schedule is the announcement.
Between sessions, the requests board and the challenge brief are where the conversation actually happens.