1. Emmanuel Ang


    Can someone give light to my confusion? Is the “Gutenberg plugin” is different from the “Gutenberg” that you’re talking about here? I’ve tried installing the Twenty Twenty-One theme and the “Gutenberg plugin” is not installed by default. However, the “Gutenberg” blocks are present in the said theme.


    • Justin Tadlock

      Yes, Gutenberg is a plugin. It is the ongoing project behind the block system where users can test the features that will eventually land in WordPress.

      What you currently see in WordPress, regardless of your theme, matches an earlier version of what’s in Gutenberg. The last few versions of Gutenberg have new features that you can test and use that are not in WordPress.


  2. Riad Benguella

    Hi Justin, thanks for the posts. I wanted to add some clarifications around the page templates feature.

    While this is a nice development, traditional page templates may not make much sense in the block theming paradigm. There is no way to change the visual output of the page in the editor based on the selected template

    The page templates that were introduced in Gutenberg 9.7 have nothing traditional aside the fact that they’re being applied with the same existing UI. Actually, you can m make changes and see the visual output in the editor based on the selected template. You can do so by relying on the “template mode” that was introduced in Gutenberg 9.6.

    So they are already what you suggest they should be: Block Layouts the user can choose from when starting a page/post but at the “template” level and not the “content” level.

    This is not reflected in the UI clearly yet but the work on the interface often takes some time and iterations.

    Thanks a lot for all these updates.


    • Justin Tadlock

      Thanks for chiming in. I see that you can edit them via template-switching mode now. Yeah, the UI will definitely need some work. :)

      My point about doing it similar to CPT templates is that some theme authors would like the ability to create a specific content-level layout for the page template. For example, they might want to create a front page template that had all the blocks in place. Then, the user sees that in the post content canvas itself without having to switch over to template editing. Template-locking options would be nice for this too.

      In talks with various theme authors and agencies in the past couple of years, I think this is what many of them were imagining the block system would let them do with page templates. And, maybe as we continue merging interfaces, this is what it will ultimately look like.

      As block patterns have emerged, I see those as perhaps an alternative (better?) solution for that, just without the ability to lock the blocks in place.


  3. Gary Taylor

    Unfortunately, there are no FSE templates yet.

    In your chosen WordPress Admin area, go into Themes, Add New, open the Feature Filter and select Full Site Editing. See how many themes get returned…

    I know the themes are out there because they’re highlighted by the Tavern (thankfully!) but until they make their way into the themes repository do they really exist?


    • Justin Tadlock

      The Q theme and Block-Based Bosco are currently in the WordPress.org theme directory. Armando, which I covered recently, is still awaiting review, but it’s in line for the directory.

      It’s not much, but it’s something. It’d also help if this Meta ticket was addressed for allowing FSE themes to be uploaded without special workarounds.


      • Gary Taylor

        Hopefully the Feature Filter will be updated (or the themes updated, whichever is at fault) so that we can give FSE a better test. Not everyone visits WP Tavern, so even if they’d heard of FSE and wanted to give it a go wouldn’t have found any themes to test.

        Thank you also for the name-check in the TT1 Blocks story ;-)


        • Justin Tadlock

          I chatted with the Themes Team about what was going on there. It was the theme authors who hadn’t added the full-site-editing tag. They’ve been asked to in their respective Trac tickets. Q, at least at last check, has the tag in its GitHub repo but hasn’t been updated on .ORG yet.

          Thanks for bringing this up though. Before your comment, I hadn’t realized the filter wasn’t showing any themes.


  4. Ricardo

    I apologize for some nonsense terms I may use, I’m a Designer, not an advanced developer, but I really want to contribute in some way.

    I agree, Page Templates as used before in the page editor seem redundant with Patterns coming in.
    But I think keeping the Template Hierarchy is fundamental for building dynamic Websites/Apps/PWAs.

    I also think WP can have two kind of users:
    A) the ones who want to build single pages with blocks.
    B) the ones who want to fill fields to feed a Database – that would feed the template-pages & blocks.

    A) could be divided in Normal and Advanced users. See structure below..

    Thinking on a data structure, I believe some kind of CPT and Custom Fields are still essential to build Complex Queries. And as data gains more value it’s important to control it. Of course, with blocks the way it’s organized it’s different but I think the a good approach could be:

    |__ Dashboard
    |__ NEW
    |     |__ Page (page-template.php) – Pattern X, Y, etc
    |     |__ Product (product-template)
    |     |__ Post (etc)
    |     |__ Etc..
    |  EDIT Templates/Patterns (Advanced User level)
    |     |
    |     |       |__ Pattern X (Header A + Sponsor A + Etc)
    |     |       |__ Pattern Y
    |     |       |__ Etc.
    |     |__ Product
    |     |       |__ Pattern X
    |     |       |__ Pattern Y
    |     |__ Post
    |     |__ Etc..
    |     |__ Header A (header-template-a.php)
    |     |__ Header B (header-template-b.php)  
    |     |__ Sponsor A (sponsor-template-a.php)
    |__ Media
    |__ Etc..

    Where “Templates” option would only show in Dev or Advanced user level, controlled on WP installation and after in some kind of on/off switch.

    Blocks themselves should be simple templates, dynamic = PHP (dynamic HTML).
    HTML isn’t more user friendly than PHP – a user will never touch code anyway. Why not having PHP doing the heavy stuff – fetching, parsing, embedding, using custom-fields, etc..?

    PHP is so strong now. It had its down momentum with the appearance of new systems and languages but it’s being updated more than ever, it’s quicker, safer and it is a super SS language. With the evolution of CDN’s, Cache solutions (functions?), etc.
    Isn’t it a strong option to keep it alive?!

    I would prefer go 1 step back now then 2 or 3 later.  

    I hope it wasn’t to confusing or absurd.


Comments are closed.

%d bloggers like this: