Prepare reusable Vapor theme bundle and canonical design map for cross-project integration

This commit is contained in:
2026-02-28 14:50:06 +03:00
parent 45dc8a8868
commit 1553eb1394
20 changed files with 5071 additions and 24 deletions

View File

@@ -1,17 +1,18 @@
# Aqua Theme Module (Canonical Design Layer)
# Aqua Theme Module (Legacy Archive Layer)
Status: canonical Aqua design layer for reusable UI primitives.
Status: legacy archive/reference layer (not the active demo/scaffold baseline).
This directory defines the shared Aqua visual language for the design code:
This directory preserves the Aqua visual language archive for the design code:
- global visual tokens and component surfaces
- reusable control geometry (buttons, segmented controls, table chrome)
- icon rendering baseline (stroke style + sprite integration)
Pattern modules consume this theme layer and then define behavior-specific contracts.
Active pattern contracts should target the current baseline and may reference this module only
for migration/comparison purposes.
Contents:
- `demo-aqua-freeze.css`canonical Aqua stylesheet baseline used by demo/scaffold references
- `demo-aqua-freeze.css`frozen Aqua stylesheet snapshot
- `templates/icon_sprite.html` — canonical icon sprite for reusable action semantics
- `notes.md` — scope and usage policy for this theme module

View File

@@ -2865,7 +2865,7 @@ code {
background: linear-gradient(90deg, rgba(245,247,250,0.96), rgba(238,242,247,0.96));
}
/* Aqua-first authoritative segmented controls for playground modules. */
/* Legacy Aqua snapshot segmented controls for playground modules. */
.style-playground.theme-aqua .status-filter-tabs {
display: inline-flex;
flex-wrap: nowrap;

View File

@@ -1,6 +1,6 @@
# Aqua Theme Notes
This module is the reusable Aqua style source for design-code consumers.
This module is a reusable Aqua style archive for design-code consumers.
## What it captures
@@ -12,9 +12,10 @@ This module is the reusable Aqua style source for design-code consumers.
## How to use
- Treat this module as the visual baseline for reusable UI components in this repository.
- Pattern contracts should reference this module instead of redefining shared visual primitives.
- When visual behavior changes in demo/scaffold, sync the canonical rules here so host projects can reproduce the same output deterministically.
- Treat this module as a legacy reference snapshot, not the active baseline.
- Pattern contracts should inherit the active baseline first and use this module only when a host
project explicitly opts into Aqua-like styling.
- Do not move new baseline decisions here.
## Boundary