The last couple of days were the first where the site started looking like a site rather than a component catalogue with some text in it. There's a Making section now, with the photography Darkroom promoted into it (plus a refractive glass loupe for looking at photos up close) and video pages with the YouTube embeds. Each app got its own page instead of one long directory, and the footer turned into an inverted band with a small interactive optical study in it, which is probably more fun than a footer needs to be.
Then the first deploy of all this to Vercel went sideways. The two build guards I'd added — one making sure pages actually prerendered, one making sure the lab stayed out of production — were both reading from .output/public, which is where files land locally. With the Vercel preset they land in .vercel/output/static, and Vercel had the framework set to null on top of that. A guard only guards the folder it's looking in. Small fix, a shared helper that picks the folder from the preset, but a bit embarrassing given the whole point of them.
The design system got two more snapshots from the artifact: charcoal grounds and a slate tertiary colour first, then the lime signal colour and inverse surfaces that follow the OS theme. Three new components came across with them — ListingGrid, KitTable and CareerLine — and ListingGrid is now on every listing page and the landing page, with per-entry treatments (signal, inverse, quote, date and terminal cells) so the grids don't all look the same. Sections got a space prop on new band tokens, so the landing page bands finally have some air between them.
The resume is the one I'm most pleased with. CareerLine lays twenty years out as a ruler, each role a span on it, and as you scroll the role in the middle of the screen lights up and a crosshair moves to it. There's a sheet view too, which turns the same data into an A4 page for printing. Wiring it in was mostly rewriting the resume data in the component's own shape. The component has the current year hard-coded, so that's one to fix before January.
The app, open source and making pages are borrowing the writing layout for now — the article template with the contents rail down the left and, on the dossier variant, a file data panel on the right. Each one is really just a handful of fields (a description, a list of features, some links), so splitting those into sections gives the rail something to point at and the panel somewhere to put the platform and stack details. It's a stopgap until they get templates of their own, and it shows a bit: the hero still proudly reports "1 MIN READ" for an app page, and the videos have no date so they're filed under a dash. The one actual bug was the reading-time package, which needs Node's util and fell over the moment the page rendered in the browser, so a word count is now a split on whitespace, which is all it ever was.