Support » Plugin: Gutenberg » Please do not merge Gutenberg into core, keep it as plugin

  • I appreciate any engagement in making WP better, giving the complexity of the WP ecosystem & the ways WP is used, for me as a developer it is a no-brainer that you must not and should not force such a change to all users.

    My main concern is that the trust that is lost by enforcing this change has really the potential to disrupt the future successful development of WordPress in general (users switching to other CMS, WP forks, lost markets hare…).

    Please take my – and concerns of other developers & reviewers here – seriously. GB could still be a great (additional) way to edit content as opt-in solution/plugin only.

Viewing 5 replies - 1 through 5 (of 5 total)
  • @harmr thank you for posting your feedback. Disrupt can be a tool for change, and while change can be hard, it can also lead to a more successful future. It is okay to disagree, and what I hope is that we can work together to make a disruption that leads to success. What you’ve written saying that there’s a potential to disrupt the future is hard to address as feedback because it isn’t specific or actionable. However, I want to say I do hear you and reviews are being read and taken seriously. Your feedback is heard. On the point of trust, opening the editor for opt-in feedback in the dashboard is part of that effort and even before that many developers have been testing, working with, posting feedback about Gutenberg in GitHub for a while now already.

    @designsimply

    It really feel like you guys do not really understand who use WP.org. There are here a bunch of people, myself including, that are making website for others, granted in my case I am small potatoes and I do it just for fun to help other develop their SMBs.

    But what you do not understand that by default we are training a lot of people and having to retrain these peoples that are not take savvy by default is a nightmare, especially when Gutenberg as been clearly designed to “Look Fancy” first and Writing was optional at best.

    You have clearly not though about the hell that forcing GB on us will be to have clients getting made and frustrated at us because of GB and not being able to understand how it works and how to use it.

    On paper GB is an interested 3rd party Plugin that you could actually make it available for a Fee in a Pro version, but after a few more years of development when it comes to UX, as it is today and if it ever reach core in 5.0 I will have to consider one of the following

    1. Never upgrade to 5.0 all the sites I handles
    2. Wait for someone to Fork WP (And I will totally support that).
    3. Wait for a “Un-Gutemberg” Plugin
    4. Find other alternative to WP

    I have been using WP regularly since “Duke” or 2.0, there have been some rough moments but Gutemberg is, in my case, the worst.

    Please, listen to WP users and make GB a standalone Plugin.

    • This reply was modified 1 month, 2 weeks ago by  GonzagueGB.
    • This reply was modified 1 month, 2 weeks ago by  GonzagueGB.

    @designsimply thanks for your reply.

    However, I want to say I do hear you and reviews are being read and taken seriously. Your feedback is heard.

    I believe that all feedback and review is read – what I do not see is that it is taken seriously, at least if the review is about making GB opt-in only. I also took the time to read the reviews and a vast majority is asking you to revise the decision to enforce GB for all users and keep it as optional plugin only – I did not read any reply to those reviews which made me believe that also this is heard.

    There are so many arguments against enforcing this into core (training needed for clients, compatibility issues…) and the 1 star reviews explain those issues in great detail (also reply to this review by @gonzaguegb which did not make it through the moderation queue, so it would be great if a moderator could publish it please).

    On the point of trust, opening the editor for opt-in feedback in the dashboard is part of that effort and even before that many developers have been testing, working with, posting feedback about Gutenberg in GitHub for a while now already.

    Yes and the general approach to listen to feedback is appreciated & part of the success of the WordPress ecosystem we all love so much. Just please do not stop listening to feedback, if it would result in revising the roadmap or additional extra effort needed – in the long run I think this is the only proper way to succeed & get the backing from the community & keeping it together.

    Moderator Jan Dembowski

    (@jdembowski)

    Brute Squad and Volunteer Moderator

    *Reads. Removes modlook tag.*

    The reply was archived but has been restored. It was a coin toss for me as the reply is a pile on.

    Here’s the thing. The reviews here are not blog posts. The replies here are not blog comments. Pinging a user isn’t about this review and that user has his own review about Gutenberg.

    The reviews here are about feedback for a plugin or theme. That’s not a Gutenberg thing, that applies to all reviews here. If someone wants to address a review then that’s fantastic. If someone wants to pile on and ping notify someone then that’s not for here.

    Before anyone get’s all heated and bent out of shape or posits a conspiracy theory, please don’t. If you have a problem with any plugin then I invite them to start a support topic. For Gutenberg that’s this link.

    https://wordpress.org/support/plugin/gutenberg/#new-post

    If someone wants to leave feedback then yes, please do. That’s the whole point of the reviews here.

    But if you’re going to comment hop on every review just to spread unhappiness then don’t. That has a very limited value if at all. See comment above about how this is not a blog.

    Leave your own review instead. That has more weight and again, these forums are not anyone’s blog. Though we all know where to get some good software for that.

    For the small percentage of users who get abusive here, and thankfully that really is a small number, then those users can expect to be moderated. That can’t be a surprise; these forums are moderated and they work.

    Thanks for the explanation Jan!

    RobertHarm, while feedback is taken seriously and listened to, that does not mean it will change the outcome of every decision. In this case, Gutenberg is planned to go forward. What I am here to do is listen to feedback and try to pull out details which I can use to help move the project forward in good ways. I appreciate the discussion and concern and I will continue to do work that will help improve the editor in good ways for everyone as much as I can. For me, this means testing, reviewing feedback, and consolidating those things.

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