Jul 2026
Building this site in the open.
Why the portfolio and the library are separate builds, and what a static-first architecture buys a personal site: no server, no cold starts, nothing to page you at 3am.
Two jobs, two sites
A portfolio and a library want opposite things. The portfolio has thirty seconds to make a case; every element competes for that attention. The library is the slow burn — somewhere thinking accretes over months. Bolting them together dilutes both, so they ship as separate builds that share one design system.
Static by default
Neither site has per-visitor state, so both render to plain HTML at build time. No server means no cold starts, no request quota, and nothing to wake up at 3am. Publishing writes to the CMS, a webhook rebuilds, and the new page is live in about a minute. The tradeoff is that publish is not instant — and for a personal site, that costs nothing.