Repository navigation
feat(nav): name the navigation's groups - #394
Merged
Merged
Conversation
The nav rail's 18 items sit in four groups, each named above its first item: what people use every day, Explore (Entities, Topics, Graph, Podcasts, Reports), Automate (Pipelines, Routines, Extensions, Sensors or Sources) and Manage (Costs, Analytics, Settings, Admin). Costs moves from the first group to Manage. Collapsed to icons, the names are lines. Items are 32px rather than 34px, so the names add about 20px to the rail. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012QHdEu9xFwnsCUnJn4yB3v
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012QHdEu9xFwnsCUnJn4yB3v
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: the navigation rail listed 18 items in one column, split only by unnamed lines, with Costs among the everyday pages.
After: the items sit in four groups, each named above its first item: what people use every day (Home, Library, Import, Chat and the rest), Explore (Entities, Topics, Graph, Podcasts, Reports), Automate (Pipelines, Routines, Extensions, Sensors or Sources) and Manage (Costs, Analytics, Settings, Admin). Costs moves to Manage. Collapsed to icons, the names become lines. Items are 32px tall rather than 34px, so the names add about 20px to the rail; at 1366x768 every item and Collapse still fit, and the phone drawer fits through Admin.
How: each item in
nav-config.tscarries agroupinstead of adividerflag, andnav.tsxdraws a group's name where it starts.Motivation and Context
Adeel asked to simplify the interface and settings; this is the third step after #390 (settings groups and Find) and #392 (folds).
Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.## UnreleasedinCHANGELOG.md. (n/a)Done questions (AGENTS.md)
navigation.test.ts,nav-groups.test.tsx; docs/frontend.md "Navigation").🤖 Generated with Claude Code
https://claude.ai/code/session_012QHdEu9xFwnsCUnJn4yB3v
Generated by Claude Code