How this site is built
A portfolio is a small product, so I held it to the bar I would set for one: fast, accessible, private by default, and honest about how it was made.
Front end
React 19 and TypeScript, with React Router prerendering every page to plain HTML at build time. A page reads fine with JavaScript switched off, and a link pasted into LinkedIn or Slack shows a proper preview.
Styling is Tailwind CSS. Type is Saira, stretched wide for headings, with IBM Plex Sans and IBM Plex Mono for reading and figures. Every font is served from this site; nothing loads from another domain.
Server
A small Go program embeds the built pages and serves them: clean addresses, a real 404, long-lived caching for files that never change, compression, and a strict Content Security Policy built from a hash of each page's own scripts.
It also counts visits without cookies. No IP address is stored. A visitor is counted through a hash mixed with a random value that changes every day; that value is deleted within an hour of the day ending, so from then on a stored hash can no longer be traced back to anyone. A ref tag on a link I send with an application shows me whether it was opened, and nothing about who opened it.
Hosting
One service on Railway, rebuilt from GitHub whenever a change is merged, from a Dockerfile into a minimal container image, always on. Visit counts live on a small attached volume.
Quality bar
Every page is checked in a real browser before a change is merged into the branch Railway deploys from: it loads without errors, has no serious accessibility violations under WCAG 2.2 AA rules, works on a 360 pixel wide phone, holds still for people who ask their system for reduced motion, and has its own title, description and preview image.
On launch day, November 19, 2026, Lighthouse's mobile test scored the home page and the MusterDeck case study 100 for performance, accessibility, best practices and SEO, with the main content painted in about a second and no layout shift.
How AI helped
I built this site with Claude Code, the same way I build MusterDeck. I set the brief, the research questions and the design direction, made the calls on content and trade-offs, and reviewed every page. Claude Code wrote most of the code and the tests under those rules.
Back to the home page.