his security and maintenance release features <a href=\"https://core.trac.wordpress.org/query?milestone=5.8.1&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priority\">60 bug</a> <a href=\"https://github.com/WordPress/gutenberg/pull/34393\">fixes</a> in addition to 3 security fixes. Because this is a <strong>security release</strong>, it is recommended that you update your sites immediately. All versions since WordPress 5.4 have also been updated.</p>\n\n\n\n<p>WordPress 5.8.1 is a short-cycle security and maintenance release. The next major release will be version <a href=\"https://make.wordpress.org/core/5-9/\">5.9</a>.</p>\n\n\n\n<p>You can download WordPress 5.8.1 by downloading from WordPress.org, or visit your Dashboard → Updates and click Update Now.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h3><strong>Security Updates</strong></h3>\n\n\n\n<p>3 security issues affect WordPress versions between 5.4 and 5.8. If you haven’t yet updated to 5.8, all WordPress versions since 5.4 have also been updated to fix the following security issues:</p>\n\n\n\n<ul><li>Props <a href=\'https://profiles.wordpress.org/mdawaffe/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>mdawaffe</a>, member of the WordPress Security Team for their work fixing a data exposure vulnerability within the REST API.</li><li>Props to Michał Bentkowski of Securitum for reporting a XSS vulnerability in the block editor.</li><li>The Lodash library has been updated to version 4.17.21 in each branch to incorporate upstream security fixes.</li></ul>\n\n\n\n<p>In addition to these issues, the security team would like to thank the following people for reporting vulnerabilities during the WordPress 5.8 beta testing period, allowing them to be fixed prior to release:</p>\n\n\n\n<ul><li>Props <a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://evanricafort.com/\">Evan Ricafort</a>&nbsp;for reporting a XSS vulnerability in the block editor discovered during the 5.8 release’s beta period.</li><li>Props <a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://profiles.wordpress.org/stevehenty/\">Steve Henty</a>&nbsp;for reporting a privilege escalation issue in the block editor.</li></ul>\n\n\n\n<p>Thank you to all of the reporters for <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">privately disclosing the vulnerabilities</a>. This gave the WordPress security team time to fix the vulnerabilities before WordPress sites could be attacked.</p>\n\n\n\n<p>For more information, browse the <a href=\"https://core.trac.wordpress.org/query?milestone=5.8.1&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priority\">full list of changes</a> on Trac, or check out the <a href=\"https://wordpress.org/support/wordpress-version/version-5-8-1/\">version 5.8.1 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks and props!</h2>\n\n\n\n<p>The 5.8.1 release was led by <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a> and <a href=\"https://profiles.wordpress.org/circlecube/\">Evan Mullins</a>.</p>\n\n\n\n<p>In addition to the security researchers and release squad members mentioned above, thank you to everyone who helped make WordPress 5.8.1 happen:</p>\n\n\n\n<a href=\"https://profiles.wordpress.org/2linctools/\">2linctools</a>, <a href=\"https://profiles.wordpress.org/zieladam/\">Adam Zielinski</a>, <a href=\"https://profiles.wordpress.org/schlessera/\">Alain Schlesser</a>, <a href=\"https://profiles.wordpress.org/ajlende/\">Alex Lende</a>, <a href=\"https://profiles.wordpress.org/alexstine/\">alexstine</a>, <a href=\"https://profiles.wordpress.org/algala/\">AlGala</a>, <a href=\"https://profiles.wordpress.org/oandregal/\">André</a>, <a href=\"https://profiles.wordpress.org/andraganescu/\">Andrei Draganescu</a>, <a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/ankitmaru/\">Ankit Panchal</a>, <a href=\"https://profiles.wordpress.org/antpb/\">Anthony Burchell</a>, <a href=\"https://profiles.wordpress.org/antonvlasenko/\">Anton Vlasenko</a>, <a href=\"https://profiles.wordpress.org/aristath/\">Ari Stathopoulos</a>, <a href=\"https://profiles.wordpress.org/ribaricplusplus/\">Bruno Ribaric</a>, <a href=\"https://profiles.wordpress.org/poena/\">Carolina Nymark</a>, <a href=\"https://profiles.wordpress.org/daisyo/\">Daisy Olsen</a>, <a href=\"https://profiles.wordpress.org/talldanwp/\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/dariak/\">Daria</a>, <a href=\"https://profiles.wordpress.org/davidanderson/\">David Anderson</a>, <a href=\"https://profiles.wordpress.org/davidbinda/\">David Biňovec</a>, <a href=\"https://profiles.wordpress.org/dlh/\">David Herrera</a>, <a href=\"https://profiles.wordpress.org/ocean90/\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\">Ella van&nbsp;Durpe</a>, <a href=\"https://profiles.wordpress.org/enchiridion/\">Enchiridion</a>, <a href=\"https://profiles.wordpress.org/circlecube/\">Evan Mullins</a>, <a href=\"https://profiles.wordpress.org/garyj/\">Gary Jones</a>, <a href=\"https://profiles.wordpress.org/mamaduka/\">George Mamadashvili</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Greg Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/priethor/\">Héctor Prieto</a>, <a href=\"https://profiles.wordpress.org/ianmjones/\">ianmjones</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/jblz/\">Jeff Bowen</a>, <a href=\"https://profiles.wordpress.org/joedolson/\">Joe Dolson</a>, <a href=\"https://profiles.wordpress.org/joen/\">Joen A.</a>, <a href=\"https://profiles.wordpress.org/johnbillion/\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/juanmaguitar/\">JuanMa Garrido</a>, <a href=\"https://profiles.wordpress.org/jrf/\">Juliette Reinders Folmer</a>, <a href=\"https://profiles.wordpress.org/kevin940726/\">Kai Hao</a>, <a href=\"https://profiles.wordpress.org/kapilpaul/\">Kapil Paul</a>, <a href=\"https://profiles.wordpress.org/gwwar/\">Kerry Liu</a>, <a href=\"https://profiles.wordpress.org/kevinfodness/\">Kevin Fodness</a>, <a href=\"https://profiles.wordpress.org/mkaz/\">Marcus Kazmierczak</a>, <a href=\"https://profiles.wordpress.org/mark-k/\">Mark-k</a>, <a href=\"https://profiles.wordpress.org/mhuntdesign/\">Matt</a>, <a href=\"https://profiles.wordpress.org/mdawaffe/\">Michael Adams (mdawaffe)</a>, <a href=\"https://profiles.wordpress.org/mikeschroder/\">Mike Schroder</a>, <a href=\"https://profiles.wordpress.org/moch11/\">moch11</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/ntsekouras/\">Nik Tsekouras</a>, <a href=\"https://profiles.wordpress.org/paaljoachim/\">Paal Joachim Romdahl</a>, <a href=\"https://profiles.wordpress.org/swissspidy/\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/pbearne/\">Paul Bearne</a>, <a href=\"https://profiles.wordpress.org/pbiron/\">Paul Biron</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/walbo/\">Petter Walbø Johnsgård</a>, <a href=\"https://profiles.wordpress.org/radixweb/\">Radixweb</a>, <a href=\"https://profiles.wordpress.org/rtm909/\">Rahul Mehta</a>, <a href=\"https://profiles.wordpress.org/ramonopoly/\">ramonopoly</a>, <a href=\"https://profiles.wordpress.org/ravipatel/\">ravipatel</a>, <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/noisysocks/\">Robert Anderson</a>, <a href=\"https://profiles.wordpress.org/kreppar/\">Rodrigo Arias</a>, <a href=\"https://profiles.wordpress.org/sanketchodavadiya/\">Sanket Chodavadiya</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/sabernhardt/\">Stephen Bernhardt</a>, <a href=\"https://profiles.wordpress.org/netweb/\">Stephen Edgar</a>, <a href=\"https://profiles.wordpress.org/stevehenty/\">Steve Henty</a>, <a href=\"https://profiles.wordpress.org/terraling/\">terraling</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/tmatsuur/\">tmatsuur</a>, <a href=\"https://profiles.wordpress.org/tobiasbg/\">TobiasBg</a>, <a href=\"https://profiles.wordpress.org/hellofromTonya/\">Tonya Mork</a>, <a href=\"https://profiles.wordpress.org/toro_unit/\">Toro_Unit (Hiroshi Urabe)</a>, <a href=\"https://profiles.wordpress.org/vladytimy/\">Vlad T</a>, <a href=\"https://profiles.wordpress.org/wb1234/\">wb1234</a>, and <a href=\"https://profiles.wordpress.org/wfmattr/\">WFMattR</a>.\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11190\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"The Month in WordPress: August 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://wordpress.org/news/2021/09/the-month-in-wordpress-august-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Sep 2021 14:00:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:7:\"updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11176\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:338:\"I really believe in WordPress’ mission to democratize publishing. And I, for one, will never stop learning about what gives people more access to the software, and what makes the software more usable, and especially how we can combine usability with accessibility in a way that puts form and function on a level playing field. [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Hari Shanker R\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:16142:\"\n<blockquote class=\"wp-block-quote\"><p>I really believe in WordPress’ mission to democratize publishing. And I, for one, will never stop learning about what gives people more access to the software, and what makes the software more usable, and especially how we can combine usability with accessibility in a way that puts form and function on a level playing field.<br></p></blockquote>\n\n\n\n<p>That was <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden</a> on the “<a href=\"https://wordpress.org/news/2021/08/episode-14-the-art-and-science-of-accessibility/\">The Art and Science of Accessibility</a>” episode of the <a href=\"https://wordpress.org/news/podcast/\">WP Briefing Podcast</a>, talking about accessibility and exploring how it applies to the WordPress open source software. You will find that many of our updates from August 2021 tie in closely with the core principles of access, accessibility, and usability. Read on to find out more!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Join the 2021 WordPress Translation Day Celebrations in September</h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://wptranslationday.org/\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" width=\"632\" height=\"395\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/09/image.jpeg?resize=632%2C395&#038;ssl=1\" alt=\"WordPress Translation Day 2021 September 1 - 30, 2021\" class=\"wp-image-11177\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2021/09/image.jpeg?resize=1024%2C640&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2021/09/image.jpeg?resize=300%2C188&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2021/09/image.jpeg?resize=768%2C480&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2021/09/image.jpeg?w=1440&amp;ssl=1 1440w, https://i0.wp.com/wordpress.org/news/files/2021/09/image.jpeg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure>\n\n\n\n<p>Join WordPress contributors around the world on <a href=\"https://wptranslationday.org/\">WordPress Translation Day celebrations</a> for the entire month of September! The sixth edition of #WPTranslationDay &#8211; which is a cross-team effort led by the Polyglots and Marketing Teams, has a host of fun programs aimed at helping WordPress speak all languages of the world. Want to join the fun? Here’s how.</p>\n\n\n\n<ul><li><a href=\"https://wptranslationday.org/wptd-2021/local-events/\">Join your local translation event</a> and collaborate on efforts to translate WordPress! Can’t find a <a href=\"https://wptranslationday.org/wptd-2021/local-events/\">local event in your area</a>? Why don’t you <a href=\"https://make.wordpress.org/polyglots/2021/08/11/call-for-local-event-organizers-wordpress-translation-day-2021/\">organize one on your own</a>?</li><li>Join <a href=\"https://wptranslationday.org/wptd-2021/global-events/\">one of our global events</a> from September 17-30!<em> </em>We have exciting sessions on <a href=\"https://wptranslationday.org/wptd-2021/global-events/\">polyglots tools and open source translation communities</a>, to name a few.</li><li>You can help<a href=\"https://translate.wordpress.org/\"> translate WordPress to your own language</a>, in your own time, this month! <a href=\"https://make.wordpress.org/polyglots/handbook/translating/first-steps/\">Here’s how!</a></li><li>Share what you are translating using the #WPTranslationDay hashtag on social media, to build excitement around the event! Don’t forget to amplify posts about the event on <a href=\"https://www.facebook.com/WPTranslationDay/\">Facebook</a>, <a href=\"https://twitter.com/TranslateWP\">Twitter</a>, <a href=\"https://www.instagram.com/wptranslationday/\">Instagram</a>, and <a href=\"https://www.linkedin.com/company/wptranslationday/\">LinkedIn</a>!</li></ul>\n\n\n\n<p>&nbsp;For more information, check out <a href=\"https://wptranslationday.org/\">the translation day website</a> and the <a href=\"https://make.wordpress.org/polylgots/tag/wptranslationday/\">Polyglots blog</a>.</p>\n\n\n\n<h2>WordPress Release Updates</h2>\n\n\n\n<p>The Core Team <a href=\"https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/\">commenced work</a> on the next major release &#8211; WordPress 5.9. The team aims to ship some cool features such as intrinsic web design to blocks, improved block patterns, navigation menus, better design tools, edit flows for block themes, and a new interface for theme.json. Check out the <a href=\"https://make.wordpress.org/core/5-9/\">WordPress 5.9 development cycle</a> to know more. This release is set to go out in December 2021. The team is also <a href=\"https://make.wordpress.org/core/2021/08/24/wordpress-5-8-x-release-team-and-5-8-1-schedule/\">working on shipping a minor release WordPress 5.8.1</a> –– its <a href=\"https://make.wordpress.org/core/2021/09/01/wordpress-5-8-1-rc-1/\">release candidate</a> is already out and the final release will launch on September 8.</p>\n\n\n\n<p>Want to contribute to WordPress core? Join the <a href=\"https://wordpress.slack.com/archives/C02RQBWTW\">#core</a> channel, follow the <a href=\"https://make.wordpress.org/core/\">Core Team blog</a>, and check out the <a href=\"https://make.wordpress.org/core/handbook/\">team handbook</a>. Don’t miss the Core Team chats on Wednesdays at <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=5&amp;min=00&amp;sec=0\">5 AM</a> and <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=20&amp;min=00&amp;sec=0\">8 PM</a> UTC. You can also help <a href=\"https://translate.wordpress.org/\">translate WordPress</a> to your local language &#8211; and what better time to do it, than in September, <a href=\"https://wptranslationday.org/\">during the translation month celebrations</a>? Another fun way to contribute would be to <a href=\"https://make.wordpress.org/marketing/2021/08/11/share-about-wordpress-5-8-on-social-media/\">share about WordPress 5.8 on social media</a>!</p>\n\n\n\n<h2>Say Hello to Gutenberg Versions 11.2 and 11.3</h2>\n\n\n\n<p>We launched Gutenberg <a href=\"https://make.wordpress.org/core/2021/08/05/whats-new-in-gutenberg-11-2-0-4-august/\">version 11.2</a> and <a href=\"https://make.wordpress.org/core/2021/08/18/whats-new-in-gutenberg-11-3-18-august/\">version 11.3</a> this month. <a href=\"https://make.wordpress.org/core/2021/08/05/whats-new-in-gutenberg-11-2-0-4-august/\">Version 11.2</a> adds customizing/color options to the search block, a flex layout for the group block, and a new button for creating posts as part of the publishing flow. <a href=\"https://make.wordpress.org/core/2021/08/18/whats-new-in-gutenberg-11-3-18-august/\">Version 11.3</a> offers a new dimensions panel (replacing the spacing panel) with more styling options, dimensions control for the feature image block, and significant performance improvements for block inserters.<br></p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core Team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the <a href=\"https://wordpress.slack.com/archives/C02QB2JS7\">#core-editor</a> channel in the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a>. The “<a href=\"https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/\">What’s next in Gutenberg</a>” post offers more details on the latest updates.&nbsp;</p>\n\n\n\n<h2>Get Excited about WordCamp US 2021</h2>\n\n\n\n<p>The biggest WordCamp in North America &#8211; <a href=\"https://us.wordcamp.org/2021/\">WordCamp US 2021-</a> is barely a month away. <a href=\"https://us.wordcamp.org/2021/tickets/\">Get your (free) tickets</a>, if you haven’t already! The organizing team has opened up calls for <a href=\"https://us.wordcamp.org/2021/calling-all-musicians/\">musicians</a>, <a href=\"https://us.wordcamp.org/2021/call-for-contributor-stories/\">contributor stories</a>, and <a href=\"https://us.wordcamp.org/2021/call-for-media-partners/\">media partners</a>. Check out <a href=\"https://us.wordcamp.org/2021/\">the event website</a> and follow the event on <a href=\"https://twitter.com/wordcampus\">Twitter</a>, <a href=\"https://www.instagram.com/wordcampus/\">Instagram</a>, and <a href=\"https://www.facebook.com/WordCampUSA\">Facebook</a> to stay updated on all that #WCUS news.</p>\n\n\n\n<h2>Important Announcements/Updates</h2>\n\n\n\n<ul><li>Support for the Classic Editor plugin <a href=\"https://wordpress.org/news/2021/08/an-update-on-the-classic-editor-plugin/\">will be extended for a full year until 2022</a>!</li><li>The Themes Team published a <a href=\"https://make.wordpress.org/themes/2021/08/06/summary-of-the-request-for-feedback-on-requirement-changes/\">feedback summary</a> on the <a href=\"https://make.wordpress.org/themes/2021/07/20/discussion-request-for-feedback-on-requirement-changes/\">proposed requirement changes for WordPress theme review</a>, and will soon be updating the handbook and review tools. You will find more context in their <a href=\"https://make.wordpress.org/themes/2021/08/10/meeting-notes-themes-team-and-theme-authors-regarding-requirements-change/\">meeting notes</a>.</li><li>The Plugins Team <a href=\"https://make.wordpress.org/plugins/2021/08/27/inaccurate-stats-have-been-corrected/\">corrected inaccurate plugin statistics</a> in the plugin directory.</li><li>Check out the <a href=\"https://make.wordpress.org/test/2021/08/17/fse-program-theme-design-survey-results/\">results of the FSE Theme Design (theme.json) survey</a>!</li></ul>\n\n\n\n<h2>Feedback/Testing Requests from Contributor Teams</h2>\n\n\n\n<ul><li>The Testing Team is requesting testing help for a <a href=\"https://make.wordpress.org/test/2021/08/30/week-in-test-30-aug-2021/\">few tickets and patches in WordPress</a>. The team is also looking for volunteers to <a href=\"https://make.wordpress.org/test/2021/08/20/call-for-volunteeers-audit-and-update-testing-instructions-across-the-make-sites/\">audit and update Core testing instructions </a>across different Make sites.</li><li>The Community Team shared a <a href=\"https://make.wordpress.org/community/2021/09/01/proposal-centralized-global-do_action-charity-hackathons/\">proposal on planning online-only recurring global do_action charity hackathons</a>. Share your feedback by September 24.</li><li>The Training Team is also exploring the possibility of adding <a href=\"https://make.wordpress.org/training/2021/08/10/proposal-learner-achievements-on-profiles/\">learner achievements (on learn.wordpress.org) on WP Profiles</a> and is requesting feedback from the community.</li><li>Help the Marketing Team’s outreach research by filling out <a href=\"https://forms.gle/4QFhX8fcNxKAfK8y5\">this 2 question survey</a> on how you search for WordPress release information. If you have any favorite features from the latest release (WordPress 5.8) let the team know by completing this <a href=\"https://docs.google.com/forms/d/e/1FAIpQLSd_2llymf79-h5sgTiprz7Kw4Gr4cbDHh-AAdAQfiArXlHksg/viewform\">short form</a>.</li><li>Version 18.1 of WordPress for <a href=\"https://make.wordpress.org/mobile/2021/08/23/call-for-testing-wordpress-for-ios-18-1/\">iOS</a> and <a href=\"https://make.wordpress.org/mobile/2021/08/23/call-for-testing-wordpress-for-android-18-1/\">Android</a> are now available for testing!</li></ul>\n\n\n\n<h2>WordPress Event Updates</h2>\n\n\n\n<ul><li><a href=\"https://floripa.wordcamp.org/2021/\">WordCamp Florianopolis 2021</a> was held on August 11-12, 2021. The event, which sold 390 tickets, had 11 speakers and 4 sponsors. Catch the <a href=\"https://www.youtube.com/channel/UCh1CeGfuDRH-o13xh7kpgUQ\">event recap on YouTube</a>!</li><li><a href=\"https://galicia.wordcamp.org/2021/\">WordCamp Galicia 2021</a> is being held from September 30 &#8211; October 2, 2021! </li><li><a href=\"https://doaction.org/event/karnataka-2021/\">do_action Karnataka 2021</a> was held from August 7-15, 2021. Check out <a href=\"https://wordpressfoundation.org/2021/do_action-karnataka-2021-a-report/\">the recap</a>!</li><li>The Core Team organized a <a href=\"https://make.wordpress.org/core/2021/08/25/hallway-hangout-summary-compare-and-contrast-the-navigation-screens/\">hallway hangout</a> to compare the ‘experimental’ Gutenberg navigation feature with the built-in core feature. The team decided to wait until feature parity with core nav menus, to move the feature from experiments to the main plugin.</li><li>The Diverse Speakers Training group (<a href=\"https://make.wordpress.org/community/tag/wpdiversity/\">#WPDiversity</a>) of the Community Team held their first “<a href=\"https://make.wordpress.org/community/2021/09/02/report-diverse-speaker-workshops-august-2021/\">Allyship for WordPress Event Organizers</a>” workshop on August 19, 2021. The event had 13 attendees from six countries who reported a 52% increase in preparedness to help create inclusive WordPress events. <a href=\"https://make.wordpress.org/community/tag/wpdiversityworkshops/\">Stay tuned</a> for their next workshop in November!</li></ul>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading</h2>\n\n\n\n<ul><li>Don’t miss this blog post on <a href=\"https://wordpress.org/news/2021/08/widgets-in-wordpress-5-8-and-beyond/\">Widgets in WordPress 5.8 and beyond</a>!</li><li>The Full Site Editing (FSE) Outreach program wrapped up its ninth challenge –– <a href=\"https://make.wordpress.org/test/2021/08/11/fse-program-testing-call-9-handling-highered-headers/\">Handling HigherEd Headers</a>, on September 1. Keep an eye out for <a href=\"https://make.wordpress.org/test/tag/fse-outreach-program/\">test results and future testing call announcements</a>!</li><li>The Test Team is <a href=\"https://make.wordpress.org/test/2021/08/19/test-team-chat-summary-17-august-2021/\">attempting to modernize PHPUnit tests</a> for WordPress.</li><li>The Accessibility Team is testing the <a href=\"https://make.wordpress.org/accessibility/2021/08/20/accessibility-team-meeting-notes-august-20-2021/\">navigation block</a> for accessibility feedback.</li><li>The Docs Team <a href=\"https://make.wordpress.org/docs/2021/08/31/summary-of-docs-team-meeting-aug-24-2021/\">launched a new repository</a> for tracking issues with WordPress documentation: <a href=\"https://github.com/WordPress/Documentation-Issue-Tracker\">https://github.com/WordPress/Documentation-Issue-Tracker</a></li><li>The Training Team <a href=\"https://make.wordpress.org/training/2021/08/17/proposal-brand-guidelines-for-learn-wordpress-content/#comment-3130\">finalized</a> brand <a href=\"https://make.wordpress.org/training/2021/08/17/proposal-brand-guidelines-for-learn-wordpress-content/\">guidelines</a> for <a href=\"https://learn.wordpress.org\">learn.wordpress.org</a>. The team is also working on setting up <a href=\"https://make.wordpress.org/training/2021/08/12/wordpress-101-microcourses-proposal/\">Micro courses for Learn</a>.</li><li>The Openverse Team is <a href=\"https://make.wordpress.org/openverse/2021/08/16/multi-stage-docker-builds-in-the-openverse-api/\">exploring Multistage docker builds</a> as a solution to better set up waveforms for audio search results in the Openverse tool.&nbsp;</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it using this form</em></a><em>.&nbsp;</em></p>\n\n\n\n<p><em>The following folks contributed to August’s Month in WordPress:&nbsp; <a href=\'https://profiles.wordpress.org/evarlese/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>evarlese</a> <a href=\'https://profiles.wordpress.org/meher/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>meher</a> <em><a href=\'https://profiles.wordpress.org/nao/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>nao</a></em> <a href=\'https://profiles.wordpress.org/jillbinder/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>jillbinder</a></em> <em><a href=\'https://profiles.wordpress.org/webcommsat/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>webcommsat</a></em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11176\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:60:\"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"An Update on the Classic Editor Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/08/an-update-on-the-classic-editor-plugin/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 25 Aug 2021 16:51:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:7:\"Updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11149\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:333:\"Before the release of WordPress 5.0 in 2018, the Classic Editor plugin was published to help ease the transition to the new block editor. At the time, we promised to support the plugin through 2021 and adjust if needed as the deadline got closer. After discussing this with Matt, it&#8217;s clear that continuing to support [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:1583:\"\n<p>Before the release of WordPress 5.0 in 2018, the <a href=\"https://wordpress.org/plugins/classic-editor/\">Classic Editor plugin</a> was published to help ease the transition to the new block editor. At the time, we promised to support the plugin through 2021 and adjust if needed as the deadline got closer. After discussing this with Matt, it&#8217;s clear that continuing to support the plugin through 2022 is the right call for the project as well as the community.</p>\n\n\n\n<p>Still, if you’ve been putting off using the block editor, this is an excellent time to give it another shot. Since it first appeared in 2018, hundreds of WordPress contributors have made a lot of updates based on user feedback. You will be pleasantly surprised at how far it’s come!</p>\n\n\n\n<p>Big thanks to everyone who has been working on WordPress, Gutenberg, and the Classic Editor plugin. And thank you to every WordPress user and tester who has provided the feedback we need to make the software even better.</p>\n\n\n\n<p>~ Josepha</p>\n\n\n\n<p><em>Returning to the block editor for the first time in a long time? You can give feedback early in the process by <a href=\"https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/\">joining the outreach program</a>! Looking at it for the first time ever? <a href=\"https://learn.wordpress.org/workshops/?series=24&amp;topic=&amp;language=&amp;captions=\">Get your bearings with some workshops</a> or <a href=\"https://wordpress.org/support/article/wordpress-editor/#how-does-the-block-editor-work\">check out this demo</a>!</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11149\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:58:\"\n		\n		\n		\n		\n		\n				\n		\n\n					\n										\n					\n		\n		\n\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"WP Briefing: Episode 15: A Very WordPress Blooper\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2021/08/episode-15-a-very-wordpress-blooper/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 23 Aug 2021 22:14:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11146\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:130:\"Ever wonder what it\'s like behind the scenes of WP Briefing? Listen in on this episode for a little levity and Josepha\'s bloopers.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:65:\"https://wordpress.org/news/files/2021/08/WP-Briefing-Bloopers.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8885:\"\n<p>Ever wonder what it&#8217;s like behind the scenes of WP Briefing? Listen in on this episode for a little levity and Josepha&#8217;s bloopers.</p>\n\n\n\n<p><em><strong>Have a question you’d like answered? You can submit them to&nbsp;<a href=\"mailto:wpbriefing@wordpress.org\">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<ul><li>Editor:&nbsp;<a href=\"https://profiles.wordpress.org/dustinhartzler/\">Dustin Hartzler</a></li><li>Logo:&nbsp;<a href=\"https://profiles.wordpress.org/beafialho/\">Beatriz Fialho</a></li><li>Production:&nbsp;<a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id=\"more-11146\"></span>\n\n\n\n<p>[contemporary intro music]</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:10</p>\n\n\n\n<p>Hello, everyone, and welcome to a bonus briefing. Normally I talk to you about WordPress and stuff, but I figured that we all need a little levity in our lives right now. So today&#8217;s episode is actually just a series of bloopers and mistakes that I&#8217;ve made while recording. When I was preparing for this podcast, no one mentioned the deep weirdness of standing alone in your closet talking to yourself, nor did they realize just how lost I can get in the surpassingly, lovely lyricism of a lilting line, and then just have no idea what I&#8217;m supposed to be reading in the script that I wrote for myself. So, my dear friends, I hope these bring you a little laugh. And if we&#8217;ve got any luck at all, you may also hear me singing to myself, my computer, or about how terrible my talking just was. Here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:12</p>\n\n\n\n<p>Hello, everyone, and welcome to a bonus briefing. I know I wasn&#8217;t going to sit boop, boop.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:21</p>\n\n\n\n<p>I messed up the thing where I&#8217;m talking about how I mess up, of course. I&#8217;m going to do it one more time, and you can choose whatever is a reasonable thing there.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:33</p>\n\n\n\n<p>Because we had such a lengthy WP Briefing, WordPress, I’m going to just start that over again. Sorry, everyone.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:42</p>\n\n\n\n<p>My friends. Oh, no. I don&#8217;t know how I end my own show. How do I end my own show? There we go. Sorry.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:52</p>\n\n\n\n<p>That was a weird way to say that. I&#8217;m going to start over again from the transition. And then we&#8217;re just going to go straight through to the end. Maybe.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:03</p>\n\n\n\n<p>The names that&#8230; I sound weird. I sound like I don&#8217;t know what my words are. And I said I wrote the words. I said I was all going to go in one go, and I&#8217;m a liar today. Okay, here we go. For realsies!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:16</p>\n\n\n\n<p>Final first last take. Here we go. Sorry, I made myself laugh.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:22</p>\n\n\n\n<p>Matt Mullenweg. And, and I, I&#8217;m also in that group. I don&#8217;t know why I said that like it was a surprise. I have me too. I&#8217;m also in there.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:33</p>\n\n\n\n<p>Ugh, I ran out of air. For reasons, it was a short sentence. I don&#8217;t know why I ran out of air.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:43</p>\n\n\n\n<p>Coming out on April 14. That&#8217;s not true. It&#8217;s April 13. Right?</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:50</p>\n\n\n\n<p>On the form below to share the. Pfft &#8211; what are the things!&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:58</p>\n\n\n\n<p>This is WP Briefing episode seven, no title because I don&#8217;t know what to call it because I gave it a title already. I gave it two titles, and then couldn&#8217;t remember why I gave it those titles. So I&#8217;ll come up with a title before we publish it. But I also have no idea what it is. I&#8217;m going to ask for help. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:17</p>\n\n\n\n<p>Testing project since I have too many commas, and I really believed in my comma when I said it. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:24</p>\n\n\n\n<p>Prior to Gutenberg&#8230; pfft. Open source software like WordPress. I was going to smash that sentence into half a sentence. I was going to say when you know what you&#8217;re workussing on you have a solution which is not my friends of thing. So, I am just going to say the sentence again. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:47</p>\n\n\n\n<p>I was sitting over here wringing my hands for some reason during that entire list. And so if you can hear me wringing my hands, which would be a whole new height of anxiety for anyone, you let me know, and I will rerecord that also.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:00</p>\n\n\n\n<p>Get a concept of. Nope, this is a lie. Get a concept of where to get your tickets is the silliest thing. I&#8217;m starting over from the small list of big things. Also, because I got too excited about how big my list is. I am going to get that excited again. But I will try not to shout about it.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:17</p>\n\n\n\n<p>&#8220;Humming intro song&#8221; Dun dun dun dun dun.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:23</p>\n\n\n\n<p>Sorry, I had to scroll up, and I try not to scroll up when I&#8217;m talking in case maybe my whole computer turns into a microphone. Sorry, I&#8217;m just going to keep going because this has been a fine take so far.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:34</p>\n\n\n\n<p>Mercy! I have words that I can say with my mouth. They aren&#8217;t these words today. It seems.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:45</p>\n\n\n\n<p>Build up to&#8230; Oh my goodness. My stomach grumbled, and this microphone, I know,&nbsp; picked it up. And so I&#8217;m going to redo bullet two so that we don&#8217;t just have a small monster under the bed in the middle of the podcast.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:03</p>\n\n\n\n<p>Also, like DEI, I feel s—Eh &#8211; maybe I should say, DEI, somewhere in there, so it&#8217;s clear for people cause I&#8217;m talking to people and not actually a screen. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:17</p>\n\n\n\n<p>Before I joined the WordPress project, the majority of my work with accessibility was in the context of the digital divide. Now, when talking about the digital divide, there are three concepts around quote-unquote, getting things to people. And those concepts are&#8230; I guess I could say the thing, hold on one second, I can do it. I feel like I&#8217;m chopping up my words like I&#8217;m not really breathing very well. So I apologize. But here we go again.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:58</p>\n\n\n\n<p>Don&#8217;t include that one. Sorry, I&#8217;m so nervous about this episode that, like, my mouth is getting dry, and I worry that you can hear it, and it drives me nuts every time I hear podcasters with a dry mouth, and you can just like hear it clicking and always stresses me out. I&#8217;m like, someone should give that poor thing a drink of water. And I just know I&#8217;m going to feel that way about myself later. And so I&#8217;m trying to stay hydrated, but it also means that I have to stop every two paragraphs and take a drink of water. I apologize for that interlude. I am about to start again, at my next section, which is like, halfway through.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:39</p>\n\n\n\n<p>Also, I learned that you can hear me swallowing my water with this microphone because it is a spectacular microphone. And so, I apologize for that as well. All right. Here I go. I&#8217;m going to do it all in one take. Watch me.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:56</p>\n\n\n\n<p>But I also have questions, especially about how to move everything forward. Mm-hmm. Whoops. I put especially in the wrong spot. But I also thought&#8230;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>07:10</p>\n\n\n\n<p> Ta da, we did it. Gosh, that&#8217;s a short one. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>07:16</p>\n\n\n\n<p>I did it. Where&#8217;s my where&#8217;s my turning offing button.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>07:22</p>\n\n\n\n<p>Tada! And scene and done.</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11146\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n\n\n\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"Widgets in WordPress 5.8 and Beyond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2021/08/widgets-in-wordpress-5-8-and-beyond/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 09 Aug 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:9:\"Gutenberg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11115\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:367:\"Copy and Design by @critterverse WordPress 5.8 brings the power of Gutenberg blocks to widget areas — which means the highly customizable layout and styling options bring you closer to a&#160;WYSIWYG editing experience. I made a test site based on the oldie-but-goodie Twenty Sixteen theme, with three separate widget areas. In this post, I’ll highlight [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:3:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/08/classic-widgets.mov\";s:6:\"length\";s:7:\"6475399\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/08/block-widgets-1.mov\";s:6:\"length\";s:8:\"23931847\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:58:\"https://wordpress.org/news/files/2021/08/custom-html-1.mov\";s:6:\"length\";s:8:\"13767042\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:7682:\"\n<p><strong><em>Copy and Design by <a href=\'https://profiles.wordpress.org/critterverse/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>critterverse</a> </em></strong></p>\n\n\n\n<p>WordPress 5.8 brings the power of Gutenberg blocks to widget areas — which means the highly customizable layout and styling options bring you closer to a&nbsp;WYSIWYG editing experience. I made a test site based on the oldie-but-goodie <a href=\"https://wordpress.org/themes/twentysixteen/\">Twenty Sixteen theme</a>, with three separate widget areas. In this post, I’ll highlight a few cool things that are now possible to do with your widgets and where things may be heading next.</p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><a href=\"https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"1130\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?resize=632%2C1130&#038;ssl=1\" alt=\"A zoomed-out view of a single post with one sidebar widget area and two footer widget areas. The site content is about Marine Park Salt Marsh. A List View of blocks floating next to each widget area shows how the design is constructed.\" class=\"wp-image-11116\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?w=2183&amp;ssl=1 2183w, https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?resize=168%2C300&amp;ssl=1 168w, https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?resize=573%2C1024&amp;ssl=1 573w, https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?resize=768%2C1373&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?resize=859%2C1536&amp;ssl=1 859w, https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?resize=1145%2C2048&amp;ssl=1 1145w, https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?w=1264&amp;ssl=1 1264w, https://i0.wp.com/wordpress.org/news/files/2021/08/site-long-1x.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a><figcaption><br><br><br><br></figcaption></figure></div>\n\n\n\n<h2>Create Interesting Visual Effects With Overlapping Layouts and Duotone Images</h2>\n\n\n\n<p>Appearance-wise, users have a lot more control over widget areas than ever before — especially through the use of blocks with customization options like the Cover and Image block. Here’s what I can create in the classic widgets editor (above) versus what I can create in the new block-based widget editor (below).</p>\n\n\n\n<figure class=\"wp-block-video aligncenter\"><video controls src=\"https://wordpress.org/news/files/2021/08/classic-widgets.mov\"></video></figure>\n\n\n\n<figure class=\"wp-block-video aligncenter\"><video controls src=\"https://wordpress.org/news/files/2021/08/block-widgets-1.mov\"></video></figure>\n\n\n\n<h2>Intersperse Widgets and Custom Code Throughout Your Visual Designs</h2>\n\n\n\n<p>Container blocks like Cover and Columns make it easy to weave dynamic or interactive elements into your designs. While this is a given for many widgets, the block versions of widgets can be easily wrapped and layered within container blocks to integrate them into your layout more fully.</p>\n\n\n\n<p>In the example below, I tried placing a Search block in front of a Cover block, which creates a nice layered effect. I also inserted Custom HTML blocks within a Columns block to display different messaging depending on the time of day. (<a href=\"https://stackoverflow.com/questions/31242051/show-content-based-on-time-of-day-timing-changes-on-different-days-of-the-week\">jQuery script</a>)</p>\n\n\n\n<figure class=\"wp-block-video aligncenter\"><video controls src=\"https://wordpress.org/news/files/2021/08/custom-html-1.mov\"></video></figure>\n\n\n\n<h2>Use Traditional Widget Layouts (Or Not) With Lots of Flexibility Over Title and Structure</h2>\n\n\n\n<p>Classic widgets have always had a lockup that includes a widget title. One cool thing about having blocks in widget areas is that you have complete flexibility over how titles appear. For example, you might choose to have a title over every widget, you might only want one title at the top of each widget area, or your design might not need titles at all.</p>\n\n\n\n<p>Note: Some themes, like <a href=\"https://wordpress.org/themes/twentytwentyone/\">Twenty Twenty-One</a>, are designed to flow content horizontally within widget areas. If you’re having trouble with a theme splitting your layout into columns, you could try keeping the lockup together by containing it within a Group block.</p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"381\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?resize=632%2C381&#038;ssl=1\" alt=\"Side-by-side comparison of List View of a Sidebar widget area with and without grouped/nested lockups.\" class=\"wp-image-11122\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?w=1760&amp;ssl=1 1760w, https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?resize=300%2C181&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?resize=1024%2C618&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?resize=768%2C463&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?resize=1536%2C927&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/08/grouped.jpg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></div>\n\n\n\n<h2>Copy &amp; Paste Existing Layouts From the WordPress Pattern Directory</h2>\n\n\n\n<p>While patterns haven’t been fully integrated into the widget editors yet, one thing you <em>can</em> do is copy and paste patterns from the game-changing new <a href=\"https://wordpress.org/patterns/\">WordPress Pattern Directory</a> into your site’s widget areas. I used this <a href=\"https://wordpress.org/patterns/pattern/horizontal-call-to-action/\">horizontal call to action</a> pattern from the directory almost exactly as is, with minor color and copy adjustments:</p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"389\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?resize=632%2C389&#038;ssl=1\" alt=\"Footer widget area with a black box that reads, “Become a monthly patron” with paragraph text and a “Join now” button in a separate column. A painted image of waves hitting rocks is directly below with no space between them.\n\" class=\"wp-image-11123\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?w=1656&amp;ssl=1 1656w, https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?resize=300%2C185&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?resize=1024%2C630&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?resize=768%2C473&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?resize=1536%2C945&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/08/footer.jpg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a><figcaption><br></figcaption></figure></div>\n\n\n\n<p>FYI: Patterns have not been curated for or integrated into widget areas yet, so you may run into some unexpected behavior — consider this feature to be a preview of what’s coming next for widget editing!</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11115\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:57:\"\n		\n		\n		\n		\n		\n				\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"The Month in WordPress: July 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2021/08/the-month-in-wordpress-july-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 03 Aug 2021 13:53:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11107\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:334:\"WordPress is global in reach and open source in nature. And you would assume that what allows the software to be used by anyone would also enable it to be built by anyone. After all, your location doesn’t matter, and who employs you also doesn’t matter. And your relative social standing certainly shouldn’t matter. As [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Hari Shanker R\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:15260:\"\n<blockquote class=\"wp-block-quote\"><p>WordPress is global in reach and open source in nature. And you would assume that what allows the software to be used by anyone would also enable it to be built by anyone. After all, your location doesn’t matter, and who employs you also doesn’t matter. And your relative social standing certainly shouldn’t matter. As long as you can communicate with the others contributing to the project, there should be no obstacle to your participation.</p></blockquote>\n\n\n\n<p class=\"has-drop-cap\">That was <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden</a> on the “<a href=\"https://wordpress.org/news/2021/07/episode-13-cherishing-wordpress-diversity/\">Cherishing WordPress Diversity</a>” episode of the <a href=\"https://wordpress.org/news/podcast/\">WP Briefing Podcast</a>, speaking about the importance of diversity, equity, and inclusion within the fabric of the WordPress project. Her statement captures the spirit of the WordPress open source project, and we hope it resonates with you. Now, let&#8217;s dive in!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Say hello to WordPress 5.8</h2>\n\n\n\n<p>WordPress <a href=\"https://wordpress.org/news/2021/07/tatum/\" target=\"_blank\" rel=\"noreferrer noopener\">version 5.8</a>, “Tatum,” came out on July 20. Version 5.8 is a major release that offers features like block-based widgets, a host of new blocks and patterns, a template editor, a duotone feature to stylize images, theme.json, and support for webP images, to name a few. Read more in the <a href=\"https://wordpress.org/news/2021/07/tatum/\">release post</a>, the <a href=\"https://make.wordpress.org/core/2021/07/03/wordpress-5-8-field-guide/\">field guide</a>, and the <a href=\"https://make.wordpress.org/community/2021/06/18/meetup-group-resources-talking-points-for-wordpress-5-8/\">talking points post for meetup groups</a>. </p>\n\n\n\n<p>Want to contribute to WordPress core?&nbsp;</p>\n\n\n\n<ul><li>Join the&nbsp; <a href=\"https://wordpress.slack.com/archives/C02RQBWTW\">#core</a> channel, follow the <a href=\"https://make.wordpress.org/core/\">Core Team blog</a>, and check out the <a href=\"https://make.wordpress.org/core/handbook/\">team handbook</a>. Don’t miss the Core Team chats on Wednesdays at <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=5&amp;min=00&amp;sec=0\">5 AM</a> and <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=20&amp;min=00&amp;sec=0\">8 PM</a> UTC.</li><li><a href=\"https://translate.wordpress.org/\">Translate WordPress</a> to your local language &#8211; here’s the <a href=\"https://make.wordpress.org/polyglots/2021/07/09/wordpress-5-8-translation-status-july-9-2020/\">latest translation status</a>.</li><li>Contact the Marketing Team in the <a href=\"https://wordpress.slack.com/archives/C0GKJ7TFA\">#marketing</a> slack channel, if you wish to support <a href=\"https://make.wordpress.org/marketing/2021/07/21/social-media-pack-for-5-8-ongoing-collaborations/\">social media engagement around WordPress 5.8</a>.</li></ul>\n\n\n\n<h2>Gutenberg Version 11.0 is released</h2>\n\n\n\n<p>Contributor teams released the <a href=\"https://make.wordpress.org/core/2021/07/09/whats-new-in-gutenberg-11-0-0-9-july/\">11th version</a> of Gutenberg on July 9. <a href=\"https://make.wordpress.org/core/2021/07/09/whats-new-in-gutenberg-11-0-0-9-july/\">Version 11.0</a>, which focuses heavily on backports and bug fixes, showcases some cool features such as an editing overlay for template parts and reusable blocks, and support for CSS shorthand properties in theme.json and block attributes. <a href=\"https://make.wordpress.org/core/2021/07/21/whats-new-in-gutenberg-11-1-0-21-july/\">Version 11.1</a> was also shipped this month, on July 21. The release adds custom block borders as block supports and adds “drag and drop” to the list view.&nbsp;</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core Team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the <a href=\"https://wordpress.slack.com/archives/C02QB2JS7\">#core-editor</a> channel in the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a>. The “<a href=\"https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/\">What’s next in Gutenberg</a>” post offers more details on the latest updates.&nbsp;</p>\n\n\n\n<h2>Returning to in-person WordPress events</h2>\n\n\n\n<p>The Community Team kicked off work to bring back in-person WordPress events. The team <a href=\"https://make.wordpress.org/community/2021/07/01/in-person-meetup-events-for-vaccinated-community-members/#comment-29654\">recently announced</a> that in-person WordPress meetups can be organized in a region if the local public health authority allows in-person events and if the region passes the in-person<a href=\"https://make.wordpress.org/community/handbook/meetup-organizer/2021-returning-to-in-person-meetups/in-person-meetup-decision-checklist/\"> safety checklist</a>. If the region does not meet guidelines on page one of the <a href=\"https://make.wordpress.org/community/handbook/meetup-organizer/2021-returning-to-in-person-meetups/in-person-meetup-decision-checklist/\">safety checklist</a>, organizers can plan events for fully vaccinated, recently tested (negative), or recently recovered community members. Subsequently, the team also <a href=\"https://make.wordpress.org/community/2021/07/27/proposal-how-to-return-to-safe-in-person-wordcamps/\">shared a proposal for the return to in-person WordCamps</a> in places that meet the <a href=\"https://make.wordpress.org/community/handbook/meetup-organizer/2021-returning-to-in-person-meetups/in-person-meetup-decision-checklist/\">safety guidelines and the vaccination/testing requirements</a>. Please share your feedback on the post if you have any thoughts. For more context, check out the “<a href=\"https://wordpress.org/news/2021/07/episode-12-wordpress-in-person/\">In Person!</a>” episode of the <a href=\"https://wordpress.org/news/podcast/\">WP Briefing Podcast</a>.&nbsp;</p>\n\n\n\n<p>Want to contribute to the Community Team? Follow the <a href=\"https://make.wordpress.org/community/\">Community Team</a> blog, or join them in the <a href=\"https://wordpress.slack.com/archives/C037W5S7X\">#community</a> channel in the Make WordPress Slack.&nbsp;</p>\n\n\n\n<h2>BuddyPress 9.0 is out</h2>\n\n\n\n<p>The BuddyPress team is busy! Within barely a month of their last major release (<a href=\"https://buddypress.org/2021/06/buddypress-8-0-0-alfano/\">version 8.0)</a>, the team shipped <a href=\"https://buddypress.org/2021/07/buddypress-9-0-0-mico/\">version 9.0</a> on July 19. Key features of the release include widget blocks and updates to the BP REST API.&nbsp; Download it from the <a href=\"https://wordpress.org/plugins/buddypress/\">WordPress.org plugin directory</a> or check it out from its <a href=\"https://buddypress.trac.wordpress.org/browser/branches/9.0\">subversion repository.</a> Want to help build BuddyPress? Follow their <a href=\"https://bpdevel.wordpress.com/\">developer relations blog</a>, check out their <a href=\"https://codex.buddypress.org/participate-and-contribute/contribute-with-code/\">handbook page</a>, or join them in the <a href=\"https://wordpress.slack.com/archives/C02RQBYUG\">#buddypress</a> channel in the Make WordPress Slack.</p>\n\n\n\n<h2>WordPress Event updates</h2>\n\n\n\n<ul><li>WordCamp US is coming back on October 1, 2021, <a href=\"https://us.wordcamp.org/2021/wordcamp-us-is-back/\">as a daylong online event</a>!</li><li>Free tickets for <a href=\"https://floripa.wordcamp.org/2021/inscricoes/\">WordCamp Florianopolis</a> (August 11-12) are now available.</li><li>The <a href=\"https://make.wordpress.org/community/tag/wpdiversity/\">Diverse Speaker Training group</a> of the Community Team announced <a href=\"https://make.wordpress.org/community/2021/07/26/announcement-and-call-for-volunteers-expanding-wpdiversity-to-three-programs/\">three new programs</a> for Meetup and WordCamp organizers. Sign up for the <a href=\"https://make.wordpress.org/community/2021/07/30/workshop-august-19-2021-allyship-for-wordpress-event-organizers-amer-emea/\">inaugural allyship program for event organizers</a> on August 19, 2021, at <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210819T1700\">5:00</a> &#8211; <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210819T1900\">7:00 pm</a> UTC!</li><li>The Polyglots Team is planning a <a href=\"https://make.wordpress.org/polyglots/tag/wptranslationday/\">month-long translation day celebration in September 2021</a>, with two weeks of “core events” from September 17 to 30. The team will announce more details on the event shortly, and you <a href=\"https://make.wordpress.org/polyglots/tag/wptranslationday/\">can follow all the latest updates on their P2</a>.&nbsp;</li><li>Stay updated on <a href=\"https://make.wordpress.org/community/events/online/\">online WordPress meetups</a> around the world by following the Marketing Team’s <a href=\"https://www.linkedin.com/company/make-wordpress-marketing-team/\">WordPress Meetup roundup</a> every Monday.&nbsp;</li><li><a href=\"https://santaclarita.wordcamp.org/2021/\">WordCamp Santa Clarita 2021</a> was held online on July 17-18, 2021. The highlight of the event, which had 41 speakers, 19 sponsors, and 672 attendees, was a <a href=\"https://santaclarita.wordcamp.org/2021/schedule/\">dedicated track for WordPress accessibility</a>. Videos of the event will soon be posted on WordPress.tv.</li><li>The Hosting Team organized <a href=\"https://www.meetup.com/wphosting/events/278295555\">their first meetup</a> in June. Check out the <a href=\"https://www.youtube.com/watch?v=V4UCc1Bze5E&amp;t=702s\">event recording</a>.</li></ul>\n\n\n\n<h2>Feedback requests from WordPress contributor teams</h2>\n\n\n\n<p>Please help these WordPress contributor teams by answering their research requests:</p>\n\n\n\n<ul><li>The Core Team has published a <a href=\"https://make.wordpress.org/core/2021/07/28/wordpress-5-8-tatum-retrospective/\">WordPress 5.8 release retrospective</a>. Share your release feedback as <a href=\"https://make.wordpress.org/core/2021/07/28/wordpress-5-8-tatum-retrospective/#respond\">comments on the post</a> or by <a href=\"https://docs.google.com/forms/d/e/1FAIpQLSei8fSLjV0um4hk_1JKwgu-8E6mpNwwxF3j43mInW7lnVOTDw/viewform?usp=sf_link\">filling out this form</a> before August 15. The team is also <a href=\"https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/\">requesting feedback</a> on a “proof of concept” for the new WordPress updater.&nbsp;</li><li>The Training Team wishes to <a href=\"https://make.wordpress.org/training/2021/07/30/learn-wordpress-user-survey-focus-groups/\">find what learners and potential learners would like to see</a> in the <a href=\"https://learn.wordpress.org\">learn.wordpress.org</a> platform. To contribute, please <a href=\"https://www.surveymonkey.com/r/LearnWordPress\">fill out an anonymous survey</a> (by August 13) OR <a href=\"https://forms.gle/jdk2qkkvGyszx1SG6\">join a short video call</a> to share feedback (on the week of August 2-6).</li><li>The Polyglots Team <a href=\"https://make.wordpress.org/polyglots/2021/07/19/polyglots-training-ready-for-testing/\">announced</a> that “Polyglots Training” (a course to help WordPress translators and communities) is now available for testing. <a href=\"https://make.wordpress.org/polyglots/2021/07/19/polyglots-training-ready-for-testing/\">Sign up now</a>!</li><li>The Test Team wants to<a href=\"https://make.wordpress.org/test/2021/07/30/help-shape-the-future-of-theme-design/\"> hear from theme authors</a> on how they use theme.json in order to shape its future. Help them by <a href=\"https://wordpressdotorg.survey.fm/block-theme-author-feedback\">filling out this survey</a> on or before August 13.</li><li>The Marketing Team is doing research on building engagement around WordPress releases. Please help the team by filling out <a href=\"https://forms.gle/4QFhX8fcNxKAfK8y5\">this quick, two-question survey</a> on how you search for release information. If you have any favorite features from the latest release (WordPress 5.8) let the team know by completing this <a href=\"https://docs.google.com/forms/d/e/1FAIpQLSd_2llymf79-h5sgTiprz7Kw4Gr4cbDHh-AAdAQfiArXlHksg/viewform\">short form</a>.</li></ul>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further reading</h2>\n\n\n\n<ul><li>The Meta Team launched the new <a href=\"https://make.wordpress.org/meta/2021/07/20/the-wordpress-pattern-directory-is-live/\">WordPress Pattern Directory</a> alongside the 5.8 release. The Design Team also contributed to this project, working with contributors on <a href=\"https://make.wordpress.org/design/2021/07/29/initial-patterns-for-the-patterns-directory-launched/\">launching around 85 block patterns in the directory</a>.</li><li>Check out the following blog posts from the Design Team: <a href=\"https://make.wordpress.org/design/2021/07/13/a-walk-around-the-search-block/\">A Walk Around: The Search Block</a> and <a href=\"https://make.wordpress.org/design/2021/07/27/widgets-in-wordpress-5-8-and-beyond/\">Widgets on 5.8 and beyond</a>. Join their <a href=\"https://make.wordpress.org/design/?s=show+and+tell\">Show and Tell meetings</a> on the last Wednesday of each month to learn about updates on their latest projects and new ideas.</li><li>Check out <a href=\"https://wordpress.org/news/2021/07/configuring-theme-design-with-theme-json/\">this blog post</a> to learn how to configure theme design with theme.json.&nbsp;</li><li>The Test Team has put out a <a href=\"https://make.wordpress.org/test/2021/07/20/test-team-reps-call-for-nominations/\">call for team-rep nominations</a>.</li><li>The Themes Team is in the process of discussing <a href=\"https://make.wordpress.org/themes/2021/07/20/discussion-request-for-feedback-on-requirement-changes/\">updated theme directory guidelines</a>.</li><li>Version 17.9 of WordPress for <a href=\"https://make.wordpress.org/mobile/2021/07/27/call-for-testing-wordpress-for-android-17-9/\">Android</a> and <a href=\"https://make.wordpress.org/mobile/2021/07/28/call-for-testing-wordpress-for-ios-17-9/\">iOS</a> are now available for testing.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it using this form</em></a><em>.&nbsp;</em></p>\n\n\n\n<p><em>The following folks contributed to July’s Month in WordPress:&nbsp; <a href=\'https://profiles.wordpress.org/webcommsat/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>webcommsat</a> <a href=\'https://profiles.wordpress.org/chaion07/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chaion07</a> <a href=\'https://profiles.wordpress.org/jillbinder/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>jillbinder</a> <a href=\'https://profiles.wordpress.org/lmurillom/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>lmurillom</a> <a href=\'https://profiles.wordpress.org/meher/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>meher</a></em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11107\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:58:\"\n		\n		\n		\n		\n		\n				\n		\n\n					\n										\n					\n		\n		\n\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"WP Briefing: Episode 14: The Art and Science of Accessibility\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://wordpress.org/news/2021/08/episode-14-the-art-and-science-of-accessibility/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 02 Aug 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11096\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:463:\"In this episode, Josepha Haden Chomphosy discusses the nuances of building accessible software, the differences between access, usability, and accessibility, and how this all applies to the WordPress project. Have a question you’d like answered? You can submit them to&#160;wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor:&#160;Dustin Hartzler Logo:&#160;Beatriz Fialho Production:&#160;Chloé Bringmann Transcription: [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/07/WP-Briefing-014.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Nicholas Garofalo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:9393:\"\n<p>In this episode, Josepha Haden Chomphosy discusses the nuances of building accessible software, the differences between access, usability, and accessibility, and how this all applies to the WordPress project.</p>\n\n\n\n<p><em><strong>Have a question you’d like answered? You can submit them to&nbsp;<a href=\"mailto:wpbriefing@wordpress.org\">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<ul><li>Editor:&nbsp;<a href=\"https://profiles.wordpress.org/dustinhartzler/\">Dustin Hartzler</a></li><li>Logo:&nbsp;<a href=\"https://profiles.wordpress.org/beafialho/\">Beatriz Fialho</a></li><li>Production:&nbsp;<a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a></li><li>Transcription: <a href=\"https://profiles.wordpress.org/eidolonnight/\">Nicholas Garofalo</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>\n\n\n\n<h2>References</h2>\n\n\n\n<ul><li><a href=\"https://wordpress.org/about/accessibility/\">About WordPress Accessibility</a></li><li><a href=\"https://make.wordpress.org/accessibility/\">Make WordPress Accessibility Team</a></li><li><a href=\"https://twitter.com/wpaccessibility\">WordPress Accessibility Team Twitter</a></li><li><a href=\"https://make.wordpress.org/accessibility/handbook/best-practices/\">WordPress Accessibility Handbook</a></li><li><a href=\"https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/\">Accessibility Coding Standards</a></li><li><a href=\"https://www.w3.org/WAI/intro/wcag\">Web Content Accessibility Guidelines (WCAG)</a></li><li><a href=\"https://www.a11yproject.com/checklist/\">A11y Checklist</a></li><li><a href=\"https://en.wikipedia.org/wiki/Digital_divide\">The Digital Divide</a></li></ul>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id=\"more-11096\"></span>\n\n\n\n<p>[contemporary intro music]</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 0:10</p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Josepha Haden Chomphosy. Here we go.</p>\n\n\n\n<p>[musical interlude]</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 0:28</p>\n\n\n\n<p>This is the second of my big scary topics for this month. I&#8217;ll be talking about accessibility, which much like Diversity, Equity and Inclusion, or DEI in the last episode, is one of those areas where the work is never finished. Also, like DEI in last episode, I feel strongly about accessibility and the need for accessible experiences in the world, but I&#8217;m aware that this is an area where I&#8217;m still learning.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 1:04</p>\n\n\n\n<p>WordPress has both an accessibility statement and team, which makes a lot of sense given that the software supports so many different people, and industries, and cultures. But if you&#8217;re not quite bought into the idea that software should be accessible, or that accessible software can&#8217;t also be usable, then this is the episode for you.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 1:25</p>\n\n\n\n<p>Before I joined the WordPress project, the majority of my work with accessibility was in the context of the digital divide. Now, when talking about the digital divide, there are three concepts around quote-unquote, &#8220;getting things to people,&#8221; and those are access, usability, and accessibility. Sometimes these words seem interchangeable, but ultimately they have nuanced differences that address different problems. And I like to think of them this way.</p>\n\n\n\n<p>Access is making sure that someone can obtain something.</p>\n\n\n\n<p>Usability is making sure that the user experience is understandable or coherent.</p>\n\n\n\n<p>And accessibility is making sure that it&#8217;s usable by the largest number of people.</p>\n\n\n\n<p>I have always considered each as a subset of the one that came before it. So having something everyone can access is good, but easy to access and easy to use is better. Easy to use is good, but easy to use and easily accessible is better.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 2:27</p>\n\n\n\n<p>After joining WordPress, I discovered that accessibility in the context of software building is well, substantially more complicated. There&#8217;s no such thing as perfect accessibility, or a site that is 100% accessible, and many aspects are pretty open to interpretation. It turns out that accessibility, like so many things in WordPress, is a complicated intersection of art and science.</p>\n\n\n\n<p>As an example, there&#8217;s a rule that says, &#8220;Ensure that links are recognizable as links.&#8221; A fast shorthand to accomplish that, that we see all over the internet, is to underline all links or put that icon next to it that says, &#8220;This opens in a new tab.&#8221; You know that icon that&#8217;s a box with an arrow? That definitely has a name, that I definitely don&#8217;t know? That icon. [laughing] But those solutions don&#8217;t necessarily fit every context that you&#8217;ll find a link in, and that&#8217;s where we see that intersection between the art of communication and the science of necessity.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 3:32</p>\n\n\n\n<p>If you came with me earlier on the idea that accessibility is a subset of usability, and it&#8217;s not a far leap to say that the choices around accessibility implementations should always include design and the overall user experience.</p>\n\n\n\n<p>I know that some of you are thinking, &#8220;But we have guidelines! Like, that&#8217;s why we have the guidelines, so that not everything has to be a gray area.&#8221; And on the one hand, yeah, that&#8217;s true. There are a lot of guidelines. There are guidelines for the code, and what the code produces, and the design elements. But I worry that when a solution is driven solely by rules, rather than reasons, we run the risk of throwing out the good along with the bad.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 4:15</p>\n\n\n\n<p>Accessibility has been a consistent topic of debate in the project for as long as I can remember, and based on all of this, it&#8217;s really clear why. There are a few big picture questions that still deserve some sort of canonical answer for WordPress, and where possible I dig in and research the positions that everyone has taken in the past. But I also have questions about how to move everything forward, especially as the editing experience gets more and more standardized across the software, which reduces cognitive load, shortens the learning curve, etc.</p>\n\n\n\n<p>What is the future possibility for having a series of more niche admin interface options?</p>\n\n\n\n<p>What would it be like to be able to account for functional limitations in a way that lets site builders select what is needed for their clients or organization, or just individual situations they know their sites would be maintained under?</p>\n\n\n\n<p>What more could we do if part of the setup flow of WordPress was to select some bundle of potential add ons for neuro diversity, or colorblindness, or dyslexia, and more?</p>\n\n\n\n<p>It&#8217;s a really big question I have.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 5:26</p>\n\n\n\n<p>And I have to be really transparent here and share that my foundational understanding of accessibility and usability is 10 plus years old, and I learned it in the context of people in education, not software. So a lot of my questions about the future of accessibility and WordPress is the result of old knowledge exploring new spaces, which means they are a little untested. And I&#8217;m so grateful for the contributors who point out what the current research and thinking is, in this incredibly complex field.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 6:00</p>\n\n\n\n<p>I normally like to wrap up the briefing with a tidy takeaway, but this particular topic doesn&#8217;t really lend itself to that. So I&#8217;ll leave you with this. I really believe in WordPress&#8217; mission to democratize publishing. And I, for one, will never stop learning about what gives people more access to the software, and what makes the software more usable, and especially how we can combine usability with accessibility in a way that puts form and function on a level playing field.</p>\n\n\n\n<p>[musical interlude]</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 6:40</p>\n\n\n\n<p>And now, that brings us to our small list of big things.</p>\n\n\n\n<p>Thing one, it&#8217;s that time of year where many of our community members take a short break to relax and refresh. I&#8217;ll be taking a bit of a break during the month of August, and so the WP Briefing will return again starting in September.</p>\n\n\n\n<p>And thing two, huge thanks to the production crew that helps me make this podcast every couple of weeks, but a special shout out to our editor Dustin Hartzler, who makes quick work of all of my rambling thoughts.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> 7:09</p>\n\n\n\n<p>And that is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I&#8217;m your host, Josepha Haden Chomphosy, and I&#8217;ll see you again in September.</p>\n\n\n\n<p>[contemporary outro music]</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11096\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:66:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"Configuring Theme Design with theme.json\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://wordpress.org/news/2021/07/configuring-theme-design-with-theme-json/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 29 Jul 2021 22:26:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{i:0;a:5:{s:4:\"data\";s:6:\"Themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:6:\"design\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:9:\"Gutenberg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11060\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:368:\"Starting in WordPress 5.8, a new tool — “theme.json” — is available to use in your theme. Maybe you’re hearing about it for the first time, or maybe you’re testing and developing themes with it already. Either way, I&#8217;m glad you&#8217;re here because it&#8217;s an exciting time for WordPress themes. This post provides a quick introduction [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Jeff Ong\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:21957:\"\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"356\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?resize=632%2C356&#038;ssl=1\" alt=\"\" class=\"wp-image-11082\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?resize=1024%2C576&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?resize=300%2C169&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?resize=768%2C432&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?resize=1536%2C864&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?resize=2048%2C1152&amp;ssl=1 2048w, https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?w=1264&amp;ssl=1 1264w, https://i2.wp.com/wordpress.org/news/files/2021/07/themejson-1.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>Starting in <a href=\"https://wordpress.org/news/2021/07/tatum/\">WordPress 5.8</a>, a new tool — “theme.json” — is available to use in your theme. Maybe you’re hearing about it for the first time, or maybe you’re testing and developing themes with it already. Either way, I&#8217;m glad you&#8217;re here because it&#8217;s an exciting time for WordPress themes.</p>\n\n\n\n<p>This post provides a quick introduction to this new framework, and describes what’s possible by sharing a few practical tips and examples.</p>\n\n\n\n<h2>What’s theme.json?</h2>\n\n\n\n<p>Technically, theme.json is just a file that lives at the top-level of a theme’s directory.&nbsp;</p>\n\n\n\n<p>Conceptually, it’s a major shift in how themes can be developed. Theme authors now have a centralized mechanism to tailor the WordPress experience for site authors and visitors. Theme.json provides theme authors fine-grained control over global styles, block styles, and the block editor settings.</p>\n\n\n\n<p>By providing these settings and controls in a single file, theme.json provides a powerful framework that brings together many aspects of theme design and development. And as the block editor matures and adds more features, theme.json will shine as the backbone for themes and the editor to work <em>together</em> <img src=\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f4aa.png\" alt=\"💪\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" />. </p>\n\n\n\n<h2>Why Use it?</h2>\n\n\n\n<p>It’s the future! But if you’re like me, you might need something more tangible to be convinced. Here are a few reasons why you might use theme.json today:</p>\n\n\n\n<ul><li>Control editor settings like color, typography, spacing, and layout, and consolidate where these settings are managed.</li><li>Guarantee that styles apply correctly to blocks and elements across your site.</li><li>Reduce the amount of boilerplate CSS a theme used to provide. Theme.json won&#8217;t replace your stylesheet completely — there will be instances where CSS is needed to give your theme that extra flare (transitions, animations, etc.). But it can greatly reduce the base CSS needed from the theme.</li></ul>\n\n\n\n<h2>How do I use it?</h2>\n\n\n\n<p>The rest of this post demonstrates a few theme.json configurations you can try out. The examples use the tt1-blocks<a href=\"https://github.com/WordPress/theme-experiments/blob/master/tt1-blocks/theme.json\"> theme.json</a> — <a href=\"https://wordpress.org/themes/tt1-blocks/\">the block-based version of this year’s default theme</a>. </p>\n\n\n\n<p>If you&#8217;re starting with an existing theme, you might try copying a theme.json from the <a href=\"https://github.com/WordPress/theme-experiments/\">WordPress/theme-experiments repository</a> (for example, <a href=\"https://github.com/WordPress/theme-experiments/blob/master/fse-tutorial/theme.json\">the fse-tutorial theme</a> by <a href=\"https://profiles.wordpress.org/poena/\">@poena</a>) and adding it to the root of your theme’s directory.</p>\n\n\n\n<h3><strong>Change the typography settings of your site globally</strong></h3>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: jscript; title: ; notranslate\">\n&quot;settings&quot;: {\n	&quot;typography&quot;: {\n		&quot;fontSize&quot;: &quot;30px&quot;,\n		...\n</pre></div>\n\n\n<p>Making the change above in theme.json would result in the following updates to your theme&#8217;s body typography styles (before and after): </p>\n\n\n\n<figure class=\"wp-block-gallery columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"398\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?resize=632%2C398&#038;ssl=1\" alt=\"\" data-id=\"11062\" data-full-url=\"https://wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png\" data-link=\"https://wordpress.org/news/?attachment_id=11062\" class=\"wp-image-11062\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?resize=1024%2C645&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?resize=300%2C189&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?resize=768%2C484&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?resize=1536%2C968&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?resize=2048%2C1291&amp;ssl=1 2048w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?w=1264&amp;ssl=1 1264w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.06.07-AM.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li><li class=\"blocks-gallery-item\"><figure><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"398\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?resize=632%2C398&#038;ssl=1\" alt=\"\" data-id=\"11061\" data-full-url=\"https://wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png\" data-link=\"https://wordpress.org/news/?attachment_id=11061\" class=\"wp-image-11061\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?resize=1024%2C645&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?resize=300%2C189&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?resize=768%2C484&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?resize=1536%2C968&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?resize=2048%2C1291&amp;ssl=1 2048w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?w=1264&amp;ssl=1 1264w, https://i1.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.05.40-AM.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li></ul></figure>\n\n\n\n<h3><strong>Changing the base color settings of your site globally</strong></h3>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: jscript; title: ; notranslate\">\n&quot;styles&quot;: {\n	&quot;color&quot;: {\n		&quot;background&quot;: &quot;#ffc0cb&quot;,\n		&quot;text&quot;: &quot;#6A1515&quot;\n	},\n	...\n}\n</pre></div>\n\n\n<figure class=\"wp-block-gallery columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><a href=\"https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"398\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?resize=632%2C398&#038;ssl=1\" alt=\"\" data-id=\"11063\" data-full-url=\"https://wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png\" data-link=\"https://wordpress.org/news/?attachment_id=11063\" class=\"wp-image-11063\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?resize=1024%2C645&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?resize=300%2C189&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?resize=768%2C484&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?resize=1536%2C968&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?resize=2048%2C1291&amp;ssl=1 2048w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?w=1264&amp;ssl=1 1264w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.10.03-AM.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li><li class=\"blocks-gallery-item\"><figure><a href=\"https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"398\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?resize=632%2C398&#038;ssl=1\" alt=\"\" data-id=\"11064\" data-full-url=\"https://wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png\" data-link=\"https://wordpress.org/news/?attachment_id=11064\" class=\"wp-image-11064\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?resize=1024%2C645&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?resize=300%2C189&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?resize=768%2C484&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?resize=1536%2C968&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?resize=2048%2C1291&amp;ssl=1 2048w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?w=1264&amp;ssl=1 1264w, https://i2.wp.com/wordpress.org/news/files/2021/07/Screen-Shot-2021-07-23-at-11.08.54-AM.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li></ul></figure>\n\n\n\n<h3><strong><strong>Changing spacing / padding settings on specific blocks</strong></strong></h3>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: jscript; title: ; notranslate\">\n&quot;styles&quot;: {\n	&quot;blocks&quot;: {\n		&quot;core/code&quot;: {\n			&quot;spacing&quot;: {\n				&quot;padding&quot;: {\n					&quot;top&quot;: &quot;3em&quot;,\n					&quot;bottom&quot;: &quot;3em&quot;,\n					&quot;left&quot;: &quot;3em&quot;,\n					&quot;right&quot;: &quot;3em&quot;\n				}\n			}\n		}\n	}\n}\n\n</pre></div>\n\n\n<figure class=\"wp-block-gallery columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><a href=\"https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"356\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?resize=632%2C356&#038;ssl=1\" alt=\"\" data-id=\"11065\" data-full-url=\"https://wordpress.org/news/files/2021/07/code-padding-original.png\" data-link=\"https://wordpress.org/news/?attachment_id=11065\" class=\"wp-image-11065\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?resize=1024%2C576&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?resize=300%2C169&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?resize=768%2C432&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?resize=1536%2C864&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?w=1600&amp;ssl=1 1600w, https://i2.wp.com/wordpress.org/news/files/2021/07/code-padding-original.png?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li><li class=\"blocks-gallery-item\"><figure><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/07/code-padding-edited.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"356\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/07/code-padding-edited-1024x576.png?resize=632%2C356&#038;ssl=1\" alt=\"\" data-id=\"11066\" data-full-url=\"https://wordpress.org/news/files/2021/07/code-padding-edited.png\" data-link=\"https://wordpress.org/news/?attachment_id=11066\" class=\"wp-image-11066\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/code-padding-edited.png?resize=1024%2C576&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/code-padding-edited.png?resize=300%2C169&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/code-padding-edited.png?resize=768%2C432&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/code-padding-edited.png?resize=1536%2C864&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/07/code-padding-edited.png?w=1600&amp;ssl=1 1600w, https://i1.wp.com/wordpress.org/news/files/2021/07/code-padding-edited.png?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li></ul></figure>\n\n\n\n<h3><strong><strong>Set a custom color palette in the editor for specific blocks like a button </strong></strong></h3>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: jscript; title: ; notranslate\">\n&quot;settings&quot;: {\n    &quot;blocks&quot;: {\n		&quot;core/button&quot;: {\n			&quot;color&quot;: {\n				&quot;palette&quot;: &#91; \n					{\n						&quot;name&quot;: &quot;Maroon&quot;,\n						&quot;color&quot;: &quot;#6A1515&quot;,\n						&quot;slug&quot;: &quot;maroon&quot;\n					},\n					{\n						&quot;name&quot;: &quot;Strawberry Ice Cream&quot;,\n						&quot;color&quot;: &quot;#FFC0CB&quot;,\n						&quot;slug&quot;: &quot;strawberry-ice-cream&quot;\n					}\n				]\n			}\n		}\n	}\n}\n</pre></div>\n\n\n<figure class=\"wp-block-gallery columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><a href=\"https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"444\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?resize=632%2C444&#038;ssl=1\" alt=\"\" data-id=\"11069\" data-full-url=\"https://wordpress.org/news/files/2021/07/button-all-colors.png\" data-link=\"https://wordpress.org/news/?attachment_id=11069\" class=\"wp-image-11069\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?resize=1024%2C719&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?resize=300%2C211&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?resize=768%2C539&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?resize=1536%2C1079&amp;ssl=1 1536w, https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?resize=2048%2C1438&amp;ssl=1 2048w, https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?w=1264&amp;ssl=1 1264w, https://i0.wp.com/wordpress.org/news/files/2021/07/button-all-colors.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li><li class=\"blocks-gallery-item\"><figure><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"444\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?resize=632%2C444&#038;ssl=1\" alt=\"\" data-id=\"11070\" data-full-url=\"https://wordpress.org/news/files/2021/07/buttons-custom-palette.png\" data-link=\"https://wordpress.org/news/?attachment_id=11070\" class=\"wp-image-11070\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?resize=1024%2C719&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?resize=300%2C211&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?resize=768%2C539&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?resize=1536%2C1079&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?resize=2048%2C1438&amp;ssl=1 2048w, https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?w=1264&amp;ssl=1 1264w, https://i1.wp.com/wordpress.org/news/files/2021/07/buttons-custom-palette.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li></ul></figure>\n\n\n\n<h3><strong><strong>Enable and disable typography controls</strong></strong></h3>\n\n\n\n<p>In the following example, the ability to supply a custom font size and line height for all heading blocks is disabled:</p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: jscript; title: ; notranslate\">\n	&quot;settings&quot;: {\n		&quot;blocks&quot;: {\n			&quot;core/heading&quot;: {\n				&quot;typography&quot;: {\n					&quot;customFontSize&quot;: false,\n					&quot;customLineHeight&quot;: false\n				}\n			}\n		}\n	}\n</pre></div>\n\n\n<figure class=\"wp-block-gallery columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"444\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?resize=632%2C444&#038;ssl=1\" alt=\"\" data-id=\"11071\" data-full-url=\"https://wordpress.org/news/files/2021/07/heading-all-options.png\" data-link=\"https://wordpress.org/news/?attachment_id=11071\" class=\"wp-image-11071\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?resize=1024%2C719&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?resize=300%2C211&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?resize=768%2C539&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?resize=1536%2C1079&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?resize=2048%2C1438&amp;ssl=1 2048w, https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?w=1264&amp;ssl=1 1264w, https://i1.wp.com/wordpress.org/news/files/2021/07/heading-all-options.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li><li class=\"blocks-gallery-item\"><figure><a href=\"https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"444\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?resize=632%2C444&#038;ssl=1\" alt=\"\" data-id=\"11072\" data-full-url=\"https://wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png\" data-link=\"https://wordpress.org/news/?attachment_id=11072\" class=\"wp-image-11072\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?resize=1024%2C719&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?resize=300%2C211&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?resize=768%2C539&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?resize=1536%2C1079&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?resize=2048%2C1438&amp;ssl=1 2048w, https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?w=1264&amp;ssl=1 1264w, https://i2.wp.com/wordpress.org/news/files/2021/07/heading-no-line-height-custom-size.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure></li></ul></figure>\n\n\n\n<h2>What&#8217;s Next?</h2>\n\n\n\n<p>I hope this gives you a sense of what&#8217;s possible and where themes are going. The above examples just scratch the surface of what kinds of theme design configurations are possible, and I’m very excited to see what theme authors create.</p>\n\n\n\n<p>If you&#8217;re interested in learning more, <a href=\"https://make.wordpress.org/core/2021/06/25/introducing-theme-json-in-wordpress-5-8/\">here&#8217;s the developer note on theme.json</a>, and <a href=\"https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/\">here&#8217;s the documentation for theme.json</a> in the handbook.</p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><em><strong>Thanks to <a href=\"https://profiles.wordpress.org/kjellr/\">@kjellr</a>, <a href=\"https://profiles.wordpress.org/chanthaboune/\">@</a></strong></em><strong><em><a href=\"https://profiles.wordpress.org/chanthaboune/\">chanthaboune</a>, <a href=\"https://profiles.wordpress.org/priethor/\">@priethor</a>, <a href=\"https://profiles.wordpress.org/annezazu/\">@annezazu</a> for helping with and peer-reviewing this post.</em></strong></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11060\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:60:\"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"WordPress 5.8 Tatum\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://wordpress.org/news/2021/07/tatum/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 20 Jul 2021 17:43:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10976\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:277:\"Introducing 5.8 “Tatum”, our latest and greatest release, named in honor of the legendary jazz pianist Art Tatum. This release includes an all new widget editor powered by blocks, major technical tools for building block themes, as well as newly streamlined workflow tools.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:55737:\"\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"422\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/07/5x8-Album-1.jpg?resize=632%2C422&#038;ssl=1\" alt=\"\" class=\"wp-image-11042\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>Introducing 5.8 “Tatum”, our latest and greatest release now available for&nbsp;<a href=\"https://wordpress.org/download/\">download</a>&nbsp;or update in your dashboard. Named in honor of Art Tatum, the legendary Jazz pianist. His formidable technique and willingness to push boundaries inspired musicians and changed what people thought could be done.&nbsp;</p>\n\n\n\n<p>So fire up your music service of choice and enjoy Tatum’s famous recordings of ‘Tea for Two’, ‘Tiger Rag’, ‘Begin the Beguine’, and ‘Night and Day’ as you read about what the latest WordPress version brings to you.</p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<h2 class=\"has-text-align-center\">Three Essential Powerhouses</h2>\n\n\n\n<div style=\"height:16px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<figure class=\"wp-block-gallery columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><img loading=\"lazy\" width=\"632\" height=\"474\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/07/about-widgets-blocks.png?resize=632%2C474&#038;ssl=1\" alt=\"\" data-id=\"10985\" data-full-url=\"https://wordpress.org/news/files/2021/07/about-widgets-blocks.png\" data-link=\"https://wordpress.org/news/?attachment_id=10985\" class=\"wp-image-10985\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/about-widgets-blocks.png?resize=1024%2C768&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-widgets-blocks.png?resize=300%2C225&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-widgets-blocks.png?resize=768%2C576&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-widgets-blocks.png?w=1280&amp;ssl=1 1280w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></li><li class=\"blocks-gallery-item\"><figure><img loading=\"lazy\" width=\"632\" height=\"501\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/about-query-loop.png?resize=632%2C501&#038;ssl=1\" alt=\"\" data-id=\"10986\" data-full-url=\"https://wordpress.org/news/files/2021/07/about-query-loop.png\" data-link=\"https://wordpress.org/news/?attachment_id=10986\" class=\"wp-image-10986\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/about-query-loop.png?resize=1024%2C811&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-query-loop.png?resize=300%2C238&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-query-loop.png?resize=768%2C608&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-query-loop.png?w=1280&amp;ssl=1 1280w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></li><li class=\"blocks-gallery-item\"><figure><img loading=\"lazy\" width=\"632\" height=\"411\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/about-template.png?resize=632%2C411&#038;ssl=1\" alt=\"\" data-id=\"10987\" data-full-url=\"https://wordpress.org/news/files/2021/07/about-template.png\" data-link=\"https://wordpress.org/news/?attachment_id=10987\" class=\"wp-image-10987\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/about-template.png?resize=1024%2C666&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-template.png?resize=300%2C195&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-template.png?resize=768%2C499&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-template.png?w=1280&amp;ssl=1 1280w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></li></ul></figure>\n\n\n\n<h3>Manage Widgets with Blocks</h3>\n\n\n\n<p>After months of hard work, the power of blocks has come to both the Block Widgets Editor and the Customizer. Now you can add blocks both in widget areas across your site and with live preview through the Customizer. This opens up new possibilities to create content: from no-code mini layouts to the vast library of core and third-party blocks. For our developers, you can find more details in the&nbsp;<a href=\"https://make.wordpress.org/core/2021/06/29/block-based-widgets-editor-in-wordpress-5-8/\">Widgets dev note</a>.</p>\n\n\n\n<h3>Display Posts with New Blocks and Patterns</h3>\n\n\n\n<p>The Query Loop Block makes it possible to display posts based on specified parameters; like a PHP loop without the code. Easily display posts from a specific category, to do things like create a portfolio or a page full of your favorite recipes. Think of it as a more complex and powerful Latest Posts Block! Plus, pattern suggestions make it easier than ever to create a list of posts with the design you want.</p>\n\n\n\n<h3>Edit the Templates Around Posts</h3>\n\n\n\n<p>You can use the familiar block editor to edit templates that hold your content—simply activate a block theme or a theme that has opted in for this feature. Switch from editing your posts to editing your pages and back again, all while using a familiar block editor. There are more than 20 new blocks available within compatible themes. Read more about this feature and how to experiment with it in the release notes.</p>\n\n\n\n<div style=\"height:32px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<h2 class=\"has-text-align-center\">Three Workflow Helpers</h2>\n\n\n\n<div style=\"height:16px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<figure class=\"wp-block-gallery columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><img loading=\"lazy\" width=\"632\" height=\"496\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/07/about-list-view.png?resize=632%2C496&#038;ssl=1\" alt=\"\" data-id=\"10988\" data-full-url=\"https://wordpress.org/news/files/2021/07/about-list-view.png\" data-link=\"https://wordpress.org/news/?attachment_id=10988\" class=\"wp-image-10988\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/about-list-view.png?resize=1024%2C803&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-list-view.png?resize=300%2C235&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-list-view.png?resize=768%2C602&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-list-view.png?w=1280&amp;ssl=1 1280w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></li><li class=\"blocks-gallery-item\"><figure><img loading=\"lazy\" width=\"632\" height=\"343\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/07/about-pattern-suggestions.png?resize=632%2C343&#038;ssl=1\" alt=\"\" data-id=\"10989\" data-full-url=\"https://wordpress.org/news/files/2021/07/about-pattern-suggestions.png\" data-link=\"https://wordpress.org/news/?attachment_id=10989\" class=\"wp-image-10989\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/07/about-pattern-suggestions.png?resize=1024%2C555&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-pattern-suggestions.png?resize=300%2C163&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-pattern-suggestions.png?resize=768%2C416&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/07/about-pattern-suggestions.png?w=1280&amp;ssl=1 1280w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></li><li class=\"blocks-gallery-item\"><figure><img loading=\"lazy\" width=\"632\" height=\"517\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/07/about-duotone.png?resize=632%2C517&#038;ssl=1\" alt=\"\" data-id=\"10990\" data-full-url=\"https://wordpress.org/news/files/2021/07/about-duotone.png\" data-link=\"https://wordpress.org/news/?attachment_id=10990\" class=\"wp-image-10990\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2021/07/about-duotone.png?resize=1024%2C837&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2021/07/about-duotone.png?resize=300%2C245&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2021/07/about-duotone.png?resize=768%2C628&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2021/07/about-duotone.png?w=1280&amp;ssl=1 1280w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></li></ul></figure>\n\n\n\n<h3>Overview of the Page Structure</h3>\n\n\n\n<p>Sometimes you need a simple landing page, but sometimes you need something a little more robust. As blocks increase, patterns emerge, and content creation gets easier, new solutions are needed to make complex content easy to navigate. List View is the best way to jump between layers of content and nested blocks. Since the List View gives you an overview of all the blocks in your content, you can now navigate quickly to the precise block you need. Ready to focus completely on your content? Toggle it on or off to suit your workflow.</p>\n\n\n\n<h3>Suggested Patterns for Blocks</h3>\n\n\n\n<p>Starting in this release the Pattern Transformations tool will suggest block patterns based on the block you are using. Right now, you can give it a try in the Query Block and Social Icon Block. As more patterns are added, you will be able to get inspiration for how to style your site without ever leaving the editor!</p>\n\n\n\n<h3>Style and Colorize Images</h3>\n\n\n\n<p>Colorize your image and cover blocks with duotone filters! Duotone can add a pop of color to your designs and style your images (or videos in the cover block) to integrate well with your themes. You can think of the duotone effect as a black and white filter, but instead of the shadows being black and the highlights being white, you pick your own colors for the shadows and highlights. There’s more to learn about how it works in the documentation.</p>\n\n\n\n<div style=\"height:32px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<h2 class=\"has-text-align-center\">For Developers to Explore</h2>\n\n\n\n<div style=\"height:16px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"378\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?resize=632%2C378&#038;ssl=1\" alt=\"\" class=\"wp-image-10992\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?resize=1024%2C613&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?resize=300%2C179&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?resize=768%2C459&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?resize=1536%2C919&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?resize=2048%2C1225&amp;ssl=1 2048w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?w=1264&amp;ssl=1 1264w, https://i1.wp.com/wordpress.org/news/files/2021/07/about-theme-json-2x.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<div style=\"height:16px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<h3>Theme.json</h3>\n\n\n\n<p>Introducing the Global Styles and Global Settings APIs: control the editor settings, available customization tools, and style blocks using a theme.json file in the active theme. This configuration file enables or disables features and sets default styles for both a website and blocks. If you build themes, you can experiment with this early iteration of a useful new feature. For more about what is currently available and how it works,&nbsp;<a href=\"https://make.wordpress.org/core/2021/06/25/introducing-theme-json-in-wordpress-5-8/\">check out this dev note</a>.</p>\n\n\n\n<div style=\"height:16px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<div class=\"wp-block-columns\">\n<div class=\"wp-block-column\">\n<h3>Dropping support for IE11</h3>\n\n\n\n<p>Support for Internet Explorer 11 has been dropped as of this release. This means you may have issues managing your site that will not be fixed in the future. If you are currently using IE11, it is strongly recommended that you&nbsp;<a href=\"https://browsehappy.com/\">switch to a more modern browser</a>.</p>\n</div>\n\n\n\n<div class=\"wp-block-column\">\n<h3>Adding support for WebP</h3>\n\n\n\n<p>WebP is a modern image format that provides improved lossless and lossy compression for images on the web. WebP images are around 30% smaller on average than their JPEG or PNG equivalents, resulting in sites that are faster and use less bandwidth.</p>\n</div>\n</div>\n\n\n\n<h3>Adding Additional Block Supports</h3>\n\n\n\n<p>Expanding on previously implemented block supports in WordPress&nbsp;<a href=\"https://make.wordpress.org/core/2020/11/18/block-supports-in-wordpress-5-6/\">5.6</a>&nbsp;and&nbsp;<a href=\"https://make.wordpress.org/core/2021/02/24/changes-to-block-editor-components-and-blocks/\">5.7</a>, WordPress 5.8 introduces several new block support flags and new options to customize your registered blocks. More information is available in the&nbsp;<a href=\"https://make.wordpress.org/core/2021/06/25/block-supports-api-updates-for-wordpress-5-8/\">block supports dev note</a>.</p>\n\n\n\n<div style=\"height:16px\" aria-hidden=\"true\" class=\"wp-block-spacer\"></div>\n\n\n\n<h3>Check the Field Guide for more!</h3>\n\n\n\n<p>Check out the latest version of the WordPress Field Guide. It highlights developer notes for each change you may want to be aware of:&nbsp;<a href=\"https://make.wordpress.org/core/2021/07/03/wordpress-5-8-field-guide/\">WordPress 5.8 Field Guide.</a></p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<h2>The Squad</h2>\n\n\n\n<p>The WordPress 5.8 release was led by <a href=\"https://profiles.wordpress.org/matt/\">Matt Mullenweg</a>, and supported by this highly enthusiastic release squad:</p>\n\n\n\n<ul><li><strong>Release Co-Coordinator:</strong>&nbsp;Jeffrey Paul (<a href=\'https://profiles.wordpress.org/jeffpaul/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>jeffpaul</a>)</li><li><strong>Release Co-Coordinator:</strong>&nbsp;Jonathan Desrosiers (<a href=\'https://profiles.wordpress.org/desrosj/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>desrosj</a>)</li><li><strong>Editor Tech Lead:</strong>&nbsp;Riad Benguella (<a href=\'https://profiles.wordpress.org/youknowriad/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>youknowriad</a>)</li><li><strong>Marketing and Communications Lead:</strong> Josepha Haden Chomphosy (<a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a>)</li><li><strong>Documentation Lead:</strong> Milana Cap (<a href=\'https://profiles.wordpress.org/milana_cap/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>milana_cap</a>)</li><li><strong>Test Lead:</strong>&nbsp;Piotrek Boniu (<a href=\'https://profiles.wordpress.org/boniu91/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>boniu91</a>)</li><li><strong>Support Lead:&nbsp;</strong>Mary Job (<a href=\'https://profiles.wordpress.org/mariaojob/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>mariaojob</a>)</li></ul>\n\n\n\n<p>This release is the reflection of the hard work of 530 generous volunteer contributors. Collaboration occurred on over <a href=\"https://core.trac.wordpress.org/query?milestone=5.8&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priority\">320 tickets on Trac</a> and over <a href=\"https://github.com/wordpress/gutenberg/compare/v10.0.0...v10.7.0\">1,500 pull requests on GitHub</a>.</p>\n\n\n\n<a href=\"https://profiles.wordpress.org/2linctools/\">2linctools</a>, <a href=\"https://profiles.wordpress.org/5ubliminal/\">5ubliminal</a>, <a href=\"https://profiles.wordpress.org/ninetyninew/\">99w</a>, <a href=\"https://profiles.wordpress.org/9primus/\">9primus</a>, <a href=\"https://profiles.wordpress.org/jorbin/\">Aaron Jorbin</a>, <a href=\"https://profiles.wordpress.org/aaronrobertshaw/\">Aaron Robertshaw</a>, <a href=\"https://profiles.wordpress.org/abderrahman/\">abderrahman</a>, <a href=\"https://profiles.wordpress.org/webcommsat/\">Abha Thakor</a>, <a href=\"https://profiles.wordpress.org/abhijitrakas/\">Abhijit Rakas</a>, <a href=\"https://profiles.wordpress.org/achbed/\">achbed</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein/\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/zieladam/\">Adam Zielinski</a>, <a href=\"https://profiles.wordpress.org/addiestavlo/\">Addie</a>, <a href=\"https://profiles.wordpress.org/aduth/\">aduth</a>, <a href=\"https://profiles.wordpress.org/chaion07/\">Ahmed Chaion</a>, <a href=\"https://profiles.wordpress.org/engahmeds3ed/\">Ahmed Saeed</a>, <a href=\"https://profiles.wordpress.org/ajitbohra/\">Ajit Bohra</a>, <a href=\"https://profiles.wordpress.org/schlessera/\">Alain Schlesser</a>, <a href=\"https://profiles.wordpress.org/alanjacobmathew/\">Alan Jacob Mathew</a>, <a href=\"https://profiles.wordpress.org/aljullu/\">Albert Juh&#233; Lluveras</a>, <a href=\"https://profiles.wordpress.org/aleperez92/\">Alejandro Perez</a>, <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha</a>, <a href=\"https://profiles.wordpress.org/akirk/\">Alex Kirk</a>, <a href=\"https://profiles.wordpress.org/ajlende/\">Alex Lende</a>, <a href=\"https://profiles.wordpress.org/alexstine/\">alexstine</a>, <a href=\"https://profiles.wordpress.org/algala/\">AlGala</a>, <a href=\"https://profiles.wordpress.org/firewatch/\">allilevine</a>, <a href=\"https://profiles.wordpress.org/amandariu/\">Amanda Riu</a>, <a href=\"https://profiles.wordpress.org/amarinediary/\">amarinediary</a>, <a href=\"https://profiles.wordpress.org/gadgetroid/\">Amogh Harish</a>, <a href=\"https://profiles.wordpress.org/oandregal/\">Andr&#233;</a>, <a href=\"https://profiles.wordpress.org/afercia/\">Andrea Fercia</a>, <a href=\"https://profiles.wordpress.org/andraganescu/\">Andrei Draganescu</a>, <a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/andrewserong/\">Andrew Serong</a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey \"Rarst\" Savchenko</a>, <a href=\"https://profiles.wordpress.org/nosolosw/\">André Maneiro</a>, <a href=\"https://profiles.wordpress.org/afragen/\">Andy Fragen</a>, <a href=\"https://profiles.wordpress.org/apeatling/\">Andy Peatling</a>, <a href=\"https://profiles.wordpress.org/andy/\">Andy Skelton</a>, <a href=\"https://profiles.wordpress.org/wpgurudev/\">Ankit Gade</a>, <a href=\"https://profiles.wordpress.org/ankitmaru/\">Ankit Panchal</a>, <a href=\"https://profiles.wordpress.org/annalamprou/\">annalamprou</a>, <a href=\"https://profiles.wordpress.org/annezazu/\">Anne McCarthy</a>, <a href=\"https://profiles.wordpress.org/anotherdave/\">anotherdave</a>, <a href=\"https://profiles.wordpress.org/anotia/\">anotia</a>, <a href=\"https://profiles.wordpress.org/antpb/\">Anthony Burchell</a>, <a href=\"https://profiles.wordpress.org/antonlukin/\">Anton Lukin</a>, <a href=\"https://profiles.wordpress.org/vanyukov/\">Anton Vanyukov</a>, <a href=\"https://profiles.wordpress.org/antonvlasenko/\">Anton Vlasenko</a>, <a href=\"https://profiles.wordpress.org/antonisme/\">Antonis Lilis</a>, <a href=\"https://profiles.wordpress.org/apedog/\">apedog</a>, <a href=\"https://profiles.wordpress.org/apokalyptik/\">apokalyptik</a>, <a href=\"https://profiles.wordpress.org/arena/\">arena</a>, <a href=\"https://profiles.wordpress.org/lephleg/\">Argyris Margaritis</a>, <a href=\"https://profiles.wordpress.org/aristath/\">Ari Stathopoulos</a>, <a href=\"https://profiles.wordpress.org/ariskataoka/\">ariskataoka</a>, <a href=\"https://profiles.wordpress.org/arkrs/\">arkrs</a>, <a href=\"https://profiles.wordpress.org/aruphi/\">Armand</a>, <a href=\"https://profiles.wordpress.org/arnaudban/\">ArnaudBan</a>, <a href=\"https://profiles.wordpress.org/arthur791004/\">Arthur Chu</a>, <a href=\"https://profiles.wordpress.org/arunsathiya/\">Arun</a>, <a href=\"https://profiles.wordpress.org/aspexi/\">Aspexi</a>, <a href=\"https://profiles.wordpress.org/atjn/\">atjn</a>, <a href=\"https://profiles.wordpress.org/aurooba/\">Aurooba Ahmed</a>, <a href=\"https://profiles.wordpress.org/filosofo/\">Austin Matzko</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans/\">Ayesh Karunaratne</a>, <a href=\"https://profiles.wordpress.org/barry/\">Barry</a>, <a href=\"https://profiles.wordpress.org/bartkalisz/\">bartkalisz</a>, <a href=\"https://profiles.wordpress.org/beafialho/\">Beatriz Fialho</a>, <a href=\"https://profiles.wordpress.org/pixolin/\">Bego Mario Garde</a>, <a href=\"https://profiles.wordpress.org/utz119/\">Benachi</a>, <a href=\"https://profiles.wordpress.org/benoitchantre/\">Benoit Chantre</a>, <a href=\"https://profiles.wordpress.org/bernhard-reiter/\">Bernhard Reiter</a>, <a href=\"https://profiles.wordpress.org/bernhard reiter/\">Bernhard Reiter</a>, <a href=\"https://profiles.wordpress.org/birgire/\">Birgir Erlendsson (birgire)</a>, <a href=\"https://profiles.wordpress.org/bph/\">Birgit Pauli-Haack</a>, <a href=\"https://profiles.wordpress.org/blobfolio/\">Blobfolio</a>, <a href=\"https://profiles.wordpress.org/bmcculley/\">bmcculley</a>, <a href=\"https://profiles.wordpress.org/boblinthorst/\">Bob Linthorst</a>, <a href=\"https://profiles.wordpress.org/bobbingwide/\">bobbingwide</a>, <a href=\"https://profiles.wordpress.org/bogdanpreda/\">Bogdan Preda</a>, <a href=\"https://profiles.wordpress.org/gitlost/\">bonger</a>, <a href=\"https://profiles.wordpress.org/boonebgorges/\">Boone Gorges</a>, <a href=\"https://profiles.wordpress.org/bradt/\">Brad Touesnard</a>, <a href=\"https://profiles.wordpress.org/kraftbj/\">Brandon Kraft</a>, <a href=\"https://profiles.wordpress.org/brechtvds/\">Brecht</a>, <a href=\"https://profiles.wordpress.org/brentswisher/\">Brent Swisher</a>, <a href=\"https://profiles.wordpress.org/brettshumaker/\">Brett Shumaker</a>, <a href=\"https://profiles.wordpress.org/ribaricplusplus/\">Bruno Ribaric</a>, <a href=\"https://profiles.wordpress.org/burhandodhy/\">Burhan Nasir</a>, <a href=\"https://profiles.wordpress.org/cameronjonesweb/\">Cameron Jones</a>, <a href=\"https://profiles.wordpress.org/cvoell/\">Cameron Voell</a>, <a href=\"https://profiles.wordpress.org/carike/\">Carike</a>, <a href=\"https://profiles.wordpress.org/carlalexander/\">Carl Alexander</a>, <a href=\"https://profiles.wordpress.org/carlomanf/\">carlomanf</a>, <a href=\"https://profiles.wordpress.org/carlosgprim/\">Carlos Garcia Prim</a>, <a href=\"https://profiles.wordpress.org/poena/\">Carolina Nymark</a>, <a href=\"https://profiles.wordpress.org/caseymilne/\">Casey Milne</a>, <a href=\"https://profiles.wordpress.org/cenay/\">Cenay Nailor</a>, <a href=\"https://profiles.wordpress.org/ceyhun0/\">Ceyhun Ozugur</a>, <a href=\"https://profiles.wordpress.org/nhuja/\">Chandra M</a>, <a href=\"https://profiles.wordpress.org/chetan200891/\">Chetan Prajapati</a>, <a href=\"https://profiles.wordpress.org/chintan1896/\">Chintan hingrajiya</a>, <a href=\"https://profiles.wordpress.org/chipsnyder/\">Chip Snyder</a>, <a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a>, <a href=\"https://profiles.wordpress.org/chouby/\">Chouby</a>, <a href=\"https://profiles.wordpress.org/chrisvanpatten/\">Chris Van Patten</a>, <a href=\"https://profiles.wordpress.org/chriscct7/\">chriscct7</a>, <a href=\"https://profiles.wordpress.org/vimes1984/\">Christopher Churchill</a>, <a href=\"https://profiles.wordpress.org/ryno267/\">Chuck Reynolds</a>, <a href=\"https://profiles.wordpress.org/claytoncollie/\">Clayton Collie</a>, <a href=\"https://profiles.wordpress.org/codeamp/\">Code Amp</a>, <a href=\"https://profiles.wordpress.org/design_dolphin/\">CodePoet</a>, <a href=\"https://profiles.wordpress.org/costdev/\">Colin Stewart</a>, <a href=\"https://profiles.wordpress.org/collizo4sky/\">Collins Agbonghama</a>, <a href=\"https://profiles.wordpress.org/copons/\">Copons</a>, <a href=\"https://profiles.wordpress.org/coreymckrill/\">Corey McKrill</a>, <a href=\"https://profiles.wordpress.org/cr0ybot/\">Cory Hughart</a>, <a href=\"https://profiles.wordpress.org/courane01/\">Courtney Engle Robertson</a>, <a href=\"https://profiles.wordpress.org/crazycoders/\">crazycoders</a>, <a href=\"https://profiles.wordpress.org/critterverse/\">critterverse</a>, <a href=\"https://profiles.wordpress.org/davidszabo/\">D&#225;vid Szab&#243;</a>, <a href=\"https://profiles.wordpress.org/daisyo/\">Daisy Olsen</a>, <a href=\"https://profiles.wordpress.org/damonganto/\">damonganto</a>, <a href=\"https://profiles.wordpress.org/danfarrow/\">Dan Farrow</a>, <a href=\"https://profiles.wordpress.org/diddledan/\">Dani Llewellyn</a>, <a href=\"https://profiles.wordpress.org/talldanwp/\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/danieldudzic/\">danieldudzic</a>, <a href=\"https://profiles.wordpress.org/mte90/\">Daniele Scasciafratte</a>, <a href=\"https://profiles.wordpress.org/vetyst/\">Danny</a>, <a href=\"https://profiles.wordpress.org/dariak/\">Daria</a>, <a href=\"https://profiles.wordpress.org/davilera/\">David Aguilera</a>, <a href=\"https://profiles.wordpress.org/davidanderson/\">David Anderson</a>, <a href=\"https://profiles.wordpress.org/dartiss/\">David Artiss</a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\">David Baumwald</a>, <a href=\"https://profiles.wordpress.org/davidbinda/\">David Biňovec</a>, <a href=\"https://profiles.wordpress.org/dpcalhoun/\">David Calhoun</a>, <a href=\"https://profiles.wordpress.org/dlh/\">David Herrera</a>, <a href=\"https://profiles.wordpress.org/davidkryzaniak/\">David Kryzaniak</a>, <a href=\"https://profiles.wordpress.org/get_dave/\">David Smith</a>, <a href=\"https://profiles.wordpress.org/dekervit/\">dekervit</a>, <a href=\"https://profiles.wordpress.org/devle/\">devfle</a>, <a href=\"https://profiles.wordpress.org/devrekli/\">devrekli</a>, <a href=\"https://profiles.wordpress.org/dhruvkb/\">dhruvkb</a>, <a href=\"https://profiles.wordpress.org/dianeco/\">Diane Co</a>, <a href=\"https://profiles.wordpress.org/dingdang/\">dingdang</a>, <a href=\"https://profiles.wordpress.org/dd32/\">Dion Hulse</a>, <a href=\"https://profiles.wordpress.org/djbu/\">djbu</a>, <a href=\"https://profiles.wordpress.org/ocean90/\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/donmhico/\">donmhico</a>, <a href=\"https://profiles.wordpress.org/donnapep/\">Donna Peplinskie</a>, <a href=\"https://profiles.wordpress.org/dougwollison/\">Doug Wollison</a>, <a href=\"https://profiles.wordpress.org/dpik/\">dpik</a>, <a href=\"https://profiles.wordpress.org/dragongate/\">dragongate</a>, <a href=\"https://profiles.wordpress.org/drebbitsweb/\">Dreb Bits</a>, <a href=\"https://profiles.wordpress.org/drewapicture/\">Drew Jaynes</a>, <a href=\"https://profiles.wordpress.org/eatsleepcode/\">eatsleepcode</a>, <a href=\"https://profiles.wordpress.org/metalandcoffee/\">Ebonie Butler</a>, <a href=\"https://profiles.wordpress.org/ediamin/\">Edi Amin</a>, <a href=\"https://profiles.wordpress.org/itsjusteileen/\">Eileen Violini</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\">Ella van Durpe</a>, <a href=\"https://profiles.wordpress.org/aliveic/\">Emil E</a>, <a href=\"https://profiles.wordpress.org/emarticor/\">Emilio Martinez</a>, <a href=\"https://profiles.wordpress.org/manooweb/\">Emmanuel Hesry</a>, <a href=\"https://profiles.wordpress.org/empatogen/\">empatogen</a>, <a href=\"https://profiles.wordpress.org/enchiridion/\">Enchiridion</a>, <a href=\"https://profiles.wordpress.org/enej/\">Enej Bajgorić</a>, <a href=\"https://profiles.wordpress.org/nrqsnchz/\">Enrique S&#225;nchez</a>, <a href=\"https://profiles.wordpress.org/epiqueras/\">epiqueras</a>, <a href=\"https://profiles.wordpress.org/kebbet/\">Erik</a>, <a href=\"https://profiles.wordpress.org/etoledom/\">etoledom</a>, <a href=\"https://profiles.wordpress.org/circlecube/\">Evan Mullins</a>, <a href=\"https://profiles.wordpress.org/fabiankaegy/\">Fabian K&#228;gy</a>, <a href=\"https://profiles.wordpress.org/fabianpimminger/\">Fabian Pimminger</a>, <a href=\"https://profiles.wordpress.org/gaambo/\">Fabian Todt</a>, <a href=\"https://profiles.wordpress.org/felipeelia/\">Felipe Elia</a>, <a href=\"https://profiles.wordpress.org/flixos90/\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/felixbaumgaertner/\">felixbaumgaertner</a>, <a href=\"https://profiles.wordpress.org/femkreations/\">Femy Praseeth</a>, <a href=\"https://profiles.wordpress.org/fijisunshine/\">fijisunshine</a>, <a href=\"https://profiles.wordpress.org/florianbrinkmann/\">Florian Brinkmann</a>, <a href=\"https://profiles.wordpress.org/mista-flo/\">Florian TIAR</a>, <a href=\"https://profiles.wordpress.org/francina/\">Francesca Marano</a>, <a href=\"https://profiles.wordpress.org/bueltge/\">Frank Bueltge</a>, <a href=\"https://profiles.wordpress.org/frosso1/\">frosso1 (a11n)</a>, <a href=\"https://profiles.wordpress.org/fullofcaffeine/\">fullofcaffeine</a>, <a href=\"https://profiles.wordpress.org/gab81/\">gab81</a>, <a href=\"https://profiles.wordpress.org/galbaras/\">Gal Baras</a>, <a href=\"https://profiles.wordpress.org/kafleg/\">Ganga Kafle</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse/\">Garrett Hyder</a>, <a href=\"https://profiles.wordpress.org/garyj/\">Gary Jones</a>, <a href=\"https://profiles.wordpress.org/pento/\">Gary Pendergast</a>, <a href=\"https://profiles.wordpress.org/geekpress/\">GeekPress</a>, <a href=\"https://profiles.wordpress.org/soulseekah/\">Gennady Kovshenin</a>, <a href=\"https://profiles.wordpress.org/geoffrey1963/\">Geoffrey</a>, <a href=\"https://profiles.wordpress.org/revgeorge/\">George Hotelling</a>, <a href=\"https://profiles.wordpress.org/mamaduka/\">George Mamadashvili</a>, <a href=\"https://profiles.wordpress.org/georgestephanis/\">George Stephanis</a>, <a href=\"https://profiles.wordpress.org/geriux/\">geriux</a>, <a href=\"https://profiles.wordpress.org/glendaviesnz/\">glendaviesnz</a>, <a href=\"https://profiles.wordpress.org/grantmkin/\">Grant M. Kinney</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Greg Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/gregorlove/\">gRegor Morrill</a>, <a href=\"https://profiles.wordpress.org/priethor/\">H&#233;ctor Prieto</a>, <a href=\"https://profiles.wordpress.org/hannahmalcolm/\">Hannah Malcolm</a>, <a href=\"https://profiles.wordpress.org/happiryu/\">happiryu</a>, <a href=\"https://profiles.wordpress.org/hareesh-pillai/\">Hareesh</a>, <a href=\"https://profiles.wordpress.org/hazdiego/\">Haz</a>, <a href=\"https://profiles.wordpress.org/hedgefield/\">hedgefield</a>, <a href=\"https://profiles.wordpress.org/helen/\">Helen Hou-Sandí</a>, <a href=\"https://profiles.wordpress.org/hermpheus/\">Herm Martini</a>, <a href=\"https://profiles.wordpress.org/herregroen/\">Herre Groen</a>, <a href=\"https://profiles.wordpress.org/herrvigg/\">herrvigg</a>, <a href=\"https://profiles.wordpress.org/htmgarcia/\">htmgarcia</a>, <a href=\"https://profiles.wordpress.org/iandunn/\">Ian Dunn</a>, <a href=\"https://profiles.wordpress.org/ianmjones/\">ianmjones</a>, <a href=\"https://profiles.wordpress.org/icopydoc/\">icopydoc</a>, <a href=\"https://profiles.wordpress.org/ipstenu/\">Ipstenu (Mika Epstein)</a>, <a href=\"https://profiles.wordpress.org/isabel_brison/\">Isabel Brison</a>, <a href=\"https://profiles.wordpress.org/dragunoff/\">Ivaylo Draganov</a>, <a href=\"https://profiles.wordpress.org/wphound/\">Ivete Tecedor</a>, <a href=\"https://profiles.wordpress.org/jdgrimes/\">J.D. Grimes</a>, <a href=\"https://profiles.wordpress.org/jacklenox/\">Jack Lenox</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\">Jake Spurlock</a>, <a href=\"https://profiles.wordpress.org/jamesbonham/\">James Bonham</a>, <a href=\"https://profiles.wordpress.org/jameskoster/\">James Koster</a>, <a href=\"https://profiles.wordpress.org/jnylen0/\">James Nylen</a>, <a href=\"https://profiles.wordpress.org/pondermatic/\">James Richards</a>, <a href=\"https://profiles.wordpress.org/jamesros161/\">James Rosado</a>, <a href=\"https://profiles.wordpress.org/jamil95/\">jamil95</a>, <a href=\"https://profiles.wordpress.org/janak007/\">janak Kaneriya</a>, <a href=\"https://profiles.wordpress.org/janwoostendorp/\">janw.oostendorp</a>, <a href=\"https://profiles.wordpress.org/jsnjohnston/\">Jason Johnston</a>, <a href=\"https://profiles.wordpress.org/javiarce/\">Javier Arce</a>, <a href=\"https://profiles.wordpress.org/jaymanpandya/\">Jayman Pandya</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jean-Baptiste Audras</a>, <a href=\"https://profiles.wordpress.org/jblz/\">Jeff Bowen</a>, <a href=\"https://profiles.wordpress.org/jffng/\">Jeff Ong</a>, <a href=\"https://profiles.wordpress.org/jeffpaul/\">Jeff Paul</a>, <a href=\"https://profiles.wordpress.org/jeffikus/\">Jeffrey Pearce</a>, <a href=\"https://profiles.wordpress.org/jdy68/\">Jenny Dupuy</a>, <a href=\"https://profiles.wordpress.org/jeremyfelt/\">Jeremy Felt</a>, <a href=\"https://profiles.wordpress.org/jeherve/\">Jeremy Herve</a>, <a href=\"https://profiles.wordpress.org/jeremyyip/\">Jeremy Yip</a>, <a href=\"https://profiles.wordpress.org/jeremy80/\">jeremy80</a>, <a href=\"https://profiles.wordpress.org/jeroenreumkens/\">JeroenReumkens</a>, <a href=\"https://profiles.wordpress.org/jeryj/\">jeryj</a>, <a href=\"https://profiles.wordpress.org/jillebehm/\">jillebehm</a>, <a href=\"https://profiles.wordpress.org/jipmoors/\">Jip Moors</a>, <a href=\"https://profiles.wordpress.org/sephsekla/\">Joe Bailey-Roberts</a>, <a href=\"https://profiles.wordpress.org/joedolson/\">Joe Dolson</a>, <a href=\"https://profiles.wordpress.org/joemcgill/\">Joe McGill</a>, <a href=\"https://profiles.wordpress.org/joen/\">Joen Asmussen</a>, <a href=\"https://profiles.wordpress.org/jonkastonka/\">Johan Jonk Stenstr&#246;m</a>, <a href=\"https://profiles.wordpress.org/goaroundagain/\">Johannes Kinast</a>, <a href=\"https://profiles.wordpress.org/johnbillion/\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/johnny5/\">John Godley</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby</a>, <a href=\"https://profiles.wordpress.org/bhwebworks/\">John Sundberg</a>, <a href=\"https://profiles.wordpress.org/jb510/\">Jon Brown</a>, <a href=\"https://profiles.wordpress.org/jonsurrell/\">Jon Surrell</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/spacedmonkey/\">Jonny Harris</a>, <a href=\"https://profiles.wordpress.org/jonoaldersonwp/\">Jono Alderson</a>, <a href=\"https://profiles.wordpress.org/joostdevalk/\">Joost de Valk</a>, <a href=\"https://profiles.wordpress.org/koke/\">Jorge Bernal</a>, <a href=\"https://profiles.wordpress.org/jorgefilipecosta/\">Jorge Costa</a>, <a href=\"https://profiles.wordpress.org/joseeyoast/\">Josee Wouters</a>, <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden</a>, <a href=\"https://profiles.wordpress.org/dkampdesign/\">JoshuaDoshua</a>, <a href=\"https://profiles.wordpress.org/joyously/\">Joy</a>, <a href=\"https://profiles.wordpress.org/jsnajdr/\">jsnajdr</a>, <a href=\"https://profiles.wordpress.org/juanfra/\">Juan Aldasoro</a>, <a href=\"https://profiles.wordpress.org/juanmaguitar/\">JuanMa Garrido</a>, <a href=\"https://profiles.wordpress.org/jrf/\">Juliette Reinders Folmer</a>, <a href=\"https://profiles.wordpress.org/juliobox/\">Julio Potier</a>, <a href=\"https://profiles.wordpress.org/justinahinon/\">Justin Ahinon</a>, <a href=\"https://profiles.wordpress.org/k3nsai/\">k3nsai</a>, <a href=\"https://profiles.wordpress.org/kaavyaiyer/\">kaavyaiyer</a>, <a href=\"https://profiles.wordpress.org/kevin940726/\">Kai Hao</a>, <a href=\"https://profiles.wordpress.org/akabarikalpesh/\">Kalpesh Akabari</a>, <a href=\"https://profiles.wordpress.org/kapilpaul/\">Kapil Paul</a>, <a href=\"https://profiles.wordpress.org/vyskoczilova/\">Karolina Vyskocilova</a>, <a href=\"https://profiles.wordpress.org/ryelle/\">Kelly Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/kellychoffman/\">Kelly Hoffman</a>, <a href=\"https://profiles.wordpress.org/gwwar/\">Kerry Liu</a>, <a href=\"https://profiles.wordpress.org/kevinfodness/\">Kevin Fodness</a>, <a href=\"https://profiles.wordpress.org/kishanjasani/\">Kishan Jasani</a>, <a href=\"https://profiles.wordpress.org/ixkaito/\">Kite</a>, <a href=\"https://profiles.wordpress.org/kittmedia/\">KittMedia</a>, <a href=\"https://profiles.wordpress.org/kjellr/\">Kjell Reigstad</a>, <a href=\"https://profiles.wordpress.org/klevyke/\">klevyke</a>, <a href=\"https://profiles.wordpress.org/knutsp/\">Knut Sparhell</a>, <a href=\"https://profiles.wordpress.org/vdwijngaert/\">Koen Van den Wijngaert</a>, <a href=\"https://profiles.wordpress.org/obenland/\">Konstantin Obenland</a>, <a href=\"https://profiles.wordpress.org/xkon/\">Konstantinos Xenos</a>, <a href=\"https://profiles.wordpress.org/devnel/\">Kyle Nel</a>, <a href=\"https://profiles.wordpress.org/lakrisgubben/\">lakrisgubben</a>, <a href=\"https://profiles.wordpress.org/notlaura/\">Lara Schenck</a>, <a href=\"https://profiles.wordpress.org/lmurillom/\">Larissa Murillo</a>, <a href=\"https://profiles.wordpress.org/laxman-prajapati/\">Laxman Prajapati</a>, <a href=\"https://profiles.wordpress.org/lewiscowles/\">LewisCowles</a>, <a href=\"https://profiles.wordpress.org/lifeforceinst/\">lifeforceinst</a>, <a href=\"https://profiles.wordpress.org/linux4me2/\">linux4me2</a>, <a href=\"https://profiles.wordpress.org/lovor/\">Lovro Hrust</a>, <a href=\"https://profiles.wordpress.org/displaynone/\">Luis Sacrist&#225;n</a>, <a href=\"https://profiles.wordpress.org/infolu/\">Luiz Ara&#250;jo</a>, <a href=\"https://profiles.wordpress.org/lukecarbis/\">Luke Carbis</a>, <a href=\"https://profiles.wordpress.org/m0ze/\">m0ze</a>, <a href=\"https://profiles.wordpress.org/maedahbatool/\">Maedah Batool</a>, <a href=\"https://profiles.wordpress.org/onemaggie/\">Maggie Cabrera</a>, <a href=\"https://profiles.wordpress.org/travel_girl/\">Maja Benke</a>, <a href=\"https://profiles.wordpress.org/mciampini/\">Marco Ciampini</a>, <a href=\"https://profiles.wordpress.org/mkaz/\">Marcus Kazmierczak</a>, <a href=\"https://profiles.wordpress.org/marekhrabe/\">Marek Hrabe</a>, <a href=\"https://profiles.wordpress.org/tyxla/\">Marin Atanasov</a>, <a href=\"https://profiles.wordpress.org/clorith/\">Marius L. J.</a>, <a href=\"https://profiles.wordpress.org/markjaquith/\">Mark Jaquith</a>, <a href=\"https://profiles.wordpress.org/markparnell/\">Mark Parnell</a>, <a href=\"https://profiles.wordpress.org/mark-k/\">Mark-k</a>, <a href=\"https://profiles.wordpress.org/markoheijnen/\">Marko Heijnen</a>, <a href=\"https://profiles.wordpress.org/m-e-h/\">Marty Helmick</a>, <a href=\"https://profiles.wordpress.org/marybaum/\">Mary Baum</a>, <a href=\"https://profiles.wordpress.org/mariaojob/\">Mary Job</a>, <a href=\"https://profiles.wordpress.org/marylauc/\">marylauc</a>, <a href=\"https://profiles.wordpress.org/imath/\">Mathieu Viet</a>, <a href=\"https://profiles.wordpress.org/matveb/\">Matias Ventura</a>, <a href=\"https://profiles.wordpress.org/mhuntdesign/\">Matt</a>, <a href=\"https://profiles.wordpress.org/mattchowning/\">Matt Chowning</a>, <a href=\"https://profiles.wordpress.org/matt/\">Matt Mullenweg</a>, <a href=\"https://profiles.wordpress.org/maxpertici/\">Maxime Pertici</a>, <a href=\"https://profiles.wordpress.org/mblach/\">mblach</a>, <a href=\"https://profiles.wordpress.org/immeet94/\">Meet Makadia</a>, <a href=\"https://profiles.wordpress.org/meher/\">Meher Bala</a>, <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/meloniq/\">meloniq</a>, <a href=\"https://profiles.wordpress.org/mensmaximus/\">mensmaximus</a>, <a href=\"https://profiles.wordpress.org/mdawaffe/\">Michael Adams (mdawaffe)</a>, <a href=\"https://profiles.wordpress.org/mbabker/\">Michael Babker</a>, <a href=\"https://profiles.wordpress.org/tw2113/\">Michael Beckwith</a>, <a href=\"https://profiles.wordpress.org/czapla/\">Michal Czaplinski</a>, <a href=\"https://profiles.wordpress.org/mcsf/\">Miguel Fonseca</a>, <a href=\"https://profiles.wordpress.org/simison/\">Mikael Korpela</a>, <a href=\"https://profiles.wordpress.org/mikehansenme/\">Mike Hansen</a>, <a href=\"https://profiles.wordpress.org/mikejolley/\">Mike Jolley (a11n)</a>, <a href=\"https://profiles.wordpress.org/mike_cowobo/\">Mike Martel</a>, <a href=\"https://profiles.wordpress.org/mikeschroder/\">Mike Schroder</a>, <a href=\"https://profiles.wordpress.org/mihdan/\">Mikhail Kobzarev</a>, <a href=\"https://profiles.wordpress.org/dimadin/\">Milan Dinić</a>, <a href=\"https://profiles.wordpress.org/milana_cap/\">Milana Cap</a>, <a href=\"https://profiles.wordpress.org/mkdgs/\">mkdgs</a>, <a href=\"https://profiles.wordpress.org/mmuyskens/\">mmuyskens</a>, <a href=\"https://profiles.wordpress.org/mmxxi/\">mmxxi</a>, <a href=\"https://profiles.wordpress.org/moch11/\">moch11</a>, <a href=\"https://profiles.wordpress.org/daddou/\">Mohamed El Amine DADDOU</a>, <a href=\"https://profiles.wordpress.org/mohamedfaragallah/\">Mohammed Faragallah</a>, <a href=\"https://profiles.wordpress.org/monikarao/\">Monika Rao</a>, <a href=\"https://profiles.wordpress.org/mor10/\">Morten Rand-Hendriksen</a>, <a href=\"https://profiles.wordpress.org/mrjoeldean/\">mrjoeldean</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/munyagu/\">munyagu</a>, <a href=\"https://profiles.wordpress.org/m_uysl/\">Mustafa Uysal</a>, <a href=\"https://profiles.wordpress.org/mweichert/\">mweichert</a>, <a href=\"https://profiles.wordpress.org/assassinateur/\">Nadir Seghir</a>, <a href=\"https://profiles.wordpress.org/nalininonstopnewsuk/\">Nalini Thakor</a>, <a href=\"https://profiles.wordpress.org/naoki0h/\">Naoki Ohashi</a>, <a href=\"https://profiles.wordpress.org/nao/\">Naoko Takano</a>, <a href=\"https://profiles.wordpress.org/nayanchamp7/\">Nazrul Islam Nayan</a>, <a href=\"https://profiles.wordpress.org/dway/\">nderambure</a>, <a href=\"https://profiles.wordpress.org/krstarica/\">net</a>, <a href=\"https://profiles.wordpress.org/nicegamer7/\">nicegamer7</a>, <a href=\"https://profiles.wordpress.org/eidolonnight/\">Nicholas Garofalo</a>, <a href=\"https://profiles.wordpress.org/celloexpressions/\">Nick Halsey</a>, <a href=\"https://profiles.wordpress.org/ntsekouras/\">Nik Tsekouras</a>, <a href=\"https://profiles.wordpress.org/ninanmnm/\">ninanmnm</a>, <a href=\"https://profiles.wordpress.org/pianist787/\">Noah Allen</a>, <a href=\"https://profiles.wordpress.org/nvartolomei/\">nvartolomei</a>, <a href=\"https://profiles.wordpress.org/oguzkocer/\">oguzkocer</a>, <a href=\"https://profiles.wordpress.org/olafklejnstrupjensen/\">olafklejnstrupjensen</a>, <a href=\"https://profiles.wordpress.org/olgabulat/\">Olga Bulat</a>, <a href=\"https://profiles.wordpress.org/oglekler/\">Olga Gleckler</a>, <a href=\"https://profiles.wordpress.org/otshelnik-fm/\">Otshelnik-Fm</a>, <a href=\"https://profiles.wordpress.org/oxyrealm/\">oxyrealm</a>, <a href=\"https://profiles.wordpress.org/ozh/\">Ozh</a>, <a href=\"https://profiles.wordpress.org/paaljoachim/\">Paal Joachim Romdahl</a>, <a href=\"https://profiles.wordpress.org/palmiak/\">palmiak</a>, <a href=\"https://profiles.wordpress.org/paaggeli/\">Panagiotis Angelidis</a>, <a href=\"https://profiles.wordpress.org/paragoninitiativeenterprises/\">Paragon Initiative Enterprises</a>, <a href=\"https://profiles.wordpress.org/swissspidy/\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/fantasy1125/\">Pascal Knecht</a>, <a href=\"https://profiles.wordpress.org/patkemper/\">Pat</a>, <a href=\"https://profiles.wordpress.org/patricklindsay/\">patricklindsay</a>, <a href=\"https://profiles.wordpress.org/pbearne/\">Paul Bearne</a>, <a href=\"https://profiles.wordpress.org/pbiron/\">Paul Biron</a>, <a href=\"https://profiles.wordpress.org/pabline/\">Paul Bunkham</a>, <a href=\"https://profiles.wordpress.org/paulschreiber/\">Paul Schreiber</a>, <a href=\"https://profiles.wordpress.org/paulstonier/\">Paul Stonier</a>, <a href=\"https://profiles.wordpress.org/pschrottky/\">Paul Von Schrottky</a>, <a href=\"https://profiles.wordpress.org/psrpinto/\">Paulo Pinto</a>, <a href=\"https://profiles.wordpress.org/pavelvisualcomposer/\">Pavel I</a>, <a href=\"https://profiles.wordpress.org/mrpauloen/\">Paweł</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/walbo/\">Petter Walbø Johnsgård</a>, <a href=\"https://profiles.wordpress.org/phena109/\">phena109</a>, <a href=\"https://profiles.wordpress.org/philipmjackson/\">Philip Jackson</a>, <a href=\"https://profiles.wordpress.org/strategio/\">Pierre SYLVESTRE</a>, <a href=\"https://profiles.wordpress.org/wppinar/\">Pinar</a>, <a href=\"https://profiles.wordpress.org/boniu91/\">Piotrek Boniu</a>, <a href=\"https://profiles.wordpress.org/mordauk/\">Pippin Williamson</a>, <a href=\"https://profiles.wordpress.org/ptahdunbar/\">Pirate Dunbar</a>, <a href=\"https://profiles.wordpress.org/promz/\">Pramod Jodhani</a>, <a href=\"https://profiles.wordpress.org/presskopp/\">Presskopp</a>, <a href=\"https://profiles.wordpress.org/presstoke/\">presstoke</a>, <a href=\"https://profiles.wordpress.org/psealock/\">psealock</a>, <a href=\"https://profiles.wordpress.org/pwallner/\">pwallner</a>, <a href=\"https://profiles.wordpress.org/pyronaur/\">pyronaur</a>, <a href=\"https://profiles.wordpress.org/itsjonq/\">Q</a>, <a href=\"https://profiles.wordpress.org/rachelbaker/\">Rachel Baker</a>, <a href=\"https://profiles.wordpress.org/radixweb/\">Radixweb</a>, <a href=\"https://profiles.wordpress.org/rafaelgalani/\">Rafael Galani</a>, <a href=\"https://profiles.wordpress.org/rafhun/\">rafhun</a>, <a href=\"https://profiles.wordpress.org/rtm909/\">Rahul Mehta</a>, <a href=\"https://profiles.wordpress.org/rkradadiya/\">Rajesh Radadiya</a>, <a href=\"https://profiles.wordpress.org/ramiy/\">Rami Yushuvaev</a>, <a href=\"https://profiles.wordpress.org/rahmohn/\">Ramon Ahnert</a>, <a href=\"https://profiles.wordpress.org/ramonopoly/\">ramonopoly</a>, <a href=\"https://profiles.wordpress.org/jontyravi/\">Ravi Vaghela</a>, <a href=\"https://profiles.wordpress.org/ravipatel/\">ravipatel</a>, <a href=\"https://profiles.wordpress.org/rellect/\">Refael Iliaguyev</a>, <a href=\"https://profiles.wordpress.org/renehermi/\">Rene Hermenau</a>, <a href=\"https://profiles.wordpress.org/retrofox/\">retrofox</a>, <a href=\"https://profiles.wordpress.org/reynhartono/\">reynhartono</a>, <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/rianrietveld/\">Rian Rietveld</a>, <a href=\"https://profiles.wordpress.org/rima1889/\">Rima Prajapati</a>, <a href=\"https://profiles.wordpress.org/rinatkhaziev/\">Rinat</a>, <a href=\"https://profiles.wordpress.org/rnaby/\">Rnaby</a>, <a href=\"https://profiles.wordpress.org/robdxw/\">robdxw</a>, <a href=\"https://profiles.wordpress.org/noisysocks/\">Robert Anderson</a>, <a href=\"https://profiles.wordpress.org/miqrogroove/\">Robert Chapin</a>, <a href=\"https://profiles.wordpress.org/kreppar/\">Rodrigo Arias</a>, <a href=\"https://profiles.wordpress.org/rogertheriault/\">Roger Theriault</a>, <a href=\"https://profiles.wordpress.org/rogerlos/\">rogerlos</a>, <a href=\"https://profiles.wordpress.org/roo2/\">roo2</a>, <a href=\"https://profiles.wordpress.org/lev0/\">Roy</a>, <a href=\"https://profiles.wordpress.org/geekstreetwp/\">Russell Aaron</a>, <a href=\"https://profiles.wordpress.org/rmccue/\">Ryan McCue</a>, <a href=\"https://profiles.wordpress.org/welcher/\">Ryan Welcher</a>, <a href=\"https://profiles.wordpress.org/sergiomdgomes/\">S&#233;rgio Gomes</a>, <a href=\"https://profiles.wordpress.org/soean/\">S&#246;ren Wrede</a>, <a href=\"https://profiles.wordpress.org/stodorovic/\">Sa&#353;a</a>, <a href=\"https://profiles.wordpress.org/sabrinazeidan/\">Sabrina Zeidan</a>, <a href=\"https://profiles.wordpress.org/sahilmepani/\">Sahil Mepani</a>, <a href=\"https://profiles.wordpress.org/solarissmoke/\">Samir Shah</a>, <a href=\"https://profiles.wordpress.org/otto42/\">Samuel Wood (Otto)</a>, <a href=\"https://profiles.wordpress.org/sandipmondal/\">Sandip Mondal</a>, <a href=\"https://profiles.wordpress.org/sanketchodavadiya/\">Sanket Chodavadiya</a>, <a href=\"https://profiles.wordpress.org/sannevndrmeulen/\">Sanne van der Meulen</a>, <a href=\"https://profiles.wordpress.org/sarahricker/\">sarahricker</a>, <a href=\"https://profiles.wordpress.org/sarayourfriend/\">sarayourfriend</a>, <a href=\"https://profiles.wordpress.org/sasagar/\">SASAPIYO</a>, <a href=\"https://profiles.wordpress.org/satrancali/\">satrancali</a>, <a href=\"https://profiles.wordpress.org/savicmarko1985/\">savicmarko1985</a>, <a href=\"https://profiles.wordpress.org/gmagicscott/\">Scott Lesovic</a>, <a href=\"https://profiles.wordpress.org/coffee2code/\">Scott Reilly</a>, <a href=\"https://profiles.wordpress.org/scottconnerly/\">scottconnerly</a>, <a href=\"https://profiles.wordpress.org/scruffian/\">scruffian</a>, <a href=\"https://profiles.wordpress.org/sean212/\">Sean Fisher</a>, <a href=\"https://profiles.wordpress.org/seanchayes/\">Sean Hayes</a>, <a href=\"https://profiles.wordpress.org/sebbb/\">sebbb</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/yakimun/\">Sergey Yakimov</a>, <a href=\"https://profiles.wordpress.org/sergioestevao/\">SergioEstevao</a>, <a href=\"https://profiles.wordpress.org/shaunandrews/\">shaunandrews</a>, <a href=\"https://profiles.wordpress.org/shital-patel/\">Shital Marakana</a>, <a href=\"https://profiles.wordpress.org/silb3r/\">silb3r</a>, <a href=\"https://profiles.wordpress.org/siobhyb/\">Siobhan</a>, <a href=\"https://profiles.wordpress.org/sirstuey/\">SirStuey</a>, <a href=\"https://profiles.wordpress.org/snapfractalpop/\">snapfractalpop</a>, <a href=\"https://profiles.wordpress.org/spikeuk1/\">spikeuk1</a>, <a href=\"https://profiles.wordpress.org/spytzo/\">spytzo</a>, <a href=\"https://profiles.wordpress.org/stacimc/\">stacimc</a>, <a href=\"https://profiles.wordpress.org/khromov/\">Stanislav Khromov</a>, <a href=\"https://profiles.wordpress.org/deustron/\">Stefan H&#252;sges</a>, <a href=\"https://profiles.wordpress.org/stefanjoebstl/\">stefanjoebstl</a>, <a href=\"https://profiles.wordpress.org/ryokuhi/\">Stefano Minoia</a>, <a href=\"https://profiles.wordpress.org/hypest/\">Stefanos Togoulidis</a>, <a href=\"https://profiles.wordpress.org/sabernhardt/\">Stephen Bernhardt</a>, <a href=\"https://profiles.wordpress.org/netweb/\">Stephen Edgar</a>, <a href=\"https://profiles.wordpress.org/dufresnesteven/\">Steve Dufresne</a>, <a href=\"https://profiles.wordpress.org/stevegrunwell/\">Steve Grunwell</a>, <a href=\"https://profiles.wordpress.org/stevehenty/\">Steve Henty</a>, <a href=\"https://profiles.wordpress.org/stevenkword/\">Steven Word</a>, <a href=\"https://profiles.wordpress.org/subrataemfluence/\">Subrata Sarkar</a>, <a href=\"https://profiles.wordpress.org/sumaiyasiddika/\">Sumaiya Siddika</a>, <a href=\"https://profiles.wordpress.org/sumanm/\">Suman</a>, <a href=\"https://profiles.wordpress.org/5um17/\">Sumit Singh</a>, <a href=\"https://profiles.wordpress.org/sumitsingh/\">Sumit Singh</a>, <a href=\"https://profiles.wordpress.org/quadthemes/\">Sunny</a>, <a href=\"https://profiles.wordpress.org/sushmak/\">sushmak</a>, <a href=\"https://profiles.wordpress.org/cybr/\">Sybre Waaijer</a>, <a href=\"https://profiles.wordpress.org/synchro/\">Synchro</a>, <a href=\"https://profiles.wordpress.org/szaqal21/\">szaqal21</a>, <a href=\"https://profiles.wordpress.org/tamlyn/\">tamlyn</a>, <a href=\"https://profiles.wordpress.org/karmatosed/\">Tammie Lister</a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</a>, <a href=\"https://profiles.wordpress.org/terraling/\">terraling</a>, <a href=\"https://profiles.wordpress.org/terriann/\">Terri Ann</a>, <a href=\"https://profiles.wordpress.org/wildworks/\">Tetsuaki Hamano</a>, <a href=\"https://profiles.wordpress.org/themes-1/\">them.es</a>, <a href=\"https://profiles.wordpress.org/kraftner/\">Thomas Kr&#228;ftner</a>, <a href=\"https://profiles.wordpress.org/thomasplevy/\">Thomas Patrick Levy</a>, <a href=\"https://profiles.wordpress.org/thomas-vitale/\">Thomas Vitale</a>, <a href=\"https://profiles.wordpress.org/tigertech/\">tigertech</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/timotijhof/\">TimoTijhof</a>, <a href=\"https://profiles.wordpress.org/tkama/\">Tkama</a>, <a href=\"https://profiles.wordpress.org/tmatsuur/\">tmatsuur</a>, <a href=\"https://profiles.wordpress.org/tmdk/\">tmdk</a>, <a href=\"https://profiles.wordpress.org/tz-media/\">Tobias Zimpel</a>, <a href=\"https://profiles.wordpress.org/tobiasbg/\">TobiasBg</a>, <a href=\"https://profiles.wordpress.org/tobifjellner/\">tobifjellner (Tor-Bjorn Fjellner)</a>, <a href=\"https://profiles.wordpress.org/tjnowell/\">Tom J Nowell</a>, <a href=\"https://profiles.wordpress.org/skithund/\">Toni Viemer&#246;</a>, <a href=\"https://profiles.wordpress.org/hellofromtonya/\">Tonya Mork</a>, <a href=\"https://profiles.wordpress.org/toro_unit/\">Toro_Unit (Hiroshi Urabe)</a>, <a href=\"https://profiles.wordpress.org/torres126/\">torres126</a>, <a href=\"https://profiles.wordpress.org/zodiac1978/\">Torsten Landsiedel</a>, <a href=\"https://profiles.wordpress.org/toru/\">Toru Miki</a>, <a href=\"https://profiles.wordpress.org/travisnorthcutt/\">Travis Northcutt</a>, <a href=\"https://profiles.wordpress.org/trejder/\">trejder</a>, <a href=\"https://profiles.wordpress.org/desaiuditd/\">Udit Desai</a>, <a href=\"https://profiles.wordpress.org/grapplerulrich/\">Ulrich</a>, <a href=\"https://profiles.wordpress.org/utsav72640/\">Utsav tilava</a>, <a href=\"https://profiles.wordpress.org/vcanales/\">Vicente Canales</a>, <a href=\"https://profiles.wordpress.org/vipulc2/\">Vipul Chandel</a>, <a href=\"https://profiles.wordpress.org/vladytimy/\">Vlad T</a>, <a href=\"https://profiles.wordpress.org/wangql/\">wangql</a>, <a href=\"https://profiles.wordpress.org/wb1234/\">wb1234</a>, <a href=\"https://profiles.wordpress.org/webdragon/\">WebDragon</a>, <a href=\"https://profiles.wordpress.org/wendyjchen/\">Wendy Chen</a>, <a href=\"https://profiles.wordpress.org/westonruter/\">Weston Ruter</a>, <a href=\"https://profiles.wordpress.org/wfmattr/\">WFMattR</a>, <a href=\"https://profiles.wordpress.org/earnjam/\">William Earnhardt</a>, <a href=\"https://profiles.wordpress.org/williampatton/\">williampatton</a>, <a href=\"https://profiles.wordpress.org/xavivars/\">Xavi Ivars</a>, <a href=\"https://profiles.wordpress.org/tikifez/\">Xristopher Anderton</a>, <a href=\"https://profiles.wordpress.org/y_kolev/\">Y_Kolev</a>, <a href=\"https://profiles.wordpress.org/yansern/\">Yan Sern</a>, <a href=\"https://profiles.wordpress.org/fierevere/\">Yui</a>, <a href=\"https://profiles.wordpress.org/yuliyan/\">Yuliyan Slavchev</a>, <a href=\"https://profiles.wordpress.org/yvettesonneveld/\">Yvette Sonneveld</a>, <a href=\"https://profiles.wordpress.org/zackkrida/\">Zack Krida</a>, <a href=\"https://profiles.wordpress.org/zebulan/\">Zebulan Stanphill</a>, <a href=\"https://profiles.wordpress.org/zkancs/\">zkancs</a>, and <a href=\"https://profiles.wordpress.org/sunxiyuan/\">孙锡源</a>.\n\n\n\n<p></p>\n\n\n\n<p>In addition to these contributors, many thanks to all of the community volunteers who contribute in the&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://wordpress.org/support/\">support forums</a>. They answer questions from people across the world, whether they are using WordPress for the first time, or they’ve been around since the first release all the way back in 2003. These releases are as successful as they are because of their efforts!</p>\n\n\n\n<p>Finally, thanks to all the community translators who help make WordPress available in over 200 languages for every release. 80 languages have translated 80% or more WordPress 5.8 and our community translators are hard at work ensuring more languages are on their way. If contributing to WordPress appeals to you, it’s easy to learn more. Check out&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://make.wordpress.org/\">Make WordPress</a>&nbsp;or the&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://make.wordpress.org/core/\">core development blog</a>.</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"10976\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:58:\"\n		\n		\n		\n		\n		\n				\n		\n\n					\n										\n					\n		\n		\n\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"WP Briefing: Episode 13: Cherishing WordPress Diversity\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"https://wordpress.org/news/2021/07/episode-13-cherishing-wordpress-diversity/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 19 Jul 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=10949\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:357:\"In this episode, Josepha Haden Chomphosy discusses the importance of Diversity, Equity, and Inclusion to the fabric of the WordPress project and how we can move from a place of welcoming it to cherishing it. Have a question you&#8217;d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/07/WP-Briefing-013.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:14890:\"\n<p>In this episode, Josepha Haden Chomphosy discusses the importance of Diversity, Equity, and Inclusion to the fabric of the WordPress project and how we can move from a place of welcoming it to cherishing it.</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href=\"mailto:wpbriefing@wordpress.org\">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<p>Editor: <a href=\"https://profiles.wordpress.org/dustinhartzler/\">Dustin Hartzler</a></p>\n\n\n\n<p>Logo: <a href=\"https://profiles.wordpress.org/beafialho/\">Beatriz Fialho</a></p>\n\n\n\n<p>Production: <a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a></p>\n\n\n\n<p>Song: Fearless First by Kevin MacLeod</p>\n\n\n\n<h2>References</h2>\n\n\n\n<p><a href=\"https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/diversity-speaker-training-workshop/\">Diverse Speaker Training Workshop</a></p>\n\n\n\n<p><a href=\"https://josepha.blog/2020/12/23/a-wordpress-dinner-party/\">A WordPress Dinner Party</a></p>\n\n\n\n<p><a href=\"https://josepha.blog/2018/11/06/the-burden-of-proof/\">The Burden of Proof</a></p>\n\n\n\n<p><a href=\"https://josepha.blog/2021/03/05/leading-at-any-level/\">Leadership At Any Level</a></p>\n\n\n\n<p><a href=\"https://josepha.blog/2019/03/02/building-a-culture-of-safety/\">Building a Culture of Safety</a></p>\n\n\n\n<p><a href=\"https://josepha.blog/2020/03/27/leadership-basics-ethics-in-communication/\">Leadership Basics: Ethics in Communication</a></p>\n\n\n\n<p><a href=\"https://wordpress.org/support/wordpress-version/version-5-6/\">WordPress 5.6</a></p>\n\n\n\n<p>Bonus resource: <a href=\"https://allienimmons.com/how-to-be-a-wordpress-ally/\">How to Be a WordPress Ally</a></p>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id=\"more-10949\"></span>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:10</p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Josepha Haden Chomphosy. And before we get started, I have to be honest with you all, this episode and the next one have made me feel really anxious. This one is about Diversity, Equity, and Inclusion in open source, and especially in WordPress. And the next one is about accessibility in WordPress. And I feel like there&#8217;s just so much to do, and we don&#8217;t do enough, but we do what we can. And still, we will never be done with that work. And if you don&#8217;t know what I mean by Diversity, Equity, and Inclusion, you can kind of think of it this way. Diversity is bringing in people with different viewpoints and lived experiences. Equity is making sure everyone has what they need to get a fair chance of success, which is different from equality. And Inclusion is making sure that the environment is built to not only tolerate diverse groups but to celebrate them as well. So remember this as you listen to what I have to say here. We are never where we want to be in either of those spaces. But that shouldn&#8217;t stop us from looking at the things we have done to get us in the right direction. All right. Here we go.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:54</p>\n\n\n\n<p>I say a lot that we are a project that serves a majority collection of minority voices. WordPress is global in reach and open source in nature. And you would assume that what allows the software to be used by anyone would also enable it to be built by anyone. After all, your location doesn&#8217;t matter, and who employs you also doesn&#8217;t matter. And your relative social standing certainly shouldn&#8217;t matter. As long as you can communicate with the others contributing to the project, there should be no obstacle to your participation. The mission of the WordPress project is to democratize publishing, right? It&#8217;s to get the ability to have a website tap into passive income on your web presence. I mean, the job is to level the playing field for everyone. However, it&#8217;s my experience that bringing in new voices takes a lot of proactive work on behalf of leaders and contributors. It&#8217;s not enough to say, &#8220;Hey, I&#8217;m having a party,&#8221; you also have to say, &#8220;I&#8217;m having a party, and I&#8217;d like you to be there.&#8221; It&#8217;s not enough to think people will make their own space at this table. You have to make sure that you have table settings for everyone. And even beyond the basics of directing people to you.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:12</p>\n\n\n\n<p>And on toward the next steps, you have to be honest about the fact that open source contribution requires a fair amount of privilege. By privilege, I mean the luxury of extra time or extra funding or just an understanding employer. WordPress supports 41% of the web. I think it&#8217;s 42% of the web right now. But less than 1% of people who use WordPress show up to help maintain it. And that 1% that does show up skews toward people who already have a pretty high level of representation and technology. And so, when you look at who is building it versus who is using it, it doesn&#8217;t always match. And since what we build so frequently reflects who we are, sometimes what we build doesn&#8217;t match the needs of the people who are using what we have.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:10</p>\n\n\n\n<p>So what has WordPress done to be proactive on the question of Diversity, Equity, and Inclusion? There are quite a few unseen things that have gone into this over the years and a few pretty visible things. This is a very long list. And it has a whole lot of just reference material. And so the show notes today will come in handy for people, and there will be just a laundry list of linked resources for everyone.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:39</p>\n\n\n\n<p>But the first thing that WordPress has done is that we have accepted the burden of proof. I&#8217;m going to share a post about this in the show notes. That means we accept that it&#8217;s not the job of underrepresented folks to figure out if they are welcome. It&#8217;s up to us to make it clear that they are. So, there are three big little things that the community has done over the years. One is that many teams open their text-based meetings with an explanation of what is done in the meeting, who comes to the meetings, where to find help if you&#8217;re lost in the meeting, and for teams that have a specific type of requests that comes into those channels that aren&#8217;t handled in those channels. They also will share where people can go to get those requests taken care of. Many teams have also updated their team handbooks to have good beginner docs, limited use of inside jokes or jargon, and good first bugs. And also, there is a code of conduct in the community declaring that everyone is welcome and clarifies what to do if you see folks being unwelcoming.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:51</p>\n\n\n\n<p>A second big thing that folks in the WordPress community have done is written down what was unwritten. Having things clearly documented unlocks institutional knowledge that you&#8217;d otherwise have to know someone to get. Clarity and process and the structure help anyone engage with your organization, not just the people who have extra time to figure things out. What that looks like in the WordPress project is that many teams have documented their workflows and their working spaces and just their general team norms. Many teams have also started defining what it means to be a team rep and holding open processes to choose those team reps. Many other community leaders and I have written down countless unspoken rules, guidelines, and philosophical underpinnings so that people don&#8217;t have to guess what we&#8217;re doing or why we&#8217;re doing things, or where we want to do them.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:46</p>\n\n\n\n<p>And the more visible thing that the WordPress project has been doing is that we found ways to invite people in, and they&#8217;re not failsafe; they’re not foolproof, but it is certainly a step in the right direction. The first one is an ongoing, diverse speaker training initiative. And I&#8217;ll include a link to that in the show notes as well. It is run by Jill Binder and a fantastic group of contributors that collaborate with her. And I really have loved watching that particular program grow and flourish and help WordPress make a difference where we absolutely can.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>07:27</p>\n\n\n\n<p>The second thing that was pretty visible about how we invited people in was at the end of 2020, and we had an all-women and nonbinary release squad for our biggest release of the year; WordPress 5.6. I had a group of probably 70 women and nonbinary identifying folx who joined in the process and joined in learning more about the process. Some of them have continued in the project. Others have stepped away for various reasons. But all of them are welcome to return. And I encourage everyone to return to contribution when time and resources make that possible for you.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>08:09</p>\n\n\n\n<p>And then the third thing that we&#8217;ve done, which I have talked about a lot, is the revival of the testing and triage practices. That has been work that&#8217;s been ongoing for a number of years. And it happens across multiple teams. It is not always immediately clear to people why the testing work. And the triage work is identifiable for me as a way to invite people into this process. And so I&#8217;ll be briefly clear about it right now. So testing as a practice brings in the users that otherwise don&#8217;t have a lot of spare time and that extra privilege to like, figure out what&#8217;s going on with WordPress, and contribute their own fixes to problems. They can give back to this project by being co-developers with us, co-creators with our entire process of making WordPress real and usable for the largest number of people that we can because we now support 42% of the web. And then, the triage practice invites in a diverse voice of people. Because you don&#8217;t necessarily always need to know everything about a project to help with triage. And when you&#8217;re helping with triage, you get active learning through participating in the process. But you also get passive learning from the people who already know huge amounts about the project and the process and everything that goes into it. And so it&#8217;s a low key low stress way to get your feet wet and start building that knowledge that sometimes is hard to come by unless you are actively working in it. So the testing practices, the triage practices, I really to the core of my being believe that those are active and ongoing ways for us to invite people who otherwise wouldn&#8217;t have a chance to get their voices heard in an open source project. And y&#8217;all, as I said at the start, y’all, there&#8217;s nothing about this list that I just shared, which makes me feel like our work on this is done. Just like any muscle, you don&#8217;t fight to peak fitness, and then hit the big stop button on time and say, &#8220;Now, I never have to work out again.&#8221; If we did, the world would be a very different place probably. But it does then lead us to the next steps for fostering a community culture that&#8217;s as broad as the people who use this software. If you believe in leadership at any level, as I do, there are a ton of things that you can do right now. But I&#8217;ll boil them down into three big chunks of things.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>10:54</p>\n\n\n\n<p>First, check your community area, or whatever community you want to apply this to, for things that need a little more proactive work. I will share a post called<em> Building A Culture of Safety</em> that will take you through a list of good first steps. And it is not as hard as it looks. When you say build a culture of safety, there are many really clear-cut minor changes that you can ask people to make and, in like, four or five different areas that can help your community be more welcoming and more open.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>11:30</p>\n\n\n\n<p>The second thing that you can do is know that small changes add up over time and commit to making those changes where you can. If you are elite at any level, you know that supporting people and processes is the responsibility of everyone in the group. And if you can make your own autonomous decisions and commit to making small changes that make a big difference over time, you will be part of that solution. And that is not specific to any one group that we have in our communities. You can be an ally for anyone, whether they look like you, whether they have your same experiences, or not. And sometimes, it&#8217;s as easy as just holding space for the people who haven&#8217;t had a chance to talk yet. And on the subject of holding space and the way that we communicate.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>12:22</p>\n\n\n\n<p>The third thing that I think is incredibly important is that you can take on as a foundational personal practice the concept of ethical communication. I&#8217;ll share a post about that as well in the show notes, but the core of it is that you have to know that what you say and don&#8217;t say what you do and don&#8217;t do has an impact on others and embrace that responsibility. All right, so you made it all the way through, and I am so proud of you. I&#8217;m sure you have questions about this. And I encourage you to share those. You can email them to me at wp briefing@wordpress.org.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>13:10</p>\n\n\n\n<p>This brings us to our small list of big things. I&#8217;ve got two things for you today. First and foremost, WordPress 5.8 gets released tomorrow. It&#8217;s a big release, and lots of people have been working on it. So get your update processes ready and keep an eye on wordpress.org/news for the announcement post. Second, and still pretty important, team reps have been working on their quarterly check-ins so that all other teams can get an idea of what&#8217;s happening around the WordPress office. Keep an eye out for that post on make.wordpress.org/updates. And that is your smallest of big things. Thank you for tuning in today for the WordPress Briefing. I&#8217;m your host Joseph Hayden Chomphosy, and I&#8217;ll see you again in a couple of weeks.</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"10949\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 5.8 Release Candidate 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2021/07/wordpress-5-8-release-candidate-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 14 Jul 2021 01:09:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10933\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:303:\"The third release candidate for WordPress 5.8 is now available! WordPress 5.8 is slated for release on July 20, 2021, and we need your help to get there—if you have not tried 5.8 yet, now is the time! You can test the WordPress 5.8 release candidate 3 in any of these three ways: Install and [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Jeffrey Paul\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3233:\"\n<p>The third release candidate for <a href=\"https://make.wordpress.org/core/5-8/\">WordPress 5.8</a> is now available! </p>\n\n\n\n<p>WordPress 5.8 is slated for release on <strong>July 20, 2021</strong>, and we need <em>your</em> help to get there—if you have not tried 5.8 yet, now is the time!</p>\n\n\n\n<p>You can test the WordPress 5.8 release candidate 3 in any of these three ways:</p>\n\n\n\n<ul><li>Install and activate the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester plugin</a> (select the <code>Bleeding edge</code> channel and then <code>Beta/RC Only</code> stream)</li><li>Directly download the release candidate version <a href=\"https://wordpress.org/wordpress-5.8-RC3.zip\">(zip)</a></li><li>Use WP-CLI to test: <code>wp core update --version=5.8-RC3</code></li></ul>\n\n\n\n<p>Thank you to all of the contributors who tested the&nbsp;Beta/RC releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.</p>\n\n\n\n<h2>Plugin and Theme Developers</h2>\n\n\n\n<p>Please test your plugins and themes against WordPress 5.8 and update the&nbsp;<em>Tested up to</em>&nbsp;version in the <code>readme</code> file to 5.8.  If you find compatibility problems, please be sure to post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta/\">support forums</a>&nbsp;so we can work to solve them in time for the final release.</p>\n\n\n\n<p>For a more detailed breakdown of the changes included in WordPress 5.8, check out the <a href=\"https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/\">WordPress 5.8 beta 1 post</a>.  The&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://make.wordpress.org/core/2021/07/03/wordpress-5-8-field-guide/\">WordPress 5.8 Field Guide</a>, which is particularly useful for developers, has all the info and further links to help you get comfortable with the major changes.</p>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Can you speak and write in a language other than English? &nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev\">Help us translate WordPress into more than 100 languages!</a></p>\n\n\n\n<p><em><strong>If you think you have found a bug</strong>, you can post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a>&nbsp;in the support forums. We would love to hear from you!  If you are comfortable writing a reproducible bug report,&nbsp;<a href=\"https://core.trac.wordpress.org/newticket\">file one on WordPress Trac</a>, where you can also find&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">a list of known bugs</a>.</em></p>\n\n\n\n<p class=\"has-text-align-right\"><strong><em>Props to <a href=\'https://profiles.wordpress.org/cbringmann/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>cbringmann</a>, <a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a>, and <a href=\'https://profiles.wordpress.org/marybaum/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>marybaum</a> for peer-reviewing!</em></strong></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>Code is poetry<br>Jazz is improvisation<br>Both are forms of art<br><br></em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"10933\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:18;a:6:{s:4:\"data\";s:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 5.8 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2021/07/wordpress-5-8-release-candidate-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 07 Jul 2021 01:12:57 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10912\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:305:\"The second release candidate for WordPress 5.8 is now available! 🎉 WordPress 5.8 is slated for release on July 20, 2021, and we need your help to get there—if you have not tried 5.8 yet, now is the time! You can test the WordPress 5.8 release candidate 2 in any of these three ways: Install [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Jeffrey Paul\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3376:\"\n<p>The second release candidate for <a href=\"https://make.wordpress.org/core/5-8/\">WordPress 5.8</a> is now available! <img src=\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f389.png\" alt=\"🎉\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></p>\n\n\n\n<p>WordPress 5.8 is slated for release on <strong>July 20, 2021</strong>, and we need <em>your</em> help to get there—if you have not tried 5.8 yet, now is the time!</p>\n\n\n\n<p>You can test the WordPress 5.8 release candidate 2 in any of these three ways:</p>\n\n\n\n<ul><li>Install and activate the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester plugin</a> (select the <code>Bleeding edge</code> channel and then <code>Beta/RC Only</code> stream)</li><li>Directly download the release candidate version <a href=\"https://wordpress.org/wordpress-5.8-RC2.zip\">(zip)</a></li><li>Use WP-CLI to test: <code>wp core update --version=5.8-RC2</code></li></ul>\n\n\n\n<p>Thank you to all of the contributors who tested the&nbsp;Beta/RC releases and gave feedback.  Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.</p>\n\n\n\n<h2>Plugin and Theme Developers</h2>\n\n\n\n<p>Please test your plugins and themes against WordPress 5.8 and update the&nbsp;<em>Tested up to</em>&nbsp;version in the <code>readme</code> file to 5.8.  If you find compatibility problems, please be sure to post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta/\">support forums</a>,&nbsp;so they can get ready for the final release.</p>\n\n\n\n<p>For a more detailed breakdown of the changes included in WordPress 5.8, check out the <a href=\"https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/\">WordPress 5.8 beta 1 post</a>.  The&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://make.wordpress.org/core/2021/07/03/wordpress-5-8-field-guide/\">WordPress 5.8 Field Guide</a>, which is particularly useful for developers, has all the info and further links to help you get comfortable with the major changes.</p>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Can you speak and write in a language other than English? &nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev\">Help us translate WordPress into more than 100 languages!</a></p>\n\n\n\n<p><em><strong>If you think you have found a bug</strong>, you can post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a>&nbsp;in the support forums.  We would love to hear from you!  If you are comfortable writing a reproducible bug report,&nbsp;<a href=\"https://core.trac.wordpress.org/newticket\">file one on WordPress Trac</a>, where you can also find&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">a list of known bugs</a>.</em></p>\n\n\n\n<p class=\"has-text-align-right\"><strong><em>Props to <a href=\'https://profiles.wordpress.org/lukecarbis/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>lukecarbis</a> for the haiku, <a href=\'https://profiles.wordpress.org/webcommsat/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>webcommsat</a> and <a href=\'https://profiles.wordpress.org/marybaum/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>marybaum</a> for peer reviewing!</em></strong></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>Five-eight in two weeks<br>So test your plugins and themes<br>Update your readme</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"10912\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:58:\"\n		\n		\n		\n		\n		\n				\n		\n\n					\n										\n					\n		\n		\n\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"WP Briefing: Episode 12: WordPress – In Person!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2021/07/episode-12-wordpress-in-person/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 05 Jul 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=10889\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:384:\"In this episode, Josepha Haden Chomphosy talks about WordPress &#8211; In Person! The WordPress events that provide the dark matter of connection that helps sustain the open source project. Have a question you&#8217;d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/07/WP-Briefing-012.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:13118:\"\n<p>In this episode, Josepha Haden Chomphosy talks about WordPress &#8211; In Person! The WordPress events that provide the dark matter of connection that helps sustain the open source project.</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href=\"mailto:wpbriefing@wordpress.org\">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<p>Editor:<a href=\"https://profiles.wordpress.org/dustinhartzler/\"> Dustin Hartzler</a></p>\n\n\n\n<p>Logo:<a href=\"https://profiles.wordpress.org/beafialho/\"> Beatriz Fialho</a></p>\n\n\n\n<p>Production:<a href=\"https://profiles.wordpress.org/mkaz/\"> </a><a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a></p>\n\n\n\n<p>Song: Fearless First by Kevin MacLeod</p>\n\n\n\n<h2>References</h2>\n\n\n\n<p><a href=\"https://en.wikipedia.org/wiki/Tragedy_of_the_commons\">The tragedy of the commons</a></p>\n\n\n\n<p><a href=\"https://wordpress.org/news/2021/06/wordpress-5-8-release-candidate/\">WordPress 5.8 Release Candidate announcement </a></p>\n\n\n\n<h2>Transcript </h2>\n\n\n\n<span id=\"more-10889\"></span>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:11</p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Josepha Haden Chomphosy. Here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:39</p>\n\n\n\n<p>Today we&#8217;re talking about one of my favorite parts of the project &#8211; WordPress events. The in-person component of the project is the dark matter that helps us build resilience and thrive as a group. A lot of what I&#8217;m going to share applies to every WordPress event, whether it&#8217;s a meetup or workshop, a contributor day, any other sort of format. But I&#8217;ll be focused on WordCamps. It&#8217;s been a while since we had any in-person WordCamps. Our last two were WordCamp Malaga in Spain and WordCamp Greenville in the US. But that hasn&#8217;t stopped anyone from gathering people together online. Which honestly makes a lot of sense for WordPress. Because there are many reasons we gather, the main three reasons are connecting, inspiring, and contributing. It&#8217;s true. It says so right in our documentation, &#8220;paper rustling.&#8221; All WordPress events should connect WordPress users, inspire people to do more with WordPress, and contribute to the WordPress project. As an aside, I&#8217;ll tell you that some groups also get to collaborate and educate in there, but connect, inspire, contribute. Those are the big three. And that&#8217;s what I&#8217;m talking about today. And if you subscribe to this podcast for the back office deep cuts, I&#8217;ll also have a few of those for you. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:57</p>\n\n\n\n<p>Alright, so first up, connect. WordCamps are generally annual-ish gatherings organized by local WordPress meetup groups. They&#8217;re not meant to be big or fancy. The definition of the minimum viable product for WordCamp is 50 people gathered all day to talk about WordPress. They are intentionally affordable to allow people from all walks of life to attend, meet, share and learn. This is made possible by donations and sponsorships from local businesses and larger businesses in the WordPress ecosystem. And this helps us get people connected to those in their community that works with or are sustained by WordPress. That connection feeds into the overall health of the global WordPress project. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:45</p>\n\n\n\n<p>Next up is inspire. WordCamps do not discriminate. They are open to any WordPress users, developers, designers, or other enthusiasts, regardless of their level of experience. And because of this, sessions generally span a variety of formats. So presentations or live demos to workshops or panels, any other format you can think of. But that also means that there are a variety of skill levels represented. There&#8217;s always content about how to use WordPress. That’s a given. But you can also count on content that inspires people to do more with their own dreams and aspirations. When I was still organizing WordCamps, my favorite thing was seeing people who came back year after year, putting into practice something that they learned the year before. It is that <em>Choose Your Own Adventure</em> aspect to WordCamps that lets people see the edge of their ideas and then expand that just a little bit further. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:42</p>\n\n\n\n<p>And finally, contribute. WordCamps often have a contribution component to them. Sometimes it&#8217;s just a talk telling you how you can get more involved in the WordPress project. But sometimes, it&#8217;s a whole contributor day. And those range in size from single focus, like everyone, will show up and learn how to review a theme or a focus from every team that we have, like at the big flagship events where we gather hundreds of people into a room just to contribute to WordPress and all of the teams that go with it. Getting started with contributing can be daunting, but it is also essential to avoid something called the Tragedy of the Commons, an economic concept. So I&#8217;ll share a link to that in the show notes below. But the most important thing, the most important thing to remember, is that WordPress is open source. And we asked people to help us keep this great tool running by giving back a little bit of their time if they have gotten any benefit from the WordPress project or CMS over the course of their careers.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:40</p>\n\n\n\n<p>So that&#8217;s it. The three big things you can get from a WordCamp. I know that I can&#8217;t wait to get back to them myself because while a lot of these things can still happen online and do, it&#8217;s really hard to replace the dark matter of in-person connections for open source projects. And since we&#8217;re talking dark matter anyway, let&#8217;s dig into it a little.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:01</p>\n\n\n\n<p>At the start of the section, I mentioned that WordCamps are local, locally organized, and people are encouraged to attend locally. But I am part of a group that ends up traveling to a lot of WordCamps. If you don&#8217;t know about the unseen work of WordPress, this raises eyebrows. So here is some clarification around the back office work that some of these traveling WordCampers often do. When I listed these out, there were about 20 different tasks, 20 different jobs, which was, frankly, a bit overwhelming when I listed them that way. So I&#8217;ve grouped them into kind of two genres, each with a group of current versus future types of work. So my two big buckets, big picture stuff, and then community stewardship.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:50</p>\n\n\n\n<p>The big picture stuff, our first big genre here, when you&#8217;re looking at current topics, current issues kind of information, when we&#8217;re working on big picture stuff, you get the clarification of the mission or vision of WordPress, the sharing of open source methods or processes that we use in the WordPress project, and also sometimes those goal-setting conversations that you have to have both because we have a bunch of teams and team reps, that have a lot of really great ideas about what can be done in their teams to help WordPress succeed. But then also, because when you are working, when you&#8217;re contributing to a single team in the project, it can sometimes be hard to know how your work relates to the overall goals and visions of WordPress. And so that&#8217;s part of the work that gets done that I do there.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:43</p>\n\n\n\n<p>And when you&#8217;re looking at future topics, future issues, the second part of this genre, that stuff like starting conversations or discussions around what the future holds for WordPress, and that&#8217;s the project as well as the technology or hearing from people about big things coming up for them. And any content that can support it, anything that I can provide to support those big things. It&#8217;s also a good time for me and others to identify trends based on what I see in presentations or what I hear from people at social functions. Really, it&#8217;s just a huge opportunity for information gathering to make sure that I know what everyone else in the project is trying to do and if they understand what the project is trying to do.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>07:32</p>\n\n\n\n<p>And then the second big genre of things that happen in that dark matter kind of work at WordCamps is what I call community stewardship—so taking care of the community itself for the project itself. And a lot of that work is actually incident response kind of work. So conflict resolution, mediation often happens at in-person events, but also uncovering the shared foundations, the shared understanding for upcoming changes. So a lot of really, in the weeds kind of change management work. And for me, it&#8217;s certainly doing my best as a cultural liaison when I do see that there has been some miscommunication or gathering context for the latest disagreement that people are having with me so that I can clarify anything that was misunderstood from what I said. And also a little bit of policy clarification, just explaining why we do things and the way we do them. So for community stewardship, that&#8217;s kind of the current stuff that we look at. And that I do when I&#8217;m traveling for WordCamps. </p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>08:36</p>\n\n\n\n<p>And then for the future tasks that we do with community stewardship in the project, that stuff like training, and that&#8217;s training team reps, community deputies, or new contributors like it&#8217;s, it&#8217;s not really one type of training, necessarily. But then also, all of the checking in with our organizers, team reps, volunteers, sponsors, everyone like that, to make sure that what we have in the project and what&#8217;s happening in the project, the tools that we have, the experience that contributors have while they are working here, and WordPress is good, and is what they need. We&#8217;ve got a lot of tools to get things done in WordPress, and we can always make them better. And so checking in with people to kind of see how those processes are, how the tools are making sure that I have an idea of where our holes are and what needs to be patched, and how we can patch them in the long run. So that&#8217;s all of the future planning kind of work and topic stuff, just you know, making sure that WordPress has what it needs to survive long into the future and long after I&#8217;m doing anything with it, and long after you&#8217;re doing anything with it either.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>09:56</p>\n\n\n\n<p>So, lots and lots of unseen work being done at our in-person events. But folks who keep a keen eye on the online global work of WordPress will probably recognize that a lot of that work is also done routinely on make.wordpress.org and within the making WordPress Slack. There’s just, I don&#8217;t know, there&#8217;s just something different about receiving information from a human being with a face rather than an avatar with a photo. So I guess at the end of the day, that means the dark matter that keeps open source together is really an issue of communication. And you&#8217;ll get no arguments for me there.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>10:44</p>\n\n\n\n<p>That brings us now to our small list of big things. And there&#8217;s really just one big thing. And that&#8217;s WordPress 5.8. We are about two weeks away from this big release; the community has been working tirelessly on it. And it&#8217;s shaping up to be one of the most tested releases that we&#8217;ve had in a long time. Myself, I&#8217;m grateful to see so much activity before the release. Since 5.8 and 5.9 releases represent such monumental shifts in our software, I&#8217;m incredibly grateful to see so much activity prior to the release, especially in the beta period. We&#8217;ve been testing everything for it feels like six or eight months, and we&#8217;re really starting to see the positive benefits of that. And I think that we, the WordPress community, should be really proud of everything that we&#8217;re going to ship in 2021. Okay, so that was less of a small list of big things and really like one big thing with a generous garnish of encouragement, but you deserve it. So thank you for tuning in today for the WordPress briefing. I&#8217;m your host, Josepha Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks.</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"10889\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n	hourly	\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n	1	\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 22 Oct 2021 15:48:53 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:25:\"strict-transport-security\";s:11:\"max-age=360\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Tue, 19 Oct 2021 21:47:11 GMT\";s:4:\"link\";s:63:\"<https://wordpress.org/news/wp-json/>; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20210205134904\";}','no');
INSERT INTO `wpy6_options` VALUES (1088855,'_transient_timeout_elementor_remote_info_api_data_3.4.6','1634967442','no'),(1088856,'_transient_elementor_remote_info_api_data_3.4.6','a:4:{s:9:\"timestamp\";s:10:\"1634923003\";s:14:\"upgrade_notice\";a:3:{s:7:\"version\";s:5:\"2.0.0\";s:7:\"message\";s:0:\"\";s:11:\"update_link\";s:0:\"\";}s:11:\"pro_widgets\";a:64:{i:0;a:4:{s:4:\"name\";s:5:\"posts\";s:5:\"title\";s:5:\"Posts\";s:4:\"icon\";s:15:\"eicon-post-list\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:1;a:4:{s:4:\"name\";s:9:\"portfolio\";s:5:\"title\";s:9:\"Portfolio\";s:4:\"icon\";s:18:\"eicon-gallery-grid\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:2;a:4:{s:4:\"name\";s:7:\"gallery\";s:5:\"title\";s:7:\"Gallery\";s:4:\"icon\";s:23:\"eicon-gallery-justified\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:3;a:4:{s:4:\"name\";s:4:\"form\";s:5:\"title\";s:4:\"Form\";s:4:\"icon\";s:21:\"eicon-form-horizontal\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:4;a:4:{s:4:\"name\";s:5:\"login\";s:5:\"title\";s:5:\"Login\";s:4:\"icon\";s:15:\"eicon-lock-user\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:5;a:4:{s:4:\"name\";s:6:\"slides\";s:5:\"title\";s:6:\"Slides\";s:4:\"icon\";s:12:\"eicon-slides\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:6;a:4:{s:4:\"name\";s:8:\"nav-menu\";s:5:\"title\";s:8:\"Nav Menu\";s:4:\"icon\";s:14:\"eicon-nav-menu\";s:10:\"categories\";s:33:\"[\"pro-elements\",\"theme-elements\"]\";}i:7;a:4:{s:4:\"name\";s:17:\"animated-headline\";s:5:\"title\";s:17:\"Animated Headline\";s:4:\"icon\";s:23:\"eicon-animated-headline\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:8;a:4:{s:4:\"name\";s:10:\"price-list\";s:5:\"title\";s:10:\"Price List\";s:4:\"icon\";s:16:\"eicon-price-list\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:9;a:4:{s:4:\"name\";s:11:\"price-table\";s:5:\"title\";s:11:\"Price Table\";s:4:\"icon\";s:17:\"eicon-price-table\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:10;a:4:{s:4:\"name\";s:8:\"flip-box\";s:5:\"title\";s:8:\"Flip Box\";s:4:\"icon\";s:14:\"eicon-flip-box\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:11;a:4:{s:4:\"name\";s:14:\"call-to-action\";s:5:\"title\";s:14:\"Call to Action\";s:4:\"icon\";s:20:\"eicon-image-rollover\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:12;a:4:{s:4:\"name\";s:14:\"media-carousel\";s:5:\"title\";s:14:\"Media Carousel\";s:4:\"icon\";s:20:\"eicon-media-carousel\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:13;a:4:{s:4:\"name\";s:20:\"testimonial-carousel\";s:5:\"title\";s:20:\"Testimonial Carousel\";s:4:\"icon\";s:26:\"eicon-testimonial-carousel\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:14;a:4:{s:4:\"name\";s:7:\"reviews\";s:5:\"title\";s:7:\"Reviews\";s:4:\"icon\";s:12:\"eicon-review\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:15;a:4:{s:4:\"name\";s:17:\"table-of-contents\";s:5:\"title\";s:17:\"Table of Contents\";s:4:\"icon\";s:23:\"eicon-table-of-contents\";s:10:\"categories\";s:33:\"[\"pro-elements\",\"theme-elements\"]\";}i:16;a:4:{s:4:\"name\";s:9:\"countdown\";s:5:\"title\";s:9:\"Countdown\";s:4:\"icon\";s:15:\"eicon-countdown\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:17;a:4:{s:4:\"name\";s:13:\"share-buttons\";s:5:\"title\";s:13:\"Share Buttons\";s:4:\"icon\";s:11:\"eicon-share\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:18;a:4:{s:4:\"name\";s:11:\"search-form\";s:5:\"title\";s:11:\"Search Form\";s:4:\"icon\";s:17:\"eicon-site-search\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:19;a:4:{s:4:\"name\";s:10:\"author-box\";s:5:\"title\";s:10:\"Author Box\";s:4:\"icon\";s:12:\"eicon-person\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:20;a:4:{s:4:\"name\";s:13:\"post-comments\";s:5:\"title\";s:13:\"Post Comments\";s:4:\"icon\";s:14:\"eicon-comments\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:21;a:4:{s:4:\"name\";s:15:\"post-navigation\";s:5:\"title\";s:15:\"Post Navigation\";s:4:\"icon\";s:21:\"eicon-post-navigation\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:22;a:4:{s:4:\"name\";s:9:\"post-info\";s:5:\"title\";s:9:\"Post Info\";s:4:\"icon\";s:15:\"eicon-post-info\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:23;a:4:{s:4:\"name\";s:7:\"sitemap\";s:5:\"title\";s:7:\"Sitemap\";s:4:\"icon\";s:13:\"eicon-sitemap\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:24;a:4:{s:4:\"name\";s:11:\"breadcrumbs\";s:5:\"title\";s:11:\"Breadcrumbs\";s:4:\"icon\";s:11:\"eicon-yoast\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:25;a:4:{s:4:\"name\";s:10:\"blockquote\";s:5:\"title\";s:10:\"Blockquote\";s:4:\"icon\";s:16:\"eicon-blockquote\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:26;a:4:{s:4:\"name\";s:19:\"wc-archive-products\";s:5:\"title\";s:16:\"Archive Products\";s:4:\"icon\";s:14:\"eicon-products\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:27;a:4:{s:4:\"name\";s:31:\"woocommerce-archive-description\";s:5:\"title\";s:19:\"Archive Description\";s:4:\"icon\";s:25:\"eicon-product-description\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:28;a:4:{s:4:\"name\";s:20:\"woocommerce-products\";s:5:\"title\";s:8:\"Products\";s:4:\"icon\";s:14:\"eicon-products\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:29;a:4:{s:4:\"name\";s:22:\"woocommerce-breadcrumb\";s:5:\"title\";s:23:\"WooCommerce Breadcrumbs\";s:4:\"icon\";s:25:\"eicon-product-breadcrumbs\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:30;a:4:{s:4:\"name\";s:14:\"wc-add-to-cart\";s:5:\"title\";s:18:\"Custom Add To Cart\";s:4:\"icon\";s:17:\"eicon-woocommerce\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:31;a:4:{s:4:\"name\";s:11:\"wc-elements\";s:5:\"title\";s:17:\"WooCommerce Pages\";s:4:\"icon\";s:19:\"eicon-product-pages\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:32;a:4:{s:4:\"name\";s:13:\"wc-categories\";s:5:\"title\";s:18:\"Product Categories\";s:4:\"icon\";s:24:\"eicon-product-categories\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:33;a:4:{s:4:\"name\";s:21:\"woocommerce-menu-cart\";s:5:\"title\";s:9:\"Menu Cart\";s:4:\"icon\";s:10:\"eicon-cart\";s:10:\"categories\";s:41:\"[\"theme-elements\",\"woocommerce-elements\"]\";}i:34;a:4:{s:4:\"name\";s:25:\"woocommerce-product-title\";s:5:\"title\";s:13:\"Product Title\";s:4:\"icon\";s:19:\"eicon-product-title\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:35;a:4:{s:4:\"name\";s:26:\"woocommerce-product-images\";s:5:\"title\";s:14:\"Product Images\";s:4:\"icon\";s:20:\"eicon-product-images\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:36;a:4:{s:4:\"name\";s:25:\"woocommerce-product-price\";s:5:\"title\";s:13:\"Product Price\";s:4:\"icon\";s:19:\"eicon-product-price\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:37;a:4:{s:4:\"name\";s:31:\"woocommerce-product-add-to-cart\";s:5:\"title\";s:11:\"Add To Cart\";s:4:\"icon\";s:25:\"eicon-product-add-to-cart\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:38;a:4:{s:4:\"name\";s:26:\"woocommerce-product-rating\";s:5:\"title\";s:14:\"Product Rating\";s:4:\"icon\";s:20:\"eicon-product-rating\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:39;a:4:{s:4:\"name\";s:25:\"woocommerce-product-stock\";s:5:\"title\";s:13:\"Product Stock\";s:4:\"icon\";s:19:\"eicon-product-stock\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:40;a:4:{s:4:\"name\";s:24:\"woocommerce-product-meta\";s:5:\"title\";s:12:\"Product Meta\";s:4:\"icon\";s:18:\"eicon-product-meta\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:41;a:4:{s:4:\"name\";s:37:\"woocommerce-product-short-description\";s:5:\"title\";s:17:\"Short Description\";s:4:\"icon\";s:25:\"eicon-product-description\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:42;a:4:{s:4:\"name\";s:29:\"woocommerce-product-data-tabs\";s:5:\"title\";s:17:\"Product Data Tabs\";s:4:\"icon\";s:18:\"eicon-product-tabs\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:43;a:4:{s:4:\"name\";s:42:\"woocommerce-product-additional-information\";s:5:\"title\";s:22:\"Additional Information\";s:4:\"icon\";s:19:\" eicon-product-info\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:44;a:4:{s:4:\"name\";s:27:\"woocommerce-product-related\";s:5:\"title\";s:15:\"Product Related\";s:4:\"icon\";s:21:\"eicon-product-related\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:45;a:4:{s:4:\"name\";s:26:\"woocommerce-product-upsell\";s:5:\"title\";s:7:\"Upsells\";s:4:\"icon\";s:20:\"eicon-product-upsell\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:46;a:4:{s:4:\"name\";s:6:\"lottie\";s:5:\"title\";s:6:\"Lottie\";s:4:\"icon\";s:12:\"eicon-lottie\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:47;a:4:{s:4:\"name\";s:15:\"facebook-button\";s:5:\"title\";s:15:\"Facebook Button\";s:4:\"icon\";s:23:\"eicon-facebook-like-box\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:48;a:4:{s:4:\"name\";s:17:\"facebook-comments\";s:5:\"title\";s:17:\"Facebook Comments\";s:4:\"icon\";s:23:\"eicon-facebook-comments\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:49;a:4:{s:4:\"name\";s:14:\"facebook-embed\";s:5:\"title\";s:14:\"Facebook Embed\";s:4:\"icon\";s:14:\"eicon-fb-embed\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:50;a:4:{s:4:\"name\";s:13:\"facebook-page\";s:5:\"title\";s:13:\"Facebook Page\";s:4:\"icon\";s:13:\"eicon-fb-feed\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:51;a:4:{s:4:\"name\";s:7:\"hotspot\";s:5:\"title\";s:7:\"Hotspot\";s:4:\"icon\";s:19:\"eicon-image-hotspot\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:52;a:4:{s:4:\"name\";s:13:\"paypal-button\";s:5:\"title\";s:13:\"PayPal Button\";s:4:\"icon\";s:19:\"eicon-paypal-button\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:53;a:4:{s:4:\"name\";s:14:\"code-highlight\";s:5:\"title\";s:14:\"Code Highlight\";s:4:\"icon\";s:20:\"eicon-code-highlight\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:54;a:4:{s:4:\"name\";s:14:\"video-playlist\";s:5:\"title\";s:14:\"Video Playlist\";s:4:\"icon\";s:20:\"eicon-video-playlist\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:55;a:4:{s:4:\"name\";s:8:\"template\";s:5:\"title\";s:8:\"Template\";s:4:\"icon\";s:19:\"eicon-document-file\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:56;a:4:{s:4:\"name\";s:15:\"theme-site-logo\";s:5:\"title\";s:9:\"Site Logo\";s:4:\"icon\";s:15:\"eicon-site-logo\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:57;a:4:{s:4:\"name\";s:16:\"theme-site-title\";s:5:\"title\";s:10:\"Site Title\";s:4:\"icon\";s:16:\"eicon-site-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:58;a:4:{s:4:\"name\";s:16:\"theme-page-title\";s:5:\"title\";s:10:\"Page Title\";s:4:\"icon\";s:19:\"eicon-archive-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:59;a:4:{s:4:\"name\";s:16:\"theme-post-title\";s:5:\"title\";s:10:\"Post Title\";s:4:\"icon\";s:16:\"eicon-post-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:60;a:4:{s:4:\"name\";s:18:\"theme-post-excerpt\";s:5:\"title\";s:12:\"Post Excerpt\";s:4:\"icon\";s:18:\"eicon-post-excerpt\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:61;a:4:{s:4:\"name\";s:25:\"theme-post-featured-image\";s:5:\"title\";s:14:\"Featured Image\";s:4:\"icon\";s:20:\"eicon-featured-image\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:62;a:4:{s:4:\"name\";s:19:\"theme-archive-title\";s:5:\"title\";s:13:\"Archive Title\";s:4:\"icon\";s:19:\"eicon-archive-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:63;a:4:{s:4:\"name\";s:13:\"archive-posts\";s:5:\"title\";s:13:\"Archive Posts\";s:4:\"icon\";s:19:\"eicon-archive-posts\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}}s:17:\"canary_deployment\";a:2:{s:11:\"plugin_info\";a:11:{s:2:\"id\";s:23:\"w.org/plugins/elementor\";s:4:\"slug\";s:9:\"elementor\";s:6:\"plugin\";s:23:\"elementor/elementor.php\";s:11:\"new_version\";s:5:\"3.4.0\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/plugin/elementor.3.4.0.zip\";s:3:\"url\";s:40:\"https://wordpress.org/plugins/elementor/\";s:5:\"icons\";a:3:{s:2:\"2x\";s:62:\"https://ps.w.org/elementor/assets/icon-256x256.png?rev=1427768\";s:2:\"1x\";s:54:\"https://ps.w.org/elementor/assets/icon.svg?rev=1426809\";s:3:\"svg\";s:54:\"https://ps.w.org/elementor/assets/icon.svg?rev=1426809\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:65:\"https://ps.w.org/elementor/assets/banner-1544x500.png?rev=1475479\";s:2:\"1x\";s:64:\"https://ps.w.org/elementor/assets/banner-772x250.png?rev=1475479\";}s:11:\"banners_rtl\";a:0:{}s:6:\"tested\";s:5:\"5.8.1\";s:12:\"requires_php\";s:3:\"5.6\";}s:10:\"conditions\";a:1:{i:0;a:1:{i:0;a:3:{s:4:\"type\";s:8:\"language\";s:9:\"languages\";a:26:{i:0;s:5:\"he_IL\";i:1;s:5:\"en_GB\";i:2;s:5:\"en_NZ\";i:3;s:5:\"en_ZA\";i:4;s:5:\"en_AU\";i:5;s:5:\"en_CA\";i:6;s:5:\"sv_SE\";i:7;s:5:\"da_DK\";i:8;s:5:\"fr_FR\";i:9;s:5:\"nl_NL\";i:10;s:5:\"nb_NO\";i:11;s:5:\"de_AT\";i:12;s:2:\"fi\";i:13;s:5:\"it_IT\";i:14;s:5:\"nn_NO\";i:15;s:5:\"de_CH\";i:16;s:5:\"en_GB\";i:17;s:5:\"is_IS\";i:18;s:2:\"ga\";i:19;s:5:\"fr_BE\";i:20;s:5:\"nl_BE\";i:21;s:3:\"ast\";i:22;s:5:\"lb_LU\";i:23;s:5:\"es_ES\";i:24;s:5:\"pt_PT\";i:25;s:3:\"mlt\";}s:8:\"operator\";s:2:\"in\";}}}}}','no'),(1088866,'_site_transient_boldgrid_plugins_filtered','a:2:{s:35:\"boldgrid-backup/boldgrid-backup.php\";a:13:{s:4:\"Name\";s:12:\"Total Upkeep\";s:9:\"PluginURI\";s:41:\"https://www.boldgrid.com/boldgrid-backup/\";s:7:\"Version\";s:7:\"1.14.13\";s:11:\"Description\";s:159:\"Automated backups, remote backup to Amazon S3 and Google Drive, stop website crashes before they happen and more. Total Upkeep is the backup solution you need.\";s:6:\"Author\";s:8:\"BoldGrid\";s:9:\"AuthorURI\";s:25:\"https://www.boldgrid.com/\";s:10:\"TextDomain\";s:15:\"boldgrid-backup\";s:10:\"DomainPath\";s:10:\"/languages\";s:7:\"Network\";b:0;s:10:\"RequiresWP\";s:0:\"\";s:11:\"RequiresPHP\";s:0:\"\";s:5:\"Title\";s:12:\"Total Upkeep\";s:10:\"AuthorName\";s:8:\"BoldGrid\";}s:51:\"boldgrid-backup-premium/boldgrid-backup-premium.php\";a:13:{s:4:\"Name\";s:20:\"Total Upkeep Premium\";s:9:\"PluginURI\";s:41:\"https://www.boldgrid.com/boldgrid-backup/\";s:7:\"Version\";s:5:\"1.3.0\";s:11:\"Description\";s:46:\"Premium extension for the Total Upkeep plugin.\";s:6:\"Author\";s:8:\"BoldGrid\";s:9:\"AuthorURI\";s:25:\"https://www.boldgrid.com/\";s:10:\"TextDomain\";s:15:\"boldgrid-backup\";s:10:\"DomainPath\";s:10:\"/languages\";s:7:\"Network\";b:0;s:10:\"RequiresWP\";s:0:\"\";s:11:\"RequiresPHP\";s:0:\"\";s:5:\"Title\";s:20:\"Total Upkeep Premium\";s:10:\"AuthorName\";s:8:\"BoldGrid\";}}','no'),(1088863,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1634924495;s:7:\"checked\";a:7:{s:17:\"bsa-council-theme\";s:5:\"1.5.8\";s:10:\"scouttroop\";s:4:\"1.25\";s:14:\"twentynineteen\";s:3:\"2.1\";s:15:\"twentyseventeen\";s:3:\"2.8\";s:13:\"twentysixteen\";s:3:\"2.5\";s:12:\"twentytwenty\";s:3:\"1.8\";s:15:\"twentytwentyone\";s:3:\"1.4\";}s:8:\"response\";a:0:{}s:9:\"no_update\";a:5:{s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"2.1\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.2.1.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentyseventeen\";a:6:{s:5:\"theme\";s:15:\"twentyseventeen\";s:11:\"new_version\";s:3:\"2.8\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentyseventeen/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentyseventeen.2.8.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:13:\"twentysixteen\";a:6:{s:5:\"theme\";s:13:\"twentysixteen\";s:11:\"new_version\";s:3:\"2.5\";s:3:\"url\";s:43:\"https://wordpress.org/themes/twentysixteen/\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/theme/twentysixteen.2.5.zip\";s:8:\"requires\";s:3:\"4.4\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"1.8\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.1.8.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentytwentyone\";a:6:{s:5:\"theme\";s:15:\"twentytwentyone\";s:11:\"new_version\";s:3:\"1.4\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentytwentyone/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentytwentyone.1.4.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.6\";}}s:12:\"translations\";a:0:{}}','no'),(1088862,'elementor_pro_remote_info_api_data_3.4.2','a:2:{s:7:\"timeout\";i:1634967612;s:5:\"value\";s:36598:\"{\"stable_version\":\"3.4.2\",\"last_updated\":\"2021-08-31 15:40:43\",\"sections\":\"a:2:{s:11:\\\"description\\\";s:161:\\\"Elementor Pro adds new features to the Elementor Page Builder plugin. Control your conversions, your user engagement, your entire website, from one page builder.\\\";s:9:\\\"changelog\\\";s:32546:\\\"<h4>3.4.2 - 2021-10-12<\\/h4>\\n<ul>\\n<li>Fix: Icons color style conflicts when Font-Awesome Inline experiment is active in Share Buttons widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/16435\\\">#16435<\\/a>)<\\/li>\\n<li>Fix: Mini Cart hides page content when closed in Menu Cart widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/16305\\\">#16305<\\/a>)<\\/li>\\n<li>Fix: UI glitches in the Editor edit mode when inserting Post Content widget and Font-Awesome Inline experiment is active in Single Post template (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/16358\\\">#16358<\\/a>)<\\/li>\\n<li>Fix: Slides per view controls disappeared from multiple breakpoints in Testimonial Carousel<\\/li>\\n<li>Fix: Product variations UI glitch in Menu Cart widget<\\/li>\\n<li>Fix: Buttons UI glitch on Safari browser in Menu Cart widget<\\/li>\\n<\\/ul>\\n<h4>3.4.1 - 2021-09-01<\\/h4>\\n<ul>\\n<li>Fix: Sticky functionality is not working if the Additional Custom Breakpoints experiment is active (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/16186\\\">#16186<\\/a>)<\\/li>\\n<li>Fix: Slideshow skin UI glitch in Media Carousel widget<\\/li>\\n<li>Fix: Product price typography weight control is not working as expected in Menu Cart widget<\\/li>\\n<\\/ul>\\n<h4>3.4.0 - 2021-09-01<\\/h4>\\n<ul>\\n<li>Tweak: Added new Mini Cart layout type in Menu Cart widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11312\\\">#11312<\\/a>)<\\/li>\\n<li>Tweak: Added styling options for Cart, Products, and Cart buttons in Menu Cart widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/14952\\\">#14952<\\/a>)<\\/li>\\n<li>Tweak: Added the ability to open cart automatically when an item is added in Menu Cart widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/14119\\\">#14119<\\/a>)<\\/li>\\n<li>Tweak: Added the ability to remove an item from cart without reloading the page with an AJAX request (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/9531\\\">#9531<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/10875\\\">#10875<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11309\\\">#11309<\\/a>)<\\/li>\\n<li>Tweak: Added Load More AJAX functionality to Posts widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12126\\\">#12126<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/1284\\\">#1284<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/14557\\\">#14557<\\/a>)<\\/li>\\n<li>Tweak: Added Vimeo support to the Video Playlist widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15319\\\">#15319<\\/a>)<\\/li>\\n<li>Tweak: Improved asset loading performance by serving lighter JS files (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/8572\\\">#8572<\\/a>)<\\/li>\\n<li>Tweak: Added query string to the URL only after the first video is played in Video Playlist widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15348\\\">#15348<\\/a>)<\\/li>\\n<li>Tweak: Added various layout options with more responsive controls and cart structure options in Menu Cart widget<\\/li>\\n<li>Tweak: Added the option to open the menu cart by click or hover in Menu Cart widget<\\/li>\\n<li>Tweak: Added the ability to choose a specific product to draw data from in WooCommerce Dynamic tags<\\/li>\\n<li>Tweak: Removed auto-scroll to the widget location when arriving from external URL in Video Playlist widget<\\/li>\\n<li>Tweak: Removed the Video Playlist widget from the Experiments list<\\/li>\\n<li>Tweak: Added descriptive error messages for MailChimp action after submit and on form submit in Forms widget<\\/li>\\n<li>Tweak: Added tooltip trigger None and Hover for link in Hotspot widget<\\/li>\\n<li>Tweak: Added responsive controls to Offset and Effects Offset in Sticky options<\\/li>\\n<li>Tweak: Added responsive control to Alignment in Testimonial Carousel widget<\\/li>\\n<li>Tweak: Adjusted Motion Effects module to support future feature<\\/li>\\n<li>Tweak: Added future compatibility to support better loading of <code>eicons<\\/code> font<\\/li>\\n<li>Tweak: Changed Rename Part title and button color in Theme Builder<\\/li>\\n<li>Fix: Products don\'t appear on the cart while editing in Menu Cart widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15451\\\">#15451<\\/a>)<\\/li>\\n<li>Fix: Videos always start muted in the Video Playlist widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15292\\\">#15292<\\/a>)<\\/li>\\n<li>Fix: Unnecessary spacing if submenu indicator is set to None in Nav Menu widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15365\\\">#15365<\\/a>)<\\/li>\\n<li>Fix: MailChimp double opt-in feature doesn\'t work in Forms widget<\\/li>\\n<li>Fix: Fetching MailChimp groups field blocks the loading of the rest of the fields in the Form widget<\\/li>\\n<li>Fix: Missing field IDs causes forms not to be sent in Forms widget<\\/li>\\n<li>Fix: Full Content Skin is not working properly when inserted twice on the same page in Posts widget<\\/li>\\n<li>Fix: Avoid Duplicates option doesn\'t exclude manual selections in Posts widget<\\/li>\\n<li>Fix: Submenu indicator alignment issue in Nav menu widget<\\/li>\\n<li>Fix: Query control deprecated message appears when debug mode is defined<\\/li>\\n<li>Fix: Tweet Button icon incorrect color and size when the icon is rendered as SVG in Blockquote widget<\\/li>\\n<li>Fix: Video icon size is not changing on Active state in Video Playlist widget<\\/li>\\n<li>Fix: Header icon color is not working in Table Of Content widget<\\/li>\\n<li>Fix: Icons style glitches when Font Awesome Inline experiment is active in Video Playlist widget<\\/li>\\n<li>Fix: Bullet markers are not visible on preview mode when Font Awesome Inline experiment is active in Table of Content widget<\\/li>\\n<li>Fix: UI Glitch when Font-Awesome Inline experiment is active in Price Table widget<\\/li>\\n<li>Fix: Submenu Indicator appears larger when Font Awesome Inline experiment is active in Nav Menu widget<\\/li>\\n<li>Fix: Part name is deleted when clicking on the &quot;Change&quot; Button without changing the name in Theme Builder<\\/li>\\n<li>Fix: Redundant pagination queries in the Editor<\\/li>\\n<li>Deprecated: Remove all usages of <code>ElementorUtils::get_create_new_post_url()<\\/code><\\/li>\\n<li>Deprecated: See all deprecations to this version in our <a href=\\\"https:\\/\\/developers.elementor.com\\/v3-4-planned-deprecations\\/\\\">Developers Deprecations Post<\\/a><\\/li>\\n<\\/ul>\\n<h4>3.3.8 - 2021-08-23<\\/h4>\\n<ul>\\n<li>Fix: Products grid width issue when adjusting columns and rows in Products widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/16001\\\">#16001<\\/a>)<\\/li>\\n<li>Fix: Font Awesome Inline experiment causes icons glitch in Price Table widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/16045\\\">#16045<\\/a>)<\\/li>\\n<li>Fix: reCAPTCHA v3 <code>z-index<\\/code> is lower than the Section\'s background color<\\/li>\\n<li>Fix: Style missing when Font Awesome inline experiment is active in Post Info widget<\\/li>\\n<li>Fix: Font Awesome icons were not loaded in Post Info widget<\\/li>\\n<li>Fix: Zero character can\'t be used as a placeholder in Number field in Form widget<\\/li>\\n<li>Fix: Carousels are not working properly in the Editor when Additional Custom Breakpoints experiment is active<\\/li>\\n<\\/ul>\\n<h4>3.3.7 - 2021-08-15<\\/h4>\\n<ul>\\n<li>Tweak: Added support for Additional Custom Breakpoints in Nav Menu widget<\\/li>\\n<li>Tweak: Added support for Additional Custom breakpoints in Motion Effects<\\/li>\\n<li>Fix: Columns didn\'t respond to changes in Gallery widget if Additional Custom Breakpoints Experiment is active<\\/li>\\n<\\/ul>\\n<h4>3.3.6 - 2021-08-10<\\/h4>\\n<ul>\\n<li>Tweak: Added support for future feature in Nav Menu widget<\\/li>\\n<li>Fix: WooCommerce responsive grid styles are not being reflected in Product Related widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15857\\\">#15857<\\/a>)<\\/li>\\n<li>Fix: WooCommerce responsive grid styles are not being reflected in Upsells widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15857\\\">#15857<\\/a>)<\\/li>\\n<li>Fix: WooCommerce responsive grid styles are not being reflected in Product Categories widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15857\\\">#15857<\\/a>)<\\/li>\\n<\\/ul>\\n<h4>3.3.5 - 2021-08-01<\\/h4>\\n<ul>\\n<li>Fix: Responsive layout glitches in Products and Products Archive widgets (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15773\\\">#15773<\\/a>)<\\/li>\\n<li>Fix: reCAPTCHA V3 integration conflict with required fields validation in Forms widget<\\/li>\\n<\\/ul>\\n<h4>3.3.4 - 2021-07-21<\\/h4>\\n<ul>\\n<li>Fix: Grid layout glitch in WooCommerce Products Archive widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15718\\\">#15718<\\/a>)<\\/li>\\n<\\/ul>\\n<h4>3.3.3 - 2021-07-20<\\/h4>\\n<ul>\\n<li>Tweak: Added a descriptive message in Collect Submissions action after submit<\\/li>\\n<li>Tweak: Added future compatibility for Additional Custom Breakpoints for Pro widgets<\\/li>\\n<li>Fix: Some widget style breaks when Improved CSS Loading Experiment is active in certain cases (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15632\\\">#15632<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15683\\\">#15683<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15660\\\">#15660<\\/a>)<\\/li>\\n<li>Fix: Translation update keep appearing as available after install (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/14297\\\">#14297<\\/a>)<\\/li>\\n<li>Fix: Wrong default icon color when using Font Awesome icons as inline SVG in Call to Action widget<\\/li>\\n<\\/ul>\\n<h4>3.3.2 - 2021-07-13<\\/h4>\\n<ul>\\n<li>Tweak: Updated plugin description<\\/li>\\n<li>Fix: MailChimp tags in form widget replaced existing tags (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11111\\\">#11111<\\/a>)<\\/li>\\n<li>Fix: Clicking videos from the items list in edit mode doesn\\u2019t initiate videos properly<\\/li>\\n<li>Fix: User unauthorized message when activated but not connected in Kit Library<\\/li>\\n<li>Fix: Carousel widgets did not support additional custom breakpoint responsive values<\\/li>\\n<li>Fix: Tab border is overridden by the Section background color in Video Playlist widget<\\/li>\\n<li>Fix: Widgets style breaks when Improved CSS Load experiment is active in a Single Page template and Post Content widget<\\/li>\\n<\\/ul>\\n<h4>3.3.1 - 2021-06-20<\\/h4>\\n<ul>\\n<li>Tweak: Added support for more Theme Builder display conditions in Export \\/ Import experiment<\\/li>\\n<li>Tweak: Adjusted License page heading structure for future feature<\\/li>\\n<li>Tweak: Adjusted Font Awesome icon for allowing support for future feature<\\/li>\\n<li>Fix: <code>frontend.min.js<\\/code> file size increased in Elementor Pro 3.3.0 (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/15278\\\">#15278<\\/a>)<\\/li>\\n<li>Fix: Prevent conditions from being reset when object cache is enabled in site (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13299\\\">#13299<\\/a>)<\\/li>\\n<li>Fix: Custom Code publish modal responsiveness issues (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/14519\\\">#14519<\\/a>)<\\/li>\\n<li>Fix: Populating fields with options programmatically doesn\'t appear in Submissions screen (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/10671\\\">#10671<\\/a>)<\\/li>\\n<li>Fix: Large images are not shown on the Image Carousel widget when set via Toolset dynamic tag<\\/li>\\n<li>Fix: Enable inline editing to the inner content tabs in Video Playlist widget<\\/li>\\n<li>Fix: Clicking on the video list doesn\'t play videos properly in Video Playlist widget<\\/li>\\n<li>Fix: Hide Play Icon control when Image overlay is toggled off in Video Playlist widget<\\/li>\\n<li>Fix: Removed extra space below the player when viewing from mobile view in Video Playlist widget<\\/li>\\n<li>Fix: Import button is not working properly in Theme Builder interface<\\/li>\\n<li>Fix: Preview Dynamic Content as control is not updating preview and throws an error in Popup Builder<\\/li>\\n<\\/ul>\\n<h4>3.3.0 - 2021-06-08<\\/h4>\\n<ul>\\n<li>New: Video Playlist widget - Add Engaging Video Content to Your Website (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11859\\\">#11859<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/7803\\\">#7803<\\/a>)<\\/li>\\n<li>New: Hotspot widget - Create Interactive Images With Contextually Relevant Information (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/7282\\\">#7282<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/2768\\\">#2768<\\/a>)<\\/li>\\n<li>Tweak: Accessibility improvements for sub-menus in Nav Menu widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13859\\\">#13859<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13810\\\">#13810<\\/a>)<\\/li>\\n<li>Tweak: MailChimp action after submit can now add new tags to existing subscribers in Forms widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11111\\\">#11111<\\/a>)<\\/li>\\n<li>Tweak: Added <code>elementor_pro\\/forms\\/record\\/actions_before<\\/code> to filter the record before it sent to Actions After Submit in Forms widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/14261\\\">#14261<\\/a>)<\\/li>\\n<li>Tweak: Yoast SEO breadcrumbs widget can be used in Elementor without the need of enabling them in Yoast setting<\\/li>\\n<li>Tweak: Added future support for widgets CSS conditional loading (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/10329\\\">#10329<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/14229\\\">#14229<\\/a>)<\\/li>\\n<li>Tweak: Added future support for Sticky JS library conditional loading<\\/li>\\n<li>Tweak: Added future support for Import \\/ Export experiment<\\/li>\\n<li>Tweak: Preparations and fixes for Import Export Experiment in Pro version<\\/li>\\n<li>Tweak: Added gradient button capabilities to Login widget buttons<\\/li>\\n<li>Tweak: Added gradient button capabilities to Slides widget button<\\/li>\\n<li>Tweak: Added gradient button capabilities to Price Table widget button<\\/li>\\n<li>Tweak: Added gradient button capabilities to Flip Box widget button<\\/li>\\n<li>Tweak: Added Code Highlight widget Developers Documentation<\\/li>\\n<li>Tweak: Adjusted Submissions page for future updates<\\/li>\\n<li>Tweak: Added <code>em<\\/code> and <code>%<\\/code> units for padding control in Carousel widgets<\\/li>\\n<li>Tweak: Shorten currency name to currency symbol in PayPal button widget<\\/li>\\n<li>Fix: Custom Fonts URLs should be replaced when replace URL is triggered (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/7376\\\">#7376<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/10382\\\">#10382<\\/a>)<\\/li>\\n<li>Fix: The currency symbol size changed in the Price Table widget if enabling sale (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13519\\\">#13519<\\/a>)<\\/li>\\n<li>Fix: Nav Menu widget is not loading Font Awesome submenu icons (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/9907\\\">#9907<\\/a>)<\\/li>\\n<li>Fix: Hamburger toggle is not working in Nav menu widget<\\/li>\\n<li>Fix: Activation bug for IDN domains<\\/li>\\n<li>Fix: Conditions modal responsive glitches in Custom Code<\\/li>\\n<li>Fix: Duplicated strings in Custom Code module<\\/li>\\n<li>Fix: Enable resize option for code input field in Custom Code<\\/li>\\n<li>Fix: &quot;Save &amp; Close &quot;button in Custom Code\'s Conditions modal was not visible on small screen sizes<\\/li>\\n<li>Fix: Removing a column from a section in the navigator resulted in an empty section<\\/li>\\n<li>Fix: Recommend option is cut If the layout is not &quot;Standard&quot; in the Facebook Button widget<\\/li>\\n<li>Fix: Video item does not play without adding an image in Media Carousel widget<\\/li>\\n<li>Fix: <code>search-plus<\\/code> icon missing from panel in Media Carousel widget<\\/li>\\n<li>Fix: UI hover state glitch in Media Carousel widget<\\/li>\\n<li>Fix: PHP notice was thrown when trying to import a kit without overrideConditions parameter in Kit Import flow<\\/li>\\n<li>Fix: Templates conditions not imported if there are no conflicts in Import Export Experiment<\\/li>\\n<li>Fix: Non english values are not encoded properly on Submissions export<\\/li>\\n<li>Fix: Theme Builder import is not working properly<\\/li>\\n<li>Fix: UI glitch when no global widgets were found in Editor Panel<\\/li>\\n<li>Deprecated: See all deprecations to this version in our <a href=\\\"https:\\/\\/developers.elementor.com\\/v3-3-planned-deprecations\\/\\\">Developers Deprecations Post<\\/a><\\/li>\\n<\\/ul>\\n<h4>3.2.2 - 2021-05-05<\\/h4>\\n<ul>\\n<li>Tweak: Added support for Expert tier templates in Templates Library<\\/li>\\n<li>Tweak: Updated compatibility tag to support Elementor v3.2.x<\\/li>\\n<li>Tweak: Added compatibility for future Library improvements<\\/li>\\n<li>Fix: Toolset image dynamic field is not working with Gallery widget<\\/li>\\n<\\/ul>\\n<h4>3.2.1 - 2021-03-21<\\/h4>\\n<ul>\\n<li>Tweak: Added strings context in PayPal button and Price Table widgets<\\/li>\\n<li>Tweak: Added support for future Import \\/ Export Kit feature<\\/li>\\n<li>Fix: Submissions with over than 191 characters weren\'t indexed properly<\\/li>\\n<\\/ul>\\n<h4>3.2.0 - 2021-03-16<\\/h4>\\n<ul>\\n<li>New: PayPal Button widget - Collect PayPal payments directly from your site<\\/li>\\n<li>Experiment: Submissions - Save all of your form submissions in one place (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/1686\\\">#1686<\\/a>)<\\/li>\\n<li>Tweak: Added Stay In Column option to Inner Section element (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/7956\\\">#7956<\\/a>)<\\/li>\\n<li>Tweak: Adjusted \'Max Height\' control range in Table of Contents widget<\\/li>\\n<li>Tweak: Changed descriptive text in Create Custom Code screen<\\/li>\\n<li>Tweak: Added support for dynamic capabilities in Code Highlight widget<\\/li>\\n<li>Tweak: Added support for future load on demand for <code>share-link<\\/code> library<\\/li>\\n<li>Tweak: Added support for future load on demand for <code>dialog<\\/code> library in Popup<\\/li>\\n<li>Tweak: Allow overwriting the assets URL when using a mirror domain<\\/li>\\n<li>Fix: Animation was triggered multiple times when accessing the viewport in certain cases in Animated Headline widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13951\\\">#13951<\\/a>)<\\/li>\\n<li>Fix: Location is not being updated after a Custom Code snippet is published (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13971\\\">#13971<\\/a>)<\\/li>\\n<li>Fix: Custom Fonts CSS files were not updated after regenerating CSS files<\\/li>\\n<li>Fix: Conditions modal is not responsive in Custom Code<\\/li>\\n<li>Fix: Empty order buttons are displayed in Custom Fonts screen<\\/li>\\n<li>Fix: Typo in \'Reply To\' Email action after submit placeholder in Forms widget<\\/li>\\n<li>Fix: Unnecessary Save Draft button in Custom Code<\\/li>\\n<li>Fix: RTL glitches in Custom Code<\\/li>\\n<li>Fix: Sanitized options in the editor to enforce better security policies<\\/li>\\n<li>Deprecated: See all deprecations to this version in our (<a href=\\\"https:\\/\\/developers.elementor.com\\/v3-2-planned-deprecations\\/\\\">Developers Deprecations Post<\\/a>)<\\/li>\\n<\\/ul>\\n<h4>3.1.1 - 2021-02-23<\\/h4>\\n<ul>\\n<li>Tweak: Adjusted \'Max Height\' control range in Table of Contents widget<\\/li>\\n<li>Fix: Popup event handler is undefined (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11475\\\">#11475<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/10690\\\">#10690<\\/a>)<\\/li>\\n<li>Fix: Conditions modal is not responsive in Custom Code<\\/li>\\n<li>Fix: RTL glitches in Code Highlight widget<\\/li>\\n<li>Fix: Minor UI glitches in Code Highlight widget<\\/li>\\n<li>Fix: Users can\'t get Pro Developer Edition version updates<\\/li>\\n<\\/ul>\\n<h4>3.1.0 - 2021-02-16<\\/h4>\\n<ul>\\n<li>New: Introducing Custom Code - Add custom code snippets to your site, including <code>head<\\/code>, <code>body<\\/code> start and <code>body<\\/code> end<\\/li>\\n<li>New: Meet Code Highlight widget - showcase any syntax with highlighted UI (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/5815\\\">#5815<\\/a>)<\\/li>\\n<li>Experiment: Improved Pro widgets performance by loading JS and Swiper assets conditionally in frontend (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/8572\\\">#8572<\\/a>, <a href=\\\"https:\\/\\/developers.elementor.com\\/experiment-optimized-asset-loading\\/\\\">Developer Documentation<\\/a>)<\\/li>\\n<li>Tweak: Added Compatibility Tag support in Elementor Pro (<a href=\\\"https:\\/\\/developers.elementor.com\\/compatibility-tag\\/\\\">Developer Documentation<\\/a>)<\\/li>\\n<li>Tweak: Added Dynamic capabilities to Rotating Text animation in Animated Headline widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/4625\\\">#4625<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/8569\\\">#8569<\\/a>)<\\/li>\\n<li>Tweak: Added an option to set Selected color for Typing effect in Animated Headline widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/5403\\\">#5403<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/7826\\\">#7826<\\/a>)<\\/li>\\n<li>Tweak: Added animation Loop option for Animated Headline (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/9749\\\">#9749<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/2457\\\">#2457<\\/a>)<\\/li>\\n<li>Tweak: Added timing options for Animated Headline widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/4392\\\">#4392<\\/a>)<\\/li>\\n<li>Tweak: Added dynamic capabilities for Testimonial Carousel widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/8569\\\">#8569<\\/a>)<\\/li>\\n<li>Tweak: Added dynamic capabilities for Price Table widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/4242\\\">#4242<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/8569\\\">#8569<\\/a>)<\\/li>\\n<li>Tweak: Added Word Wrap control to Code Highlight widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13577\\\">#13577<\\/a>)<\\/li>\\n<li>Tweak: Upgraded Font Awesome Pro library to v5.15.1<\\/li>\\n<li>Tweak: Improved method of loading field mapping repeater in Form widget (<a href=\\\"https:\\/\\/developers.elementor.com\\/how-to-add-a-repeater-control-to-elementor-add-on\\/\\\">Developer Documentation<\\/a>)<\\/li>\\n<li>Tweak: Added &quot;Show on Browsers&quot; Popup Advanced Rule<\\/li>\\n<li>Tweak: Added real-time JS handling to prevent redundant renders in Slides widget and all Carousel widgets<\\/li>\\n<li>Tweak: Import scroll utility from core and remove it from Pro<\\/li>\\n<li>Tweak: Added alignment options for Post Excerpt widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/9757\\\">#9757<\\/a>)<\\/li>\\n<li>Tweak: Changed alignment control to work with selectors in Share Buttons<\\/li>\\n<li>Tweak: Upgraded to Webpack 5, Grunt-Webpack 4 and TerserPlugin instead of UglifyJsPlugin<\\/li>\\n<li>Fix: Steps Divider is not vertically aligned in Multi Step Form widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12569\\\">#12569<\\/a>)<\\/li>\\n<li>Fix: Slides are playing in an infinite loop mode even when the option is disabled in Slides Widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/6726\\\">#6726<\\/a>)<\\/li>\\n<li>Fix: Redundant spacing is added to Share Buttons widget<\\/li>\\n<li>Fix: Step buttons text is not updated without a page reload in Forms widget<\\/li>\\n<li>Fix: Overflow issue in certain animations in Animated Headline widget<\\/li>\\n<li>Fix: When dragging a new Testimonial Carousel there is a console error thrown<\\/li>\\n<li>Fix: Step Buttons are cut in mobile view in Multi Step Form<\\/li>\\n<li>Fix: Submit and Step buttons size differences when using Twenty Twenty theme<\\/li>\\n<li>Fix: Duplicate button Text Color control in Slides widget<\\/li>\\n<li>Fix: JS error is thrown when editing and saving global widgets<\\/li>\\n<li>Fix: <code>get_version<\\/code> API function may fail with Redis \\/ DB cache<\\/li>\\n<li>Fix: Multiple license check requests are created in certain cases<\\/li>\\n<li>Deprecated: Deprecate methods prefixed with an underscore and replace them with unprefixed methods<\\/li>\\n<li>Deprecated: See all deprecations to this version in our <a href=\\\"https:\\/\\/developers.elementor.com\\/v3-1-planned-deprecations\\/\\\">Developers Deprecations Post<\\/a><\\/li>\\n<\\/ul>\\n<h4>3.0.10 - 2021-01-20<\\/h4>\\n<ul>\\n<li>Tweak: Added Editing Handles string translation compatibility with Elementor Pro v3.1<\\/li>\\n<\\/ul>\\n<h4>3.0.9 - 2020-12-29<\\/h4>\\n<ul>\\n<li>Tweak: Added compatibility to support Elementor 3.1.0<\\/li>\\n<li>Fix: Wrong phrasing of Import template success message in Theme Builder<\\/li>\\n<li>Fix: Border color glitch in Theme Builder<\\/li>\\n<\\/ul>\\n<h4>3.0.8 - 2020-11-26<\\/h4>\\n<ul>\\n<li>Fix: Navigation arrows UI glitch in Media Carousel widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/13172\\\">#13172<\\/a>)<\\/li>\\n<\\/ul>\\n<h4>3.0.7 - 2020-11-25<\\/h4>\\n<ul>\\n<li>Fix: Console Error when dragging Testimonials Carousel widget<\\/li>\\n<li>Fix: Arrows of Testimonial and Reviews Carousel widgets navigate to the wrong direction in RTL websites<\\/li>\\n<li>Fix: Removed the conditional loading of Webpack<\\/li>\\n<li>Fix: Fatal error is thrown after deleting an associated custom taxonomy when Posts widget with Cards skin has a badge<\\/li>\\n<li>Fix: Upload JSON files only when the user allowed to prevent security issues<\\/li>\\n<li>Fix: Gallery not displayed in Theme Builder templates preview<\\/li>\\n<\\/ul>\\n<h4>3.0.6 - 2020-11-04<\\/h4>\\n<ul>\\n<li>Tweak: Updated the embedded post in Facebook Embed widget<\\/li>\\n<li>Fix: Minor UI glitches in Theme Builder\'s conditions screen footer<\\/li>\\n<li>Fix: Template type changes into Single Page after conditions change in Theme Builder<\\/li>\\n<li>Fix: Redundant Custom Caption option in Site Logo widget<\\/li>\\n<li>Fix: Removed unused code in Drip integration<\\/li>\\n<li>Fix: Removed Weibo and WeChat social networks due to website and links inactivity from Share Buttons widget<\\/li>\\n<li>Fix: Removed redundant code from Portfolio and Post Navigation widgets<\\/li>\\n<\\/ul>\\n<h4>3.0.5 - 2020-09-23<\\/h4>\\n<ul>\\n<li>Fix: If the default page layout is set to &quot;Canvas&quot; Headers and Footers cannot be edited<\\/li>\\n<li>Fix: Product Image Dynamic Tag throws an error when no image is set<\\/li>\\n<li>Fix: Missing Single document placeholder in Theme Builder<\\/li>\\n<li>Fix: Document editing handles inherit the <code>font-family<\\/code> from 3rd party source<\\/li>\\n<li>Fix: Can\'t add linebreaks to Textarea input when used as Multi Step Form<\\/li>\\n<li>Fix: Incorrect width in Facebook Page widget<\\/li>\\n<li>Fix: Added compatibility to allow the use of \'get_create_url\' in Theme Builder<\\/li>\\n<\\/ul>\\n<h4>3.0.4 - 2020-09-09<\\/h4>\\n<ul>\\n<li>Fix: Autogenerated screenshots appear in WP Media Library modal (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12304\\\">#12304<\\/a>)<\\/li>\\n<li>Fix: Make sure Elementor Posts widget Pagination doesn\'t interfere with 3rd party plugins (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12126\\\">#12126<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12127\\\">#12127<\\/a>)<\\/li>\\n<li>Fix: Shrinking conditions indicator in Theme Builder<\\/li>\\n<li>Fix: Column can\'t be dragged and dropped if it populates a Global widget<\\/li>\\n<li>Fix: Styles are missing from Single templates in some edge cases<\\/li>\\n<\\/ul>\\n<h4>3.0.3 - 2020-09-02<\\/h4>\\n<ul>\\n<li>Fix: Pagination doesn\'t work in WordPress 5.5 (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12126\\\">#12126<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12127\\\">#12127<\\/a>)<\\/li>\\n<li>Fix: Change delete template action to &quot;Move to Trash&quot; in the new Theme Builder view<\\/li>\\n<\\/ul>\\n<h4>3.0.2 - 2020-08-31<\\/h4>\\n<ul>\\n<li>Tweak: Replaced WordPress &quot;Learn More&quot; links with dynamic links for better control over time (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12312\\\">#12312<\\/a>)<\\/li>\\n<li>Tweak: UI tweaks to the Conditions screen In the new Theme Builder<\\/li>\\n<li>Fix: Motion Effects not working when assigned to a column and throws JS error when DOM optimization is disabled (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12299\\\">#12299<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12275\\\">#12275<\\/a>)<\\/li>\\n<li>Fix: Multiple Galleries display all the images in the Lightbox slideshow (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11809\\\">#11809<\\/a>)<\\/li>\\n<li>Fix: Old Theme Builder is being opened when accessing through the Finder<\\/li>\\n<li>Fix: Mixed templates import glitch in Theme Builder<\\/li>\\n<li>Fix: Card icon sizes in Theme Builder<\\/li>\\n<li>Fix: Preview button leads to <code>render_mode<\\/code> instead of preview when importing a template from the new Theme Builder<\\/li>\\n<\\/ul>\\n<h4>3.0.1 - 2020-08-26<\\/h4>\\n<ul>\\n<li>Tweak: Keep previous Theme Builder when accessing from the WP Dashboard for legacy support<\\/li>\\n<li>Tweak: Updated video tutorials in Theme Builder<\\/li>\\n<li>Tweak: Don\'t show auto-screenshots in the Media Library (Props <a href=\\\"https:\\/\\/github.com\\/black-eye\\\">@black-eye<\\/a>)<\\/li>\\n<li>Fix: Repeater items throws <code>childView<\\/code> is undefined message in Forms widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12239\\\">#12239<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12221\\\">#12221<\\/a>)<\\/li>\\n<li>Fix: Misspelling of the word &quot;occurred&quot; in Form widget default error message (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12137\\\">#12137<\\/a>)<\\/li>\\n<li>Fix: Facebook comments not showing up (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/12157\\\">#12157<\\/a>)<\\/li>\\n<li>Fix: Check for conflicts in Theme Builder doesn\'t work properly<\\/li>\\n<li>Fix: Minor UI fixes in Theme Builder<\\/li>\\n<li>Fix: Dark mode glitches in Theme Builder<\\/li>\\n<li>Fix: Global Site Part toaster appears when you publish a Popup<\\/li>\\n<li>Fix: Site Parts aren\'t in the correct order in Theme Builder<\\/li>\\n<li>Fix: Date field caused forms to get corrupted in Forms widget<\\/li>\\n<li>Fix: Theme Builder application page is forbidden<\\/li>\\n<\\/ul>\\n<h4>3.0.0 - 2020-08-23<\\/h4>\\n<ul>\\n<li>New: Introducing the new and improved Theme Builder<\\/li>\\n<li>Tweak: Removed <code>.elementor-inner<\\/code> and <code>.elementor-column-wrap<\\/code> from DOM output to improve performance (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/7351\\\">#7351<\\/a>, <a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/7817\\\">#7817<\\/a>, <a href=\\\"https:\\/\\/developers.elementor.com\\/dom-improvements-ahead-html-wrappers-removal-from-v3-0\\/\\\">Developers Blog Post<\\/a>)<\\/li>\\n<li>Tweak: Added contextual anchors ID support to Table of Contents widgets (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/10052\\\">#10052<\\/a>)<\\/li>\\n<li>Tweak: Added WeChat and Weibo social networks to Share Buttons widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11554\\\">#11554<\\/a>)<\\/li>\\n<li>Tweak: Added Dynamic capabilities for Redirect after Login\\/Logout in Login widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11343\\\">#11343<\\/a>)<\\/li>\\n<li>Tweak: Added Blend Mode and CSS Filters controls to adjust the Background Overlay in Flipbox widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11653\\\">#11653<\\/a>)<\\/li>\\n<li>Tweak: Added responsive capabilities to Toggle Button styling in Nav Menu widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/8269\\\">#8269<\\/a>)<\\/li>\\n<li>Tweak: Added responsive Text Alignment control in Call to Action widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11968\\\">#11968<\\/a>)<\\/li>\\n<li>Tweak: Added dynamic content to Ribbon element in Call to Action widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/10364\\\">#10364<\\/a>)<\\/li>\\n<li>Tweak: Converted uses of Color and Typography Schemes to Global Colors and Fonts<\\/li>\\n<li>Tweak: Separated Title and Description control fields labels in Call to Action widget<\\/li>\\n<li>Tweak: Removed unnecessary style in WC Product with variations<\\/li>\\n<li>Tweak: Converted Portfolio, Posts and Share Buttons widgets to use CSS Variable-based Elementor Grid (<a href=\\\"https:\\/\\/developers.elementor.com\\/elementor-dropping-support-ie\\/\\\">Developers Blog Post<\\/a>)<\\/li>\\n<li>Tweak: Added Date Modified option to Posts widget metadata<\\/li>\\n<li>Fix: PHP 7.4 compatibility to Media Carousel widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11355\\\">#11355<\\/a>)<\\/li>\\n<li>Fix: Divider alignment issue in Post Info widget (<a href=\\\"https:\\/\\/github.com\\/elementor\\/elementor\\/issues\\/11628\\\">#11628<\\/a>)<\\/li>\\n<li>Fix: Color doesn\\u2019t change in Products Archive Description widget<\\/li>\\n<li>Fix: WC Product variations layout breaks when using Variation Swatches plugin<\\/li>\\n<li>Fix: WC Product variations layout issue<\\/li>\\n<li>Fix: WC Product variations mobile zoom-in glitch<\\/li>\\n<li>Fix: Can\'t edit a Popup after accessing Theme Style<\\/li>\\n<li>Fix: Twitter icon missing in Blockquote widget<\\/li>\\n<li>Fix: Removed redundant default text color from Share Buttons minimal skin<\\/li>\\n<li>Fix: UI glitch in Display Conditions modal<\\/li>\\n<li>Fix: Insert template button UI glitch in Templates Library<\\/li>\\n<li>Fix: Added sanitization to post titles in WordPress dashboard for better security<\\/li>\\n<li>Fix: Show when arriving from search engines rule doesn\'t work in Popup<\\/li>\\n<li>Fix: Child categories are shown with a different parent category in Query control<\\/li>\\n<li>Deprecated: See all deprecations to this version in our <a href=\\\"https:\\/\\/developers.elementor.com\\/v3-0-planned-deprecations\\/\\\">Developers Deprecations Post<\\/a><\\/li>\\n<\\/ul>\\\";}\",\"new_version\":\"3.4.2\",\"name\":\"Elementor Pro\",\"slug\":\"elementor-pro\",\"url\":\"https:\\/\\/elementor.com\\/pro\\/changelog\\/\",\"homepage\":\"https:\\/\\/elementor.com\\/pro\\/\",\"requires\":\"5.0\",\"tested\":\"5.8.1\",\"elementor_requires\":\"3.0.1\",\"package\":\"https:\\/\\/my.elementor.com\\/edd-sl\\/package_download\\/MTYzNTAxMDgxMzoxMjY1MWE3ZWYxNzY3NDBhZGQ0YzZjMjlkMDY3OTE5NToxOmVkZjA1NTk2ZjcyMWYzOTNiNDUyMjNiZThkMzY2ZjUxOmh0dHBzQC8vdmFjLWJzYW5ldy5vcmc6MA==\",\"download_link\":\"https:\\/\\/my.elementor.com\\/edd-sl\\/package_download\\/MTYzNTAxMDgxMzoxMjY1MWE3ZWYxNzY3NDBhZGQ0YzZjMjlkMDY3OTE5NToxOmVkZjA1NTk2ZjcyMWYzOTNiNDUyMjNiZThkMzY2ZjUxOmh0dHBzQC8vdmFjLWJzYW5ldy5vcmc6MA==\",\"banners\":{\"2x\":\"https:\\/\\/ps.w.org\\/elementor\\/assets\\/banner-1544x500.png?rev=1475479\",\"1x\":\"https:\\/\\/ps.w.org\\/elementor\\/assets\\/banner-772x250.png?rev=1475479\"},\"icons\":{\"svg\":\"https:\\/\\/ps.w.org\\/elementor\\/assets\\/icon.svg\"},\"canary_deployment\":{\"plugin_info\":{\"new_version\":\"3.4.0\",\"name\":\"Elementor Pro\",\"slug\":\"elementor-pro\",\"url\":\"https:\\/\\/elementor.com\\/pro\\/changelog\\/\",\"homepage\":\"https:\\/\\/elementor.com\\/pro\\/\",\"requires\":\"5.0\",\"tested\":\"5.8.1\",\"elementor_requires\":\"3.0.1\",\"package\":\"https:\\/\\/my.elementor.com\\/edd-sl\\/previous_download\\/MTYzNTAxMDgxMzoxMjY1MWE3ZWYxNzY3NDBhZGQ0YzZjMjlkMDY3OTE5NToxOjMuNC4wOjgyM2Q4NDJlNTIwMThlNmI0NjAwY2ZlYTRkYzEyZDE1Omh0dHBzQC8vdmFjLWJzYW5ldy5vcmc=\",\"download_link\":\"https:\\/\\/my.elementor.com\\/edd-sl\\/previous_download\\/MTYzNTAxMDgxMzoxMjY1MWE3ZWYxNzY3NDBhZGQ0YzZjMjlkMDY3OTE5NToxOjMuNC4wOjgyM2Q4NDJlNTIwMThlNmI0NjAwY2ZlYTRkYzEyZDE1Omh0dHBzQC8vdmFjLWJzYW5ldy5vcmc=\",\"banners\":{\"2x\":\"https:\\/\\/ps.w.org\\/elementor\\/assets\\/banner-1544x500.png?rev=1475479\",\"1x\":\"https:\\/\\/ps.w.org\\/elementor\\/assets\\/banner-772x250.png?rev=1475479\"},\"icons\":{\"svg\":\"https:\\/\\/ps.w.org\\/elementor\\/assets\\/icon.svg\"}},\"conditions\":[[{\"type\":\"language\",\"languages\":[\"he_IL\",\"nl_NL\",\"en_GB\",\"en_NZ\",\"en_ZA\",\"en_AU\",\"en_CA\",\"sv_SE\",\"da_DK\",\"fr_FR\",\"nl_NL\",\"nb_NO\",\"de_AT\",\"fi\",\"it_IT\",\"nn_NO\",\"de_CH\",\"en_GB\",\"is_IS\",\"ga\",\"fr_BE\",\"nl_BE\",\"ast\",\"lb_LU\",\"es_ES\",\"pt_PT\",\"mlt\"],\"operator\":\"in\"}]]}}\";}','yes'),(1035909,'boldgrid_backup_environment','a:3:{s:8:\"hostname\";s:24:\"ehub56.webhostinghub.com\";s:10:\"phpversion\";s:6:\"7.3.30\";s:9:\"wpversion\";s:5:\"5.6.5\";}','yes'),(1088261,'_transient_timeout_boldgrid_backup_system_zip_test','1634987387','no'),(1088262,'_transient_boldgrid_backup_system_zip_test','1','no'),(1088263,'_transient_timeout_boldgrid_backup_is_functional','1634987387','no'),(1088264,'_transient_boldgrid_backup_is_functional','1','no'),(1073652,'_site_transient_timeout_php_check_b18180942574278ff67528037bdd7ba9','1634925961','no'),(1073653,'_site_transient_php_check_b18180942574278ff67528037bdd7ba9','a:5:{s:19:\"recommended_version\";s:3:\"7.4\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:0;s:9:\"is_secure\";b:1;s:13:\"is_acceptable\";b:1;}','no'),(1088665,'_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1634960933','no'),(1088666,'_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1634917733','no'),(1088667,'_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9','1634960934','no'),(1088668,'_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9','a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:61:\"\n	\n	\n	\n	\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"WordPress Planet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://planet.wordpress.org/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:2:\"en\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WordPress Planet - http://planet.wordpress.org/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:50:{i:0;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"Post Status: Post Status Excerpt (No. 29) — Better Ways To Support Customers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=88157\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/29/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4339:\"<h2>&#8220;If you\'re a founder of a company go through your own custom experience yourself — with your own eyes.&#8221;</h2>\n\n\n\n<p class=\"has-drop-cap\">In this episode of Post Status Excerpt, Cory and David talk about their best and worst support experiences as customers. If you are a freelancer or small agency and your ability to deal with support issues from customers isn\'t working, then that\'s a sign of something broken in your workflow. Companies should try to be more proactive and helpful to customers even if they can\'t help them immediately or solve all their problems.</p>\n\n\n\n<p><strong>Also don\'t forget: </strong>We\'re encouraging listeners to check out the &#8220;<a href=\"https://poststatus.com/make-wordpress/\">Week at WordPress.org</a>&#8221; — get the feed <a href=\"https://poststatus.com/make-wordpress/feed/\">here</a>) — and <a href=\"https://poststatus.com/submit-2021-black-friday-cyber-monday-deals/\">submit your Black Friday / Cyber Monday deals</a> to us at Post Status.</p>\n\n\n\n\n\n\n\n<p class=\"has-background\">Every week <strong><a href=\"https://poststatus.com/podcast/the-excerpt/\">Post Status Excerpt</a></strong> will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash. <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a1.png\" alt=\"⚡\" class=\"wp-smiley\" /><br /><br />You can listen to <a href=\"https://poststatus.com/podcast/the-excerpt/\">past episodes</a> of <strong>The Excerpt</strong>, <a href=\"https://poststatus.com/category/post-status-podcasts/\">browse all our podcasts</a>, and don’t forget to subscribe on <a href=\"https://open.spotify.com/show/1m3xwXbe0MG5BzFVPtB0A7\">Spotify</a>, Amazon Music, <a href=\"https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zaW1wbGVjYXN0LmNvbS8ySkU5c2M4UA\">Google Podcasts</a>, <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">iTunes</a>, <a href=\"https://castro.fm/podcast/c53552c6-1ee0-4fc4-9de4-08ed6bf1ee4d\">Castro</a>, <a href=\"https://www.youtube.com/c/PostStatus\">YouTube</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, <a href=\"https://player.fm/series/wordpress-post-status-podcasts\">Player.fm</a>, <a href=\"https://pca.st/05rR\">Pocket Casts</a>, <a href=\"https://wordpress-post-status-draft-podcast.simplecast.com/\">Simplecast</a>, or by <a href=\"https://feeds.simplecast.com/2JE9sc8P\">RSS</a>. <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f3a7.png\" alt=\"🎧\" class=\"wp-smiley\" /></p>\n\n\n\n<h3 id=\"h-mentioned-in-the-show\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f517.png\" alt=\"🔗\" class=\"wp-smiley\" /> Mentioned in the show:</h3>\n\n\n\n<ul><li><a href=\"https://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html\">SuperDuper!</a></li><li><a target=\"_blank\" rel=\"noreferrer noopener\" href=\"https://jenniferbourn.com/profitable-project-plan/\">Profitable Project Plan | Business Training For Web Designers</a></li><li><a href=\"https://www.amazon.com/Myth-Revisited-Small-Businesses-About-ebook/dp/B000RO9VJK/ref[%E2%80%A6]8350250%2CB00HTJR0NU%2CB00OH76SJE%2C0060938404&srpt=ABIS_BOOK\">The E-Myth Revisited: Why Most Small Businesses Don\'t Work and What to Do About It</a></li><li><a href=\"https://poststatus.com/submit-2021-black-friday-cyber-monday-deals/\">Share Black Friday / Cyber Monday Deals With Post Status</a></li><li><a href=\"https://twitter.com/dimensionmedia\" target=\"_blank\" rel=\"noreferrer noopener\">David Bisset (Twitter)</a></li><li><a href=\"https://twitter.com/corymiller303\" target=\"_blank\" rel=\"noreferrer noopener\">Cory Miller (Twitter)</a></li><li><a href=\"https://twitter.com/post_status\" target=\"_blank\" rel=\"noreferrer noopener\">Post Status (Twitter)</a></li></ul>\n\n\n\n<h3><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f64f.png\" alt=\"🙏\" class=\"wp-smiley\" /> Sponsor: <a href=\"https://poststat.us/ithemes\" target=\"_blank\" rel=\"noreferrer noopener sponsored nofollow\">Yoast SEO</a></h3>\n\n\n\n<p><strong>Yoast</strong> is SEO for everyone. Yoast SEO Premium gives you 24/7 support and extra features like internal linking, social previews, a redirect manager, tutorial videos, and integration with Google Webmaster Tools. Get on board today with the premiere SEO plugin for WordPress — <strong>Yoast</strong>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 Oct 2021 03:41:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"WPTavern: Branded Social Images, a New Plugin for Generating Per-Post Open Graph Images\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=124633\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:217:\"https://wptavern.com/branded-social-images-a-new-plugin-for-generating-per-post-open-graph-images?utm_source=rss&utm_medium=rss&utm_campaign=branded-social-images-a-new-plugin-for-generating-per-post-open-graph-images\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5138:\"<p class=\"has-drop-cap\">Generated social images seem to be all the rage now. <a href=\"https://wptavern.com/automattic-acquires-social-image-generator-plugin-plans-to-integrate-with-jetpack\">Automattic scooped up</a> Daniel Post&rsquo;s Social Image Generator last month for eventual inclusion in Jetpack. There is a <a href=\"https://wptavern.com/dynamic-social-images-for-plugins-themes-and-patterns-yes-please\">proposal to dynamically generate them</a> for plugins and themes hosted on WordPress.org. And, there is a new player in town: <a href=\"https://wordpress.org/plugins/branded-social-images/\">Branded Social Images</a>.</p>\n\n\n\n<p>Admittedly, I have had a mild obsession lately with the concept, and I would like to see the Tavern use dynamically-generated social images at some point. Because we already use Jetpack, I will wait to see where its development team takes the feature.</p>\n\n\n\n<p>Branded Social Images is a solid addition to the WordPress plugin directory for those who want a solution now. It is not as featured-filled as Social Image Generator, which is no longer available for purchase. However, it is an introduction to the concept for those trying it out for the first time. And, it may just prove well-rounded enough for many users.</p>\n\n\n\n<p>The plugin was <a href=\"https://www.clearsite.nl/branded-social-images/\">released by Internetbureau Clearsite</a>, a web development and design agency. Branded Social Images is the team&rsquo;s first extension on WordPress.org.</p>\n\n\n\n<p>My favorite feature from this plugin is that it allows users to upload any TTF or OTF font file for the social image&rsquo;s text. I tested it with the Oleo Script Swash Caps and Rampart One font families to see how it worked.</p>\n\n\n\n<ul><li class=\"blocks-gallery-item\"><img /></li><li class=\"blocks-gallery-item\"><img /></li></ul>Testing custom font families.\n\n\n\n<p>Well, I tested with several more than that, but I had to stop myself before going too far. I have a font addiction and am easily sucked into hours of tinkering with them. The goal was to test this plugin feature, and it worked as it was supposed to.</p>\n\n\n\n<p>The plugin already packages a reasonable set of 10 font families to choose from out of the box. If nothing suits your fancy, just snag one from Google Fonts or another site of your choosing and upload the <code>.ttf</code> or <code>.otf</code> file.</p>\n\n\n\n<p>Branded Social Images is straightforward to use. Its settings screen has a preview image at the top and two boxes with settings. One for the social image text. The other is for the background image and logo.</p>\n\n\n\n<p>Where it fails to live up to the competition is that it does not have any pre-built templates. This is not necessarily a make-or-break feature, but it also does not have the design options to recreate many of the layouts of something like Social Image Generator.</p>\n\n\n\n<p>Essentially, the layout options boil down to positioning a logo and text atop a background image via a three-by-three grid.</p>\n\n\n\n<ul><li class=\"blocks-gallery-item\"><img /></li><li class=\"blocks-gallery-item\"><img /></li></ul>Plugin options.\n\n\n\n<p>However, its scaled-back interface with minimal options could be seen as a feature in and of itself. Not everyone needs or desires a swath of settings when a few baseline customizations will do.</p>\n\n\n\n<p>I did have some trouble understanding whether the placeholder logo could be removed. After some testing, I realized it was limited to the settings screen unless I explicitly uploaded a custom one. I would also like to see an option to use the site title instead &mdash; not every site has a logo but might still want to show their brand name.</p>\n\n\n\n<p>Users can also modify the social image on a per-post basis. The plugin adds a meta box with four options on the post-editing screen for:</p>\n\n\n\n<ul><li>Disabling the social image.</li><li>Editing the text.</li><li>Disabling the text.</li><li>Adding a custom image.</li></ul>\n\n\n\n<img />Per-post social image options.\n\n\n\n<p>By default, the text will be the post&rsquo;s document title. It should work with most SEO plugins, such as Yoast SEO. The featured image will also be swapped in for the background if a custom one is not added.</p>\n\n\n\n<p>After three years of using the current WordPress post editor, it still catches me off-guard when a plugin puts a meta box at the bottom of the screen instead of the sidebar. It always looks out of place. In this case, it takes up a ton of real estate for four options, and there is no need for it. If I could wave a magic wand and change one thing about the plugin, this would be it.</p>\n\n\n\n<p>The plugin also breaks the cardinal rule of not adding a top-level admin menu item for a single screen. WordPress literally allows for sub-menu items under Settings. <em>So, maybe I need that magic wand for two things.</em></p>\n\n\n\n<p>Outside of a few issues, I love what the plugin team has created thus far. It is a little rough around the edges, but that is OK for a version 1.x. Software is meant to be iterated and improved upon, and Branded Social Images has the foundation for becoming even better.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 Oct 2021 00:35:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"WPTavern: Jetpack Launches Commercial Backup Feature as a Standalone Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=124622\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:195:\"https://wptavern.com/jetpack-launches-commercial-backup-feature-as-a-standalone-plugin?utm_source=rss&utm_medium=rss&utm_campaign=jetpack-launches-commercial-backup-feature-as-a-standalone-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3577:\"<p>Jetpack is splitting out its <a href=\"https://cloud.jetpack.com/pricing\">commercial Backup feature</a> into a standalone plugin that can be used without installing the core Jetpack plugin. </p>\n\n\n\n<p>The commercial product includes automated daily or real-time backups with one-click restores, even for sites that are offline. Backups include all WordPress database, theme, and plugin files, which are stored on WordPress.com&rsquo;s infrastructure with redundant copies on multiple servers. The product was built with WooCommerce in mind and can restore a site to any past state while keeping current orders and products in place. </p>\n\n\n\n<p>Jetpack representative Rob Pugh <a href=\"https://jetpack.com/2021/10/21/meet-jetpack-backup-now-as-a-standalone-plugin/\">said</a> the product was split out of the core plugin because &ldquo;many developers and site owners asked for the flexibility to use specific components of Jetpack as part of their own, custom-built &lsquo;tech stack&rsquo; of plugins.&rdquo;</p>\n\n\n\n<p>The standalone plugin is available on WordPress.org and requires a user connection to WordPress.com. It is essentially a shell for connecting the commercial product, as the plugin doesn&rsquo;t have a free tier or perform any function unless you click &ldquo;Upgrade Now.&rdquo; </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The plugin&rsquo;s description on WordPress.org is somewhat misleading, as it isn&rsquo;t explicit that this is a commercial-only product. The &ldquo;Get Started&rdquo; section states, &ldquo;Installation is free, quick, and easy. It only takes a few minutes to install Jetpack Backup.&rdquo; The fact that it&rsquo;s a paid product isn&rsquo;t evident unless you dig into the accordion FAQ section about how to create a backup: &ldquo;As soon as you purchase Jetpack Backup, it will be activated, and the first backup will be completed.&rdquo; </p>\n\n\n\n<p>The launch of the new standalone plugin should not affect current Jetpack customers using the backup services.</p>\n\n\n\n<p>&ldquo;It&rsquo;s the same engine that powers the backup solution that&rsquo;s part of the full Jetpack plugin and we&rsquo;ve developed loaders to only load the engine once&mdash;whether you have only Jetpack, only this, or both,&rdquo; Jetpack engineer Brandon Kraft <a href=\"https://twitter.com/Kraft/status/1428101956879454210\">said</a>. &ldquo;If you have Jetpack already, this adds some UI for you, but the same service.</p>\n\n\n\n<p>&ldquo;The loader tech is the same that ensures the connection code only loads once between this, Jetpack, Boost, WooCommerce Payments, etc and ensure the latest version is running. [You] don&rsquo;t have to load into memory more than you need.&rdquo;</p>\n\n\n\n<p>Jetpack is often criticized for being &ldquo;bloated&rdquo; and bundling too many features. In 2019, the Jetpack team began <a href=\"https://wptavern.com/jetpack-is-promoting-paid-upgrades-on-plugin-search-screen-wordpress-plugin-team-says-it-may-be-a-violation-of-directory-guidelines\">promoting feature suggestions on the plugin search screen</a> in an attempt to solve a discovery problem, where users are quite often not familiar with the plugin&rsquo;s dozens of modules and end up installing plugins to perform functionality that Jetpack already includes. Splitting the backup feature out into its own plugin should be helpful on this front and is part of a long-term plan to make Jetpack more modular. Jetpack Backup joins Jetpack CRM and Jetpack Boost, two features already available as standalone plugins outside of the core plugin.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Oct 2021 22:56:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"Post Status: Post Status Live: Membership and Courses with Sean McCabe\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=88020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://poststatus.com/post-status-live-membership-and-courses-with-sean-mccabe/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3578:\"<h2>&#8220;It\'s easier to sell courses today&#8230; what hasn\'t changed is HOW you sell and the validation of what you\'re selling.&#8221;</h2>\n\n\n\n<p class=\"has-drop-cap\"><strong>Cory Miller</strong> talks with <strong>Sean McCabe</strong>, CEO of <strong>Seanwes Media</strong>. While it’s likely never been easier to sell courses for an audience (especially if you are using a system like WordPress), what hasn’t changed — according to Sean — is the marketing and the validation of what you are marketing, how you are marketing it, and how you are pricing it. Sean shares his perspectives on these permanent problems, outlining what has and hasn’t worked for him. Sean also shares his thoughts on what comes first — the community, the courses, or both. This is a must-listen for anyone with a membership course or learning site, or anyone who is thinking of starting one.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n\n\n\n\n<p class=\"has-background\">Every week <strong><a href=\"https://poststatus.com/podcast/the-excerpt/\">Post Status Live</a></strong> will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash. <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a1.png\" alt=\"⚡\" class=\"wp-smiley\" /><br /><br />You can listen to <a href=\"https://poststatus.com/podcast/the-excerpt/\">past episodes</a> of <strong>Post Status Live</strong>, <a href=\"https://poststatus.com/category/post-status-podcasts/\">browse all our podcasts</a>, and don’t forget to subscribe on <a href=\"https://open.spotify.com/show/1m3xwXbe0MG5BzFVPtB0A7\">Spotify</a>, Amazon Music, <a href=\"https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zaW1wbGVjYXN0LmNvbS8ySkU5c2M4UA\">Google Podcasts</a>, <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">iTunes</a>, <a href=\"https://castro.fm/podcast/c53552c6-1ee0-4fc4-9de4-08ed6bf1ee4d\">Castro</a>, <a href=\"https://www.youtube.com/c/PostStatus\">YouTube</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, <a href=\"https://player.fm/series/wordpress-post-status-podcasts\">Player.fm</a>, <a href=\"https://pca.st/05rR\">Pocket Casts</a>, <a href=\"https://wordpress-post-status-draft-podcast.simplecast.com/\">Simplecast</a>, or by <a href=\"https://feeds.simplecast.com/2JE9sc8P\">RSS</a>. <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f3a7.png\" alt=\"🎧\" class=\"wp-smiley\" /></p>\n\n\n\n<h3 id=\"h-mentioned-in-the-show\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f517.png\" alt=\"🔗\" class=\"wp-smiley\" /> Mentioned in the show:</h3>\n\n\n\n<ul><li><a href=\"https://seanwes.com/courses/presale-profits/\" target=\"_blank\" rel=\"noreferrer noopener\"><a href=\"https://seanwes.com/courses/presale-profits/\">Seanwes.com on presale profits</a></a><a href=\"https://twitter.com/corymiller303\" target=\"_blank\" rel=\"noreferrer noopener\">Cory Miller (Twitter)</a></li><li><a href=\"https://twitter.com/post_status\" target=\"_blank\" rel=\"noreferrer noopener\">Post Status (Twitter)</a></li></ul>\n\n\n\n<h3><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f64f.png\" alt=\"🙏\" class=\"wp-smiley\" /> Sponsor: <a href=\"https://poststat.us/ithemes\" target=\"_blank\" rel=\"noreferrer noopener sponsored nofollow\">Pagely</a></h3>\n\n\n\n<p>You need durable Managed WordPress Hosting for all your mission-critical sites.&nbsp;Pagely offers managed DevOps and a flexible stack with the same enterprise-level support to all its customers. Peace of mind starts with Pagely. Try it today!</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Oct 2021 16:57:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: The HeroPress Network Launches Find It WP, a Cooperative Resource Archive for WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=124587\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:237:\"https://wptavern.com/the-heropress-network-launches-find-it-wp-a-cooperative-resource-archive-for-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=the-heropress-network-launches-find-it-wp-a-cooperative-resource-archive-for-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6301:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Two weeks ago, Cate and Topher DeRosia <a href=\"https://wptavern.com/the-heropress-network-launches-as-a-multi-project-portal\">launched the HeroPress Network</a>, a centralized website that would host various projects for helping people with WordPress. Today, the duo announced the opening of <a href=\"https://finditwp.com/\">Find It WP</a>, a new site that is part of the collective. It will serve as a database or archive of all things WordPress.</p>\n\n\n\n<p>The goal is ambitious, and it is powered by submissions from the community. The site is open to anyone who wants to share a WordPress-related resource. &ldquo;Resources&rdquo; in this sense is literally anything. It can be a plugin, agency, podcast, theme shop, or even more. And, if there is not a category available, submitters can recommend a new one.</p>\n\n\n\n<p>&ldquo;This new way to search WordPress resources helps both veteran and beginner users by saving them time and frustration as they try to find what they need,&rdquo; wrote Cate DeRosia in the <a href=\"https://heropressnetwork.com/a-new-wordpress-resource-archive-find-it-wp/\">announcement post</a>. &ldquo;Often, I&rsquo;ve seen someone tweet out that they&rsquo;re looking for a WooCommerce specialist or have a friend ask me if I know of a plugin that does x. Now everyone has a new place to start: Find It WP.&rdquo;</p>\n\n\n\n<p>All of the submissions are manually approved to make sure the content is appropriate. This will add to the team&rsquo;s workload. DeRosia jokingly said her role has become &ldquo;Chief Approval Officer.&rdquo;</p>\n\n\n\n<img />Partial view of the resource submission form.\n\n\n\n<p>&ldquo;And this really highlights the reason we&rsquo;ll be reaching out for funding,&rdquo; she said. &ldquo;There&rsquo;s a lot to maintain with the new additions to the HeroPress Network, resources that seem like they&rsquo;ll be a real asset to the growth of the WordPress community. Instead of each company trying to do this on their own, let&rsquo;s pool our resources and support it together.&rdquo;</p>\n\n\n\n<p>The current plan is to open some funding options for the HeroPress Network on October 24. DeRosia said in an <a href=\"https://heropressnetwork.com/introducing-the-heropress-network/\">earlier announcement</a> that this would be similar to Patreon, where users could fund the mission. However, they will also have a corporate sponsorship program for WordPress businesses.</p>\n\n\n\n<p>&ldquo;I think of it like the local library,&rdquo; she said. &ldquo;Not everyone needs to be in there checking out books and shelving things, but somebody does, and they have to buy groceries, too.&rdquo;</p>\n\n\n\n<p>DeRosia believes this will benefit individuals as well as smaller and larger agencies.</p>\n\n\n\n<p>&ldquo;You never know where a customer is going to come from or what up and coming agency could give you unexpected competition, so this is a simple way to see what all is going on in the WordPress ecosystem,&rdquo; she said. &ldquo;It&rsquo;s also an ideal opportunity to find smaller products and business larger companies may want to acquire.&rdquo;</p>\n\n\n\n<p>I asked her whether including plugins and themes was worth it because there are already dedicated directories and marketplaces for those types of resources.</p>\n\n\n\n<p>&ldquo;We had the same thoughts as you about whether it was worth including plugins and themes, particularly free ones,&rdquo; she responded. She listed four primary reasons they thought it was worth doing:</p>\n\n\n\n<ul><li>If it&rsquo;s for &ldquo;all things WordPress,&rdquo; we need to include all things WordPress.</li><li>We liked that free and paid plugins were searchable alongside each other.</li><li>The WordPress repositories don&rsquo;t have our advanced searching. We&rsquo;re not a replacement for them, just an additional option.</li><li>Reviews can negatively impact products that don&rsquo;t always deserve them. We wanted to level the playing field there.</li></ul>\n\n\n\n<p>DeRosia said the idea for this project and <a href=\"https://wppodcasts.com/\">WP Podcasts</a> came along at about the same time (note: the WP Tavern podcast is <a href=\"https://wppodcasts.com/podcast/wp-tavern/\">listed on the site</a>). The latter was less ambitious in scope, so they launched it first as a case study.</p>\n\n\n\n<p>&ldquo;From the beginning, the driving force behind the HeroPress expansion was to create bridges between the various WordPress communities, and Find It WP seemed like a natural element to that,&rdquo; said DeRosia. &ldquo;It&rsquo;s really difficult to be successful and stay on top of an ever-growing ecosystem like WordPress. With Find It WP, we can simplify it all, for both searchers and those looking to be found.</p>\n\n\n\n<p>&ldquo;I&rsquo;ve spent the last 18 months looking at ways people can get visibility in the WordPress Community, and it&rsquo;s nearly impossible. It&rsquo;s so large and spread out that, even if you have the most amazing new product, it&rsquo;s hard to get noticed. Find It WP simplifies all of that and provides equitable opportunities for anyone.&rdquo;</p>\n\n\n\n<p>Equity is a a crucial part of this project, leveling the playing field for creators regardless of their size. There is no special attention given to major players. The resources are simply there for people to search for and find what they are looking for.</p>\n\n\n\n<p>At the moment, there are currently 42 listings spread across multiple categories. DeRosia said she was getting back to approving more as we ended our chat. As the site grows, it should offer opportunities for more businesses and people to connect.</p>\n\n\n\n<p>&ldquo;The idea for Find It WP did come out of our experiences with HeroPress and expanding into the HeroPress Network,&rdquo; she said. &ldquo;We&rsquo;ve needed help along the way and have been thrilled by the talent we&rsquo;ve come across. If we hadn&rsquo;t been looking or had the connections we had, we wouldn&rsquo;t have found them. We didn&rsquo;t want to keep that to ourselves. We want everyone to be able to experience the benefits that come from working together as a community.&rdquo;</p>\n\n\n\n<p>Topher DeRosia also published a <a href=\"https://heropress.com/a-new-heropress-family-member/\">Find It WP announcement</a> on the HeroPress blog.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Oct 2021 21:58:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:11:\"\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"HeroPress: A New HeroPress Family Member\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://heropress.com/?p=4190\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"https://heropress.com/a-new-heropress-family-member/#utm_source=rss&utm_medium=rss&utm_campaign=a-new-heropress-family-member\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2398:\"<img width=\"1024\" height=\"683\" src=\"https://heropress.com/wp-content/uploads/2121/10/marten-newhall-uAFjFsMS3YY-unsplash-scaled-1-1024x683.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"\" /><p>Last summer when Cate and I were on our anniversary trip we were brainstorming about new things we could bring to the WordPress community that would really help people. Cate came up with the idea of a site that lists every single WordPress resource in the entire world. I was a little dubious at first, but she pitched it well, and I came around. We&#8217;ve spent months planning, building, starting over, and dreaming about it at night, and today we released <a href=\"http://FindItWP.com\">FindItWP.com</a> as part of the <a href=\"https://heropressnetwork.com\">HeroPress Network</a>.</p>\n<h3>So What Is It?</h3>\n<p>Imagine a list of every WordPress resource in the world. Every podcast, every email newsletter, every plugin, every theme, every agency for hire, every news outlet, every training site, etc. Then imagine you can search and filter it, to find exactly what you&#8217;re looking for.</p>\n<p>Now also imagine you&#8217;re a small plugin or theme shop selling a product, struggling to get visibility an overwhelming world. You can get your item listed on an equal platform as places that have far more marketing resources.</p>\n<p>That&#8217;s <a href=\"https://finditwp.com\">FindItWP.com</a>.</p>\n<h3>Who Is It For?</h3>\n<p>Anyone who wants to find something, and anyone who wants to be found.</p>\n<h3>Can I Help?</h3>\n<p>Yes! The entire foundation of Find It WP is the community entering all the resources.&nbsp; There&#8217;s no way a single person, or even a large group could handle it.&nbsp; It has to be all of us or it won&#8217;t really work. Anyone can enter any resource, even if it&#8217;s not theirs. Then if the owner wants to take over the listed we&#8217;ll facilitate that. So literally EVERYONE can help, and be entering content!</p>\n<p>So if you&#8217;re ready to be on the team, <a href=\"https://finditwp.com/add-new-resource/\">start adding resources</a>!</p>\n<h3>Where Can I Learn More?</h3>\n<p>Cate did a <a href=\"https://heropressnetwork.com/a-new-wordpress-resource-archive-find-it-wp/\">wonderful post</a> over on the HeroPress Network site, and it has TONS more information about it than I&#8217;ve written here.&nbsp; I highly recommend checking it out!</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Oct 2021 20:36:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"WPTavern: Software Freedom Conservancy Takes On Vizio in Lawsuit Alleging GPL Violations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=124497\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:221:\"https://wptavern.com/software-freedom-conservancy-takes-on-vizio-in-lawsuit-alleging-gpl-violations?utm_source=rss&utm_medium=rss&utm_campaign=software-freedom-conservancy-takes-on-vizio-in-lawsuit-alleging-gpl-violations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7277:\"<img /><p>Inside of a Vizio TV &ndash; Model V435-J01 &ndash; photo credit: Software Freedom Conservancy</p>\n\" data-medium-file=\"https://wptavern.com/wp-content/uploads/2021/10/Screen-Shot-2021-10-20-at-1.14.16-PM-300x218.png\" data-large-file=\"https://wptavern.com/wp-content/uploads/2021/10/Screen-Shot-2021-10-20-at-1.14.16-PM-500x363.png\" loading=\"lazy\" width=\"880\" height=\"638\" src=\"https://wptavern.com/wp-content/uploads/2021/10/Screen-Shot-2021-10-20-at-1.14.16-PM.png\" alt=\"\" class=\"wp-image-124577\" srcset=\"https://wptavern.com/wp-content/uploads/2021/10/Screen-Shot-2021-10-20-at-1.14.16-PM.png 880w, https://wptavern.com/wp-content/uploads/2021/10/Screen-Shot-2021-10-20-at-1.14.16-PM-300x218.png 300w, https://wptavern.com/wp-content/uploads/2021/10/Screen-Shot-2021-10-20-at-1.14.16-PM-500x363.png 500w, https://wptavern.com/wp-content/uploads/2021/10/Screen-Shot-2021-10-20-at-1.14.16-PM-768x557.png 768w\" sizes=\"(max-width: 880px) 100vw, 880px\" />Inside of a Vizio TV &ndash; Model V435-J01 &ndash; photo credit: Software Freedom Conservancy\n\n\n\n<p>The Software Freedom Conservancy <a href=\"https://sfconservancy.org/copyleft-compliance/vizio.html\">announced</a> that it is suing Vizio, an American TV manufacturer, for what it alleges are &ldquo;repeated failures to fulfill even the basic requirements of the General Public License (GPL).&rdquo; </p>\n\n\n\n<p>The 501(c)(3) charity organization is a non-profit that provides infrastructure support for free and open source software projects, defending users&rsquo; rights under copyleft licenses and the GPL. A few of its member projects include BusyBox, Git, Homebrew, OpenWrt, and phpMyAdmin. As part of its mission, the Conservancy assists member projects in enforcing the terms of FLOSS licenses, including through litigation.</p>\n\n\n\n<p>The Software Freedom Conservancy contends that Vizio&rsquo;s TV products contain software with copyleft licenses but the company refused to provide the source code after multiple attempts at contact since 2018. Vizio also did not inform its customers about the rights included with the software it was bundling.</p>\n\n\n\n<p>&ldquo;We filed suit as a purchaser of TVs to stand up for copyleft,&rdquo; Software Freedom Conservancy Executive Director Karen Sandler said. &ldquo;There was no source or offer for source even after we&rsquo;d been working with them for a long time on older products. Copyleft can help us take control of our tech in a meaningful way, it&rsquo;s a huge benefit to consumers.&rdquo;</p>\n\n\n\n<p>In a new twist on GPL enforcement, the organization is presenting this lawsuit on behalf of individual consumers, as opposed to the traditional path of defending copyright holders of the GPL code in question.</p>\n\n\n\n<p>The Software Freedom Conservancy contends that Vizio&rsquo;s alleged noncompliance prevents consumers from being able to repair their devices, improve and control them, as well as curtail surveillance and ads through modifications. The <a href=\"https://sfconservancy.org/docs/conservancy-v-vizio-original-complaint-2021-10-19.pdf\">full text of the complaint</a> includes examples of how consumers might benefit from having access to the source code:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Vizio is unlikely to unilaterally implement features that prevent the collection of such user data, as such user data is valuable to Vizio. Access to the Source Code of the Linux kernel, the other SmartCast Programs at Issue, and for the Library Linking Programs, as used on Vizio smart TVs, would enable software developers to preserve useful but obsolete features. It would also allow software developers to maintain and update the operating system should Vizio or its successor ever decide to abandon it or go out of business. In these ways, purchasers of Vizio smart TVs can be confident that their devices would not suffer from software-induced obsolescence, planned or otherwise.</p></blockquote>\n\n\n\n<p>In the organization&rsquo;s announcement of the lawsuit, Sandler highlighted the environmental impact of denying consumers access to the code.</p>\n\n\n\n<p>&ldquo;The global supply chain shortages that have affected everything from cars to consumer electronics underscore one of the reasons why it is important to be able to repair products we already own,&rdquo; says Sandler. &ldquo;Even without supply chain challenges, the forced obsolescence of devices like TVs isn&rsquo;t in the best interest of the consumer or even the planet. This is another aspect of what we mean by &lsquo;ethical technology.&rsquo; Throwing away a TV because its software is no longer supported by its manufacturer is not only wasteful, it has dire environmental consequences. Consumers should have more control over this, and they would if companies like Vizio played by the rules.&rdquo;</p>\n\n\n\n<p>The complaint alleges that Vizio is in breach of the GPLv2 and the LGPLv2.1 every time they distribute a smart TV without the source code or a written offer to provide it. It claims that none of the smart TVs Vizio has introduced in the US market in the past four years have been accompanied by the source code. </p>\n\n\n\n<p>Open source leaders from affiliate organizations commented on the unique approach of this lawsuit, where the Conservancy is acting on behalf of consumers as the plaintiff, as opposed to prevailing upon the copyright holder to defend its users. The complaint states:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>No one other than the purchaser has both the information and motive to enforce the Source Code Provision. Purchasers will both know whether the Source Code Provision has been honored and have a desire to examine and further develop the corresponding source code.</p></blockquote>\n\n\n\n<p>&ldquo;If this consumer-rights-based approach succeeds, the main excuse for copyright assignments to organizations like the FSF will be gone and we can unambiguously treat a CLA as a red flag,&rdquo; Open Source Initiative Director of Standards/Policy Simon Phipps said.</p>\n\n\n\n<p>The complaint states that the &ldquo;Plaintiff and other members of the class of persons intended to benefit from the GPLv2 and LGPLv2.1 have been damaged in an amount that cannot be readily determined.&rdquo; Vizio&rsquo;s alleged noncompliance has effectively stunted the source code&rsquo;s potential for improvements from consumers for years. It has also robbed consumers of the control of their electronics and given Vizio an unfair advantage that protects their corporate interests at the expense of users&rsquo; freedoms. The Conservancy is not seeking an exact amount for damages but rather leaving it to the judgment of the court. </p>\n\n\n\n<p>&ldquo;This lawsuit has the potential to empower many consumers, radically changing the landscape of consumer technology,&rdquo; Open Source Initiative Executive Director Stefano Maffulli said.</p>\n\n\n\n<p>The Conservancy&rsquo;s case will be an important one to watch, as its decision could set a precedent for GPL enforcement in the future. If nothing else, it should signal to companies benefiting from GPL-licensed code that they must also respect consumers&rsquo; rights. If consumers are the intended third-party beneficiaries of the license agreement, then they have a right to the source code. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Oct 2021 20:07:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"WPTavern: Tidying the Media Library With WP Ninjas’ Remove Unused Media Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=124177\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:199:\"https://wptavern.com/tidying-the-media-library-with-wp-ninjas-remove-unused-media-plugin?utm_source=rss&utm_medium=rss&utm_campaign=tidying-the-media-library-with-wp-ninjas-remove-unused-media-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6172:\"<p class=\"has-drop-cap\">A few weeks ago, <a href=\"https://wp-ninjas.de/remove-unused-media\">WP Ninjas announced</a> it was stepping into the media optimization plugin market. The team released its <a href=\"https://remove-unused-media.com/en\">Remove Unused Media</a> plugin as a commercial project for tidying storage space. I received a full copy of it and put it through the ropes.</p>\n\n\n\n<p>With so many commercial plugins, I am accustomed to the developers creating an entirely new menu item, taking up precious admin real estate. This happens even with those that just have a single screen too. However, I was happy to see the WP Ninjas team tucked everything neatly under &ldquo;Media&rdquo; as a sub-menu. We were off to a good start, and things only got better.</p>\n\n\n\n<p>When I review plugins, there is one thing that I consistently preach: simplicity. That begins with following the core WordPress UI and sticking as closely to it as the plugin&rsquo;s features will allow. In essence, <em>don&rsquo;t make me think</em> about how to use your plugin.</p>\n\n\n\n<p>For the most part, Remove Unused Media got the user experience right.</p>\n\n\n\n<p>I could nitpick a few design choices with the interface, such as modifying the list table with rounded corners and extra padding. The &ldquo;filter&rdquo; sub-navigation also deviates from the standard. And, the &ldquo;last analysis&rdquo; message should receive the WordPress admin notice treatment so that it stands out.</p>\n\n\n\n<p>These are all core UI elements with unnecessary customizations. However, they did not diminish the experience on the whole. The plugin mostly stuck with the WordPress standard.</p>\n\n\n\n<p>The real question is whether the plugin does what it says on the tin. <em>What is the experience of removing unused media like?</em></p>\n\n\n\n<p>It was easy. Users merely need to click the &ldquo;Start Analysis&rdquo; button and wait a few seconds. The plugin then has three tabs:</p>\n\n\n\n<ul><li>Unused Media</li><li>Used Media</li><li>Ignored</li></ul>\n\n\n\n<p>The Unused Media tab presents an overview of all media that the plugin could not find used on the site. There is a possibility that it missed something. However, I only found one old-school scenario where this happened, which I will dive into later.</p>\n\n\n\n<img />Unused media screen.\n\n\n\n<p>From this point, end-users can manually delete individual media attachments or use the bulk-delete option. Before doing so, the plugin recommends making a backup of the site &mdash; solid advice for any such plugin.</p>\n\n\n\n<p>My favorite feature of the plugin was not its primary feature of deleting media. It was actually the &ldquo;Used Media&rdquo; screen. Its &ldquo;Where?&rdquo; and &ldquo;How?&rdquo; columns break down where images, videos, and other files are used and in what context.</p>\n\n\n\n<img />Used media screen.\n\n\n\n<p>It reminded me of the &ldquo;instances&rdquo; screen for the WordPress <a href=\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced\">admin block directory proposal</a> from 2019. The concept showed where specific blocks were used across the site. Remove Unused Media does the same thing for media files.</p>\n\n\n\n<p>The &ldquo;Ignore&rdquo; tab for the plugin keeps track of media files that should not be deleted, even if they are unused. Users can click a link from the other screens to add them to the list. This persists after running a new analysis too.</p>\n\n\n\n<p>The plugin scans several third-party plugins like Elementor, Beaver Builder, ACF, and Yoast SEO. Some store media instances outside of the post content, such as in custom post meta, and Remove Unused Media searches those specific fields.</p>\n\n\n\n<p><a href=\"https://remove-unused-media.com/en/pricing/\">Pricing</a> starts at 39&euro; ($45.38 at today&rsquo;s exchange rate) for one year of support and updates for a single site. It also has a five-site option at 149&euro; and a 100-site tier at 299&euro;.</p>\n\n\n\n<p>For the first version, the user experience felt solid. However, it does not have much in the way of customizability. That could be a sticking point for users who are looking for a more flexible premium option.</p>\n\n\n\n<h2>Exploring Alternatives</h2>\n\n\n\n<p class=\"has-drop-cap\">The plugin is not the first of its kind. The <a href=\"https://wordpress.org/plugins/media-cleaner/\">Media Cleaner</a> plugin by Meow Apps is free, routinely updated, and has over 40,000 active installations. It also has a commercial version with more features, such as third-party plugin integration, WP-CLI support, filesystem scan, and live-site analysis.</p>\n\n\n\n<img />Media Cleaner plugin results.\n\n\n\n<p>The UI for Remove Unused Media feels more like WordPress. Its &ldquo;Used&rdquo; tab also shows where (i.e., what posts) and how (e.g., content, featured image) specific media files are used across the site. This feature alone makes it worthwhile for me.</p>\n\n\n\n<p>One area where Media Cleaner shines is its option for ignoring (not deleting) attached media. This is a vital feature if users have ever added the old <code>gallery</code> shortcode. At one point, WordPress simply displayed all attached images as a gallery. Eventually, it specified the IDs in the shortcode. However, for those older instances, this was not the case. Without enabling this option, those media items might get queued up for deletion.</p>\n\n\n\n<p>The Remove Unused Media plugin does not have such an option. Attached images that are not explicitly used are considered unused. This may not be an issue for most users, but those with old gallery shortcodes should be aware of potential problems.</p>\n\n\n\n<p>The baseline features for both are similar. Remove Unused Media gets the edge in its default user interface and experience. However, Media Cleaner has many more options for customizing how the plugin works. Plus, users who cannot afford an upgrade can always run the free version.</p>\n\n\n\n<p>This is not to say either is better or worse than the other. Both were solid options in my tests. I just want to merge the best features from each, snagging the interface from Remove Unused Media and the configurability of Media Cleaner.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Oct 2021 01:31:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"Gutenberg Times: Gutenberg Adoption: Levels One through Five — Page Builder Summit, October 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://gutenbergtimes.com/?page_id=19119\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://gutenbergtimes.com/gutenberg-adoption-levels-1-5-page-builder-summit-october-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:446:\"<p class=\"has-large-font-size\">Thank you for attending my talk at the Page Builder Summit! 💕</p>\n\n\n\n<p>Follow-up from the Page Builder Summit October 18 &#8211; 22, 2021 and the presentation: &#8220;<strong>Customizing WordPress Block Editor for Client Projects</strong>&#8221; by Birgit Pauli-Haack </p>\n\n\n\n\n\n\n\n<p><em>Video is still rendering</em></p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"toolbelt-video-wrapper\"></div>\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 Oct 2021 15:15:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: Build Notification Banners With ElmaStudio’s Latest Block Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=124460\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:191:\"https://wptavern.com/build-notification-banners-with-elmastudios-latest-block-plugin?utm_source=rss&utm_medium=rss&utm_campaign=build-notification-banners-with-elmastudios-latest-block-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5840:\"<p class=\"has-drop-cap\">A friend and I were discussing the need for more one-off block plugins earlier today. He had mentioned that WordPress has this powerful block search feature that rarely turns up anything useful. Most are part of collections that do not appear in the results. This was part of a more wide-ranging conversation that I am sure I will tackle on another day.</p>\n\n\n\n<p>However, it reminded me that I had a couple of ElmaStudio&rsquo;s block plugins sitting in the backlog along with some notes on them. The team released <a href=\"https://wordpress.org/plugins/aino-accordion-faq-block/\">Aino Accordion FAQ Block</a> and <a href=\"https://wordpress.org/plugins/aino-notification-block/\">Aino Notification Banner Block</a> three weeks ago. The latter piqued my interest more so than the former.</p>\n\n\n\n<img />Inserting an error notification.\n\n\n\n<p>The two-person team of Ellen Bauer and Manuel Esposito could have continued amassing a collection within their existing Aino Blocks plugin. Instead, they took a turn down the path few have traveled. They are now releasing single-purpose blocks.</p>\n\n\n\n<p>&ldquo;We plan to work on smaller add-on single blocks from now on as well,&rdquo; <a href=\"https://wptavern.com/a-second-look-at-elmastudios-aino-theme-and-companion-block-plugin#comment-392898\">said Bauer in the comments</a> on my last <a href=\"https://wptavern.com/a-second-look-at-elmastudios-aino-theme-and-companion-block-plugin\">review of their theme and block library</a>. &ldquo;Blocks that are needed for building more complex block page templates.&rdquo;</p>\n\n\n\n<p>Notification boxes are so commonplace that you almost wonder why they are not a part of core WordPress. Many block collection plugins bundle one or multiple, but it is hard to find a solid solution as a single block.</p>\n\n\n\n<p>The block has six statuses that users can select from:</p>\n\n\n\n<ul><li>Welcome</li><li>Info</li><li>Help</li><li>Success</li><li>Warning</li><li>Error</li></ul>\n\n\n\n<p>Each status has its own icon and default colors. The colors are customizable, but the icon itself is not. I am a fan of the decision because it means one less choice I must make. There is also an option to hide the icon and switch between fill and outline versions.</p>\n\n\n\n<img />Testing different notification statuses.\n\n\n\n<p>The block also displays a &ldquo;dismiss&rdquo; button for visitors to close the banner on the front end. The state is not saved, so if the visitor returns to the page, it will reappear. I would like to see an option to store the banner state in the browser in the future.</p>\n\n\n\n<p>I like the plugin for its simplicity. The default output works well enough for most themes, but it has enough options for users to customize it.</p>\n\n\n\n<p>The upcoming site editor is where the plugin could really shine. Of course, a user would need a block theme to use it there, such as ElmaStudio&rsquo;s <a href=\"https://wordpress.org/themes/aino/\">Aino</a>. The block offers a quick and easy way of plopping something like a sales banner across the top of the site.</p>\n\n\n\n<img />Adding a sales banner at the top of the site.\n\n\n\n<p>I do have a few nit-picks, of course. These are not <em>OMGBBQ</em> problems that make the plugin unusable. Instead, they are places where it could be improved.</p>\n\n\n\n<p>Because many themes use a top margin approach to vertical rhythm, it can disrupt the alignment of the icon and paragraph. The plugin should zero this out.</p>\n\n\n\n<p>If anyone else runs into this issue, the following CSS is a quick fix:</p>\n\n\n\n<pre class=\"wp-block-code\"><code>.wp-block-ainoblocks-notification-block .content-wrapper p:first-of-type {\n    margin-top: 0;\n}</code></pre>\n\n\n\n<p>One of the downsides to the plugin is its custom system for borders and padding. From a development perspective, I prefer the plugin&rsquo;s system under the hood, which uses a curated set of values that keep a user from doing something really crazy. It offers a balance between flexibility and rational choices.</p>\n\n\n\n<img />The plugin&rsquo;s custom controls.\n\n\n\n<p>I have argued that most design controls should have such a system &mdash; the same one that is in place for font sizes and colors &mdash; <em>ad nauseum</em>. However, Gutenberg and core have moved in a different direction, preferring arbitrary user-defined values over a range of presets. Plugin authors should fall in line for the sake of users.</p>\n\n\n\n<p>As a user, I prefer consistency. I want the interface to be the same, regardless of whether I am dealing with a core or third-party block. Having to learn multiple methods to add padding or change a border creates unnecessary friction.</p>\n\n\n\n<p>The plugin&rsquo;s custom system also conflicts with default block styles that theme authors can define in their <code>theme.json</code> files. The standards set by WordPress create a bridge between plugins and themes that the platform has never had before. The more block developers follow it, the easier it is for theme designers to work within the system.</p>\n\n\n\n<p>There are other options. In the past week, the <a href=\"https://wordpress.org/plugins/alert-box-block/\">Alert Box Block</a> plugin landed in the directory. It provides far more icon options and more design controls in general. However, its UI is so different from the WordPress standard that I cannot imagine using it.</p>\n\n\n\n<p>When I talk about issues with Aino Notification Banner, it must be taken into context. I point out problems because I see its potential. I want the developers to continue iterating on it, improving what is already one of the best options out there. This is something that ElmaStudio has proven it can do with earlier projects, so I look forward to what the plugin looks like in the future. For now, it is a solid option for users who need to display notification boxes.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 Oct 2021 00:08:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: Gutenberg Contributors Propose Renaming Reusable Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=123800\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:175:\"https://wptavern.com/gutenberg-contributors-propose-renaming-reusable-blocks?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-contributors-propose-renaming-reusable-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4106:\"<p>WordPress&rsquo; Reusable blocks may soon be <a href=\"https://github.com/WordPress/gutenberg/issues/34352\">getting re-named</a>, as the feature&rsquo;s distinct capabilities are less recognizable from its name following the introduction of patterns. </p>\n\n\n\n<p>When the Gutenberg project first took off, nobody had any idea how important patterns would become in the page building experience, or that they would be getting their own directory on WordPress.org. During a demo at WordCamp Europe 2021, Gutenberg lead architect Mat&iacute;as Ventura commented on how transformative patterns have been for making page design approachable for users.</p>\n\n\n\n<p>&ldquo;Perhaps it was a smaller part of the roadmap initially but it&rsquo;s becoming a centerpiece &ndash; especially because it allows&hellip;world class designers to provide a starting point for users and users get to learn design as they are interacting with themes,&rdquo; Ventura said.&nbsp;</p>\n\n\n\n<p>A year later, patterns have made their way to the forefront of theme design and development with an excitement that rivals <a href=\"https://wordpress.com/blog/2006/02/25/wordpress-widgets/\">the introduction of widgets</a> in WordPress&rsquo; earlier days. WordPress 5.9 will feature <a href=\"https://github.com/WordPress/gutenberg/issues/31153\">pattern insertion</a> directly from the Pattern Directory so users will be able to change their patterns as often as they like, without having to switch themes. Coming in Gutenberg 11.8, the pattern inserter will <a href=\"https://github.com/WordPress/gutenberg/pull/35115\">highlight featured patterns from the directory</a> in the initial view, instead of displaying the first alphabetical category. Contributors are also considering a path for allowing themes to <a href=\"https://github.com/WordPress/gutenberg/issues/35364\">surface specific patterns from the directory</a> instead of bundling them.</p>\n\n\n\n<p>In light of all this activity around Patterns, Reusable blocks are in need of a renaming that is more descriptive. </p>\n\n\n\n<p>&nbsp;&ldquo;In the end, patterns are also&nbsp;<em>reusable</em>&nbsp;pieces of design,&rdquo; Ventura said.</p>\n\n\n\n<p>&ldquo;Given the nature of these [Reusable] blocks is to have content in sync wherever it&rsquo;s displayed &mdash; edit once; update everywhere &mdash; I propose we change the name in the UI to &lsquo;Synced Blocks&rsquo; and adjust the block description a little bit to clarify that.&rdquo;</p>\n\n\n\n<p>The UI for Reusable Blocks is confusing because it is built on top of assumptions that users know the intricacies of how they work. WordPress developer Lee Hodson <a href=\"https://github.com/WordPress/gutenberg/issues/31163#issuecomment-898376830\">summarized the problem</a> and how the current UI leads to reusable blocks being accidentally edited:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>The save reusable blocks dialog is nice but how many creators actually understand what this save dialog means? On the surface it looks as though everyone should understand the save/not save option but it&rsquo;s meaning is only obvious when you understand that reusable blocks are (currently) meant to either (a) not be edited or (b) edits to them are meant to affect all instances of the same block and (c) that reusable blocks can be converted to editable blocks (and not everyone immediately understands the difference) when edits to reusable blocks are meant to be independent of the block&rsquo;s template.</p><p>I feel that a nice idea (reusable blocks) has been very badly implemented and many creators are blissfully unaware of its pitfalls until they realize their &lsquo;template blocks&rsquo; have been overwritten.</p></blockquote>\n\n\n\n<p>Several contributors participating in the renaming discussion concurred that &ldquo;Synced Blocks&rdquo; would be a better name for the feature. This suggestion is the frontrunner so far. The conversation is still open and consideration of this proposal has been added to the <a href=\"https://github.com/WordPress/gutenberg/issues/27890\">Reusable Blocks Improvements</a> tracking issue.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Oct 2021 21:50:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WordPress.org blog: WP Briefing: Episode 18: The Economics of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11351\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wordpress.org/news/2021/10/episode-18-the-economics-of-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:20740:\"<p>In episode 18 of WP Briefing, Josepha Haden Chomphosy reflects on a recent lecture that she gave to students at Hendrix College in which she explored the economics of WordPress and the principles that sustain the project&#8217;s ecosystem.</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href=\"mailto:wpbriefing@wordpress.org\">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<ul><li>Editor:&nbsp;<a href=\"https://profiles.wordpress.org/dustinhartzler/\">Dustin Hartzler</a></li><li>Logo:&nbsp;<a href=\"https://profiles.wordpress.org/beafialho/\">Beatriz Fialho</a></li><li>Production:&nbsp;<a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>\n\n\n\n<h2>References </h2>\n\n\n\n<p><a href=\"https://wordpress.org/showcase/\">WordPress Showcase</a></p>\n\n\n\n<p><a href=\"https://wpengine.com/resources/value-of-wordpress-worlds-first-study-of-wordpress-economy/#An_Expansive_WordPress_Ecosystem\">The Value of WordPress: The World&#8217;s First Study of the WordPress Economy </a></p>\n\n\n\n<p><a href=\"https://wordpress.org/five-for-the-future/\">Five for the Future</a></p>\n\n\n\n<p><a href=\"https://make.wordpress.org/core/2021/10/15/wordpress-5-9-feature-go-no-go-october-14-2021/\">WordPress 5.9 Feature Go/No-Go </a></p>\n\n\n\n<h3>Digital Citizenship Resources</h3>\n\n\n\n<p><a href=\"https://wordpress.org/news/2019/10/becoming-better-digital-citizens-through-open-source/\">Becoming Better Digital Citizens Through Open Source</a></p>\n\n\n\n<p><a href=\"https://wordpress.org/news/2019/10/empowering-generations-of-digital-natives/\">Empowering Generations of Digital Natives</a></p>\n\n\n\n<p><a href=\"https://wordpress.org/news/2019/10/responsible-participation-in-online-communities/\">Responsible Participation in Online Communities</a></p>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id=\"more-11351\"></span>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:11</p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Joseph Haden Chomphosy. Here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:40</p>\n\n\n\n<p>So today marks the start of Digital Citizenship week. This year in 2021, it is the week of October 18th, and to kick it off, I want to share with you a bit of a lecture that I gave to a college class last week.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:55</p>\n\n\n\n<p>An economics professor teaches this class. And so, a little bit, I went to talk about how WordPress is essentially a microcosm of global societies. That was mostly why I was invited to come and give the talk. But one of the students asked a really interesting question about economics, and especially the economics of WordPress. And so, I&#8217;m going to take some time to do my best to answer that question here as well. But first, we&#8217;re going to start with some big picture information about WordPress that I shared with the students, and then maybe you also don&#8217;t necessarily know.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:00</p>\n\n\n\n<p>So the first place that we started was with the question of what WordPress is. Most of them had heard of it but didn&#8217;t necessarily have a good handle on what it is. And so this is the definition that I gave to them. This is a bit of each of the facets of WordPress that we kind of see right now.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:57</p>\n\n\n\n<p>Firstly, WordPress is, of course, a content management system, which means it&#8217;s a piece of software that uses a copyleft license, which means that it&#8217;s open source, and no one individual necessarily owns the rights to the code. If you get very specific, WordPress is, of course, a FOSS project or a free and open source software project. I know that there are discussions around when a piece of software is free, then what are you using to pay for that piece of software or to pay for your access to that software? And often, the answer is that you&#8217;re using your personally identifying information to pay for something commonly referred to as the data economy. If you&#8217;re not familiar with that, it&#8217;s a little bit of a three-pronged effort there. So you submit your data to get access to the software, or you can join the platform, depending on what it is that you&#8217;re working with. That platform or that software collects your data so that they can build a profile about what sorts of content engages you and so that they can share, essentially, audience cohorts like groups of people that kind of are talking about what you&#8217;re talking about, agree with what you agree about, and find interesting, the same sorts of things that you find interesting. And then those companies sell access to your attention. This is something that I refer to as the attention economy. I think there are a lot of startups at the moment that refers to the attention economy. The most iconic recent example was when the folks over at Netflix said that they weren&#8217;t competing against other streaming services; they were competing against sleep.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:54</p>\n\n\n\n<p>And I think that might ring true for quite a few of us at the moment. But anyway, to scoot us back one level, I had, as I said, WordPress is free software. But the difference with WordPress is that to get a copy of WordPress, you are not necessarily required to hand over any data. You don&#8217;t need to give anyone data to get a copy. You don&#8217;t need to give anyone money or data to open up a copy that you own or to build a website in it if you&#8217;re just doing it locally, but especially around that data side because WordPress is not collecting any data, we&#8217;re also not brokering access to anyone&#8217;s attention.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:37</p>\n\n\n\n<p>Another answer to the question of &#8220;What is WordPress?&#8221; WordPress software and the project enable nearly half a trillion dollars of revenue in the global digital economy, as we learned from a recent study from one of the hosting companies inside the WordPress project&nbsp; &#8211; oh, Inside the WordPress ecosystem anyway. And WordPress also runs 42% of the web, with some of the biggest sites we know using WordPress. Such sites like the New York Times, Rolling Stone, many, many others, which you can see in the WordPress showcase as well. I don&#8217;t necessarily want to just like call out all the big groups that use it. But it&#8217;s a lot.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:22</p>\n\n\n\n<p>&nbsp;To recap what we just learned about WordPress and what WordPress is. It is software that one uses a copyleft license, meaning no single entity owns it. Two, it is available at no cost, meaning no money changes hands for you to own a copy. Three does not track you, which means that you don&#8217;t have to give WordPress any personally identifying information to get a copy. Four is an enabler of a massive digital economy massive portion of the digital economy even. That, you know, means their services, extensions, themes, plugins, all of that stuff. And five, it is software that supports 42% of the web. Practically every other site you visit uses the software. So that&#8217;s WordPress.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:10</p>\n\n\n\n<p>With this massive free software, you might be thinking to yourself a couple of things. The first thing you might be thinking is, &#8220;Well, that sounds impossible.&#8221; But if that&#8217;s not what you&#8217;re thinking, you may be thinking, &#8220;how is it possible that a software that is technically owned by no one and takes no money or data to obtain &#8211;&nbsp; how is it that a software like that can power 42% of the web.&#8221; This brings me, of course, to a topic that I specialize in, which is how WordPress is made.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:45</p>\n\n\n\n<p>WordPress is, by now you know, built by a global community of contributors. And it&#8217;s partially contributors that are self-sponsored or giving of their own time freely, and partly sponsored volunteers, people who are paid by Five for the Future initiatives inside various companies. I have said many times, most recently at WordCamp US, that I have an ideal ratio of about two to one in that kind of volunteer or self-sponsored versus corporately sponsored set of voices. And also, as I said, at WordCamp US, we’re not necessarily getting to that ideal ratio right now because of the nature of the way the world is at the moment. However, this community functions almost like a tiny little digital society. There are ways to get your voice heard ways to take on leadership roles; there is a little bit of light governmental structure. And as with any society, any community like this, there&#8217;s a relationship inherent there. There&#8217;s almost a transactional element that takes place when you&#8217;re participating fully. Although I know that for the WordPress project, especially for open source in general, there is a reminder that we should always be contributing without the expectation of reciprocity. But even if you are contributing without the expectation of reciprocity, you still are engaging in an existing community, which means that you are fostering a relationship with the community or with the people who are also participating in the community with you. It&#8217;s just inescapable if you have people around and working together.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>08:38</p>\n\n\n\n<p>So two concepts really informed my work to future-proof the WordPress project. And the first one is digital citizenship, which is why this particular WordPress Briefing fits today. And the other is the Tragedy of the Commons, especially how we go about refreshing those commons. So digital citizenship, I talked about it a bit in the last WP Briefing. But it&#8217;s still true today that that&#8217;s important. And the thing that really matters to me as we are working through how to make sure that WordPress is moving forward together. But most discussions of citizenship are location-specific, which makes plenty of sense. However, with so many mobile devices and broader access to some level of internet, we have increasing opportunities to be connected because of interests or skill sets. And even the things that we aspire to or aspire to be with a community like WordPress, which has no home office or main location. Of course, it&#8217;s very important that all of the leaders in WordPress, all of the team reps in WordPress, are proactively engaging with the people in their teams and in their portions of the community instead of waiting for like happenstance running into people. We also use a bunch of social stuff to get people together: twitch screams, not twitch screams because it&#8217;s not that Halloweeny! Twitch streams, hallway hangouts, events that are both online and off. Everything that the Learn section of the community is doing with their discussion groups. There are so many ways that WordPress proactively engages with each other and engages with itself. And that work is all really important to keeping the community involved, which is key to any organization&#8217;s long-term success, and certainly is true for WordPress as long-term success. Because when your community or your organization or your society is engaged and invested in your collective success, then you are (get ready for a list) one, more likely to see obstacles early and be able to overcome them, two more likely to see upcoming trends and prepare for them, three more likely to see what is broken and be able to repair it before it is a major issue. And four, you are more likely to be a resilient and fruitful organization long after any single member has stopped participating.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>11:10</p>\n\n\n\n<p>The more connected to the community you are and the more active, the greater your influence and the ability to affect changes also become. And so, not only is it important for us to remain connected as a community just to make sure that everything is going well. But also, it&#8217;s one of the primary ways that people who are giving back can sort of have more of an opportunity in this particular ecosystem. In open source, anyone can gain influence by helping others by helping the software and by keeping the trains on the tracks. And so, one of the only lasting limits to long-term potential in an open source project is how good you are at seeing beyond yourself and seeing what good action can make beyond just your own benefits. I understand that there are also specific hurdles to contribution in your free time that I have dedicated a couple of different podcasts to, so I don&#8217;t want to neglect that reality.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>12:19</p>\n\n\n\n<p>I have found in my experience that one of the limiting factors that sometimes cannot be unlearned is not being able to see kind of a broader scope, a broader perspective than what you&#8217;re already bringing into it.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>12:34</p>\n\n\n\n<p>So being a good digital citizen, that&#8217;s a really important part of keeping any society together any organization together and moving forward. But especially is in the context of digital citizenship, is true for WordPress.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>12:48</p>\n\n\n\n<p>The second thing that is really important to me is this concept of the Tragedy of the Commons, which is, of course, an economics term, open source has borrowed. We have talked about it in this podcast in the past. And today, I specifically am talking about how WordPress works to consistently be refreshing the commons. So the theory of the Tragedy of the Commons says that all societies can withstand a certain volume of free-riders. A certain number of people who reap the benefits of that community’s society without necessarily putting anything back into it. And that is no different in open source than in any other place where you would apply this concept. The particular catch for WordPress is of course, that it is free, freely available and has no specific copyright holder. And so in those circumstances, it is incredibly easy for a small group of people to maintain the software while the whole world uses it for free. And not only is it possible for a small group of people to maintain it, but if you&#8217;re not careful, it&#8217;s also easy for a small group of unpaid people and unacknowledged people to maintain something forever. And at the volume that WordPress operates at, that&#8217;s a really risky choice. It doesn&#8217;t help to support those people; it puts the long-term stability of the software in jeopardy. And at the end of the day, it just does not help to replenish the commons to make sure that everybody keeps getting to have the benefits of this ecosystem in the long term.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>14:39</p>\n\n\n\n<p>As many of you know, there is this program called Five for the Future. And that program is essentially modeled after a tithe. So the invitation to this program when it was first introduced in 2014 was that if you or your company or your community is made better or made possible by WordPress, you should give back to the WordPress project 5% of your resources.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>15:07</p>\n\n\n\n<p>It is an aspirational 5%, of course, and some groups give back their time while others give back with their money. But almost anyone who wants to give back has some skill that WordPress needs. That particular program has really grown in leaps and bounds since it was introduced. I don&#8217;t know exactly how many team members were considered Five for the Future contributors when it was first introduced in 2014; it was a little before my time. But at the moment, it&#8217;s about 150 people that I am routinely aware of or in contact with, which is still a small number considering how many people use WordPress.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>15:52</p>\n\n\n\n<p>However, many corporations who have seen the most benefit, including, you know, the company that I work for (Automattic), and a lot of other hosting companies in the ecosystem, all do a really good job of refreshing the commons so that WordPress is still usable for businesses of all levels.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>16:11</p>\n\n\n\n<p>I want to leave us with one final big picture thought about open source. This is going to be a callback to one of my earliest episodes in this podcast. But I think that it&#8217;s always worth remembering. We&#8217;re going to talk about this really popular phrase in open source projects &#8220;free as in speech, not free as in beer.&#8221; And for WordPress, as you know, it&#8217;s a little bit of both. It&#8217;s literally free. But also, since it&#8217;s open source, it has a free as in speech component to it as well.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>16:46</p>\n\n\n\n<p>The four freedoms of open source as laid out in the 90s. So 10 years into the open source movement, are basically that you have the freedom to run the program for any purpose, the freedom to study how the program works, and change it so that it can do your computing as you wish, the freedom to redistribute copies so that you can help your neighbor and the freedom to distribute copies of your modified versions, giving the community a chance to learn and benefit from the changes that you put into the software.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>17:22</p>\n\n\n\n<p>I don&#8217;t remember if I said this in my original podcast, but I&#8217;m going to say it today, free speech has a lot of responsibility, just like being a part of a community. Governments or communities, or in our case, this software is built by the people who show up. For WordPress at 42% of the web, every small choice we make can cause huge changes in how people experience the web today and tomorrow. And that, to my mind, is really no different than participating in any sort of civic infrastructure. The changes that are made today, or the errors that we prevent, set the tone and the circumstance and the potential to thrive for everyone who comes after us.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>18:17</p>\n\n\n\n<p>That leads us into our smallest of big things. I just have a couple of things for you all today. Firstly, at the time of this recording, this is prior to the Go/No-Go demo meeting for WordPress 5.9. So I have no idea what&#8217;s happened. But by the time this podcast has been released, we will have had the Go/No-Go meeting and also have shipped the post that summarizes what happened, what we hope to change in the next essentially sprint so that we can confidently move forward with a clear set of features for the 5.9 release. I will include a link to the notes below in the show notes. Kudos to everyone, props to everyone who participated in that meeting. And also props to all the people who have been helping us as we head into this final release of the year and all of you who are going to help us make it successfully to the end.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>19:15</p>\n\n\n\n<p>The second thing I already kind of alluded to at the top of the podcast, it is Digital Citizenship week; two or three years ago, the WordPress blog had a series about digital citizenship and what it means to be a good digital citizen, what it means to do that in the context of WordPress. I will drop a link to those posts in the show notes as well. They are very well written and very important, and fairly evergreen content. If I think that there is something worth updating, I will update it before putting it in the show notes. And that is your small list of big things.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>19:57</p>\n\n\n\n<p>Thank you all for tuning in today for the WordPress sprint. I&#8217;m your host, Joseph Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Oct 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:141:\"Gutenberg Times: Changelog #53 – WordPress 5.9 Go/No Go decision, Gutenberg releases 11.6 and 11.7, and Themes and Styles for the Editor￼\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/?post_type=podcast&p=19322\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://gutenbergtimes.com/podcast/changelog-53-wordpress-5-9-go-no-go-decision/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:58603:\"<p>In this episode, Birgit Pauli-Haack and Grzegorz Ziółkowski discuss WordPress 5.9 Go/No-Go Decision, Gutenberg Releases 11.6 and 11.7, and ongoing discussions about Themes and Styles for the Editor.</p>\n\n\n\n<ul><li>Music:&nbsp;<a href=\"https://soundcloud.com/xirclebox\">Homer Gaines</a></li><li>Editor:&nbsp;<a href=\"https://www.linkedin.com/in/sandy-reed/\">Sandy Reed</a></li><li>Logo:&nbsp;<a href=\"https://markuraine.com/\">Mark Uraine</a></li><li>Production:&nbsp;<a href=\"https://paulisystems.net/wordpress-consulting\">Pauli Systems</a></li></ul>\n\n\n\n<p><a href=\"https://gutenbergtimes.com/podcast/changelog-53-wordpress-5-9-go-no-go-decision#shownotes\">Show Notes </a>/ <a href=\"https://gutenbergtimes.com/podcast/changelog-53-wordpress-5-9-go-no-go-decision#transcript\">Transcript</a></p>\n\n\n\n<span id=\"more-19322\"></span>\n\n\n\n<p><strong>Subscribe to the&nbsp;<a href=\"https://gutenbergtimes.com/podcast/\">Gutenberg Changelog</a>&nbsp;podcast via your favorite podcast apps!</strong><br />🎙️&nbsp;<a href=\"https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe\">Spotify</a>&nbsp;|&nbsp;<a href=\"https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0\">Google</a>&nbsp;|&nbsp;<a href=\"https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475\">iTunes</a>&nbsp;|&nbsp;<a href=\"https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf\">PocketCasts</a>&nbsp;|&nbsp;<a href=\"https://www.stitcher.com/show/gutenberg-changelog\">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href=\"https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast\">Pod Bean</a>&nbsp;|&nbsp;<a href=\"https://castbox.fm/channel/Gutenberg-Changelog-id2173375\">CastBox</a>&nbsp;|&nbsp;<a href=\"https://www.podchaser.com/podcasts/gutenberg-changelog-878239/\">Podchaser</a>&nbsp;|&nbsp;<a href=\"https://gutenbergtimes.com/feed/podcast\">RSS Feed</a>&nbsp;</p>\n\n\n\n<p class=\"has-large-font-size\" id=\"shownotes\"><strong>Show Notes </strong></p>\n\n\n\n<h2>Announcements</h2>\n\n\n\n<ul><li><a href=\"https://app.mypodcastreviews.com/podcasts/k7H9zO/reviews/7420388\">Review by Jorge Calle, Ecuador</a></li><li><a href=\"https://us02web.zoom.us/webinar/register/3416344753630/WN_v-EXlrFaRcabGz78jgj8CA\">Oct 28, 2021 &#8211; noon EDT / 16:00 UTC </a><br />Live Q &amp; A: Case Study: Converting Classic Widgets to Blocks for BuddyPress</li><li>Video: <a href=\"https://www.youtube.com/watch?v=-PZwfvtkQOM\">How can we make building blocks easier?</a> w/ Helen Hou-Sandí, Mark Jauquith and Riad Benguella</li><li><a href=\"https://helen.blog/2021/08/exploring-custom-blocks-from-a-php-centric-developer-ux-point-of-view/\">Exploring custom blocks from a PHP-centric developer UX point of view</a></li><li>Video:&nbsp;<a href=\"https://www.youtube.com/watch?v=eiIhJdFfamA&t=9s\">Going from Classic to block-based Themes</a> w/ Ellen Bauer, Carolina Nymark and Anders Noren</li></ul>\n\n\n\n<h3>WordPress 5.9 Updates</h3>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/core/2021/10/15/wordpress-5-9-feature-go-no-go-october-14-2021/\">WordPress 5.9 Go/No-Go Decision October 14, 2021</a> (Make Core)</li><li><a href=\"https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/\">WordPress 5.9 Planning Roundup</a> (Make Core)</li><li><a href=\"https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/\">Preliminary Road to 5.9</a> (Make Core)</li><li><a href=\"https://github.com/WordPress/gutenberg/issues/35662\">Series of bugs and shortcomings faced during 5.9 go/no go prep</a> (GitHub)</li><li><a href=\"https://github.com/WordPress/gutenberg/projects/62\">WordPress 5.9 Must-Haves Project</a> (GitHub)</li><li><a href=\"https://make.wordpress.org/core/2021/10/15/summary-navigation-editor-and-block-hallway-hangout/\">Summary: Navigation Editor and Block hallway hangout</a></li></ul>\n\n\n\n<h3>WordCamp US</h3>\n\n\n\n<ul><li><a href=\"https://www.youtube.com/watch?v=_6-yAZRXY8k&t=6725s\">Building Modern WordPress Sites: The Interplay of Blocks, Patterns &amp; Theme.json</a> – Rich Tabor from Extendify</li><li><a href=\"https://www.youtube.com/watch?v=_6-yAZRXY8k&t=19298s\">A Voice for the New White House Administration with the Block Editor</a> – Helen Hou-Sandi from 10up</li><li><a href=\"https://www.youtube.com/watch?v=_6-yAZRXY8k&t=23716s\">Creative Use of Block Styles</a> – Kjell Reigstad from Automattic</li><li><a href=\"https://www.youtube.com/watch?v=_6-yAZRXY8k&t=2234s\">Demystifying Gutenberg Blocks – Understanding First Steps to Becoming a Gutenberg Developer</a> &#8211; Cory Webb, software engineer at Fast</li></ul>\n\n\n\n<h2>Community Contributions</h2>\n\n\n\n<ul><li><a href=\"https://wpblockpatterns.com/\">WPBlockPatterns.com</a></li><li><a href=\"https://wordpress.org/plugins/blockeditor-fullscreen-mode-control/\">Persistent Block Editor Settings plugin</a></li></ul>\n\n\n\n<h2>What&#8217;s Released</h2>\n\n\n\n<h3>Gutenberg 11.6</h3>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/core/2021/10/01/whats-new-in-gutenberg-11-6-29-september/\">What’s new in Gutenberg 11.6 (29 September)</a> (Make Core)</li><li><a href=\"https://wptavern.com/gutenberg-11-6-improves-the-global-styles-ui-adds-child-theme-support\">Gutenberg 11.6 Improves the Global Styles UI, Adds Child Theme Support</a> (WPTavern)</li><li><a href=\"https://wptavern.com/gutenberg-11-6-introduces-new-api-for-locking-blocks\">Gutenberg 11.6 Introduces New API for Locking Blocks</a> (WPTavern)</li></ul>\n\n\n\n<h3>Gutenberg 11.7</h3>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/core/2021/10/14/whats-new-in-gutenberg-11-7-october-13th/\">What’s new in Gutenberg 11.7 (October 13th)</a></li><li><a href=\"https://wptavern.com/gutenberg-11-7-iterates-on-global-styles-improves-adding-navigation-links-and-adds-column-spacing\">Gutenberg 11.7 Iterates on Global Styles, Improves Adding Navigation Links, and Adds Column Spacing</a></li></ul>\n\n\n\n<h2>What’s in active development or discussed</h2>\n\n\n\n<p><strong>Gallery Block Refactor</strong> <a href=\"https://make.wordpress.org/core/2021/08/20/gallery-block-refactor-dev-note/\">Dev note by Glen Davies</a></p>\n\n\n\n<h3>FSE Q &amp; A &#8211; Submit your questions!</h3>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/core/2021/10/13/submit-full-site-editing-questions-by-oct-27th/\">Submit Full Site Editing questions by Oct 27th</a></li><li><a href=\"https://make.wordpress.org/test/2021/05/13/fse-program-answers-from-round-two-of-questions/\">FSE Program: Answers from Round Two of Questions</a></li><li><a href=\"https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-general-functionality/\">FSE Program: Answers about general functionality</a></li></ul>\n\n\n\n<h3>FSE Theme Switching </h3>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/\">FSE Program Block Theme Switching Summary</a></li><li><a href=\"https://make.wordpress.org/design/2021/10/08/adventures-in-block-theme-switching/\">Adventures in Block Theme Switching</a></li></ul>\n\n\n\n<p class=\"has-large-font-size\">Stay in Touch</p>\n\n\n\n<div class=\"wp-container-6172d8672d2e1 wp-block-group\"><div class=\"wp-block-group__inner-container\">\n<ul><li>Did you like this episode? <a href=\"https://lovethepodcast.com/gutenbergchangelog\"><strong>Please write us a review </strong></a></li><li>Ping us on Twitter or send DMs with questions. <a href=\"https://twitter.com/gziolo\">@gziolo </a>and <a href=\"https://twitter.com/bph\">@bph</a>.</li><li><em>If you have questions or suggestions, or news you want us to include, send them to <a href=\"mailto:changelog@gutenbergtimes.com\">changelog@gutenbergtimes.com</a>. </em></li><li><em>Please write us a review on iTunes! <a href=\"https://gutenbergtimes.com/itunes/\">(Click here to learn how)</a></em></li></ul>\n</div></div>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Hello, and welcome to our 53rd episode of the Gutenberg Changelog podcast recorded on October 15th, 2021. In today&#8217;s episode we will talk about so much, WordPress 5.9 go/no go decision, Gutenberg releases 11.6 and 11.7 and ongoing discussions on themes and styles and editors and everything.&nbsp;</p>\n\n\n\n<p>I am Birgit Pauli-Haack, curator at the Gutenberg Times and WordPress developer advocate, sponsored by Automattic. I&#8217;m here with my co-host, Grzegorz Ziółkowski, code wrangler at Automattic and WordPress core contributor. How are you, Grzegorz? How are you doing?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I&#8217;m great. I had a blast during my vacation. I want to tell you more about it, but we have so much to cover today that there isn&#8217;t much time for chit-chat. How have you been lately, Birgit?</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Well, I had a blast running live Q&amp;As this week and last week and the week after next and talking to developers and users. You&#8217;re right, let&#8217;s catch up after the show and let&#8217;s get this started.</p>\n\n\n\n<p><em>Grzegorz Ziolkowsk</em>i: Yay. Before we start we want to thank you, Jorge Calle user name, AtrumGeost from Ecuador for his five-star review.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yay.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Hooray. We are so thrilled to have you as our listener. Jorge wrote, “the best all-the-things Gutenberg podcast. This is my favorite Gutenberg and WP-related podcast. It helps me keep up-to-date with all the new and upcoming changes and to understand the reason behind those changes.”</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: That&#8217;s so nice. That&#8217;s exactly what we&#8217;re trying to do. Thank you, Jorge. Greetings to Ecuador.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, we could put that as our mission. Yes, greetings.</p>\n\n\n\n<h3><strong>Announcements</strong></h3>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yes. All right, we have a few announcements because it&#8217;s been a while. The next live Q&amp;A, put this on your calendar, is a discussion with the BuddyPress team on how they converted classic widgets into blocks. We learn what was hard and got easier over the first two times I did it. Join us on October 28th at noon Eastern, 1600 UTC with Mathieu Viet, David Cavins and Varun Dubey on the live Q&amp;A show. It&#8217;s going to be really, really interesting, especially for developers who still are a little bit on the edge to jump into Gutenberg development, also theme developers who have widgets in their themes. It&#8217;s definitely going to be educational because we will have some demos.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, I guess it should be also useful for the developers who have plug-ins and they still waited to convert them to blocks because it&#8217;s all about that, right?</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Right, right. Everything needs to be a block now. It&#8217;s just so much better for the users to use them because everything&#8217;s just one concept, they don&#8217;t have to do the mystery meet with what are widgets, what are menus, what are sidebar and all this kind of thing. Yeah, speaking of live Q&amp;As, yesterday I had the privilege to host a discussion among WordPress giants, Mark Jaquith, core committer for 17 years, Helen Hou-Sandi working on WordPress for 10 years and Riad Benguella who is the newbie in that regard.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: A rookie.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: He&#8217;s already working on Gutenberg for even five or even seven years, so &#8230;</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Five. Five.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Five years. They discussed how can we make building blocks easier. It was a follow up on a Twitter thread Mark started with a question, what if building custom blocks for the block editor was as easy as supplying attributes and a block of HTML? What if this produced react editing code and PHP rendering code without a build stack? Coincidentally enough, he and Riad independently of each other were exploring some technical avenues for that and Helen was too. Grzegorz, you know more about the technical framework and underpinnings of Gutenberg, what was your take from the discussion yesterday?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I was really excited to see this discussion happening in the forum where people have more time to express their ideas, where they come from, what&#8217;s their use case and how they arrived at similar conclusions which is the best part of that. All three people, they were working on different aspects. Riad is working only on core, mostly on core and Helen is doing work for customers, same as Mark. Basically different venues came to the same conclusions. It&#8217;s really nice that we have good understanding where it should all go now. Those ideas that they both shared are pretty decent and I guess this is something that should be materialized in the future. That should greatly benefit all the developers that increase blocks on a daily basis. It was really cool and I encourage everyone who is doing block development to catch up with this discussion.&nbsp;</p>\n\n\n\n<p>Also check the references they mentioned. One is from Riad, it&#8217;s on his GitHub, it&#8217;s called Block, we will provide links. Mark, he also has the same idea, I believe it&#8217;s called Blocksta, the code name. Yeah, that&#8217;s really insightful from my perspective. I learned a lot, especially about the background, all the friction people have and the pain points. It&#8217;s something that, as a core team member, I heard a lot about that, but it was more on the side of showing what&#8217;s wrong and not necessarily what are the challenges people have on a daily basis that end up with all the frustration they share, which is very limited, especially on Twitter which is a few characters.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah, yeah. I also like that both Mark and Helen expressed and emphasized that the ideas that they had on how to do some templating and all that would not have been possible from the beginning because you need some underpinnings already working and some expansion of the API. Mark mentioned the block API version two where PHP and JavaScript have the same information about blocks, that was necessary to actually even think about any of the additional helper function, tool function for block editing and block writing or building. They also expressed that it shouldn&#8217;t, it&#8217;s not necessarily something that needs to be in core, but it could be one of the official tool building for plug-in developers. Yeah, it was a really good discussion. I will also share in the show notes Helen Hou-Sandi&#8217;s blog post called exploring custom blocks from a PHP-centric developer UX point of view where she even more elaborated on where she was coming from from the agency work there.</p>\n\n\n\n<h3><strong>WordPress 5.9 Go/No Go Decision</strong></h3>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, definitely. I could continue on this topic for long, but let&#8217;s go to the most important announcement of the day which is the go/no go decisions. The meeting happened yesterday. The official post isn&#8217;t ready yet. Yesterday will be October 14. We spoke with Matias and Hector Pietro who attended the meeting. It looks like all the features discussed during this session should be included in the WordPress 5.9 release which means that block themes will be supported as an option with how they call it, a remark that there will be something like early access or something along those lines just to build proper expectations for users. At the same time it&#8217;s worth to mention that the new Twenty Twenty-Two theme built out of the blocks will ship with WordPress. Therefore, the default experience with themes for all new websites will start with blocks. I think it&#8217;s huge and super exciting to see it happening finally. They took so much time, but there is more. Do you want to say something about that?</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Well, I just wanted to notice that the theme Twenty Twenty-Two was actually introduced last week by Kjell Reigstad and he&#8217;s working with Jeff Ong on it. We will share, of course, the link in the show notes, but if you want to check it out it&#8217;s on the design, actually on the core make blog, very buried but it&#8217;s beautiful. He also has some ways how he can change the theme.json and then make the theme a total different look than what he&#8217;s originally planned there. It&#8217;s really nice. You had more to say about the go/no go from Matías Ventura?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. No, you sidetracked my brain now for the Twenty Twenty-Two theme. It&#8217;s really beautiful. I really admire the work done with that, especially because it was very challenging on the technical level. We had to build all the blocks to make that happen but the outcome is really good.&nbsp;</p>\n\n\n\n<p>I also would like to bring to your attention the issue that was created today by Matías which contains a series of bugs and shortcomings that he faced during preparation for this 5.9 go/no go decisions meeting. We will share a link to the issue which has the number 35662. It only confirms that there aren&#8217;t any significant bugs that put too much risk on the roll-out plan, however it will be essential to sort out those minor issues because they might negatively impact the first user impression. One more thing to mention is that you all will be able to watch the progress of the release execution in the traditional way which is through the issue, through the project board which is Gutenberg and the name is WordPress 5.9 must-haves. The project number is 62.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. Thank you for the summary there. There&#8217;s actually a video that you can, it was a one-hour meeting and they recorded it, it&#8217;s available on WordPress.TV. I wanted to go still for those who &#8230; the plan, the schedule of the release. Feature freeze will be November 9th, that&#8217;s 42 days after go/no go. From today on it&#8217;s 41 days.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Or even 40 because the meeting was postponed by one day.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Oh right. Right, right. It&#8217;s actually 39. Beta one will be released or is scheduled to be released November 16th and then the release candidate one is scheduled to be released on November 30th. The final release is scheduled for December 14th, 2021 and will have, from the Gutenberg plug-in releases, the latest one will be 11.9, all the versions from 11, or 10.8, or 11.0 I think to 11.9, release candidate. 11.8 will still be a normal release on Gutenberg plug-in and then 11.9, the release candidate, the features that are in there will be then merged with core and then bug fixing starts.&nbsp;</p>\n\n\n\n<p>I just also want to mention that before the go/no go meeting the group working on the navigation block and editor screen, navigation editor screen held a hallway hangout so to speak. Among other things they concluded that the navigation editor screen itself is not ready for 5.9. Only the navigation block and the block for new navigation and I think it has some &#8230; I don&#8217;t think it has a feature for existing menus, so we need to see about that, the main reason why they won&#8217;t solve the underlying backwards compatibility issues successfully before the release. A menu is a major part of a website. There are a myriad of third-party products tapping into the current features and they all need to be accommodated in one way or another.&nbsp;</p>\n\n\n\n<p>There is a summary post about that on the core blog, we&#8217;ll share the links of course and there&#8217;s also a video where you can also follow along on the meeting. We will share all the relevant links for the 5.9 at the current stage in our show notes, that&#8217;s a summary post of the meeting, Matías&#8217;s roadmap, Josepha&#8217;s planning post and then the meeting recording as well as the summary post by Hector Pietro. That&#8217;s about that.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. Just to summarize, the navigation block is going to be included, right? It&#8217;s crucial to have it for the block themes.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yes. Yes, but they were still trying to figure out if they need a second block for the backwards compatibility or they want to put it all in one block. They concluded now that they don&#8217;t want to burden the new feature, the new navigation block with the legacy part from 18 years of WordPress development so they are working on a second block that is the compatibility, that handles the compatibility issues. Also, some of the plug-ins actually tap into the navigation editor screen as well and the customizer so there are so many different branches of what to think about that they said, okay, we need to take a step back and see that we&#8217;re not making the same mistake that happened with the widget editor where they weren&#8217;t having enough tests with the third-party plug-ins to get this out.</p>\n\n\n\n<p>Yeah, that&#8217;s about the release. I&#8217;m totally excited about it, especially because of the block theme with the full site editing. We will have some new or old terms. I think we were always talking about the block-based theme, it&#8217;s now called block theme. We were talking about the site editor, or template editor, now it&#8217;s the editor. We were talking about the global styles, they&#8217;re just the styles because, yeah, that&#8217;s all there is. Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Everything gets simplified.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Simplicity is to aim for, yes.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Even the user experience that the blocks provide.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah, and….</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Okay. Let&#8217;s move to another point.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Move on. Yeah.</p>\n\n\n\n<h3><strong>WordCamp US 2021</strong></h3>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. WordCamp US, I didn&#8217;t watch it live, I watched some talks afterwards. How about you, Birgit?</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: I watched it live. I took the day off from other work so I could really concentrate on that. My favorite talks were, I couldn&#8217;t decide on the favorite so I have three favorite talks. One was from Rich Tabor from Extendify, his talk was building modern WordPress sites, the interplay of blocks, pattern and theme.json. That&#8217;s definitely a very good presentation to watch, not only because all his slides were so beautiful and his voice was so soothing, we were all very relaxed about all the new things that come to WordPress, but he also made very clear how all these things work together.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I saw also that some people were confused whether it&#8217;s an advertisement for WordPress or is it an actual talk.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Then the other one was a voice for the new White House Administration with the block editor by Helen Hou-Sandi. It was an hour-long presentation but it had a few different parts in there. One was making clear the advantages between a form-based content collection screen to the what-you-see-is-what-you-get editor and how they accomplish that. They actually built custom blocks, they did that for the experience. Then Helen, in the second part of it she also went in and explained why native blocks, Gutenberg blocks are so important. Then went on to actually show how she coded one of them and made the difference between the different, showed the difference between the approaches that they were exploring and where they finally settled. She has actually some code examples in there and she walked us through her set-up. That was really good. There was a lot of things packed in there, but it was one whole presentation.</p>\n\n\n\n<p>Then the last one was Kjell Reigstad who showed us creative uses of block styles. Block styles is something that you use the core block, but you add additional CSS to it. That&#8217;s pretty much what block styles are. He showed how to do this, he also shared his repository, but he did all kinds of different graphical and animation. It was just beautiful to see what is all possible with just using block styles. You don&#8217;t have to do a whole lot of programming from that, at least not in JavaScript or in PHP, you need to do a lot of CSS for that. A lot of designers know that part and I think it&#8217;s a good starting point to get your creative juices going. Yeah, how about you? What did you watch on the rerun?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I watched all the talks you mentioned so you took my picks. Anyway, I have one more to share, the one from Cory Webb, software engineer at Fast. He had a talk named the demystifying Gutenberg blocks, understanding first steps to becoming a Gutenberg developer. I really liked the talk because it was structured in a very nice way. It covered all the APIs, basic APIs you need to know to start with blocks, but he also added a section where it was nice to know and there&#8217;s some additional going further if you want to extend your knowledge base and there are some other topics. That&#8217;s a good way of approaching that and it will be super beneficial for anyone who either already started working with blocks or they want to start because it covers all the levels when you want to become a master going from the beginner and scaling your knowledge. I liked that about this talk.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. If you watched that you have all the pieces that you need to go from beginner to experienced. That&#8217;s also a part of my talk that will be shown at the Page Builder Summit that starts on Monday from Nathan Wrigley and Ann le Roux. There are a lot of talks there on the professional use of page builders in all areas. Ann is doing her full site editing talk and I&#8217;m going to talk about how to customize blocks for client projects. If you missed it, last week was also a theme developer live Q&amp;A. Ellen Bauer, Anders Norén and Carolina Nymark were on the show. Anders showed his block theme, Tove, and Ellen Bauer showed her studios theme, Aino, as a hybrid theme. I loved their excitement about the new possibilities of themes and blocks and full-site editing. They also shared how they made the journey from building classic themes to going block themes now. They also answered a ton of questions from the audience. The recording is available on YouTube and we will try and post a transcript and resources on the Gutenberg Times next week.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I started listening to this live Q&amp;A as well, it was pretty good, but I was driving so I couldn&#8217;t show the demo so I stopped. I didn&#8217;t have to time to go back, but I definitely have to. One thing that caught my attention was that Anders mentioned that one of the users of his team, he applied a lot of modification using styles and similar things. He sent a link to show the end effect. Anders said that he didn&#8217;t recognize this theme, he couldn&#8217;t say it was his. That&#8217;s a great thing about the future of building themes, the user will be so much empowered to achieve their goals.</p>\n\n\n\n<h3><strong>Community Contributions</strong></h3>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Right. Yes. Yeah. Speaking about themes, there is a new site out there called wpblockpatterns.com. It&#8217;s a place where you can find out how your block patterns or the block patterns in the directory look with any of the block themes that are in the repository. I did a few tests and I&#8217;m delighted to see that block patterns will persist even when you switch the theme on your site, so something that&#8217;s very hard to do with third party page builders but that&#8217;s also very hard to do with classic themes where you sometimes lose content just because you switch themes. Now with block patterns that&#8217;s a much better build and they all persist, including the design, when you switch the theme. It&#8217;s really interesting to see. Speaking of block pattern, there&#8217;s a small change in the pattern directory. The meta team has added now a featured category so the best patterns you can look up in the featured category. You can also select them from the inserter inside of the editor.</p>\n\n\n\n<p>Another community contribution came from Marius Jensen. He updated his plug-in called persistent block editor settings. He added support for the following user settings, block breadcrumbs, that&#8217;s the breadcrumbs on the bottom of a screen, on and off, change the most used blocks to what the user actually is doing and the caret positioning. Then all the settings are stored in the individual user profile information on the site so that persists between computer or browser changes. I think it&#8217;s a great plug-in and many, many people have asked for that. It has quite a following on the WordPress repository. I also think that sooner or later, I know that the core team is working on something like that, but it&#8217;s still blocked by some of the not finished things I would say. Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yes. It&#8217;s in progress for so long. There were several approaches that tried to address that. Maybe it&#8217;s good that it didn&#8217;t happen before because now we will have several screens for the editor and that brings another level of complexity. Still, the way it&#8217;s structured, even in the local storage of the browser, so it persists per browser at the moment, it&#8217;s still something that might change slightly at the time of the WordPress 5.9 release. Starting from that, I guess it&#8217;s a very good moment to finally bring the same functionality to core.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. Yeah. You mentioned this, I was just &#8230; you were distracting me because I was counting the different editor screens that we have now and it&#8217;s quite a few. It&#8217;s a post editor, it&#8217;s a widget screen, it&#8217;s a template editor, it&#8217;s a template parts editor, it&#8217;s the reusable block editor. It&#8217;s really interesting.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, that&#8217;s a lot. I mean some of them are the same editors behind the scenes, but conceptually they are different. Now, as we will cover soon, we also have this zoom mode so you can switch in the editor as it will be called from now on from a full template view to the template part view, so that&#8217;s yet another way of looking at that.</p>\n\n\n\n<h3><strong>What’s Released &#8211; Gutenberg 11.6</strong></h3>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. Well finally, half an hour into the show, we are at the releases. Gutenberg 11.6 was released on September 29th. The WP Tavern covered some of it and of course some of it is also in the &#8230; oh, the WP Tavern actually had two posts about it. One is about the release as a whole and the other one was introducing the new API for locking blocks. I think that was one of the major features there. Let&#8217;s go through that.&nbsp;</p>\n\n\n\n<h3><strong>Enhancements</strong></h3>\n\n\n\n<p>We start with the query pagination now can use the flex layout which is really cool. The site logo now has the feature to crop the image. If your logo that you uploaded is not fitting in the spot you can crop it. Now it&#8217;s also possible to zoom and rotate the image, so that is really a step forward.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: There is this item for gallery block which is at toolbar bottom to convert old galleries to new format. I&#8217;m not quite sure it&#8217;s something that will stay for longer, or is it something for the transition period, but it&#8217;s great that this is now possible because it will help with the ongoing efforts to bring inner blocks for the gallery.</p>\n\n\n\n<p><em>Birgit Pauii-Haack:</em> The gallery block has experienced a refactor, instead of just having the IDs of the images in there and then rendering them it actually comprises now of single image blocks that you can add all the different features that you have with the image block also to the single image in a gallery block. You have then the gallery outer and then the inner blocks are image blocks. The roll-out is, in that regard it will not automatically convert the old to the new galleries until it&#8217;s rolled out and until it&#8217;s coming to core because right now it&#8217;s still an experiment. You can switch that over to the new gallery. It&#8217;s called update, the button in your gallery toolbar and then you can convert it to the new format. I think in the final roll-out, when you open up the post it will automatically convert it, but not with all the previous. It will not touch that unless you really wanted or unless you edit that particular post. Yeah.&nbsp;</p>\n\n\n\n<p>Then the color picker got changed and is rolled out, it&#8217;s more accessible and it also has a copy function and all that. It also makes the rounds now, we saw it in 11.6 as well as in 11.7, that&#8217;s gradually exchanged on all the blocks. Do you know anything else about the color picker?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: No, I know that there is a big redesign happening. I don&#8217;t know why, but there&#8217;s always a reason.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. I think it was accessibility problems that the old color picker had.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Oh. Maybe, as far as I remember that was something that was worked on before, WordPress 5.0, which was a long time ago. I&#8217;m sure it was accessible enough to get through to the release then. Maybe there was some concerns that are addressed now.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Now there is a simple styles preview in the sidebar of the template editor or site editor that you can modify some of the styles in your panel and it also now uses a navigation component. That&#8217;s just the underlying feature for the global styles preview.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. For the preview you see some characters and it shows the typography, how it looks in practice and also the colors that are applied to that. It just gives you a slight preview so you don&#8217;t have to navigate through the page and look for that. It&#8217;s pretty useful in my opinion.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. You see the final version of it right now in the video from last night&#8217;s meeting of the go/no go when Matias Ventura was demoing it. It&#8217;s a nice &#8230; also with additional color palettes. It has received quite a few iterations since it got added to the plug-in. Full site editing, there is now basic support, the executive word is basic support for child themes when you have a block theme so you can have different features added or switched on and off in your child theme that maybe the parent theme doesn&#8217;t allow. You have different color settings and any settings that you want to you can do in your theme.json for the child theme and still get updates for your parent theme.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. The feature that I mentioned a few minutes before is a way to edit template parts in a special view. When you are editing your template you can use this dropdown menu which is an icon with three dots. There is this new option, edit template part. When you click that, everything disappears but the template part and you can focus on editing only that area, which is pretty handy. In the context when there is a lot of blocks sometimes it&#8217;s hard to see when the template part starts or ends. I like this addition.</p>\n\n\n\n<h3><strong>APIs</strong></h3>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. Yeah. Then we come to the lock control for block type level. As we mentioned there&#8217;s an article that covers that as a whole at the WP Tavern. At the attribute level it supports locking the block from being moved or removed and it hides the block moving errors and the delete button if the block is locked. You can use that also with your &#8230; it&#8217;s just an attribute in the block.json if I see this correctly. You can also use that for your block patterns. That can have locked and unlocked blocks. That&#8217;s-</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Oh yeah. That&#8217;s true. That would be a good use case, yes.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. That&#8217;s also something that Matias demonstrated yesterday, last night in the video. What else do we want to point out from the 11.6? Bug fixes, well we&#8217;re going to jump over the bug fixes.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I think you had something highlighted for the site editor.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah, the experiments. The experiments, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Basic plug-in support.</p>\n\n\n\n<h3><strong>Experiments</strong></h3>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. Sorry. The site editor now has basic also, our executive word is basic plug-in support. It adds the support for the plug-in sidebar. The site editor is now the editor and that&#8217;s where you do the full site editing pieces. The sidebar there can now be targeted by plug-ins for the sidebar, for the menu items in the menu as well as close and open general sidebar action. Plug-in developers, extenders will really be happy to hear about that. We were waiting for that too.&nbsp;</p>\n\n\n\n<h3><strong>Documentation</strong></h3>\n\n\n\n<p>There was a big push for documentation updates, especially for the packages and the components. Developers can now look up some of the documentation and don&#8217;t have to figure out from code what does this do.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. I guess there were also some updates related to how to contribute to the WordPress components package. That&#8217;s the most important part that builds all the experience, all the UI elements and so on. There&#8217;s a lot of movement in that area which also shapes how global styles look. You can see a lot of changes in that area. That&#8217;s all because of these efforts.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. All right. Code quality, I think that was all &#8230; was that all that we wanted to say about 11.6 in this episode?</p>\n\n\n\n<h3><strong>Gutenberg 11.7 Release</strong></h3>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I guess we have a lot of cover also from 11.7 that was released on October 13th. It would be fair to say that we are done with the 11.6 release and just move to the next one because it was a huge one and there was a lot of enhancements included in this one, way more than the one we already covered.&nbsp;</p>\n\n\n\n<h3><strong>Enhancements</strong></h3>\n\n\n\n<p>Let me start with the changes to the block editor. With the work, ongoing work on the navigation block and all the child blocks there was a need to have a way to use also slash inserter in this content. So far you could do it only through the paragraph block, which was quite a big limitation. It is now fixed.&nbsp;</p>\n\n\n\n<p>It&#8217;s enabled to some of the links to the blocks that allow you to insert links and stuff like this. When you insert a link and it has some name, when you delete that name and write a slash then you will be able to insert a block, other types of blocks that fit in that context, which is pretty good. This is something that is still, the API behind that is still experimental. Every block author there can experiment with that by enabling the flag called underscore experimental slash inserter.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. I think what that also does is give you a little input screen from the slash inserter, not that you have to &#8230; up until now the slash inserter only added, gives you fast access to adding a block, but now you can actually add also some parameters to that and enter it right there. That&#8217;s a real speeding up the workflow quite tremendously. As you said, any block can have that so it&#8217;s also the plug-in, the blocks that come with plug-ins can also use that. That&#8217;s really good, immediately extender friendly.&nbsp;</p>\n\n\n\n<p>It also has added or enabled the ability to create pages directly from the inline link UI on the navigation bar. The new empty page gets created, that&#8217;s a feature that comes over from the other editor screen but I think I really like how they implemented that, the new empty page gets created behind the scenes with a title set on the text typed in the search input field. That&#8217;s definitely also a fast way to create a menu when you know you have the outline of your website and you just create the menu headers and then it automatically creates all the pages for it as well. That&#8217;s really cool.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. At the end of the process of creating your navigation you just go to those pages and fill it with content, which is pretty nice. It should speed up the whole process really.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Exactly. Yeah. In 11.6 came the site logo cropping and image manipulating features, now you also get, with 11.7 you also get duotone support which means that you can have a fixed color scheme around your website. Every image that you have might fit better into it. Really that&#8217;s a cool thing.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yes. Exactly. There&#8217;s more for the columns block, they enabled the block gap feature which we covered in past episodes. When it&#8217;s combined with vertical margin support you can have a really nice effect, so finally you can add some spaces between columns and there is a control for that which allows that and some nice animations that support that. It&#8217;s a very nice way that was missing for so long. Now it&#8217;s finally implemented.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. If you&#8217;re a theme developer who has actually taken out the gap between the columns, you can now, it can now be done through the interface. I saw some nice animations or demos where you have three columns that are a different color but they don&#8217;t have a boundary so they go from one color to the next without the background color of the site shining through which is quite a nice effect when you just want to liven up the text, the wall of text when you&#8217;re writing so much and just have some graphical play around with it interspersed there.&nbsp;</p>\n\n\n\n<p>The navigation, oh yeah, from the navigation block you can now transform your link into other allowed navigation blocks. You can transform it into a sub-menu, menu or a site logo or a home link or a social icon, which is cool if you change your mind on some of the links.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. I&#8217;m not quite sure what happened with the content. For instance, if you have a site logo and you want to transform it into something else, which probably will have a different URL, it might be it uses just the same URL and then you just need to edit that. Anyways, it&#8217;s a really interesting idea to speed up the process.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Well this one is actually only going from a link to something else, not the other way around.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Oh, is it?</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> The initial idea that I always, that stuck in my mind, all the transforms should be two ways. If you convert from something you are able to convert that back. Maybe it&#8217;s now relaxed, you can always use an undo button and that should be pretty much it. I guess it&#8217;s whatever makes it easier for the user is fine from my perspective.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah, I think I need to press that for this if there is a way going back, just from a social icon link to just a mere menu link. Maybe it&#8217;s a different context here. Yeah. Now you can actually &#8230; there was a problem when you have these.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Just to explain that, why the rule was like that, when you are transforming from the heading to the paragraph then you use the same content and it&#8217;s pretty straightforward. However, if you would like to go from the image to cover block then you have only the image, but as soon as you add some heading or something like that in the cover image, when you go back to the image block then it isn&#8217;t quite sure what should happen with this heading. You could lose some content.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. Yeah. No, I get it. Yeah. I&#8217;ve only been situational, but I&#8217;ve never had a situation that I have already a cover block and only want to go back to an image. I think that&#8217;s just a lack of imagination I guess.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Also, when you&#8217;ve invested so much time to polish your cover block and make it pretty, it doesn&#8217;t make any sense to go back to the image.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. That&#8217;s so true. Yes, yeah. The next item on our list is show none as an alignment option and use contextual text to clarify the settings. There are now hints included in the alignment options, spread text maximum wide, 720 pixels wide or something like that. It explains a little bit to the user what does it mean when you change something to align wide or to full width. Some users had trouble to see, I&#8217;m one of those, to see that you can uncheck those alignments and then remove it. Now there is and option that says no alignment, just do what you normally do as a block, don&#8217;t make it wider or go out of the content. I think that&#8217;s a good addition there because I got totally and utterly confused. Oh, I can switch it just off. It was not a good.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, you had to click on the same option again to disable it, which wasn&#8217;t so straightforward.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: It wasn&#8217;t clear. That&#8217;s a toggle switch, that wasn&#8217;t clear. Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I wanted to emphasize that the number you mentioned is not something that is hard colored, it depends on the theme. It is able to, the context there provides very useful information which can vary between themes, right?</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Is that coming from the theme.json file do you know?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: They probably compute it on the fly using some JavaScript.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Okay. Yeah. All right. That&#8217;s great, but we&#8217;re not done yet. What&#8217;s the next thing?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Format library.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: This is one of the options you have when you have text based blocks. Before it was only possible to change the foreground color of your text, so change it to something different. Now there is also an option to change the background color or the highlight how it&#8217;s called in other tools. The change was applied to the existing controls so now you have a pop up dialogue, I don&#8217;t know, which has tabs so you can switch between text and background and apply those different colors.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: I think that&#8217;s a feature that has been missing from the beginning for a very long time. There was something that you could do in the classic editor very easily with the little toolbars up there that you can just highlight a word in your text within the paragraph and then give it a different text color or give it a different background color. The text color was still there, is already there, but now you can change the background color of that. Yeah. You find it at the same place where you also find the text color change in your paragraph toolbar. You can now, as a theme developer you can now also set presets on the duotone for your theme. If you say every duotone, when it comes out of default, should be a blue filter or a pink filter or something like that, you can help your user to set the right duotone on certain images in the content.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. You can change it per block, so that&#8217;s pretty nice. You can say, oh, site logo, I want to have it in a red filter and that&#8217;s also possible now.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. The possibilities become endless.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. In general all the management for colors becomes so complex that now it got extracted, the color palette is in its own global styles screen. Basically you need to, when you go to the editor for editing, for changing your site, when you go to the styles sidebar, now you need to first click on the color link and then it will show all the colors you have. You can also drill down to the palette or individual elements to change those settings.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: As the next iteration, probably not for 5.9 because it takes a little more, but one of the features that will come is that you can, in that you can also have multiple color palettes to choose from or have a color palette directory where you can grab a wonderful &#8230; yeah, Matt Mullenweg actually mentioned that in yesterday&#8217;s video that there is a colorpalette.com site where you can pick the color palette that you like and then you get all the hex decimal values for it for your site. That would be so cool to actually have a source like that that can pull in new color palettes for your theme there or for your site. Yeah, this has opened so many possibilities, it&#8217;s really mind-boggling. Right now we just have these three screens, all the styles, the color styles and then the color palette separate where you can add additional colors to it.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. It&#8217;s really hard to wrap your head around how colors work at the moment. If I am correct, now you have the default colors that come from the WordPress core, then you have theme styles that every theme can provide and it looks like you can also, the users can define their own colors right now.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. The hierarchy is users first, then the theme, then the core, but it&#8217;s also that the theme can say please disable custom colors, my users don&#8217;t know how to use color.&nbsp;</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yes.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: To offset or to avoid the GeoSitters interesting page designs.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> To make it even more advanced, it&#8217;s also possible to say that, a theme author can say that for this particular block I want to have a different color palette.</p>\n\n\n\n<p><em>Birgit Pauii-Haac</em>k: Yeah, yeah, yeah. There&#8217;s also something new and I didn&#8217;t realize that until now when I see the screenshot that I was looking at here from the post. In the styles there was, up until 11.6, with the new version now you can actually go directly to the blocks to change their settings. Before you had to close the sidebar from the style, from the global styles and go back to &#8230; when you do template editing you have to go back to the blocks sidebar. There wasn&#8217;t a clear path for that. Now you can, I see here blocks is another panel that you can open there. That&#8217;s really cool.</p>\n\n\n\n<p>All right, next thing, the template editor got some new workflow things. There&#8217;s a back button now for the isolated template part editor. When you drill down you can go back up the rabbit hole again. Then also the template areas have added some template details like header and footer areas there. That&#8217;s really cool.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: When you go to the header and you click on the name of the template you are currently editing, you not only see the details about the theme template but also some details about template areas used in that template which allows you to quickly navigate to them because there are dropdown menus with additional options.</p>\n\n\n\n<h3><strong>Experiments</strong></h3>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Exactly. Yeah. Then the navigation screen still in experimental has a new feature that you can add tool tips to navigation items in their set-up states. That is interesting and helpful.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I guess it&#8217;s coming from the block editor. When there&#8217;s something wrong, the link is missing in your navigation where it should be, then it just underlines it with the squiggly line. When you hover over it it just shows you what the issue is.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. You don&#8217;t want to have in the menu a link or a menu item that doesn&#8217;t go anywhere. That helps you too. Then the next one is insert the navigation link blocks by default in the navigation block.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. Basically, when you click on the plus sign to add another item, you can start writing and it will show you a list of matching links. You can just click on one of them and that will add it to the menu. You don&#8217;t have to choose the type or you don&#8217;t, give me category page, no, we just type the name of the link and it just does everything behind the scenes.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. That&#8217;s a very nice feature because in the current menu screen you really have to know what kind of type you&#8217;re looking for. This goes away right away with that feature. I&#8217;ve got to test it, what happens with custom post types and post categories or are these pages also being surfaced. Yeah. Wow, that was a lot in this release. Do you have anything else? I think that was it, the major parts.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. We had to cover two Gutenberg plug-in releases pretty packed with features. I guess that&#8217;s a lot already to process for our listeners.</p>\n\n\n\n<h3><strong>What’s in Active Development or Discussed</strong></h3>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yeah. In one sitting, yes. Let&#8217;s go to the active development and what&#8217;s discussed. I wanted to highlight again the gallery block refactor will come out of the experimental stage with the next plug-in release, that&#8217;s 11.8, that&#8217;s in two weeks. It will be in 5.9, WordPress 5.9. At the moment we&#8217;re doing the extender outreach to plug-in and theme developers to alert them to the changes. If you are one of those and/or you work for agencies but you don&#8217;t have public plug-ins or themes in the repository, then I would suggest to go to the developer note that Clan has already published a month ago on the changes so you can see if that affects your gallery handling in your theme or your plug-in. We will have it in the show notes of course.&nbsp;</p>\n\n\n\n<p>Then on the FSE Outreach Program update Anne McCarthy has another call for questions where you click on a button and have your question and then it gets sent to her inbox and then she finds the answers for that and she will publish all the questions and answers in a post later on. The deadline for getting your question in is October 27th, that&#8217;s in two weeks. Then she will, within a week, publish that post. This is also for 5.9 when full-site editing comes in with early access there that you can get your questions answered, or also your fears, either way is fine.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I think we should also include a link to the previous installment and all the answers. I think there were about 50 questions answered. That was a lot. Maybe that would be also good to check. Maybe you already have answers for your questions and you don&#8217;t have to reach out again.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Right. Yeah. I think the reason that Anne does it now at this stage is because the last one was at the beginning of the year. With the, I don&#8217;t know, six or seven plug-in releases that happened since then, quite a few things have changed, some irritations that were &#8230; because it was annoying or it was an interface that didn&#8217;t make sense, you had questions there, but that has been already fixed so the new questions certainly also in regards to the go/no go decision, I would wait until the post is out, to read through it and get &#8230; some of the answers might be in that summary post from the go/no go meeting that Hector will publish.</p>\n\n\n\n<p>Then also from the FSE Outreach Program was the summary of the theme switching experience. It was a great read. There were quite a few theme developers who had some expectations there that also went through, some site owners went through the testing and had some surprises there. Channing Ritter on the design team did some nice mock-ups on how to make it a better experience. It might not be part of 5.9, but it&#8217;s definitely something that you who sent in or did the test have influenced how the next steps are going to work.</p>\n\n\n\n<p>With that, get your questions in, think about the gallery block refactor and then live Q&amp;A October 28th with the BuddyPress team members on converting classic widgets to blocks. This is the end of our show.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. I wanted to remind everyone that we are waiting for more reviews and that&#8217;s always great to hear from you what do you think about the show. You can also ping us on Twitter or send DMs with questions, with the feedback, whatever you&#8217;d like to talk about with us. My handle is GZIOLO and Birgit is BPH.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Yes. As always, the show notes will be published on <a href=\"http://gutenbergtimes.com/podcast\">GutenbergTimes.com/podcast</a>. If you have questions and suggestions you can also send them via email to <a href=\"mailto:changelog@gutenbergtimes.com\">changelog@gutenbergtimes.com</a>. That&#8217;s <a href=\"mailto:changelong@gutenbergtimes.com\">changelong@gutenbergtimes.com</a>. Well, it was good to see you. I&#8217;m glad you&#8217;re back from vacation and rested and ready to go. Thank you so much for being here and a big thank you for our listeners to stay with us so truthfully into another long episode. That&#8217;s it for me. Goodbye.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Thank you, Birgit. Thank you everyone for waiting four weeks for the next episode. See you in two weeks. We won&#8217;t do so long breaks for quite a while I hope. Goodbye.</p>\n\n\n\n<p><em>Birgit Pauii-Haack</em>: Goodbye.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 17 Oct 2021 13:37:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"Gutenberg Times: Changelog #52 -Planning, Scope and Team for WordPress 5.9, Roadmap for WooCommerce Blocks and Gutenberg 11.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/?post_type=podcast&p=19056\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://gutenbergtimes.com/podcast/changelog-52-wordpress-5-9/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:58350:\"<p>In this episode, Birgit Pauli-Haack and Grzegorz (Greg) Ziolkowski discuss Planning, Scope and Team for WordPress 5.9, Roadmap for WooCommerce Blocks, Gutenberg 11.5 Release and more&nbsp;</p>\n\n\n\n<ul><li>Music:&nbsp;<a href=\"https://soundcloud.com/xirclebox\">Homer Gaines</a></li><li>Editor:&nbsp;<a href=\"https://www.linkedin.com/in/sandy-reed/\">Sandy Reed</a></li><li>Logo:&nbsp;<a href=\"https://markuraine.com/\">Mark Uraine</a></li><li>Production:&nbsp;<a href=\"https://paulisystems.net/wordpress-consulting\">Pauli Systems</a></li></ul>\n\n\n\n<p><a href=\"https://gutenbergtimes.com/podcast/changelog-52-wordpress-5-9#shownotes\">Show Notes </a>/ <a href=\"https://gutenbergtimes.com/podcast/changelog-52-wordpress-5-9#transcript\">Transcript</a></p>\n\n\n\n<span id=\"more-19056\"></span>\n\n\n\n<p><strong>Subscribe to the&nbsp;<a href=\"https://gutenbergtimes.com/podcast/\">Gutenberg Changelog</a>&nbsp;podcast via your favorite podcast apps!</strong><br />🎙️&nbsp;<a href=\"https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe\">Spotify</a>&nbsp;|&nbsp;<a href=\"https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0\">Google</a>&nbsp;|&nbsp;<a href=\"https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475\">iTunes</a>&nbsp;|&nbsp;<a href=\"https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf\">PocketCasts</a>&nbsp;|&nbsp;<a href=\"https://www.stitcher.com/show/gutenberg-changelog\">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href=\"https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast\">Pod Bean</a>&nbsp;|&nbsp;<a href=\"https://castbox.fm/channel/Gutenberg-Changelog-id2173375\">CastBox</a>&nbsp;|&nbsp;<a href=\"https://www.podchaser.com/podcasts/gutenberg-changelog-878239/\">Podchaser</a>&nbsp;|&nbsp;<a href=\"https://gutenbergtimes.com/feed/podcast\">RSS Feed</a>&nbsp;</p>\n\n\n\n<p class=\"has-large-font-size\" id=\"shownotes\"><strong>Show Notes </strong></p>\n\n\n\n<h2>Announcements</h2>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/\">WordPress 5.9 Planning Roundup</a> by Josepha Haden Chomphosy</li><li><a href=\"https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/\">Preliminary Road to 5.9</a> by Matias Ventura</li><li><a href=\"https://developer.woocommerce.com/2021/08/31/peek-into-the-woocommerce-blocks-roadmap/\">Peek into the WooCommerce Blocks&nbsp;Roadmap</a> by Darren Either</li><li><a href=\"https://us02web.zoom.us/webinar/register/1616234355871/WN_TShtABQnRYKrHN6ffMFpaA\">Live Q &amp; A: Theme developer discussion going from classic to block-based Themes </a>on October 7th, 16:00 UTC / 11 am Eastern</li></ul>\n\n\n\n<h2>Gutenberg 11.5</h2>\n\n\n\n<ul><li>Make.Core: <a href=\"https://make.wordpress.org/core/2021/09/17/whats-new-in-gutenberg-11-5-16-september/\">What’s new in Gutenberg 11.5? (16 September)</a></li><li>WPTavern: <a href=\"https://wptavern.com/gutenberg-11-5-adds-widget-grouping-iterates-on-the-block-gap-feature-and-updates-nav-menus\">Gutenberg 11.5 Adds Widget Grouping, Iterates on the Block Gap Feature, and Updates Nav Menus</a></li></ul>\n\n\n\n<h2>What&#8217;s discussed and worked on</h2>\n\n\n\n<ul><li><a href=\"https://oandre.gal/the-developer-experience-of-presets/\">The developer experience of WordPress presets</a> by Andre Maniro</li><li><a href=\"https://github.com/WordPress/gutenberg/issues/29882\">Gallery Block Refactor: Features and functionality to test during CFT</a> by Glen Davies</li><li><a href=\"https://github.com/WordPress/gutenberg/issues/29102#issuecomment-919886307\">Update on Navigation Block and Screen</a> by Daniel Richards</li><li>Discussion: <a href=\"https://github.com/WordPress/gutenberg/issues/31551\">How to provide backwards compatibility for custom fields on the existing Menus screen</a>.</li></ul>\n\n\n\n<p>To get weekly updates via email, <strong><a href=\"https://gutenbergtimes.com/subscribe\">subscribe to our Weekend Edition.</a> </strong></p>\n\n\n\n<div class=\"wp-container-6172d8674f517 wp-block-group\"><div class=\"wp-block-group__inner-container\">\n<p>Did you like this episode? Please write us a reviewhttps://lovethepodcast.com/gutenbergchangelog</p>\n\n\n\n<p> </p>\n\n\n\n<p><em>If you have questions or suggestions, or news you want us to include, send them to <a href=\"mailto:changelog@gutenbergtimes.com\">changelog@gutenbergtimes.com</a>. </em></p>\n\n\n\n<p><em>Please write us a review on iTunes! <a href=\"https://gutenbergtimes.com/itunes/\">(Click here to learn how)</a></em></p>\n</div></div>\n\n\n\n<h2><strong>Transcript</strong></h2>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Hello and welcome to our 52nd episode of the Gutenberg Changelog podcast. We’re recording this on September 16th, 2021. In today&#8217;s episode we will talk about the planning scope and team for WordPress 5.9, the roadmap for WooCommerce blocks and of course this week&#8217;s Gutenberg 11.5 release.&nbsp;</p>\n\n\n\n<p>I am Birgit Pauli-Haack, WordPress developer advocate and curator for Gutenberg Times. Again, I&#8217;m delighted to have with me on the show co-host Grzegorz, or Greg, Ziółkowski, JavaScript developer at Automattic and WordPress core contributor. Hi, Grzegorz, how are you doing today?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Hello, Birgit. I&#8217;m fine. I&#8217;m looking forward to my vacation that starts this weekend. I&#8217;m going to Greece. It&#8217;s first time since two years going abroad, so I am really excited but also not so happy about all the paperwork that is necessary to travel these days.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah, with all the COVID and vaccines and all that kind of thing, is that what you&#8217;re referring to with paperwork?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yes. I have five forms to fill in for myself and my family. It&#8217;s strange. I guess you know that because you traveled from the States to Germany a few weeks back.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. Yeah, we did. I scheduled my test that I have to do because the United States changed how they let people in. Now I have to have a test that&#8217;s not older than three days to get in although I&#8217;m vaccinated. It&#8217;s strange. It&#8217;s all strange.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, yeah. At least I don&#8217;t have to do any tests because I&#8217;m also vaccinated. That&#8217;s on the good side here.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, on the way in we only needed to show our vaccination records and be done with it. On the way back it&#8217;s going to be both.&nbsp;</p>\n\n\n\n<h3><strong>Announcements</strong></h3>\n\n\n\n<p>Anyway, we start our episode today with an announcement, with an announcement that Josepha Haden Chomphosy published the preliminary planning for WordPress 5.9. That&#8217;s supposed to be released December 14, 2021. Yes. It&#8217;s again just before the holidays and many sites will wait until January to update, but most sites it turns out update right away. We did this, had this exercise now for the last four years I think as far as I can remember.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yes, even WordPress 5.0 was released on December 8th, 9th, I don&#8217;t remember exactly.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> 6th?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Maybe 3rd. It was in December and we had the same discussion, why it&#8217;s happening just before Christmas.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Right. Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> We are a worldwide project, it is not only Christmas for people, some people don&#8217;t even know what that is and they just have their own holidays.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. The world does not stop when WordPress releases. We found that out with 5.0. The internet did not break and everything was going smoothly. I know there are a few US agencies that want to close down over Christmas and they just &#8230; yeah, I don&#8217;t think it&#8217;s a hard sell for them to say we do all the upgrades in January when we come back.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> It&#8217;s perfectly fine.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. I think so too, yeah.&nbsp;</p>\n\n\n\n<p>Again, as they did for 5.8, there will be a go/no-go decision for what will be in the release. That is scheduled to happen on October 12th. That&#8217;s about four weeks ago, in four weeks, sorry. That&#8217;s in four weeks. The feature freeze will be November 9th and then beta one is supposed to be ready for November 16th. People get cracking.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I think this series is a bit smaller in the scope, so I think that those dates make a lot of sense. I think the schedule for the 5.8 was a bit longer, especially between the feature freeze there was two weeks, but at the end of the day I don&#8217;t think that matters that much.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Mostly not for Gutenberg because you patch back to the WordPress right away when you have bug fixes, yeah.&nbsp;</p>\n\n\n\n<p>The scope follows pretty much what Matías Ventura published earlier this month as the preliminary scope, so we will have blocks with intrinsic web design, then the navigation menus, interface, the user interface for the theme JSON. Theme JSON was introduced for theme developers for 5.8 and 5.9 will have the first version of the interface so users can also configure their themes and their block editor through that. There&#8217;s also refining of editing flows for block themes, a new default theme and additional design tools from the block editor.&nbsp;</p>\n\n\n\n<p>Then there are a few, Josepha called them hopefuls that might get in but they might not get in. Part of it is the pattern insertion and creation features so that you can submit patterns to the directory and then also insert them directly from the inserter. Right now you have to click the copy button and then copy/paste them. For 5.9 the meta team is aiming for insertion into the block editor. Then also unzip/rollback fail-safe, there&#8217;s a whole team working on that, more PHP unit tests and then improved compatibility with PHP 8.0 and 8.1.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> The last three items aren&#8217;t related to the Gutenberg at all, but in some ways they improve the overall quality on WordPress core, so it&#8217;s maybe somehow related.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Right. Right. Yeah. That&#8217;s that. The team is, release lead is again Matt Mullenweg with Josepha being the coordinator I think.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: And the marketing team lead.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> And the marketing team lead, yeah, with that. Who else is there already in the posting?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> I&#8217;ve seen that a few days before and the list was still missing a few names. I don&#8217;t know if it was updated since then.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> That was quite a while ago. Here we go. September third was it published. The team, to go back to that, release lead is Matt Mullenweg, marketing and comms is Josepha Haden, technical writer is Jonathan Bossenger and those are the leads that are filled in. I think the rest is going to come together when the meeting is, the board chair meeting later on. All right.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yes. There&#8217;s still time to volunteer if some of our listeners want to jump in and help with the release, even as people who just watch the process and be ready for the next major release to take this leadership role.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. Josepha asked for volunteers for triage lead and the release coordinators. If you don&#8217;t triage the bugs or the tickets that are supposed to go into 5.9 and see how they&#8217;re going you&#8217;re not going to get a release together. The coordinators are really important to get all the teams ready and working on this. I think there are a few volunteers already on the post in the comments section, but you can still throw your hat in the ring. That is about 5.9. I think the next date for that to watch is October 12th with the go/no-go because that will determine what exactly will come into the release from the navigation screen, new navigation blocks, see how far the gallery block, the new gallery block, refacted, is going. That&#8217;s still in the experiment. There are a few other things that might or might not come.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski: </em>Yeah. I think the most important one would be the navigation block and the navigation screen. That&#8217;s quite a huge project that has evolved for quite a while.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. I think over almost two years. It&#8217;s also, I just saw and we&#8217;ll see it in the updates later there are some discussions going on that our listeners might want to chime in in terms of backwards compatibility.&nbsp;</p>\n\n\n\n<p>We promised also a Woocommerce roadmap regarding blocks. Darren Either from the team put a nice blog post together with a lot of information about that, what is happening and what is in the near future or what is soon happening. The high priority is to build robust blocks for checkout and cart, the shopping cart, that not only gives the store and their customers a much better user experience but also allows for extensibility for third-party tools. The blocks will become the default way to handle checkout and carts soon. They were a little bit cagey with dates and something, but it&#8217;s definitely something to watch out for. They will also have, for the transition, fallbacks to shortcuts and the shortcuts for cards and checkout and then if the extension isn&#8217;t optimized for blocks.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. We will include also a link to the GitHub repository that contains all the blocks. There are a few of them. They are very advanced I must say. In the WordPress core we have a lot of blocks, however they are more on the side of editing content so the complexity comes only in the block editor, whereas Woo, they do something really impressive on the front-end so those blocks are interactive, they are optimized in terms of performance. There&#8217;s some really impressive work on their side. I&#8217;ve been watching that for quite a while, this is in the works for over two years now, and they are improving. Their initial implementation, it was mostly bringing back compatibility from shortcuts, that was transitioned from shortcuts to blocks. I remember the first prototype, it was creating the safe implementation, the short code and that was just not working. Their block editor experience was the change but the rest has stayed the same. They have evolved in so many ways.</p>\n\n\n\n<p>They also shared some ways for the users and shop owners, the checkout flows are now much more smoother and that leads to better conversion rates, which is the whole goal of this concept. It&#8217;s also, now you have the ability to preview how cart and checkout looks from the editor. It sounds, in our context when we talk all the time about the block editor the preview is something you just take for granted, but here we are, it&#8217;s improvement in their workflows. They were also talking about the iterations they are doing and how they are trying to use InnerBlocks to structure or architect their blocks. That&#8217;s also a great way when they are presenting in the post how it empowers users to add their own integration pretty easily. You have now a checkout form and you can inject any type of blocks, you can add a heading in any place you want, you can add, I don&#8217;t know, an image. Whatever you like you can add there and also reorder items like change headings. It&#8217;s something that wasn&#8217;t possible before and this just opens new possibilities.</p>\n\n\n\n<p>I&#8217;m also happy to see that this flow is now becoming the default one, because it was present but it was only for some extensions that were in Woocommerce store by default. Now it&#8217;s open also to plug-in others. That&#8217;s the biggest change.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. I really like how Darren put the post together. He has many, many screenshots in there so you get really a good picture of what&#8217;s going to happen. Check it out. There&#8217;s also some work being done to prepare Woocommerce for the site editing feature that&#8217;s coming to 5.9 somehow, or 6.0. I think it was good for the Woocommerce team to wait until the block editor was a little bit more stable and had more features for extensibility. I&#8217;m glad that they found it now worthwhile to put it together and that the user experience is up to the quality that they wanted to. That will open up the signal also for other plug-in developers and also gives quite a nice set of example code that you can study if you are into reading code. As Greg said, we&#8217;re going to share not only post the show notes, but also the GitHub repository so you can check it out.</p>\n\n\n\n<p>Now I have the last announcement, then we get to the release, our next live Q&amp;A on the Gutenberg Times YouTube channel will be October 7 at 16:00 UTC, 11AM Eastern and 18:00 Central Europe Time. Sorry. Got all the times mixed up again. That is pretty much the story of this week for me. I go either way and I always go wrong, so I need to read it and pronounce it right. October 7, 16:00 UTC. We will discuss with experienced WordPress theme developers how they transition from building a classic theme to a block based theme and using theme JSON and also full site editing and the global styles as far as it&#8217;s already available.&nbsp;</p>\n\n\n\n<p>We will have as a guest Ellen Bauer. They published just recently their Aino theme. That is their block based theme and they have additional features in there that will cover that. Carolina Nymark, who&#8217;s on the themes team and also worked on the 2021 blocks, TT1 Blocks theme, that&#8217;s the block based 2021 product. She also has a site called full-site editing where she teaches full-site editing to theme developers. It&#8217;s great to have her on the show. Then the last one is Andres Norén who designed the 2020 default theme last year. He&#8217;s working on a new theme as we speak. Oh yeah, by the way, his theme Eksell is actually powering the Gutenberg Times site for, I don&#8217;t know, half a year now. I&#8217;m glad to have those two, Ellen and Carolina and Andres, on the show on October 7th.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, I think the line-up is just so great. I&#8217;m looking forward to this Q&amp;A session. I think you did a great job convincing all the people who have so much experience building full site editing themes to be on the show.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. I&#8217;m really happy that they all make the time to educate our community on this. Also not only to be on the show, to take the time, but also take the time and work through this because we all know that, if you are an early adopter, you basically do all the bug testing and quality assurance for the team, but you also have to invest a lot more time because of course documentation is not yet complete or changes. It&#8217;s a major undertaking and I&#8217;m glad that these three are coming to the show and telling us what they have found.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. There is also this bright side that you are on the bleeding edge of innovation and you are part of the process and you influence how this all shapes up.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Absolutely.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> I think it has more pros than cons.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Oh, absolutely. Looking back, the three years, block editor, most of the early adopters have had, really a jump on the new technology and, yeah, were supported by big acquisitions or hired just right away because of their expertise that they have shown. It will be similar to theme developers that are early adopting these new features, even if it&#8217;s a little bit of a heartache or a headache, more a headache. It&#8217;s the cutting edge, indeed. Sometimes it&#8217;s the bleeding edge, you&#8217;re right.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. In this context, which makes me very happy, is that all three invited guests, they are in the community for quite a while and they seem to be aligned with the vision and they are adjusting their themes to be up-to-date, which is really impressive.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, they totally get the vision. All three of them have published quite a bit of their learnings. Yes, I will share a few links in the show notes so you can check them out, but definitely sign up for, register for the live Q&amp;A so you get also your questions answered.</p>\n\n\n\n<h3><strong>What’s Released &#8211; Gutenberg 11.5</strong></h3>\n\n\n\n<p>That brings us to the Gutenberg 11.5 release. We are, as of today there is not a final release yet because there&#8217;s some problems with the build sequence.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, it&#8217;s some turbulence like during the flight. I mean everything is ready, it&#8217;s just the process didn&#8217;t end up successfully and it&#8217;s more of the technical challenge of the release process itself than something is wrong. Yeah, I hope at the time when this podcast will be produced and ready then the release will be out, hopefully today. We said the date for recording before assuming that everything goes out on Wednesday as usual.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, yeah. Well there was, the 11.5 release candidate is out or has been out for a week, so that&#8217;s what we are basing things on. There weren&#8217;t any changes on it from the features or the PRs, it&#8217;s just the build process.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yes.</p>\n\n\n\n<h3><strong>Features</strong></h3>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: All right. We have a few new features. Do you want to talk us through it?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. Let&#8217;s start with the block support changes. In the previous episode we mentioned that gap block support feature. That was still an experiment. It was implemented on the team JSON side, but it was disabled by default. Now we have this support, there&#8217;s a UI for that. It&#8217;s pretty simple. In the dimensions panel, if I recall correctly, we have this control that allows you to change the gap between blocks. The name is still to be settled as far as I know because it has some, in the world of design there is something similar that might be confusing, but it was, you just change the numbers and it just increases the spacing between blocks.&nbsp;</p>\n\n\n\n<p>Related to that there is also a change in the group block. At the moment the group block has this layout option, layout control that allows you to change how it is presented. By default it just uses, every block in the group is in its own row, however this new feature is just integrated with the inserter that inserts a group block with every block in the same row. They are aligned, next to each other in one line, which is pretty nice for some complex designs. This is just, it was there in the group black, it&#8217;s just the new way of discovering this feature in the inserter, in the slash inserter when you are typing in the prompt in the editor.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. It&#8217;s the first implementation of the Flex layout that I think Riad actually put the basis in for with 11.4. Now this is the first iteration where one block is actually using that. Of course there will be more. In the PR, if you want to follow up on that, there are some links back to the Flex layout.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, but I think the Flex layout we talked about one or two episodes before.</p>\n\n\n\n<h3><strong>Enhancements</strong></h3>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Right. Yeah, but there was not a block that came with it out of the gate. It&#8217;s also part of what&#8217;s in 5.9 being the intrinsic design of pages. There will also be, another change is actually that the bug report form, which is one of the most important forms on the GitHub repo, has received some changes. The ones that are here in that release are more cosmetic but I wanted to point it out, the new template feature of GitHub is now used and they created a new bug report form to remind people of all the information that would be helpful if someone would take on an issue to fix it. I encountered quite a few issues where we needed to find out what actually the user used, what versions they are or what are the steps to reproduce it. Those are very important information. If we have to read minds what&#8217;s actually happening, we might not get to reproduce the error or the quirkiness that is and we have to go back and ask for further information. That is just delaying the time of the fixing.&nbsp;</p>\n\n\n\n<p>Following the form is now much easier and you don&#8217;t forget anything. I also wanted to point that out for those who are in the GitHub repo. Let us know, or let the team know when there is something to be fixed or not working right.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, that&#8217;s a nice change. Usually it sends up someone needs to ask for more details. After a few weeks, if there is no answer, the issue is closed, which isn&#8217;t something we really want. It is just the reality because we cannot reproduce the issue.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. There&#8217;s no questioning the experience of the person who posts it, it&#8217;s just we need to see it, we need to be able to reproduce it to locate where the code change needs to happen to actually fix it. It&#8217;s just saving a lot of time and being very specific in what&#8217;s not working. Yeah. Yeah. Next the block library has got some new enhancements. One of them is using the block gap between column blocks, so that is another iteration of a new feature. Now you can….</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, but this has only changed on the CSS level for now. As the rich table in the PR set, it&#8217;s a stop gap for block gap.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Nice, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Fun with words. Yeah, but that&#8217;s the direction, I guess. Most of those layout related blocks should start using those design controls, elements, to make the experience more cohesive. That in general is the direction where it&#8217;s heading.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. There was an article in the WP Tavern about what controls somebody could use, should use or should be having out of default and not changeable, who&#8217;s having control over themes? I think there were some misunderstandings. Matías went into the comments section and clarified a few things regarding that. If you come across an article go into the comments and see what Matías has to say as well. Matías Ventura, the spark of Gutenberg, just to reiterate that.&nbsp;</p>\n\n\n\n<p>The video block got an enhancement to use the existing video poster image on insert. The video block has become quite powerful and quite flexible. There are six or seven different settings that you can have in the sidebar that you can switch on and off. This issue or feature is now that, once you assign a poster image to the video the first time, it remembers it. When you embed it into a page or post again, because it&#8217;s in a different context or it&#8217;s in a series of videos or something like that, you don&#8217;t have to assign the poster image again, it will remember it. It&#8217;s all about the effort to streamline the content creator&#8217;s workflow.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> There is also a change in the query pagination next and previous blocks. They are very low level blocks that construct the query pagination, which is part of Query Loop Block, but it shows how flexible the InnerBlocks paradigm is. There is now an arrow attribute that syncs next/previous block arrows.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. It was there before, but it wasn&#8217;t really good, visible in the sidebar or for people to check on. Now they are real settings that are big buttons that you can click so it changes. You were always able to change the text of your pagination from next to previous page or something else. You say low level, but it&#8217;s also quite an important block because, when you get to full-site editing and you write your own templates and you have a list of block posts from a category or from a tag and you have multiple pages of those, you want that query pagination to be available and also be usable. It&#8217;s quite interesting, especially for publishers that have online magazines or so.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> There&#8217;s also a change in the post outer block. You&#8217;ve got duotone support. At first I was surprised seeing that, but there is an avatar or the image of the user which got this feature, which is, again, a good to have way to apply similar effects to all images on your page.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, or just make it blend in more into the overall design because it&#8217;s a small avatar. To normalize it amongst all the others that you have on your site. There&#8217;s also, the wide alignment control now is only available if the theme provides the layout wide size setting. I think that&#8217;s a change to, so you can adjust that setting through the theme JSON again and not have to &#8230; yeah, you don&#8217;t have to do it through the functions PHP now.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. I think in the past you would enable full and wide at once, so it just gives you more grand control over those features.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, you can now decide, okay, I only want the wide but not the full, or you only want the full but not the wide kind of thing. Yeah. That&#8217;s a good point. Yeah. Thank you.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> There is also a quite important change for the navigation screen that&#8217;s being in the works and preparing for the final release. They are the undo and redo buttons in the editors, it&#8217;s the same feature that you have for the post content editor in the headers, it was just missing there. Definitely an important change.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Oh yeah, yeah. All in the streaming of the content creator&#8217;s workflow. Streamlining, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. It&#8217;s also related to the keyboard shortcuts. Some of you probably use command Z and command X. No.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> The redo? I don&#8217;t know. I never redo, I only do undo.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, command Z is the most popular one because you want to go back.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, I need to find out what the keyboard….</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, check this out in the Gutenberg editor when you go to the header and there is three dots, menu, then you have keyboard shortcuts as one of the options. That&#8217;s the simplest way to check all the shortcuts and learn new if you don&#8217;t know them yet.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. Yeah. There were other changes to the navigation screen. I just wanted to remind our listeners that it&#8217;s not yet in the plug-in per se, it&#8217;s still in experimentation so you need to go to the Gutenberg menu and the WP admin experiments section and then check the navigation screen so you can test it for yourself and try and help us get it tested and do a lot of bug fixes, bug reports there. There is also a change, the REST API team is working on creating the end points for the navigation editor for the menu. At the moment I think it&#8217;s all through the admin Ajax. The final version will use the REST API like any other places in the block editor.</p>\n\n\n\n<p>Yeah, speaking of screens there&#8217;s a widget editor. It now received a widget group block for the widget screen which is quite nice now to follow the idea of classic widgets where you have a heading and then a widget. You can change the title of it and now you can add the heading and the widget into a group and then get it a little bit more contained and keep it together, style them and have a background of it and all that. It&#8217;s more what the user was accustomed to when dealing with widgets, the widget group helps with that.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. I would say it&#8217;s more to bridge the experience for everyone familiar with the widgets old screen. It seems like a good change in that regard.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> I like it, yes.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> I don&#8217;t know how it works technically. When you insert a widget does it wrap it with the group out of the box now?</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. I think you can highlight, like you do in the post editor, you highlight the things that you want to group and then you transform it into a widget group.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Okay.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. The widget group has all the group block settings as well in the sidebar. All right.&nbsp;</p>\n\n\n\n<p>There are some enhancements for the global styles or fixes. Now you are able to disable text and background colors via the theme JSON. I thought you were doing that before, but maybe it didn&#8217;t work.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. As far as I know it&#8217;s related to some mock-ups that were presented. The idea is that you would be able to disable almost all the color customizations one by one. Maybe that worked only for the link before. There&#8217;s a few.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, yeah. I think they changed a little bit the logic on how sub-components are shown in the color panel. Link color is enabled when the block supports it, the theme supports it, it&#8217;s launched by default. Yeah, it needs to be switched on or even the presets contain some solid value or the custom colors are used. Presets have some color. You need some color presets and the same is true for the text color, the background color and the gradients, although the gradients, you need to have either the custom colors in there or it&#8217;s empty, it&#8217;s disabled. For both the link color, text color and background color the block needs to support it, the theme needs to be supported and the defaults are different for each of them. Then the presets need to contain values for it. That&#8217;s quite a good set of logic there.&nbsp;</p>\n\n\n\n<p>Yeah, they streamlined all that logic and then now they are making the global styles available for all themes. That&#8217;s in PR 34334. I like that number, 34334. The preset classes for colors and font sizes were in the block library and they are now part of the global styles sheet that&#8217;s loaded later. That&#8217;s a change in the style sheets that are included by default. Then the preset classes look like the preset dev class. There are some changes. If you need to target those classes you might want to look at this again here. There is a post.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I just shared a link with you from André is who one of the lead developers on the global styles project. He explains how the experience of using WordPress presets looked before team JSON and how it&#8217;s changed, how it got simplified. That would be a good read in this context. Also in the same PR that we are talking about, this 34, 334, there is a dev note sketched already that will be published later in the release process of WordPress 5.9. It also just covers what you, Birgit, just said. It&#8217;s pretty complex, so I guess that&#8217;s something that you should process at the time of learning how to use those presets.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. Then the media placeholder experienced another change. For now you can create a URL, if you wanted to add an image through the URL of the image you only could use absolute links. It needed to start with HTTP because it was a URL input type on the placeholder and that has changed to a text input type in some verification. Also now you can actually use local URLs. If you know the URL of your image that you want to add to a gallery or to a post, you can now use local URLs and don&#8217;t have to put in the domains, which is actually good when you move the site or move the site to a different domain, or you have just an image that&#8217;s somewhere in a different place than on the WP content uploads directory. That&#8217;s definitely a good thing that&#8217;s ….</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, I personally was surprised that when you are using an input HTML tag, when you set the tag to URL it expects the full URL. That was the original issue that caused….</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Right. Caused this change, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> &#8230; this change. Yes.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. I think it was only Firefox, but the browser developers are really tightening up the browsing experience. That was a part of their verification so you wouldn&#8217;t be able to add it to that.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> There is also a quite important change for team developers. Now there are default editor styles that are applied to teams without team JSON and without editor styles. Sounds complex, but it&#8217;s just something that is even considered for the minor WordPress edits like 5.8 to now. It just adds some basic styles to all sides just to ensure that the experience is better for the block editor in particular.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. This plays well out of the box even if the theme editor, the theme developer has not updated a style sheet for the theme. I think that&#8217;s a good place for the adoption of the block editor that we are all working towards, that more and more people adopt that, especially in the themes. If it&#8217;s nice looking out of the box and they don&#8217;t have to go back to the theme developer to style a column or to style images or the widened and full width or the media and text, that there are quirks, I think that&#8217;s a good decision now that theme developers can control it through theme JSON and their own editor styles. They can just the default styles. Yeah, that&#8217;s good work there.</p>\n\n\n\n<h3><strong>New APIs</strong></h3>\n\n\n\n<p>Ah, here it is. Of course, every time, and you hear me say this on this podcast quite a bit, every time you have a new feature you also need to provide the opt out of the feature. Here it is, allow themes with theme JSON to opt out of the block gap styles. There is a mechanism there how you do this.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, I think it&#8217;s also related to the fact that it was opt in add styles, so now that&#8217;s probably, it has become a default so now you need to have a way to disable that if you don&#8217;t like that.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Now we moved also to the new API sections with this item on the list.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Oh, yeah. Yeah. We have so many sections in this release note.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yes, it&#8217;s very long this time.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: It&#8217;s very nice, yeah, but it&#8217;s also &#8230; it&#8217;s pretty much in the settings of your theme JSON. It&#8217;s settings, spacing, block gap, null. That&#8217;s how you opt out of that.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Quite a common way for all those global style related features. That&#8217;s the only item in the new API. Now it&#8217;s time for bug fixes. As usual, the list is very long.</p>\n\n\n\n<h3><strong>Bug Fixes</strong></h3>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> There seem to be not really big boo-boos that we have fixed. You find in the list under the block library fixes for the gallery block. I wanted to point out that those are referring to the gallery Refactor. This is the newly created gallery block. It&#8217;s still an experiment in the Gutenberg plug-in. If you want to do the navigation screen and test the new gallery block, you have to enable them also on the experiments screen of your Gutenberg plug-in.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> You can always test the new gallery block on the new navigation screen and that&#8217;s two things at once tested properly.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> But don&#8217;t do this in production. It&#8217;s called experiment for a reason. Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I mean for new websites I wouldn&#8217;t worry at all about enabling the new gallery factor block. I think the fact that it&#8217;s in experiment still is only because of backward compatibility.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. I would not say only. It&#8217;s a big part. It&#8217;s a big part and it&#8217;s also part of the headaches that they have, but it&#8217;s also &#8230; if you want to switch it on and you need a list of test instructions, I&#8217;ll link in the show notes to the GitHub issue 29882, 29882, because there&#8217;s a list of 40 tests that you can do, everything that you can do with a gallery block, you should do. We are preparing, on the developer relations team we are preparing an official call for testing that would hopefully get more people involved. We will also reach out to the plug-in developers to make sure they know about the new plug-in, new gallery block and update their features.&nbsp;</p>\n\n\n\n<p>I know that the developer team has already tested the full plug-ins like CoBlocks and Jetpack blocks gallery blocks, but there are many, many more that need to be tested. If you have questions about that, feel free to DM me. Send me a direct message on WordPress Slack at BPH. Again, the test instructions that are right now out, that also the developers use, is the issue 29882, 29882. Of course we&#8217;ll link in the show notes. I just want to make sure that everybody knows this is coming and it&#8217;s cool.&nbsp;</p>\n\n\n\n<p>What&#8217;s the Refactor? We talked about it before, but we always have new listeners. The gallery block as it is now is just a feature parity with the old classic editor gallery block where you have a list of images and then they&#8217;re all pulled in, but you&#8217;re not able to do much with those images except for moving them. You&#8217;re not able to adopt styles that are only for one image. The new gallery block is now a collection of single image blocks with which come all the features that you can do from an image block like obviously duotone, be it applying styles, applying backgrounds, adding a different link to each image and all these nice features. It&#8217;s a much richer experience for editors and you have much more freedom for it. It needs quite a few testings. Because of that switch of the InnerBlocks the extensions will change as well. I tested it about two months ago and I found that the gallery plug-ins that I used were working fine, but I&#8217;m not using all of the gallery blocks. It might have changed because there was some development on that. Yes.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, definitely the best part here is that now it doesn&#8217;t matter whether you are changing a dual image not a standalone block or it&#8217;s part of the gallery block, you have everything unified, the same controls, the same capabilities. It&#8217;s pretty cool to see that working this way.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Also all the extensions that you have for the image block are now also in the gallery block which is cool.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. Cool is the right word.</p>\n\n\n\n<p>Grzegorz Ziolkowski: Yeah. We are still on bug fixes. One of the changes that landed is for the writing flow, it&#8217;s in the block editor now. When you merge two blocks together the current position of the cursor is put in a better place than before. I don&#8217;t know what exactly was the issue, but it&#8217;s very annoying when you need to use arrows to move the cursor to the proper position when you change this type of modification, like when you have two paragraphs or similar text-related box.</p>\n\n\n\n<h3><strong>Experiments</strong></h3>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. Then we get to the experiments but we have been talking about experiments before. Now you are able to put in the navigation block the site title as well as the logo and that makes it much nicer to assemble a header for a site when you use full site editing with that. It&#8217;s now really easy to have a logo and the site title and then the menu all in one line. Try it out and see if that works for you.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah. I&#8217;m looking forward to see how the gallery block will evolve because the same feature that you have now in the navigation block could work there as well. I can imagine that you could inject a site logo also inside the gallery because why not, that would be also in some ways &#8230; you could have some designs where that would work. In general, the idea of InnerBlocks, this is what we really want because it just opens so many possibilities for designs that weren&#8217;t possible before. You had to hard code that in HTML in your PHP files and now it&#8217;s at your site, you just need to move some blocks around, insert something and then it just aligns nicely.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> It&#8217;s a good point, because now you could have, a three by three grid of images at the center could actually be a poem or something like that that is not an image but a text. The InnerBlocks really open up quite a few more possibilities, especially on the gallery block. That&#8217;s why the Refactor is so important and also that&#8217;s why it takes a little longer to merge into the plug-in because there are some things that need to be changed for backwards compatibility.</p>\n\n\n\n<p>We also get, the social links now use the Flex layout. That means you can arrange the social links either vertically or horizontally I think and also have the block gap in between so you can have the distances also controlled. All kinds of different things are available now in the social links block.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Those design tools are really powerful. I&#8217;m looking forward to having them all stable and released as part of WordPress 5.9. I hope it happens.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> We need testers. We need people who test things. The more bugs you find, the better the release will be in 5.9.</p>\n\n\n\n<h3><strong>Documentation</strong></h3>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Now we are at the documentation. This section, do you see something that is a bigger one? There is a lot of typos that were fixed or some tooling that was improved like ESLint, something that is more in general for the Gutenberg project. Some improvements to bring the documentation up to date, like replacing, we select calls from WordPress data package to use, a react hook which is called useSelect.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. Good point.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. I guess there isn&#8217;t anything very important that we have to mention today. Again, there&#8217;s a code quality. This section, it&#8217;s very long.</p>\n\n\n\n<h3><strong>Code Quality</strong></h3>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: But that&#8217;s your favorite section, right?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, I mean it depends what&#8217;s inside it. There are some changes to bring code up to date, similar to what I said about using most recent APIs that were developed and some errors which is &#8230; for those who don&#8217;t know there are some special validations for the code quality that helps us catch some bugs. Whenever they show up or the tools get updated and they are better at catching those bugs we try to fix this as soon as possible.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Excellent. Yes.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> There&#8217;s a lot of refactoring that doesn&#8217;t have any impact on the user interface but helps for the longer, in terms of long term support for the project.</p>\n\n\n\n<h3><strong>Various</strong></h3>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> No, I get it. That brings us also to my favorite section, the various section. There&#8217;s one item in there that I wanted to point out, that&#8217;s the vertical heading levels menu. When you insert a heading into the block editor, you get a list of levels, H2, H3, H4, H5, H6. Now you can have, the heading can now be vertical. I think it&#8217;s by default vertical now instead of horizontal as it was before so it only covers a certain different amount of content when you have the toolbar right next to the block. It&#8217;s quite nice to look at that. You just go with the mouse pointer up and down instead of left and right. That was a bit ….</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. I think initially in the first release it was also vertical, but then, at that point, there were only H2, H3 and H4 options in the menu so it was short and it was quite easy to &#8230; on the visual level it would look better, but then you had six options like right now and there was also text for each of them. It just was too much to see H1 and heading one, this is why those iterations were applied now.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. It also came from the query block, when you have other, not only the heading block but also the post title block or the archive title, then the context of that menu was a little bit different and you were covering up too much of that query block that you tried to template things.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Right, right.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. That was the other part. The heading is now multi-usage so to speak and not just a mere heading block. Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski: </em>Yeah. The last item is a very important one. I hope that&#8217;s not the case for our listeners, but if you are using WordPress 5.6 then the Gutenberg plug-in won&#8217;t be supported anymore in that version. You need to have at least WordPress 5.7 to be able to still use the Gutenberg plug-in.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> To use the newer version of the Gutenberg plug-in.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: In general we recommend using the latest one because that makes everything so much easier, but we also know that, when there&#8217;s a new major version, some sites cannot be immediately updated. We wait for one more major release, but in the future we consider that this period of time would be shorter, maybe two months, three months, something like that. It also depends on the major release cycles. Now this year we have only three major releases. The plan initially was to have four. That wouldn&#8217;t be that much of an issue. With three releases it&#8217;s just too much time when we have to support code that is no longer necessary in the plug-in.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. To make this specific, if you are on 5.6, only Gutenberg plug-in until 11.4 will work with your WordPress. You can use the plug-in but you won&#8217;t get the updates after, unless you upgrade to the next version, 5.7, in your WordPress. I don&#8217;t know if I made it clearer.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. I don&#8217;t know, I don&#8217;t want to test that, but &#8230;.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Well if you have any questions, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Encourage everyone to stay on the latest major version which is 5.8.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yes, 5.8.1, yes. All right.&nbsp;</p>\n\n\n\n<p>This was the Gutenberg 11.5 Changelog. It&#8217;s quite an interesting mix on that, but most of them are design tools and theme related and some of them are related to some blocks and also for the content creator flows. It&#8217;s a nice release again with a lot of people bringing &#8230; we have quite a few new contributors now on the Gutenberg repository which is a nice change.</p>\n\n\n\n<h3><strong>What’s in Active Development or Discussed</strong></h3>\n\n\n\n<p>Now we are coming to the section of what&#8217;s in active development or discussed. Because it&#8217;s so &#8230; the next big thing that comes into WordPress is the navigation block and screen, or that&#8217;s what everybody&#8217;s hoping. Daniel Richards posted an update on what are they working on. Of course it&#8217;s slow progressing and they&#8217;re migrating the navigation editor, I mentioned it before, to the REST API. Those changes have been merged and it&#8217;s all updating now. Lots of UI changes that are working now, the top bar, the editor top bar being updated, the main block inserter added and then fixes for the block styles.&nbsp;</p>\n\n\n\n<p>Now I can put the important part, good discussion is on the way, he writes, on how to provide backwards compatibility for custom fields on existing menu screens. That covers the part where now the plug-in advance custom fields has a section where you can augment the menu, in the classic menu, with additional fields and additional information. The discussion on that issue is how far should that &#8230; the team works under the assumption that it needs to all be backwards compatible and it&#8217;s the issue &#8230; if you want to follow up and not go to the show notes, 31551 is the issue with the navigation screen menu items custom CF options. There&#8217;s a discussion, Elliot Condon, the lead developer on the plug-in, is in the discussion as well, so help make this, we need you to also chime in.</p>\n\n\n\n<p>Then what they&#8217;re working on next is that they want to have &#8230; in the current editor, menu editor you can say, &#8220;Okay, give me all the posts or all the pages.&#8221; You&#8217;re bulk adding links to your menu, that&#8217;s still in the works for the navigation screen, the block-based navigation screen and also to have theme JSON controls to configure the navigation block further. That still is in the works.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> It sounds like a lot of work to me.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. Those all &#8230; yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. I&#8217;m sure all of those tasks are in progress, however to take them to the finish line is going to be quite a huge challenge because we have four weeks between go/no-go dates, so it really depends. Also I could envision that the new navigation block would be included in core but maybe not the navigation screen. There is a lot of ways to proceed in this regard. Let&#8217;s see how it works. I hope that the screen will be enabled. Opt in is the only option they consider, similar to the widget screen, that you need to enable yourself.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. Yeah. I think so, especially with the backwards compatibility. These menu plug-ins that are out there, it&#8217;s not only the advanced custom fields plug-in that modified the menu pieces or menu entity or the link entity in the menu screen or menus, there were other plug-ins, albeit the Mega Menus, albeit some others. They need to be backwards compatible. Oh, the other part was naming menus. When we build sites we sometimes have a footer menu, a header menu and a main menu and we need to name them and make them available to pull in into any other screens there and make them available for full-site editing as well. There are a few things that this powerful feature in classic WordPress, it&#8217;s hard to reproduce it and be as flexible as it is now.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Okay. That&#8217;s all about the announcement. I just wanted to remind that I&#8217;m taking time off. Unfortunately that coincides with the next Gutenberg release. Together with Birgit we decided to skip recording in two weeks. We cover two Gutenberg plug-in releases in one episode and that should be available for you in four weeks.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> That&#8217;s right. We will take a break from the podcast. I hope you are subscribed to the newsletter of the Gutenberg Times so you can still get some updates in between, or just visit the website in between.&nbsp;</p>\n\n\n\n<p>Before the end of the show I want to remind you that there is actually a live Q&amp;A coming up on October 7 at 16 UTC, 11 Eastern, when we discuss the building, going from building classic themes to building block based themes with Ellen Bauer, Carolina Nymark and Andres Norén. We will entertain you there and answer all your questions. I&#8217;m thinking I will ask them to actually stay for, instead of 60 minutes to 90 minutes, because we will have some demos and we want to make sure that we answer all your questions.</p>\n\n\n\n<p>There will be a link on the homepage of the Gutenberg Times and of course we will have it in the show notes.&nbsp;</p>\n\n\n\n<p>As always, the show notes will be published on <a href=\"https://gutenbergtimes.com/podcast/\">GutenbergTimes.com/podcast</a>. This is episode 52. If you have questions or suggestions or news you want us to include, send them to <a href=\"mailto:Changelog@GutenbergTimes.com\">Changelog@GutenbergTimes.com</a>. That&#8217;s <a href=\"mailto:Changelog@GutenbergTimes.com\">Changelog@GutenbergTimes.com</a>.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: I just wanted to remind that you also can reach out to us on Twitter. My handle is G-Z-I-O-L-O. You, Brigit, is B-P-H, right?</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Right. Right. Well I say thank you, Greg, Grzegorz, it was again a great pleasure talking to you. I wish you a wonderful vacation in Greece. Until the next time.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Thank you, Birgit and our listeners for being with us. You, Birgit, I wish you a pleasant flight back home. See you all in four weeks.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> All right. That&#8217;s it. Thanks for listening. Goodbye.&nbsp;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 16 Oct 2021 19:45:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:122:\"Gutenberg Times: Changelog #51 – Automattic Becomes a Sponsor, new Gallery Block, Theme.json, and Gutenberg 11.4 Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/?post_type=podcast&p=18882\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"https://gutenbergtimes.com/podcast/changelog-51-new-gallery-block-theme-json/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:60542:\"<p>Birgit Pauli-Haack and Grzegorz (Greg) Ziolkowski discuss Automattic becoming a sponsor of Gutenberg Times and Gutenberg Changelog, Classic Editor, Frontity, Theme.json, the Gutenberg 11.4 Release and more. </p>\n\n\n\n<ul><li>Music:&nbsp;<a href=\"https://soundcloud.com/xirclebox\">Homer Gaines</a></li><li>Editor:&nbsp;<a href=\"https://www.linkedin.com/in/sandy-reed/\">Sandy Reed</a></li><li>Logo:&nbsp;<a href=\"https://markuraine.com/\">Mark Uraine</a></li><li>Production:&nbsp;<a href=\"https://paulisystems.net/wordpress-consulting\">Pauli Systems</a></li></ul>\n\n\n\n<p><a href=\"https://gutenbergtimes.com/podcast/changelog-49-drag-and-drop-flex-layout#shownotes\">Show Notes </a>/ <a href=\"http://changelog-51-new-gallery-block-theme-json#transcript\">Transcript</a></p>\n\n\n\n<span id=\"more-18882\"></span>\n\n\n\n<p><strong>Subscribe to the&nbsp;<a href=\"https://gutenbergtimes.com/podcast/\">Gutenberg Changelog</a>&nbsp;podcast via your favorite podcast apps!</strong><br />🎙️&nbsp;<a href=\"https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe\">Spotify</a>&nbsp;|&nbsp;<a href=\"https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0\">Google</a>&nbsp;|&nbsp;<a href=\"https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475\">iTunes</a>&nbsp;|&nbsp;<a href=\"https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf\">PocketCasts</a>&nbsp;|&nbsp;<a href=\"https://www.stitcher.com/show/gutenberg-changelog\">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href=\"https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast\">Pod Bean</a>&nbsp;|&nbsp;<a href=\"https://castbox.fm/channel/Gutenberg-Changelog-id2173375\">CastBox</a>&nbsp;|&nbsp;<a href=\"https://www.podchaser.com/podcasts/gutenberg-changelog-878239/\">Podchaser</a>&nbsp;|&nbsp;<a href=\"https://gutenbergtimes.com/feed/podcast\">RSS Feed</a>&nbsp;</p>\n\n\n\n<p class=\"has-large-font-size\" id=\"shownotes\"><strong>Show Notes </strong></p>\n\n\n\n<h2>Announcements</h2>\n\n\n\n<ul><li><a href=\"https://twitter.com/bph/status/1432272585404915713\">Birgit Pauli-Haack joins Automattic as Developer Advocate</a> (Twitter) </li><li><a href=\"https://frontity.org/blog/frontity-is-joining-automattic/\">Frontity announced they joined Automattic</a></li><li><a href=\"https://wptavern.com/automattic-acquires-frontity-founders-to-work-full-time-on-gutenberg\">Automattic Acquires Frontity, Founders to Work Full-Time on Gutenberg</a> (WordPress Tavern)</li><li><a href=\"https://wordpress.org/news/2021/08/an-update-on-the-classic-editor-plugin/\">An Update on the Classic Editor Plugin</a> </li><li><a href=\"https://wptavern.com/wordpress-classic-editor-support-extended-for-at-least-another-year\">WordPress Classic Editor Support Extended for at Least Another Year</a></li></ul>\n\n\n\n<h2>Community Contributions</h2>\n\n\n\n<ul><li><a href=\"https://frostwp.com/\">Frost theme</a> by Brian Gardner</li><li><a href=\"https://wpaino.com/\">Aino theme</a> by Ellen Bauer and Manual Esposito, </li><li><a href=\"https://tellmeaboutblocks.com/2-how-rich-tabor-created-the-markdown-comment-and-todo-list-blocks\">Tell me about Blocks podcast episode 2 w/ Rich Tabor</a>, hosted by Michael Schneider</li></ul>\n\n\n\n<h2>What&#8217;s Released</h2>\n\n\n\n<p><a href=\"https://make.wordpress.org/core/2021/09/01/wordpress-5-8-1-rc-1/\">WordPress 5.8.1 RC, final release September 8th, 2021</a></p>\n\n\n\n<h3>Gutenberg 11.4</h3>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/core/2021/09/01/whats-new-in-gutenberg-11-4-1-september/\">What’s new in Gutenberg 11.4? (1 September)</a> </li><li><a href=\"https://wptavern.com/gutenberg-11-4-overhauls-galleries-adds-axial-padding-for-buttons-and-lays-groundwork-for-global-spacing\">Gutenberg 11.4 Overhauls Galleries, Adds Axial Padding for Buttons, and Lays Groundwork for Global Spacing</a></li><li><a href=\"https://make.wordpress.org/core/2021/08/20/gallery-block-refactor-dev-note/\">Gallery Block Refactor Dev Note</a></li><li><a href=\"https://make.wordpress.org/core/handbook/glossary/\">Core Handbook / Glossary</a></li></ul>\n\n\n\n<h2>What&#8217;s in active development or discussed? </h2>\n\n\n\n<p><a href=\"https://matiasventura.com/post/the-theme-json-horizon/\">The theme.json horizon</a> by Matias Ventura</p>\n\n\n\n<h2>Discussion on Twitter and beyond:  Building Blocks with JavaScript and PHP </h2>\n\n\n\n<ul><li><a href=\"https://twitter.com/markjaquith/status/1432461667187765251\">Mark Jaquith </a>(Twitter)</li><li><a href=\"https://twitter.com/riadbenguella/status/1432645771535568899\">Riad Benguella</a> (Twitter)</li><li><a href=\"https://twitter.com/lrs62318876/status/1432699364313636877?s=20\">Lars Gersmann</a> (Twitter)</li><li><a href=\"https://twitter.com/swissspidy/status/1432608191196667906\">Pascal Bichler </a>(on Twitter)</li></ul>\n\n\n\n<ul><li><a href=\"https://github.com/youknowriad/blocky\">POC: Blocky</a> (GitHub)</li><li><a href=\"https://helen.blog/2021/08/exploring-custom-blocks-from-a-php-centric-developer-ux-point-of-view/\">Exploring custom blocks from a PHP-centric developer UX point of view</a> by Helen Hou-Sandi</li><li><a href=\"https://wptavern.com/a-world-where-some-block-development-is-merely-a-templating-system-with-no-build-process\">A World Where (Some) Block Development Is Merely a Templating System With No Build Process?</a></li></ul>\n\n\n\n<div class=\"wp-container-6172d867877db wp-block-group\"><div class=\"wp-block-group__inner-container\">\n<p>Did you like this episode? Please write us a reviewhttps://lovethepodcast.com/gutenbergchangelog</p>\n\n\n\n<p> </p>\n\n\n\n<p><em>If you have questions or suggestions, or news you want us to include, send them to <a href=\"mailto:changelog@gutenbergtimes.com\">changelog@gutenbergtimes.com</a>. </em></p>\n\n\n\n<p><em>Please write us a review on iTunes! <a href=\"https://gutenbergtimes.com/itunes/\">(Click here to learn how)</a></em></p>\n</div></div>\n\n\n\n<h2 id=\"transcript\"><strong>Transcript</strong></h2>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Hello, and welcome to our 51st episode of the Gutenberg Changelog podcast. In today&#8217;s episode we&#8217;ll talk about Automattic becoming a sponsor of Gutenberg Times and the Changelog, theme.json, Gutenberg 11.4 release and a lot more.&nbsp;</p>\n\n\n\n<p>I am Birgit Pauli-Haack, curator of the Gutenberg Times, and I&#8217;m here with my co-host, Grzegorz Ziolkowski, JavaScript developer at Automattic and WordPress core contributor. Hi, Grzegorz, how are you today?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> I still feel energized and extremely excited after all the big news shared this Monday in the context of the Gutenberg project. Maybe you should speak first. How have you been lately? Has anything interesting happened?</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. That&#8217;s funny. Yeah, it&#8217;s been a wonderful week, though.&nbsp;</p>\n\n\n\n<h3><strong>Announcements</strong></h3>\n\n\n\n<p>I have fabulous news and some of our Gutenberg Times subscribers already know that. People who follow me on Twitter know this, but I&#8217;m thrilled to announce that on Monday, August 30th, I started as a developer advocate at Automattic. Grzegorz and I have been co-workers for five days now.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yay! Congratulations. I can&#8217;t think of anyone else who fits better for this role.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Oh, thank you. You&#8217;re too kind. Like many people who responded and shared on Twitter, many are podcast listeners, as I said, and I was overwhelmed by all the kindness in the WordPress community. Thank you to everyone. Sometimes Twitter really shares its love and I took it all in. Well, it was overwhelming, and a lot of people have reached out. And so thank you.&nbsp;</p>\n\n\n\n<p>So, Automattic is now main sponsor of the Gutenberg Times, the Changelog podcast, and our live Q&amp;As and my work working on it.&nbsp;</p>\n\n\n\n<p>Being part of the WordPress developer relations team feels like coming home to me. And I&#8217;m deeply grateful for Automattic for offering me that position. The best is yet to come for Gutenberg and publishing with blocks. I&#8217;m elated to be part of an astonishing team that takes the worldwide WordPress community to the next journey.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yes, so I&#8217;m really glad that you will be able to dedicate 130% of your work time to help people to get to their next level when hacking with Gutenberg. And I&#8217;m highly impressed with what you were able to achieve as a volunteer, in addition to other duties that help you to pay the bills. So I can also imagine how much of an impact it will make on the community now. I said there is more news to share. What else has happened?</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Well, on Monday, Frontity announced they joined Automattic too. So Grzegorz, can you describe what Frontity framework is, and how this fits into the Gutenberg roadmap?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> So for those who don&#8217;t know Frontity, it&#8217;s a &#8230; how they call it? Server-side dynamic framework for headless WordPress sites and blocks. So in some ways, it&#8217;s similar to Gatsby for those who know the space of headless or decoupled WordPress. The biggest difference is that Gatsby, it&#8217;s a static site generator, which means it generates HTML files, JavaScript files, and it just runs on your server, so you don&#8217;t need Node.js server, whereas Frontity uses Node.js.&nbsp;</p>\n\n\n\n<p>So it allows you to create a sort of front-end theme that is for WordPress, and that&#8217;s run in Node.js. And it uses the content you create including the content with blocks, and it adds some additional functionality to it like nice page transitions. It adds some dynamic features like for images and there are plugins that can apply some changes to that so it&#8217;s really interesting. And the best thing here is that Frontity as a framework, in their announcement post, they said that they are planning to pivot their efforts to WordPress core.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yes, but so Frontity runs in ReactJS too, right? Not only Node.js but ReactJS, okay.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski: </em>Yes.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah, no, that&#8217;s awesome. So Matias Ventura, he&#8217;s a member the developer experience team at Automattic and lead architect at the WordPress Gutenberg project. He wrote that, &#8220;I&#8217;m really impressed with the effort and care the Frontity team has put into the work over the past few years. We are at a cusp of exciting new opportunities for Gutenberg and I cannot wait to start collaborating together on making the experience of developing with it a joy to behold.&#8221; So that sounds like a great pivot for Frontity to just be a framework to actually bring everything into Gutenberg, as you said, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. So I see it more like they bring their experience. And they will try to replicate some of great ideas they had in the Frontity framework, and find ways to achieve the same goals inside WordPress core, which would benefit so much bigger audience. I&#8217;m thinking about developers, but also for users on the WordPress. And I&#8217;m also beyond excited about the plan they outlined in the post.</p>\n\n\n\n<p>So they said that, &#8220;Automattic offered to sponsor our team to work directly on the WordPress open-source project, and in particular, to contribute our expertise in developer experience, front-end tooling, performance and user experience to the WordPress core itself.&#8221; So this is exactly what I just said. And actually for me, who is focused around experience with building blocks, it&#8217;s really great how this expertise can bring the project to the next level, and our efforts to making full-site editing so performant and optimized for bringing only the assets you need, bringing what&#8217;s missing the most now is that the block editors is focused on the WP Admin but on the front-end side, we need more interactivity and more better experience of global sites, the first step but Frontity bringing their own experience can fill the gaps in other areas.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, yeah. And I have seen that there are also developer relations people with Frontity, so I&#8217;m glad we will definitely be able to learn from them. What I missed early on was talking about the developer relations team. It&#8217;s actually now a band of five with Anne McCarthy and Daisy Olsen being there for almost over a year just wrangling the whole thing by themselves. And then Tara King was joined, and then Ryan Welcher and myself, so we are band of five.&nbsp;</p>\n\n\n\n<p>And I think there are two people coming away from Frontity, but I&#8217;m not quite sure yet. We haven&#8217;t even as a team yet have &#8230; because we&#8217;re all new. So we&#8217;re all in support rotation right now at Automattic and at the WordPress forums. So I think next week is going to be the bigger week where we&#8217;ll co-organize everything a bit better. Yeah, so but there&#8217;s exciting news for the future of Gutenberg and there&#8217;s also some good news for some other site owners, agencies and developers. The WordPress core committers officially extended the support for the Classic Editor plugin all through 2022.&nbsp;</p>\n\n\n\n<p>This gives everyone another year to migrate to blocks. Josepha Haden Chomphosy wrote, &#8220;Still, if you have been putting off using the Block Editor, this is an excellent time to give it another shot. Since it first appeared in 2018, hundreds of WordPress contributors have made a lot of updates based on user feedback. And you will be pleasantly surprised how far it&#8217;s come.&#8221; Of course, most of our listeners know that, about all the huge changes because we haven&#8217;t been shutting up about them. But it&#8217;s definitely an interesting year now for the Gutenberg project and migrating to Gutenberg because all of a sudden, it has a much better picture of the final version or the final vision. Not the version, it will never be done, but yeah, final vision.&nbsp;</p>\n\n\n\n<p>And also, now that quite a few APIs are settled, there is a great creativity amongst developers and we&#8217;re going to talk about it a little later in the show. But on the WordPress Tavern, Justin Tadlock also interviewed core committer, Jonathan Desrosiers. And he had some more details on their approach towards maintaining the plugin beyond 2022. So we will share that link in the show notes like we will all the other links in our Announcement section here, that&#8217;s now quite big. Yes. Anything to comment there, Grzegorz?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, I mean I wouldn&#8217;t be surprised if there were listeners of this podcast that still use the Classic Block plugin. And this is mostly because you might have a site that is no longer developed and it just doesn&#8217;t make too much sense take therefore to migrate that to blocks. So there are always use cases like that. So I&#8217;m really happy that the support is extended. But eventually, I think that it would be good to say that it&#8217;s only a plugin. And if you want to, just keep it installed, and the community should take over the effort, because it&#8217;s a lot of work to keep it up to date. And it&#8217;s not something that we want to have forever.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Well, and funny, you mentioned that. I have quite a few sites, and it might surprise everybody to hear that, quite a few sites that are actually on Classic Editor. We have taken them over about two years ago or some of them three years ago. And the theme is that Franken theme, like where all the plugin functionalities within the theme. And then there are plugin that we could build and separate out. But the theme, it does the custom post types, and then relies heavily on advanced custom fields.</p>\n\n\n\n<p>Even they have a blocks kind of building thing, there is no migration work done between former advanced custom field sites to migrating to blocks. That&#8217;s one thing. I own this one site where there are thousands and thousands of posts on them that there&#8217;s no bulk, reliable way to migrate those over. One site is so old, or that was designed in 2012. So it&#8217;s not even responsive now, or the responsiveness is kind of really clunky, but the content creator has used a lot of HTML tags within his postings. And it&#8217;s an elaborate layout. Making that into Gutenberg blocks is very, very, very hard. But those are the projects I will be handling sooner or later.</p>\n\n\n\n<p>But yeah, there is a good reason to stay in Classic Editor for another year or two or three. But yeah, you&#8217;re right. Once in a while, it&#8217;s probably needs to be taken over by the community. And there are actually a few plugins already in the repository that go a little bit further than the Classic Editor. One of them is by John Starr, and it says Disable Gutenberg. And it also covers the classic widgets section from that. So yeah, just a little side note, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> One question.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Mm-hmm.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> So why don&#8217;t you stop upgrading WordPress, like keep it on 4.9 and just take the security updates? Isn&#8217;t that the best option to feel safe about the future of the site?</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Well, I think sooner or later that most people would actually appreciate Gutenberg as a user interface and getting block patterns rather than a section of, I don&#8217;t know, two pages of ACF Meta Boxes and they don&#8217;t have a clue how it looks, as long as they don&#8217;t hit preview and see how it looks on the front-end. And so, I think the advantages of using Gutenberg for even a big site that has a lot of layouts would be even better. So a migration sooner or later needs to happen.&nbsp;</p>\n\n\n\n<p>Also, not only for that, but also we have new editors come online, all the knowledge is kind of outdated, or they see it on other sites. And that&#8217;s a WordPress skill now, to work with Gutenberg. And now they come to a publication that doesn&#8217;t use them, it&#8217;s anachronistic. It takes the fun out of it, pretty much. It takes the fun out of me when I need to use the Classic Editor because, &#8220;Oh, it would be so much easier to do it in Gutenberg and we can do so many more things.&#8221; So sooner or later, we need to think about migrating these large sites.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah. So I guess the reason is that you want to stay with the latest WordPress to get all the updates and make sure that the plugins are still compatible, and they also get updates, right?</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Right.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, I mean, it makes a lot of sense. I&#8217;m just mostly curious.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah, no, I totally get it. Yeah. Especially that-</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, I guess we can move on.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: &#8230; I think we have to otherwise we&#8217;re getting a little long, yeah.</p>\n\n\n\n<h3><strong>Community Contributions</strong></h3>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> We can move on to Community Contribution. So I only wanted to highlight two full-site editing themes that I found out about recently. One of them is called Frost and the other one is Aino, I don&#8217;t know if I pronounced that right. And they are very interesting. And we&#8217;ll leave the links in the show notes as usual. And one of those themes had a very interesting idea because it was like a master theme that had a collection of block patterns.&nbsp;</p>\n\n\n\n<p>So it&#8217;s like you have many different target groups in one theme, but you can select that through pattern, which is pretty interesting idea. It&#8217;s like a sort of block patterns directory inside the theme, which is something new. I like those explorations in the community that happen right now with all the new possibilities. So Aino is also targeting e-commerce websites. So that&#8217;s also quite fine.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. So Aino has been built by Ellen Bauer and Manuel Esposito, I think, the theme developer shop out of New Zealand. And Ellen Bauer was already part of our live Q&amp;As talking about full-site editing early on. And Frost WP is the full name of the site, frostwp.com, started by Brian Gardner. And Brian Gardner has been around the WordPress community for ages. He was the original founder of the Genesis framework, which was then sold to WP Engine.&nbsp;</p>\n\n\n\n<p>And he has started now, with the full-site editing in mind, a new theme base called Frost WP. So both themes are not done by new people. They evolve their own coming from the Classic theme going into full-site editing theme and going in full speed. So it&#8217;s really exciting to see them grow and work.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Yeah, pretty inspiring to see those full-site editing themes growing. And I also wanted to report that I did my homework, and I caught up with the new Tell Me About Blocks podcast, which is hosted by Michael Schneider. I guess he&#8217;s from Germany, right?</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> I think Australia, but I haven&#8217;t done my homework yet. I haven&#8217;t connected with him yet, which will happen. Michael, if you listen to this, expect a ping from me.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, so if you look for inspiration how to build blocks, or extend their capabilities inside the WordPress Block Editor, then I strongly recommend listening to both published episodes. I enjoyed the one with Rich Tabor a bit more because he has outstanding experience in the field and he profoundly understand the project&#8217;s visions. So I wouldn&#8217;t feel comfortable saying that he&#8217;s a representative of the Gutenberg core team and put him on the spot and talk about Gutenberg. He deeply understands how it all should work.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, and I followed Rich Tabor from the beginning of his CoBlocks plugin that came out quite early. He built it with Jeffrey Carandang together. Listened to him at the Boston WordCamp in 2019. And he had some great philosophical ideas on how to build blocks in terms of what needs to be in the toolbar, what goes into the sidebar, and how to approach metadata and options data that need to be built into the Block Editor as well and how to handle those.&nbsp;</p>\n\n\n\n<p>So it was quite an interesting way. So he publishes also on richtabor.com, with blog starts about theme.json, about his experience, and what he thinks how everything should work and how it works.&nbsp;</p>\n\n\n\n<h3><strong>What’s Released &#8211; WordPress 5.8.1 RC</strong></h3>\n\n\n\n<p>Yeah, this brings us to our What&#8217;s Released section, and we have a release candidate for WordPress 5.8.1. And it was released two days ago on September 1st, and it has 41 bug fixes to core and about 20 bug fixes to the Block Editor. Although there are 20 release pull requests as you mentioned before we started recording, Grzegorz, not all of them are part of the bug fix. Some of them are just PRs that need to be added so the other PRs would work.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, so Gutenberg developed so fast that we introduce some technical changes that just are related to, let&#8217;s say, code quality, and then it makes it difficult to backport the actual bug fixes. So that&#8217;s why it took 20 commits, instead of let&#8217;s say, 10 or 15.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. So we will share the show notes to the release candidate post on the core Make blog with all the track tickets and PRs that went into it. The release date for it is September 8th, unless, of course, any additional fixes to be made. But that&#8217;s expected to be Wednesday, September 8.&nbsp;</p>\n\n\n\n<h3><strong>Gutenberg 11.4 Release</strong></h3>\n\n\n\n<p>And then we had Gutenberg 11.4 release.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: Finally.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Finally?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Finally, the Gutenberg plugin.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, do you want to start out with what the most important things are?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski</em>: It&#8217;s one thing that I marked like we said and big font is the change that converts the Gallery block to use Image block. So it&#8217;s a concept of having composed log of several blocks, I mean, two blocks at the moment. So this change is still behind an experimental flag. So you need to go in the WP Admin to the sidebar. And there is Gutenberg, and there is Experiments page, and you need to mark the checkbox and save the settings to enable this new version of the block.&nbsp;</p>\n\n\n\n<p>There are several reasons that were covered with the dev note that we talked about, I guess in the last episode. We will include the link to the dev note. This change is planned for inclusion in WordPress 5.9. So we encourage all the block authors and theme authors to check out this new version, because there will be some incompatibilities. It&#8217;s mostly because the markup has changed, and it might break some CSS styles.&nbsp;</p>\n\n\n\n<p>There are also some plugins that do transforms between Gallery blocks to something else or vice versa. So that needs a lot of testing, it was tested extensively already, because it&#8217;s a huge change, which brings a lot of opportunities. And the best way to check it out is look at the release post for the Gutenberg plugin, which shows that demo, and it&#8217;s really nice.&nbsp;</p>\n\n\n\n<p>It shows how you can move images, you can change every individual image the same way as you modify a single image. So, that&#8217;s a great way. You can use drag and drop now inside the Gallery block. It&#8217;s just an excellent change. And of course, the plugin authors can do any change they wanted. Usually they can allow you to use other blocks inside the Gallery block, it&#8217;s very exciting.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, it&#8217;s totally &#8230; I love to see&#8230;. I have experimented with it a bit. And yeah, I like that you can have a different style for each image. So you can have rounded corners for one and circles for a speaker list or something like that. Or each image can have a separate URL now. So when you do a speaker section, that each speaker gets its own link to the profile or the session; just thinking about online conferencing right now, I guess. But it&#8217;s really exciting to see how that works.&nbsp;</p>\n\n\n\n<p>I actually tested this PR a couple of months ago. And I was really amazed how it worked quite well with some of the plugins that you mentioned, Grzegorz like CoBlocks Gallery, or others that had a gallery modification. The three ones that I worked with, were quite compatible with it. I know that Glen Davies, who spearheaded the refactor of the Gallery block also did additional testing with that. He tested them with the Jetpack blocks and Lightbox for the Default Gallery &amp; Image Block.</p>\n\n\n\n<p>So, I mean, he also made a point in testing the three default themes, as well as Astra and Arbutus. So it&#8217;s all in the developer note that he published and which you will find a link in the show notes as Grzegorz said. Yeah, but I&#8217;m really excited about this. I think this is such a great way to put a huge photo gallery together and make it work on a website, yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, and just to add more, so now in the Gallery, you can apply image editing, so you can crop the individual image. You can add duotone effects. It&#8217;s so powerful because of this change.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. And all you learn with the Image block, you can certainly apply to the Gallery block now. And you don&#8217;t have to use two different ways on image handling. So that&#8217;s definitely an advantage of reducing the cognitive load and expand the horizon a bit. Yeah. So what else is in there? Good. All the next things seem to be like an anticlimax to that.&nbsp;</p>\n\n\n\n<h3><strong>Enhancements</strong></h3>\n\n\n\n<p>But the Cover block now; you can allow an alt text now for your Cover blocks, which is a great accessibility necessity. The Block Lists is now improved, the iframe block, patterns and template previews. So it&#8217;s easier to see what you&#8217;re getting when you go through the list. What else?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> There are a couple of changes to Post Featured Image. So it was pretty basic before but now there is support for duotone. They added the scale property, so which allows you to change how this Post Featured Image is displayed inside the block. And as far as this Post Featured Image can fit to the space it has, it can be somehow like constraint and something like that. So there is some contextual help now added to make it clear what it does, really. And there is now, for other blocks, there is font weight support that was added to several blocks, like Post Date, Post Terms, Site Tagline, and the Button. And yeah, basically, it&#8217;s a constant effort to add those features to more blocks.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, to add more controls to more blocks. Yeah. So I think what I learned with Gutenberg was that well, first, one block gets an extension like the font weight controls, and then once that is finalized, it will be replicated for the other blocks, or other blocks get the support for that, and then it&#8217;s tested, how that would work out.</p>\n\n\n\n<p>So, I really like that to kind of have additional testing in there before it&#8217;s rolled out to all the blocks. Yeah, and that way, the Button block received the spacing support that uses axial padding. So you can have also horizontal and vertical padding for the buttons now within your Buttons block, which is a feature that was requested quite a bit for Gutenberg. And because many, many block suites actually had that built in almost from the beginning, but so now it&#8217;s in core. Yay!</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> So this is&#8230;.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> &#8230; Yeah.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, mark, also some changes, because we have those editor feature preferences. And they were reimplemented now on the Widgets page, on the Site Editor page, on the Post Editor page and now they are extracted. And the idea is to have one common interface to use on all screens and share the logic. So that needs to be tested by all the users because there might be some bugs. I would expect that because there is some technical challenges in how to migrate that and store it in the browser. So when whenever you refresh the page, you have still the same settings, they are stored in the local storage.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> When you talk about feature preferences, do you have an example of that?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, sure. So when you open the more menu like the one on the top, on the right side, and then you have fix my toolbar to the top, disable the full screen mode, and things like that, so some of them are present on all screens, some of them are specific to the given screen, but the code that powers that is now in one place.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Oh, okay. So for all the three editors, it&#8217;s all at one place. And if you change it for one, you know where to change things? Is that answer the past or it&#8217;s now getting closer to thinking about taking those preferences out of local storage and put it into user metadata or is that still a ways off?</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Oh, this one is actually in progress for two years or something like that.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Right, right. But I can understand.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> So we are aware about this limitation. So the first exploration was to use cookies. And because there is some API already that uses cookies in WordPress. However, cookies have limitations in the browsers. In some of them it&#8217;s four kilobytes and in turns out that it&#8217;s not enough for the settings that we want to store. So yeah, there is a REST API-based approach that is close to land, but it never happened. And definitely….</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> &#8230; No, I can see why. Yeah, I can see why it didn&#8217;t happen. Because the editors&#8217; screens were not yet finalized. Because many people knew that there will be a Widget screen, there will be a Navigation screen and then there will be a said editor screen. And the other preference were not yet settled completely over all for different editors. So I can see why it didn&#8217;t happen. But it was also not kind of clear to me that that&#8217;s the reason. Yeah because-</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> &#8230; It&#8217;s also complex from the user perspective because now it&#8217;s the question. So now, you said that you don&#8217;t want to have full screen mode. The question is, &#8220;If you don&#8217;t want to have it only on one of the screens or it should be applied to all screens?&#8221; And now we have it in one place, we could consolidate that and give this option that this option should apply to all screens. But that would now like these user-experience questions.&nbsp;</p>\n\n\n\n<p>And there&#8217;s also other questions. So once you pick something; now I am on the mobile that have a small screen. Do I want to have fullscreen there, or it should apply only to the desktop? So there are so many combinations that make it really hard to build a good API.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: &#8230; Yeah. I imagine. And there&#8217;s also the question, &#8220;Okay, if we do it for our editor team, but when I&#8217;m an administrator, do I want to change that setting again?&#8221; Yeah, that&#8217;s another level there. So I can see why that hasn&#8217;t been finalized. But then if you really want to have your editor screen, I don&#8217;t know what Marias Jensen does, he has this plugin where he stores these kinds of preferences, actually, in the user database, how he manages that. So it&#8217;s interesting to see, yeah once that&#8217;s explored, where it goes. But for this release, all things are now in one interface package. So that&#8217;s a big start in that direction.</p>\n\n\n\n<p><em>Grzegorz Ziolkowski:</em> Yeah, but the changes are applied per screen. So when you change the&#8230; what is it, your toolbar displayed, it will only apply to the given screen for now. But in the future, it has to be decided and we are looking for feedback. So new listeners, if you want to chime in, just open an issue and propose how you would like to see.</p>\n\n\n\n<h3><strong>Bug Fixes</strong></h3>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah, I like that. This brings us to the Bug Fix section, and there were quite a few small bug fixes. We are pointing today to the design 