🔗 Sections: Contributing to the design system | Project details | Taking it over the finish line | Feedback & results
The past contribution strategy was based on partnerships between the product designer and Design System designer which took time away from a product's existing roadmap and also required significant project management on the part of the Design Systems team. To further promote contributions, we created a new strategy that gave more ownership to the Design Systems team.
With the creation of a new streamlined contribution process, my project roadmap was focused on supporting the pilot program of vetted components being contributed back to the Lyft Product Language (LPL).
With each component contribution, I focused on the quality standards that are built into the LPL to elevate the product designer's work. And from their use case, help create usage guidelines to be used across the entire product.
⬆️ Back to top
The first review that I perform on the product designer's component is to ensure the LPL attributes are being used which includes Color, Typography, Elevation, and Spacing. From here, I perform a check for design patterns that apply to similar LPL components. This is especially important when the component being contributed will be applied to both Native (Android and iOS) and Web platforms. Any inconsistencies along with design recommendations, I make sure to review them with the contributing product designer to ensure full transparency as well as promote a collaborative environment.
Quality review for the Inline Message Card component contribution.
Quality review for Web Global Header component contribution.
Quality review for Segmented Control component evolution (adding Detail text).
Once the design tweaks have been approved by the stakeholders, the real work begins to start to define the component in its entirety. From a design system standpoint, we consider things like:
A few of the Inline Message Card component definitions.
A few of the Web Global Header component definitions.