Support » Requests and Feedback » Gutenberg should NOT be default

  • Michael

    (@michaelswengel)


    Whoever created Gutenberg needs to be slapped with a trout.

    It’s cumbersome and requires far too much TLC to do the same as the old editor.

    There is apparently no ability to indent blocks? In the classic editor, one can indent and outdent any selected paragraph, line or list item at will.

    Now we’re told we have to use the Classic editor or custom CSS for that?

    Fix this!

    Gutenberg COULD be good and perhaps will be in time, but it’s not ready yet. Telling us we need to install the classic editor to do basic things is admitting that Gutenberg isn’t fully cooked, and if it isn’t, it should not be the default.

    • This topic was modified 2 months ago by  Michael.
Viewing 13 replies - 1 through 13 (of 13 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    The indent feature was not included in the new editor because it’s one of the least used features in the old editor. Having things that nobody actually uses doesn’t make a lot of sense.

    If you need such a thing, there’s better ways to do it. What do you use this feature for, exactly?

    Michael

    (@michaelswengel)

    @otto42 I was never polled. Ha.

    I like to indent subheadings. I used the feature ALL the time. So unless I’m a nobody…. 🙂

    PLEASE add this to the editor. It is very very important for me.

    Michael

    (@michaelswengel)

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    I didn’t make the editor myself, so I’m not adding a thing. However, if you indent subheadings, then it would honestly make more sense to just alter your theme’s CSS to make subheadings always indented instead of individually doing it by hand every single time.

    If you do need to indent a paragraph on an individual basis, then the better way would be to define a class with padding-left: 30px or something in your theme, and then to use the Advanced section, which is available for all blocks, to add that class to the paragraph. Then they would be indented.

    Michael

    (@michaelswengel)

    @otto42 The implied “you” is those who created Gutenberg. I understand you didn’t create it yourself.

    This is something that wouldn’t be difficult to include in Gutenberg and is actually used by many. Even if it was one of the least used features of the old editor, it was still used and is still a need.

    While some are comfortable adding CSS and using custom classes, many aren’t. One of the draws of WordPress is its ease of use and power. If that is no longer going to be a part of the WordPress platform, we need to know.

    I have filed a bug report on Github with the developers – as have several others. While not strictly a bug, this is a massive hole in functionality.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    I can think of many things that wouldn’t be difficult to include, but if you just throw the full kitchen sink in there again, then you end up with the same problem as the classic editor has: too many buttons that you never use.

    The indent button was removed, and it was correctly removed, IMO. We don’t need it. You shouldn’t need it. There’s better ways to solve the problem, and having two rows of icon buttons ala MS Word isn’t a good user experience.

    Sorry if that lack upsets you, but it is what it is and I think it is a good thing.

    Michael

    (@michaelswengel)

    A custom class is not a better solution, Samuel. I can understand and appreciate it’s not something you would use. I get that. But those of us who do miss it dearly.

    //but if you just throw the full kitchen sink in there again, //

    I agree! But that isn’t what we’re asking for.

    //The indent button was removed, and it was correctly removed,//

    That is your opinion. While you have a right to your opinion, we do to ours as well.

    Michael

    (@michaelswengel)

    One final thing….

    This is a fantastic philosophy: “If the next version of WordPress comes with a feature that the majority of users immediately want to turn off, or think they’ll never use, then we’ve blown it.”

    I love that, and it’s so true. Please don’t turn Gutenberg into the very thing you hate.

    Gutenberg could be amazing, and I sincerely hope that one day it will be. But it simply is not there yet.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    The majority of users don’t want to turn it off, because it’s whole worlds better than the old crappy editor. Not sure where you’re going with that.

    Michael

    (@michaelswengel)

    It has some nice new features. I’m not disputing that. But it is lacking important features.

    Look at the reviews for Gutenberg. 458 5 star reviews compared to 1808 1 star reviews.

    The majority of reviews are negative.

    Please don’t misunderstand me, Samuel. I’m all for change. WordPress needs to stay current and updated. But something is very wrong with this picture.

    If you really need to do such things, switch to classic editor. I tried Gutenberg on another site for a month. I found it took me longer in Gutenberg than classic. Even after that I still switched back to classic for ease of use.

    There are a lot of things Gutenberg doesn’t do well and the replies are usually the same from the poor moderators who have to deal with the fallout, here is a workaround which is even more cumbersome, or go add a plugin for something we could do easily with a click of the button in classic.

    Gutenberg is still a beta, but I feel our protests fall on deaf ears in WP execs who make the decisions.

    Michael

    (@michaelswengel)

    The problem, however, is the classic editor will be going away. Telling users to rely on a system that will die isn’t a solution.

    I really really want to love Gutenberg. It could be awesome. But right now… it simply isn’t.

    Bit of our ideas: We stopped using the old editor and switched to wpbakery. Not ideal, but it saves us users a lot of hassle. Tried Gutenberg. Really tried. Fail. three steps back without any improvement.
    And thinking about adding css: CSS is the worst web-invention since the invention of printing books. Way too complex, Way too large also in output, Way too nerdy, made without any consideration for the normal user. It should be impeached forthwith.

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.