Headless CMS
Short definition
A headless CMS keeps content separate from page design and delivers that content to a website, app or other channel through an API.
A content editor enters text and images through a panel as usual, but the system does not pair it with a ready-made template; it stores it purely as structured data. A website, mobile app or any other screen then pulls that data through an API and displays it with its own design.
You meet it when the same product description needs to appear on a website, a mobile app and a third-party screen; content is entered once and used everywhere.
It is often confused with a classic CMS. A classic CMS manages content and presentation together, whereas headless content stands alone; that flexibility can make development a little more involved.
The most common mistake is letting editors enter content with no visual preview at all, never seeing how it will actually render on each channel, which can make text overflow the layout or an image get cropped awkwardly. The correct approach is to define length limits for every content field and to give editors a real preview for each channel before anything is published.
Why it matters
Copying the same content by hand across several channels wastes time and invites mistakes. A headless CMS manages content from one place and keeps a website and a mobile app equally current.
Illustrative example
A spa chain's service list is pulled into both its website and its booking app from the same headless CMS, so one update reaches both channels at once.
