7 (not so secret) secrets about headless CMS

8 min readJan 3, 2019

Having problems understanding the concept of headless CMS? Cracking these secrets might help you understand what it is.

The technology called “headless CMS” has gained traction lately, leading to startup companies and new solutions from established vendors. A headless CMS severs the connection between the content (body) and the presentation (head), effectively making the solution “headless” and allowing for the content to be compatible with a number of different outputs.

But it’s useless to keep explaining the concept over and over like this if you still don’t get it. Our purpose here is therefore to bust myths and clarify the concept, and perhaps in the process tell you something you didn’t already know or could understand … up until now.

1. You might not understand it, and that’s okay

Digital marketers are experts in content tactics, marketing strategies, and copywriting techniques, but they are not necessarily at home with programming.

“Headless CMS” is a technical term, by and for developers. If you can’t wrap your head around the concept, that’s totally fine. It probably doesn’t help to repeat the phrase that in headless, the presentation layer is separated from the content layer. What does this even mean?

But, maybe these comparisons will help:

Imagine if every engine were inseparably linked to its car. The engineers and mechanics couldn’t use the principles of a V8 engine from an Aston Martin Vantage in an Aston Martin DBS Superleggera. They would have to create it from scratch as whole new engine. But luckily, the engine (content) is the same in several different cars (presentations), enabling economic efficiency.

Imagine if the text of a novel were inseparable from the first physical copies made of it in hardcover. That would make pocket editions, collector editions, digital editions, and so on impossible. Luckily, the content is in reality separated from the presentation also here.

Imagine if you could wear only one piece of clothing — the first you accidentally put on early on in your adulthood. Again, we are able to separate the content (the person, you) from the presentation (the clothing).

Headless is not pointless. A headless CMS makes it easier for your developers to deliver your content to several different channels, or said in other terms: reusing your content and liberating yourself from different technologies.

2. Headless is not new

Believe it or not, but contrary to what the recent surge in popularity suggests, the method behind a headless CMS is nothing new at all. Already back in 1979 the Norwegian computer scientist Trygve Reenskaug introduced the idea of the “model–view–controller.”

In this design pattern, an application is divided into three interconnected parts: the controller, the model, and the view. The model represents the data and nothing else, and is not dependent on the other parts. The view shows the model data and sends user actions like button clicks to the controller.

In a similar fashion, a headless CMS acts like a specialised database, where the interface enables editors to manage content (the model). At the same time, developers can build clients with their preferred tools. The client then connects to the headless database, fetches the content and handles the presentation locally (the view and the controller).

This approach has actually been done since the very early days of content management systems, but the difference today are more use cases, and more commodities — with vendors specialising in delivering only headless solutions.

The basic change is the way people want to solve tasks and deliver services. Today we can observe more reuse of content through different channels than before. In the past you would be happy with just a website, but that has all but changed in the present.

Now we have mobile apps, smartwatches, and front-end frameworks with rich web clients — examples being websites that look and feel more like apps with rich functionality. Think about Facebook or AirBnB, and the interactive feeling you get, the immediate responses, and so on — essentially what is dubbed “web 2.0.”

Want more technical stuff? Read about 4 technical things you should know about CMS »

3. Once upon a time there were only websites

With the influx of modern and feature-rich websites, it is hard to imagine a time when there were only static and server-based web pages on the world wide web. Examples include news sites, personal blogs, corporate brochure websites, and such.

Today, the websites have evolved into rich applications — like social media, online banks or online office suites. This demands a new way to think about content and presentation. The development has also been fueled by several new technologies, like the front-end frameworks Angular and React.

What we see is a microservice approach: Different services with APIs (connectivity toolboxes) that delivers both content and functionality. This aligns with headless CMS, which itself is an API. The world has changed, and so does technology.

4. Headless has some serious advantages

Compared to traditional or “coupled” CMS, a headless CMS has several perks. Remember, a “traditional” CMS is one where the content and the presentation is closely interlinked. When you alter the content, it might affect the looks and functionality, and vice versa.

Headless CMS can offer advantages like:

Omnichannel readiness
Low operating costs (depending on your choices)
Reduced time to market (for content)
Ease of use (fewer options for the content creator)
Flexibility
Cloud scalability
System security

Editors, who create and maintain content, don’t have to bother with the presentation, i.e. the way things look on the web, on mobile, on smart devices, and so on. Instead editors can focus on the content itself, while the developers have full control in the reuse of the content in different channels.

The greatest advantage may still be this: The developers can do whatever they wish — they don’t have to do programming using the CMS. They can build the service in whatever relevant technology, and then fetch and use the content as they see fit.

8 reasons why your digital projects are slow — and how to solve them »

5. But it’s not all glitter and gold

Even though a headless CMS has multiple advantages, not everything about it is a bed of roses. Some disadvantages include:

Multiple services to manage
No channel-specific support
Marketing more dependent on developers
No inherent content organisation

The greatest disadvantage with headless CMS might be that you have to recreate a lot of functionality — e.g. a landing page editor, URL management and content organisation with tree structures etc. Also, there are no templates, and developers have to handle this themselves.

A headless CMS is “only” an online database, with a user-friendly user interface. Whether you need it or not depends on the use cases. Do you only need to deliver content into some application, “help texts”, or so on, or do you need to build a full-blown website?

This is why you must think use case, use case, use case!

See how you can build a business case for your new digital project »

6. It might pay off to go for a hybrid CMS

Do you have to choose between either a coupled CMS or a headless CMS? Do you have to have a closed link between content and presentation, or no link at all? Fear not, because there is such a thing called a hybrid CMS — also known as “decoupled” CMS.

A hybrid CMS is essentially this: headless + template-based CMS in one package. You get the best of both worlds — the separation of the content layer and the presentation layer, and the option to connect them when needed. Your developers can code and adapt a lot more in this kind of system.

An example of a hybrid CMS might be as follows: A solution offering a website with a landing page editor + content to an app. This means different uses of the same content in one platform.

Again, whether or not you should go for a headless CMS depends solely on your use case — your actual requirements. Consult with this flowchart to see what you really need:

7. The headless metaphor is not too great

You might have been explained the headless metaphor already: Headless “chops” off the “head” — the front-end, that is the website — from the “body” — the back-end, the content repository.

The idea is that you can have several heads attached to the same body. For instance: You have the same back-end, the same content, but presented in different places, like a traditional website, a smartwatch, a refrigerator, a traffic sign, and so on.

Here the body is the same, but the heads are all different — the content is the same, but the clients are different, either they are a desktop browser, a smart device OS, or a digital signage system. E.g., you can have the content “Hello, world!” in different channels; on your browser, your watch, and on the sign you drive past to work.

However, in real life it’s actually your head that provides the content. The body is just a vessel, while your mind, your ideas, thoughts, values, and actions, are determined in your head. So switching heads doesn’t really make any sense in this regard.

Switching bodies from a lean and flexible one, to a muscular and sturdy, or a big and heavy one, makes the presentation of your thoughts and actions quite different if you would participate in acrobatics. But the essential content is the same — what differs is the presentation and execution.

But, as neither switching bodies nor heads are possible today, a completely realistic metaphor would be “mask” or “outfit”. You, the back-end, stays the same, but can be applied to different costumes, or front-ends. But that’s not as fun or striking as “headless”.

A headless CMS doesn’t make you a god — you still have to make smart decisions and create awesome content. Hopefully this blog post has made you aware of some facts about the concept that will aid you in your future endeavours.

Originally published at blog.enonic.com.