Headless content management system

Last updated

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]

Contents

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]

One advantage of this decoupled approach is that content can be sent via APIs to multiple display types, like mobile and Internet of things (IoT) devices, alongside a website. [1] A disadvantage, however, is that maintaining two separate systems for a single site can require more resources. [3]

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. [4] [5] 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. [6]

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. [7]

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, website design, and templates inseparable. [8]

Decoupled CMS

A decoupled CMS and a headless CMS have a lot in common as a headless CMS is a type of decoupled architecture. [9]

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. [10] [11]

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. [12] 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.

Related Research Articles

In software engineering, multitier architecture is a client–server architecture in which presentation, application processing and data management functions are physically separated. The most widespread use of multitier architecture is the three-tier architecture.

A content management system (CMS) is computer software used to manage the creation and modification of digital content . A CMS is typically used for enterprise content management (ECM) and web content management (WCM).

<span class="mw-page-title-main">Drupal</span> Web content management system

Drupal is a free and open-source web content management system (CMS) written in PHP and distributed under the GNU General Public License. Drupal provides an open-source back-end framework for at least 14% of the top 10,000 websites worldwide and 1.2% of the top 10 million websites—ranging from personal blogs to corporate, political, and government sites. Systems also use Drupal for knowledge management and for business collaboration.

In software engineering, the terms frontend and backend refer to the separation of concerns between the presentation layer (frontend), and the data access layer (backend) of a piece of software, or the physical infrastructure or hardware. In the client–server model, the client is usually considered the frontend and the server is usually considered the backend, even when some presentation work is actually done on the server itself.

Headless may refer to:

A web content management system 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 programming languages or markup languages create and manage website content. A WCMS provides the foundation for collaboration, providing users the ability to manage documents and output for multiple author editing and participation. Most systems use a content repository or a database to store page content, metadata, and other information assets the system needs.

Nuxeo is a software company making an open source content management system.

<span class="mw-page-title-main">DotCMS</span> Open source content management system

dotCMS is an open source content management system (CMS) written in Java for managing content and content driven sites and applications.

<span class="mw-page-title-main">Umbraco</span>

Umbraco is an open-source content management system (CMS) platform for publishing content on the World Wide Web and intranets. It is written in C# and deployed on Microsoft based infrastructure. Since version 4.5, the whole system has been available under an MIT License.

django CMS

django CMS is a free and open source content management system platform for publishing content on the World Wide Web and intranets. It is written in Django language framework, with Python.

ProcessWire is a free and open source content management system (CMS), content management framework (CMF) and web application framework (WAF) written in the PHP programming language. It is distributed under the Mozilla Public License 2.0. ProcessWire is built around an API with usage and naming conventions similar to the JavaScript framework jQuery. The stated goal behind the API is to provide the level of accessibility and control to pages in a website that jQuery provides to the DOM. Content is managed either via the API or the web-based admin control panel. ProcessWire is largely used for development of web sites, web applications, services, content feeds and related applications.

Omni CMS (formerly OU Campus) is a web content management system (CMS) for colleges, universities, and other higher education institutions.

Cloud CMS is an enterprise content management system offered under both a SaaS and an On-Premises model using Docker containers. It was designed from the ground up to leverage a fully elastic architecture built on top of Amazon AWS, Elastic Search, and MongoDB in order to provide a "Headless" CMS.

Zesty.io is a decoupled SaaS cloud-based Web Content Management System that allows companies to create, deploy, maintain, and optimize enterprise web properties. It is specifically designed for mid-market and enterprise brands. It is built on globally available Google Cloud Platform infrastructure and, as a SaaS product, requires no hardware or software resources. Zesty.io also allows for collaborative website building and for users to manage multiple web properties from a single portal.

Magnolia is an open-source content management system (CMS). It is developed by Magnolia International Ltd., based in Basel, Switzerland. It is based on Content repository API for Java (JSR-283).

