docs: record UI direction — dashboards for map-heavy modes

Phase 5 decision gate of the architecture refactor plan: dedicated
dashboard pages are the pattern for map-centric modes; APRS and
Meshtastic migrations to follow under separate plans.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
James Smith
2026-06-12 08:46:37 +01:00
parent 5cff7de117
commit 379b6a9667
+5
View File
@@ -158,6 +158,11 @@ Each signal type has its own Flask blueprint:
| direwolf | APRS | TNC modem for packet radio |
### Frontend Structure
- **UI direction (decided 2026-06-12)**: map-heavy modes get dedicated dashboard
pages (`/adsb/dashboard`, `/ais/dashboard`, `/satellite/dashboard`); the SPA
in `index.html` keeps text/scan modes. APRS and Meshtastic are map-centric
and should migrate to dashboards under their own plans — do not grow their
SPA footprint.
- **Templates**: `templates/index.html` (main SPA), `templates/partials/modes/*.html` (sidebar panels), `templates/partials/nav.html` (global nav)
- **JS Modules**: `static/js/modes/*.js` - IIFE pattern per mode (e.g., `WeatherSat`, `SSTV`, `Meshtastic`)
- **CSS**: `static/css/modes/*.css` - scoped styles per mode, CSS variables for theming (`--bg-card`, `--accent-cyan`, `--font-mono`)