Headless versus traditional
A traditional CMS such as WordPress owns both the content and the templates that render it. A headless CMS such as Sanity or Contentful owns only the content; the front end is yours to build in whatever framework you choose.
The trade is flexibility for convenience. You gain full control of the front end and lose the ability to preview a change by clicking around a page, unless you build that preview yourself.
| Traditional CMS | Headless CMS | Webflow | |
|---|---|---|---|
| Front end | Bundled themes | You build it | Visual, built in |
| Content reuse | One site | Any number of channels | Mostly one site |
| Editor experience | Familiar | Depends on what you build | Visual and familiar |
| Developer needed to publish | No | For the front end | No |
| Best fit | Simple sites | Multi-channel content | Marketing sites teams run |
When it is the right call
- Content has to appear in more than one place, such as a site plus a product
- You want a front-end framework the CMS does not dictate
- The content model is complex enough to deserve real structure
- Your team has developers. A headless CMS without one is a liability
When it is overkill
For a marketing site that one team publishes to, a visual CMS such as Webflow usually wins. Editors get a real preview, there is no build step to wait on, and nobody has to maintain a front end.
Why it matters for B2B marketing teams
Headless is frequently sold to B2B marketing teams who do not need it. It suits genuine multi-channel content. For a marketing site that one team publishes, it usually buys a developer dependency in exchange for flexibility nobody uses.