docs: fix broken RTVI link in System Frames reference#932
Merged
markbackman merged 1 commit intoJun 23, 2026
Conversation
The link pointed to /api-reference/server/rtvi, which has no page or redirect; the section index lives at /api-reference/server/rtvi/introduction.
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
2 participants
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.
Problem
In
api-reference/server/frames/system-frames.mdx, the RTVI link points to:That path has no page and no redirect — there's no
rtvi/index.mdx, anddocs.jsonhas no redirect entry for it (unlike the other legacy/server/...paths, which do). So the link 404s. The actual section index lives at/api-reference/server/rtvi/introduction.Fix
Point the link at the real page:
How I found it
Scanned all
.mdxinternal links against existing pages and the 437redirectsindocs.json. This was the only internal link with neither a target page nor a redirect — the other near-misses (/server/events/service-events,/guides/fundamentals/service-settings, etc.) are all covered by existing redirects, so they're left untouched.Single-line change, no content/behavior impact.