Uses.

The App Router, static wherever a page can be static. This site is the example — every route you have opened was prerendered as HTML before a line of JavaScript ran.

For the parts that genuinely need state — the booking flow, the scoping wizard, the assistant. Everything else stays a server component so it costs the visitor nothing.

Used where a design system earns it. Much of this site is deliberate inline styling instead, because one-off compositions do not benefit from a utility layer.

Deploys by CLI, static output, image optimisation. Chosen because the framework and the platform being the same removes a category of problem.

Plugin development, deep customisation and commerce built into the same install as the services — the pattern behind the clinic build.

On builds where a non-technical team will keep restyling the site. Chosen deliberately, with the licence and the lock-in accounted for.

Six of them, all free to download — page speed, Elementor animation, link management, prescriptions into a WooCommerce cart.

A forensic analyser and a Playwright utility that rebuilds a whole site from a backup archive. Both written because the manual version kept costing days.

Relational by default, with row-level security so the access rules sit with the data rather than in application code that has to remember.

The pipelines and scrapers behind the AI work — the YouTube back-catalogue scorer runs on it.

Because plugins are PHP, and pretending otherwise is how people ship WordPress code they cannot maintain.

Transactional email over plain fetch, no SDK. One POST does not justify a dependency and a supply chain.

The model behind the transcript, archive and relevance-scoring systems in the work here.

Chosen over fine-tuning almost every time, because facts change and answers have to be attributable to a source.

For the connective automation where a workflow tool is genuinely the right answer, self-hosted when the data should not leave.

Agentic development as part of the actual workflow rather than an experiment — including on this site.

No dev server in this workflow. Changes are built, deployed and verified on a real URL, because a thing that only works locally has not been tested.

Every ship is both, because the repository and the live site drifting apart is a silent failure.

Superseded code, stale docs and dead files get deleted rather than left. Several components and a whole route have been removed from this site for exactly that reason.

Counts derive from the content files, case studies link to live sites, and anything that cannot be backed one click away does not ship.