29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
# Vapor Theme Notes
|
|
|
|
This module is the active reusable theme source for design-code consumers.
|
|
|
|
## What it captures
|
|
|
|
- Vapor control surfaces and button hierarchy
|
|
- segmented controls and grouped tab geometry
|
|
- table/filter/toolbar primitives
|
|
- icon rendering baseline and shared sprite usage
|
|
- modal and status component style language
|
|
- app-shell color/height presets for host-level branding fit within Vapor aesthetics
|
|
|
|
## How to use
|
|
|
|
- Use this module as the visual baseline for host projects that adopt the canonical demo style.
|
|
- Pattern contracts should reference shared behavior contracts and rely on this module for visual primitives.
|
|
- When baseline visuals change, update this module first to keep downstream integration deterministic.
|
|
- For shell color selection, use `palette-catalog.md` and set `data-vapor-shell` on `<html>`.
|
|
- For runtime switching, the recommended query key is `vapor_shell` (same IDs as the catalog).
|
|
- Keep host-specific brand overrides outside this module unless they are reusable presets.
|
|
|
|
## Boundary
|
|
|
|
- This module standardizes visual language only.
|
|
- Domain behavior, labels, and business workflow semantics belong to pattern contracts.
|
|
- Preset palette IDs are part of the reusable contract; host projects may choose one, but should not
|
|
rename/remove preset IDs in downstream copies without migration notes.
|