Still a lot of changes, but moving into the right direction

  • All in all, I like to use Gutenberg, but these perpetual changes to codes, which then have a massive impact on existing CSS, are very annoying. It can not be that in one release adjustments to the CSS codes must be made and then given in the next release completely different tags and so a re-adaptation of the blog operator is necessary.

    ————–

    Alles in Allem nutze ich Gutenberg zwar gerne, aber diese ewigen ?nderungen an Codes, die dann massive Auswirkungen auf bestehendes CSS haben, sind sehr nervig. Es kann doch nicht sein, dass in einem Release Anpassungen an die CSS-Codes vorgenommen werden müssen und dann im n?chsten Release ganz andere Tags vergeben werden und so eine erneute Anpassung beim Blogbetreiber n?tig ist.

Viewing 3 replies - 1 through 3 (of 3 total)

  • Gutenberg is now included in WP 5.0 beta RC1, which is considered release stable, & is available for testing now.

    What you see with the Gutenberg plugin now will be pretty much the default editor in WP 5.0 (due Nov. 2018 or Jan 2019).

    There will of course be changes after that time but they will follow the usual WordPress release cycle.

    Development of the Gutenberg project will also continue with the current Gutenberg plugin through Phase 2 which covers areas beyond the editor interface like widgets, menus & the media library.

    You will still see rapid changes here until the decision is made to merge them to WP core.

    When you say it is included in WP 5.0 beta RC1, does that mean there is no Gutenberg plugin required at all? What would happen if you had the Gutenberg plugin installed on a WP 5.0 beta RC1 installation, would it automatically deactivate itself?

    Moderator James Huff

    (@macmanx)

    When you say it is included in WP 5.0 beta RC1, does that mean there is no Gutenberg plugin required at all?

    That is exactly correct.

    What would happen if you had the Gutenberg plugin installed on a WP 5.0 beta RC1 installation, would it automatically deactivate itself?

    Also exactly correct, the Gutenberg plugin will be deactivated.

    If you still want to use the Classic Editor under WordPress 5.0, install and activate https://www.ads-software.com/plugins/classic-editor/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Still a lot of changes, but moving into the right direction’ is closed to new replies.