Headless CMS

A headless CMS is a content management system that separates the back-end content repository from the front-end presentation. Editors use an admin interface, and developers fetch the content as JSON through a REST or GraphQL API.

Why it matters

The same content can feed a website, a mobile app and a kiosk, and developers can use any front-end technology. The price is more work: you must build and host the front end, previews and routing yourself. The API also becomes a dependency, so its uptime and rate limits affect your site.

Example

A request and response:

GET /api/articles/blue-kettle
{
  "title": "Blue Kettle",
  "body": "<p>Boils in 90 seconds.</p>",
  "updated": "2026-10-01"
}

The front end inserts this data into its own templates.

Common mistakes

• Choosing headless when a traditional CMS would meet every need with less effort.
• Ignoring editor previews, which frustrates the content team.
• Hitting the API from the browser on every visit without caching.

Related

• CMS
• Jamstack
• Static Site Generator
• Fetch API
• टूल: Http status checker

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.