Optimize UX workflow on how labels are used for planning, discovery, delivery within the design system
Currently, the UX workflow is missing a concrete description of how we use labels as far as the design system is concerned. The only reference to labels, when is comes to Pajamas, is during component implementation which only implies adding stage group labels.
After the creation of gitlab-org&973, we've added labels for the component lifecycle stages like pajamas::create, pajamas::build, pajamas::style, and pajamas::implement as well as labels for each individual component like component::alerts, component::avatars, and more.
In addition, we've extended labels beyond components to include other sections of the design system like foundation::animation. See proposal in https://gitlab.com/gitlab-org/design.gitlab.com/issues/314#note_178154470.
Repeating here some questions from the relevant slack discussion (internal):
- Do you think
component::xyzscoped labels could or should span across other repositories like
gitlab-ee. For example, see https://gitlab.com/gitlab-org/gitlab-ee/issues/11307, https://gitlab.com/gitlab-org/gitlab-ee/issues/11306, https://gitlab.com/gitlab-org/gitlab-ee/issues/9231, and https://gitlab.com/gitlab-org/gitlab-ce/issues/54605.
- Does it make sense to have the
design.gitlab.comlabel attached to all these issues? Looks redundant, right? See https://gitlab.com/gitlab-org/design.gitlab.com/issues?label_name%5B%5D=design.gitlab.com.
- Pajamas label in most of these issues also looks redundant now that
pajamas::xyzlabels are in place, right? See https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name=Pajamas.
- Some of the issues in  could be have a new
The Pajamas label is needed in order to scope the relevant issue board, see Pajamas board, which is already missing 10 issues because of the missing Pajamas label. This board can be easily recreated using the
pajamas::* label for each of the four distinct stages of a component lifecycle including all related issues, see for example the Pajamas Test Board.
foundation::*, etc. labels to issues and merge request across other repositories like
- Remove the design.gitlab.com label from all issues in the
gitlab-orggroup. 99% of these issues are directly within the
design.gitlab.comrepository which should suffice.
- Remove the Pajamas label from all issues in the
gitlab-orggroup, especially from the repositories that are closely related to the design system like
gitlab-svgs, but allow usage if needed to raise awareness and enable discoverability on issues like https://gitlab.com/gitlab-org/gitlab-ce/issues/61987 or epics like gitlab-org&973.
- Replace the Design documentation with a new ~"pajamas::documentation" label. Alternatively, use pajamas::create.
Create: A need for a component is identified. Documentation is written regarding its usage and the component is created and added to the Pattern Library.