In reply to Greg Schoppe.

@matthijs

you are correct that this is a temporary solution, because eventually some plugins will make Gutenberg mandatory. For the next year or so, I believe most plugins that move to a Gutenberg-only interface will receive significant backlash from their classic-editor userbase, which will force them to support classic metaboxes as well as Gutenberg. This fundamental schism is one of the most worrisome parts of the whole project, as it will either alienate developers' userbases or it will make developer's jobs twice as hard, when building admin interfaces, as they will have to build two variations.

Because Gutenberg can be enabled or disabled on an individual post-type basis, this will effect many plugin developers like yoast, who add interface elements to all post types, regardless of the use of classic editor.

Personally, I think WooCommerce's experiments with Gutenberg make the least sense of any I've seen, as stores should be a highly structured interface, to make all products uniform and easily scannable.

In any event, if we want 3rd party support for classic editor to be a priority for plugin authors, we are going to have to be very vocal in demanding it. Whenever a plugin updates in a non-compatible way, there is going to need to be a concerted effort by many users to report tickets, comment, and leave reviews.