Skip to content

Patterns and content only: improve pattern editing discoverability #73271

Closed

Description

@ramonjd

Partly based on feedback from:

We need a more prominent way to indicate to the user that they can edit and are editing a pattern.

The experience of patterns introduces a major change. Agency owners and other power users are not used to needing to do an extra click to edit a pattern.

We also need to make it really obvious how to enter/exit the pattern editing mode and access the sidebar, including if someone doesn’t have the sidebar open.

The edit/exit button

One idea was to make edit section button more prominent to indicate to the user that they can edit and are editing a pattern.

This could be via colors and/or adding icons

Here's what it looks like now:

Kapture.2025-11-14.at.15.09.04.mp4

Icons and colors, list view opacity, and document bar text

Editor’s header updates the document bar to reflect the content user is editing. For synced patterns the visual update is bolder as you’re editing the source. #73208

Pattern block in ListView changes to the root block of the pattern user is now in.

See the following mockups:

Pattern Synced pattern
Image Image

Expose sidebar functionality/pattern internals

It's not obvious what is editable inside a pattern in content only mode.

Right now the sidebar fields and list view do this work. But they are not guaranteed to be open.

How do we communicate this new editing mode to users?

We might be to add an "Edit section" item or equivalent hint, to the pattern's root block toolbar, or in the canvas itself.

Activity

  1. added theissue type on Nov 14, 2025
  2. added
    [Feature] PatternsA collection of blocks that can be synced (previously reusable blocks) or unsynced
    on Nov 14, 2025
  3. changed the title [-]Patterns and content only: make the button to edit the pattern in the inspector bar more prominent[/-] [+]Patterns and content only: improve discoverability[/+] on Nov 19, 2025
  4. changed the title [-]Patterns and content only: improve discoverability[/-] [+]Patterns and content only: improve pattern editing discoverability[/+] on Nov 19, 2025
  5. fcoveram commented on Jan 5, 2026

    @fcoveram
    Contributor

    The experience of patterns introduces a major change. Agency owners and other power users are not used to needing to do an extra click to edit a pattern. We also need to make it really obvious how to enter/exit the pattern editing mode and access the sidebar, including if someone doesn’t have the sidebar open.

    In the current version, I see the Edit action in the block root's toolbar, and the back action in Editor's header. I think this address these two points.

    It's not obvious what is editable inside a pattern in content only mode. Right now the sidebar fields and list view do this work. But they are not guaranteed to be open. How do we communicate this new editing mode to users?

    The approach for opening the block panel is something that should be addressed more widely for the editor, rather than just for this use case. I think @annezazu has a similar concern and agrees that certain actions in the toolbar could open the panel to expose the advanced tools.

  6. talldan commented on Mar 4, 2026

    @talldan
    Contributor

    We might be to add an "Edit section" item or equivalent hint, to the pattern's root block toolbar, or in the canvas itself.

    This has been implemented now across unsynced patterns (#75602), so I think the discoverability has been improved. I'll close the issue. If there are any new ideas for refinement, those can be new issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs DesignNeeds design efforts.[Feature] PatternsA collection of blocks that can be synced (previously reusable blocks) or unsynced[Type] EnhancementA suggestion for improvement.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions