8 Comments

  1. Johannes
    · Reply

    I don’t really understand what the Gutenberg teams reasoning behind the whole “full site editing” is. Traditionally themes have worked by giving a template to the user to fill out with content. This was done by separating the content from the presentation, the user handles the content and the theme handles the presentation. This ensures that the user can’t do anything stupid and mess up the site.

    I checked the example theme and it seems like it’s a bunch of Gutenberg blocks in a HTML file that the user can edit however they want using the Gutenberg editor. I can’t get the theme working properly on my computer but presumedly these templates will be stored in the database to preserve the changes. This means that the user is able to do whatever they want to mess up the design. Want to delete the title from all blog posts? Delete the site logo? No problem.

    Rather than giving the user the possibility to “fill in the blanks” the full site editor seems to try to replicate something like Dreamweaver in the worst possible way, giving free rein to modify the entire site however they see fit.

    I have no idea what the Gutenberg team’s vision is in the end. What’s the point of a theme if you can do the same by cobbling a bunch of Gutenberg blocks together? Is it just a bunch of CSS files that maybe change the colours and fonts a bit? And some example templates the user can mess around with?

    I get that something like this will work for the casual user to compete with something like Squarespace and Vix but for custom client projects the whole thing is completely unnecessary.

    I think Gutenberg, Customizer and “block areas” that replace widgets are good ideas because the theme author ultimately controls how the content appears and they give content editors possibility to edit the site without breaking anything.

    Composing the entire site out of Gutenberg blocks seems like a crazy idea to me. I hope the “normal” PHP based themes are not going anywhere soon.

    Report

    • Justin Tadlock
      · Reply

      We’re a long way from any sort of finalization on this. And, I’d love to see more about the overall vision from the Gutenberg team. Right now, a lot of this is speculation and experimentation. The following is how I envision the system working based on what we currently know.

      The role of themes will be reduced and will cover three primary areas:

      • Themes will offer unique styles for block output. This will be the primary purpose of a theme — styling content.
      • Themes may optionally register custom block styles to offer extras to users.
      • Themes will set the default output of templates.

      The last point, which is what this post covers, is kind of a big question mark right now in terms of how it will work. The idea seems to center on templates simply being a collection of blocks. That’s not much different than the original purpose of templates. HTML is essentially blocks. What the block system does is standardize the code so that it can be interpreted by WordPress and also shared between themes.

      Where themes really come into play here is they give the user a starting point. This is where the theme designer presents their vision. Many users will simply use the theme and not change anything just like they do today (WordPress currently has a built-in theme editor). Some users will want to change minor things, such as moving the post category to output below the post title instead of after the post. Yet, other users like the general color scheme and block styles of a theme but want to change the overall layout and other major elements. Because theme templates are all built on this standardized block system, end-users can move these parts around without breaking things.

      The big change essentially comes down to themes being built in a standardized language (blocks) and end-users having the ability to make changes to templates without editing code.

      I’m still on the fence about whether this is a better direction than simply allowing themes to register custom block areas and have a little more control.

      Report

    • Bastian
      · Reply

      Rather than giving the user the possibility to “fill in the blanks” the full site editor seems to try to replicate something like Dreamweaver in the worst possible way, giving free rein to modify the entire site however they see fit.

      It’s GeoCities design all over again

      Report

  2. Jakub Mikita
    · Reply

    Taking into consideration that a simple theme gets reviewed and accepted in about 4-6 months, it’s rather optimistic that we’ll see first Gutenberg editable theme in the repository in 2 years ;)

    Report

    • Justin Tadlock
      · Reply

      That’s one reason the theme review team should focus on block-based themes this year. From my understanding, the team leads are okay with these types of themes being submitted before full-site editing lands in core WordPress. Those theme authors who get ahead may already have themes available in the directory by then.

      Report

  3. Paul Davidson
    · Reply

    Functionality from the Beaver Builder team’s exceptionally powerful Themer product comes to mind.

    With Themer, the entire header, footer, or a “part” area can be built and customized in admin vs. PHP files.

    Filters can be applied to use alternate parts on certain pages, replacing the need to add custom PHP files in the WP template hierarchy. Unique and editable page templates can be set up for posts, archives, etc. i.e. single post pages could use a different header than pages with a secondary category navigation.

    Very powerful stuff.

    I like the comment about how a theme can provide a default view, which an administrator could add to or customize as needed.

    Report

  4. Ray Peacock
    · Reply

    I may have missed it, but is there any significant article that compares the loading time of a WordPress site with a common theme like Twenty Nineteen with and without Gutenberg? Does Gutenberg speed up loading or slow it down?

    Could make a difference.

    Report

Leave a Reply to Ray Peacock Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: