 | In the web development world, few trends are spreading more rapidly than decoupled (or headless) content management systems. A decoupled architecture allows developers to utilize any technology to render the front-end experience (“the glass” where a user interacts with an application) in lieu of the theming and presentation layers that come with a coupled CMS out-of-the-box. In a decoupled Drupal architecture, the Drupal back end exposes content to other front-end systems, such as native mobile applications, conversational UIs, or applications built in JavaScript frameworks. Organizations may select a decoupled Drupal approach for a few reasons. Some implement a decoupled strategy to leverage Drupal as a content repository to serve content to any device in a complex digital ecosystem. Others favor decoupling to allow front-end teams to use popular JavaScript frameworks while maintaining the back-end capabilities of Drupal. For example, digital agencies are taking advantage of decoupled Drupal to showcase creativity in the front end with JavaScript Model-View-Controller (MVC) frameworks, such as Angular or Ember. Request Free! |
