Add columns to the page editor (#68) #74
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba!74
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/68-columns"
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?
Closes #68
Summary
A Columns block in the page editor: 2 or 3 columns of equal width, side by side from md on and stacked below. Our own Editor.js tool with one nested editor per column (ADR 0016).
The format nests one level; the parser, search text, page image references and renderer recurse:
Behaviour in the editor:
Also: a page's content and its editor now span the page's full width (max-w-6xl), and the page editor is taller, so editing looks like the page when read.
Evidence
After: unit tests for round trip, dropping nested columns and unknown blocks, search text, image ids, renderer; e2e:
Mutation check: with keydown not stopped at a column's border, the Enter and Tab assertions fail. The paste assertion cannot fail: Editor.js 2.31 already ignores paste targets in nested editors; it stays as a guard.
Merge Danger
Door: two-way
No migration. Stored columns blocks would be dropped by an older parser on the next save of that page, so rolling back after pages use columns loses that layout's content on re-save.
Blast Radius: pages
Page editor and page rendering only; guides, steps and categories keep their editors and 48rem width. Known limit: undo works per editor (a column or the page), not across both.
🤖 Generated with Claude Code