| 词条 | Headless content management system |
| 释义 |
A headless content management system, or headless CMS, is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via a RESTful API for display on any device. The term “headless” comes from the concept of chopping the “head” (the front end, i.e. the website) off the “body” (the back end, i.e. the content repository). IntroductionWhereas a traditional CMS typically combines the content and presentation layers of a website, a headless CMS is just the content component and focuses entirely on the administrative interface for content creators, the facilitation of content workflows and collaboration, and the organization of content into taxonomies. It doesn’t concern itself with presentation layers, templates, site structure, or design, but rather stores its content in pure format and provides access to other components (e.g. delivery front ends, analytics tools, etc.) through stateless or loosely coupled APIs. The headless CMS concept is one born of the demands of the digital era and a business’s need to focus on engaging customers with personalized content via multiple channels at all stages of the customer journey. As the content in a headless CMS is considered “pure” (because it has no presentation layer attached) just one instance of it can be used for display on any device; website, mobile, tablet, Internet of Things devices, smart watches, etc. There is some confusion around what makes a headless CMS truly “headless”, as vendors use the term somewhat loosely to label their decoupled or hybrid CMS systems. But a true headless CMS is one that was built from the ground up to be API-first, not a full monolith CMS with APIs attached afterwards. Cloud-first headless CMSs are those that were also built with a multitenant cloud model at their core and whose vendor promotes Software as a service (Saas), promising high availability, scalability and full management of security, upgrades, and hotfixes, etc. on behalf of clients.[1][2] Common features
Coupled CMS vs. Headless CMSMost traditional (monolithic) CMS systems are “coupled”, meaning that the content management application (CMA) and the content delivery application (CDA) come together in a single application, making back-end user tools, content editing and taxonomy, website design, and templates inseparable. Coupled systems are useful for blogs and basic websites as everything can be managed in one place. But this means that the CMS code is tightly connected to any custom code and templates, which means developers have to spend more time on installations, customizations, upgrades, hotfixes, etc. and they cannot easily move their code to another CMS. Decoupled CMS vs. Headless CMSThere is a lot of confusion around the differences between a decoupled CMS and a headless one because they have a lot in common. A decoupled CMS separates the CMA and CDA environments, typically with content being created behind the firewall and then being synchronized and pushed to the delivery environment. The main difference between a decoupled CMS and a headless CMS is that the decoupled architecture is active—it prepares content for presentation and then pushes into the delivery environment—whereas a headless CMS is reactive—it sits idly until a request is sent for content. Decoupled architecture allows for easier scalability and provides better security than coupled architecture, but it does not provide the same support for omnichannel delivery. Plus, there are multiple environments to manage, hiking up infrastructure and maintenance costs.[3] [4]Advantages of Headless CMS software
Disadvantages of Headless
See also
References1. ^{{cite web|url=http://www.cmswire.com/digital-experience/why-2017-is-the-year-of-cloud-first-headless-cms|title=Why 2017 Is the Year of Cloud-First Headless CMS|author=Petr Palas |access-date=2017-01-30}} 2. ^{{cite web|url=https://www.cmscritic.com/cloud-first-headless-cms-what-it-is-and-why-you-should-use-it/|title=Cloud-First Headless CMS: What It Is and Why You Should Use It|author=Stephen Griffin|access-date=2017-02-07}} 3. ^{{cite web|url=https://gadgetopia.com/post/9926|title=The State of the Headless CMS Market|author=Deane Barker|access-date=2017-02-08}} 4. ^{{cite web | url=https://www.contentstack.com/blog/content-management-systems-history-and-headless-cms | title=A History of Content Management Systems and the Rise of the Headless CMS| author=Brent Heslop|access-date=2019-01-12}} 5. ^{{cite web|url=https://bitwizards.com/Thought-Leadership/Blog/2017/March/What-the-Headless-CMS-Means-for-Marketers|title=What the Headless CMS Means for Marketers|author=Candace R. Mitchell|access-date=2017-03-31}} External links
1 : Content management systems |
| 随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识，基本涵盖了大多数领域的百科知识，是一部内容自由、开放的电子版国际百科全书。