Gutenberg is here! If you’re a plugin developer, you’ve maybe already taken steps to ensure that your plugin is ready. And if you’ve done so, you know how much a step forward the new block-based editor is.

Unfortunately, with over 1 million installs, the Classic Editor is going to be a reality that you’ll have to deal with for a long time to come. Fragmentation between user bases is a difficult problem to solve, because it can mean maintaining two entirely separate user interfaces for different editors. Choosing to support one editor or another limits the potential reach of whatever awesome thing you’re building, while choosing to support both can lead to serious headaches.

Thankfully, with a few abstractions, it can be possible to build React applications that can just as easily target Gutenberg or TinyMCE, or another context altogether. This talk will provide a basic outline for building interfaces that can handle different contexts with maximum reuse.