-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template Parts and path towards "library" management #50397
Comments
Adding a potential pathway here. We've put far more emphasis on patterns as of late and will continue to do so. The site editor currently doesn't reflect these efforts. This project aims to set the stage for block unification by introducing the concept of a library which is a dedicated space for all the building blocks of your site. For this bit of work we can simply rename the Template Parts menu item to Library and introducing category grouping to the list page. This includes Headers, Footers, and any other template parts available. This new "Library" space is a natural fit for when pattern management becomes a thing. 6.3-library.mp4
|
Noting #50028 as related to this one. |
@SaxonF not urgent, but per recent designs (#50379 (comment) and #50392 (comment) come to mind), would you be able to update your video, or share screenshots instead, with the latest sidebar design? I think we can update this issue and mark it ready for dev with that. |
Is there a Figma file of the UI available on the WordPress.org Team? |
Noting that as we explore this Library concept, it would be advantageous to explore how to show the relationship between template parts and templates: #42482 |
Agreed. It doesn't even need to be granular to begin with (though that would be nice). Just marking the items that are actively in use would be helpful. It probably requires a dedicated design effort though, to get the placement right. Anyway here are some updates to Saxon's earlier visuals, taking into account the latest work around other panels: Instead of drilldowns for each type, I lean slightly towards a single list for a couple of reasons:
The drilldown pattern can be utilised in the future, once all patterns are displayed in the Library and scalability becomes a bigger issue. Of course if I've missed something and the intention is to have that as a part of 6.3, then we should probably use the drilldown straight-away – though it will require some modifications to the management view. What do y'all think? |
I like starting simple. |
One last follow up here: #52042 Rest is considered accomplished. |
Milestone 1
Milestone 2
The text was updated successfully, but these errors were encountered: