Glossary
Headless CMS
A headless CMS is a content management system that stores and edits content but does not control how it is displayed. It sends the content through an API to a website, app or other screen that is built separately.
Headless vs traditional CMS
| Traditional CMS | Headless CMS | |
|---|---|---|
| How pages are built | The CMS stores content and renders the pages, usually through a theme | The CMS stores content; a separate front end, for example Next.js, builds the pages |
| Where content can go | Mainly one website | Websites, apps and other channels, through an API |
| Extra features | Often added with plugins | Built into the front end or added as separate services |
| Examples | WordPress, Drupal, Joomla | Strapi, Contentful, Sanity |
When does a headless CMS make sense?
- You want a fast, custom front end such as a Next.js site, while editors keep a familiar editing screen.
- The same content has to appear on a website and in an app.
- You want fewer plugins on the public site to update and look after.
For a small brochure site that rarely changes, a traditional CMS is often the simpler choice.
Frequently asked questions
Can WordPress be used as a headless CMS?
Yes. WordPress has a built-in REST API, so it can send content to a separate front end while editors keep using the WordPress dashboard. This is a common first step when moving a WordPress site to Next.js.
Is a headless CMS harder for editors?
Editing text and images is usually much the same. The difference is that page layouts are set in code, so a new kind of page needs a developer, while day-to-day content changes do not.