The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
|Content Last Reviewed
Thanks for visiting this direction page on the Navigation & Settings category at GitLab. This page belongs to the Foundations Group within the Manage Stage and is maintained by Jeff Tucker, but everyone can contribute. If you're a GitLab user and have direct feedback about your needs for Navigation, we'd especially love to hear from you.
~"Category:Navigation & Settings" label
#g_manage_foundations Slack channel.
This joint category is shared between the navigation elements of GitLab and the settings that make it configurable. These aspects serve as the framing for the product itself. Our goal is to make these areas of the product more useful, predictable, and convenient.
Navigation is the highway through which almost every feature is accessed or discovered, and it must be accessible for all types of people and abilities. For this reason, the navigation structure is one of the most important parts of any application’s user interface.
Settings provide administrators, owners, and users an opportunity to configure GitLab to their unique needs. We default to convention over configuration but also provide flexibility to customize settings if needed.
The complexity and breadth of GitLab weighs heavily on both the navigation and settings. In FY24 we invested in overhauling our core navigation, and now we are looking towards how the navigation must evolve to address existing pain points while also accommodating future changes to the product. With settings we must address the historical challenges: discoverability, consistency, access, and visibility.
The navigation experience must be described as intuitive. When navigation is effective, users trust that they can rely on it to help orient and empower themselves within the product. To aid in decision making we will continue to invest in these themes:
Executing this plan we will requires iterating in three ways:
In addition, the Foundations Group owns the navigation structures of GitLab and is responsible for reviewing and approving any proposed changes. Given the effort required by these requests we dedicate time each milestone to support teams with this process.
Over years of product development, the Gitlab settings have evolved into a catchall space lacking a cohesive structure. As a result, it's evident there is difficulty in discovering, finding, and configuring settings within GitLab. Our goals to address this include:
Our starting point is to perform an assessment of the current experience. This includes blending our findings with the extensive collection of epics based on historical requests and user research. There are likely straightforward opportunities that require minimal validation. We will prioritize these earlier in our backlog while delving deeper into other areas.
Unifying feature development and the design system
The Foundations Group is also responsible for the Design system category. Previously treated as a separate focus area, our strategy now is to bundle product improvements to the Gitlab product and design system into a cohesive package of work. We aim to deliver iterative improvements to the design system that will streamline our work to improve the settings experience.
As this is not a marketing category, we don't have a specific measure of maturity.
All roles & personas interact with this category in some capacity.