Decoupled Drupal

Learn More

A decoupled CMS 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. Developing decoupled, digital experience applications involves using front-end components and frameworks, decoupled CMS's and content services, standard APIs, and cloud and application services. It also requires a DevOps culture. Some of the key decoupled design points are the digital app reference platform, the decoupled CMS, and the structured content that is required to implement amazing experience apps.

Posted by Preston So
If you have decided to decouple Drupal, after conducting due diligence with regard to assessing the risks and rewards of decoupling Drupal and understanding how best to decouple Drupal in 2018, it is essential to understand how web services in Drupal 8 core and their dependencies undergird all decoupled Drupal architectures, regardless of the application you are implementing. In this Experience Express column, we’ll explore the process of decoupling Drupal through the…
Posted by Preston So
At no point in the history of digital content has there ever been such a dizzying proliferation of devices in our lives, and experiences we encounter and consume. Long the most critical element of an organization’s digital presence, the website is increasingly treated as just a single facet in a kaleidoscope of content channels and form factors. Many of today’s users, in the course of acquiring content or data, never touch a desktop web browser at all. How do we…
Posted by Leah Wagner
This summer we were excited to launch a new website for Scanse. After they impressively fulfilled their Kickstarter funding, The Jibe was brought on board to develop their new website. After assessing their short and long term needs, we decided to move full steam ahead with developing their site using Drupal 8. We knew the Drupal 8 contributed module ecosystem was not up to speed with Drupal 7. However, we also knew that Drupal core, out of the box, was more robust…
Posted by Preston So
With the advent of web services in Drupal 8 core, decoupling Drupal — namely, using Drupal as a content repository to expose data for retrieval and manipulation by other applications — has never been easier. Now, with the REST module in core, you can transform Drupal into a data service without custom code or substantial configuration. But is it a good idea? What are some of the considerations you should scrutinize when opting for a fully decoupled project? Decoupling…