Skip to content

CONCEPT Cited by 1 source

Headless CMS

Definition

A headless CMS is a content management system that separates authoring from delivery. It provides a structured authoring UI and a content data model, and exposes published content only via API — it does not render web pages itself. The consumer (a website, a native app, a static site generator, a micro-service aggregator) owns the entire presentation tier and fetches content over REST or GraphQL.

The "headless" label refers to the missing presentation head — the monolithic template engine, theme system, and URL router that a traditional CMS (WordPress, Drupal, Adobe Experience Manager in its template-delivery mode) ships as an integrated whole.

Why it matters architecturally

  • Presentation autonomy. Consumer applications can use any framework, language, or rendering model they like — React SSR, native iOS, Flutter, static Next.js export — without the CMS imposing a template language or theming constraints. A single CMS instance can back multiple surfaces (web + iOS + Android + kiosks) off the same content.
  • API-shaped contract. The boundary between CMS and consumer is a stable API, not a template runtime. CMS upgrades and delivery-tier upgrades are decoupled. This also makes it straightforward to put an internal proxy between the CMS and the consuming aggregation tier — see patterns/proxy-layer-for-external-saas.
  • Authoring UX as the product. Because the CMS no longer owns rendering, the value it delivers is concentrated in the authoring experience — schema design, validation, collaboration, localisation, content review, custom-app extensibility. This is why building a headless CMS from scratch is generally judged more expensive than buying one: the authoring-UX surface is large, product- like, and not where most consuming companies have a differentiating opinion.

Canonical wiki instance

Contentful at Zalando (Source: sources/2022-09-28-zalando-more-editorial-content-please). Contentful's API-only delivery + entry-type data model + custom-app extensibility for the editor UI are exactly the three properties Zalando's Landing Pages team selected for.

Last updated · 550 distilled / 1,221 read