How this site is made.
A colophon — the note that tells you how the thing was built. Kept public, because the making-of is part of the argument.
A colophon is the note at the back of a book that tells you how it was made — the typeface, the paper, the press. This is that note for this site, kept public on purpose.
Most personal sites hide their machinery. I keep mine in the open, because on a site about building software, how the site itself is built is part of the argument.
- Framework
- Next.js (App Router) with React and TypeScript, built with Turbopack. Statically exported — no server at request time.
- Styling
- Tailwind CSS with a shared design-token preset. One typeface carries the type; motion is navigational only.
- Content
- Every essay and knowledge entry is typed TypeScript in git — no CMS, no MDX, no database. The compiler is the validation layer: a malformed entry is a build error, not a silent bug.
- Distribution
- One canonical home. An RSS feed and an llms.txt index make the corpus readable by feed clients and by other people’s AI agents; social networks are just pointers back here.
This site is tended through Claude Code — I describe a change in plain language, and it edits the typed data files directly. That only works because the content is code: a request like “add a knowledge entry on X” resolves to a concrete file the compiler can check, not a paragraph a model guessed at.
So the manifesto — “manage the site in natural language” — isn’t a chatbot bolted onto the front. It’s the authoring surface at the back. The words on every page are still mine; what’s automated is the plumbing, not the thinking.
The trade is deliberate: typing the content makes it cheap to add and impossible to malform, which is what keeps a living site honest instead of letting it rot into a stale feed.
A living knowledge layer
Twin timestamps (first-published + last-tended) and a maturity signal (draft → working → stable) across writing and knowledge; a cross-type stream feeding a reverse-chron “latest”, an RSS feed, and an llms.txt index. Designed and built in a working session with Claude Code, then reviewed and committed by hand.
The authoring interface
A single instruction file that lets the agent add or revise content correctly — the exact types, the shared taxonomy, the honesty rules — so every future edit follows one checked contract instead of re-deriving the structure each time.
Kept honest with a date. When the stack or method changes, this page changes with it — in the same commit.
