![]() ![]() If you would like to dive in further, here is a great blog by Dries Buytaert on decoupled Drupal architecture in 2018. Here’s an image to help you visualize the difference between a more traditional Drupal architecture and a decoupled Drupal setup. To put it very simply, decoupled Drupal separates your front end experiences from the back end CMS. The Drupal CMS serves as an interface for editors to enter content, but its primary use is as a store for content. The visitor will see pages created with Javascript frameworks (like Angular.js, React.js, or Ember), rather than a traditional Drupal theme. With decoupled Drupal, a website visitor will not interact with Drupal directly, much like shoppers do not interact with the back of a brick and mortar store. ![]() The back of the store exists to house items that employees can access and feature in the departments for customers to see. You walk in and enjoy the ambiance, interact with the items across departments, maybe chat with an employee, but you never venture into the back of the store. Think about your favorite department store. But do you know what it means and what the implications of decoupled Drupal are for marketers? In this guide we will define decoupled Drupal and share three reasons why marketers should consider a decoupled architecture as they evolve their digital experience platforms. ![]() If you are considering a move to Drupal 8, or upgrading your current Drupal platform, it’s likely that you’ve come across the term “decoupled Drupal”, aka “headless Drupal”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |