Skip to content
dvnt.io

Resources · glossary

Headless CMS

A content management system that stores content and serves it through an API but does not dictate how the site looks. The presentation layer is built separately, usually in a modern framework.

Also called
  • headless CMS
  • API-first CMS
  • decoupled CMS
  • content API
  1. 01

    How it differs from a regular CMS

    In a traditional CMS such as WordPress, content and design are fused: the template decides how a post is displayed. In a headless CMS the two are separate — the CMS is responsible only for content and serves it through an API, while a separate application decides how it looks.

  2. 02

    When it makes sense

    When the same content has to go to more than one place — a website, a mobile app, a screen in a showroom — or when speed and resilience to traffic matter. Headless can also be the answer to years of technical debt: it lets you replace the front end without touching the content.

  3. 03

    When it does not

    For a simple company website that someone will edit themselves, with no plans to expand, headless adds cost without benefit. It needs a developer for design changes that a traditional CMS handles in the admin panel.

  4. 04

    What it changes in the budget

    The build is usually more expensive, because the front end is created from scratch instead of from a ready-made theme. Maintenance can be cheaper and safer — a smaller attack surface and no plugins that break on updates.

  5. 05

    What it gets confused with

    Headless is not the same as JAMstack or a static site. Headless is about where the content lives; JAMstack is about how the site is built and served. You can use a headless CMS without JAMstack and the other way round.

Related terms

  • Vendor lock-inDependence on a single provider, where switching tools or vendors is so costly that it stops being a real option. It is rarely a decision, usually a side effect.
  • E-commerce migrationMoving an online shop to another platform along with its products, customers, orders and URLs. The biggest risk isn't the data; it's losing search visibility.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.