SR
EN
DE
SLPortals
What is a headless CMS and when do you need one?
A headless CMS separates content from presentation. We explain the pros, cons and when it makes sense for a portal or a multi-platform site.
A classic CMS keeps content and its presentation together in one tightly coupled system — when you change a text, the change is immediately reflected in the only place that system displays, usually the website. A headless CMS separates those two layers: content is stored separately in a database, and any frontend — a website, a mobile app, or a third channel — fetches that content via an API as needed.
The concrete advantages of the headless approach
The same content (an article, product, listing) can be shown simultaneously on the website, in the mobile app, and on any other channel, without duplicating entry — write once, display everywhere.
The frontend (what the user sees) is completely free to be built with the most modern, fastest technology, independent of which CMS stores the content in the background — you don't have to choose frontend technology based on CMS limitations.
Easier scaling for a large number of simultaneous visitors, because the layer storing content and the layer displaying it can be optimised and scaled separately, each according to its own needs.
When a headless CMS makes sense, and when not
For big portals with an extensive content archive and concrete plans for the same content to appear on multiple platforms (web + mobile app, for example) — the headless approach pays off long-term through flexibility.
For a simple company presentation site that will never need to share content with a mobile app or a third channel, a classic CMS is often sufficient, simpler to set up and easier to maintain long-term without the extra complexity the headless approach introduces.
Nikola Cerić
Founder & CEO, Manage IT
More than 10 years of software development experience — in his own company and in major IT companies across the Balkans.