Blog

@technolass Also, Disable Gutenberg/Classic Editor essentially use the same function to do the disabling. The classic editor is still in WordPress for various reasons, it's just that these plugins provide an easy way for users to do the disabling without needing to write code.

@technolass So they all work, that's not the issue. The issue is that the community as a whole is going toward an options not decisions model instead of the traditional decisions not options model, which has implications for themes and plugins. Specifically for themes, it means that designers are assuming that users now have the capability to enact whatever design decisions they choose, so designers aren't making decisions about topography ETC. So you can use Classic Editor/Disable Gutenberg with these themes, but you end up in a situation where you need to hire someone to do all theme customizations for you with regard to topography and such. Alternatively, you can tell your clients that they have to use a 6/7 year old theme and they're stuck with whatever design decisions and all the other problems Gutenberg is attempting to solve from the Classic Editor era. The latter is not an option for this organization.

Yes I'm talking about the techno group.