Repository navigation
Ensure links are correct after change to markdown format #2095
Description
When #2017 was merged, it unintentionally changed some links by blindling changing it from ({{ref "PAGE"}}) to /PAGE.
For example, the old link of [CHT Core Framework]({{< ref "core" >}} goes to Contributing CHT Core Code (/community/contributing/code/core/). Then this was converted to [CHT Core Framework](/core), which incorrectly goes to Concepts and paradigms of the CHT (/technical-overview/concepts/)
Hopefully there's not too many incidents of this, but we should double check to be sure starting with the one above which is on the Building page (see "using the CHT Core Framework").
Huge shout out to @cliftonmcintosh who found this while working on #2069
Metadata
Metadata
Assignees
Labels
No labels
Activity
gmarav05 commentedon Mar 23, 2026
Hello @andrablaj, I investigated this issue by searching the codebase for the broken link pattern described.
The specific broken link mentioned (
[CHT Core Framework](/core)) no longer exists in the codebase. I also searched for other short internal paths that might have been incorrectly converted, and all remaining internal links appear to be valid.The remaining
{{< relrefand{{< see-alsoshortcodes are valid Hugo shortcodes and are not affected by the original conversion.andrablaj commentedon Mar 23, 2026
cc @mrjones-plip - are you available to support with @gmarav05's findings? Thank you!
mrjones-plip commentedon Mar 24, 2026
Thanks @andrablaj ! And thanks for the effort to validate the links @gmarav05 - that's awesome!
However, I'm not sure if your checks are effective. Looking at the example link (
/core), it was valid before and valid now in that it has always returned a200:The reason it was broken (or "not correct") was that
/coreused to hold other content (see left side below from archive.org) but now it holds different content (see right side)This ticket is especially tricky in that searching for short internal paths programmatically and checking they return a
200doesn't verify they're contextually correct, just that they're not404.I suspect we shouldn't put a huge effort into this ticket , but instead maybe just spot check our top level pages by spending 10 or 15 min clicking around ensuring the link matches the destination?
fix(medic#2095): correct CHT Core Framework link on Building page
fix(medic#2095): correct CHT Watchdog card link on Architecture page
fix(medic#2095): move /core alias to cht-core.md and remove duplicates
gmarav05 commentedon Mar 25, 2026
@mrjones-plip Thanks for pointing it out i found two links and raised my PR fixing them. I followed your advice to find them. I was able to find them just by manually clicking few links. It took only 15 mins to find them out. thanks once again for the advice.
Building page -
[CHT Core Framework]was pointing to/building/local-setupinstead of/technical-overview/architecture/cht-core.Architecture page -
CHT Watchdogcard was pointing tocht-confinstead ofcht-watchdog./corealias - was duplicated across three files (architecture/_index.md,concepts/_index.md,technical-overview/_index.md) causing/coreto incorrectly resolve to "Concepts and paradigms of the CHT" instead of the CHT Core Framework page. Moved the alias exclusively tocht-core.md.fix(#2095): correct links broken by markdown conversion in #2017 (#2169)
mrjones-plip commentedon Mar 25, 2026
Perfect - thanks @gmarav05 - this worked a treat!