Keep it optional. The users have spoken.

  • Reece

    (@firstclasscode)


    6 years, 3 months ago

    Really, hardly anyone wants this project merged in the core. Keep it as a plugin for those who want to use it. What reasoning is there to force this on everyone? If they want it, let them use it. If they don’t, great, keep the classic editor. I don’t see any valid reason for removing classic editor completely.

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

  • I know a lot of people want to see Gutenberg kept as a plugin. In fact I see a place for it in core alongside the current editor. It suits certain use cases and given time could cover many more.

    At the same time there are many use cases where it just does not fit in to many workflows and has many limitations in the backend interface outside of the content creation area. for example the flexibility to arrange metaboxes anywhere, even above the content creation area.

    Not only do we need some balance but people need to identify the pain points in detail so that it is clear why Gutenberg should not be made the default editor on many current install and themes.

    Thread Starter Reece

    (@firstclasscode)

    Right, as long as it remains optional I am all for it coming in to the core. I guess saying “keep it as a plugin” should really be “keep it optional”. There is no need for this editor to be the only editor. It’s crazy, especially considering the push back.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Keep it optional. The users have spoken.’ is closed to new replies.