Support » Plugin: Gutenberg » This is no fun to use when you just want to write long articles.

  • Edit: I want to change this because I’ve been playing around with Gutenberg and I’m really just not liking it. It feels so clunky and horrible to use. There’s so much wasted space and the fact that every paragraph is a block is awkward as heck. Images are really hard to get where you want them and I’ve had troubles with the image placement interface locking up and rendering images as immovable (I’ve tried replicating this but I dunno, images are a law unto their own). I try to hit DEL on my keyboard to merge a paragraph with another and nothing happens. I keep on accidentally inserting new blocks when I’m just trying to highlight the end of a paragraph. The Bold/Italic/Link hovering menu covers up previous text, making it harder to correctly format some things. Copying and pasting seems to take a long time, even with only 300-400 words. It’s also awkward just clicking between paragraphs to add new ones, especially with the “Add text or type / to add content” thing whenever I make a new space and don’t immediately start writing.

    Even switching to the code editor doesn’t save me as everything’s formatted with a set of <!– wp:paragraph –> tags on every single paragraph.

    Writing blog posts is supposed to be a simple pleasure, and Gutenberg for me really isn’t a pleasure to use at all. If it was an optional plugin, I wouldn’t have a problem with it, but since it’s being forced into the core build, I feel sad that I’ll have to keep Classic Editor activated at all times.

    Old version: Bloody hell. That’s insane.

    You see, the basic text editor that we currently use is great for just writing blog posts, one of the main reasons to use WordPress. But what this is… it’s closer to a page builder. You’ve said in your reviews that it’s not, but that’s what it feels like, shoving everything into content blocks and customizing each block on its own. That’s what most page builder plugins do. But it doesn’t mesh nicely with the core of WordPress blog post making. I just want to be able to write a paragraph of text without having a mile of space around it, I just want to be able to see a basic toolbar at the top. If anything, at first glance, it looks like there’s less functionality. Editing text is hidden away, and if you’re writing a blog post, do you need the ability to clone a section of text? That’s why we have copy and paste. These changes could have all been neat little additions to the existing text editor rather than a total revamp.

    I’m not saying give up on this as a plugin, because it could be a very nice recommended plugin, on the lines of Buddypress. Another, optional way of creating posts and pages. I’m saying give up on making this a core part of WordPress, because it doesn’t fit with the rest of WordPress. You’re making basic blog posts into pages.

    Heavens knows the cost to the WordPress community. How many man hours and how much money is it going to cost to make sure that the thousands of plugins out there will be able to be updated? And what the hell is this going to do to my blog with nearly 2000 posts on it should it become a part of WordPress?

    • This topic was modified 4 months, 1 week ago by  Phovos.
    • This topic was modified 3 months, 1 week ago by  Phovos. Reason: Actual review as a user
Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Marius L. J.

    (@clorith)

    Hiya,

    Firstly, thank you for taking the time to leave a review and letting us know how your experience with Gutenberg has been!

    As for your review, we don’t modify review ratings, but some times there may be hiccups in the system and the value wasn’t included, and the default value is 5. You can edit your review at any time to fix this though!

    I’d love to have a look at your concerns as well, as I understand this new change can be confusing, and a little bit scary moving forward.

    Gutenberg isn’t just a new editor, it’s a new editing experience. You’ll see that we’ve updated the entire edit screen, covering content as well as meta data (those boxes that float around the text editor it self).These are changes that have been long requested, and have had tickets existing for many years. It felt strange to not address the whole screen and only parts of it when we wanted to bring new functionality and modern behaviors into the mix.

    As for the spacing around blocks, this can actually be modified by your theme, allowing them to give as close a representation of how the content will look on the front end as possible (we even encourage them to do so). This was, in part, possible with the classic editor as well, but Gutenberg gives them much more control and allows for a much cleaner and truer representation of what things will look like, if themes chose to make use of it.

    You can still see the toolbars up top and similar, although not easy to discover right away if you click the ellipsis in of the editor there’s an option to fix the toolbar to the top of the editing screen. You can even add the classic editor into Gutenberg (we added it as a block for those that feel more comfortable with it, or need that little bit of extra control over their content).

    Cloned text is intended more for repeated content, it’s there to give flexibility to users, and if you don’t need it for your posts, you don’t have to use it.

    I am curious about one of your statements:

    I’m saying give up on making this a core part of WordPress, because it doesn’t fit with the rest of WordPress.

    What about it doesn’t fit with the rest of WordPress, and how do you see it blending in better?

    As for your last concern, the one of hours and cost. We’ve been actively educating developers for over a year now, with talks and workshops at WordCamps, as well as frequent updates on developer related areas here on WordPress.org. This means that anyone interested in adding specific support or interactions with Gutenberg should have been at least in the loop by now and have an idea of what needs doing.

    I should note though, that for what I suspect is a majority of plugins, they won’t have to change anything, only plugins that interact directly with the editor will you see a need for larger changes to be properly compatible once it is released.

    As for themes, they will still display content like before, and we are taking steps to ensure compatibility and fallbacks are in place should other plugins or themes declare use of anything that’s not supported. You can see https://wordpress.org/gutenberg/ for some information about the project as a whole, as well as what we are doing in terms of compatibility.

    I should also note that this change won’t affect existing content, we will not retroactively go through every posts, page, etc. and modify. When you open old content you’ll be shown a legacy block with your content in the classic editor inside the new editor window. You can then choose to convert it to the new format, or leave it as is.

    We do also have some alternatives for those that feel they are not ready for the new experience just yet. You can use the Classic Editor plugin to force the current look once WordPress 5.0 is released, or you could use Gutenberg Ramp to enable it only for some content at a time if you for example wish to test it out on pages, but not on posts to begin with.

    Moderator Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    I did set it to 1 star… Unless someone changed it…

    You made a mistake and set it to 5 star, nobody has the authority to change your review rating and that functionality does not exist.

    Firstly, thank you for taking the time to leave a review and letting us know how your experience with Gutenberg has been!

    As for your review, we don’t modify review ratings, but some times there may be hiccups in the system and the value wasn’t included, and the default value is 5. You can edit your review at any time to fix this though!

    Eh I must have messed up then. My bad.

    As for the spacing around blocks, this can actually be modified by your theme, allowing them to give as close a representation of how the content will look on the front end as possible (we even encourage them to do so). This was, in part, possible with the classic editor as well, but Gutenberg gives them much more control and allows for a much cleaner and truer representation of what things will look like, if themes chose to make use of it.

    This would be alright but only really if it’s automatic. If one has to fiddle around with a theme to make what’s seen on the editor match what’s on the website then at the end of the day does it really make much difference? If one of your goals is to make backend match frontend then perhaps frontend editing would have been a better idea.

    You can still see the toolbars up top and similar, although not easy to discover right away if you click the ellipsis in of the editor there’s an option to fix the toolbar to the top of the editing screen. You can even add the classic editor into Gutenberg (we added it as a block for those that feel more comfortable with it, or need that little bit of extra control over their content).

    Cloned text is intended more for repeated content, it’s there to give flexibility to users, and if you don’t need it for your posts, you don’t have to use it.

    But that’s the thing. Things shouldn’t be “not easy to discover right away”, requiring clicking on some little dots. Really, this is my biggest issue with the new system, that it’s kinda not really clear and obvious what you’re being presented with. You get a plain, blank screen and some options on the side, with important things like the Publish button stuck away at the top, next to what looks like two options menus (the gear and the ellipsis), and everything else being stuck behind the “Block” tab.

    And cloned text really does feel like something a page builder would use. Is it really something that people use on blog posts and the like?

    What about it doesn’t fit with the rest of WordPress, and how do you see it blending in better?

    I feel that it goes past the layout of all other WordPress pages. The menus and everything you want to edit are on the right of the page, rather on the left like the Customizer and the normal WordPress menu, losing the boundaries between what is menu and options and what is one’s content. Everything else is squished up at the top of the page rather than having some breathing room, and a lot of labels are replaced with symbols rather than basic text.

    Rather than being presented with boxes you can fill in, it’s got a clean, surgical look. Like a blank piece of paper.

    As for your last concern, the one of hours and cost. We’ve been actively educating developers for over a year now, with talks and workshops at WordCamps, as well as frequent updates on developer related areas here on WordPress.org. This means that anyone interested in adding specific support or interactions with Gutenberg should have been at least in the loop by now and have an idea of what needs doing.

    I should note though, that for what I suspect is a majority of plugins, they won’t have to change anything, only plugins that interact directly with the editor will you see a need for larger changes to be properly compatible once it is released.

    That doesn’t actually cover the man hours and time and money that will be required to update plugins though. Sure they’re in the loop but they’ve got to spend time and money to fix their stuff up because WordPress has suddenly decided to completely shake up their editor. And at the same time, it’s a whole new learning experience, sites that have multiple levels of users will have to reteach how to use the new editing system.

    I should also note that this change won’t affect existing content, we will not retroactively go through every posts, page, etc. and modify. When you open old content you’ll be shown a legacy block with your content in the classic editor inside the new editor window. You can then choose to convert it to the new format, or leave it as is.

    Well that’s good, I guess. But that still leaves us with the following:

    We do also have some alternatives for those that feel they are not ready for the new experience just yet. You can use the Classic Editor plugin to force the current look once WordPress 5.0 is released, or you could use Gutenberg Ramp to enable it only for some content at a time if you for example wish to test it out on pages, but not on posts to begin with.

    It seems paradoxical to make a large change and force users to get a plugin to go back. Why can’t we keep things as we are and have a plugin to change things? You’re dragging users forward rather than giving them the option to move forward themselves. And that just leaves a sour taste in a lot of people’s mouths.

    My biggest issue is that this system will be rolled into WordPress 5.0. As a plugin, it’s not something I enjoy using at all, but I can see maybe some people would like a very simplified pagebuilder-esque sort of thing. But in a CMS that applauds having choices, it seems weird to force out such a big change.

    The thing is, you WILL go ahead with this, no matter what users and developers say.

    Moderator Marius L. J.

    (@clorith)

    I’ll work my way through this back to front I think, and I hope that’s OK with you.

    Yes, we will be implementing Gutenberg in WordPress 5.0, there are some bad reviews here, but that’s currently based on every review since the plugins original inception, and many of them are no longer valid as they address bugs and missing features. WordPress 5.0 won’t be released until the new editing experience is finished, so it’s not a matter of us rushing the development here to fit a release schedule, hopefully that knowledge helps keep the worry at a minimal level.

    We provide the extra plugins for those that feel they need them, but for the majority of users we think the new editing experience is what they will be using. Our goal is to design this for the majority, as our core philosophy dictates, and I honestly believe we’re getting close to that goal.

    The classic editor also provides meta boxes and “editor alternatives” on the right side, we’ve just compacted them more in the new experience, the clean slate view is often what users want today when they start working on a page. Again though, themes and plugins can here come into play, they can pre-define layouts that can be used as boilerplates for users. This means you can have a clean slate regular post, but then you want to add a list of books, every time you go to add a book it’s got pre-filled in defaults and block placements with the information you need.

    The discoerability is being worked on, we’re introducing a first time guided tour that can be skipped for those that are familiar with the editor, that should hopefully help with making some of the less obvious features found in a timely manner.

    As for representing editing more closely, someone may make a front end editor, we’ve toyed with a few options for it in the past, but nothing that we’ve been happy with. But who knows what the future holds in that regard.

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