Document stock visual decisions and operational UI examples

This commit is contained in:
mchus committed 2026-10-03 09:15:31 +03:00
1 parent 714447aa06
commit 08ff987edb
14 files changed
+532 -7

No files matched your search

+7 -2
View File
@@ -1,6 +1,6 @@
# Contract: Forms + Validation + Suggestions
Version: 1.1
Version: 1.2
This contract owns validation UX and multi-step flow rules for all form surfaces,
including modals (`modal-workflows` adds only modal-specific mechanics).
@@ -10,6 +10,12 @@ including modals (`modal-workflows` adds only modal-specific mechanics).
- Group fields semantically and keep labels explicit.
- Inputs requiring suggestions may use `datalist` or equivalent autocomplete UI.
- Suggestion sources must represent the full relevant scope (not only visible rows from paginated tables).
- Size fields by expected content: a short identifier/date beside a flexible name field is
preferable to equal-width columns. Align read-only metadata with adjacent editable values.
- Group editable child rows under the requirement/parent they satisfy, with indentation or
light connector lines. Label row controls even when repeated visible labels are omitted.
- Collapse field groups on narrow screens; retain horizontal scrolling for genuinely tabular
child editors. A fixed desktop width must not make the Save action unreachable.
## Validation
@@ -39,4 +45,3 @@ Rules:
- If a workflow includes upload, the file control should be clearly labeled and the supported formats explicit.
- Import parsing/preview may be delegated to a dedicated import/export pattern, but the form contract must remain clear.