Renaming Reusable Blocks Should Still Be Discoverable

[courtneyr-dev]

Description

As a user familiar with Reusable Blocks, I expect to find them as a search result when inserting a block even if that feature has moved. Assume I do not know that the feature as moved.

How do I navigate to see all reuseable blocks I previously created? How do I get to the manage reusable blocks counterpart?

Step-by-step reproduction instructions

In 6.2.2:

• Create a Reusable Block
• Insert it from the Block Inserter searching for "reusable" and/or the reusable block tab
• Insert it using the / command in a paragraph block searching for "reusable"

In 6.3b2
Attempt the same

Screenshots, screen recording, code snippet

reusable63b2.mp4

ScreenFlow.mp4

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[Mamaduka]

Probably related issues: #51944, #52150.

cc @aaronrobertshaw

[ndiego]

I just added this to the 6.3 project board as a Todo.

[courtneyr-dev]

This is partially resolved in beta 3. Let's continue to check on the / command insertion method.

[ndiego]

Let's continue to check on the / command insertion method.

It would be good to keep the 6.2 functionality until perhaps 6.4. This will let folks migrate to the new "patterns" paradigm more gracefully.

[courtneyr-dev]

Beta 4: I am so happy with the prompts for users to know it has been renamed. I still wonder if /reusable should work, as /pattern does.

[courtneyr-dev]

Thanks @noisysocks!

[annezazu]

After seeing this change in beta 4 for create pattern/reusable block, I wanted to chime in as, while I understand this helps in the creation flow, it isn't going to help reduce confusion when thinking about the entire experience. I worry it might add to it. For example, here's a screenshot of what I see on a current reusable block after switching from 6.2.2 to 6.3 beta 4:

I think consistency across the different flows, along with the built in nudges, will help immensely. Are there other options to consider here that might work? For example, I can see we have concerns about the accessibility of the menu as is but @alexstine shares the following:

Another option might be to go with @talldan's suggestion above. Using aria-describedby or aria-description might work fine. Although I think aria-description still lacks browser support in some cases.

@richtabor @karmatosed for 6.3 in case you all have any thoughts here.

[richtabor]

Create pattern/reusable block isn't ideal.

I wonder if it will help if the control renders "Create synced pattern" and the sync control is enabled by default.

This is an existing reusable blocks control that folks who use reusable blocks will be looking for — and we're calling reusable blocks "synced patterns" now.

[glendaviesnz]

@richtabor, @annezazu, @courtneyr-dev what do you think of the idea of only showing Create pattern/reusable block until the user has seen and dismissed one of the rename prompts, once they have dismissed the prompt we assume "discovery phase over" and revert to Create pattern for the menu? That way they aren't stuck with that less than optimal menu for the whole of the 6.3 release.

[glendaviesnz]

"Create synced pattern" and the sync control is enabled by default.

I think this would help as the default action is then the previous behaviour. @SaxonF what do you think about this?

[ndiego]

"Create synced pattern" and the sync control is enabled by default.

Making the toggle enabled by default would make the experience more consistent for current reusable block users.

[glendaviesnz]

There is a PR here that renames the menu when the prompt is dismissed and also makes synced the default - probably good to get ✅ and into RC1 if possible.

[courtneyr-dev]

RC1 tested and I can find using /reusable 💯

[glendaviesnz]

Closing this as I think the discoverability is covered off for reusable blocks. We still need to look at the discrepancy of unsynced patterns not displaying in the quick inserter, but this is covered on this issue.