docs(guides): redirect Send-to imports to the Send-to guide#2619
Conversation
Claude Design's only doc-discovery tool is web search, which ranks this Template-First (Download-ZIP) guide first; the Send-to guide is not indexed, so Send-to imports get authored against the wrong flow. A body link here lets CD's fetch of this page unlock a fetch of the correct guide (its URL now appears in a prior fetch result).
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…page The /guides/claude-design landing page (claude-design.mdx) is the indexed nav page and points only at the Download-ZIP instruction file; a Send-to author landing here got no pointer to the Send-to guide. Mirror the redirect from claude-design-hyperframes.md.
miga-heygen
left a comment
miga-heygen
left a comment
There was a problem hiding this comment.
SSOT Review: docs(guides): redirect Send-to imports to the Send-to guide
PR #2619 | 2 files | +9/-0
Docs-only — two redirect notes added at the top of existing Claude Design guides:
-
claude-design-hyperframes.md(the raw-fetchable guide CD actually finds via web search): blockquote callout with the raw GitHub URL toclaude-design-send-to-hyperframes.md. Using the raw URL is deliberate — CD can only web-fetch URLs that appeared in prior search/fetch results, and this bootstraps discovery from the ranked guide to the correct one. -
claude-design.mdx(the Mintlify rendered page):<Note>block with the same link, for human readers browsing the docs site.
Both correctly placed before any content, clearly labeling this as the Download-ZIP flow and directing Send-to users elsewhere. The PR body explains the web-search ranking issue that makes this necessary and notes a follow-up to add the Send-to guide to the Mintlify nav.
No code changes, no SSOT concerns.
Approve.
--- Miga
miguel-heygen
left a comment
miguel-heygen
left a comment
There was a problem hiding this comment.
Reviewed exact head 0114a2a.
The redirect is placed at the entry point Claude Design actually discovers, the raw target exists on main, and the rendered MDX surface carries the same flow distinction for human readers. I read the complete two-file diff, found no unresolved review threads, and verified docs validation, Mintlify deployment, security analysis, and all applicable required checks are green.
Verdict: APPROVE
Reasoning: The current head cleanly separates Send-to from Download-ZIP authoring without changing runtime behavior, and the linked source plus required CI are valid.
— Magi
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
3 participants
Summary
Redirect Claude Design Send to HyperFrames authors from this Template-First (Download-ZIP) guide to the dedicated Send-to guide.
Why
Claude Design's only doc-discovery tool is web search. It reliably ranks this guide (
claude-design-hyperframes.md) first, while the Send-to guide (claude-design-send-to-hyperframes.md, added in #2131) is not in the Mintlify nav and isn't indexed. So Send-to imports get authored against the Download-ZIP flow, whose rules differ (e.g. Google Fonts<link>vs inlined base64@font-face), yielding low-fidelity imports. Confirmed on a live import.How this fixes it
Claude Design's web-fetch only allows URLs that appeared in a user message or a prior search/fetch result. Naming the guide in a tool description doesn't unlock it, and the Send-to guide doesn't rank. But this guide does rank #1, so CD fetches it reliably; once the Send-to URL appears in this page's body (a prior fetch result), CD can fetch the correct guide. It bootstraps from the findable guide to the right one, no reindex needed.
Follow-up (separate, optional)
Also adding
guides/claude-design-send-to-hyperframesto the Mintlify nav indocs/docs.jsonwould let web search surface it directly and let humans browse to it.