Files
bible/rules/patterns/web-visual-baseline/README.md
T

25 lines
1.5 KiB
Markdown

# Web Visual Baseline — Reference Assets
The normative rules live in `contract.md`.
Canonical reference files (full, production version of the style) are in `assets/`:
- `assets/view.css` — copy this as the starting stylesheet and adapt tokens
- `assets/view.html` — reference page structure (header, panels, tables)
- `assets/upload.html` — reference upload/open panel
- [assets/operations.html](assets/operations.html) — static component sheet for dense tables,
nested rows, active filters, draft controls, history, disabled/loading states and privacy masking
- [assets/operations.css](assets/operations.css) — optional operational extension, loaded after
`view.css`; no duplicate palette or base theme
- [recipes.md](recipes.md) — integration examples for formatting, forms, drafts and privacy
- [stock-review-2026-10-03.md](stock-review-2026-10-03.md) — source audit, accepted decisions
and implementation gaps that must not become shared defaults
Do not maintain a separate "starter" copy of the CSS anywhere; `assets/view.css` is the
single source. For a new app, copy it and delete unused rules.
Open `assets/operations.html` locally to inspect the sample geometry; it needs no server,
external fonts or vendor libraries. It is a static state reference, not a working CRUD screen.
Wire application behavior according to the linked contracts and recipes. The existing `view.css`
is unchanged: optional density, sticky scrolling and operational controls live in the extension.