Internal links reports — tmp/README.md

Internal links reports — tmp/README.md

This folder contains autogenerated reports and a small set of safe, automated changes for helping you find and fix broken internal links in the built _site output.

Files

• internal_links_auto_changes.csv — CSV of automated source edits applied by _scripts/fix_internal_links.rb (format: source_file,original_href,replacement). Backups were written as <file>.bak before any change; review backups before committing.

• internal_links_report.csv — Raw broken-link rows found by the linter (format: site_file,href,expected_target). Use this to find and edit the source pages.

• internal_links_summary.csv — Aggregated, prioritized list of missing hrefs (format: href,count,sample_site_files,expected_targets). Higher count means higher priority for fixing.

• internal_links_summary.txt — Human-friendly top summary of missing hrefs (first ~50 lines) for quick triage.

Scripts

• _scripts/fix_internal_links.rb — Safe auto-fix script that replaces href="foo.html" → href="foo/" when _site/foo/index.html exists. It writes .bak backups before modifying source files and writes tmp/internal_links_auto_changes.csv.

• _scripts/summarize_internal_links.rb — Summarizes the raw report into tmp/internal_links_summary.csv and tmp/internal_links_summary.txt.

How to use

1. Inspect tmp/internal_links_summary.csv to find the highest-impact missing hrefs. Review sample pages listed in that CSV.

2. For each missing href, decide whether to:
   • Update the source page to point to an existing _site page (recommended), or
   • Add the missing asset/page, or
   • Remove the stale/legacy link if the content is intentionally gone.
3. After making source edits, run:

bundle exec jekyll build
bundle exec rspec spec/pages/internal_links_spec.rb

1. Repeat until the spec passes.

Notes & Safety

• We excluded _legacypages/ from automated edits by request — legacy files are left unchanged.
• The auto-fix script only converts .html → / when a corresponding foo/index.html exists in _site.
• Always inspect .bak files before committing changes.

Want help?

If you want, I can:

• Produce a prioritized checklist (Markdown) with suggested edits for each high-impact href.
• Open a draft branch/PR that includes the safe automated changes and the tmp/ reports for review (no content commits without your approval).
• Start making small, human-reviewed content fixes on a branch for your review.

Tell me which you prefer and I’ll proceed.