Below is an overview of the contribution path in the Atlas Design System. While it's been created primarily with Atlas designers & engineers in mind, everyone is welcome to contribute to the Atlas Design System by submitting their proposal via a GitHub issue.
As contribution ideas can come in different shapes and sizes, star icons are used to determine the contribution path for each size. Steps marked with one star icon apply to all contribution sizes.
| Stars | Contribution size | Examples |
|---|---|---|
| ⭐️ | Small | Making a minor change in a component, creating a new icon, etc. |
| ⭐️⭐️ | Medium | Adding a new variant of a component, a missing piece of documentation, etc. |
| ⭐️⭐️⭐️ | Large | Creating a new component from scratch, making a change in design tokens, etc. |
A proposal is sent via GitHub issue by the proposal author.
By default, all incoming proposals land in the proposals inbox on GitHub, awaiting a backlog grooming. During backlog grooming, occurring (most likely) every two weeks, proposals are assigned with priorities and sizes, determining the order in which they're tackled.
A meeting between the proposal author and a designated member of the Design System team to discuss details about the proposal and gather all requirements.
A designated Design System team member designs the solution based on the previously gathered requirements.
A meeting between the proposal author and a designated member of the Design System team to present the solution and gather feedback.
A meeting between designated members of the Tech and Design System teams to discuss technical aspects of the solution and whether it can be implemented in the proposed shape and form.