Contributing to Blueprint
While designing, you may come across a design token or component that hasn't been defined or built in Blueprint. Reach out to Design Systems or submit a contribution ticket.
Creating a ticket
Create a Feature Request ticket in JIRA. Design Systems will review each proposal and will reach out with next steps.
What to expect
Review: Design Systems will review your proposal and reach out with any questions.
Kick-off: For larger contributions, we'll schedule a kickoff meeting where we'll agree on scope, your team's involvement, and confirm any relevant timelines.
Build: While in design and development we'll collaborate with your team. If your team is leading the development, Design Systems will guide and advise.
Review: Final review with your team.
Publish: We'll update relevant documentation including Storybook, Doc sites, and Figma tools.
Proposal considerations
Below are a few guiding questions to help make the most of your contribution proposal and to ensure our system maintains its flexibility, scalability, and efficiency.
Is it new?
Explore our components and patterns. Does the new component solve a problem that can't be solved with anything already existing in Blueprint?
Is it scalable?
Every component needs to work at a system wide level. In order to maintain our system's efficiency your proposal should be a scalable solution that enhances more than one experience.
Does it solve a user problem?
Determine if the proposal solves a current user problem or simplifies their experience.
Is it accessible?
Has accessibility and usability been considered? Take advantage of our tools like design tokens to ensure a level of accessibility.
Guides and documentation
Technical guides and documentation to contribute to Blueprint
