-
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 should follow the wp:pattern interaction model #65698
Comments
Not sure how I feel about this one. I thought we learned through all the confusion from users that directly allowing editing of synced patterns causes confusion because it's not clear that your change affect the rest of the site? 🤔 |
Yeah, it'd be something we need to clarify on the UI. There's a lot of permutation between partially synced patterns and content-only UI that we need to get right. For fully synced (templates and patterns) it can just be a matter of what is exposed as content—ff there are no named static blocks, for example, perhaps that just doesn't get exposed in content-only. But blocks like site-title, site-logo, navigation, etc, that are already global in attributes would be very useful to have the ability to edit their "content" without having to go into design mode for it. |
The video here (and attached) touches on this a little bit, specifically at 2.30 mark. As an interim step I think we can still follow the same rules as synced patterns in that editing a template part should require a dedicated "edit" click. This transitions you into a global context. We can do a much better job of highlighting that context in inspector etc. 314389161-77bfc27c-9646-4db8-8487-c1eb70b691eb.1.mp4The video here is also related and shows highlighting what's editable in inspector. |
@getdave Is my understanding correct that the new "Drilldown" interaction for content-only mode would allow these blocks to maintain their block context while editing? Currently, this context gets detached when editing patterns in isolation. That's really my only concern with changing the template part interaction model is that it could break a few blocks we have that provide context to inner blocks, including template parts. |
@sethrubenstein I'm afraid I'm not sure at this point. I took a look at that PR again yesterday. It's now fairly out of date and I'm not entirely convinced on the drill down idea. I'm going to close it out until we have more time to explore this. I'm currently focused on WP 6.7 release. |
Now that the concepts around #48458 are more solid, we need to ensure interactions are consistent between inserted template parts, synced patterns, and top level groups through the various edit modes.
The text was updated successfully, but these errors were encountered: