Make Ramp + Classic Editor play nicer together about gutenberg-ramp HOT 2 OPEN

Of course we can add filters in Classic Editor if needed. But wondering if we should try to make Gutenberg Ramp and Classic Editor work alongside, or disable one when the other is installed? They are adding functionality that overlaps and seems conflicts like this one would happen often?

Thanks for weighing in @azaozz The new features sound great. As Classic Editor plugin becomes more sophisticated, and especially if it is included with Core in some form, perhaps we should revisit the possibility of moving Ramp functionality into Classic Editor plugin?

One key consideration from VIPs side is that Ramp was created explicitly to ensure control over Gutenberg loading behaviour is not subject to the whims of editorial staff in wp-admin. That seems somewhat opposed to Classic Editor's current approach where the aim is to give everyone as much choice and options as possible? How do you see that working? cc @justnorris @pento

from gutenberg-ramp.

I'm actually planning more updates to Classic Editor now that 5.0-beta is out. Should at least wrap the code in a static class :)

Thinking to add two more options:

• To "remember" which editor was used for each post and open it there next time.
• To use the classic editor by default but have links to the Block editor.

Of course we can add filters in Classic Editor if needed. But wondering if we should try to make Gutenberg Ramp and Classic Editor work alongside, or disable one when the other is installed? They are adding functionality that overlaps and seems conflicts like this one would happen often?

from gutenberg-ramp.