Skip to content

docs: clarify which version shapes support sdk - #7037

Open
brandonmcconnell wants to merge 1 commit into
brandon/eng-10850-allow-sdk-on-version-nodesfrom
brandon/eng-10850-version-sdk-shape-guidance
Open

docs: clarify which version shapes support sdk#7037
brandonmcconnell wants to merge 1 commit into
brandon/eng-10850-allow-sdk-on-version-nodesfrom
brandon/eng-10850-version-sdk-shape-guidance

Conversation

@brandonmcconnell

Copy link
Copy Markdown
Contributor

Summary

  • Documents that a version with sdk can only carry groups or pages, not tabs, languages, dropdowns, anchors, products, or an href
  • Adds a "Versions that use tabs" section showing the supported pattern: declare sdk on a tab inside the version, with a unique directory per version to avoid route collisions

Stacked on #7035. Matches the validation behavior in mintlify/mint#10298.

Test plan

  • Preview the page and confirm the new section renders correctly
  • Confirm the JSON example validates against the mint#10298 schema

Made with Cursor

@brandonmcconnell

Copy link
Copy Markdown
Contributor Author

FYI - this is pending some core product work that might not go in

A version with sdk only carries groups or pages. Versions that use tabs
declare sdk on a tab inside the version, with a unique directory per
version to avoid route collisions.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brandonmcconnell
brandonmcconnell force-pushed the brandon/eng-10850-version-sdk-shape-guidance branch from 638bdb2 to f5cbe43 Compare August 26, 2026 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants