Headless, Traditional or Hybrid CMS?
When planning a new website or redevelopment, one of the first questions an organisation should ask, even before engaging an agency is: What do we actually need our website to do?
This has become an increasingly difficult question to answer as the technology landscape evolves. Organisations now have more options than ever, with traditional content management systems (CMS), SaaS platforms and headless architectures offering different levels of flexibility, functionality and complexity.
Over recent years, headless architecture has emerged as an increasingly popular alternative to traditional CMS implementations such as WordPress and Craft CMS, alongside integrated SaaS platforms like Shopify and Webflow.
But does every organisation need a headless CMS?
The answer depends on its requirements, existing technology investments and long-term digital ambitions.
Understanding the architectural differences
In a traditional or monolithic implementation, the CMS and frontend website are closely integrated. Content management, presentation and supporting functionality operate within the same platform, typically sharing a common hosting environment.
Headless architecture separates the frontend from the CMS. Content is delivered through APIs, allowing developers to build independent frontend experiences using technologies such as Next.js.
Hybrid CMS architecture combines elements of both approaches, allowing a platform to support traditional website rendering alongside API-driven content delivery.
These distinctions matter because architectural decisions influence far more than website functionality. They affect how marketing teams manage content, how easily new systems can be integrated and the resources required to maintain the website over time.
Headless isn’t inherently better than traditional architecture. Each approach offers advantages and trade-offs that should be evaluated against an organisation’s actual requirements.
When traditional architecture makes sense
For organisations relying heavily on established plugins, applications or off-the-shelf functionality, we generally recommend considering a traditional implementation before introducing the additional complexity of headless architecture.
Platforms such as WordPress and Shopify benefit from extensive ecosystems of plugins, applications and integrations that allow businesses to introduce functionality without significant bespoke development.
This is particularly relevant when third-party functionality directly influences the frontend experience, including memberships, forms, subscriptions, product reviews and customer accounts.
While these capabilities can often be replicated within a headless environment, doing so may require additional development and ongoing maintenance.
Traditional Shopify implementations use Liquid templates and Shopify’s established storefront architecture. Businesses can leverage its application ecosystem for marketing automation, shipping, customer engagement and other operational requirements.
Client example: Black Snake Strops
Our work with Black Snake Strops demonstrates the advantages of a traditional Shopify implementation.
By working within Shopify’s established ecosystem, the business can benefit from integrated commerce functionality and third-party applications without the additional responsibilities of maintaining a separately developed frontend.
For organisations primarily focused on operating an online store, the convenience of an integrated platform can outweigh the additional flexibility offered by headless architecture.
This doesn’t imply limited digital ambition. Rather, it recognises that an established platform may already provide the functionality and flexibility the business requires.
When headless architecture becomes advantageous
Headless architecture becomes increasingly attractive for organisations with complex digital requirements, particularly those integrating multiple business systems, distributing content across different channels or evolving their digital platforms over time.
Rather than relying on a single platform to manage every aspect of the website, headless architecture allows organisations to select specialised technologies and integrate them into a unified digital experience.
This approach can also make content more reusable across websites, applications and other digital channels, provided it has been structured appropriately within the CMS.
Separating the frontend from the backend provides greater flexibility to evolve individual systems without necessarily rebuilding the entire website, although this depends on how integrations and content models are implemented.
Client example: ANZSOG
Our ongoing work with the Australia and New Zealand School of Government (ANZSOG) demonstrates the advantages of this approach.
For ANZSOG, we implemented Storyblok as the primary content management platform, with Next.js responsible for delivering the frontend website experience.
This provides a flexible foundation for managing marketing content while supporting integrations with other business systems.
Through our ongoing innovation partnership, we’re continuing to explore opportunities to more tightly integrate platforms such as Zoho and Salesforce into the website experience.
Rather than operating as an isolated publishing platform, the website can become part of a broader digital ecosystem where content, customer information and business processes work together.
Client example: Life Fitness
Our recent work with Life Fitness demonstrates another advantage of headless architecture: combining specialised platforms that each perform different responsibilities.
The website uses Storyblok to manage structured, reusable marketing content, while Shopify provides eCommerce functionality. A custom Next.js frontend brings these systems together into a unified experience.
This architecture supports Life Fitness’s distinct commercial and home-use audiences, including different purchasing journeys, while allowing marketing content to be managed independently of Shopify’s traditional theme system.
It’s an example of composable architecture, where individual technologies are selected for their strengths rather than expecting a single platform to accommodate every requirement.
What about hybrid CMS architecture?
Hybrid CMS architecture is often described as a middle ground between traditional and headless, although the distinction requires some clarification.
A hybrid CMS supports both traditional rendering and API-driven content delivery. For example, a WordPress website might use a traditional WordPress theme for its primary website while supplying content through APIs to a mobile application or customer portal.
However, organisations can also retain an established CMS while moving their entire frontend to a headless architecture.
Client example: Westbourne Grammar
For Westbourne Grammar, we retained WordPress as the content management system while developing a new frontend using Next.js.
This allowed staff to continue working within a familiar environment, retain established functionality such as Gravity Forms and simplify content migration from the previous website.
At the same time, the independently developed frontend provides flexibility for future integrations, including planned HeyGen SDK functionality supporting an AI-powered chatbot experience.
While technically a headless WordPress implementation rather than a fully hybrid delivery model, it demonstrates how organisations can modernise their digital experience without abandoning existing technology investments.
Comparing the options
Each approach offers different advantages depending on an organisation’s requirements.
Traditional CMS platforms generally offer lower development costs, established editing workflows and extensive plugin ecosystems, with simpler ongoing maintenance.
Headless architecture provides greater frontend flexibility, integrations and content reuse, but typically requires higher investment and more technical maintenance.
Hybrid approaches combine familiar content management tools with flexible content delivery, although complexity varies depending on implementation.
Performance and usability also depend on implementation rather than architecture alone. A well-optimised traditional website can perform just as effectively as a headless website, while the editorial experience ultimately depends on the CMS and how it’s configured.
How to make the right decision
Before selecting a CMS architecture, organisations should consider several practical questions:
- Existing technology: Are there established plugins, applications or workflows that would be costly to replace?
- Content requirements: Will content need to be reused across multiple websites, brands or digital channels?
- Integrations: How closely must the website interact with CRM, ERP, eCommerce or other business systems?
- Internal resources: Does the organisation have the technical expertise and budget to maintain multiple integrated platforms?
- Future requirements: Is the website likely to evolve significantly over its expected lifespan?
The answers should guide both architectural and platform selection.
For organisations with straightforward requirements and established publishing workflows, traditional architecture may provide the most cost-effective solution.
For those managing complex digital ecosystems, headless architecture can offer the flexibility needed to support ongoing innovation.
Hybrid capabilities and headless implementations of established CMS platforms can also provide opportunities for incremental modernisation.
Ultimately, the objective isn’t to adopt the newest technology. It’s to select an architecture that balances functionality, flexibility, investment and long-term operational requirements.
At JTB Studios, we approach CMS selection by understanding an organisation’s requirements before recommending a platform or architecture.The best solution is the one that solves your organisation’s problems without introducing unnecessary complexity.