Strapi, Contentful, Drupal, Directus: Compare headless CMSs, choose the right platform, and implement it. A complete guide by Smile experts.
A website. A mobile application. An interactive kiosk. A voice assistant. A smartwatch. Organizations today distribute their content on an increasing number and diversity of channels.
Traditional CMSs were designed for a single channel: the website. Faced with modern omnichannel needs, they are showing their limitations. Headless CMS is the architectural solution to this problem.
This guide explains what a decoupled CMS is, how to choose the right platform for your context and how to implement it.
- The Headless CMS market is projected to exceed $1.6 billion by 2024 and is growing at over 22% per year (MarketsandMarkets, 2024)
- 63% of organizations adopting a headless architecture cite frontend flexibility as their primary benefit (Contentful State of Digital Experience, 2024)
What is a Headless CMS?
A CMS (Content Management System) is a content management system that allows editorial teams to create, organize, and publish content without technical skills. WordPress, Drupal, and Joomla are the best-known traditional CMSs.
In a traditional CMS, the content management backend and the presentation frontend are tightly coupled. The CMS generates the HTML pages directly. This is simple to implement but restrictive: the frontend is dictated by the CMS, and distribution on channels other than the web requires specific development.
A headless CMS is a content management system that completely separates the back end, which stores and manages content, from the front end, which displays it. Content is exposed via APIs (REST or GraphQL) and consumed by any front end: a website built with React or Vue.js, an iOS or Android mobile application, an interactive kiosk, a voice assistant, or any other digital channel.
The term "headless" comes from the absence of a "head," meaning an integrated presentation layer. The CMS manages the content. The front-end consumes the content. The two evolve independently.
Traditional CMS vs Headless vs Decoupled
There is an important difference between headless and decoupled.
A decoupled CMS (like Drupal in decoupled mode) retains its native presentation layer while also exposing its content via APIs. This hybrid approach allows for a gradual migration to headless architecture.
A pure headless CMS (Strapi, Contentful, Sanity) has no built-in presentation layer. It is designed from the ground up to expose content via APIs only.
Comparative Table: Traditional vs. Headless CMS
Criteria | traditional CMS | Headless CMS |
Frontend flexibility | Weak | Total |
Omnichannel distribution | Difficult | Native |
Performance | Average | Excellent |
Technical complexity | Weak | High |
Editorial independence | High | Depends on the interface |
Initial cost | Weak | Medium to high |
SEO | Integrated | Managed on the front end |
Accommodation | Simple | Separate (CMS + frontend) |
Time-to-market | Fast | Longer |
Vendor lock-in | Depends on the CMS | Low if open source |
Leading Headless CMS Platforms
Strapi: French open-source headless headphones
Strapi is the most widely adopted open-source headless CMS. Developed in France, it can be self-hosted on any infrastructure, exposes content via REST and GraphQL APIs, and features a clear and customizable administration interface.
Its MIT license for the Community version makes it the ideal sovereign solution for French organizations subject to the GDPR. It is the preferred choice for teams that want complete control over their data and infrastructure.
Contentful: the leading SaaS
Contentful is the most widely used headless SaaS platform in large organizations. Its editorial interface is very polished, its integration ecosystem is very rich, and its API performance is excellent.
Its positioning is enterprise-oriented: high prices, but top-tier support and reliability. It's the choice of major brands and organizations with internationally distributed editorial teams.
Sanity: Real-time headless navigation
Sanity stands out for its structured content approach and its fully customizable editing studio (Sanity Studio). It supports real-time collaboration between editors and offers a very powerful GROQ API (proprietary query language).
It is the preferred choice for development teams who want a tailored editorial experience and advanced structured content capabilities.
Directus: Headless computing on an existing database
Directus is unique in its category: it connects directly to an existing SQL database (PostgreSQL, MySQL, SQLite) and automatically transforms it into a REST and GraphQL API with an administration interface.
This is the ideal solution for organizations that already have a structured database and want to expose this content via a decoupled CMS without data migration.
Decoupled Drupal: Enterprise Power
Drupal is the leading open-source CMS for large organizations, public administrations, and complex projects. In decoupled mode, it retains its full power (access management, editorial workflows, multilingual support) while exposing content via JSON:API or GraphQL for modern frontends.
This is the choice for projects with very advanced editorial governance requirements, an existing Drupal base, or strict compliance constraints.
WordPress headless: the progressive option
WordPress exposes its content via the WP-JSON REST API and can be used as a headless backend with a decoupled frontend (Next.js via WPGraphQL, for example). This is an option for organizations that want to leverage their existing WordPress base while modernizing their frontend.
How to choose your Headless CMS
Technical criteria
Three questions guide the technical choice. Is the API RESTful, GraphQL, or both? Does the performance meet your traffic requirements? Is the platform extensible via plugins or hooks for your specific needs?
Editorial criteria
Is the administration interface suitable for the non-technical profiles of your editorial team? Do the publishing workflows (draft, review, publication) cover your processes? Does the role and permission management meet your governance requirements?
Organizational criteria
Do you have any data sovereignty constraints that exclude US SaaS providers? What is your total ownership budget (license, hosting, development)? Does your team have the skills to maintain a headless architecture?
Decision guide by profile
- Startup or technical team : Strapi (open source, flexible, sovereign) or Sanity (customizable studio)
- Large organization, distributed editorial team : Contentful (mature SaaS) or decoupled Drupal (enterprise open source)
- Existing database : Directus (direct connection without migration)
- Existing WordPress database : WordPress headless via WPGraphQL
- Strict GDPR constraints : Self-hosted Strapi or Directus
Implementing a Headless CMS
Typical architecture
A standard headless architecture comprises three layers. The back-end CMS manages and stores content, exposed via APIs. The API layer (REST or GraphQL) transports the content to the frontends. The frontend (Next.js, Nuxt, mobile application) consumes and presents the content.
Integration with frontend frameworks
Next.js and Nuxt.js are the most widely used frameworks with a decoupled CMS. They natively support SSR and SSG, which allows for the generation of complete HTML pages from the CMS content, guaranteeing excellent performance and optimal SEO.
Most headless platforms offer official SDKs for Next.js, Nuxt and other major frameworks, which simplify content retrieval and typing.
Headless SEO management
SEO is one of the most sensitive topics in headless architecture. In a traditional CMS, SEO is managed directly by the CMS. In headless architecture, it's managed on the front end.
Modern frameworks (Next.js, Nuxt) natively handle meta tags, sitemaps, and structured data. However, this responsibility must be explicitly addressed in the frontend project and not left to the default configuration.
Sovereign deployment and hosting
For organizations with GDPR or sovereignty constraints, self-hosting Strapi or Directus on a SecNumCloud certified sovereign cloud is the recommended configuration. The frontend can be deployed on Vercel, Netlify, or a sovereign CDN, depending on the requirements.
Smile and Headless CMS
At Smile, we have been implementing headless CMS architectures since the early days of the paradigm. Our expertise covers Strapi and Directus for sovereign open source projects, decoupled Drupal for enterprise projects with advanced governance requirements, and the integration of these platforms with Next.js and Nuxt.js frontends.
We support our clients from the platform selection phase (needs audit, solution benchmarking) to production launch, including architecture design, integration development and editorial team training.
Do you want to implement a headless architecture for your organization? Discover our expertise in Headless CMS with Drupal or Strapi .
Frequently Asked Questions about Headless CMS
Is a Headless CMS always more efficient than a traditional CMS?
Not necessarily inherently, but it offers the potential for maximum performance. Actual performance depends on the frontend implementation: a Next.js site with statically generated content (SSG) powered by Strapi will be extremely fast. A well-optimized traditional WordPress site can also be very performant. The difference is that headless architecture offers more optimization levers, notably the separation of the frontend's CDN cache from the CMS's API cache.
Is it possible to migrate from WordPress to a Headless CMS without rebuilding everything?
Yes, gradually. Two approaches are possible. The first is to switch WordPress to headless mode using WPGraphQL and developing a new frontend: the content remains in WordPress, only the presentation changes. The second is to migrate the content to a new headless CMS (Strapi, Contentful) while rebuilding the frontend. The first approach is less risky but retains the limitations of WordPress. The second is more ambitious but produces a cleaner architecture in the long run.
How to manage content previews in a headless architecture?
Previewing is one of the technical challenges of headless development. Major platforms offer native mechanisms: Strapi exposes a preview mode, while Contentful and Sanity have dedicated preview APIs. On the front end, Next.js and Nuxt.js support Draft Mode (formerly Preview Mode), which allows content to be displayed in draft form before publication. Implementation requires specific configuration but is well-documented for major platforms.
Headless CMS and GDPR: what are the risks with SaaS solutions?
American SaaS solutions (Contentful, Sanity) host data on servers subject to the Cloud Act. If your content includes personal data or sensitive information, this risk must be assessed in your GDPR impact analysis. Self-hostable open-source alternatives (Strapi, Directus) on a SecNumCloud-certified sovereign cloud eliminate this risk and are recommended for French organizations with strict regulatory constraints.