[META] UX Big Plan
Let’s focus on the Big picture for GitLab’s UX. It is important that we keep our day to day work focused on contributing to larger goals. It is easy to get so heads down in work that we lose sight of bigger things we are trying to accomplish as a team and company.
The intention of this issue is to set UX goals that will continue to establish and evolve GitLab’s UX. We already have OKRs for this quarter and those will need to be considered in determining which issues to take up and move forward on. However, I think there is plenty of room for us to focus on UX centric goals. Specifically, cleaning up and establishing GitLab's unique personality and voice.
The basic ground rules are:
- Each team member should think about an area they you would want to focus on and contribute to
- We must be sure to fully support our OKRs
- We should write blog post (or series of) stating our plan - declare our intentions to the community and company
- All issues we take on and create should support our plan
- We should establish a GitLab Pages for UX (design.gitlab.com) - Be visibly committed
The end goal is to have an established UX Foundation Guide.
Phase 1 - GitLab UX Foundation
- GitLab Color Pattern/System(WIP)
- Iconography(WIP)
- Typography
- Vertical Rhythm(WIP)
- Writing Style
- Illustration Style(WIP)
- Accessibility
Phase 2 - GitLab UI Components
- Avatars
- Labels
- Banners
- Breadcrumbs
- Buttons
Phase 3 - GitLab UI Patterns
- Comments
- Forms
- Alerts
- Empty States
- Pattern Library in Brand AI
Designs
Relates to
- gitlab-foss #24310
- gitlab-foss #28614
- gitlab-foss #3289410.0
- gitlab-foss #30495
- gitlab-foss #30506
- gitlab-foss #34244
- gitlab-foss #34138
- #39
- gitlab-foss #31351
- gitlab #6951
- gitlab #847110.2
- gitlab #9430
- gitlab #10621Backlog
Activity
https://medium.com/eightshapes-llc/adopting-design-systems-71e599ff660a
Might be a good fit for our next UX functional group update.. plus for ourselves.. to see how far along we are in getting to a full gitlab specific design system and getting it implemented (with phases so to say)
This way we can clearly communicate and track our progress as a team in our efforts of getting a gitlab design system foundation implemented.
especially the following images resonate here:
-
Of course we should not redesign for the sake of redesigning.. we should be clear into communicating this as is the gitlab way. Reasons/Goals to give are:
We’re enabling a cohesiveness across products that is a competitive advantage. We are an integrated product, our UI should thus reflect this.
Iteration is key:
Bit by bit, part by part, the system weaves in alongside features work.
Also a nice one :) when a design system is done right.. things fall in place ;)
They’ll also achieve benefits that they can’t do themselves or refuse to prioritize, like accessibility.
mentioned in issue gitlab-com/marketing#1290
marked this issue as related to #26 (closed)
marked this issue as related to #39
added process label
mentioned in issue #44
mentioned in issue #43
marked the checklist item Pattern Library in Craft(WIP) as completed