A headless content management system (CMS) stores and manages content but does not decide how it looks. Instead, it sends content through an API to a separate front end, such as a website, app or kiosk. The 'head' is the display layer, and a headless system leaves it out.
In short
In a traditional CMS such as WordPress, the same system manages content and builds the pages. A headless setup separates them, which gives more freedom in design and lets one set of content feed many places. The trade-off is more to build and run, so a simple site rarely needs it.
Consider it when one content store must feed a site, an app and other channels, when a custom front end is needed for speed or design, or when a large team edits content in one place. For a small business site, a standard setup is usually simpler and cheaper to keep running.
Our web application development page covers custom builds.
A real person reads every message and replies.
