gschoppe

I agree with the goal that Gutenberg won’t break as many sites as possible, but some breakage will occur (imagine upgrading a site that is using the current version of BoldGrid or Blockade).

I understand that this plugin is partly for demonstration purposes at the moment, but the primary driving force for non-devs to try the plugin at the moment is to see if it is actually a complete removal of Gutenberg. Their workflow is:

• install Gutenberg
• install Classic Editor
• See if all their customizations to the interface still work

Having as few steps as possible involved in the process of fully removing Gutenberg would help to ease many concerns about their upgrade paths.

I agree with Web 242. This is entirely backwards. Gutenberg is clearly plugin territory, and has no business in Core

No one wants to have to install a plugin to get a sane editor back. you have the solution completely backwards.

well, I have returned over and over to look, and I must say my review stands. Relegating metaboxes to iframes is NOT an acceptable solution, as they are sometimes the primary interface for post types, and they should not be treated as second-class citizens. WordPress has always been defined by developer freedom, and forcing developers to shoehorn their ideas into the structure of Gutenberg blocks to get a first-class experience is unacceptable. Furthermore, a comment/html structure for gutenberg blocks is entirely the wrong approach. It ignores separation of concern, and leaves every post with embedded html that may be completely deprecated in the future. JSON is how you store structure. Dont reinvent the wheel.

I find it incredible that a project that is this far off the mark is slated for merge in the next release of WordPress, and truly believe that such a merge would be disastrous for the developer ecosystem that WordPress’s success is dependent on.

I intend to take a second look, but I have to say right off the bat, the idea that page building and editing with blocks can be separated into two different concepts is deeply flawed. If my post needs columns, it needs columns in a section, not a “layout”. If you have columns as an option in the editor, then there is no logic in duplicating that functionality in layouts. All that will result is that people will re-implement page builders as blocks, and if that use case isn’t intrinsically handled smoothly, WordPress will end up in the same sort of mess it currently is with systems like Visual Composer that misuse shortcodes.