You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Difficult to get to the library repo from the docs pages #1177
@tannerlinsley Source audit evidence: the repository URL already exists in useMenuConfig, but it is nested under the generic Menu group. The only direct repository link in the docs tab bar is the Built in public link, and that block renders only when isLandingPage is true. This matches the reported behavior: once someone opens a docs page, the repo is still available, but only after discovering and opening Menu.
Expected impact: a persistent repository affordance would remove a documented navigation dead end for people moving from docs to source or issues.
Proposed direction: reuse the existing repo value and show a clearly named GitHub link in the docs top bar on non-landing pages at desktop widths, while keeping the current menu item as the mobile and compact fallback. This is smaller than redesigning the full docs navigation and does not introduce a second source of repository metadata.
Alternatives: put the link in the right rail, which is not available at all viewport sizes, or rename/restructure the generic Menu, which changes a broader navigation contract.
Decision needed: should non-landing docs pages get the direct top-bar GitHub link, or should repository access remain inside a redesigned Menu surface?
Activity
tannerlinsley commentedon Aug 25, 2026
@tannerlinsley Source audit evidence: the repository URL already exists in
useMenuConfig, but it is nested under the genericMenugroup. The only direct repository link in the docs tab bar is theBuilt in publiclink, and that block renders only whenisLandingPageis true. This matches the reported behavior: once someone opens a docs page, the repo is still available, but only after discovering and openingMenu.Expected impact: a persistent repository affordance would remove a documented navigation dead end for people moving from docs to source or issues.
Proposed direction: reuse the existing
repovalue and show a clearly namedGitHublink in the docs top bar on non-landing pages at desktop widths, while keeping the current menu item as the mobile and compact fallback. This is smaller than redesigning the full docs navigation and does not introduce a second source of repository metadata.Alternatives: put the link in the right rail, which is not available at all viewport sizes, or rename/restructure the generic
Menu, which changes a broader navigation contract.Decision needed: should non-landing docs pages get the direct top-bar
GitHublink, or should repository access remain inside a redesignedMenusurface?