

Talking Drupal #487 - Single Directory Components Workflow
Feb 3, 2025
Brian Perry, a senior front-end developer at Chapter 3 and Nintendo aficionado, joins Jacob Rockowitz, a Drupal consultant and module maintainer. They dive into Single Directory Components (SDCs), discussing their advantages and potential pitfalls. Topics include how SDCs streamline workflows and their future impact on decoupled front ends. The conversation also highlights the Embedded Content module's role in facilitating rich content creation within Drupal, likening SDCs to Minecraft blocks, and sharing best practices for integrating these innovative components.
AI Snips
Chapters
Transcript
Episode notes
Understanding SDCs
- SDCs are Drupal's way of formalizing components, collecting markup, styles, and JavaScript in one directory.
- Unlike general web components, SDCs are Drupal-specific and enhance code organization.
SDCs in Client Projects
- Brian Perry's recent client projects, including a D7 to D10 migration, led him to use SDCs more.
- The projects suited SDCs as the frontend work was simple, and a decoupled approach wasn't necessary.
SDCs and JavaScript Components
- SDCs share core concepts with JavaScript components, such as props and slots.
- Props are data passed to components (like attributes), while slots are placeholders for markup.