How a headless CMS works
Editors manage structured content in the CMS. Websites, mobile apps and other clients request that content through an API and render it independently. This separation lets one content source serve several experiences and gives frontend teams more freedom.
The same separation moves responsibility. Routing, page composition, previews, forms, search, caching and frontend deployments may no longer be handled by the CMS. A headless decision should include these missing pieces in its budget and ownership map.
Headless and hybrid options
| CMS | Model | Stack | License | Best fit |
|---|---|---|---|---|
| Strapi | Headless | JavaScript / TypeScript | MIT (community edition) | Custom apps needing an API-first editorial backend |
| Directus | Headless / data platform | TypeScript | BSL 1.1 / commercial terms | Teams that want APIs and an admin layer over SQL data |
| Ghost | Publishing / headless | JavaScript | MIT | Newsletters, memberships and focused publications |
| Drupal | Structured / hybrid | PHP | GPL-2.0-or-later | Complex content models, permissions and large organizations |
| WordPress | Traditional / hybrid | PHP | GPLv2 or later | Publishing, marketing sites, broad plugin needs |
When headless is a strong fit
Good signals
- Content must serve multiple products or channels.
- A frontend engineering team already owns delivery.
- Structured, reusable content matters more than page editing.
- The product needs independent frontend releases.
Warning signals
- Editors expect visual page building without development.
- The project is a small single-channel marketing site.
- No team owns preview, caching and API reliability.
- “Headless” is the goal rather than a solution to a requirement.
Proof-of-concept test
Create one realistic content model, connect one frontend page, implement draft preview, handle an image transformation and simulate an API outage. This small exercise exposes more risk than a long vendor feature matrix.
Frequently asked questions
What is a headless CMS?
It is a CMS that manages content separately from the presentation layer and makes content available to websites or applications through APIs.
Is WordPress a headless CMS?
WordPress is traditionally coupled to themes, but its REST API and other integrations allow it to be used in a headless or hybrid architecture.
What is the main disadvantage of headless CMS?
More delivery responsibility moves to the implementation team, including frontend rendering, preview, routing, caching, forms and deployment.