13 Comments

  1. Project Topics

    I will stick with the Classic Editor.

    Report

  2. Dan Herman

    I’m very happy about the promise of extended support of the Classic Editor. I’d be much happier if we took this to its logical conclusion and make Gutenberg an optional plugin until it’s both a) finalized, and b) in wide-enough use that it makes sense to switch over, instead of forcing people to install a plugin to make sure their website doesn’t break. Even if they wanted to make the Gutenberg plugin default in new installations, that’d be fine.

    The heavy-handedness of the announcement and plan actually bother me more than the actual plugin itself, because there are always ways to architect around bad decisions. As someone who manages enterprise installations, I have trouble selling my bosses on a product that the maintainer can decide needs a wholesale revamp on, despite it working very well for us as-is.

    Report

  3. Stephen Vaughan

    If Gutenburg implements the same or similar functionality that is present in the current editor that may Go some way to make it more useable.

    Report

  4. Greg Schoppe

    one is now very hard-pressed to find a theme developer who is rolling their own options panel after the Customizer was introduced as the new standard

    Is this a joke? Perhaps that is true on the WordPress.org repository, since integrating options into the customizer is a requirement for themes that want to be listed there, but the vast majority of themes on other marketplaces still roll their own admin panels.

    It’s also apples vs oranges. No one needs to disable the customizer for their site’s features to work. It’s just an additive experience. This is much more similar to the replacement of the media library, which saw a mass die off of popular plugins in its wake.

    The issue with Gutenberg vs Classic Editor is that they are two completely different and mutually exclusive development environments. So, either plugin developers stick to the subsets of metabox interfaces that aren’t broken by Gutenberg, or they build systems that aren’t compatible with Classic Editor, or they do twice the work.

    Realistically, that means plugin devs are going to pick a side. Those that pick the Gutenberg side will see a significant reduction of userbase, but will also make it much harder for users of Classic Editor.

    What is really crucial from Matt/Automattic is not just a statement that classic editor will be supported indefinitely, but a statement that it will be supported by all Automattic properties, such as WooCommerce. This is especially crucial with WooCommerce’s history of implementing breaking changes.

    Report

    • Chris Howard

      Agreed.

      I use Beaver Builder, Beaver Themer, and Beaver Theme, and I avoid the customizer like the plague. And always have once I got to see its failings.

      As a site dev, I find a child theme with all my custom css in its stylesheet the best workflow. Then everything is in one place.

      I wish WordPress would stick to and focus on its core product instead of seeing something succeed in the dev community then eating those dev’s lunch.

      Let the dev community make WP great. It’s worked for 15 years and was working fine before the Customiser and before Gutenberg.

      Report

  5. Hector Garcia

    Hello I understand new and improved ways of doing things are always at hand or in the future. But, am sure you know how many people are not welcoming to change (new unfarmiliar ways) in how things work? They have to learn something new (again). Especially when they just learned the Old way of doing things or how things worked. WHY or Can’t Someone Develope a way for the Old to be Automatically changed (updated) to the new process with (option of) instructions on how the New process works? Therefore leaving noone behind in the process of updating systems or operations? And then Everyone is Happy with learning something New in the process.

    Report

  6. Paul Dahlen

    And then, at some point, I’m totally ok if you drop support for the Classic [Editor]. There will be themes and plugins that will say you need to have Gutenberg, [WP] 5.0 or newer if you want to use this.

    What incredible arrogance. This is what WordPress has come to; what a horrible shame.

    Report

    • Nick

      That would be true, but since WordPress and it plugins are open source, you can hire a developer to customize that plugin to fit your needs. Once you purchase the plugin from the original developer, there is nothing that they can do to stop you from paying someone to customize it to your needs.

      Report

  7. Phillip

    I don’t feel better about the Classic Editor plugin. Gutenberg is absolute trash, and adding it to the WP core is blatantly ignoring the fact that the majority of people hate it. The WordPress editor needs to be left as it is, and Gutenberg needs to remain a plugin — this is only my opinion and hundreds of others.

    It’s too late to turn back now, because there’s been too much marketing involved with claims of the so-called almighty, amazing capabilities & functionality of this disaster called Gutenberg. The Gutenberg plugin authors and WP core team members are too arrogant and not willing to admit the catastrophe of this horrible thing. Admitting that the Gutenberg project is a failure (despite its good intent), would be too much of an ego buster.

    When Gutenberg becomes part of the core, my hope is that WordPress receives soo much heat to the point that they are forced to remove Gutenberg from the core. If Gutenberg still isn’t removed from the core and issues/bugs still persist, then my hope that it will be possible somehow for people to take legal action the Gutenberg authors and WP core team members that allowed Gutenberg become part of the core. If Gutenberg disrupts enough themes and plugins, there are going be developers losing clients and money — lots and lots of moolah. Even though the WordPress script is open source, there is a slew of people displaying their critiques and dislikes of Gutenberg (well prior to its release), and people are literally ‘begging’ for this not to be added to the core.

    Report

  8. Simon

    He cited the Customizer as one example where one is now very hard-pressed to find a theme developer who is rolling their own options panel after the Customizer was introduced as the new standard.

    I think this is not the best example, because in my company our clients never ask us to make theme options with customizer, this is not always convient for the client and it’s a lot more easier to make theme options panel with Advanced Custom Fields, for example or with the Redux Framework.

    Report

  9. Nick

    This might be true, but keep in mind that WordPress and all of the plugins and themes are open source. That means, someone can hire a developer to disable gutenberg and customize a plugin that was purchased to fit your wordpress website. This will increase the cost of doing business, but it will be worth it.

    Report

  10. Paul Taylor

    I do not know where you get the idea that developers are excited by Gutenberg. A simple comment that I posed on Facebook produced a vast number of responses from developers, all united in their dislike. I have tried Gutenberg as a plugin for several weeks now, on a couple of my websites. It tends to freeze up the backend. This is probably due to a clash with another plugin, and, when I get chance, I will try to find out which one. But why fix what isn’t broken? Gutenberg is an answer for a question that nobody was asking. And it has some considerable problems – Gutenberg’s code editor, for example, is just plain text, with none of the helpful tools found in the Classic Editor’s code editor.

    WordPress is an open source product. They have the right to do what they like, and I don’t have to use it. I will be interested to see if ClassicPress manages to get off the ground as a viable fork.

    Report

Comments are closed.

%d bloggers like this: