Support » Plugin: Gutenberg » Dread

  • Please do not force this into core. It seems like a huge betrayal to the many developers around the world who have created the rich ecosystem of plugin functionality that has helped make WordPress the successful CMS that it is today. I can also imagine a lot of freaked out website owners when this shows up unexpectedly. This really seems like a big mistake for WordPress.

    At least please consider making this an opt-in option. Gutenberg is obviously polarizing the community, and many people simply do not want it.

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


    @alarthur-1 I am interested why you think Gutenberg is a betrayal to the ecosystem of plugin functionality. You are totally ok feeling that way, it’s more I would love to know more how about that exact statement.

    The discovering of Gutenberg is something as a team we need to explore. What happens on 5.0 is not set in stone. That’s something which will be explored over the next few months.

    Hi Tammie,

    I’ve always subscribed to the metaphor that WordPress core is like the engine of a car that can be used to power just about any type of website. Themes and plugins would be interchangable, and would allow the complete customization of the user experience, including the front facing website and the backend editing environment.

    As a result of this architecture, many people have created themes and plugins that enable users to pick and choose every aspect of how they want thier WordPress website to be. This includes a lot of page builders that enable users to choose what type of editor they would prefer.

    Gutenberg seems like it could be a great page builder option as a plugin, but as part of core will seemingly eliminate the competition while limiting the options available to users. I don’t understand why this is a desirable goal.


Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Dread’ is closed to new replies.