Skip to content

Fix the broken ADSB-AT-01 link and the aireplay-ng command rendering - #17

Merged
wero1414 merged 1 commit into
mainfrom
fix/broken-link-and-command-rendering
Sep 29, 2026
Merged

wero1414 merged 1 commit into
mainfrom
fix/broken-link-and-command-rendering

Conversation

@wero1414

Copy link
Copy Markdown
Member

Two problems found by crawling the published site (240 pages).

Broken link

/controls/rfsam-adsb-at-01/ returned 404. src/data/coverage-map.js listed RFSAM-ADSB-AT-01 as existing, but the control file was never written, so the roadmap linked to a page that does not exist.

  • The entry is now planned.
  • npm run validate now fails when the coverage map and src/content/controls/ disagree, in either direction. Covered by a unit test.

Fixes #9.

Command rendered wrong

On the Resources page, aireplay-ng --test was displayed with a dash in place of the two hyphens, because the command was written as plain prose. It is now in code formatting. It was the only such case in the content.

Checks

npm test (18 pass), npm run validate and npm run build pass. The built site has no link to the missing page and no dash characters.

RFSAM-ADSB-AT-01 was listed as existing in the coverage map with no control file, so the roadmap linked to a 404. It is now planned, and validation fails when the map and the controls directory disagree.

The aireplay-ng --test command in RFSAM-RES-11 is now in code formatting, so its two hyphens are no longer rendered as a dash.
@wero1414
wero1414 merged commit a8fcad5 into main Sep 29, 2026
1 check passed
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.

coverage-map.js lists RFSAM-ADSB-AT-01 as existing but the file isn't there

1 participant