Decoupled

Please give us a detailed overview of your session and why attendees will be excited to hear about it.  

Ensure that you let us know:

• What level of knowledge should attendees have before walking into your session
• What will your session accomplish and what will attendees walk away having learned

Please give us a detailed overview of your session and why attendees will be excited to hear about it.  

Ensure that you let us know:

• What level of knowledge should attendees have before walking into your session
• What will your session accomplish and what will attendees walk away having learned

When a decoupled project begins one of the hardest parts that I’ve found is setting up a local environment to simulate all of the necessary components. How will the CMS be served? How will the decoupled front end be displayed? What about the dev server for rendering previews? Can I still call it headless or is decoupled the only appropriate word?

Decoupled Drupal is the realization of Drupal as a content hub for frontend websites and web applications. Automated testing is critical to the success of decoupled systems due to the complexities of the overall architecture. In addition, the coverage provided by automated testing allows teams to focus on developing and releasing new features rather than fixing bugs that have made it into production.

This presentation is for anyone who has created a website using Drupal and is interested in discovering a standardized, simpler, and faster way to model and build a website's content and information architecture. 

When a decoupled project begins one of the hardest parts that I’ve found is setting up a local environment to simulate all of the necessary components.  How will the CMS be served? How will the decoupled front end be displayed? What about the dev server for rendering previews? Can I still call it headless or is decoupled the only appropriate word?

There are a lot of Drupal features we end up missing out on when going fully Decoupled. In a lot of scenarios, only a part of our application needs the functionality that Decoupled Drupal provides, and going overboard ends up hurting us more than it saves our time.

Can't we have your cake and eat it too? Well, we certainly can when we decouple progressively. With such an architecture we get to enjoy the strong suite of both Drupal and the Frontend framework without worrying about how to scale our infrastructure or the team.

If you find GatsbyJS, ReactJS, Angular, NextJS/NuxtJS, REST & GraphQL interesting then this talk is for you. We will learn how to marry 3 wonderful platforms to build insanely fast, offline-first, mobile-friendly, interactive Single Page Applications (SPA) / web sites.

An exploration of enterprise patterns for using GraphQL at NBA.com.  We will go over some interesting explorations and patterns in different areas such as scalability, performance, security, and flexibility. We will discuss a strategy of using nodjejs based graphql-compose with Drupal’s JSON API. We will discuss how you can integrate GraphQL at scale using special CDN headers and federation.

Why the attendees will be interested in the session?

This is the session to attend if you are considering developing a Gatsby website using Drupal as a backend content source. We will cover static-site generation with Gatsby, compare and contrast different content sources (or backends), and even show a demo of live content preview capabilities between Gatsby & Drupal.

This session is intended for beginners looking for a high level overview of the design/development process. We will live demo a working Gatsby / Drupal site while providing an overview of: