Headless CMS
A headless CMS is a content management system that stores and manages content but has no built-in front end; it delivers content through an API to a website, app or other channel.
“Headless” means the content (body) is separated from the presentation (head). Examples include Contentful, Sanity and Storyblok. Developers build the website separately and pull the content in.
Pros and cons
Pro: one content source for many channels, such as website, app and product.
Pro: flexible for complex content models and large teams.
Con: every design change usually needs developers.
Con: more moving parts, such as hosting, builds and integrations.
Some teams combine both: miro.com runs on Framer synced with Contentful. See the Miro case study and Contentful vs. Framer.
FAQ
When does a headless CMS make sense?
When the same content must feed several channels, or when a large content team needs complex workflows. For a marketing website alone, a built-in CMS is often simpler.
Can Framer work with a headless CMS?
Yes. Content from a headless CMS such as Contentful can be synced into Framer’s CMS.
Related terms
Content Management System (CMS)
A content management system (CMS) is software that lets people create, edit and publish website content, such as blog posts, case studies or job listings, without changing the site's code or design.
Framer
Framer is a visual website builder and design tool for creating, hosting and managing production websites without hand-written code, with a built-in CMS, localization, animations and hosting.
Website migration
A website migration is moving a website to a new platform, domain, structure or design, for example from WordPress or Webflow to Framer, while keeping content, search rankings and integrations intact.
Related at Trueform:
