• Anonymous User

    (@anonymized-15094376)


    People hate change and a major change such as this is inevitably going to divide opinions. I can understand why WordPress is doing this but personally, I am not a fan of page builders or drag-and-drop editors. I like to have the control that a normal text editor provides. But having tested it for a while, I can honestly say there are MUCH worse commercial page builders out there. And as long as it’s possible to revert to the classic editor, I really don’t see what all the fuss is about. At least WordPress is giving us that option (for now at least) and is rolling the new editor out in a controlled manner.

    Edit Jan 2019: downgraded rating to 1*. I tried. I really did. But after persisting for several months, I’ve given up. I find Gutenberg way too fiddly and simply not intuitive. It adds nothing positive to the user experience. So I thought it was just me, after all, I’m not a fan of page builders of any description. But I asked several of my clients to try it out and without exception, they all gave up after an hour or so.

    As far as I’m concerned, the old editor worked. It wasn’t wonderful, but it was simple enough that anyone could use it pretty much from the off. There are much more pressing things in WordPress that need addressing and I really fail to see why a new editor was given such a high priority. This is a huge step backwards for WP IMHO.

    • This topic was modified 6 years, 6 months ago by Andrew Nevins.
    • This topic was modified 6 years, 1 month ago by Anonymous User.
    • This topic was modified 6 years, 1 month ago by Anonymous User.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi @woopee,

    Thanks for your review and testing, we really appreciate it and we keep working on improving with every new version released almost every week.

    Could I dig a little more into what you see it can be improved of the current Gutenberg experience? Thanks in advance!

    Thread Starter Anonymous User

    (@anonymized-15094376)

    Hi @_dorsvenabili

    Sorry for the delayed response. The notification email had gone into my spam!

    I think most of my “issues” are down to the fact that, as a coder, I prefer to see code. As I mentioned, I’ve never been a fan of page builders and there are some pretty awful commercial ones out there – slow, bloated hideous things.

    My experience of Gutenberg so far is, I have to say, largely positive – as far as page builders go. It is relatively simple, well laid out (see comment below) and feels lightweight. I also like the way it is easy to add CSS class to elements if needed.

    I am testing Gutenberg on a clean WP4.9.8 installation (on my local machine) with no plugins installed and I’m using the Twenty Seventeen theme (v1.7). My aim was to reproduce a page I’d previously created in the classic editor.

    On the negative side, I get a couple of recurring errors. When updating a post, I get an “Updating failed” error. When loading a page, I get a “Unhandled promise rejection” error in the browser console, relating to “rest_cookie_invalid_nonce” in wp-content/plugins/Gutenberg/build/index.js.

    The preview doesn’t for me work either (“Please wait.. Generating preview.” – for ever).

    Some other minor thoughts:

    • The “Add Block” button seems a bit lost on the menu bar. I think it needs to be more prominent and possibly located to the right with the other menu items.
    • It’s not so easy to delete content. In the classic editor, you can just select a whole load of content with the mouse, then press delete. This isn’t possible (as far as I can tell) in Gutenberg.

    Other than that, I think it’s very promising . . . as far as page builders go. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘It could be worse . . .but not much’ is closed to new replies.