Steve

We also know that most plugins developer will wait for the WordPress 5.0 Beta to come around to work on making their plugins Gutenberg-ready.

The problem is that developing plugins for GB is a seriously steep learning curve – before you just needed to know php, a bit of javascript (especially if you were interacting with TinyMCE directly), and possibly some CSS, and you had access to a pretty well documented API.

Now you need to know an additional set of languages and programming skills and the GB developer documentation is, unless its changed in the past couple of weeks, woefully inadequate : documentation of simple tasks is incomplete and confusing ( https://wordpress.org/gutenberg/handbook/blocks/writing-your-first-block-type/)

The developers themselves admit that GB will break :

Plugins relying on selectors that target the post title, post content fields, and other metaboxes (of the old editor).
Plugins relying on TinyMCE’s API because there’s no longer a single TinyMCE instance to talk to in Gutenberg.
Plugins making updates to their DOM on “submit” or on “save”.

But don’t explain how, as a developer, you can fix any of these – or are they saying that as far as GB is concerned these sort of plugins are dead.

Forcing GB on people will, I suspect, kill off a lot of “hobbyist” plugins leaving only plugins developed by full time professional indy developers or big companies. Maybe that’s what Automattic want?

Name *

Email *

Website:

Topic Title (Maximum Length: 80):

Forum:
— No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor