Practically Decoupled Drupal

Using Drupal 8 as a backend to serve content to a separate lightweight frontend can produce incredibly flexible, beautiful and reusable pieces of front and backend code. With the right approach and a little practice, the ability to decouple Drupal can be a fantastic tool in your belt.

Decoupling Drupal doesn't necessarily mean a 100% separation of Drupal from a Drupal-free frontend. In practice, the ability to decouple a discrete piece of your application from Drupal can actually be a small part of a greater whole. This often turns out to be simpler and faster and can free your hands to create beautiful and intuitive user experiences.

Over the last year we've had the opportunity to use Drupal in a decoupled way on many different projects. These included standalone e-learning games using Drupal as a datastore, Drupal-backed native iOS applications, and extending traditional Drupal web pages with highly interactive apps.

In this session we’ll share what we've learned building and consuming Drupal 8 APIs - how to extend existing Drupal applications, where the pain points are, how to avoid them, and especially how not to reinvent the wheel.

You’ll get perspectives from front- and back-end development.  John Ferris has led the front-end development efforts on Aten’s decoupled React and React Native applications. Gabe Sullice is actively involved in ensuring Drupal has first-class API support. He is co-maintainer of the JSON_API module for Drupal 8, maintainer of the Entity Query API module, a more lightweight complement to Drupal's core REST module and contributor to Acquia’s Waterwheel project, a Javascript SDK for Drupal.

Slides: https://pixelwhip.github.io/practically-decoupled-drupal/#/

Session track: 
Session skill level: 
Session speaker(s): 
Session time slot: 
Session room: