Designing with a system goes by many names: atomic design, pattern libraries, modular design, component-based design…but regardless of what you call it, implementing a system can help make a project more consistent and scalable, and your team more efficient. In the recently released 2017 Design in Tech Report from John Maeda, shareable design systems are specifically called out, suggesting the method definitely having a moment. But, one thing we’ve noticed about all the discussion about design systems is that—generally speaking—they’re all from in-house groups. What about using a design system as a consultant?
Every spring, anticipation builds in the Drupal community. DrupalCon — the official conference for the Drupal community to participate in learning sessions, talks, code sprints, and social events — is around the corner. While several “Cons” are held internationally, this marked my first experience at the event, held this year in New Orleans, Louisiana.
Kicking-off sessions was Drupal’s founder and Acquia CTO, Dries Buytaert. The opening keynote was well-attended and furiously tweeted with the affectionate #DriesNote as excited developers, product owners, and sellers-of-open-source anxiously awaited Dries’ SOD (state of Drupal) speech.