Pages collection
Home, about, contact, the archive, now, the résumé, the legal pages and the subscriber welcome page — one document each, so they share a folder and an index rather than each inventing their own.
Not a collection of posts — the site's own one-offs: home, about, contact, the archive, now, the résumé and the legal pages. Each is exactly one page, so they share a folder instead of each inventing its own, and — since a folder full of routes with no way to see them all in one place is not actually a collection — the folder gets the same index.html every collection above it has.
Every page, in one list
The docs collection's row card — a label, a note, an arrow, no media — because a one-off page is a fact to be found, not a scene to be looked at.
The site itself — every collection and what is lately in each.
Who is building this, and why token-first.
One form, no ticket system behind it.
Everything published, in one year-grouped timeline.
What I am actually working on this month.
Experience, education, skills — one page, print-ready.
Three tiers, and a free one that is not a trial.
The centred-card auth shape.
The split auth shape — the form still has to sell.
The minimal auth shape, for one field.
The legal page, kept as short as it can legally be.
What is collected, and what is not.
The page a new subscriber lands on.
.c.c-doc — unchanged, from /collection/_pages/index.html
Each one, documented on its own page
Not a screenshot, and not one long combined tour — the same treatment the résumé page already gets below: what the page is, a live link to it, and every component it is built from.
8 doc pages, one per route in collection/_pages/build.py