Big systems, big problems: lessons learned building 40 design systems
keylerwerve
martensc
Extensive digital platforms require extensive design, so it’s not uncommon for our design systems to have upwards of 100 components. How do product owners make sure that they’re including all of the necessary components, or at least prioritizing the most important? How do developers and designers stay in alignment on naming conventions across the design system and the CMS? How do clients know what components they have and how they are supposed to use them?
The Palantir.net team has built 40+ design systems, and we’re sharing our processes and tools to help you keep your design system creation work aligned with your engineering team and client-friendly.
Learning Objectives
At the end of this session, attendees will have a set of templates and tricks for:
-
Identifying and prioritizing the components/templates to create for a new design system
-
Ensuring that the design system component names match the Drupal back-end
-
Creating effective design system documentation for client teams
Target Audience
This session is for Designers, Front End developers, and Product Owners.
Prerequisites
Knowing the basic principles of design systems will help, because we'll be focusing on practical implementation tips and tricks.
Track
User Experience, Accessibility, & Design
Experience Level
Beginner
When & Where
Time:
Tuesday, 14 July, 2020 - 21:15 to 22:00
Room:
Hopin Sessions
If no timezone is set on your profile, time is displayed in UTC.
Update your profile's timezone
