Support » Plugin: Gutenberg » Stop Gutenberg !

  • Sabrina

    (@monlisseurvapeur)


    what the **** is this *** update ? This is not Wix! WordPress is made to create professional sites for developers, not crappy sites for beginners with anti ergonomic blocks as possible!

    • This topic was modified 1 year, 4 months ago by Andrew Nevins.
    • This topic was modified 1 year, 4 months ago by Andrew Nevins.
    • This topic was modified 1 year, 4 months ago by Andrew Nevins. Reason: Language
Viewing 7 replies - 1 through 7 (of 7 total)
  • Sorry to hear your first reaction isn’t good!

    Would it be possible to get a bit more information about why you called the blocks anti ergonomic?

    Sabrina

    (@monlisseurvapeur)

    this interface is clearly not made for developers or those who know how to code a minimum, but only for newbies who know absolutely nothing about it and are happy to have fun moving blocks with a more graphical interface.

    The problem is that content publishing loses a lot of interest for an insider. For example, switching between the code editor and the visual editor takes more time and is much less clear.

    We lose the essential with this interface. The strength of WordPress at its core lies in its simplicity and streamlined interface for me, beyond functionality and community.

    • This reply was modified 1 year, 4 months ago by Sabrina.

    “only for newbies who know absolutely nothing about it and are happy to have fun moving blocks” LOL

    @designsimply

    Because nothing is in front of you! Here’s one example of so many:

    Convert a paragraph block to html. Then try to delete the text and the leftover html <p></p> with the delete key. You can’t. The <p></p> comes back after you click elsewhere.
    Something so simple now requires clicking 3 dots to start the deletion. Here’s the kicker…
    Those 3 dots aren’t even there when you hover over that same block. You have know to click inside of the block to even see a 3 dot menu, then click the 3 dot menu, click “remove block”.
    Try explaining this to clients who haven’t used WordPress.

    User Testing is a great website that could have been used before this.
    “Don’t make me think” is a great book that should have been read before this.

    People aren’t leaving bad reviews for the sake of leaving bad reviews.

    Instead of asking what’s wrong with the new editor, ask what was wrong with the old editor, now that you see how much everyone misses it.

    Thank you for the additional information. It’s interesting about the code editor because there is some thinking around the idea that it’s nice for developers, not just newbies, to have a writing tool focused on writing as well. I see that you do not agree, and that’s okay and I’m glad to have a conversation about it so I can understand better.

    In case it’s helpful to you for now, there is a keyboard shortcut to switch back and forth between the code editor and the visual editor which is Cmd+Opt+Shift+M or Ctrl+Alt+Shift+M. There is also a request to add a keyboard shortcut for the same interaction per block (the “Edit as HTML” link).

    It’s also really good to have new users be able to use an editor easily. I feel this should absolutely be a goal, but not the only goal, in addition to serving developers and there’s a balance to make there. It may not be perfect, and it may turn out that not everyone agrees with the first presentation, but it will be iterated too.

    Something so simple now requires clicking 3 dots to start the deletion.

    While clicking the dots to remove a block is one option, it isn’t the only one. To delete a paragraph, you can also simply press the backspace or delete key exactly the same way you would in the classic editor. In your case, the blocks may be getting a bit in your way and I would recommend that you give Fullscreen Mode a try if you’re willing to! You can find it in the More menu at top right.

    Instead of asking what’s wrong with the new editor, ask what was wrong with the old editor, now that you see how much everyone misses it.

    I love this statement! User testing was done, and is ongoing, for both editors. There is a ton of frustration with the old editor, and one of my goals is to help uncover the reasons about why and try to work towards something better overall. Right now, there is a blend of both editors with the classic block being available in the new editor.

    @designsimply You seem like a sweet person and I’m sorry you have to take the brunt of this, but (haha)…..

    You posted above:

    It’s interesting about the code editor because there is some thinking around the idea that it’s nice for developers

    Yet in a the past post “Neither intuitive nor ergonomic.” you commented:

    One of the main goals for Gutenberg is to work better for users without computer skills such as knowing how to code HTML.

    WordPress’ popularity is with developers AND newbies already. It that it was as easy or as technical as you wanted it to be.

    There is a ton of frustration with the old editor

    Really? Where were they last? WordPress being 32% of the whole Internet? The editor being the primary thing people use. If it was so frustrating, how did it hit that 32%? There are plenty of alternative Open Source projects out there yet people and developers flocked to WP over the years.
    Also, the classic editor plugin already has over 700k installs.

    Keyboard Shortcuts
    You’ve also responded to people about keyboard shortcuts. Do you know the % of people who prefer keyboard shortcuts over the mouse? It’s not even close.
    Remove the back button off a browser and you’ll see a revolt. People don’t want to use the back key to go back a page in their browser. Most of us have a mouse and would like to use it without going through hoops to achieve what we used to be with one click.
    The main problem with keyboard shortcuts is that they are not visible. The old editor had both. Now you have to hover correctly, then click the right area.

    If it were that intuitive, why do we still have buttons for the WYSIWYG in the comment box I’m writing right now? Why not get rid of the “b”, the “i”, the “link”, and the rest? Why not just make keyboard shortcuts?

    People are busy writing and coding, now we have to forget what we’re doing and think about the editor, or remember keyboard shortcuts (which beside copy, cut and past, I never use).

    To delete a paragraph, you can also simply press the backspace or delete key exactly the same way you would in the classic editor.

    You didn’t read my post. When you only have <p></p> showing in the text html (nothing in between as it’s been deleted). You can’t simply use the backspace to delete it along with the block. It won’t. You have to switch back to visual, then delete, or go through the steps I’ve outlined above.

    User testing was done, and is ongoing, for both editors.

    So why do you still need examples of why people don’t like it? WordPress should have already have known they’d get this response and what the issues were if the proper Usability testing was done.
    This is your testing right now.

    I hope this isn’t a case of “being right” is more important than “doing what’s best”.

    Again, nothing personal @designsimply, you’re very nice to put up with some of the attitude here (including mine).
    Thank you.

    Thanks! I honestly appreciate the discussion.

    Keyboard shortcuts can definitely be considered a power-user tool, maybe in the same way editing HTML is often something done by power-users? I try to offer keyboard shortcuts in that context—but it might also be true that I suggest them to other users as well because I personally really like them! My apologies if that is my own bias coming through sometimes. They aren’t required, but if I think they are an option some people will like then I’ll suggest that option in case it helps someone. I think it’s okay to suggest a thing that may benefit some people in this context.

    You didn’t read my post. When you only have <p></p> showing in the text html (nothing in between as it’s been deleted). You can’t simply use the backspace to delete it along with the block. It won’t. You have to switch back to visual, then delete, or go through the steps I’ve outlined above.

    Ack. You’re right. I’m sorry, and I’ll look into that and get back to you.

    So why do you still need examples of why people don’t like it?

    Good question. I suppose it’s more that I want them. When someone leaves a review saying they don’t like the plugin, I want to know more detail about why in that case specifically if I can.

    Another reason for ongoing testing is that things are still changing. I also personally feel that it would have been better to have tested classic editor more often in the past.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Stop Gutenberg !’ is closed to new replies.