What is a headless CMS?

A headless CMS (Content Management System) is a system for managing content that provides only the back-end, without a fixed front-end (the ‘head’ or ‘header’ display). This allows the content to be used flexibly across various channels, such as websites, apps or smart devices. The name comes from the fact that the system lacks the ‘head’, i.e. the presentation layer that traditional systems come with as standard.

Unlike other CMSs such as WordPress, the design and presentation are completely separated from content management. This offers the key advantage of maximum flexibility and is the only way to implement multi-channel strategies.

The difference from a traditional CMS

A traditional CMS provides both content and presentation from a single source. Editorial management, templates and delivery are all housed within the same system. This is convenient as long as there is exactly one website. A headless CMS manages only the content and makes it available via an interface. The technology used to display it is open. Instead of templates, there is an API; instead of a single website, there can be multiple output channels.

The trade-off is the effort involved. The front end must be built from scratch, and previewing finished content is more labour-intensive than in an integrated system. Those operating a single corporate website generally gain little from a headless approach.

When a headless approach is worthwhile and when it isn’t

A headless approach is a good option if the same content is to appear in multiple places – such as a website, an app, a partner portal or a screen in a high-street shop. It is also a good option if the front end has its own technical requirements that are difficult to implement using templates, or if the editorial team and front-end development team are to work separately.

Arguments against it include a single channel with no foreseeable expansion, a team without in-house front-end development, and a tight budget. A headless architecture costs more to set up than a coupled website, as it involves creating two systems rather than one.

The decision therefore depends on specific factors, namely the number of output channels, existing technical expertise, budget and planned scalability

How content reaches the front end

There is an interface between content management and presentation. The front end requests the content it needs and receives it as structured data, without layout or HTML. There are two common approaches: firstly, a REST interface, where each query returns a fixed set of data; and secondly, GraphQL, where the requesting page specifies exactly which fields it receives. The second approach saves on data traffic, as nothing superfluous is transmitted.

From an editorial perspective, little changes; content continues to be managed in the backend. What does change is the route taken to get there, and the fact that a single entry can serve multiple destinations simultaneously

Craft is not exclusively headless. The same system can deliver a traditional website using Twig templates whilst simultaneously providing content via the GraphQL API. This freedom of choice is the practical advantage over systems built purely as headless solutions. The approach does not have to be finalised at the start of the project.

Craft CMS as a headless system

Craft CMS is a versatile content management system that can be used for a wide range of website projects. It is often chosen for projects that require a high degree of customisability, performance and security. These include e-commerce websites, digital publications and corporate marketing websites. Thanks to Craft CMS’s headless architecture, it features a built-in GraphQL API for dynamic and interactive front-ends. This allows developers to use any front-end technology whilst still benefiting from the powerful content management features. It also enables consistent presentation across different online platforms for a unified result.

Implementing a headless project with Craft

Headless sounds interesting, but you’re not sure if it’s right for your project? Let’s sort it out together. Request a consultation now.