Studio · Technology
The tools we use, and why.
We pick the simplest tool that does the job well and that another developer can still read in five years.
How we choose
Four rules
-
The browser first
HTML, CSS and the browser’s own APIs before any library.
-
Static when possible
Pre-rendered pages are fast, cheap to host and hard to break.
-
Enhance a working page
Script and WebGL are added to a page that already works without them.
-
Dull infrastructure
Proven hosting and build tools. The novelty belongs in what the visitor sees.
Stack
What we use, and why it is here
Each group says where the tools in it are used: on this site, in the Lab or in the projects under Work. Two groups are not used here: automation and AI, which are designed in the Lab, and the tools chosen per client.
Foundations
This site, every page.
- Semantic HTML
- Every word, link and form is in the page before any script runs.
- Modern CSS
- Grid, container queries and design tokens, with no CSS framework.
- JavaScript
- About 19 KB for navigation, forms and motion. The page works without it.
Real-time and motion
The orb, the canvas art and the Lab.
- WebGL and GLSL
- The orb draws on the graphics card, with a Canvas 2D version for devices without WebGL.
- View Transitions API
- Cross-page fades and the shared project cover. Browsers without it simply navigate.
Build
This site.
- A static site generator in Node
- Turns the content into HTML, the sitemap, structured data and llms.txt.
- esbuild
- Bundles and minifies the site script and styles.
Quality
Before each release of this site.
- Playwright
- Drives a real Chromium through every route, form and menu.
- axe-core
- Automated accessibility checks on every page, inside those browser tests.
- Six audits
- SEO, conversion, editorial, navigation flow, scrollbars and clipped letters, written for this site.
Hosting
This site.
- Cloudflare Pages
- Static files at the edge, with headers and redirects kept in two text files.
- Pages Functions
- One function receives forms and reports whether it can deliver them.
Systems
The form on this site.
- Webhooks
- How the form function hands a brief to the tools a team already uses: CRM, email, chat, a spreadsheet.
- Workers KV
- Somewhere to keep a submission when no other destination is connected, so nothing is lost.
Automation and AI
How we would build it. Designed in the Lab, not yet shipped for a client.
- Workflows in code
- A fixed sequence of steps a developer can read and test. Written before any agent, because most routine work does not need one.
- Language model APIs with structured output
- Only for a step that needs judgement (reading, sorting, drafting), returning a label and a reason a person can check. Never a step that sends, pays or deletes on its own.
- Run logs and a review queue
- Every automated step is recorded, and what the system is unsure about waits for a person. People keep the exceptions.
Per client project
Not used here.
- TypeScript, React apps, a headless CMS, Vercel or Netlify
- Chosen when a client’s team or content calls for them.
Example
How this site is built
Six stages from a line of content to a page in your browser. The numbers are measured by the build that produced this page.
-
Content
Every page starts as structured content in code: 131 public pages from 8 collections. Each page has a status (draft, preview or published), so unfinished work is never public.
site/content/ -
Registry
One table of every page, its route and its relations, made two-way. A published page cannot link to an unpublished one, and the menus, footer and sitemap read from the same table.
site/core/registry.js -
Templates
24 templates turn content into HTML. Titles, descriptions and structured data are generated from the same fields as the visible text, so they cannot drift apart.
site/core/templates.js -
Checks
6 audits (SEO, conversion, editorial, navigation flow, scrollbars, clipped letters) and browser tests with axe-core run against the built pages before a release.
scripts/, tests/ -
Delivery
Static files on Cloudflare Pages with security headers and redirects: 38.5 KB of JavaScript and 25.9 KB of CSS, gzipped, for the whole site. Every page reads without JavaScript.
dist/, _headers, _redirects -
Edge function
One small server function receives the forms: it validates them, drops spam and hands them to the configured destination. Nothing else runs on a server.
functions/api/lead.js
Have a project in mind?
Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.


