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 A How-To Guide to Headless and Decoupled CMS

A How-To Guide to Headless and Decoupled CMS

The rapid evolution of diverse end-user clients and applications has given rise to a dizzying array of digital channels to support.

Websites in the past were built from monolithic architectures utilizing web content management solutions (CMS) that deliver content through a templating solution tightly “coupled” with the CMS on the back-end. Agile organizations crave flexibility, and strive to manage structured content across different presentation layers consistently in a way that’s scalable. Accomplishing this efficiently requires that teams have flexibility in the front-end frameworks that dominate the modern digital landscape.

Report Snap Shot

  • Defining Decoupled CMS
  • Platform Considerations
  • Decoupled Flexibility: Progressive vs. Fully Decoupled
  • Practical Decoupled Use Cases
  • Why JavaScript Matters
  • Best Practices: Drupal API

Related Content