Building this site
This site is a static Hugo build with no theme. That is a deliberate choice, not a shortage of themes: a portfolio should look like the person who made it, and a theme is somebody else’s design decisions applied to your work.
The constraints
- No JavaScript framework. The page is HTML and CSS. The only scripts are a theme toggle, a menu button, and the filters on the project and archive pages — a few kilobytes, and the pages work without them.
- No CSS framework. One stylesheet with custom properties for colour, spacing, and type. Dark is the default; light is a token swap. The code blocks use a generated Chroma stylesheet, because syntax highlighting is the one place where hand-rolling is not worth it.
- Two fonts, self-hosted. Inter for text and JetBrains Mono for labels. Both are freely licensed, subset to Latin, and served from the same origin — no third-party font request, no layout shift.
- Hugo, pinned. The local build and the Cloudflare Pages build use the same Hugo version. Template behaviour has changed across 0.x releases; a site should not render differently because a build image updated overnight.
What is generated and what is not
Project pages are hand-written. The archive is one YAML file, because dozens of thin pages would be worse than one honest table. Images are processed from the repositories themselves: screenshots from Glaze and Kiln, kernel renders from Shekl, diagrams drawn for the projects that do not have a screenshot worth showing.
The build produces a sitemap, an RSS feed, Open Graph images, and canonical URLs. There is no analytics script and no cookie banner, because there are no cookies to consent to.
What I would change
If the site grows a real writing practice, the notes section becomes its own concern with drafts and a proper index. If the project list grows past what a single table can carry, the archive gets its own search. Until then, the simplest thing that is still honest is the right size.