The Card-ification of GitLab
Our current UI does not always do a good job of being extendible while keeping content either grouped or visually separated.
This is due to our listed and
hr'd design. This makes it so that all items make up a long list with little visual hierarchy.
Improve visual hierarchy and separation of content by introducing card-ification of our UI.
- Better separation and isolation of information
- More flexibility of extending UI elements
- Bonus: Modernisation of UI
(When do you use this pattern? And how?)
Dos and dont's
(Use this table to add images and text describing what’s ok and not ok.)
- Issue board cards
Links / references
Make sure these are completed before closing the issue, with a link to the relevant commit, if applicable.
- Ensure that you have broken things down into atoms, molecules, and organisms.
- Check that you have not created a duplicate of an existing pattern.
- Ensure that you have used the proper method for creating the pattern depending on the complexity. Atoms and molecules are symbols, organisms are groups.
- Make sure that text is created using text styles. When applicable used shared styles for colors.
- QA check by another UX'r (create and reference a file in this issue which includes the changes as you would like to add them to the gitlab-elements file)
- Added to gitlab-elements.sketch
- Add to the UX Guide and/or add to the GitLab Design Library
- Add an agenda item to the next UX weekly call to inform everyone (if new pattern, not yet used in the application)