How this site is built

React 19 and TypeScript, built with Vite and styled with Tailwind CSS 4.

Every page is also written out as plain HTML when the site is built. It reads fine before any JavaScript runs, and search engines and AI assistants see the whole page, not an empty shell.

GitHub Pages hosts it. Cloudflare runs the address and the contact form, which checks you're a person with Turnstile before a message reaches me. Email runs on Google Workspace.

• The fonts are hosted here, not borrowed from another site, and they don't hold up the first paint.
• The moving wall on the home page waits until the page has drawn, and the 3D watch only loads when it's needed.
• Speed is measured on real visits, not just in a lab test: every page reports its Core Web Vitals to my analytics.

Every visitor, wherever they are, picks how much this site measures: essential only, analytics without ads, or everything. Nothing from Google, Meta or Microsoft loads before that choice, and each loads only for what it was allowed. Google runs in its strictest consent mode, Clarity is told the choice, and the Meta Pixel waits for a yes to ads. Taking a yes back deletes the cookies it set.

Underneath runs the site's own anonymous count: pages, taps, how far people read and how long they stay, added up per day for each page and each ad, with no cookie and nothing that identifies anyone. So the site still knows which pages and ads work, even when someone says no to everything else.

The three buttons look the same on purpose: a weaker “no” is the dark pattern regulators fine. India's data protection rules ask for this kind of consent from May 2027; this site does it now. What you type in the contact form stays on your device until you press Send, and if you came from one of my ads, the form asks separately, with an unticked box, before Meta and Google are told about an enquiry. The privacy page lists everything.

• Every page carries structured data that Google can read.
• The sitemap's dates only change when a page's words, links, images or data really change.
• llms.txt gives AI assistants a plain-text map of the site.
• The blog has an RSS feed.

If your device asks for less motion, the moving parts stay still.

The 3D watch runs on three.js, from a model prepared in Blender. Some blog covers are modelled and rendered in Blender too.

This is the kind of work I take on. See what it costs on Work with me.