Why We’re Using Headless CMS

Why Headless CMS Has Become Our Default

We built WordPress websites for years. It remains a useful platform and still makes sense for certain projects, but over time we found ourselves increasingly working around it.

The websites we wanted to create were becoming more distinctive and technically ambitious. We wanted greater control over performance, more freedom in the design process and a cleaner editing experience for our clients. Achieving that within WordPress often meant adding more plugins, adapting existing tools or accepting compromises we didn’t think should be necessary - we were wasting time and resources wrestling with limitations.

Eventually, it became clear that we needed a different approach.

We began moving our website projects to a Headless CMS and, after seeing the difference it made, rebuilt the Wilkes Wood website in the same way. Headless has now become our default approach for all non-ecom website projects.

But what does that actually mean, and what difference does it make to the finished website?

What is a Headless CMS?

Every website needs somewhere to manage its content. This is the system you log into when you want to change some text, upload an image, publish an article or add a new case study.

On a traditional platform such as WordPress, that content management area and the website your visitors see are part of the same system. The design, content and functionality are all closely connected.

A Headless CMS separates them.

Your team still has a straightforward place to manage content, but the public-facing website is designed and built separately. The two communicate behind the scenes, with the CMS sending the right content to the right place on the website.

That separation gives us much more control over the website itself. We can decide exactly how it should look, how it should behave and how quickly it should load without being restricted by a particular WordPress theme or editing system.

For our clients, the process remains simple: log in, make the change and publish it. The technical work happens out of sight.

Why we changed the way we build websites

Moving to Headless wasn’t about following a trend or using newer technology for the sake of it. It solved several problems we had repeatedly encountered when building more ambitious websites.

More freedom to design properly

When a website is built around an existing theme or page-building system, the tools can begin to influence the design. Even with a custom WordPress build, you are still working within the conventions and structure of that platform.

Headless gives us a much cleaner starting point.

We can design around the business, its content and its users rather than around the limitations of a theme. That gives us more freedom to create distinctive layouts, thoughtful interactions and stronger visual details without having to force them into a system that wasn’t designed for them.

It also helps us maintain consistency. Instead of building pages from a mixture of blocks, plugins and individual settings, we can create a clear design system that works across the whole website.

Faster, lighter websites

Website speed is affected by many things, including the quality of the code, the size of the images and the way the site is hosted. Simply describing a website as Headless doesn’t automatically make it fast.

What Headless gives us is much greater control over all of those things.

The website doesn’t need to load a large theme or an assortment of plugins that may only be partly used. We can build the front end around exactly what the project requires and optimise each part of it properly.

The result is a lighter website that loads quickly and feels responsive, even when it contains large images, animation or more advanced functionality.

That matters for the people using the site, particularly on mobile devices or slower connections. It also gives the website a stronger technical foundation for search performance.

A content management area built for your team

WordPress is widely used, but that doesn’t always make it easy to use.

Its management area can quickly become crowded with plugin settings, technical menus and editing options that clients don’t understand or need. Even a relatively simple content change can feel risky when you aren’t sure what everything controls.

We use Sanity as our content management system and configure it around each individual website.

If your team only needs to manage articles, case studies, services and team members, those are the options you’ll see. Each section uses clear fields and instructions, with no unnecessary settings getting in the way.

This creates a much simpler editing experience. Your team can concentrate on the content it is responsible for without worrying about accidentally changing the design or breaking part of the website.

Less dependence on plugins

Plugins are one of WordPress’s greatest strengths, but they can also become one of its biggest weaknesses.

They make it possible to add new functionality quickly, but every plugin is another piece of third-party software that needs to remain secure, supported and compatible with the rest of the website. A future update to WordPress, a theme or another plugin can sometimes create unexpected problems.

Headless websites generally depend on far fewer of these moving parts.

Where we need a particular feature or connection, we can choose the most appropriate way to build it rather than searching for a plugin that provides an approximate solution. This gives us a cleaner, more controlled codebase and reduces the likelihood of unrelated updates causing problems elsewhere.

A smaller target for common attacks

WordPress powers a huge proportion of the internet, which makes it a very familiar target for automated attacks. Outdated plugins, exposed login pages and poorly maintained themes can all introduce vulnerabilities.

WordPress can be secure when it is built and maintained properly. The difference with Headless is that the content management system is separated from the public website.

Visitors aren’t directly interacting with the CMS or its database when they browse the site. This removes several of the common routes attackers use against traditional WordPress installations and means there is less public-facing software that needs constant patching.

No website is completely immune from security risks, but Headless gives us a more controlled setup with a smaller attack surface.

A better foundation for new features

A website shouldn’t have to be rebuilt every time the business develops.

Because the different parts of a Headless website are separated, we can add new features and integrations without having to rework the entire system. That could mean connecting the website to a booking platform, displaying information from another service, creating a customer portal or introducing a new type of content.

It also means the content isn’t confined to one website. Information managed in the CMS can potentially be used across apps, displays and other digital services without your team entering it again in several places.

Most businesses won’t need all of that immediately. The advantage is having a website that leaves those options open rather than discovering later that its original setup has become a barrier.

A safer way to make changes

Headless also gives us a more controlled process for developing and updating websites.

We can prepare and test changes away from the live site before publishing them. Previous versions of the code are recorded, making it easier to see exactly what has changed and to return to an earlier version if a problem is discovered.

Clients don’t need to understand the technical workflow behind this. The important point is that updates can be properly built and checked before they affect the website their customers are using.

Is Headless always the right choice?

No platform is automatically right for every project.

A small, conventional website built around an existing template may not need a custom Headless setup. In those cases, WordPress can still be a practical and affordable option.

Headless becomes particularly valuable when a website needs to be genuinely bespoke, performance is important, the content is expected to grow or the business wants the freedom to introduce more advanced functionality later.

It also needs to be built properly. A poorly planned Headless website can still be slow, confusing and difficult to maintain. The technology provides the foundation, but the quality of the strategy, design and development still determines the result.

Why it’s now our default

Headless gives us the freedom to build websites around our clients rather than around the limitations of a particular platform.

We can create more distinctive designs, deliver stronger performance and give clients a content management area that has been shaped around the way they actually work. We also have a cleaner foundation for supporting and developing the website after it launches.

That combination is why Headless has become our default at Wilkes Wood.

If you’re considering a new website and want to understand whether a Headless approach would suit your business, get in touch. We’ll talk you through the options in plain English and recommend the approach that makes the most sense for the project.