Build It Better, Stupid: Using Design Systems for Scalability
summary
Drupal sites pile up inconsistencies — one client has 73 content types and a HubSpot audit found 100+ shades of gray — so the claim is that a component-first process lets teams add any component to any page with minimal dev work. Workflows use Sketch + InVision Design System Manager, a build-spec spreadsheet, and Drupal tools like Paragraphs browser, Layout Builder plus Paragon/Themekit and Webpack to create a componentized theme. The result is fewer one-offs, faster handoffs, and easier content entry.
AI-written summary · about
chapters (18)
- 0:00Start
- 5:27E3 + DESIGN SYSTEMS
- 5:58ATOMIC DESIGN
- 8:17SO, WHAT'S A DESIGN SYSTEM?
- 8:54WHY BOTHER?
- 10:40DESIGN SYSTEM TYPES
- 21:25BUILD SPEC.
- 30:47DEVELOPMENT
- 31:42PARAGRAPHS.
- 35:47PARAGRAPHS BROWSER
- 38:25ADDITIONAL MODULES
- 41:39PARAGON DRUPAL 8 BASE BUILD
- 42:19THEMEKIT STARTER THEME
- 48:34PLANNING A PAGE
- 52:17IDEAS
- 58:37QUESTIONS?
- 59:08FEEDBACK
- 59:23CONTRIBUTION DAY
