What is a headless CMS?

Headless CMS: definition

In a traditional CMS, content management and website presentation are tightly linked. A headless CMS separates the two: the “head”—that is, the frontend—is missing. What remains is a content backend that stores text, images, and product data in a structured way and makes it available via interfaces.

How the content ultimately looks is decided by the respective frontend. That might be a website built with React or Vue, an app, or an entirely different system. Well-known solutions include Strapi, Directus, Storyblok, Contentful, and Sanity; WordPress can also be run headless.

How a headless CMS works

Editors maintain content in structured fields—for example, headline, teaser, image, or product number. The content is not stored as a finished page but as data. Frontends retrieve it via a REST or GraphQL API and display it in a way that suits each channel.

Because content exists as structured data, it can also be processed automatically—for product feeds, translations, or output in an AI chatbot, for example.

• Content model: defines content types and fields
• API: delivers content to all connected channels
• Frontend: freely selectable, e.g., Next.js, Nuxt, or an app
• Webhooks: trigger a rebuild of the pages when content changes

Benefits and limitations of a headless CMS

Content is maintained once and used everywhere. The frontend can be modernized independently, and statically generated pages load very quickly. And because the admin area is not directly connected to the public website, the attack surface is reduced as well.

On the other hand, the development effort is higher: a frontend has to be custom-built, and depending on the system, a true preview in the page layout is only possible to a limited extent or with additional effort. For a small company website, a traditional CMS is often more cost-effective.

• One content repository for website, app, and other channels
• Free choice of frontend technology
• Very fast loading times possible
• Higher initial effort than with traditional systems

Real-world example: when headless pays off

A manufacturer maintains product descriptions, data sheets, and manuals for its website, dealer portal, and service app. Until now, they were maintained three times—with the inconsistencies you would expect. With a headless CMS, all content is in one place, each channel retrieves it via API, and changes are immediately up to date everywhere.

Headless pays off above all with multiple output channels, high performance requirements, or large volumes of multilingual content. Nano Concepts designs content models, sets up headless systems, and develops the matching frontends.