![]() ![]() After all, as a marketer, being able to get content out to any device quickly is paramount. The back-and-forth interaction happens in real-time in the browser.Īt this point, you might be wondering why everyone isn’t heading toward decoupled CMS. When the logic is on the front-end interface, the back-end CMS can be streamlined. In other words, you, as a content provider, no longer need to worry about how the content is going to be displayed as that is handled on the device itself.ĭecoupled CMS may also be faster. When the user interface is decoupled from the CMS, the logic for displaying content on each device is on the front-end and can provide full control of the user experience in its native tools. New devices are popping up all the time and one of the big questions that marketers need to ask is how they will provide content on them. With a headless CMS, it is possible to build flexible, responsive, interactive experiences for your users. Benefits of Decoupled Drupal to Marketers This module along with other powerful modules such as Views and Paragraphs makes Drupal a good choice for a decoupled application. Then, a different framework uses that API to access, format, deliver, and display the data.ĭrupal 8 includes a RESTful Web Services module in its core which plays well into adopting a headless CMS. In a headless installation, the data display functionality is replaced with an API to the data. In normal installations, Drupal provides a way to store data, an administrative area to manage content, and a way to display data. But if you have a Drupal website, you will want to know more about headless Drupal. ![]() The decoupled CMS approach is industry wide and affects more than just those using Drupal. This separated content management and display means that the content is easily used by other sites and apps. Think of Drupal as the host, managing the content and offering that content as a service. You will often hear this strategy as API-first.ĪPI-first is an approach that starts with the RESTful API as the communication between the backend, headless CMS and user devices such as websites, mobile applications, wearable, IoT devices and more.Ĭontent as a Service (CaaS) is like a Software as a Service (SaaS), headless CMS. It’s considered “headless” because it means chopping off the part of the CMS that provides the web display.Ī headless CMS usually delivers content through an API, which means that it can deliver content anywhere, on any device. What is Decoupled (Headless) Drupal? Some Terms to KnowĪ decoupled CMS is one where the CMS serves as the back-end to store, maintain, and edit content but no longer necessarily provides the delivery of that content. Then I’ll share what factors you should consider when deciding whether to follow a decoupled CMS strategy. ![]() However, first, here are some terms marketers should know. The strategy has its place, but is not always the best option for several reasons. Much of the conversation is still occurring in the developer community, but it is also important for marketers to understand the implications of this strategy as well. ![]() In fact, Acquia is holding Decoupled Developer Days this weekend (August 19-20 in NYC). It is a hot topic in the Drupal community. Basically, it allows developers to write to many platforms without having to tediously recreate the wheel each time. Well, um.what the heck does that mean? It means that you can publish a piece of content and then use different systems to display that blog post on a computer, a mobile device, a voice-based system like Amazon’s Alexa, or even a smart watch. This web development strategy, in its most basic form, is a “write once, publish anywhere” technology that separates the content from the presentation layer. Decoupled-or “headless”-content management systems have been trending in the last few years. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |