Repository navigation
Conversation
|
A feature plan for editing core's columns block in the editor, following the nesting block RFC in emdash-cms#2049: optional gap, vertical alignment, wrap and per-column span fields, a map of the layout in the editor with each column opened at full width, and columns rendered with the page's components.
bimsonz
force-pushed
the
design/columns-block-editing
branch
from
October 18, 2026 15:33
e1dd578 to
5406935
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design proposal
Proposal: proposals/columns-block-editing.md
Core's
columnsblock is written by the WordPress importer and rendered byColumns, but the editor can't edit it. This plan makes it editable, as Louis Escher's nesting block RFC in #2049 asks, using the block core already has instead of a new type.I've run a version of this on boulderbrighton.dev since August for its header, footer and page layouts. The implementation is written on current
main, and I'll open it once this plan is settled.Today an imported columns block opens as a card that can't be edited:
Editing columns side by side doesn't work at laptop widths. With three or four columns each one is a narrow strip, and a page of a few rows runs to several screens:
So in the editor a columns block is a map of its layout. Each box is a column at its relative width, showing its first heading and the kinds of block it holds:
Clicking a box opens that column underneath at the full width of the editor, where its blocks are edited as usual. Done, or carrying on elsewhere in the page, closes it:
On the site the same page renders as columns:
Proposal type
Related work
Discussion: #2049
#2248 was my earlier PR, built on Louis's prototype. It was closed for an unsigned CLA, and the implementation will come as a new PR. #1967 made the gallery block editable the same way. Of the open design PRs, #4168 leaves Portable Text blocks out of scope, #4196 changes the table's own controls, not where a table can go, and #4240 changes how media usage reads custom blocks, where this plan only makes that walk reach blocks inside a column.
Readiness
accepted(check only when ready to merge)AI assistance