A headless content management system, or headless CMS, is a
back end-only
web content management system
A web content management system (WCM or WCMS) is a software content management system (CMS) specifically for web content. It provides website authoring, collaboration, and administration tools that help users with little knowledge of web program ...
that acts primarily as a
content repository. A headless CMS makes content accessible via an
API
An application programming interface (API) is a connection between computers or between computer programs. It is a type of software interface, offering a service to other pieces of software. A document or standard that describes how to build ...
for display on any device, without a built-in front end or
presentation layer.
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.
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
Software as a service (SaaS ) is a cloud computing service model where the provider offers use of application software to a client and manages all needed physical and software resources. SaaS is usually accessed via a web application. Unlike o ...
(SaaS). These vendors promise high availability, scalability, and full management of security, upgrades, and hotfixes on behalf of clients.
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.
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.
Coupled CMS vs. headless CMS
Most monolithic content management systems are 'coupled', meaning that the content management application (CMA) and the content delivery application (CDA) come together in a single
application. This makes back-end user tools, content editing and
taxonomy
image:Hierarchical clustering diagram.png, 280px, Generalized scheme of taxonomy
Taxonomy is a practice and science concerned with classification or categorization. Typically, there are two parts to it: the development of an underlying scheme o ...
,
website design, and templates inseparable.
Decoupled CMS
A decoupled CMS and a headless CMS have a lot in common as a headless CMS is a ''type'' of decoupled architecture.
The decoupled architecture allows for easier scalability and provides better security than coupled architecture, but it does not provide the same support for omnichannel delivery. There are multiple environments to manage, hiking up infrastructure and maintenance costs.
Criticisms and disadvantages
Headless CMS is a content management system (CMS) without a pre-built front-end presentation layer or templating system; instead, it provides a content repository and an API for managing the content. While this allows for greater flexibility and customizability, it can also present challenges or drawbacks for teams and organizations. The main downside is that it may require more effort to set up and configure and a certain level of web development knowledge on both the front and back end.
* They require heavier technical proficiency than their monolithic counterparts.
References
External links
*{{cite web, url=http://www.cms-connected.com/News-Archive/December-2016/The-Ultimate-Guide-for-Headless-Content-Management, title=The Ultimate Guide for Headless Content Management Systems, first=Venus, last=Tamturk, date=December 16, 2016, accessdate=2018-06-07, website=CMS-Connected
Content management systems