Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: clarify municipality-first workbench flow
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
Details
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
Details
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Jens
2026-07-26 03:17:03 +02:00
parent d79f751773
commit 5efcf94d82
9 changed files with 245 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CODEX_EXECUTION_LOG.md
+22
View File
@@ -11304,3 +11304,25 @@ Validation:
- visually inspected the canonical 512 px render and the 32 px favicon derivative;
- verified desktop and mobile landing-page renders with the new GeoIntel and ITWorx assets present, meaningful page content and no Vite error overlay; expected API 500 responses remained limited to the absent local backend;
- React review confirmed named, isolated brand components and accessible decorative versus meaningful image semantics.
## 2026-07-26 - Task-first usability and functional navigation audit
Implemented:
- reduced the wide desktop navigation rail and renamed the misleading read-only `Beheer` destination to the operationally accurate `Systeem` workspace;
- aligned the current/evolution period control into one stable map-header tool group and added containment rules for long dataset, quality, provider and context labels;
- promoted municipality selection from a hidden long select to a searchable first step above the map; selecting an exact persisted municipality immediately activates its existing Area geometry and project datasets;
- renumbered the simple map journey to municipality, theme, selection and results, and rewrote the map instruction to describe that complete path;
- turned the empty quality state into an actionable handoff to the map or image-analysis workflow while preserving persisted QA evidence, metrics and map drill-down when checks exist;
- replaced the passive provider-only management page with a system command surface that reports configured connectors and routes operators to the map, source/area management or readiness status.
Validation:
- frontend unit tests cover exact municipality search, regional-area exclusion and active municipality feedback;
- frontend TypeScript and production build passed;
- React review confirmed local state ownership, semantic form/button controls, stable list keys and accessible names;
- no API, persistence, CRS or official-source semantics changed.
Known limitation:
- the authenticated live workbench still requires a user session for visual browser verification after deployment; public landing and runtime health remain independently testable.