Support versions inside menu items for tab navigation (Algolia-style dropdowns) #2168
swapnil-cometchat
started this conversation in
Bugs & Feedback
Replies: 1 comment 1 reply
-
|
@swapnil-cometchat are you looking for this? Coinbase is doing this with their docs on Mintlify so it should be possible with some custom code. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
-
We are using Mintlify’s tabs + menu navigation model and want to offer dropdowns similar to Algolia’s documentation—for example:
UI Kits → React → v6 / v5 → PagesAt the moment, menu items support only:
• item
• icon
• groups
• pages
…but they do not support versions, even though versions are supported at the top navigation level.
This makes it impossible to structure documentation for products that have multiple maintained versions (SDKs, UI Kits, APIs, etc.) while still using dropdowns inside tabs.
Here is the exact structure we want to use, which currently fails schema validation:
{ "tab": "UI Kits", "menu": [ { "item": "React", "icon": "/images/icons/react.svg", "versions": [ { "version": "v6", "groups": [ { "group": "Getting Started", "pages": [ "ui-kit/react/v6/overview", "ui-kit/react/v6/integration" ] } ] }, { "version": "v5", "groups": [ { "group": "Components", "pages": [ "ui-kit/react/v5/message-list", "ui-kit/react/v5/user-list" ] } ] } ] } ] }Why this feature matters
• Many developer platforms maintain multi-version SDKs and UI Kits.
• Without versioned menus, navigation becomes cluttered or inconsistent.
• It is not currently possible to offer the clear UX seen in major docs systems like Algolia, Stripe, or Supabase.
• Tabs + menus are powerful, but the lack of version support creates a major gap for real-world documentation structures.
Requested enhancement
Allow versions to be defined inside a menu item, with groups and pages nested under each version—identical to how top-level versioning works.
This would unlock clean, scalable navigation for multi-version product documentation without breaking existing configs.
Happy to provide more examples or help test this if needed.
Beta Was this translation helpful? Give feedback.
All reactions