Case study
Dispatch + operator CMS for a newsroom-first site with a distinct agency layer.
A publishing stack designed to look like a public site first, while still giving operators image handling, structured payloads, and controlled publishing behind the scenes.
Situation
The public surface needed to read like a real publication, not a CMS demo, while still keeping the operator layer close enough to ship quickly.
The tension was simple. Most lightweight CMS surfaces leak themselves into the frontend. Readers can feel the tool behind the page. The brief here was the opposite: make the publication feel first-class, then let the operational machinery sit behind it without turning every route into a dashboard.
Constraints
The stack also had to stay light enough to operate on Cloudflare-native infrastructure, while still being opinionated about content, image handling, feeds, SEO, and consent.
That meant rejecting the usual split between a decent-looking website and a separate internal mess. The site and the operator layer had to be one system with two very different faces.
Editorial shape
On the public side, the design target was a real news-like reading surface with structured metadata, article templates, machine-readable outputs, and a content body that can evolve beyond plain markdown.
The reader should never have to think about how the article was published. But the system still needs to know how to handle images, feeds, legal pages, AI usage policy, and content state transitions.
Operator problem
Behind the scenes, the system needed a control layer for publishing states, SEO settings, image variants, API publishing, and audit-friendly updates.
That operator surface could not become a giant app. It needed to stay narrow, explicit, and understandable enough that an agent or a human editor could both work with it.
Intervention
We split the system into a public Astro frontend and a Worker-native CMS surface with D1, R2, media variants, consent handling, and API publishing.
The public frontend owns reading quality, structured layout, discoverability, and editorial identity. The CMS owns content state, site settings, media ingestion, schema, and API-safe publishing contracts.
Media and payload model
Instead of treating the article body as one undifferentiated blob, the system supports structured payloads that can drive richer layouts when needed: graphics, audio, video, link cards, or supporting evidence modules.
That gives the publication room to behave more like an operator desk when the story needs it, without forcing every article into a boxed dashboard aesthetic.
Infrastructure decisions
Images are processed into variants, machine-readable endpoints are rate-limited, and public pages are edge-cached so the reading surface stays fast while the operator system remains live and flexible behind it.
The result is not “headless” in the vague sense. It is a deliberate separation of concerns: editorial surface in front, operational logic beneath, and explicit contracts between the two.
Why it matters
The resulting site can publish articles, case studies, structured bodies, and machine-readable feeds without dragging operator concerns into the public reading experience.
That distinction matters commercially too. The publication can build authority in public, while the agency layer can point to real delivery proof without contaminating the news surface with obvious self-promotion.
Handoff and governance
The system also had to be understandable after the initial build. That means simple deployment paths, clear content modeling, a stable API, and enough documentation that future operators are not trapped inside undocumented one-off behavior.
Good CMS work is not just content entry. It is editorial operations, deployment reliability, and clear ownership over what can change safely.
Placeholder outcome
Editorial authority on the front. Operator control in the back. No fake block builder in the middle.
The final shape behaves like a publication with a real operating layer attached to it, rather than a website pretending to be a system or a system pretending to be a website.
Další důkaz