frontend: Ghost-in-the-Shell overhaul — map-first landing, event blips, tickers #1
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "frontend-overhaul"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Full frontend overhaul per the Excalidraw brief — the interactive map is now the landing page, wrapped in a Ghost-in-the-Shell / Section-9 HUD theme (near-black navy, cyan+magenta accents, Orbitron/Rajdhani/Share Tech Mono, chamfered panels, scanlines, boot splash, UTC clock).
Map (unchanged core, new chrome)
Tickers (bottom dock)
GET /api/marketreturns{"symbols": [{symbol, price, change, change_pct, updated_at}]}— contract documented in the Settings panelNavigation & Settings
Backend
GET /api/eventsgainsbbox/since/has_coordsfilters (powers the blips layer, mirrors /api/fires)events.cameraenum value was added to the DB enum by migration 004 but never added tomodels.py/schemas.py— any events query 500s once camera events flow in. Now aligned.Verified
- Map is now the landing view: full-viewport NASA GIBS globe, existing fires/cameras/HLS map machinery preserved verbatim - New 'Event Blips' layer: geolocated ingest events, color-coded by source, bbox/since/has_coords filters added to GET /api/events - Weather / Flights(ADS-B) / Vessels(AIS) layer slots reserved (feed pending) - Market ticker strip with configurable symbols — auto-promotes to LIVE when GET /api/market returns {symbols:[...]} (contract documented in Settings) - Breaking-news ticker: LLM exec-summary flash + headline marquee, 15-min cycle - Dropdown nav (Map/News/Events/Alerts/Entities/Ingest/API Keys/Settings), Settings view (localStorage: symbols, map layer defaults), System panel - Section-9 theme: near-black navy, cyan/magenta accents, Orbitron/Rajdhani/ Share Tech Mono, chamfered HUD panels, scanlines, boot splash, UTC clock - Fix: events.camera enum value missing from models.py/schemas.py caused 500s on every events query once camera events flowed in (migration 004 added it to the DB enum only)looks good