Glossary
Headless CMS
A headless CMS manages website content separately from how it is displayed, so editors update text and images in a simple interface while developers control the design and performance of the site.
In a traditional CMS such as a classic WordPress set-up, content, templates and the server that renders pages are bundled together. A headless CMS only stores and edits content; the website is built separately and pulls content in.
Why do companies choose a headless or Git-based CMS?
- Speed. Pages can be pre-built as static files and served from a global network, which keeps them fast on mobile connections.
- Security. With no database or admin login on the public site, there is far less to attack.
- Editor-friendly. Marketing teams get a clean editing screen without risk of breaking the layout.
- Reuse. The same content can feed the website, apps or other channels.
What’s a Git-based CMS?
A variant where content is saved as files in a Git repository rather than a database. Every change is versioned, reviewable and easy to roll back. It suits company websites, documentation and blogs well.
See our B2B digital agency service.
Updated
Get help with B2B Digital Agency
Websites, content and campaigns that turn B2B buyers into qualified sales conversations.