Site Editing Infrastructure and UI: Part 3

[youknowriad]

In #26355 we've introduced an initial version for the template editor mode in the post editor. This highlighted a few issues in the design/flows of that feature. The current issue is an overview tracking the progress for all oft these follow-ups:

Blank Canvas Template

• Allow creating custom block templates in classic themes Allow creating custom block templates in classic themes #30438
• Better distinguish between the content editor and the template editor. The users should be able to quickly tell which mode they are currently working with. Site Editing: It is not clear at-a-glance whether one is editing a template or an item of content #27849

Interface

• Allow deleting new custom block templates, and reverting customized block templates in the template editor It should be possible to delete new custom block templates, and revert customised block templates in the template editor #31076
• View the template while editing the post Post editor: Provide a way to view the template while editing a post #27847
• Design UX patterns for blocks based on context (content editing vs template editing) that enable users to flow between content editing and template editing directly on the canvas. Site Editing: Restrict block editing capabilities based on editing context #27848
• Site Editing: Explore a pattern for template part editing that is consistent in both content and template editing contexts #27852
• Allow selecting custom page templates. Add support for custom templates in FSE themes #27778
• Find a visual way to list the available page templates (actually preview the templates and maybe show them in a starting modal). Site Editing: Visual template selection #27850, Refine template flows in the post editor #31591
• Give the user the possibility to save the changes to a template specific to the current post or a custom template that can be used in other posts too. Site Editing: Allow template edits to be saved as a new template #27851
• Add a welcome guide for the template mode. Site / Template editor welcome guide #29031
• Colorise template parts and reusable blocks in the UI Colorise template parts and reusable blocks in the UI #32163
• Mosaic View of Theme Templates. Mosaic View of Theme Templates #20477
• Bug: Template part click-through Click-through pattern not behaving as expected for Template Parts #35079
• Refine the Site Editor loading state #35503

Infrastructure

• Allow using post meta values as "sources" for some of the blocks used in the template.
• Allow themes to opt-in/out of the "Create new template" flow.
• Support dynamic values in block-based templates. Block Based Themes: Dynamic values in static HTML theme files #20966 (Try) Template Loader: Allow PHP in block templates and parts #25316

[skorasaurus]

One more suggestion to add: While editing a template within the post editor, I went to the code editor mode, and the code editor mode returned the content of the post, not the template's content (what I expected); this is a result of #22528

[youknowriad]

#30438 is now merged so classic themes can use blocks to build custom templates for pages and all CPTs that support Page templates now.

[priethor]

Added Allow themes to opt-in/out of the "Create new template" flow to the list.

[youknowriad]

Added Allow themes to opt-in/out of the "Create new template" flow to the list.

That's already possible with the block-templates support flag. you can do remove_theme_support( 'block-templates' );

[carolinan]

Short term, are the template and template part menus under Appearance going to be in 5.8?

If not:

• How can user created templates be deleted?
• Editing templates is possible, but you would first have to find a page or post that uses that template, or create a new page or post just to access that template.
• How can users edit templates that are not post or pages, such as search, archive, and 404?

If kept:
The editing views in the appearance>edit templates and block editor>edit template are not the same.
What is the intention with these separate views?

[youknowriad]

I think these screens are not meant to be shipped at all. So yeah if the template editor makes it to 5.8, we need at least a "delete" template somewhere in the template mode or the template panel.

[jameskoster]

How can users edit templates that are not post or pages, such as search, archive, and 404?

Assuming dedicated template management (IE Appearance > Templates) doesn't ship in 5.8, it won't be possible to create these templates in the UI. So I think it's fair to assume there will not be an expectation of edit-ability either.

we need at least a "delete" template somewhere in the template mode or the template panel

There is a revert affordance for customised block theme templates in the site editor. We can use that same design for deletion in the template editor. I'll make an issue.

[carolinan]

it won't be possible to create these templates in the UI
You meant in the appearance > templates UI? Or not create templates at all via any sort of UI 😕

[jameskoster]

Not create the templates you mentioned specifically: search, archive, 404, etc.

[priethor]

we need at least a "delete" template somewhere in the template mode or the template panel.

Added this to the list based on the recently created #31076

[adamziel]

Is there any feature here that could still land until Wednesday next week to be included in WordPress 6.0 release? To increase visibility, we can add it to the WordPress Editor 6.0 project board.

[mtias]

Time for a new reset: #41241