Skip to content

Relative .md links between user docs pages resolve to 404 paths #35

Description

@cewert

What happens

Pages in jellyrock/jellyrock docs/user/ link to each other GitHub-style, e.g. [Manage Subtitles](manage-subtitles.md). fetch-docs.mjs copies the markdown unchanged, so the built HTML keeps href="manage-subtitles.md".

Starlight serves each page at a directory URL (/manage-subtitles/). From /jellyfin-server-plugins/, that href resolves to /jellyfin-server-plugins/manage-subtitles.md.

Verified

A local build served with a plain static server (python3 -m http.server on user-docs/dist):

URL Status
/jellyfin-server-plugins/ 200
/jellyfin-server-plugins/manage-subtitles.md (what the link points to) 404
/manage-subtitles/ (the real page) 200

Not verified on the live server: no page currently deployed there contains a relative .md link, and the VPS web server config may rewrite URLs differently.

Affected pages

Existing: deep-linking.md (../dev/deep-linking.md), playback-troubleshooting.md (../dev/debug-flags.md). The server plugins doc rework on jellyrock branch feat/750-subtitle-download adds more links between user pages (manage-subtitles.md, media-segments.md, jellyfin-server-feature-matrix.md, app-settings.md#…).

Suggested fix

Rewrite relative .md links at build time so the source markdown stays correct on GitHub, e.g. in copyMarkdownWithFrontmatter or with a remark plugin: x.md → ../x/, keeping #anchors. Links into ../dev/ point at the dev docs site and need that site's URL rather than a relative path.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions