Support » Plugin: Gutenberg » This should be a plugin and not a core component

  • Edit: I had the chance to test drive the new version. It’s still shit and it has no place in the core. It should remain as a plugin.

    I get that you want to make things on WordPress better for everyone. But making things look light and modern by destroying something that is already good is not a progress. It’s just complicating things.

    The goal of the block editor is to make adding rich content to WordPress simple and enjoyable.

    It is already simple and enjoyable!

    WP.org is so far built with a clean visual editor and an HTML editor with no problems at all. I don’t know why you would want to kill it for a block editor. We have page builders for that! You of all already know that WP.com and WP.org are totally different and there is no need to blur the lines between them. By introducing Gutenberg into the core, you are only going to limit a lot of control to the users.

    It is important to point out that WordPress is a CMS and not just bound to blogging. Gutenberg editor might make sense to WP.com, but it just doesn’t fit anywhere inside the WordPress core.

    My point is. I don’t have a problem with Gutenberg at all. It’s just that integrating it into the core and replacing the existing visual editor is A BAD IDEA! As a plugin, Gutenberg will be welcomed — as it will always remain as a choice. Other than that it is an unnecessary and a FORCED component of the WordPress core — hated and will be hated by most of the community.

    I also see that there is a classic editor plugin and you are suggesting it to revert back to the default editor. How about you reverse it? That is how it should be! Guess this is more of an Automattic decision than a community thing.

    I’d rather fork and maintain the last version of WordPress that’s Glutenberg free for myself, rather than to go on with 5.0 with Gutenberg forced on to me.

    • This topic was modified 2 years, 3 months ago by Andrew Nevins.
    • This topic was modified 1 year, 7 months ago by Karthikeyan KC. Reason: Opinion after testing the new version!
Viewing 8 replies - 1 through 8 (of 8 total)
  • Great review. This is the point: leave Gutenberg as a plugin, not forced as part of core. Many of us hope that they will be so wyse to avoid this mistake. They can force Gutenberg in the core anyway, but then cannot force us to continue to use the “new” WP …

    I couldn’t agree more with you Karthikeyan. I tried the plugin on a development site and can’t believe that this is meant to be the future of the post editor. The UI and especially the blocks are terrible! This has to be an optional plugin.

    Plugin Author Tammie Lister

    (@karmatosed)

    @karthikeyankc thank you for leaving a review. All reviews count as the project is being worked on and it’s important to get feedback.

    It is important to look at all users of WordPress, a lot have issues with the current implementation of editing.

    I also think it’s crucial to point out that Gutenberg isn’t just an Automattic project. Just like WordPress it is a project for the entire community, by the entire community. We have a wide range of contributors beyond those employed at Automattic. It’s important those get seen and acknowledged.

    A lot have issues with the current implementation of editing.

    A lot? Could you tell us what type of issues? Where has this been reported? Perhaps can you link us some cases of such reports? I don’t see anyone having issues with the default editor. Comparing to Gutenberg, the default editor is far better, simple, and efficient for an editor.

    And again, even if such reports exist, I am sure it’s not from ‘a lot’ of users. It could be true that a very small group of the community might have issues with the default editor. In that case, you should look at the bigger part of the community and make Gutenberg as a plugin and not force into the core.

    @karmatosed, you haven’t responded yet. You said that a lot of people have issues with default editor. Could you tell us what type of issues? Where has this been reported? Perhaps can you link us some cases of such reports?

    Plugin Author Tammie Lister

    (@karmatosed)

    Firstly, lets be civil in our approaches here, we all care about the future of WordPress. My apologies for delay in response, I have been travelling and did not catch the request.

    It’s super important to not just think about us or the users we know. To assume that everyone making Gutenberg has never worked with clients is a wrong assumption. For example, many of us have worked freelance or in agencies – in a variety of situations and companies around the world. Gutenberg also isn’t being made by one company, those working directly with clients today are also making the project.

    One question, have you ever done usability testing outside of your own user base? I ask because when you do these issues will come up time and time again. Doing usability testing myself has brought me such insights. We are also doing this with Gutenberg.

    Beyond testing, there have over time been issues in trac and also support forums. From problems with people switching themes – yes that’s from the editor too – to issues with users just being able to understand the interface. The entire publishing flow right now doesn’t work as well as it could. For those that know the ‘WordPress way’ it’s working, but that’s not a way forward.

    One smaller data point is: https://make.wordpress.org/core/2017/04/07/editor-experience-survey-results/.

    @dividendninja, I have asked the support team to remove the last few responses as you requested, I am unable to.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Side note: At a request from someone who posted here in this review, I have archive that person’s replies. Normally that isn’t done but I feel an exception this once is warranted.

    The comments were not edited or changed in anyway and any moderator can still see them and un-archive them if necessary.

    To assume that everyone making Gutenberg has never worked with clients is a wrong assumption.

    I’m not sure what prompted you to write this, but I never said that anywhere.

    The entire publishing flow right now doesn’t work as well as it could. For those that know the ‘WordPress way’ it’s working, but that’s not a way forward.

    I am still confused about the part ‘doesn’t work as well as it could’! For whom?

    I’ve been using WordPress for almost six years now and never faced any issues so far. Even the survey results that you have linked shows that there are no issues with the default editor. It works well for the majority of the community!

    Perhaps ‘the way forward’ for you is more of a cosmetic expansion under compulsion. In that case, again… It should be a plugin! Expansion components clearly belong to that domain!

    As a WordPress user and a developer, I stand with the idea that you should keep this as a plugin! These are just my 0.02$!

    I hope you people will consider all our suggestions once again. Good luck!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘This should be a plugin and not a core component’ is closed to new replies.