WPWeekly Episode 337 – Gutenberg User Experiences, Release Timelines, and the Classic Editor

In this episode, John James Jacoby and I break down what’s happening with Gutenberg. We discuss our trials and tribulations with the editor, the release timeline, and calls from members of the community to delay WordPress 5.0 until January. We also share details on how long the Classic Editor plugin will be supported. Last but not least, we talk about the possible release strategy of shipping point releases every two weeks after WordPress 5.0 is released.

Stories Discussed:

How to Add an Image to A Paragraph Block in Gutenberg

Adding Aligned Images to Paragraphs in Gutenberg Is Not as Tough as I Thought

WordPress 5.0 Beta 3 Released, RC 1 Expected November 12

WordPress 5.0 needs a different timeline   

WordPress 5.0 is Not Ready

Classic Editor Plugin May Be Included with 5.0 Updates, Support Window Set to End in 2021

WPWeekly Meta:

Next Episode: Wednesday, November 14th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #337:


  1. There will be Gutenberg (block editor) user documentation in the new HelpHub that’s currently being migrated to .org by the docs team right now.

    The docs folks are working in tandem with Chris Van Patten and the Gutenberg docs team to make sure block editor docs are part of the HelpHub migration and launch. Lots of moving pieces but the teams are pushing hard to get all of that up and launched in time for the 5.0 release.



  2. I felt like applauding all the way through this podcast. I didn’t because my hands wood by bloody by the end.

    Everything you say here, the weirdly terrible project management, the creeping and drifting design by whimsical iteration, etc. Etc.

    Sometimes I feel like I’m taking crazy pills looking at this thing and simultaneously reading people acting like its all fine, like the emperor has a nice suit on.

    The emperor is heading for a very rude cold shock. This thing is terrible in so many ways. Sure it kinda works, but it has the taste of bad specifying, bad goals testing, and bad risk management. Its absurd that such a large company is so unproffesional with such a big product.

    Sometimes I have imposter syndrome when specifiying and managing client projects. Gutenberg has made me feel incredibly competent. Its insane to see. I cant beleive it’s happened this way.

    Thanks for this podcast. A small candle light of sense in some lunatic darkness.



    1. By the way – I apologise for the brutal typos in the previous post, I know they are painful to get through. I’d blame technology but it’s just a Friday issue.



  3. I agree that there are things in Gutenberg that’s a bit rough and needs more polish. But i like it anyways and i think something must be done to improve the editing capabilities in wp.

    I work as an wp instructor (the last 4 years) and have seen so many first time wp users. And i would say agood majority are disappointed in how limited you are with the editor. It’s not until they use a pagebuilder / divi they feel they can do what they need in it. More and more of them even ends up in wix…

    I’m super excited and a bit scared. It will be a bumpy next year. I’m sure. And i have some courses where pupils will start in classic the first day to be thrown into Gutenberg the next. Those will probably have the hardest time…

    I’ll see in a year or so if people struggle more or less :)

    Have you tried the Gutenberg-blocks with woocommerce? If not – do. It’s so good and shows what I think is the best thing with the flexibility with Gutenberg.

    I have a past (~1999-2014) as a web dev / dev focused on useability and are really interested in that. I have been using WordPress since 2006. Unfortunately i developed quite bad RSI that’s why i teach mostly now. But i really like to help people so that’s ok as well :)

    Thanks for a good show! Really like it!



  4. The data storage model used for Gutenberg is stupid and should not have been introduced in the first place. No amount of polish can ever fix that stupid decision.



Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.