Headless CMS
A content management system that decouples the content backend from the frontend presentation layer, delivering content via API to any channel or device.
Definition
A headless CMS is a back-end content repository that stores and manages content but has no built-in frontend (no “head”). Instead of rendering pages itself, it exposes content through an API – typically REST or GraphQL – which developers consume to build any presentation layer they choose: a React app, a mobile app, a smart TV interface, or a static site.
Why it matters
Traditional CMSes like WordPress couple content storage tightly to HTML rendering, which limits flexibility. A headless approach lets teams choose the best frontend technology independently of the CMS, reuse content across multiple channels simultaneously, and achieve better performance by serving statically generated pages rather than server-rendered PHP.
Example
A company might store all their content in Contentful or Sanity (headless CMSes), then build their marketing site in Next.js, their mobile app in React Native, and their in-store kiosk in a custom interface – all pulling from the same content API. This is often called an “omnichannel” content strategy.