Headless content management system

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Headless content management system" – news · newspapers · books · scholar · JSTOR (October 2017) (Learn how and when to remove this message) This article is written like a personal reflection, personal essay, or argumentative essay that states a Wikipedia editor's personal feelings or presents an original argument about a topic. Please help improve it by rewriting it in an encyclopedic style. (December 2022) (Learn how and when to remove this message) This article may have been created or edited in return for undisclosed payments, a violation of Wikipedia's terms of use. It may require cleanup to comply with Wikipedia's content policies, particularly neutral point of view. (December 2022) This article needs attention from an expert in Computing. The specific problem is: superficial exposition. WikiProject Computing may be able to help recruit an expert. (October 2023) (Learn how and when to remove this message)

A headless content management system, or headless CMS, is a back end-only web content management system that acts primarily as a content repository. A headless CMS makes content accessible via an API for display on any device, without a built-in front end or presentation layer. ^[1]

Whereas a traditional CMS typically combines a website's content and presentation layers, a headless CMS comprises the content component and focuses on the administrative interface for content creators, the facilitation of content workflows and collaboration, and the organization of content into taxonomies.^[2]

Cloud-first headless CMSes are those that were also built with a multi-tenant cloud model at their core and whose vendors promote software as a service (SaaS). These vendors promise high availability, scalability, and full management of security, upgrades, and hotfixes on behalf of clients.^[3][4] Headless commerce uses the same setup to separate back-end product management and navigation from the front end of a website or other display types (e.g., IoT). This is similar to how headless CMSes focus on creating content in the back end to be displayed on front ends via APIs.^[5]

Headless CMS is similar to but distinct from the use of widgets or plugins on a site, like adding an online ordering and delivery plugin to a restaurant website.^[6]