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 Alex Moreno Lopez
DrupalCon is an exciting time. Lots of talks, lots of sessions and topics to attend. However making sure you see everything and anything you want can be stressful as well. So what should you attend to make the most of this DrupalCon experience?  Fear not, I am back to give you some of the highlights of an amazing week packed with talks, learnings, surprises and more.  And with the quantity and high quality of the sessions this year, no matter your interests, be…
Posted by Preston So
GraphQL is a rapidly maturing solution available as a web service in Drupal 8 and many production sites leverage GraphQL on Drupal. GraphQL is particularly robust as a web service due to its focus on tailored responses and readily available introspection layer. In addition, upon installation, GraphQL provides a built-in debugging tool and user interface named GraphiQL that allows us to issue queries and inspect responses in real time, located at /graphql/explorer. In…
Posted by Preston So
In a previous installment of Experience Express, we explored how effective core REST out of the box can be for the purposes of consuming content retrieved from Drupal and manipulating said data as well. Furthermore, with the help of Views, any content listing can be easily converted into an API resource. As these features indicate, Drupal 8 is a powerful web services provider that can expose content to any consumer application on any channel. Nonetheless, sometimes…
Posted by Preston So
As we saw in a previous installment of Experience Express, because Drupal has a HAL-compliant REST API available out of the box with minimal configuration, you can easily provision an API that can immediately be employed to consume content entities and manipulate them from other applications. Now that we have successfully exposed content entities as REST resources, used Entity Access to govern permissions, and customized the formats and authentication mechanisms in use…