9 Comments

  1. Matt Scheurich

    Now things are getting interesting!

    Report

  2. Matt

    Even at this stage, I still want to see this Edit Page Replacement scaled down in scope to a just an Editor replacement and for Posts only. That’s the only place it belongs for now IMO. Tackle Pages, CPTs and replacing the entire edit page later. The plan seems to still be, slap a Editor label on it anyway even if that’s disingenuous to the WP community.

    The blog post area really needs what Gutenberg provides and it’s also a great place to start the transition to the future of WP. If the project scope changed to this, Gutenberg might finally be perceived (at least by me) as a welcome improvement rather than an unwanted menace. With a little less ambition and more pragmatism the project could be successful instead a disaster.

    Report

    • Alec

      Yes, getting just the Editor right to start would be a good way to create achievable goals and to ensure continuity in the WordPress user/publisher experience. When the Editor is mastered, additional goals will present themselves. Well said.

      Report

  3. Johnny

    Some ideas for Gutenberg:
    https://oxygenapp.com/

    Report

    • Matt

      @Johnny – Really? (shudder) – If Gutenberg ever becomes something like Oxygen, I may weep openly. I like Gutenberg how it is currently.

      The current early UI / UX of Gutenberg and the WP Customizer while limited are better. Before you ask – Yes, I have (unfortunately) actually used Oxygen itself and recently too. It still sucks the air out of the room IMO. While none of these tools are fully baked yet, Oxygen has the furthest to go being WP User Community friendly.

      It’s like the design for Oxygen was inspired by some old Adobe Photoshop version and implemented worse. Adobe’s UI designs are often terrible to begin with (a sentiment shared by many better at design than myself) so using it as model for anything is likely ill advised from the start.

      Report

  4. James

    Anyone here use Beaver Builder or other visual builders? How do you think this will affect those when this becomes part of mainstream WordPress?

    Report

  5. Marcus Tibesar

    Hmmm. I could not find the Feedback link in the plugin’s sidebar menu.

    So my comments are here:

    My First Gutenberg Article

    Report

  6. Greg Schoppe

    oh great… they’re still touting raw, editable html as if it’s “structured data”.

    so, when the html needs to be updated to meet evolving standards or different design choices in a redesign, it means modifying every post everywhere, and because these blocks can be modified as raw HTML, any automation created to do so is likely to get hung up on “modded” blocks.

    Data Structure and HTML output should never be combined. The result is a mess that fails to understand that the finer points of output syntax will vary based on context.

    Imagine trying to render an HTML email template from a Gutenberg post, and you’ll understand the nightmare this storage method leads to. On Github, they’re are arguments as to whether column blocks should be based in flex or in row/column markup. If you want to make a compatible email, the answer is still html tables. Maybe they should use that for columns in every context, to be compatible?

    but, despite all logical criticism, the ship of feceus sails on into the maelstrom.

    Report

Comments are closed.

%d bloggers like this: