One of the most frequent questions when we propose a custom website is: “And then how do I change the text myself?”. It’s a legitimate concern. Having to call a developer to correct your opening hours makes no sense. In many cases, the answer is a headless CMS.
Traditional CMS vs. headless
A traditional CMS, such as WordPress, does two things at once: it stores the content (text, images, posts) and generates the pages the visitor sees. Both parts are tied together: the design depends on a theme, and the website depends on that system running on every visit.
A headless CMS only deals with content. Your team edits it in a convenient panel, and the website (built, for example, with Astro) fetches it to generate the pages. “Headless” literally means “without a head”: the content manager doesn’t decide how the website looks.
What you gain by separating content and presentation
Speed. The website can be generated as static pages that are served instantly. The content manager isn’t involved in each visit, so it doesn’t slow it down.
Security. The admin panel isn’t exposed at the same address as the public website. Many of the automated attacks that go looking for the WordPress admin login simply disappear.
Design freedom. The design isn’t limited by what a theme or visual builder allows. You build exactly what the business needs.
Reuse. The same content can feed the website, a mobile app, a screen in your premises or an email newsletter.
What options are there
There are cloud-based headless CMSs such as Sanity, Contentful, Storyblok or Hygraph, with free plans for small projects. There are also options you can host yourself, such as Strapi, Directus or Payload.
And if the project already has a Django backend, its admin panel can serve as the content manager, with the advantage of having everything (content, bookings, customers) in one place.
When it makes sense
- Your team updates content fairly often: menu, events, offers, news.
- You want the performance of a static website without giving up the ability to edit it yourself.
- You have content that’s shown across several channels.
- You’re concerned about security and the constant maintenance of plugins.
When it isn’t worth it
If your website has five pages that change twice a year, a content manager can be more complex than necessary. In that case, asking for the occasional change is cheaper than maintaining another tool.
And if your team relies on very specific features of the WordPress ecosystem that it doesn’t want to lose, it’s worth thinking it through carefully before switching.
The key: think about who will be editing
A good content manager isn’t the one with the most features, but the one your team will use without fear. Before choosing, define which parts of the website need editing and who will do it. From there, the panel is set up to show only those fields, with no options that could break the design.