30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
# Blacksite editor UX rubric
|
|
|
|
## Product intent
|
|
|
|
- What familiar editor or file-manager interaction is being matched?
|
|
- What is the primary action and what must be obvious without documentation?
|
|
- What happens on invalid input?
|
|
|
|
## Interaction matrix
|
|
|
|
Include relevant rows for mouse click, double click, right click, shortcut, drag start/hover/drop, multi-selection, empty-space action, narrow panel, modal/review, cancel, undo/redo, and restart.
|
|
|
|
## Visual design
|
|
|
|
- Reuse current typography, spacing, icons, cards, and status badges.
|
|
- Provide visible hover, drop, focus, invalid, and disabled states.
|
|
- Avoid duplicated controls and competing presentations.
|
|
- Hide managed/internal data unless diagnosing a failure.
|
|
- Support resizing and narrow layouts.
|
|
- Distinguish inherited/default/read-only state from explicit editable state.
|
|
|
|
## Acceptance
|
|
|
|
- Focused logic tests in the lightest owning crate.
|
|
- Focused UI wiring tests when editor-owned state matters.
|
|
- Native interaction against the intended build/profile.
|
|
- Targeted screenshot or recording of the relevant state.
|
|
- Cancel/failure proof and saved-state restart proof when applicable.
|
|
- Canonical documentation update after the behavior stabilizes.
|