We Value Your Privacy

We use technology such as cookies on our website, and through our partners, to personalize content and ads, provide social media features, and analyse our traffic. To find out more, read our privacy policy and Cookie Policy. Please also see our Terms and Conditions of Use. By accepting these terms you agree to your information being processed by Inbox Insight, its Partners or future partners, that you are over 18, and may receive relevant communications through this website, phone, email and digital marketing. For more information on how we process your data, or to opt out, please read our privacy policy. Our policies and partners are subject to change so please check back regularly to stay up to date with our terms of use and processing.

Accept Terms Settings
x

Please Sign-In to Access this Report

To access other reports on the platform please sign in with your username and password, or register for a free account to get unlimited access and insight customized for you.

Report Acquia Decoupled Drupal 101

Decoupled Drupal 101

A decoupled architecture allows developers to utilize any technology to render the front-end experience 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.

Report Snap Shot

  • How a decoupled architecture works
  • When you should consider decoupling
  • How developers and designers can leverage decoupled Drupal to deliver ambitious digital experiences

Related Content