feat: complete M2 content workspace and inspector
This commit is contained in:
1 parent
931f561e7f
commit
cf6eaba534
438 files changed
+59749
-19043
No files matched your search
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: blacksite-editor-ux
|
||||
description: Design and evaluate Blacksite editor UI/UX changes using a production editor interaction rubric, explicit state matrices, existing visual language, and native acceptance criteria. Use for Content Browser, Inspector, viewport, dialogs, material UI, and other interactive editor work.
|
||||
---
|
||||
|
||||
# Blacksite editor UX
|
||||
|
||||
Read [the editor UX rubric](references/editor-ux-rubric.md). Before implementing meaningful UI behavior, record a compact interaction-state matrix in session state or the active plan.
|
||||
|
||||
Cover only relevant states, but explicitly consider empty, single/multi-selection, narrow/resized, invalid/broken, inherited/read-only/built-in, loading, confirmation, cancel/failure, undo/redo, and restart persistence.
|
||||
|
||||
Keep egui rendering thin and reuse established components, spacing, icons, cards, badges, drag/drop feedback, and editor language. Move reusable models and transactions to the lightest owning module/crate. Keep IDs, fingerprints, provenance, and implementation-owned data out of primary editing surfaces.
|
||||
|
||||
Create named native scenarios and hand them to `blacksite-native-qa`. Unit tests and screenshots alone are not acceptance; exercise the interaction. If the user says behavior still does not work properly, return to acceptance-in-progress and record a scope delta rather than treating it as unrelated by default.
|
||||
@@ -0,0 +1,29 @@
|
||||
# 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.
|
||||
Reference in new issue
Block a user