Skip to content

Navigation change proposal: Sidebar navigation link for Virtual registries

Summary

We want to add a new navigation link Virtual registries for root groups under the Deploy sub-menu.

Background

Link to epic / issue with overall feature proposal:

The Deploy sub-menu already contains navigation links to Package registry, Container registry, & Dependency Proxy. Since the feature is close to the dependency proxy & the package registry, we want to add the link under the same sub-menu.

Does this navigation proposal facilitate one of our primary JTBDs? Which job?

How does this change improve the workflow for users attempting to complete that job?

How many users will be impacted by this proposed change?

  • Limited
  • Moderate
  • All users

What is the product maturity stage of the associated feature?

  • Experimental
  • Beta
  • General availability

How often do you expect an average GitLab user (not just your target persona) to reach for this functionality?

  • Several times a day
  • Once a day
  • A few times a week
  • Once a week
  • Less than once a week

Approaches Considered

  1. Group Settings Placement: The team considered placing the configuration for virtual registries within the group settings section.
  2. Build
    1. Splitting between Deploy and Build --> https://gitlab.com/gitlab-org/gitlab/-/issues/545985+

Justification for the Chosen Approach (Deploy Sub-menu)

The justification for placing "Virtual registries" under the "Deploy" sub-menu instead of group settings includes:

1. User Workflow Alignment

Developers typically visit the Package UI to verify they're using the correct artifact or to troubleshoot issues. Placing the configuration in settings would create a barrier for developers trying to understand artifact resolution from upstream sources.

2. Research-Backed User Expectations (see https://gitlab.com/gitlab-org/ux-research/-/issues/3444)

  • Quantitative study: While Build (35%) scored highest initially, users lacked understanding of what's currently under Build
  • Qualitative interviews: 6 out of 7 users expected Virtual Registries under Deploy based on existing patterns
  • User reasoning: "Container registries and package management are closely tied to the deployment process"

3. Feature Prominence

Given the importance of this feature, the team wanted to give it more visibility rather than hiding it in settings.

4. Future Functionality

There are plans to add more capabilities to the page, including:

  • Browsing cached artifacts
  • Deleting artifacts
  • Viewing usage statistics

5. Categorical Alignment

The "Deploy" sub-menu already contains related functionality (Package registry, Container registry, & Dependency Proxy), making it a logical placement since virtual registries are closely related to dependency proxy and package registry features.

6. User Impact

This change will affect all users, making proper placement important for discoverability based on established mental models.

Review checklist

Requester

  • Review the handbook page for navigation.
  • Add relevant information to the issue description detailing your proposal, including usage and business drivers.
  • List at least two other places you considered to introduce your feature.
  • Add relevant designs to the Design Management area of the issue.
  • Ensure your UI suggestion align with the Documentation Style Guide.
  • Engage Technical Writing. They can help craft a term that best describes the feature(s) you’re proposing.
  • Follow the product development workflow validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is mandatory for additions or when restructuring.
  • Engage the Foundations Product Manager for approval. The Foundations DRI (@jtucker_gl) will work with UX partners in product design, research, and technical writing, as applicable.
  • Consider whether you need to communicate the change somehow, or if you will have an interim period in the UI where your item will live in more than one place.
  • Ensure engineers are familiar with the implementation steps for navigation.

Foundations Product Manager

  • Confirm proposal has necessary information
  • Schedule design review for next milestone

Foundations Product Designer

  • Confirm Pajamas guidelines are followed
  • Confirm a11y needs are addressed
  • Confirm burden of proof supplied for stated scope of access
Edited by Annabel Dunstone Gray