Under the hood
of this website.
Curious about how this is built? We should get along. Here are some choices I made for this website, with their reasons and limitations.
Content arrives in the HTML
The editorial pages use Next.js Server Components. This page is generated at build time: its text and links are readable without waiting for JavaScript to run in the browser.
Interactions such as the mobile menu and theme toggle use Client Components. The content remains accessible when JavaScript is disabled.
Typed content in the repository
Journal articles are TypeScript objects; page copy is written in React components. Every change can therefore be reviewed alongside the code in a pull request.
This approach suits my publishing schedule. Publishing a change requires editing the repository and rebuilding the site.
Two themes using the same components
Colours are centralised in CSS variables. The system preference determines the initial theme; the toggle lets you choose one and save it in the browser.
If storage is unavailable, the toggle still works during the visit. The layout adapts to the available width using CSS container queries.
Checks focused on behaviour
Node.js tests cover Journal filters and pagination, draft exclusion and relationships between structured data, among other behaviours. Linting and the build provide additional checks.
These checks do not replace editorial review or checking the layout on mobile, with a keyboard and in both themes.