I recently found myself returning to traditional Drupal theming after multiple years working primarily in decoupled front ends. While I was admittedly nervous about losing access to some of my go-to tools, I was excited to put Single Directory Components (SDCs) through their paces to understand what impact they would have on my theming workflow.
Spoiler alert: SDCs are pretty great. In many ways they exceeded my expectations, providing a sturdy bridge to the techniques I learned in my time away from Twig. But at the same time, they still face some of the constraints I bumped up against in past Drupal themes.
In this session I will walk through the workflow I used to build a custom Drupal theme that relies heavily on Single Directory Components. Together we’ll look at the good and the bad, and also pick up some tips and tricks along the way, including:
- SDC friendly approaches to prototyping outside of Drupal.
- Mapping concepts from JavaScript components to Single Directory Components.
- Leveraging SDCs to simplify your build process.
- Mapping SDCs to Paragraphs and other Drupal entities.
- Indispensable SDC related tools from the contrib ecosystem.
- Where SDCs fall short and my dreams for the future of SDCs and Drupal theming.
