docs: fifth-pass guide metadata and doc ownership cues
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Project: Documentation Refresh and Archive Plan (2026)
|
||||
|
||||
**Last Updated:** 2026-06-12
|
||||
|
||||
**Goal:** Keep onboarding docs fast and current while preserving historical context in archive.
|
||||
|
||||
## 1) Naming Standard
|
||||
@@ -55,7 +57,7 @@ Monthly lightweight review:
|
||||
|
||||
## 5) Immediate Follow-Up Tasks
|
||||
|
||||
1. Run a link-check pass across documentation files.
|
||||
2. Add `Last Updated` metadata lines to remaining `GUIDE__` and `PROJECT__` docs that are still actively edited.
|
||||
3. Run a lightweight cross-reference audit for `archive/` links in active docs to ensure all moved files remain discoverable.
|
||||
4. Add a short "Doc Owner" line for high-churn docs (`BOOTSTRAP__*`, `TODO__Agents.md`, and `README__Docs_Index.md`) so update responsibility stays explicit.
|
||||
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").
|
||||
|
||||
Reference in New Issue
Block a user