About
We build content-driven sites that hold up
A small team, a content model editors can live in, and a front end that stays fast as the site grows
How we work
Every project starts with the content model. We work out what the pieces of content actually are, who edits them and how often, before anyone opens a design file. That choice decides how much of the site an editor can change on their own later, and how much needs a developer.
A CMS the team can live in
Fields named for the thing they hold, sensible defaults, and validation where it saves someone a mistake. Editors publish without asking us first.
The front end
Pages are rendered ahead of time and served from the edge, then refreshed when content changes. Visitors get static-speed pages; editors get their changes live without waiting for a deploy. It is a boring setup on purpose.
Fast by default, not by heroics
Images sized and served through a CDN, no client-side data fetching where the server can do it, and a budget we hold ourselves to after launch.
We are a handful of people, so we take on a handful of projects at a time and stay on them afterwards. If that sounds like the sort of arrangement you are after, the writing on this site is a decent sample of how we think.