Not That Kind of Decoupled Drupal

Decoupled Drupal

The speed at which technology is evolving, and the astounding array of digital channels users can access content from is dizzying. Organizations have to give their users the flexibility they crave. At the same time businesses must strive to manage structured content across different communication channels consistently, and scalably. Organizations have to give much more consideration to how their digital experience and the back-end content management systems are architected. To do this efficiently means that teams need to have the flexibility in front-end frameworks. As a result, the decoupled and headless CMS emerged. So, when we hear the term decoupled Drupal we often think about a Javascript front-end and Drupal Web Service API backend.

A Different Decoupling

This isn’t the kind of decoupling between the front and the back-end, but it is a kind of decoupling that results in the efficiencies and scalability that organizations need in order to thrive. This is decoupling the business logic away from Drupal concepts. Drupal then becomes a wrapper around the library to handle incoming web requests, configuration and display logic. This PreviousNext article takes a look at this specific approach to decoupling the model from Drupal.

Decoupling the Model From Drupal

The decision to take a different approach.

Main Photo by Simon Matzinger on Unsplash