Component-based Drupal
summary
Focuses on a practical pipeline: build components in Pattern Lab with a twig template, Sass partial and JSON sample data, bring that library into Drupal via Composer vendor install, map Drupal fields to component variables with a twig “presenter,” and use core Layout Builder or the UI Patterns module to expose patterns as blocks or view modes. Claims it reduces duplication, but mapping complex render arrays and cache tags is often the painful part; the decoupled library + Composer approach works in real projects and UI Patterns helps with caching and site‑builder workflows.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:00Componentbased Drupal
- 13:05Common approaches
- 15:30Baseline approach
- 17:10Card markup
- 21:10Getting used to it
- 25:33Image markup
- 29:18Twitter field value
- 37:57References
- 42:47Example
- 45:57Media Current
- 46:47UI Patterns
- 47:47Default Template
- 48:07Field Layouts
- 50:27View Modes
- 52:27CSS Structure
related talks
59mGetting Atomic with Pattern Lab
41mBuilding Your Legos: A Practitioner’s Guide to Reusable Components
42mComponents everywhere! - Bridging the gap between backend and frontend
49mLiving Styleguide in your Drupal projects: Benefit from component driven design.
30mAce any design in Drupal - layout tools and components in your site-building toolbox
46mIntroduction to the UI Patterns module
44mFostering Collaboration: Pattern Libraries / Rapid Prototyping
30mIt's About Systems