Wow! A lot has happened since the last round-up post. Where to begin? I just returned from WordCamp Atlanta and among other things, I listened to every Gutenberg related talk: Micah Wood, Rich Tabor and Victor Ramirez. They did a terrific job helping content creators, developers, publishers and consultants dive deeper into the most significant change in WordPress since Custom Post Types. The possibilities are endless.
There has been a lot more going in the last four weeks, and I hope you come back to this post multiple times to take it all in.
- The Accessibility Report via WPCampus was published.
- Building AMP Stories will be possible soon, check out the Alpha version of the AMP plugin
- After Drupal, another CMS OctoberCMS is testing the waters in using Gutenberg as editor, and there is a Laravel plugin called Laraberg.
- Two more version of Gutenberg plugin 5.5 and 5.6 came out.
These are only five of the 30+ other notable blog posts, plugins, themes and tutorials around the block editor listed. Enjoy! I am so glad you are here! — Yours, Birgit 💕
PS: Tell me what you enjoy or are missing, or what cool things you are working on. Or anything really. Leave a comment or write an email to firstname.lastname@example.org
Table of Contents
Using Gutenberg for Content Creators, Editors and Bloggers
“An inaccessible editing experience has real and significant consequences for many people in our community. The findings provided by Tenon are serious, and deserve to be considered with thought and care.” wrote Rachel Cherry on WPCampus.
- Executive Summary (34 pages, PDF)
- Full Technical Report (329 pages, PDF)
- The Gutenberg developers combined the 90 created issues into the Project: Accessiblity Audit. After a couple of days, 14 Issues were closed, not because they were resolved, but because they were either duplicates or reopened as Trac tickets for WordPress Core, mostly Media Library.
- May 13 – Live Webinar with TenonAPI and WPCampus
- WordPress Weekly Episode #351 with Rachel Cherry and Brian McCormick