1. Geraldine

    The Classic Editor plugin has become the 7th most popular WordPress plugin with over 3 million sites using it.

    It’ll be interesting to see whether core developers can implement changes to Gutenberg that’ll convince those people to make the switch, or if use of the Classic Editor plugin will continue to grow.


    • Jeff Chandler

      The people who are using the Classic Editor are running on borrowed time.


      • Manolo

        > The people who are using the Classic Editor are running on
        > borrowed time.

        Or maybe wordpress is running on borrowed times. I m using gutemberg on my websites, but ALL my clients wanted the old interface and a couple already looked for /installed alternative (classicpress being one)

        i remember 10 years ago when i moved from joomla/mambo to wp.
        The people who killed joomla replied the same exact way.
        Ditto for the people who crippled Drupal.

        I ve the greatest respect for people who work for us to improve wordpress, and i m supporting them 100%, but this kind of replies suck big time and damages wp as a whole.
        and the mentality behind it should be eradicated


      • creationdream

        Oh Jeff, please say it isn’t so.. I have not moved into Gutenburg, each painful try was awful.
        None of my clients will even explore it.

        I am getting quite concerned that this block push is going into the dashboard. I love widgets. It is dead easy to manage. Menus too.

        I do believe if this is pushed onto the dashboard where I have no say in how I want to manage sites, I too will leave WP.


      • Yves

        > The people who are using the Classic Editor are running on borrowed time.

        Indeed, this is my case. I’m using the Classic Editor until I rebuild the two remaining sites that I still have running on WordPress and transfer them to static sites.

        I love WordPress but maintenance just takes too much time.


    • Kåre Mulvad Steffensen

      Lots of old sites running themes that aren’t compatible.


  2. Doug Smith

    I’m commonly seeing users installing multiple block collections that each contain their own block manager. So now they have a confusing mess with block managers that may or may not work together, and may or may not have a way to be disabled.

    This won’t likely get better until core takes on management of blocks.


  3. Bastian

    Block management is not an immediate focus in the Gutenberg roadmap and is considered plugin territory

    The usual “we are listening to the feedback”


  4. Luke

    Why not just give us a true drag and drop interface?


  5. David Anderson

    You are telling me that more regular users will use the Amazon Kindle Embed Block (that is being baking into 5.1)

    I thought this was a very strange/niche thing to include into core. What was the reasoning behind it?


  6. Bud Kraus

    Whether it’s in core or in plugins we need a way to deal with Gutenbloat!


  7. Mark

    Amazon Kindle Embed Block?

    I’m looking forward to the “Skip this ad in 4 seconds to continue editing your post” that will probably follow.


    • Json Socks


      This new block is completely useless.

      Never saw that oembed in any thousand blogs i ever visited, before Gutenberg.


  8. David Decker

    The personal opinion of the Gutenberg lead dev on the block management thing doesn’t really matter.

    What matters is that more and more users, developers included, are wanting such management features as they get overwhelmed by blocks a lot.

    Also the whole dev pace of Gutenberg/ WP Core needs to slow down. It is way too fast at the moment.

    If you want a to adapt another release structure and schedule have a look at Mozilla with their Firefox: they do it completely right. About 10 releases a year (with exception of christmas holiday season…). Alpha beta, final release channels. A clear release calendar. And each of the releases has a clear focus: smaller steps but consistent. — Current Gutenberg / WP Core dev is the exact opposite of that, at least to me.


  9. Peter

    It is kinda worrying that such elemental features like a block manager has not been implemented until GB was merged into core and ever since that time. That way they created an issue and will need to recover that somehow but this way they just run after a problem they created by not thinking forward.

    I just wonder why one can not change the post type in GB’s latest posts block, maybe even that is thought completely useless… i don’t know


  10. Steve

    Agree that management features are needed ASAP.

    I’ve personally witness “average” users install block plugins that add in some cases 10-20 blocks. When in fact they were only after 1 block in particular.

    The CoBlocks interface for block management is exceptional and should be integrated into core.


  11. Paal Joachim Romdahl

    Here is the beginning GitHub issue for Block Management:


  12. Karen

    Block manager would be so much more useful (esp to less advanced users) if it could scan the site to detect blocks that are actually in use and suggest turning off the unused blocks.


  13. matt

    Block management features should either be baked into WP or everyone who is developing the same should do so as a separate plugin so that only one manager is likely to be installed.


  14. Scott Hartley

    Another issue with blocks is that there is now a lot of bloat being generated. Users may only be looking for a single block and end up installing a plugin with 20 of them or so loading all their assets onto every page.

    I think that there needs to be a smarter and more standardized way of handling block assets. IE if there is a slider block if you would its assets are only loading if that block is being loaded.

    As for the block management, I can see the use of such a feature but I think it’s looking to fix a problem that shouldn’t really exist. Plugins should quite frankly stop bundling 20 blocks into a plugin


Comments are closed.

%d bloggers like this: