docs: fourth-pass metadata normalization and archive linking
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Aether Events — Badges
|
||||
|
||||
**Last Updated:** 2026-06-12
|
||||
|
||||
The Badges module manages event attendee records and their physical badge configurations. It supports multi-source imports, field protection for onsite edits, and multi-tier access control for self-service review.
|
||||
|
||||
---
|
||||
|
||||
@@ -1,5 +1,7 @@
|
||||
# Aether Events — Launcher (Podium Display)
|
||||
|
||||
**Last Updated:** 2026-06-12
|
||||
|
||||
The Launcher module provides the podium display interface that runs on each session room's kiosk machine. It is designed to work in standard browsers but is optimized for the **Aether Desktop (Electron)** native shell.
|
||||
|
||||
---
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# Aether Events — Launcher Configuration Menu (Inventory)
|
||||
|
||||
> **Status:** Current Reference (v3.0)
|
||||
> **Last Updated:** 2026-06-12
|
||||
> **Location:** `src/routes/events/[event_id]/(launcher)/launcher_cfg.svelte`
|
||||
|
||||
This document provides a detailed inventory of the Launcher's configuration menu settings as of May 2026. This serves as the baseline for the v3.1 reorganization into a modal-based tabbed interface.
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# Aether Events — Exhibitor Leads Module (v3)
|
||||
|
||||
**Status:** Implemented and ready for demo. Core lead capture flow works end-to-end.
|
||||
**Last Updated:** 2026-06-12
|
||||
**Platform:** PWA only — mobile-first, offline-capable.
|
||||
**Target users:** Conference exhibitors scanning attendee badges at their booths.
|
||||
|
||||
|
||||
@@ -1,5 +1,7 @@
|
||||
# Aether Events — Presentation Management
|
||||
|
||||
**Last Updated:** 2026-06-12
|
||||
|
||||
The Presentation Management module handles the full lifecycle of conference content: sessions, presentations, presenters, presentation files, and room/location assignments. It serves as the "Back Office" interface for event staff.
|
||||
|
||||
---
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# Aether IDAA — Archives Module
|
||||
|
||||
**Status:** Active (private)
|
||||
**Last Updated:** 2026-06-12
|
||||
**Routes:** `src/routes/idaa/(idaa)/archives/`
|
||||
**Underlying library:** `src/lib/ae_archives/`
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# Aether IDAA — Bulletin Board Module
|
||||
|
||||
**Status:** Active (private)
|
||||
**Last Updated:** 2026-06-12
|
||||
**Routes:** `src/routes/idaa/(idaa)/bb/`
|
||||
**Underlying library:** `src/lib/ae_posts/`
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# Aether IDAA — Recovery Meetings Module
|
||||
|
||||
**Status:** Active (private)
|
||||
**Last Updated:** 2026-06-12
|
||||
**Routes:** `src/routes/idaa/(idaa)/recovery_meetings/`
|
||||
**Underlying library:** `src/lib/ae_events/` (repurposed)
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# Aether IDAA — Video Conferences Module
|
||||
|
||||
**Status:** Active (private)
|
||||
**Last Updated:** 2026-06-12
|
||||
**Routes:** `src/routes/idaa/(idaa)/video_conferences/`
|
||||
|
||||
Video Conferences provides IDAA’s Jitsi meeting access experience within the IDAA private module.
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# Aether Journals — Module Overview
|
||||
|
||||
**Status:** Active module
|
||||
**Last Updated:** 2026-06-12
|
||||
**Library:** `src/lib/ae_journals/`
|
||||
**Routes:** `src/routes/journals/`
|
||||
|
||||
|
||||
@@ -1,5 +1,7 @@
|
||||
# Aether Journals: Configuration & Settings Map
|
||||
|
||||
**Last Updated:** 2026-06-12
|
||||
|
||||
This document tracks all available settings across the three levels of the Journals module.
|
||||
|
||||
## 1. Module Level (Global)
|
||||
|
||||
@@ -55,7 +55,7 @@ Monthly lightweight review:
|
||||
|
||||
## 5) Immediate Follow-Up Tasks
|
||||
|
||||
1. Add `Last Updated` metadata lines to all `MODULE__` docs.
|
||||
2. Run a link-check pass across documentation files.
|
||||
3. Add `Last Updated` metadata lines to remaining `GUIDE__` and `PROJECT__` docs that are still actively edited.
|
||||
4. Run a lightweight cross-reference audit for `archive/` links in active docs to ensure all moved files remain discoverable.
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user