A headless CMS has its front-end part removed, and what still remains is content delivery via an API or static content files, some would also name those content management systems “API driven CMS”. Its focus is just on storing and delivering the content, and provide some kind of CRUD part. This means that the content of a headless CMS can be used on a website, an app, a wearable device or even your new high-end toaster.
We know that more and more websites are built with the headless CMS architecture, even WordPress tries to change from being a monolith to an API-driven CMS the so-called “headless WordPress” or “Headless Drupal”. Both of these options try to make the CMS work in a way that they were not designed for. In fact, they won’t scale that properly, since their monolithic nature doesn’t allow them to be as extensible and performant as needed.
The technical view on a headless content management system would be:
- An open content management API
- A completely free choice of technology for developers to work with
- Reuse of content for different systems out of the box
- Mix up and match with existing CMS, E-commerce or other systems.