It’s most appropriate for page- or guide-type content and one set of fields that repeats once in its template, and is reused elsewhere in the site, is better for entering almost everything else. In CMSes, block editors are a really useful way to put content in a flexible structure that is pixel-perfect on the front end without requiring authors to worry about HTML or about going back and fixing old pages when the design is tweaked. Hence, other plugins are now available that duplicate that functionality as I think people don’t trust Automattic’s determination of “as long as necessary”. The intent is clearly to force people to use Gutenberg. Disabling it requires a plugin, albeit a plugin provided by Automattic themselves, which is described:Ĭlassic Editor is an official WordPress plugin, and will be fully supported and maintained until at least 2022, or as long as is necessary. Gutenberg wasn’t rolled out as an option within core, it was rolled out as the editor within core. The problem with Gutenberg is that I don’t think it actually even comes close to approaching the functionality of the other available tools.Īnd honestly, there’s a pretty vocal contingent in the WordPress open source community that are user-hostile if those users aren’t on the “progress” train. Kind of like when Apple “sherlocks” things and builds them into the OS. I think the underlying reason was to do what the other editors do, but built-in. I’m not sure what the rationale was given there were already a bunch of block editors available for WP for those who wanted them… their version didn’t add anything to the party.
0 kommentar(er)
