You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Reusable Blocks can only be managed in a 'legacy' wp-admin view:
It's tricky to find, and the friction of moving between editor / wp-admin can be quite disruptive.
Now feels like a good time to explore how we might bring this into the site editing experience, and make the most of the features therein (previews, focussed edit mode, etc).
As we look into this it would be good also to consider the management of any other site assets we might want to bring into the site editor: Patterns, Fonts, Media, etc.
The text was updated successfully, but these errors were encountered:
Yes I think that makes a lot of sense as a top level item, and it would provide a sensible home for the other items mentioned in the OP as well, when we get to them.
Do you think we need to introduce it straight away though? It might be unnecessary at this stage, if it only contains a single item...
I think we have a couple of avenues to explore:
Add the Library section now, to include Templates, Template Parts, and Reusable Blocks
Add the Reusable Blocks section now, and move it to a Library section later, once there are items to place alongside it (Patterns, Fonts, Media).
So the main question in my mind is whether we want to include Templates in the Library. What do you think?
I wonder if Templates and Template Parts shouldn't exist in a single "Templates" section, as RBs are a bit different. A Library section with just RBs honestly seems okay to me, especially if we know we'll add more to it.
Related to #44461 and a part of #32682.
Currently Reusable Blocks can only be managed in a 'legacy' wp-admin view:
It's tricky to find, and the friction of moving between editor / wp-admin can be quite disruptive.
Now feels like a good time to explore how we might bring this into the site editing experience, and make the most of the features therein (previews, focussed edit mode, etc).
As we look into this it would be good also to consider the management of any other site assets we might want to bring into the site editor: Patterns, Fonts, Media, etc.
The text was updated successfully, but these errors were encountered: