Editing screens overhaul: choose a direction and record the mockup #168
Labels
No labels
bug
enhancement
needs-triage
ready-for-agent
ready-for-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/deckle#168
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The editor's three surfaces are disconnected: the Page module is a list/grid without a preview, the preview is its own View module, and editing an element replaces the list with a full-screen form. The implementation mirrors that:
PagePane.tsxis ~2,200 lines, the gap/row/drop markup exists twice (flat list and slot cells), and strips, badges and menus are re-implemented per screen.Decision
Three interactive mockups were built on one shared component layer, differing only in composition:
Direction A was refined over six rounds (equal-height columns, categorised insert dialog,
enabledkey for pages and elements, TYPO3-style always-visible insert rows doubling as drop targets, cut/copy/paste across pages, inherited-slot override, disabled-page banner, pending-changes panel, unsaved-changes guard, inline validation).Done when
The chosen mockup, its sources and a decision log live in the repository so implementation issues can reference them.
enabledfield for pages and elements, shown under Access #170