gitlab-ui (CSS and Reusable Components)

Attributes

Business Goal

Drive forward the gitlab-ui roadmap of our CSS Cleanup/Restructuring and the implementation of Reusable Components based on our design system. gitlab-ui will from now on have our base CSS implementation and all reusable components in one package to group all efforts of generic styling in one UI project. This will improve engineering productivity and consistency throughout the product. The main target of the working group is not to implement everything themselves but rather keep the effort moving across the whole frontend engineering group in a constant pace and pick up key tasks.

Exit Criteria

All to-do list items in the main Epic

Especially the following items:

• Shepherd restructuring for splitting generic CSS in GitLab UI and page specific in CE/EE by creating a utility-class library based on the design system
• Ensure utility-class library is available and usable within GitLab, ensuring the entire set of classes can be imported into GitLab without clashes and there is documentation to guide consumers on how to use them
• Establish working group FE members as GitLab UI maintainers
• Ensure there is clear documentation written for when and how new components should be introduced into the design system and the product, including responsible counterparts
• Ensure there is clear documentation of how to implement GitLab UI components and utility classes

Roles and Responsibilities

View page source - Edit this page - please contribute.