17 Comments

  1. Andre
    · Reply

    Is it my imagination that the plugin version of GB is merely a testing ground for what will be in the core?

    As a theme developer, it almost seems like we have to design 3 flavours of a WordPress theme:

    WordPress with the classic editor
    WordPress with the core GB
    WordPress with the core GB + the plugin version

    It also appears that full site editing is coming much faster than many have anticipated.

    Report

    • Justin Tadlock
      · Reply

      Yes, Gutenberg is the testing for what will land in core.

      My approach for theme development would be to code against the latest version of the plugin. Then, do final compat checks against core and the classic editor if you want to support it.

      With full-site editing, you’re safe for a while. From the roadmap I’ve seen, they’re shooting for a basic working version by the end of 2020 within the plugin. I imagine it’ll be sometime in 2021 before it is feature-complete enough to be in core.

      Report

      • Andre
        · Reply

        A good suggestion to design against the plugin.

        However, as a theme dev, I am trying to gauge a lifespan of themes as they are today; how long they will stay relevant as WordPress continues down the path they are going. I’m still thinking about theme shops and marketplaces, in general, as to how long they/we have before themes of today are no longer compatible with WP. More so with end-users who are not really prevalent in the future of WordPress and to know that their theme may not be compatible in the near future.

        2021 is really not that far away, less than a year.

        Report

        • Justin Tadlock
          · Reply

          Definitely. It’s just too early to gauge what theme dev will look like in 2021, but it’s going to make things a bit crazy. I’m thinking that we’ll definitely see a big split between “old” (for lack of a better phrase) and block-based themes. Popular theme companies will likely have to code their themes for both possibilities. Right now, I’m just thinking that will be a lot of duplicated code.

          Report

          • Andre

            Eventually, “old” themes will become obsolete and incompatible. The big question mark is find out when.

            I’ve been exploring the possibility of coding themes for both old and new (block-based) themes. I already code my themes for the classic and the block editor. So, perhaps that means my original flavour list will now look something like this:

            WordPress with the classic editor
            WordPress with the core GB
            WordPress with the core GB + the plugin version
            WordPress with the core GB + Classic editor + Plugin + Block areas

            Report

  2. Bastian
    · Reply

    Is it me or now when hovering over blocks there’s no tooltip or indication of the specific block you are hovering over?

    Report

    • Justin Tadlock
      · Reply

      Hmmm…I actually didn’t notice that until you mentioned it. I am unsure if this was changed in 7.6 or an earlier version. I do have to admit that I think I like it better without the tooltip. It feels a little less noisy in comparison.

      Report

  3. Martin Servk
    · Reply

    The improvement is good, really good. But there’s something that’s hard to understand. All these features is to improve the user experience with Gutenberg. But why don’t they think about developers. If for some reasons a block can’t render itself, an error is shown in browser console and the whole block is lost. You can’t recover it. That’s not the best option to catch an exception. Everybody talk about this way of showing issues, but nobody seems to care about it.

    More than it, the DOM structure in Gutenberg is different from what is rendered on frontend. That’s a problem because as a developer you have to maintain two structures that look the same, and the pixel perfect between the two is hard to.

    Report

  4. DoktorThomas
    · Reply

    Gutenberg 7.6 failed to work on my website hosted at Namecheap. Crashed me every time I tried to post. Deactivated and no problems. ©2020

    Report

  5. Jef
    · Reply

    Try: Create new Post and save it. Type some letters. The “Save” Indicator never turns back to “Saved”, even though the Changes are stored in the Background. Is this a bug or a intended behaviour?

    Report

  6. Cathy Tibbles
    · Reply

    Are there conversations anywhere about best practices for block development in themes?

    But with more and more blocks – and more options for each, wont this impact speed? Isnt it the same bloat we used to criticize in page builders?

    So far, other than custom blocks, and changing default styles, we’ve been removing a lot of options for clients – for easier editing and consistent branding. I’m not sure this is a good idea tho.

    Report

    • Justin Tadlock
      · Reply

      Yes, there is a block-based themes meeting held by the theme review team every other Wednesday at 16:00 UTC. There should be one this week. The info is available in the sidebar on the Make Themes blog. That would be one of the best places to get a feel for and catch up with what is happening.

      Also, be sure to keep up with the block-based themes experiments repo on GitHub. That is where various developers are experimenting on future theme ideas and how they will work within the block system.

      Report

  7. Tina Meeks
    · Reply

    I wonder how the full-site editing experience will compare to other builders such as Elementor, or other page builders.

    Report

    • Mario Bartolini
      · Reply

      Wait and see. From various comments and questions in issues at github here and there it appears that quite some Gutenberg devs never have seen WPBakery Visual Composer or also Elementor in real world usage or even sites with a bit more complex ACF Pro with repeaters and flexible content fields etc. or themes with own templating systems and builders like directory sites with a few thousand users and hundreds of categories, tags, custom taxonomies, which simply overload Gutenberg completely at this point. Will be interesting to see if/when Gutenberg will finally be ready for professional use.

      Report

    • Justin Tadlock
      · Reply

      Tina, while this is totally off-topic, I just wanted to say that I love your website name, Her Life Sparkles. Really cool branding. Everything stands out and draws you in to read more.

      Report

  8. Frank
    · Reply

    I think Gutenberg needs to try to stay lean. Hopefully these enhancements don’t increase page weight if you choose not to use the block.

    Report

Leave a 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: