Fix article title links producing relative URLs (404 on nested paths)

[Copilot]

Article hrefs like mesa/opengl-framebuffer resolve relative to the current path, so navigating the title link at /mesa/opengl-framebuffer targets /mesa/mesa/opengl-framebuffer.

Prepend / to destUrlPath at construction so all downstream href interpolations produce absolute URLs:

-var destUrlPath = Path.ChangeExtension(relativePath, null)...
+var destUrlPath = "/" + Path.ChangeExtension(relativePath, null)...

This fixes the <h2> title link in both article and index pages, and the "Read more…" link.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• necolas.github.io
  • Triggering command: /home/REDACTED/work/blog/blog/build/bin/Debug/net10.0/build /home/REDACTED/work/blog/blog/build/bin/Debug/net10.0/build --force (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Title link in article page causing 404.</issue_title>
<issue_description>H2 href in "/mesa/opengl-framebuffer" is "mesa/opengl-framebuffer", causing target URL to be "/mesa/mesa/opengl-framebuffer"</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Title link in article page causing 404. #28

---

⌨️ Start Copilot coding agent tasks without leaving your editor — available in VS Code, Visual Studio, JetBrains IDEs and Eclipse.

[github-actions]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-mushroom-0f508f700-29.eastasia.3.azurestaticapps.net