Jens
faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
48 lines
913 B
Markdown
48 lines
913 B
Markdown
# GeoIntel Style Guide
|
|
|
|
## Visual direction
|
|
|
|
GeoIntel should feel like a modern engineering workbench, not old desktop GIS software.
|
|
|
|
## Map layer colors
|
|
|
|
- Buildings: amber/orange.
|
|
- Roads: neutral gray.
|
|
- Water: blue.
|
|
- Vegetation: green.
|
|
- Detection boxes: yellow/orange.
|
|
- False positives: red.
|
|
- False negatives: purple.
|
|
- Matched detections: green.
|
|
|
|
## UI principles
|
|
|
|
- Analysis-first, map-supported.
|
|
- Always show status and provenance.
|
|
- No decorative clutter.
|
|
- Technical but readable.
|
|
- Every output should be exportable or inspectable.
|
|
|
|
## Component style
|
|
|
|
- Dense but not cramped.
|
|
- Clear empty states.
|
|
- Explicit loading states.
|
|
- Confidence/status badges.
|
|
- Sidebar navigation with workbench sections.
|
|
|
|
## Terminology
|
|
|
|
Use consistent module names:
|
|
|
|
- Project Workspace
|
|
- Map Workbench
|
|
- Dataset Manager
|
|
- Raster Lab
|
|
- Vector Lab
|
|
- Detection Lab
|
|
- Segmentation Lab
|
|
- QA/QC Lab
|
|
- Change Lab
|
|
- Exports
|