Headless CMS
A headless CMS stores and delivers content through an API but has no front end of its own; a separate website or app decides how the content is shown.
The “head” is the presentation layer. Remove it and the CMS becomes a content database with an editing interface and an API. The website is built separately, in any framework, and fetches the content it needs.
This makes it possible to use the same content on a website, in an app and in a newsletter, and to rebuild the front end without migrating content. The trade-off is more moving parts: two systems to host and keep in step, and previewing a page before publishing needs extra work.
How Regular approaches it
Standard is headless. Payload CMS runs on its own Cloudflare Worker, and the Astro site fetches only published content from it over a private service binding. Nothing about the CMS is reachable from the public website, which shrinks the attack surface considerably.
Sources and further reading
- Headless content management system, Wikipediaen.wikipedia.org