Support » Plugin: Gutenberg » Gutenberg has merit, but keep the Classic Editor in the core.

  • Gutenberg isn’t terrible outside of feeling sluggish, bloated, and occasionally buggy, but removing the Classic Editor from the core on launch is ridiculous.

    It needs to stay available as a built-in option until Gutenberg has become the definitive choice that people use voluntarily.

    While Gutenberg and 5.0 are supposedly being delayed until Guterberg is sufficiently ready, we all know that they’re really going to arrive long before then.

    Gutenberg has potential and something like it has been needed for a long time, but WordPress is about to shoot itself in the foot by giving it a mainstream release before it’s sufficiently ready.

    The proper roadmap should look something like this:

    1. The Classic Editor is core and Gutenberg is a plugin
    2. Both the Classic Editor and Gutenberg are core
    3. Gutenberg is core and the Classic Editor is a plugin

    Instead, you’re choosing to skip the (very necessary) second step and going straight for a hard, hard release of something that still needs much work.

Viewing 3 replies - 1 through 3 (of 3 total)
  • > 1. The Classic Editor is core and Gutenberg is a plugin
    > 2. Both the Classic Editor and Gutenberg are core
    > 3. Gutenberg is core and the Classic Editor is a plugin

    Unsurprisingly, that’s exactly what’s happening. Have you received some faulty information from somewhere?

    WP5 is going launch at “stage 2” and will highly likely stay there for a leeeeeengthy while.

    Moderator Marius L. J.

    (@clorith)

    Hiya,

    Thank you for taking the time to leave a review, we would love to hear some more about your experiences with Gutenberg it self. What features did you try and enjoy, which features did you feel were lacking or missing?

    As for the release plans, we have no intentions of removing the classic editor from core, but we also won’t be adding any options to toggle between them. The classic editor will be a fallback if something isn’t Gutenberg compatible, or you can install the Classic Editor plugin if you wish to override Gutenberg in all scenarios (that’s what the plugin does, it just tells WordPress to always use the fallback).

    How can I stay on Classic
    Gutenberg when WordPress 5.0 goes public?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Gutenberg has merit, but keep the Classic Editor in the core.’ is closed to new replies.