With the demise of Classic Editor - more moving to CP?

Yes, I think it is an opportunity. I try to bring up CP on Twitter in relevant conversations and Reddit. This also includes commenting on relevant articles like on WP Tavern.

In many cases, once someone learns CP exists they do tend to switch. Not always, but they do. The main barriers are the lack of plugins they need, but this is slowly becoming less of a problem since our community developers are building and forking plugins. Plus, more WP developers are making their plugins compatible with CP and some even switch to CP.

One big problem with the classic editor, TinyMCE itself, is that it uses an old outdated, and no longer supported version. How long will it work? It will get to the point when the browser changes or some incompatible core JS might break it. WP will most likely not upgrade it, it’s too much work and they are moving in a different direction.

CP, on the other hand, begun experimental work on upgrading TinyMCE to version 5. You can already test it using the experimental plugin and provide feedback. This, unfortunately, will be a breaking change upgrade. Some backward compatibility will be provided, but most likely WP plugins using TinyMCE will face issues if they don’t upgrade too.

We probably should do some blog posts around these issues. That will be good to share on social media. Help writing blog posts is always appreciated! However, the biggest thing we need to continue to do is to bring up CP as much as possible in conversations. Right now the main problem is still basic awareness that CP exists.

If anyone has any additional ideas, please do share.

3 Likes