Skip to content

Better organization for block transforms #40208

@mtias

Description

@mtias

Block transforms are one of the most important and powerful features of the block editor. They allow switching content types effortlessly and open many paths for users and block developers. They are so useful that it's natural people use them for basic operations (paragraph > heading), layout transforms (paragraph > group, paragraph > row), block replacements (site logo > site title), variations transforms, and everything in between.

Given this reality, the transforms menu has grown a lot, often obscuring basic transforms in favor of niche ones. I think we can improve this situation by making a couple tweaks:

  • Define a list of basic transform operations for text: paragraph, heading, list, and quote should always be prioritized and grouped together.
  • Define a list of layout related transforms: group, row, columns, stack, cover, etc, and group them together, separated from other content-driven transforms in the list of transforms.

The separation can be just a line separator for content-formatting ones and maybe another flyout menu for layouts. It'd also be fine to do a first pass that just adds a line divider and gathers them together in priority sets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs DesignNeeds design efforts.[Feature] BlocksOverall functionality of blocks[Priority] HighUsed to indicate top priority items that need quick attention[Type] EnhancementA suggestion for improvement.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions