Misplaced Pages

Headless content management system

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Content management system without a front end
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 Misplaced Pages 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 Misplaced Pages's terms of use. It may require cleanup to comply with Misplaced Pages'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.

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 (SaaS). These vendors promise high availability, scalability, and full management of security, upgrades, and hotfixes on behalf of clients. 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.

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, 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

This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources in this section. Unsourced material may be challenged and removed. (March 2021) (Learn how and when to remove this message)

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

  1. 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. Petr Palas. "Why 2017 Is the Year of Cloud-First Headless CMS". CMSWire. Retrieved 2017-01-30.
  4. Stephen Griffin (7 February 2017). "Cloud-First Headless CMS: What It Is and Why You Should Use It". Retrieved 2017-02-07.
  5. 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.
  6. Mortazavi, Alireza (2020-09-14). "Headless CMS vs WordPress vs Custom Solution [Tech Debates]". Medium. Retrieved 2021-02-25.
  7. Mixon, Erica (2020-10-28). "Headless CMS powers personalized, omnichannel e-commerce". TechTarget. Retrieved 2021-02-25.
  8. Heusser, Matt. "An overview of headless architecture design". SearchAppArchitecture. Retrieved 2021-04-19.
  9. Deane Barker (8 February 2017). "The State of the Headless CMS Market". Retrieved 2017-02-08.
  10. Brent Heslop. "A History of Content Management Systems and the Rise of the Headless CMS". Retrieved 2019-01-12.
  11. "9 Challenges of Scaling a Headless CMS". CMSWire.com. Retrieved 2022-04-06.
  12. Kaya, Ismail. "Do You Need a Headless CMS? Maybe, Maybe Not". CMSWire.com. Retrieved 2021-04-19.

External links

Category: