Thinking outside of the block. Embracing the power of a (sometimes) decoupled architecture.
Site Building
Learn how to leverage the flexibility of Drupal to deliver experiences in nearly limitless ways. See how you are able to do this—often without code and relying on the ever-expanding universe of contributed modules.
The Headless, or Decoupled Drupal concept has been around for a bit now, but what is it really? In this session we will go over some basics of a few key concepts around decoupling some (or all) content from the Drupal rendering pipeline, and how you can use this concept to create fast, lean, and modern applications while relying on Drupal to do the bulk of the content modeling work, and the less sexy, yet important bits like user and content management. The key takeaway here is that it is far from an all or nothing approach, hence:
“Render unto Caesar that which is Caesars, and render unto Drupal that which is Drupals.”
Use Drupal to render the content it's great at, and use something else to render the content it's not. Lots of Clients approach us these days looking for a specific tool. Maybe it’s a map, maybe it’s a timeline, maybe it’s a native application. Drupal isn’t necessarily always the best tool for the job for making these dreams come into fruition on the front end, but lots of our clients are already using it for their main web presence. While we could spend time building custom modules/etc within their existing install, sometimes this doesn’t really make sense. Enter the API.
We will take a look at a few simple, real world examples where we have chosen to decouple content for clients, how we did it, and how you can too!