Support » Plugin: Gutenberg » Should be kept as a plugin

  • I read with interest the other reviews and comments.

    If the Gutenberg team is listening, as they keep saying they are, it seems pretty clear that the WordPress developer community does not want Gutenberg in core, especially when there are so many superior block-based editor plugins available for those who really want that experience. Why not just acquire Beaver Builder, rename it to WordPress Builder and have it as an ‘approved’ plugin?

    And for the thousands of developers like myself who make heavy use of meta boxes, putting them in iframes is not a solution. It’s an insult.

    Gutenberg, if accepted into core, will be the worst change that ever hit WordPress and I for one will switch my sites and my client sites to a non-Gutenberg fork if one becomes available.

    Gutenberg should remain as a plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tammie Lister


    @zigpress the team is listening. It is important to look beyond the feedback just from a single source, such as users, bloggers and much more. Everyone matters as we take WordPress into the next few years.

    That all said, there will be a plugin to turn off the experience as and when it gets added to core.

    As far as acquiring Beaver Builder, the experience is different from that.That’s an important note to consider.


    Consider this please!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Should be kept as a plugin’ is closed to new replies.