docs: Component Architecture - Tiers, Inheritance, Minimalism
- Add Component Architecture (chapter 8):
- Tier 1 Canonical: Button, Input, Select, Card, Modal, Navigation,
Table, Data Grid, Search, Map Panel (10 components)
- Tier 2 Derived: Badge, Alert, Toast, Tooltip, Accordion, Tabs,
Breadcrumb, Pagination, Empty State, Skeleton (10 components)
- Tier 3 Domain: KPI Card, Map Overlay Panel, Layer Selector,
Mission Status, Dataset Card, Geospatial Inspector, Asset Summary,
Coordinate Picker, Timeline Panel (9 components)
- Component Inheritance: visual hierarchy showing parent-child
relationships (Button to Icon Button to Split Button, etc.)
- New Component Rule: 4-step checklist before creating anything new
- Principle: system shall be minimal, not maximal
- Restructure component numbering: 8.3.x for specifications
- Update table of contents with new structure
Rationale: Components before colors (component structure drives color
usage). Tiers prevent bloat. Inheritance prevents duplication.
Minimalism principle reduces complexity.
Bernt
a412177512