Summary
Fixes #2
The "The Capabilities" page at mdxg.org/readme/the-capabilities contains a broken link to SPEC.md. The relative link resolves to /readme/SPEC.md which does not exist, resulting in a 404.
Root Cause
README.md line 39: The link [SPEC.md](SPEC.md) is a relative file reference that works correctly on GitHub but breaks on mdxg.org. On the web app, the page is rendered at /readme/the-capabilities, so the relative SPEC.md resolves to /readme/SPEC.md — a route that does not exist in the content routing table (only /readme and /spec are registered).
Fix
Changed the link from [SPEC.md](SPEC.md) to [SPEC.md](https://mdxg.org/spec), using the full URL to the spec page. This works correctly on both GitHub and mdxg.org.
Changes
README.md: 1 line changed (+1 -1)
Testing
- mdxg.org/readme/the-capabilities: SPEC.md link now navigates to the spec page (
/spec) ✅ - GitHub README view: Link still works (goes to mdxg.org/spec) ✅
- Other relative links in README (CONTRIBUTING.md, package links): unaffected ✅
Activity
3This fix will make the link on GitHub incorrect.
I think the correct link on GitHub is below. https://github.com/vercel-labs/mdxg/blob/main/SPEC.md
Instead of modifying README.md, you need to modify the sample implementation of the Viewer. https://github.com/vercel-labs/mdxg/blob/main/apps/web/src/lib/content.ts
Refs: https://github.com/vercel-labs/mdxg/issues/2#issuecomment-4447440310
@algojogacor is attempting to deploy a commit to the Vercel Labs Team on Vercel.
A member of the Team first needs to authorize it.