docs: unlist the Send-to guide from the docs nav (tool-served, not web-searched) - #2918
Merged
Merged
Conversation
…b-searched) The "Send to HyperFrames" authoring guide is an internal contract for the Claude Design import flow, delivered exclusively by the get-send-to-hyperframes-guide MCP tool (raw server-side fetch of the .md, returned as tool-result data). The llms.txt / web_search discovery path it was published for is no longer used. Drop it from docs.json so it stops appearing in the public product docs nav + llms.txt; keep the .md file at its path (the tool's raw fetch URL depends on it) and the redirect note in claude-design-hyperframes.md (points at the raw URL, not the docs page). Orphan guide files build cleanly here (claude-design-hyperframes.md already is one). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
miguel-heygen
approved these changes
Jul 31, 2026
miguel-heygen
left a comment
Collaborator
There was a problem hiding this comment.
Approved exact head 24bc93df12f78db5600b411991d489afb9fe68e9. This is the correct minimal separation: removing only the docs-nav entry unlists the internal Send-to contract (and its generated discovery surface) while preserving the raw GitHub file path consumed by the MCP tool. Both raw-link redirects remain valid, the existing semantic contract test still reads the unchanged file, and the sibling orphan guide establishes that unlisted files are supported. Exact-head docs validation/CodeQL/checks are terminal green; no unresolved review threads.
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
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.
What
Unlist the "Send to HyperFrames" authoring guide (
guides/claude-design-send-to-hyperframes) from the docs navigation indocs.json, making it an unlisted orphan file (like the siblingclaude-design-hyperframes.mdalready is). The guide file itself is unchanged.Why
That guide is an internal authoring contract for the Claude Design "Send to HyperFrames" import flow, not general HyperFrames product docs. It's now delivered exclusively by the
get-send-to-hyperframes-guideMCP tool, which fetches the raw file server-side (raw.githubusercontent.com/heygen-com/hyperframes/main/docs/guides/claude-design-send-to-hyperframes.md) and returns it as tool-result data — independent of the docs site. Thellms.txt/web_searchdiscovery path it was published for is no longer used (the import tool tells the agent the guide comes from the tool, "no fetch/search needed"). So the nav entry only surfaces implementation detail in the public product docs without serving the flow.How
Remove the one
"guides/claude-design-send-to-hyperframes"line fromdocs/docs.json. This drops it from the sidebar and the auto-generatedllms.txt, while:.mdfile at its path — the MCP tool's raw fetch URL depends on it and is unchanged, so nothing in the live flow moves;claude-design-hyperframes.md(it points at the raw GitHub URL, not the docs page, so it still resolves).Orphan guide files build cleanly in this repo —
claude-design-hyperframes.mdis already an orphan (present but absent fromdocs.json), and no internal doc links reference the page.Test plan
docs.jsonvalidated as well-formed JSON; guide.mdconfirmed still present; grep confirms no internal doc links to the page.