chore: split v2 docs navigation into separate file#3762
Merged
Conversation
Use Mintlify's $ref feature to keep the v2 docs navigation in its own file, reducing docs.json by ~200 lines.
marvin-context-protocol
Bot
added
the
documentation
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
1 participant
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.
Mintlify now supports
$reffor splitting largedocs.jsonconfigs into smaller files. This moves the v2 navigation (~200 lines) intov2-navigation.jsonand references it fromdocs.json, keeping the main config focused on v3.The v2 docs are frozen and rarely touched, so having them in a separate file reduces noise when editing navigation. Mintlify resolves the
$refat build time — no behavioral change.