<span class="mw-page-title-main">Enonic XP</span>

Enonic XP is a free and open-source web application platform and content management system (CMS) in one based on Java and Elasticsearch. Developed by the Norwegian software company Enonic, the microservice web platform can be used to build progressive web applications, Next.js websites, or web-based APIs. Enonic XP uses an application framework for coding server logic with JavaScript, and has no need for SQL as it ships with an integrated content repository. The CMS is fully decoupled, meaning developers can create traditional websites and landing pages, or use XP in headless mode, that is without the presentation layer, for loading editorial content onto any device or client. Enonic is used by major organizations in Norway, including the national postal service Norway Post, the insurance company Gjensidige, the national lottery Norsk Tipping, the Norwegian Labour and Welfare Administration, and all the top football clubs in the national football league for men, Eliteserien.

A Micro-app is a super-specialized application designed to perform one task or use case with the only objective of doing it well. They follow the single responsibility principle, which states that "a class should have one and only one reason to change." Micro applications help developers create less complex applications while reducing costs by breaking down monolithic systems into groups of independent services acting as one system.

TerminusDB is an open source knowledge graph and document store. It is used to build versioned data products. It is a native revision control database that is architecturally similar to Git. It is listed on DB-Engines.

Headless commerce is an e-commerce architecture where the front-end (head) is decoupled from the back-end commerce functionality and can thus be updated or edited without interfering with the back-end, similar to a headless content management system (CMS). The term was coined by Dirk Hoerig, co-founder of Commercetools, in 2013.

Contentful is a headless content management system (CMS), founded in 2013 in Berlin, Germany by Sascha Konietzke and Paolo Negri. The company and the platform are both called Contentful. As of June 2021, the company is headquartered in San Francisco, California, with offices in Denver, Colorado and Berlin.

References

  1. 1 2 Garcia, Veronica; Writer, Staff (2021-02-15). "Should your content management system go headless?". The American Genius. Retrieved 2021-02-25.
  2. ↑ Davis, Kim (2021-04-13). "The rise of headless and hybrid CMS: Tuesday's daily brief". MarTech Today. Retrieved 2021-04-19.
  3. ↑ Lamoureux, Chris (2019-07-04). "What Is Headless CMS? Pros & Cons of Decoupling Your CMS - Veriday Blog". Veriday. Retrieved 2021-04-19.
  4. ↑ Petr Palas. "Why 2017 Is the Year of Cloud-First Headless CMS". CMSWire. Retrieved 2017-01-30.
  5. ↑ Stephen Griffin (7 February 2017). "Cloud-First Headless CMS: What It Is and Why You Should Use It" . Retrieved 2017-02-07.
  6. ↑ Levitz, Michael (2021-02-10). "3 Ways Covid Changed E-Commerce Forever: Your online store is now your flagship. Here's how to make it pop". Inc .
  7. ↑ Mortazavi, Alireza (2020-09-14). "Headless CMS vs WordPress vs Custom Solution [Tech Debates]". Medium. Retrieved 2021-02-25.
  8. ↑ Mixon, Erica (2020-10-28). "Headless CMS powers personalized, omnichannel e-commerce". TechTarget. Retrieved 2021-02-25.
  9. ↑ Heusser, Matt. "An overview of headless architecture design". SearchAppArchitecture. Retrieved 2021-04-19.
  10. ↑ Deane Barker (8 February 2017). "The State of the Headless CMS Market" . Retrieved 2017-02-08.
  11. ↑ Brent Heslop. "A History of Content Management Systems and the Rise of the Headless CMS" . Retrieved 2019-01-12.
  12. ↑ "9 Challenges of Scaling a Headless CMS". CMSWire.com. Retrieved 2022-04-06.
  13. ↑ Kaya, Ismail. "Do You Need a Headless CMS? Maybe, Maybe Not". CMSWire.com. Retrieved 2021-04-19.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.