Can we figure this Drupal Component thing out already?

Over the last two years our community has seen the rise of countless solutions to implement design systems and components within Drupal. During the same period - across camps, cons and the internet at large - Adam and Brian have been having an ongoing conversation about best practices in component based development.  

There was initially quite a bit of good natured debate; as Brian focused on ease of component integration (often with the help of contributed modules), and Adam focused on a platform agnostic approach favoring functionality in Drupal core. But, as time went on and approaches in the community matured, they found their perspectives aligning more and more.

This session will present their (mostly) shared vision of a set of best practices for component based development. They still disagree on some stuff, but that’s part of the fun. We’ll review:

• The current approaches in the community, along with some limitations.

• Our goals for a component based design system.

• How to break down your patterns using atomic design principles to represent the ideal state of design system components.

• How to manage your pattern library as an external dependency of your Drupal project.

• How to limit processing in your pattern library, and handle processing and mapping within your CMS.

• Common misconceptions about integrating design system patterns in Drupal.

• A baseline approach to implementation in Drupal - using Drupal core and limited contributed modules.

• The role of popular component-friendly contributed modules

• Emerging technology for the future of component based development.

Finally, we’ll go live with a brief demo of the shared approaches in action.