A process for proposing, designing, and adding new components or patterns to the design system.
A design system is a living product that evolves with the needs of the team and the product. Contributions from designers and developers ensure the system stays relevant, comprehensive, and useful for everyone.
Have you designed a UI pattern that is being reused in multiple places but doesn't exist in the system? This is a great candidate for a new component.
Create a proposal ticket (e.g., in Jira or GitHub). Include screenshots of where the pattern is used, why it's needed, and any initial design thoughts.
Design the component in its various states (default, hover, active, disabled, error, etc.). Get feedback from the design system team and other designers.
Once the design is approved, a developer builds the component. The designer is responsible for writing clear documentation on how and when to use it.
The new component is added to the design system library and announced to the wider team (e.g., in a Slack channel or newsletter).