feat(ui): redesign GeoIntel as Atlas Workbench
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s

This commit is contained in:
Codex
2026-07-19 14:24:54 +02:00
parent ea27873dce
commit 87345f1a8c
19 changed files with 1817 additions and 631 deletions
+13 -5
View File
@@ -113,11 +113,19 @@ The workbench uses a task-based shell instead of a single long panel stack. `App
The premium V1 presentation layer lives in `src/styles/premium.css`. It groups navigation by Workspace, Analyze and Deliver, removes the permanent inspector column, gives desktop/ultrawide workspaces stable readable widths and switches narrow screens to full-width content with a horizontally scrollable navigation rail. API calls and workflow state remain owned by the existing hooks.
The final visual polish layer lives in `src/styles/visual-polish.css`. It keeps
the map dominant, places the results rail beside the map when the viewport is
wide enough, preserves a readable two-column map flow on smaller desktops and
stacks the context header and navigation explicitly on mobile. It contains no
workflow or API logic.
The Stitch-guided Atlas Workbench redesign lives in
`src/styles/atlas-workbench.css`, with the shared icon navigation in
`components/shell/WorkbenchNavigation.tsx`. The application uses one compact
navigation rail, one context bar and task-specific work surfaces. The primary
map keeps the theme rail, map and insight rail in one row on normal desktop
and gives additional ultrawide space to the map instead of stretching text
panels. Mobile keeps all workspaces in a horizontally scrollable rail and
bounds the theme list so the map remains reachable early in the flow.
The visual contract, Stitch project and screen references are documented in
`docs/UI_DESIGN_SYSTEM.md`. The redesign changes presentation and information
hierarchy only; API, persistence and GIS behavior remain owned by the existing
hooks and services.
## Current component boundaries