GOJI
All terms
WebsitesReviewed by Minh P.

Headless CMS

A headless CMS stores your content but doesn't render your website: it hands the content over an API to whatever front end you build. The "head" (the display layer) is yours to choose, which is the point.

Why it matters

One content source can then feed the website, the app, the sales deck and the AI answer without copy-paste drift. You also stop rebuilding content every redesign: the words and structure persist while the skin changes. The cost is that you need developers to build and maintain the head.

How it works

Editors work in a structured editing UI; content is saved as fields (not finished pages) and served over an API. The site (often built in a framework like Next.js) fetches those fields and renders them into designed pages. This site works exactly this way: Sanity for content, a custom front end for the design.

What to do about it

Go headless when structure and multi-surface reuse matter and you have (or hire) the engineering to own the front end. If the website is a straightforward marketing site owned by marketing, a visual platform is usually the saner buy.

Related termsCMSAPIDesign system