Backport: Sub-navigation
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 298
- Forks
- 83
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 1
Description
Many (most?) websites organize related groups of pages into connected sections, and provide a secondary navigation to move through pages within that section. We've implemented a subnav on some pages on mozilla.org but never backported that compontent to Protocol. We could start there, but could also take this opportunity to rethink it.
Example from https://www.mozilla.org/firefox/privacy/
We'll be redesigning the main navbar component in the near future and should make considerations for that as well.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the existing sub-navigation on mozilla.org and the related Protocol components. Consider how the component should fit with the planned main navbar redesign, then define and implement the backported or redesigned sub-navigation so related page sections can be navigated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scss
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100