Headless CMS
A headless CMS is a content management system that only manages content and delivers it via an interface, while presentation on website, app or other channels is developed separately.
In classic systems such as a traditional WordPress, content management and presentation are tightly linked. In the headless approach the “head” is missing — the frontend is built, for example, with React or Next.js and fetches content via an API.
Advantages are high speed, more design freedom, better security and the ability to use the same content on website, app and other channels. The trade-off is a higher development effort.
A practical example is the agroplanta website: first WordPress as a headless CMS, since 2026 Payload CMS — with a frontend built on Next.js.
What to look out for
- Check whether the benefits justify the extra effort: multiple channels, high demands on speed or design, frequent development.
- Choose a CMS your own team can work with comfortably — including preview.
- Plan content models carefully: which content types, fields and relationships exist?
- Consider preview, publishing workflow and editor permissions from the start.
- Arrange hosting, backups and updates for CMS and frontend together.
Common mistakes
- Headless is chosen for a small brochure website that a classic system would handle more simply.
- Editors cannot see their changes before they go live.
- Nobody is responsible for updating CMS and frontend.
Frequently asked questions
Yes. Editors work in an admin interface as usual; only the presentation on the website is technically separate. With a preview they see changes before publishing.
Yes. WordPress can deliver content via its API while the frontend is developed separately — which is how agroplanta was first implemented.