Glossary
Headless CMS
A headless CMS stores and manages content without controlling how it is displayed. Content is delivered through an API, and a separate front end decides how it is presented on a website, an app or anywhere else.
Glossary
A headless CMS stores and manages content without controlling how it is displayed. Content is delivered through an API, and a separate front end decides how it is presented on a website, an app or anywhere else.
A headless system separates them, exposing content as data and leaving presentation entirely to whatever consumes it.

One content source can feed a website, a mobile app and a partner integration. Front-end technology can change without migrating content. Performance is easier to control because the rendering layer is not constrained by the platform's assumptions.
Two systems to run instead of one, preview and editing experiences that need building rather than inheriting, and a hard dependency on developers for changes that a marketer could previously make alone.
A single marketing website with a small team is usually served better by a mature traditional platform.
Not inherently. It makes fast, server-rendered output easier to achieve, which helps. It also makes it easy to build a front end that renders only in the browser, which is worse for search and AI crawlers than a traditional platform.
Only if content genuinely serves more than one destination, or the front end has requirements a conventional platform cannot meet. For one website and a small team, the extra moving parts rarely pay for themselves.
A headless CMS stores and manages content without controlling how it is displayed. Content is delivered through an API, and a separate front end decides how it is presented on a website, an app or anywhere else.