Skip to content

fix(docs): correct edit-link filenames + case-insensitive URLs#43

Merged
sandervanhooft merged 1 commit into
mainfrom
claude/fix-editlink-navcase
Jun 24, 2026
Merged

fix(docs): correct edit-link filenames + case-insensitive URLs#43
sandervanhooft merged 1 commit into
mainfrom
claude/fix-editlink-navcase

Conversation

@sandervanhooft

Copy link
Copy Markdown
Member

Two small site fixes.

  1. Edit-link filenames: useSourceRepo.ts mapped configuration -> 'Configuration.md' but the real source is docs/configuration.md (lowercase), so that edit link 404'd; it was also missing the comparison + migrating-to-vatly pages. Corrected the case and added the two entries.

  2. Case-insensitive URLs / nav highlight: content routes are all lowercase, but a mixed-case URL (typed/external) rendered via the github-pages SPA fallback with nothing highlighted (active-item match and queryCollection().path() are case-sensitive). Added a global lowercase-path middleware that redirects any uppercase path to its lowercase form (query/hash preserved) — page resolves and nav highlights.

Content unchanged, so lychee/markdownlint are unaffected.

The 'Edit this page' source-file map had 'configuration: Configuration.md' while
the real source is docs/configuration.md (lowercase), and it was missing the
comparison + migrating pages — so those edit links 404'd or fell back to the repo
root. Fix the map.

Add a global lowercase-path middleware. Every content route is lowercase, but a
mixed-case URL (hand-typed or external) rendered via the github-pages SPA
fallback with the wrong/empty page and nothing highlighted in the nav (the
active-state match and queryCollection().path() are case-sensitive). Redirect
such paths to their lowercase form so the page resolves and the nav highlights.
@sandervanhooft sandervanhooft merged commit 661693f into main Jun 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant