Improve communication of feature versions (Experiment and Beta)
Description
With Introduces an experimental category, and makes ... (gitlab-org/gitlab!116840 - merged), Alpha
feature versions was replaced by Experiment
. This issue is to use this as an opportunity to improve how we communicate feature versions like Experiment and Beta — current Pajamas documentation
Some ideas:
- Add more help content to the popover?
- Design small variants when space is tight? Is an icon valuable? And an icon-only variant?
- Is it overwhelming if multiple info badges appear in the same context (e.g. setting to enable/disable experiment/beta features?) In these cases, is it worth using a neutral variant instead?
- How do we position the badge?
- Is the badge shown before or after the user interacts with the feature?
See recent examples: suggested reviewers or AI-based feature)
Checklist
Make 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 theFigma 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 theComponent
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 Pedro Moreira da Silva