Headless CMS development

With a headless approach, content lives in one place, and your website, mobile app or in-store screen fetches it and displays it in its own way. It makes sense for some projects and is a completely unnecessary cost for others. We'll help you work out which one you are.

In a traditional CMS such as WordPress, the admin and the look of the website are one whole. That's practical as long as you only have a website. When a mobile app, a second website or a partner portal comes along, the same copy starts being duplicated in three places and soon stops being the same.

A headless CMS solves that by separating content from presentation. Editors work in one admin, and each channel fetches content through an API and displays it the way that suits it.

01

When headless makes sense

Most often when the same content needs to appear in several places: on the website and in a mobile app, on several websites for different markets, or on the website and an internal portal. A product, news item or price is then changed once and the change is everywhere.

The second reason is speed and freedom on the frontend. With presentation separated, the website can be built as a very fast modern application, and the frontend team works in the technology that suits it best, free of the CMS's limitations.

02

When you don't need it

For a ten-page brochure website, headless is overkill. You get two systems instead of one, two hosting setups and a bigger development bill, for little benefit. For a project like that we recommend classic website development, usually on WordPress.

The same applies if what matters most is that editors see the page exactly as it will look while they build it. That can be done with headless, but it takes extra work that should be budgeted from the start.

03

How we build headless projects

We work with PHP-based CMSs, from Ibexa to WordPress and Drupal in headless mode, and choose the one that fits the size of the project and the team that will edit it afterwards. We also work with headless CMSs that aren't written in PHP when the project calls for it.

Before coding, we define the content model: which content types exist, which fields they have and how they're connected. That determines how easy it will be to add a new channel in two years. Then we build the API, the frontend and a page preview for editors before publishing.

For websites we pay special attention to SEO. Pages are rendered on the server, so Google gets finished HTML with titles, metadata and structured data, not an empty page that only fills in inside the browser.

For larger systems that need user management, personalization and a product catalog on top of headless delivery, we often use Ibexa DXP, which supports both ways of working.

FAQ

Questions about headless CMS

It doesn't have to be. The problem arises when pages are rendered only in the browser. When they're rendered on the server, Google sees them like any other website.

Usually at the start, because two parts are built instead of one. It pays off when you have several channels or plan to add them, because each new channel costs less.

Yes, if the preview is built from the start. We always include it in the plan, because without it editors struggle to work.

Often, yes. First the content is moved into the new CMS and one new channel uses it through the API, and the old website is replaced when the time comes.

Not sure whether you need headless?

Tell us everywhere your content needs to appear. We'll tell you whether headless is the right path or whether there's a simpler solution.

Request a free estimate →