Settings: Design system review
The purpose of this issue is to plan the approach for a review of the settings experience in advance of the larger settings redesign effort groupfoundations is planning. Before beginning work on this project we need to identify the changes we want to make and then determine if these changes can be implemented within the current design system structure or if this needs to be expanded and improved.
Elements of the review:
- Environment setup: Define the procedures/conditions needed for us to collaborate on a consistent and comprehensive settings environment.
- Component audit: determining what is using Pajamas (and how correctly)
- Document inconsistent application of language, components and patterns across different options
- Assess settings placement and groupings according to existing settings management guidelines
- Identify areas where design system elements and guidelines need to be expanded or improved
Next steps
We still need to plan how to perform and document each of these elements. What is the scope of each individual effort? What are the specific deliverables and timelines? How can we setup each element so others can contribute?
Scope
Settings is a huge topic that include project, group, and admin settings, user preferences and profile. We will focus this review on project settings first, pausing after it's completed to decide how to proceed. We may decide to continue the review across more sections or turn to focus on design and implementation.
Output
The ultimate output of this review will be a set of issues and epics that Foundations can then prioritize and schedule. See how this fits into the overall settings redesign approach.
Related
- https://gitlab.com/gitlab-org/ux-research/-/issues/2388
- Foundations team goals for settings
- https://gitlab.com/gitlab-org/ux-research/-/issues/2596
Efforts by other designers
-
Settings inheritance exploration
@mnichols1
-
https://gitlab.com/gitlab-org/gitlab/-/issues/432827+
@mle
-
sheet
@katiemacoy
-
other sheet
@katiemacoy
-
Standardize settings inheritance (gitlab-org/gitlab-services/design.gitlab.com#1272)
@katiemacoy
-
https://gitlab.com/gitlab-org/gitlab/-/issues/413290+ (for stakeholders, as an illustration)
@katiemacoy
-
Look at package offering settings holistically (&7398) a different way to illustrate to stakeholders
@katiemacoy
-
https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/11+ overall thoughts on settings
@katiemacoy
-
rough concept (slack)
@katiemacoy @mle