Improvements to Synced Patterns

[mtias]

It's been a while since we gathered thoughts on where to take reusable blocks next. With the work that went into template parts — and particularly #27887 — the experience is going to be radically improved and several longstanding bugs removed. There are some design updates needed to accommodate some of these changes (no direct "edit / save" flow) and to improve the clarity of reusable blocks in general but let's also look into other ideas that can improve the different user flows related to them.

• Display reusable block title next to block type in toolbar (like template parts). Display reusable block name in locations where the block appears #28281
• Display reusable block outline when child blocks are selected (like template parts). Reusable blocks: Display outlines #28285
• Update block list view and breadcrumbs to show the title of a reusable block instead of "reusable block". Display reusable block name in locations where the block appears #28281
• Explore using an overlay plus extra click to get to edit the contents of a reusable block. Reusable blocks and Template parts – try a click-through-to-edit-children UX pattern #29337
• Communicate more clearly when a synced pattern has unsaved changes (in the canvas). #44048
• Improve initial creation flow to name a reusable block. Use a modal for the reusable blocks creation flow #29040
• Allow modifying saved title of reusable block in sidebar inspector.
• Show how many posts / pages are using a given block on the publish flow.
• Ensure post revisions are enabled for reusable blocks. Revisions missing for reusable blocks #19149
• Allow users to see and navigate to posts using a given reusable blocks from the post type management screen.
• Patterns: allow users to add a description #65724
• Review cases with 1000+ reusable blocks for performance bottlenecks Performance: Review pattern performance (at scale, various inserters, etc) #54704
• Consider support for categories or tags to organize reusable blocks. Organizing reusable blocks with categories or similar #7608
• Allow deleting a reusable block from the inspector Allow deleting a reusable block from the inspector #28355
• Proposal to rename "reusable blocks" to "synced blocks" #34352

[paaljoachim]

Adding the following issue to the list:
Add content alignment option into the main reusable block toolbar
#17640

There is also a bug related to the above issue. If one converts a Full width or Wide block to a reusable block the alignment option is also adjusted to the default Reusable block width. #8288

[Tropicalista]

About my issue linked here, is it possible to add a reducer on https://github.com/WordPress/gutenberg/blob/da8555d258edbe676fa079fb51252f918ae032e1/packages/reusable-blocks/src/store/reducer.js

to let know the block is just been converted from a reusable block?

[NewYorkerLaura]

Just adding to the discussion here. In 5.7.1 creating new reusable blocks experience is disastrous. Their primary functions have been stripped away. I've had to roll over 100 client sites back to 5.6.3. It is a UX disaster. The best feature and the strongest selling point to clients of the Block editor is now non-functional

• I have no ability to name a block
• Lots of "untitled blocks" doesn't let me know which one I want
• I am unable to edit the block if my boilerplate has changed and have those changes iterate across the site (kind of a disaster in a where my call to action purchase buttons across 50+ pages are now a right pain to update)
• I am unable to break a block out into regular blocks if I want a one-off change or are using the reusable block as a template

See attached video:

https://trainingvideoslaura.s3.amazonaws.com/reusable+block+not+working+on+PELC.mp4

[mtias]

The ability to name a block upon creation is addressed in trunk and should remove the case of having a bunch of "untitled reusable block" names:

[jameskoster]

A possible consideration for inclusion here: #43261

Edit: Tracked in #43598 instead.