Web development and design

The stack, and why

Next.js 15 with React 19 and TypeScript, styled with Tailwind. Content sits behind Payload CMS so editors change copy without a developer in the loop. Nothing exotic — the value is in a stack that will still be maintainable in three years, by someone who is not us.

• Server components by default, client components only where interaction demands it
• TypeScript end to end, including the CMS schema
• Design tokens rather than one-off styles, so a rebrand is a config change

Performance is a budget, not a hope

Every project ships against a Core Web Vitals budget agreed before the first line of code. Images are served in modern formats at the size actually requested, fonts are self-hosted so nothing is fetched from a third-party domain at runtime, and the JavaScript that reaches the browser is the JavaScript the page needs.

• Largest Contentful Paint measured on the deployed site, not on a developer laptop
• Fonts self-hosted at build time — no runtime request to a font CDN
• Render-blocking resources removed rather than deferred and forgotten

Findable and usable

Each meaningful piece of content gets its own URL, its own title and its own structured data. Semantic headings, real alt text and keyboard-reachable controls are part of the build, not a later audit item. A site that a screen reader can navigate is usually a site a search engine can read as well.

• One page per search intent, with canonical tags and a generated sitemap
• Structured data (JSON-LD) for organisation, services and breadcrumbs
• Contrast, focus states and keyboard paths checked before launch

Handover you can act on

You get the repository, the deployment pipeline and documentation that explains why unusual settings are the way they are. If you decide to move the project elsewhere, nothing about our setup is designed to make that difficult.