-
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
Align template part edit flows? #65096
Comments
My vote would be to revert the decision to have template parts be selectable in the "template-locked" editing mode. That should also resolve this |
To me the page editor and template editor are aimed at different groups. The former is primarily for users building their website and the latter is primarily for theme authors. If anything I'd like to see even further distinction between these two editors. For example the page editor could be based around inserting patterns / zoomed out mode. |
This would make quickly editing the header / footer more convoluted which feels like a pretty big usability trade-off to me.
That is a good observation, but I think there are a few templates that feel more like virtual pages, and likely fit the mental model for page editing. Examples being; Blog Home, Front Page, Taxonomy archives (post category archives etc.). Related: there is active discussion around surfacing the Homepage (when set to display latest posts) in the Pages list in #60772. For me the benefit in aligning around the page-edit experience is two-fold:
Zoomed-out feels useful in both contexts. |
Closing this as it is likely superseded by #65698. |
Currently the experience around editing template parts differs based on whether you're editing a page or a template.
Page editing
When editing a page, template parts can be selected but not edited until you click 'Edit' in the block toolbar, or double-click:
page.mp4
Template editing
When editing a template it's possible to select and directly manipulate blocks inside template parts:
template.mp4
I'm not sure that the differences are warranted, and would lean towards aligning around the page editing experience.
cc @WordPress/gutenberg-design
The text was updated successfully, but these errors were encountered: