Can you explain how this model is a CMS rather than a document database?

Hi Mark,

a headless CMS provides generally all services you know from a traditional CMS, including content repository, permissions, workflow, versioning, taxonomy, etc. So it’s not just a database.

Here’s an example of what it looks like from a user perspective:

The difference is that it doesn’t care how you display the content — that is completely up to you and you have full control over the presentation. You only call the REST API that returns structured content in JSON format.

Here’s an example of such API call:

I’m using our own product Kentico Cloud for illustration, but other headless CMS products work in a similar way.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.