Evolving and maturing the Design System through collaboration.
The OneUL Design System was born out of collaboration, and feedback and contributions from product teams are essential to its success. The focus for the first version release was on defining the design specification and HTML and CSS examples for core UI elements based on the atomic design methodology. Now that these basic elements are in place, product teams actively using the design system or who are transitioning to the design system, will drive its evolution.
This contribution model is for product teams who are actively using the design system. For product teams planning a transition to the design system please go here.
- Propose a new UI component or pattern
- Propose an enhancement or new variation of an existing component
- Propose a documentation improvement or change
- Contribute or enhance code for an existing element (HTML/SCSS, JavaScript, Angular, or React components)
Please [contact the Design System Team](mailto:LST.UL.DesignSystem@ul.com?subject=Design System Contribution Proposal) if you'd like to contribute. The first step is to schedule a conversation to review your need.
Evaluation of New Components - done by Design System team
- Determine if the element should be added to the design system
- Decide who owns the work
Design** - done by contributor and/or Design System team**
- Define the requirements and anatomy of the pattern
- Agreement and approval from the Design System team
Build and Test** - done by the contributor and/or Design System team**
- Create Figma components in a branch. (Optionally also in XD)
- Create HTML, S/CSS, and Javascript components
- Create Pull request
Release** - done by the Design System team**
- Merge Figma branch
- Create a new release of any code
- Design review and testing
- Code review and testing
- Accept PR
The Design System Governance Team, a team of designers and developers from across the organization, is responsible for reviewing and approving additions to the design system.