How do you build and manage a design system’s frontend architecture that is both scalable and maintainable? The typical tools and techniques for approaching design systems often break down when trying to scale across multiple sites, integrate with dynamically injected content, or keep the system up to date. Many of these technical boobytraps aren't discovered till late in development, but can be avoided through progressively decoupled components. This session (originally presented at Drupalcon Seattle 2019) is most appropriate for frontend developers & architects or teams building and maintaining a design system. You will learn:

• Why and how to decouple a design system from Pattern Lab and Drupal
• Preventing component fragmentation in Drupal through the use of web components
• Pattern Lab improvements and techniques to reduce rework and ease Twig-based component integration
• How distributing a design system via NPM (yes, NPM) can help teams overcome technical hurdles with Composer


Comments are closed.

Very informative and inspiring session, I particularly loved the visual part and how Salem reacted on questions and kept all us focused and served different needs: devs, frontend and even testers got many things to take away! Thank You!

Nina Tymińska at 11:36 on 3 Jun 2019

I am very inspired to dig into subject, thanks! :)