What is a CMS?
How a content management system separates editorial work from site delivery—and when you still need engineering.
A content management system (CMS) lets non-developers create, edit, and publish digital content—pages, posts, media, structured records—while the CMS enforces roles, workflows, and storage.
Classic vs headless
- Coupled (traditional): one product renders HTML themes (historically WordPress, Drupal).
- Headless: the CMS exposes APIs; your team builds the public site in a separate framework.
See What is a headless CMS? for API-first tradeoffs.
What a CMS usually provides
- Modeling — fields, relationships, locales
- Editorial UI — drafts, previews, roles
- Publishing — when content goes live
- Assets — images and files with metadata
Engineering still owns performance, security, caching, and deployment of the customer-facing app.
Next steps
Compare vendors on platforms or read WordPress alternatives if you are leaving a coupled stack.