Stepper component
Component description
A stepper conveys progress through numbered steps that allow users to input information in a prescribed order. They may also display feedback after a step is saved or completed.
Why is this component needed?
There are a number of examples where we use a pattern like this across GitLab, but they are not consistent. We should create a universal component to use for these cases.
Full audit
Use case | Example | In the product? |
---|---|---|
Setting up an integration | Yes | |
Installing a GitLab instance | No | |
Kubernetes agent setup | ||
SAST configuration | No | |
Purchasing a GitLab subscription | Yes | |
Create a runner | No | |
Switchboard onboarding flow - using the path component as of right now | No |
Usage guidelines
Click to expand
### ChecklistMake sure the following are completed before closing the issue:
-
Assign the correct component label to this issue. -
Create an MR with the additions or updates needed. -
When applicable, create an issue using the Figma update
issue template to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling. -
When applicable, create an MR in GitLab UI to update the component. If you do not have capacity or are unable to update the component directly, create a GitLab UI issue using the Component
issue template. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -
When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting. -
🎉 Congrats, you made it! You can now close this issue.
Edited by Gina Doyle