Content and design separated: useful for multiple channels, unnecessary for one website.
A headless CMS is a system in which you manage content without determining how it looks. The content is retrieved via an API by your website, app or other channel. That makes it powerful when the same content needs to appear in multiple places, and redundant on one website.
IN COMMON LANGUAGE
Which means disconnected
With a traditional CMS, content and display are linked: your page exists in the system. With headless, only the content exists, and each channel retrieves what it needs.
That is the power and also the complexity: something has to be built that shows that content, because the system does not do that.
WHY IT MATTERS
When it pays off
For one website it mainly results in extra moving parts. Our approach: content in files, generated pages: gives the same benefit without any additional service.
With a website plus app plus screens on location, it pays off: you want one source for all channels.
- Multiple channels — that's what it's meant for.
- One website — mostly unnecessary complexity.
- Developer needed — the system itself shows nothing.
- Speed — can be easily combined with generated pages.
- Costs — often per user or per request.
FREQUENTLY ASKED QUESTIONS
More about a headless CMS
Do you use this?
We work with content in files that are processed into pages during construction. That gives the same separation without dependence on an external service, and it's faster.
Is it better for SEO?
Not inherently. What matters is whether the page loads quickly and completely. A poorly executed headless setup can actually be worse than a regular CMS.
When would you recommend it?
Once the same content needs to appear on three or more channels and manual tracking becomes unworkable.
CONTINUE READING
Of course, continue reading about this subject.
Contents op several places?
Tell us which channels you serve. We'll tell you if this solves something you have.