[BUG] Broken links in sidebar: Redundant "/source/" segment in extension URLs

[ZehuiLin-Huawei]

On the Vulkan documentation site, clicking any extension name in the left-hand sidebar results in a 404 error page.

It looks like a pathing issue: the sidebar links point to an incorrect URL containing a redundant /source/ segment.

• Correct: .../source/VK_AMDX_dense_geometry_format.html
• Actual: .../source/source/VK_AMDX_dense_geometry_format.html

[gpx1000]

https://github.khronos.org/Vulkan-Site/spec/latest/index.html The main build seems to work. @oddhack https://github.com/KhronosGroup/Vulkan-Site/actions/runs/25560961026 if you can review the CI build, in the first link and are happy with it; then download the CI build from the second link and it should be good.

[SaschaWillems]

https://github.khronos.org/Vulkan-Site/spec/latest/index.html The main build seems to work.

That's broken too. Just check the link for e.g. Vulkan 1.2, which is 404.

[gpx1000]

Okay, looking into it now.

[oddhack]

The refpages/latest/_static_nav.js contains 'href="source/vkBlah.html"' and I'm unclear where the second 'source/' comes from - is the nav script trying to resolve relative links?

[SaschaWillems]

It looks like the JS appends a second "source" to the url once you visit it.

URL on first visit is e.g. https://docs.vulkan.org/refpages/latest/refpages/source/VK_VERSION_1_0.html

Once you're at that page, the link in the nav is changed to https://docs.vulkan.org/refpages/latest/refpages/source/source/VK_VERSION_1_0.html and is therefore broken

[oddhack]

This is clearly a good use case for a link checker - if any of the link checkers will run the nav script so they actually see these links, vs. just validating the static hrefs in the .html files.

[gpx1000]

Found the issue. Putting in an integration test to automatically ensure it is fixed will have a PR shortly.

[gpx1000]

The antora-static-nav extension extracts the navigation HTML from one sample page in each component@version group and reuses it across every page in the group. Antora renders nav href attributes as URLs relative to the rendering page, so the
cached nav only resolves correctly on pages at the same depth as the sample. When the sample was a root-level page (e.g. /spec/latest/index.html), its nav had hrefs like source/VK_AMDX_dense_geometry_format.html. Reused on a page at /spec/latest/source/X.html, the browser resolved that to
/spec/latest/source/source/VK_AMDX_dense_geometry_format.html

[gpx1000]

#206 should fix this problem. I'll work on another PR that can introduce a link checker of some kind and try to keep it optimized for the CI...

[oddhack]

@ZehuiLin-Huawei could you check and see if this is actually resolved for you? I pushed a site update using Steve's fix a short while ago. It took a while before the update showed up in my browser - Cloudflare caching maybe? - but it seems to be good now.