Headless WordPress without the regret
Going headless solves a rendering problem and creates an editing one. Most of the disappointment comes from taking the frontend away without giving anything back.
CMS4 min read
Blog
Working notes on things I had to figure out — bundle budgets and Server Components, idempotency and observability, content models that editors actually use, and where LLM cost really goes.
Going headless solves a rendering problem and creates an editing one. Most of the disappointment comes from taking the frontend away without giving anything back.
CMS4 min read
A CMS schema is a contract between engineers and editors. The difference is that when you get an API wrong, tests fail — when you get a schema wrong, people quietly stop using it.
CMS3 min read
Every Shopify build eventually faces the same fork: stay in the theme, or go headless. Getting it wrong is expensive in both directions, and the deciding question isn't technical.
CMS3 min read