You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A block is one line that opens. The line has its small wireframe, number and name, the layout it uses, a Hidden mark, and the start of its text; on the right a new eye button hides or shows the block at once, then move up and down, add below, duplicate and remove. Cards are tighter and smaller everywhere
Content and Design are apart. An open block shows its Content first, in compact fields two to a row. Its Design tab holds what every block shares: the layout (as buttons that show the choices), the background (as four colour swatches), spacing, the anchor and hiding the block. Choices of a few short words (columns, alignment, spacing) are a row of buttons instead of a menu
Lists inside a block are one line per item (people, plans, steps, questions): the line shows its picture, number, title and the start of its text, opens to its fields, and has its own move and remove buttons; Expand all and Collapse all are at the head of the list, and a new item opens ready to fill in. An image field has a thumbnail, its address, Library and a clear button
The block picker is filtered by kind: All, Openers, Content, Media, Showcase, Convert beside the search, with smaller cards and the layout and ready-made sections the same size. A block (or a theme's own) names its kind with category: in its block.yaml
Nothing about what is saved changed: the same values go to the same fields. Tests: the unit test of the blocks checks the kinds, the blocks test checks what the editor is given and what the script draws, and the hero layouts test now looks at the custom fields tab itself (it had looked at the end of the page by accident). The full suite and CI were not run