Skip to content

Fix broken footer doc links (argus.huntridgelabs.com/docs/*.md 404s)#3

Open
BGebken wants to merge 3 commits intomainfrom
fix/broken-footer-doc-links
Open

Fix broken footer doc links (argus.huntridgelabs.com/docs/*.md 404s)#3
BGebken wants to merge 3 commits intomainfrom
fix/broken-footer-doc-links

Conversation

@BGebken
Copy link
Copy Markdown
Contributor

@BGebken BGebken commented Apr 17, 2026

Summary

  • The footer had 13 relative hrefs (e.g. docs/failure-control.md, CHANGELOG.md, SECURITY.md) that resolved against argus.huntridgelabs.com and 404'd — the website doesn't host any of those files.
  • Repointed each link to the corresponding file in huntridge-labs/argus on main (blob URLs for files, tree URL for docs/examples/).
  • User-reported example: https://argus.huntridgelabs.com/docs/failure-control.md

Test plan

  • After deploy, click each footer link (Product, Resources, Trust, Stewardship columns) and confirm it opens the correct doc on GitHub
  • Spot-check that no link still points to a path on argus.huntridgelabs.com

🤖 Generated with Claude Code

The footer used relative hrefs like `docs/failure-control.md` and
`CHANGELOG.md` that resolve against argus.huntridgelabs.com, but the
website doesn't host those files — they live in huntridge-labs/argus.
All 13 affected links now point to the corresponding GitHub blob/tree
URLs on main.

Co-Authored-By: Claude Opus 4 (1M context) <noreply@anthropic.com>
Previously the deploy workflow ran only `npm run build` and pushed the
output straight to Pages. Type errors and broken relative href values
(like the footer docs links fixed in #3) could only be caught in
production.

- Add `typecheck` script (`tsc --noEmit`) and `typescript` + `@types/*`
  dev deps.
- Split workflow into `verify` (runs on push + PR) and `deploy` (runs
  only on push to main). Deploy now depends on verify passing.
- verify runs: npm ci → typecheck → href sanity check → build.
- The href check greps src/ for any `href="..."` whose value doesn't
  start with http(s):, mailto:, tel:, #, or /. This catches the exact
  class of bug where a relative path like "docs/foo.md" was shipped
  to a site that doesn't host those files.

Note: lychee/link-checkers weren't appropriate here — the site is a
Vite SPA, so hrefs live in the JS bundle, not in the built HTML.

Co-Authored-By: Claude Opus 4 (1M context) <noreply@anthropic.com>
Add CI: typecheck + relative-href sanity check
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