The one page that holds the current Day 1 plan. Tasks and owners live in 02 · Production Tracker; full lesson detail in 03 · Lesson Plans.
Last updated: 2026-08-14.
We've got intermediate-to-advanced devs who already know Three. The whole day runs WebGPU on R3F v10. The Paris mini-site is the spine — we introduce it by name at the top of the day, and every block ends by adding something to it. By 5pm everyone has rebuilt the site and touched the full scope of R3F. Nobody lectures: each block is a 15–20 minute live build, then we're on the floor helping while people work from the written steps. Agents are welcome — people just have to be the ones typing.
| Time | Block | What's in it |
|---|---|---|
| 09:00 | Mini-keynote + expectations | ~25 min why-R3F/v10 with a wow demo (the live site), then expectations and how we're using agents today. Doubles as the install buffer |
| 09:35 | Setup gate → L1: The hero, explained | the R3F mental model, components and props, useGLTF, cameras and controls, backgrounds |
| 10:30 | L2: Make it alive | useFrame and the scheduler, refs, pointer events, leva. Core is steps 06–08; the overflow/break floats to wherever those finish |
| ~11:15 | Overflow/break → polish + show & tell | catch-up time by design — floaters triage, stragglers land, then steps 09–10 self-serve |
| 12:00 | Lunch — hero pauses | |
| 13:00 | TSL (the heavy-guidance block) | nodes, uniforms, compute — capstone is the flip demo |
| 14:00 | State | React state → zustand → the time-of-day store; the sky joins the hero here |
| 14:50 | Physics (fast show) | world, bodies, colliders, impulses — capstone is the globby footer |
| 15:05 | Overflow/break | same idea — physics floor time spills here if it needs to |
| 15:20 | Finale | inside the sky's node graph, then postprocessing and site polish — the "done" moment |
| 16:30 | Stretch pool / free build | portal, magic-box, grain variants, footer variants |
| 16:45 | Recap + Day 2 preview |
Dennis drives the day, but the teaching is shared. Ava is MC — she keeps us on time and in line, both days: timeboxes the demos, calls the overflow/breaks, caps show & tell.
AM: Dennis leads; the team presents 10–25% of it in segments to give him breaks. Which segments is still open — mark them in the run-of-show once decided.
PM blocks have owners, and owners lead their block fully:
| Block | Lead |
|---|---|
| TSL | Dennis (locked) |
| State | Kris maybe, else TBD |
| Physics | Kris (locked) |
| Finale | TBD — Faraz likely takes one of the open blocks |
Whoever isn't leading floats.
People bring solid JS, real Three vocabulary, and passing familiarity with React. They don't bring R3F, TSL, or shader experience — that's the point of the day. When someone's missing a piece we help at the seat and keep the room moving; expected struggle points and the per-block responses live in the lesson plans ("Who's in the room"). Short version: weak React gets seat help and the pre-work pointer, shader failure is expected and normal (checkpoint + agent + longer guide), and nothing derails the day.
Every afternoon block follows the same shape: show the concept on its own, run a couple of quick mini-demos of the sub-ideas, then land it in a capstone that goes onto the spine. Sometimes the capstone is the hero, sometimes it's a section of its own — whatever frames the concept best.
The day sells R3F as a whole — v10 is the hook, not a checklist. The v10 things people will actually see: WebGPU (everything runs on it), the new scheduler (L2, and again when the site runs many canvases), TSL nodes and compute (the TSL block), useRenderPipeline / usePostProcessing (the finale), onFramed (how sections only render in view), and QOL improvements as they come up naturally.
paris-workshop). The Day 2 tracks will likely have their own repos. main is the finished site, the day is a linear chain of workshop/stage-NN branches, and demos plus their variants live as routes. The old v8 hello chain is retired. Deps lock ~Sep 1 — a week before the workshop — and that's when the one prep email goes out with everything: clone/verify, tooling, WebGPU check, React pre-work, logistics. The React-skill poll goes out early — it's the touchpoint before then, and its results tune the email and the pacing.