We get asked this a lot, usually by people expecting the answer to be a drag-and-drop website builder: how did you actually build your own site? The honest answer is we hand-coded it, and for a studio whose job is proving we can do that well, anything else would have been a strange advert for ourselves.

What we were optimising for

Not “fastest to launch.” We optimised for performance, accessibility, being easy for us to maintain and extend ourselves, and owning the code 100%: no page-builder lock-in, no plugin we’re one update away from being broken by, nothing running that we didn’t put there and don’t understand.

The platforms we considered, and didn’t rule out on principle

Ready-made platforms are genuinely good at getting something live quickly. But a site that a non-technical team needs to update daily still needs somewhere to edit it, and that is the part we wanted to do differently. So for our own site, and for our clients’, we pair a hand-built front end with an editor made for it, Somnia CMS, rather than a database and a stack of plugins. We chose it for the same reasons we’d recommend it: speed, accessibility, and nothing running that we don’t understand.

The actual stack

  • Astro, for a static-first site that ships close to zero JavaScript by default: pages that are just fast, rather than fast after a framework finishes hydrating.
  • Somnia DS, our own design system. Every colour, font, size and space on the site is a design token, written once in a standard format and turned into CSS by a small build script. Components (buttons, cards, callouts, the case study mockups) use those tokens rather than hard-coded values, so a change in one place reaches every page. We’ve published the whole thing at /somnia/, with each component shown in light and dark mode.
  • Tailwind for layout and one-off styling, reading the same tokens, so the utility classes and the design system can’t drift apart.
  • Node.js and npm to run the build. Nothing exotic, the same tooling most of the web already runs on.
  • GitHub, with the site’s content and code in one repository. A GitHub Action builds the site and deploys it to our host whenever we push a change, so there’s no database or plugin stack to patch or secure. Editing is through Somnia CMS, which saves each change to the repository as a version we can roll back.
  • Pagefind for site search. It builds a small search index when the site is built, and searching happens in your browser, so there’s no search server and your searches aren’t sent anywhere.
  • Umami for analytics: cookie-free and privacy-focused, so there’s no cookie banner to click through.
  • A forms service (we use Formspree) to handle the contact form’s submissions without us needing to run and secure our own backend for something that simple.

Things you might not notice

  • Light and dark mode. Both are built from the same tokens, and every page is checked for colour contrast in both.
  • Print. Pages print on light paper in our own brand, without the navigation, and with link addresses written out. We wrote up how in the ultimate print experience for websites.
  • Accessibility checks on every change. We run automated checks (axe) across the site in both modes, plus keyboard and zoom testing, before anything ships. It isn’t a substitute for testing with people, but it catches regressions early.
  • Brand switching. Because the site is built on tokens, the same components can be shown in other brands. Try it in Somnia DS, or make your own theme in the theme builder.

How heavy is it?

We measured it rather than guessed. A typical page here is around 250–400 KB before compression, and most of that is the self-hosted fonts; the home page ships about 5 KB of JavaScript. Screenshots in case studies are served as AVIF or WebP, so the heaviest page we have (a case study with several screenshots) is still well under half a megabyte on a first visit, and repeat visits are lighter again because fonts and styles are cached.

In Google’s Lighthouse test on the live site (22 October 2026, an emulated mid-range phone on a slow 4G connection), the home page scores 98 for performance and 100 for accessibility and SEO, and 100 for all three on desktop. Articles, case studies and the Somnia DS pages score 91 to 93 for performance on that phone. Automated tests only catch part of what makes a site accessible, so we also run the axe checks on every page in light and dark mode and test the controls with a keyboard.

By the standard Sustainable Web Design estimate, a first visit works out at roughly 0.1 g of CO₂. That’s an estimate, not a certificate, but it’s a useful number to keep an eye on: if a change to the site makes pages noticeably heavier, we’d rather know before it ships.

Content, without the CMS bloat

Every page and case study on this site is a plain content file living in the same repository as the code, so there’s no separate database, no admin login to maintain, no CMS vulnerability to patch at 11pm. We edit it directly, often working with Claude to draft and revise copy, and every change is just a commit like any other code change: reviewable, reversible, and versioned for free.

That said, “no CMS” is the right call for where we are now, rather than a permanent rule. Since we first wrote this, two of the things we said we’d add have happened: the design system (Somnia DS) and privacy-friendly analytics. The third, a headless CMS for a friendlier editing experience, is still on the list. Tina is the front-runner, since it edits the same Git-based content files rather than replacing them, so we’d keep the ownership, speed and simplicity that made this approach worth it in the first place.

Thinking about whether your own site needs a CMS, a page builder, a design system, or just needs building properly? Get in touch and we’ll give you an honest answer, not a sales pitch for whatever we’d rather build.

← Back to all insights