Make WordPress Core

#58579 closed task (blessed) (fixed)

Editor: Introducing the "Library" section

Reported by: priethor's profile priethor Owned by:
Milestone: 6.3 Priority: high
Severity: normal Version:
Component: Editor Keywords: gutenberg-merge needs-dev-note needs-docs needs-user-docs
Focuses: Cc:

Description (last modified by priethor)

WordPress 6.3 aims to introduce an admin section or “library” for managing blocks, patterns, styles, and fonts. This includes renaming Reusable Blocks to (Synced) Patterns, as well as a new flow to create them. Therefore, it's crucial to polish this feature to deliver a great experience to users and add appropriate guidance to users about the Reusable blocks renaming, even if some of that polishing needs to be done during the Beta period.

cc @mikeschroder @azaozz @isabel_brison @ramonopoly

Attachments (2)

notice in menu.png (53.3 KB) - added by Joen 13 months ago.
Menu rename notice
notice in library.png (28.6 KB) - added by Joen 13 months ago.
Library rename notice

Download all attachments as: .zip

Change History (13)

#1 @audrasjb
13 months ago

  • Keywords needs-dev-note needs-docs needs-user-docs added

I personally think "Synced patterns" makes more sense than "Reusable blocks", so that is probably an interesting change.

However, this is called "Reusable blocks" since WP 5.0 and this terminology is massively present in the ecosystem. I think we must communicate widely on this change and as soon as possible, so the ecosystem can catch up and prepare in time for 6.3.

Adding needs-dev-note, needs-doc, needs-user-doc.

Last edited 13 months ago by audrasjb (previous) (diff)

#2 @hellofromTonya
13 months ago

Related #46370 which may be required to support the Font Library and font management.

#3 @priethor
13 months ago

  • Description modified (diff)

This ticket was mentioned in Slack in #core-editor by karmatosed. View the logs.

13 months ago

#5 @Joen
13 months ago

From design and having worked on the Library, I think it's important we bless it. The code is solid, and the main concern leveraged is the name change itself, which I believe will be easy to mitigate as tiny followups (see notice attachments).

The question then is: why rename them?

One of the features I anticipate will play a big role in 6.4 and later, is the wp:pattern block: It is a big feature gap in the block editor allowing a sectional design to live in one place, but its content to be edited locally, then updated across. There is a massive overlap with reusable blocks functionality, which is why the name change is intended to reduce long term confusion around the two. As mentioned in the GH issue, reusable blocks might even be absorbed as a type of sync property of the pattern block.

In that light, making the name change now is going to mitigate future headaches that we will have to tackle regardless, and through careful notice of the change, we can limit those headaches further (see mockups).

13 months ago

Menu rename notice

13 months ago

Library rename notice

#6 @glendaviesnz
13 months ago

@Joen I have added the hints as you suggest here

#7 follow-up: @annezazu
13 months ago

This is an important chunk of work to both get in and get right for 6.3 as we wrap phase 2. Can this be blessed for the release?

#8 in reply to: ↑ 7 @azaozz
13 months ago

  • Type changed from feature request to task (blessed)

Replying to annezazu:

Of course.

This ticket was mentioned in Slack in #core by mukeshpanchal27. View the logs.

12 months ago

#10 @poena
12 months ago

Hi @priethor, @Joen @annezazu The menu item has been implemented, and the reusable blocks have been renamed (
Are there any necessary steps left to complete before this ticket can be closed?
Are we waiting for the dev note to be published first?

#11 @isabel_brison
12 months ago

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.