feat: dropdown: section flavor for navigation_preview.yml top nav - #3873
Open
theletterf wants to merge 10 commits into
Open
feat: dropdown: section flavor for navigation_preview.yml top nav#3873theletterf wants to merge 10 commits into
theletterf wants to merge 10 commits into
Conversation
Extends the section: entry shape in navigation_preview.yml with a dropdown:
key that renders a panel of links instead of navigating to a tree section.
Config layer:
- Add SiteDropdownLinkRef record (title + url)
- Extend SiteSectionRef with DropdownLinks property and IsDropdown flag
- Parse dropdown: sequences in SiteTableOfContentsCollectionYamlConverter;
each item is a {title, url} mapping
Builder (SectionTopNavBuilder):
- When IsDropdown, prepend the site prefix to each link URL and emit
a TopNavDropdownItem with a single flat TopNavGroup (null label)
Template (_SecondaryNav.cshtml) and JS (secondary-nav.ts) required no
changes — TopNavDropdownItem rendering and close-on-click behaviour were
already implemented.
navigation_preview.yml: add Products dropdown with four solution links
as a concrete example between the APIs external tab and Reference.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The navigation model may intentionally preserve identical sidebar trees across htmx navigations, so the synthetic should assert the visible target group and only require a fresh DOM node when the tree id changes. Co-Authored-By: GPT-5.5 <noreply@openai.com>
reakaleek
reviewed
Aug 18, 2026
reakaleek
left a comment
reakaleek
left a comment
Member
There was a problem hiding this comment.
We need mobile view handling.
Member
Author
|
@reakaleek Also for the menu itself, right? Let me develop that in a separate PR and stack this one on top. |
…o work/nav-dropdown-mobile
Top-nav dropdown sections need a mobile presentation inside the compact top-nav menu introduced by the base branch, so grouped links remain reachable on narrow screens. Co-Authored-By: GPT-5.5 <noreply@openai.com>
Co-Authored-By: GPT-5.5 <noreply@openai.com>
Member
Author
|
@reakaleek Added a mobile mechanism. WDYT? |
…o work/nav-dropdown-mobile
Keep dropdown top-nav groups inside the mobile pages drawer after stacking on the updated base branch. Co-Authored-By: GPT-5.5 <noreply@openai.com>
Restore the mobile TOC trigger alignment now that version controls live inside the drawer. Co-Authored-By: GPT-5.5 <noreply@openai.com>
Render the mobile-only pages drawer trigger on the docs landing page so section and version controls remain reachable there. Co-Authored-By: GPT-5.5 <noreply@openai.com>
Member
I think it looks good. But I was thinking of something less invasive. Like keeping the buttons as is but grouping the last 3 into a dropdown with the label (3 more) or something like that |
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
2 participants
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.
Summary
dropdown:key to thesection:entry shape innavigation_preview.yml_SecondaryNav.cshtml) and JS (secondary-nav.ts) required no changes —TopNavDropdownItemwas already wired upDemo: https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3873
What changed
Config layer (
SiteNavigationFile.cs):SiteDropdownLinkRef(Title, Url)recordSiteSectionRefgainsDropdownLinksandIsDropdownSiteTableOfContentsCollectionYamlConverterparsesdropdown:sequences as{title, url}itemsBuilder (
SectionTopNavBuilder.cs):IsDropdownsections →TopNavDropdownItemwith a single flat group; each URL gets the site prefix prependednavigation_preview.yml: adds aProductsdropdown between APIs and Reference, with four solution links as a concrete exampleTest:
SectionTopNavBuilder_BuildsDropdownTab_WhenDropdownLinksPresentverifies the new path end-to-endTest plan
dotnet test tests/Navigation.Tests/— 225 passed, 0 faileddotnet build— clean for bothElastic.Documentation.ConfigurationandElastic.Documentation.NavigationNAVIGATION_PREVIEW=trueto confirm the Products dropdown renders in the top nav🤖 Generated with Claude Code