An External Design System in Practice
summary
Rebranding migrates three sites into a single style system but ends with a partial Drupal 8 migration and two WordPress sites all sharing the same components. Design system lives in its own repo built with Pattern Lab, pulled into Drupal via composer require and installed into theme libraries.yml with twig namespaces from the Components module. WordPress gets Twig through the Timber plugin, workflow uses composer tags, composer update, and gulp tasks to prototype and sync changes.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:13BRIAN PERRY
- 2:22REBRANDING
- 2:53MIGRATION
- 4:08PROTOTYPING
- 6:56LET'S KEEP THE MUSTARD SEPARATE
- 8:47REQUIRING THE DESIGN SYSTEM
- 11:34INCORPORATING INTO THEME
- 12:35COMPONENT WORKFLOW
- 14:23LUNAMETRICS TRAINING SITE SCOPE
- 15:33WORDPRESS INTEGRATION
- 16:36TIMBER COMPONENT - TRAINING ITEMS
- 19:45ONBOARDING
- 22:31LINES BETWEEN CMSES BLUR
- 24:03YOUR NEEDS MAY BE DIFFERENT
- 24:53THINGS TO CONSIDER
related talks
45mExternal Design Systems in Practice
01h 00mBuild It Better, Stupid: Using Design Systems for Scalability
20mDesign Systems for the Rest of Us
22mRebranding, or the subtle art of juggling new and legacy design systems
40mHow to optimise the workflow between designers and developers using design..
23mDesign Systems 101
27mDesign Systems, Not Pages
29mWorkflow in the Age of the Design System