Headless CMS
A content management system that stores and serves content through an API, with no opinion about how it is displayed.
A headless CMS separates content from presentation: editors manage structured content, developers consume it through an API, and the same content can serve a website, an app and a display screen without duplication. Compared with a traditional CMS, which bundles editing and templating together, it trades convenience for flexibility and reuse.
The trade lands squarely on editors. In a traditional CMS, what you edit resembles what publishes. Headless takes that away by design, so the editing experience has to be rebuilt: live preview, clear field descriptions, validation that catches problems before publish, and content modelling that matches how editors think rather than how the database is shaped. Teams that skip this ship a system where publishing a paragraph requires a developer, and then conclude headless was a mistake.
Content modelling is the project
The schema decides what is possible for years. Fields modelled around one page layout make every future layout a migration; fields modelled around meaning survive redesigns.
In practice
A marketing team migrated to a headless CMS with no preview and fields named after database columns. Publishing dropped from about 12 pages a month to 3, because every change went through a developer for verification. Adding live preview and renaming fields to plain editorial language restored the original throughput within a month.
Where teams get it wrong
- No preview, so editors cannot see what they are publishing.
- Content modelled around one page layout instead of around meaning.
- Field names taken from the database schema.
- No validation, so broken content reaches production and is found by readers.
- Choosing headless for a single marketing site that a traditional CMS would serve better.
( Learn more )
Related terms
All terms- JamstackAn architecture serving pre-rendered pages from a CDN, with dynamic behaviour added through APIs rather than a server rendering each request.
- Design SystemThe single source of truth for how a product looks and behaves: tokens, components, patterns, usage rules and the process for changing them.
- SitemapA structured list of a site's pages and their hierarchy — used both as a design artefact and as an XML file that tells search engines what exists.
- Style GuideA document defining the visual and verbal rules of a brand or product — logo use, colour, type, spacing, imagery and tone of voice.