Chrome Redesign: Breadcrumb Tasks + Navigation Improvements
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Vision
The overall vision is that the user consistently finds the breadcrumb bar in the same place helping him orient himself in the product and also helping him navigate back to previous pages using the breadcrumb. Also, to have a main navigation that is useful and scales well.
Problem or opportunity
The current breacrumb bar doesn't always display the right breadcrumbs/location, doesn't have the proper visual hierarchy to help users determine their location and doesn't always work as expected. Our main navigation isn't optimized for usability and context.
Solution
Provide a consistent breadcrumb bar across the different pages in the product that is visually easy to parse, whose title takes advantage of the visual hierarchy to help the user clearly identify their location and to have fully functional breadcrups to help the user navigate back. Implement some usability imporvements to the main navigation.
Out-of-Scope
We are not touching any of the other items found in the breacrumb bar like the site picker, or the avatar.
Market Validation & Competitive Positioning
Better visual hierarchy to help the user identify their location within the porduct.
Easier way to navigate among pages.
Personas
- Developer teams
- Content teams
- DevOps teams
- Sys Admin
Links As Appropriate
See parent pillar for links.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by locating the breadcrumb and main-navigation implementations across the product, then review the parent pillar referenced under Links As Appropriate. Done should be defined as consistent breadcrumb placement, hierarchy, back-navigation behavior, and the stated navigation usability improvements.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100