1. Ant Ekşiler

    When will Gutenberg 7.0 be included with WordPress updates?


  2. Damien Carbery

    I used placeholders (~TITLE~ and ~TAGLINE~) to insert the post title and excerpt into a reusable block – https://www.damiencarbery.com/2019/11/filter-gutenburg-block-before-display/


  3. Caroline

    Wouldn’t call navigation block really “stable” with weird bugs like “can’t delete added items” #18866 or “does not show categories” #18859 and some more.. :-(


    • Riad Benguella

      Hi Caroline,

      This is a great observation and my wording on the release post can be misleading.

      It should be noted that features in Gutenberg go through three main phases:

      1- Experimental: For early adopters and developers, they can enable the feature by going to the “experiments” page of Gutenberg.
      2- Beta: Plugin users (beta testers) are invited to test these features extensively and provide feedback. Iterations and fixes will be applied based on that feedback.
      3- Stable: That’s when the plugin gets merged into WordPress Core. It usually happens with WordPress major releases.

      Gutenberg 7.0 Moves the Navigation block out of the experimental phase into the beta/testing phase where we invite all plugin users to test and provide feedback. It is still an early version that will receive a lot of improvements and bug fixes.


  4. Andre

    With these continuing changes of Gutenberg (block editor) which is really becoming a page/builder, has anyone speculated what is going to happen with marketplaces like Theme Forest? We know themes in general are going to be obsolete in the near future.


    • richard Ginn

      All 20 plus WordPress pagebuilder plugins can easily be rendered useless the way Gutenberg is progressing in the terms of functionality.

      I do not see themes being useless unless they are full Gutenberg compatible.

      Still possibly a year or two off.


      • ts

        “We know themes in general are going to be obsolete in the near future.”

        hey, would you care to elaborate a little on this?

        My take is that the main question is what kind of page/site is being developed and what kind of complexity with respect to design and data-display is taking place at which part of development using which technologies.

        For a mainly data-driven site, let’s say an event calendar, the additional features of Gutenberg over tiny_mce are mostly useless in my opinion, as the important content of the page is ideally saved in reusable post-type data-blocks and displayed according to list templates/search-logic. Adding page templating to Gutenberg merely changes the way the site’s frame is developed or how a loop is integrated in a page.

        (sidenote: I think there are still a couple of conceptual aspects unresolved with respect to now having two basic units for holding data in wordpress (and how they’re saved): pages/posts (data in various types, metadata) and now blocks (data serialized in one field).)

        For many corporate pages, added flexibility in terms of design is something to be avoided not to be offered to editors/authors. Here, again, there’s no added benefit derived from a complex templating engine available on every page, quite the opposite: removing blocks and limiting styling options will become the more important aspect of customizing gutenberg.

        That said, for a single, landing-page-style page, the added flexibility does make sense, because something like that takes tooo long and is too complex for classic template/coding to be economically viable.

        So, basically, I think it’s the underlying requirements of a page that will determine the most efficient way of developing and displaying data. Page builders/future Gutenberg are nice for front- and landing-pages, but usually much less important for second-level content pages, corporate pages with required design, that strive for editing simplicity, and data driven pages.

        Changing the way the templating is done doesn’t obliviate the need for it, it does, however, introduce a phase of uncertainty for certain clients who could be insecure if they should hire someone for expertise or go it alone, since, now, the technology allows them to (like page builders in general).



    • Samrat Roy

      That’s a good thought! I believe the pace at which Gutenberg is developing is worth noting, yet it has a long way to go still.

      Not sure, If you’d want to have a look at a detailed take : https://epitrove.com/gutenberg-vs-wordpress-page-builders/


  5. Gaurav Tiwari

    Is nofollow in the links coming? I am waiting for a long time now and switching to HTML view from visual editing is a real pain.


  6. Ramzan

    all the features of this is awesome


  7. Aris Kuckovic

    Looking good for the future of Gutenberg :)
    I have kept an eye on it for 2 years now – and I must say, they’re improving all the time – but there’s a long way still, imo.

    Best regards


  8. Guido

    Start using the new editor two weeks ago and must say I kind of like it. There are some issues but I know it’s still in very active development. Will check the new GB out tonight..


  9. Anh Tran

    This is awesome! These features are very similar to connections in Beaver Themer and dynamic tags in Elementor, which allows developer to connect settings (from posts like post title, post content, or from other part of the website) into a module (block/widget). And that opens a lot of possibility with the content building.

    I’m looking forward to this and more similar great things added to Gutenberg.


  10. Samrat Roy

    I would really want to understand the community’s view on the future of Gutenberg? After WP 5.3, there were about 5 updates released to 7.0? This rate speaks about how serious their vision is at Automattic with Gutenberg and it’s very impressive. But, the point is that will it be able to keep up with the intuitive and ingenious advancements that other page builders are bringing into the market?


  11. Tim

    Really excited to see when we will be able to set a block template with placeholders for the default post headers. Especially if you could assign different post formats to specific saved block layouts with featured imagery, etc in them. We’ve been using reusable blocks on our client sites a ton.

    I want to see a block template section that you can assign for headers/footers. It can’t be that far away at this point. That and post header/footers are the only things that we still use PHP templates for at this point, and it’d be a whole lot more flexible if we could use Gutenberg for universal site elements too.


  12. Helena Orstem

    Start using the new editor two weeks ago and must say I kind of like it. There are some issues but I know it’s still in very active development. Will check the new GB out tonight..


Comments are closed.

%d bloggers like this: