Size Change: +1.2 kB (0%)

Total Size: 1.42 MB

_{compressed-size-action}

This PR is not ready yet but it's ready to get thoughts and designs.

Right now, it's enable for all classic themes by default, we might want to introduce a theme support flag for it to make it opt-in.

I think that would be necessary in many situations... and it should also be filterable so users can install a plugin to enable it on their old, not-updated theme. See PR #30465 for a suggestion

Thinking about the theme-support thing some more, perhaps it should be opt-out instead of opt-in? 🤔
IMO this is going to be one of the things that will get huge adoption by classic-theme users... It will allow them to use their theme for their site, while at the same time being able to build a completely custom frontpage if they so desire.
If we make it opt-in we'll be excluding a large portion of the userbase, but it is the "safer" choice because people just won't see the feature.
If we make it opt-out, then we are more inline with what we want the future of WP to be. If a theme doesn't want FSE for some reason, then they can explicitly define that.

I believe opt-out would make more sense... (updated the PR on #30465 to reflect that)

What an intriguing PR!

I am using the Twenty Twenty One theme.
I downloaded a special version of the Gutenberg plugin (Going to Checks -> clicked Gutenberg build in left sidebar -> downloaded Gutenberg plugin. Extracted and compressed it again and uploaded the special GB plugin. Additional instructions here: https://youtu.be/eJhgUjrTSF0).

Then followed the instructions added by Riad.
Create a page. I saved it as a draft. I did not see a "Create custom template" link in the sidebar. How do I proceed?

@paaljoachim That was my bad, in 6067b42 the line defining theme-support was not renamed. I pushed a fix here just now so once the build finishes you'll be able to test it 👍
If you don't want to wait for the build, you could add in your functions.php file add_theme_support( 'block-templates' );

Great! In addition to using the special Gutenberg plugin mentioned above I then added the code snippet to the functions file add_theme_support( 'block-templates' );

My test.

1.I would suggest a developer create a PR for moving the page/post title to the top bar. It would also be one of the many connections with Full Site Editing. #27093

As having the title in the top bar. Be it "Page content: Page title", "Content: Page title" or just the "Page title".
Would right away create a connection with using templates.

For this PR where I test page templates.
One should then see the page title in the top bar. Click the Create custom template" Then in the top bar see
Template: Page title. Having the Template: Page title in the top bar gives a nice signal to the user where they are.
Here is a mockup where I added the "Custom template: Test template" to the top bar and "Custom template: Document" to the bottom breadcrumbs. Having multiple ways for the user to see where they are. (In addition to seeing the word template and template name in the sidebar settings.)

2.Save or do not save is the question. Save or discard a save.
User clicks "Apply" and notices the prechecked Custom Template.

What if the user decides not to save?
They see this:

A greyed out blue button. User it not able to move onward, and meets a dead end.
An alternative suggestion would be as seen in this comment:
#29577 (comment)

Which basically does this:

The user makes a selection if they want or do not want to save the custom template. Perhaps they just wanted to see what it is without saving. If they decide not to save they become stuck in the custom template. Having no obvious way on how to get back to the regular page. Perhaps they click the Page tab and look at Status & visibility to see if there is a bridge back to the page content in the same place they clicked to "Create a custom template" but there is none. So the user is forced to save.

Going back to the page content. It looks like this...

User might think. Why am I not seeing the template content in my page?
As it should show up similar to how a Reusable block is seen. Perhaps even use the click through method being explored here: #30156 (Actually James @jameskoster has continued to explore the click through method.) As the user would initially click the template and select the parent container. Then click into it and make changes. Then Save the change in some way. Either with a Save button in the toolbar as suggested by @critterverse Channing here: #30357 or having a save button in the sidebar settings.

Bottom line is that being able to add a page template is a very nice feature! Along the way before this PR is merged other PR's can be created making specific UI (top bar page title) and UX (being able to easily discard a save) making the flow easier for the general user and also for us. Thanks!