The portfolio is also the case study.

Every page is generated at build time to static HTML. There is no server at runtime — the content a crawler, a link preview, or a reader with JavaScript off sees is the same content you see. Live data (project records, analytics) hydrates progressively on top of baked-in fallbacks, so the page is never empty.

One token file defines the entire visual language: surfaces, ink, a single accent, hairline rules, motion curves. Two themes — paper and blueprint — are the same tokens with different values, which is why the theme toggle switches everything at once, including these words. Sharp corners are a choice, not a default.

The footer shows measured values only: the deployed commit, the build date, and GitHub statistics fetched during the build with their as-of date. Nothing self-assigned. If the GitHub API is unreachable at build time, the last verified numbers ship with their original date — staleness is labeled, never hidden. A weekly scheduled rebuild keeps every number under seven days old.

First-load JavaScript is budgeted and enforced by a build gate that fails the deploy if the homepage exceeds it. The command palette loads only after your first keypress. Motion is CSS, not a library. Fonts are subset and self-hosted. Verify the result yourself:

The build chain runs unit tests, type checks, static generation, and an output-verification script that asserts every route exists and key content actually rendered into the HTML — the class of bug where a page silently ships empty. If any gate fails, the deploy never happens.