docs: audit and archive completed Journals and Badges projects
This commit is contained in:
@@ -49,6 +49,14 @@ Do not delete historical context; move to `documentation/archive/` with clear na
|
||||
- Added `documentation/archive/README.md` to explain archive categories and restoration policy.
|
||||
- Renamed `AE__Docker_CI_Cache_Policy.md` -> `GUIDE__Docker_CI_Cache_Policy.md`.
|
||||
- Renamed `AE__UI_UX_future_ideas.md` -> `PROPOSAL__AE_UI_UX_Future_Ideas.md`.
|
||||
- Audited the Journals UI update against current source and archived
|
||||
`PROJECT__AE_UI_Journals_Module_Update_2026.md`; remaining security work was moved to
|
||||
the active task list and module documentation.
|
||||
- Audited the Badges review/print project against current source and archived
|
||||
`PROJECT__AE_Events_Badges_Review_Print.md`; email delivery and permission-source
|
||||
unification remain active follow-ups.
|
||||
- Audited Site Passcode Security against current source. It remains an active high-priority
|
||||
project because plaintext client storage and local passcode comparison are still present.
|
||||
|
||||
### Next archive candidates (review + approve)
|
||||
- Older style-review snapshots once current style guide references are centralized.
|
||||
@@ -65,7 +73,7 @@ Monthly lightweight review:
|
||||
|
||||
## 5) Immediate Follow-Up Tasks
|
||||
|
||||
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__Permissions_and_Security.md` against current permission helpers and IDAA authentication behavior.
|
||||
1. Continue quarterly archive reviews for remaining stale `PROJECT__` docs; the Journals and Badges projects were archived on 2026-06-12, while Site Passcode Security remains active.
|
||||
2. Continue the broader permission-helper and IDAA authentication review; the Site Passcode section was source-verified on 2026-06-12.
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user