CMS Websites
A website your editors actually own
Your website shouldn't need a developer every time the homepage hero changes. But too many "modern" websites end up exactly there: a beautifully built React app where every text edit becomes a deployment.
I build websites that editors actually own.
Sounds familiar?
- Marketing waits days for a single text or image change
- Adding a new landing page means filing a ticket, getting approval, scheduling a deploy
- Your current site is fast for visitors but a nightmare for the people maintaining it
What you get
- A website your editors update themselves, without breaking layout or going through engineering
- Fast load times and SEO that holds up — Headless CMS doesn't mean slow
- A content model that fits your content, not a template's idea of it
- Multi-language support that doesn't break the second you add a fourth locale
How I work
I start with the content team, not the design team. We map the actual content types you ship — landing pages, posts, products, case studies — and design a structure that's easy to fill, easy to extend, and survives the next campaign without rewrites.
The frontend is built so designers, devs, and editors all know exactly where their work lives.
Tools I tend to reach for: Strapi, DatoCMS, Sanity, or Netlify CMS on the CMS side. Next.js, TanStack Start, or Astro on the frontend. The right pick depends on who edits and who deploys.