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.
However, even with a progressively decoupled drupal project, there are a lot of scenarios where we might run into challenges. In this session, I'll try to address some of them. We will go through the following:
1. When to opt for progressively decoupled Drupal and how it compares to fully decoupled
2. How to structure your components and how various Drupal modules can make this simple for you
3. How to build components that work in harmony with Drupal localization.
4. Which Frontend library should we use and when does it make sense to use something else
5. Optimize data fetching when querying data from Drupal and third-party APIs
6. Using Drupal for tracking Frontend errors.
