Draft: Build a stable navigation [POC] 👨🏻💻
Turn on feature flag
stable_dock
Design brief
The Problem
GitLab's navigation forces a destination-first model: pick a place, then hunt for features. This creates friction at scale. Returning users re-learn navigation constantly. New users get paralyzed by scatter. Every new feature requires a navigation decision. Settings live in different places.
The Solution
Invert the model. Features and settings are always accessible from where users are. One persistent navigation shelf. One settings interaction. One feature catalog.
Stable Navigation UI
A persistent dock, configurable shelf of features that follows users across the product.
How it works:
- Users get a sensible default and can tailor further to suit their needs.
- When accessing a feature from the wrong scope (e.g., Epic Boards from a Project), they pick the correct scope first: "View Epics from: Group"
Why this works:
Returning users perceive continuity. New users see clear entry points. Everyone stops hunting.
Unified Settings Pane
Settings access is consistent everywhere, regardless of scope.
How it works:
- Modal surfaces the relevant scope hierarchy from current context
- Pick a scope, see all settings for that level
- One interaction pattern across the entire product
Why this works:
Settings fragmentation friction is minimal. Users never leave their working context.
Feature Library
A discoverable catalog of all features and their functional scopes.
How it works:
- Every feature declares which scopes it lives at (Project, Group, Instance, etc.)
- Source of truth for what can appear in stable nav
- Teams publish with lightweight gates: custom icon + tech writing name approval
Why this works:
Teams get visibility. Duplication becomes obvious. Features are discoverable.
How They Work Together
The Feature Library declares what exists and where. The Unified Settings Modal creates consistent configuration everywhere. The Stable Navigation UI uses both to give users one mental model: access what you need from where you are. Pick the right scope if needed.
Expected Outcomes
For users: Faster discovery with more intuitive navigation.
For product velocity: Navigation scales without cognitive load.