What is a headless CMS?

Kuroco is an API-first headless CMS. Unlike a conventional CMS, with Kuroco, you can build your own system flexibly without constraints. This section explains what a headless CMS is, and how it differs from a traditional CMS.

What is a headless CMS?

Traditional CMS

A traditional CMS is web-page oriented. It puts everything (HTML, CSS, text, images, etc.) together in one big framework.

Content is mixed with code, making it difficult to extract and adapt to other digital platforms. Developers have to duplicate the content from a website CMS to a mobile app CMS to a smart device CMS. Everything is done in a linear, step-by-step fashion.

Headless CMS

A headless CMS organizes and stores the content in a unified repository (the "body"), which is decoupled from the presentation logic (the "head").

The content can then be delivered via APIs for display across a wide variety of platforms. This makes device compatibility a breeze.

This kind of content structure also allows for simultaneous collaborations and agile workflows.

At a glance

The headless CMS offers multiple benefits over the traditional infrastructure.

	Traditional CMS	Headless CMS
Hosting	On premise	Cloud-native
Focus	Project-focused (time, scope, budget)	Product-focused (customer success and value)
Supported devices	Limited	Limitless
Re-using of content	Not possible (one-to-one reach)	Possible (multi-channel publishing)
Workflow	Sequential, waterfall	Agile, with simultaneous collaborations
Updates	Scheduled, manual	Continuous, automatically applied across all channels
Back-end	Monolithic, all in one bucket	Structured, with centralized content hub