docs: sixth-pass project routing and link validation

This commit is contained in:
Scott Idem
2026-06-12 17:05:13 -04:00
parent 1e3f541a39
commit e6fb4b289f
9 changed files with 21 additions and 9 deletions

View File

@@ -41,6 +41,9 @@ Do not delete historical context; move to `documentation/archive/` with clear na
- Renamed `AE_Docker_CI_cache_policy.md` -> `AE__Docker_CI_Cache_Policy.md`.
- Archived `PROJECT__AE_Style_Review.md` -> `archive/PROJECT__AE_Style_Review_2026-03.md` (active style source is `GUIDE__AE_UI_Style_Guidelines.md`).
- Clarified scope split: `GUIDE__AE_Events_Badges_Onsite.md` = deep badge-print reference, `GUIDE__AE_Events_Onsite_Runbook.md` = cross-module onsite operations runbook.
- Validated all `documentation/*.md` references in active docs; no missing targets remain.
- Added ownership and review-trigger metadata to the bootstrap, task list, and docs index.
- Reviewed active project docs for archive eligibility. Object Field Editor and Site Passcode Security remain active and were added to the docs index.
### Next archive candidates (review + approve)
- Older style-review snapshots once current style guide references are centralized.
@@ -57,7 +60,7 @@ Monthly lightweight review:
## 5) Immediate Follow-Up Tasks
1. Add `Last Updated` metadata lines to remaining active docs that still only encode dates via `Version` or legacy `Last updated` casing.
2. Promote one consistent `Last Updated` format (`**Last Updated:** YYYY-MM-DD`) across all active docs.
3. Run a quarterly archive review: identify stale `PROJECT__` docs with no TODO linkage and move to `documentation/archive/`.
4. Add a short "Review Trigger" line to high-churn docs (for example, "update after any commit that renames docs or changes module routes").
1. Run a quarterly archive review: identify stale `PROJECT__` docs with no TODO or index linkage and move them to `documentation/archive/`.
2. Review `AE__*` reference docs for overlap, outdated stack assumptions, and inconsistent naming.
3. Review module docs against current routes and store names rather than relying only on filename/header freshness.
4. Add a lightweight reusable link-check script if manual path validation becomes frequent.