Introduce secondary site nav, relocate nav items - #5187
Merged
Conversation
huntie
marked this pull request as ready for review
July 25, 2026 16:02
huntie
force-pushed
the
new-docs-secondary-nav
branch
from
July 25, 2026 16:07
f73539a to
3d833c7
Compare
Simek
reviewed
Jul 25, 2026
huntie
force-pushed
the
new-docs-secondary-nav
branch
from
July 25, 2026 17:51
3d833c7 to
91eb219
Compare
Collaborator
Simek
reviewed
Jul 26, 2026
Simek
reviewed
Jul 26, 2026
| justify-content: space-between; | ||
| gap: 1rem; | ||
| height: var(--rn-subnav-height); | ||
| padding: 0 1.5rem; |
Collaborator
Member
Author
There was a problem hiding this comment.
I reckon we'll use Flex and have the copy button drop away as the lowest priority item (especially for mobile).
Simek
reviewed
Jul 26, 2026
Member
Author
@Simek Intentional design choice to differentiate these. Versions dropdown also gets a unique colour state for "Next", and logically is a separate component. Understand the alternative take though! If we need let's launch with this then update later. |
huntie
force-pushed
the
new-docs-secondary-nav
branch
from
July 27, 2026 10:47
91eb219 to
9618491
Compare
Member
Author
|
@Simek Thanks, all changes addressed.
420px and under:
|
huntie
force-pushed
the
new-docs-secondary-nav
branch
from
July 27, 2026 11:09
9618491 to
e12eda0
Compare
huntie
force-pushed
the
new-docs-secondary-nav
branch
from
July 27, 2026 11:18
e12eda0 to
2987467
Compare
Simek
approved these changes
Jul 27, 2026
Simek
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for working on this feature, and all the follow up updates! 🚀
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.




Note
Stacked PR: Depends on #5186.
Summary
Introduces a secondary navbar above every docs-style section of the website, and renames the top-level "Development" menu item to "Docs".
Motivation
This, IMO, fixes a missing part of the site navigation story as reactnative.dev has evolved over time.
Principally, the navbar heading helps reinforce where you are on the site (motivated by the incoming new "Releases" section) — but also improves general context and navigation across the site.
(Home, Showcase, etc pages are unchanged.)
This also significantly improves navigation UX on mobile:
What moved where
Other changes
🚧 Open questions
Test Plan
Comparison tour — desktop
Screen.Recording.2026-07-25.at.16.59.32.mov