10 Comments

  1. Rhys C

    “insert wptavern gutenberg hate comment here”

    But in all seriousness I think this is a huge step forward for WP and the team is doing a great job.

    Report

    • Ashleen Lecats

      I don’t hate Gutenberg; WordPress and I are friends and GB isn’t going anywhere so I want the best for it.

      That said, I am looking forward to seeing things become more cohesive; I remember being concerned about what a hot mess it all seemed like and then it got so much better. It’s not my kind of rodeo, so I don’t use it, but when I see thoughts like this:

      Gutenberg accessibility contributor Andrea Fercia encouraged contributors to address accessibility before creating visual mockups by designing the information architecture first.

      it makes me think things are in good hands. If you can’t get from A to Z immediately, a thoughtful and iterative process that attempts to transition people without too much confusion sounds like a nice change of pace!

      It’s actually weird. Menu doesn’t look like Widgets doesn’t look like Customizer, but it’s so familiar that I don’t even question it. The opposite; the idea of everything looking like blocks seems confusing at first. But I use a page builder where everything’s done the same way and handle it fine. So I’ll be fine =)

      Report

  2. David Decker

    I am curious how the phase 2 (beta) testing will be in general — from what I read/ heard, they want to use the Gutenberg *plugin* again for that.

    This seems rather strange to me: users, and a lot of devs/ agencies already have voted with their feet that they don’t want it and then should install it again. Crazy thought.

    Apart from that I really hope the Widget Block for regular widgets that are not transformed into a block will be really usable.

    Additionally, I am still waiting on abstraction “things” to happen for people to migrate regular widgets from their plugins into usable blocks. I think there should be something like that. I mean that in an EASY, really easy to follow way.

    Report

  3. mssbee

    This update has a lot to understand and potentially like. What about sites that have chosen to stick with the classic editor, how would widgets as blocks work then? Would the classic widget work for those sites?

    Report

  4. Stephen Vaughan

    Putting widgets into the customiser where you can live preview how they will look and function does seem sensible. I always found the current mechanism of configuring widgets a bit dusconnected from what appears on the front end.

    Report

  5. Roger

    Maybe the best thing is to keep the existing layout, but just allow the use of all blocks within the accordion content areas?

    The most logical approach would be to add Gutenberg to the preview area, but that would mean recoding it to work on the frontend? Or could the the blocks be added like widgets and the inline editing be in the preview area?

    Report

  6. zieltraum (Holger Theymann)

    It is an interesting journey, we’re on with WP and Gutenberg.

    Not being best friends with Gutenberg right now, i still clearly see the innovative potential and i am looking forward to what it might become.

    Right now i still prefer BeaverBuilder… but well… that is not for free… and for pages, where less design is ok… Gutenberg might do the job.

    Report

  7. Akshya Nagar

    Gutenberg is quite a good editor. But, still, I don’t know, why I prefer classic editor. After this update, I will definitely try it again.

    Report

  8. Marcus Hiles

    Reading

    Gutenberg phase 2

    in the headline made my heart skip a beat.

    Report

  9. David

    Honestly, besides accessibility (which is a real problem), they should focus on fix those annoying issues Gutenberg has instead of moving into a phase 2. Better to successfully close phase 1 and then move ahead than open more and more issues.

    Report

Comments are closed.

%d bloggers like this: