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:"


";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:"
	
	
	
	




















































";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:"
	
	
	
	
	
	
";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:56:"WPTavern: LottieFiles Releases Official WordPress 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=134695";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:67:"https://wptavern.com/lottiefiles-releases-official-wordpress-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:3040:"<p><a href="https://lottiefiles.com/">LottieFiles</a>, a company that hosts thousands of Lottie animations and helps designers create and test their animations, has just released an <a href="https://wordpress.org/plugins/lottiefiles/">official plugin for WordPress</a>. The company recently <a href="https://techcrunch.com/2022/05/03/lottiefiles-gets-37m-to-make-the-animation-format-even-more-ubiquitous/">raised $37M</a> in a Series B round, passed three million users on its website, and is investing in making motion design more accessible. </p>



<p>Lottie&#8217;s open source animation file format is used by more than 135,000 designers and developers in websites and apps for Amazon, Google, Spotify, Microsoft, TikTok, Netflix, BBC, Uber, and other high profile companies. The JSON-based format was created by the design team at Airbnb and grew in popularity because of the small file size (600% smaller compared to GIFs), the fact that it is scalable at run-time, and its flexibility to be used across any platform. Lottie files can be used on iOS, Android, web and React Native without modification. </p>



<p>LottieFiles&#8217; new WordPress plugin is available for free on WordPress.org. Once the plugin is installed and activated, it will prompt you to sign into your LottieFiles account or a create a free account. You will also be given the option to share the account with other users and copy Lottie files to the WordPress Media Library.</p>



<img />



<p>The plugin was made for the block editor. Inserting the LottieFiles block will launch a modal window where users can browse recent, featured, and popular Lottie animations. Users can also search through LottieFiles&#8217; library of more than 50,000 animations or access private files from their accounts.</p>



<p>One of the benefits of using the plugin, as opposed to simply embedding an animation, is that the block settings allow users to easily adjust the Lottie size and background, along with the speed, looping, and controls display.</p>



<img />



<p>Although block libraries like Kadence Blocks have <a href="https://wptavern.com/kadence-blocks-2-2-4-adds-lottie-animations-block">support for Lottie animations</a>, LottieFiles&#8217; official plugin is a single-block plugin and includes more block controls. It offers one of the most user friendly ways to insert animations into web pages, blog posts, or any content that could use a little a little motion design.</p>



<p>The LottieFiles team has been responsive on the support forums and in the reviews so far. In one instance where a user <a href="https://wordpress.org/support/topic/a-number-of-issues-4/">reported</a> that the plugin adds its CSS on every page in the front and backend, instead of conditionally adding it when Lotties are displayed, the plugin&#8217;s developers said they are working on minimizing the CSS added to pages. LottieFiles is accepting bug reports and feature requests on their <a href="https://feedback.lottiefiles.com/plugin-wordpress">feedback site</a>.</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, 01 Jun 2022 02:44:29 +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:1;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:49:"WordPress.org blog: People of WordPress: Dee Teal";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=12946";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:64:"https://wordpress.org/news/2022/05/people-of-wordpress-dee-teal/";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:12388:"<p>In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people&#8217;s lives for the better. This month we feature a WordPress development and large project specialist on the difference the software and community can make to your career and life.</p>



<img width="1024" height="515" src="https://i2.wp.com/wordpress.org/news/files/2022/05/Dee-Teal.jpg?resize=1024%2C515&ssl=1" alt="" class="wp-image-12955" />



<p>Dee’s story with computers started at school in New Zealand where discovering how a mouse worked and learning BASIC and Pascal was a catalyst for what later became a programming career.</p>



<p>At a time when computers were just becoming mainstream, there were no opportunities for girls in her school to consider this as a further option. She recalls: “No one thought to say, ‘Dee, you look like you’re good at this, you should pursue it…’. I mean, I was a girl (and I was told girls didn’t ‘do’ computers). No one in the circles I moved in really had any idea where this technology revolution would take us.”</p>



<p>With no particular career path into technology, Dee was encouraged in her final year of school to apply for a job in a bank where she worked and became a teller three years later. She gained financial independence, which enabled her to travel as a 20-year-old and spend the next three years exploring the US and Europe.</p>



<p>Looking back, she noted how the world had changed: the first computer mouse she had seen had come out in 1983, and 20 years later WordPress was founded.</p>



<h2>Journey into coding</h2>



<p>During those 20 years, Dee worked as a nanny, working in child care centers, in customer support, and as a temp.</p>



<p>In 1999, she packed up her bags once again, and moved from New Zealand to Australia. She took a place at a performing arts school where she honed her singing and performance skills and volunteered her time to the music director who was starting to experiment with sending out HTML newsletters and updates via email.</p>



<p>“And so my personal revolution began. On the day after I graduated from that course, I walked into a full-time role as that music director’s assistant and began my journey back to code.”</p>



<p>As part of that job, Dee edited and sent HTML newsletters on a weekly basis. This ignited her interest in programming, and she bought books about coding for the web and experimented on her home-built PC making web pages. </p>



<blockquote class="wp-block-quote"><p>“I’m sure, like a lot of us, I remember the thrill of creating that first HTML file and seeing a ‘Hello World’ or similar heading rendered in the browser. From there, I was completely hooked.”</p><cite>Dee Teal</cite></blockquote>



<p>Later she moved to the IT department and took on maintenance of all the websites. By 2004, she was working full-time as a webmaster. A year later, she was running a small business creating sites on the side. Four years after that, her business became her full-time job as she left employment to pursue her Masters Degree in Digital Communication and Culture.</p>



<img width="1024" height="768" src="https://i0.wp.com/wordpress.org/news/files/2022/05/R0011864.jpg?resize=1024%2C768&ssl=1" alt="Dee with other contributors getting things ready for a WordCamp" class="wp-image-12961" />Dee and other volunteers setting up for a local WordCamp



<p>Dee found the theory and sociology behind the web, and its facilitation of human and machine communication fascinating.</p>



<p>She said: “I love the fact that the tech industry involves a constant constant curve of growth and discovery, which results in a perpetual exercise in finding creative elegant solutions for sticky problems.”</p>



<p>For Dee, being able to use her innate curiosity to leverage processes, people, and tools, fuelled by a focus on communicating a message, has been a defining inspiration in her work.</p>



<p>This combined fascination coincided with her meeting WordPress in 2009 and subsequently its community. She moved her existing blog to the software and it became the CMS of choice for all her client work.</p>



<h2>The WordPress community can change your world</h2>



<p>In 2011, she stumbled across WordCamps and by extension the WordPress community. Dee has reflected publicly that WordPress didn’t change her life, its community changed her world!</p>



<p>She flew on a whim from her then home in Sydney to attend a WordCamp in Melbourne she had found after a search for ‘WordPress Conferences’.</p>



<p>She said: “I met welcoming people, made friends, connected, and came back home excited and hopeful about continuing this connection with the wider WordPress community.”</p>



<p>Building a community locally around WordPress got off to a slow start in Sydney. From an inauspicious early WordPress Sydney meetup in the function room of a pub, her connection and involvement took off. Before long she was helping organize that meetup, and by the time she moved away from that great city it had branched into two meetups, and soon after, into three.</p>



<p>She was so inspired by the community that at the end of that first year and her second WordCamp, she raised her hand to help organize a WordCamp Sydney in 2012, and after moving interstate, WordCamp Melbourne in 2013.</p>



<blockquote class="wp-block-quote"><p>&#8220;WordPress and any other software package exist to serve people.&#8221;</p><cite>Dee Teal</cite></blockquote>



<p>Dee said: “WordPress, software, technology, the Internet will come and go, morph, and change, evolve. Maybe WordPress will last forever, maybe it will morph into something else, maybe one day it will look completely different than it did when I first started (actually, that’s true now). The thing that doesn’t change is the humanity around it. WordPress and any other software package exist to serve people.”</p>



<p>She added: “The thing that I have learned, not only through WordPress but in life, is that if we too serve the people around what we’re doing, we ourselves will grow, develop and change alongside the people we serve, and the tools we use to serve them.”</p>



<img width="1024" height="329" src="https://i0.wp.com/wordpress.org/news/files/2022/05/Dee_POW_5.6_slice-large.png?resize=1024%2C329&ssl=1" alt="Dee pictured second from left as part of the WordPress 5.6 contributors" class="wp-image-12957" />Some of the contributors to the <em>WordPress 5.6 release</em> 



<p>Dee was a coordinator for WordPress 5.6 release in 2020 and was able to encourage others to learn about the process.</p>



<h2>Helping others and sharing knowledge through WordPress</h2>



<p>Dee has been an advocate for cross-cultural collaboration and understanding in both WordPress and her work for a large distributed agency which has people from more than 24 countries and operates across 16 timezones. She has also written about closing the gap between diverse distributed teams and how to meet the challenges of cross cultural remote work.</p>



<p>Dee has given talks at WordCamps, including at WordCamp Europe in 2019, on developing ourselves, our relationships, and our communities in increasingly diverse environments.</p>



<p>With a strong desire to share her professional knowledge and experience, Dee hopes her involvement in the WordPress community from being part of a Release Squad in the Core Team, and volunteering in the community through organizing and speaking at WordCamp events, will inspire others to get involved.</p>



<blockquote class="wp-block-quote"><p>&#8220;It’s the connections, it’s the friendships. It’s the network of work, referrals, support, help and encouragement.&#8221;</p><cite>Dee Teal talking about the community that makes WordPress specialbenefits of the WordPress community</cite></blockquote>



<img width="1024" height="576" src="https://i1.wp.com/wordpress.org/news/files/2022/05/dee-wceu2019.png?resize=1024%2C576&ssl=1" alt="Dee Teal's talk at WordCamp Europe 2019 on 'Working a world apart'" class="wp-image-12958" /><em>Dee shared her experience with attendees at WordCamp Europe 2019</em>



<p>In contributing to WordPress and organizing community events around it, Dee found that for her: “At the end of the day it isn’t actually WordPress that matters. It’s those connections, it’s the friendships. It’s the network of work, referrals, support, help, encouragement that has kept me wired into this community and committed to helping other people find that connection and growth for themselves.”</p>



<p>Dee’s career in WordPress has moved through coding, into project management of large scale WordPress projects, and now into delivery leadership. Her connections to community have helped &#8216;fuel the transitions&#8217; through these chapters of her life.</p>



<p>She said: “I believe that the place I’ve found and the opportunities I have had owe as much to my own desire and ambition as they do to the help, support and belief of the community around me; sometimes even more than I’ve felt in myself.”</p>



<p>She feels that she is ‘living proof’ that by helping, connecting, and resourcing other people, you can be helped, resourced and connected into places you had never thought possible.</p>



<p>This has enabled her to reach and have a career in technology that she did not know existed as a teenager playing with that first computer mouse and experimenting with code. Dee hopes her story will inspire others in their journey.</p>



<h2 id="share-the-stories">Share the stories</h2>



<p>Help share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the <a href="https://wordpress.org/news/category/newsletter/interviews/">People of WordPress series</a>.</p>



<h2>Contributors</h2>



<p>Thanks to Abha Thakor (<a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</a>), Meher Bala (<a href="https://profiles.wordpress.org/meher/" class="mention"><span class="mentions-prefix">@</span>meher</a>), Mary Baum (<a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a>), Chloe Bringmann (<a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a>), Nalini Thakor (<a href="https://profiles.wordpress.org/nalininonstopnewsuk/" class="mention"><span class="mentions-prefix">@</span>nalininonstopnewsuk</a>), and Larissa Murillo (<a href="https://profiles.wordpress.org/lmurillom/" class="mention"><span class="mentions-prefix">@</span>lmurillom</a>) for work on this feature. Thank you to Josepha Haden (<a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a>) and Topher DeRosia (<a href="https://profiles.wordpress.org/topher1kenobe/" class="mention"><span class="mentions-prefix">@</span>topher1kenobe</a>) for support of the series. Thank you too to <a href="https://profiles.wordpress.org/thewebprincess/" class="mention"><span class="mentions-prefix">@</span>thewebprincess</a> for sharing her experiences.</p>



<p>This article is inspired by an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.<br />Meet more WordPress community members in our People of WordPress series.</p>



<div class="wp-block-media-text is-stacked-on-mobile is-vertically-aligned-center"><img width="180" height="135" src="https://i1.wp.com/wordpress.org/news/files/2020/03/heropress_logo_180.png?resize=180%2C135&ssl=1" alt="HeroPress logo" class="wp-image-8409 size-full" /><div class="wp-block-media-text__content">
<p class="has-small-font-size"><em>This People of WordPress feature is inspired by an essay originally published on </em><a href="https://heropress.com/"><em>HeroPress.com</em></a><em>, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. </em>#HeroPress </p>
</div></div>



<p></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, 31 May 2022 17:51:53 +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:28:"webcommsat AbhaNonStopNewsUK";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:"
	
	
	
	
	
	
";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:"Do The Woo Community: WooCommerce Builders Going to Pot with Tyler Lau";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:28:"https://dothewoo.io/?p=71728";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:72:"https://dothewoo.io/woocommerce-builders-opportunties-cbd-hemp-cannabis/";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:425:"<p>Tyler Lau has his finger on the pulse of CBD and cannabis industry. There is a lot growth and opporutunitest's an opportunities.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/woocommerce-builders-opportunties-cbd-hemp-cannabis/">WooCommerce Builders Going to Pot with Tyler Lau</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</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, 31 May 2022 09:34: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:5:"BobWP";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:"
	
	
	
	
	
	
";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:68:"Post Status: Post Status Excerpt (No. 60) — A Preview of WCEU 2022";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=98520";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:46:"https://poststatus.com/a-preview-of-wceu-2022/";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:141:"Sabrina Zeidan and Evangelia Pappa preview the upcoming WordCamp Europe 2022. This is the perfect travel episode for anyone en route to WCEU.";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, 30 May 2022 22:30:24 +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:"
	
	
	
	
	
	
";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:72:"WordPress.org blog: WP Briefing: Episode 32: An Open Source Reading List";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=12940";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/2022/05/episode-32-an-open-source-reading-list/";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:11951:"<p>In the thirty-second episode of the WordPress Briefing, WordPress Executive Director Josepha Haden Chomphosy shares her open source reading list for that post-WordCamp Europe downtime. <br /></p>



<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>



<h2 id="credits">Credits</h2>



<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/santanainniss/">Santana Inniss</a> and <a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>



<h2>References</h2>



<ul><li><a href="https://producingoss.com/en/index.html">Producing Open Source Software</a>, Karl Fogel</li><li><a href="https://www.amazon.com/dp/B08BDGXVK9/ref=dp-kindle-redirect?_encoding=UTF8&btkr=1">Working in Public: The Making and Maintenance of Open Source Software</a>, Nadia Eghbal</li><li><a href="https://www.amazon.com/CODE-Collaborative-Ownership-Digital-Leonardo/dp/0262572362">Collaborative Ownership and the Digital Economy</a>, ed Rishab Aiyer Ghosh, Roger F. Malina PhD, Sean Cubitt</li><li><a href="https://www.amazon.com/Humble-Inquiry-Second-Relationships-Organizations/dp/B08VCRL6WQ/ref=sr_1_1?crid=39U1NLFRD52VO&keywords=Humble+Inquiry&qid=1653587884&s=books&sprefix=humble+inquiry%2Cstripbooks%2C63&sr=1-1">Humble Inquiry</a>, Edgar H. Schein (Author), Peter A. Schein</li><li><a href="https://github.com/WordPress/book/">WordPress Milestones</a></li><li><a href="https://europe.wordcamp.org/2022/">WordCamp Europe 2022</a></li><li><a href="https://wp.me/p2U65r-9f3">2022 Annual Meetup Survey</a></li></ul>



<h2>Transcript</h2>



<span id="more-12940"></span>



<p><strong>[Josepha Haden Chomphosy 00:00:00]&nbsp;</strong></p>



<p>Hello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it. As well as 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>



<p><strong>[Josepha Haden Chomphosy 00:00:40]&nbsp;</strong></p>



<p>With the approach of various mid-year breaks and the prospect of wandering off for some safe, restorative travel, I&#8217;ve been updating my to-read and re-read list. As I was looking at the queued books for my Northern hemisphere summer, there were some common threads, mostly around leadership, but there&#8217;s also like a chunk that&#8217;s about cross-cultural group theory and economics, and then like some beach reads, but there&#8217;s one group in particular that you all might find interesting.</p>



<p>And that&#8217;s a group that&#8217;s sort of like a back-to-FOSS basics list. So I&#8217;ll share my top few with you in case you want to pack a copy for your next getaway.&nbsp;</p>



<p>The first one on our list is called Producing Open Source Software by Karl Fogel. I think everyone who contributes to FOSS projects has received this as one of their first recommendations. Like, y&#8217;all are building open software? Excellent, you need to read Producing Open Source Software. Like, that is just a sentence that comes out of everyone&#8217;s mouths. So this was one of the first open source books that was recommended to me when I joined the WordPress community. It was freshly revised in 2020, and I haven&#8217;t given it a read since then, which is why it is on my reread list this year.</p>



<p><strong>[Josepha Haden Chomphosy 00:01:54]</strong></p>



<p>However, it shaped the early days of the WordPress project’s leadership, and their lead developers, and some of WordPress&#8217;s basic philosophies. It&#8217;s all available online, under a creative commons, ShareAlike license. And so it&#8217;s worth the read. I&#8217;ll put a link to it in the show notes so it&#8217;s easy for everyone to find in the event that is your preferred beach read.</p>



<p>The second one on this list is a book from Nadia Eghbal. She wrote the excellent Roads and Bridges report that also is probably not light beach reading, but you know, this one is on my list to read this summer because Eghbal always delivers truths about the reality of maintaining popular software, popular, open source software, in a way that&#8217;s easy for me to access and process rather than getting paralyzed by the enormity of it all.</p>



<p>For what it&#8217;s worth your mileage may vary on that. I realized that, like, I live and breathe open source stuff. And so just because I am not paralyzed by the enormity of her explanations of things doesn&#8217;t necessarily mean that you will have a similar experience. And so I&#8217;m just going to claim that elephant in the room for all of us.</p>



<p>However, if you only read one book on this list this year, I think that this should be the one that you read.</p>



<p><strong>[Josepha Haden Chomphosy 00:03:14]</strong></p>



<p>The third one is called Code: Collaborative Ownership and the Digital Economy. It was edited by Rishab Aiyer Ghosh. I am certain that I butchered that name. And so I apologize on my own behalf to everyone that knows whether or not I said it correctly.</p>



<p>This book focuses on intellectual property rights and the original purpose of having anything like copyright in the world. So, right up my alley! The writers who contributed to this work promise exploration of the plight of creativity in the commons, the role of sharing in creative advancement, and a concept of what it would look like if intellectual property were to mean the second closing of an ecosystem versus a triumph of the commons.</p>



<p>I mean, obviously, this one is very light reading. You can take this topic to high tea and everyone will not know what you&#8217;re talking about. However, this one looks like a really interesting book to me and I am just super ready to read it.&nbsp;</p>



<p><strong>[Josepha Haden Chomphosy 00:04:19]</strong></p>



<p>The second to last one on the list is a book called Humble Inquiry.</p>



<p>This is a new-to-me book that seems right in line with one of my favorite books to recommend to leaders in the open source space. From reviews of it, I have gathered that it takes a hard look at the value of listening and asking for clarification in a world that puts a high value on an unsolicited hot take.</p>



<p>It puts the importance of high trust relationship building, which is at the heart of any cross-culturally aware organization. And for folks who&#8217;ve been working with me for a while, you know, that relationship building is an important part of my leadership expectations for myself. So it puts relationship building at the front and center with a promise of practical applications for everyday life.</p>



<p>And if you ever have tried to tackle a complicated topic like this, you know that practical applications are really hard to come by and it&#8217;s often hard to understand it if you don&#8217;t have those practical applications. And so that is why this one is on my read and reread list this year.&nbsp;</p>



<p><strong>[Josepha Haden Chomphosy 00:05:24]</strong></p>



<p>And then finally the WordPress Milestones book.</p>



<p>So this sounds like a shameless plug for WordPress. And on the one hand, this whole podcast is about WordPress. And so, yes! But on the other hand, I actually am reading this for two specific reasons. I&#8217;m rereading this actually. I read it when I first joined Automattic. And so the first of the two reasons that I&#8217;m rereading it this year is that volume two of this is, like the second decade of WordPress currently, being researched and written in preparation for WordPress’s 20th birthday next year.&nbsp;</p>



<p>So I am rereading this to kind of get that all back in my mind as that work is getting done. And the second reason is that I honestly like to remind myself of how far we&#8217;ve come sometimes. I talk about our work frequently. And I talk about what we&#8217;re working on right now, all the time.</p>



<p>I talk about what we&#8217;re looking at three years from now, five years from now. The biggest concerns of today, tomorrow, and the future-future. And it&#8217;s very easy to forget how much success WordPress has had and how much growth the contributors that support us have had over the course of our long and storied history.</p>



<p><strong>[Josepha Haden Chomphosy 00:06:40]</strong></p>



<p>And so I like to go back to that just to kind of give myself some grounding in our progress, as well as get some concept for how we can move forward together. So that one is also available online. Also under a creative commons ShareAlike license and it is also worth the read. I will share a link to that with the other one in the show notes as well.</p>



<p>That brings us now to our small list of big things. Let&#8217;s see what we got in the old lineup today.&nbsp;</p>



<p>So, firstly WordCamp Europe is happening this week and it&#8217;s possible to watch the live stream from the comfort of your own home. There are some smart and talented speakers at the event. So I encourage you to catch a few if you have the time. I&#8217;ll include a link to the live stream information in the show notes below, and then also you can always keep an eye out on Twitter.&nbsp;</p>



<p>There will be a lot of discussions, a lot of conversation there. And so you can engage with folks that are there at the time and catch up on those conversations, catch up on those presentations in your own time, as it fits into your day.</p>



<p><strong>[Josepha Haden Chomphosy 00:07:50]</strong></p>



<p>The second thing is that WordPress’s community team is preparing the annual meetup survey right now. So if you participate in meetup events, keep an eye out for that because your feedback helps us to make plans to improve that program so that it works better for you. And it helps you to learn WordPress better and feel more confident with what you are taking out into the world that way.</p>



<p>But, if you are wanting to use this as a chance to contribute, we actually will need folks who are able to translate the surveys as well. So I&#8217;ll leave a link to some information about that in the show notes. If all of that stuff about contribution didn&#8217;t make any sense, then just like keep an eye out from your meetup organizer and they will make sure that you have that survey so that you can have your voice heard.&nbsp;</p>



<p><strong>[Josepha Haden Chomphosy 00:08:33]</strong></p>



<p>And then item three is less of an item. I mean, it&#8217;s an item cause it&#8217;s in this list, but it&#8217;s less of, like, a thing to know and more of a general thing to be aware of. It&#8217;s a general awareness item. There&#8217;s a lot going on in WordPress right now. I can see how hard it is to keep track of some of these things these days.</p>



<p>And I know as someone who&#8217;s looking at this all day every day that, yeah, it&#8217;s a lot. And it&#8217;s hard to get your bearings. So if you have a team that you contribute to already, don&#8217;t forget to reach out to each other, just to check-in. Sometimes we don&#8217;t think to ask for help. Sometimes we don&#8217;t think to offer help and you know, if no one needs any help from you at that moment, a little hello also can brighten someone&#8217;s day.</p>



<p>And that, my friends, is your smallest 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 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, 30 May 2022 17: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:14:"Santana Inniss";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:13:"
	
	
	
	
	
	
";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:"Gutenberg Times: Gutenberg Changelog #67 Gutenberg 13.2 and 13.3, WordPress 6.0 and more";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=21224";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:72:"https://gutenbergtimes.com/podcast/gutenberg-changelog-67-wordpress-6-0/";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:58930:"<p>Birgit Pauli-Haack and special guest, Grzegorz Ziolkowski talk about WordPress 6.0 release, Gutenberg 13.2 and 13.3 and interesting discussions happening on the Gutenberg Repo</p>



<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://icodeforapurpose.com">Birgit Pauli-Haack</a></li></ul>



<span id="more-21224"></span>



<p><a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-67-wordpress-6-0#shownotes">Show Notes</a> / <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-67-wordpress-6-0/#transcript">Transcript</a></p>



<p class="has-large-font-size" id="shownotes"><strong>Show Notes</strong></p>



<h2>WordPress 6.0 </h2>



<ul><li><a href="https://wordpress.org/news/2022/05/arturo/wordpress-6-0-release-candidate-2-rc2-now-available-for-testing/">WordPress 6.0 </a>“Arturo” Release post</li><li><a href="https://make.wordpress.org/core/2022/05/03/wordpress-6-0-field-guide/">WordPress 6.0 Field Guilde</a> with all DevNotes and changes</li><li>Video: <a href="https://youtu.be/oe452WcY7fA">Release announcement </a></li><li><a href="https://www.youtube.com/watch?v=MjDhfW7FpAc&t=3s">Building a site with WordPress 5.0 vs WordPress 6.0&nbsp;</a>w/ Anne McCarthy</li><li><a href="https://wptavern.com/new-video-explores-site-building-progress-from-wordpress-5-0-to-6-0">New Video Explores Site Building Progress From WordPress 5.0 to 6.0</a></li><li><a href="https://pantheon.io/blog/what-expect-wordpress-6">What to expect from WordPress 6.0</a> by Birgit Pauli-Haack via Pantheon</li></ul>



<h2>Community Contributions</h2>



<ul><li>Plugin: <a href="https://wordpress.org/plugins/core-rollback/">Core Roll back</a> by Andy Fragen</li><li>Plugin: <a href="https://wordpress.org/plugins/pwa/">PWA </a>(Progressive Web App)</li></ul>



<h2>What&#8217;s Released</h2>



<h3>Gutenberg 13.2 </h3>



<ul><li><a href="https://make.wordpress.org/core/2022/05/12/whats-new-in-gutenberg-13-2-may-11/">What’s new in Gutenberg 13.2? (May 11)</a></li><li><a href="https://wptavern.com/gutenberg-13-2-adds-persistent-user-preferences-and-a-visualizer-for-margin-and-padding-controls">Gutenberg 13.2 Adds Persistent User Preferences and a Visualizer for Margin and Padding Controls</a> (WPTavern)</li></ul>



<h3>Gutenberg 13.3 </h3>



<ul><li><a href="https://make.wordpress.org/core/2022/05/26/whats-new-in-gutenberg-13-3-0-may-25/">What’s New in Gutenberg 13.3.0 ( May 25 )</a></li><li><a href="https://wptavern.com/gutenberg-13-3-introduces-experimental-table-of-contents-block">Gutenberg 13.3 Introduces Experimental Table of Contents Block</a> (WPTavern)</li></ul>



<h2>What&#8217;s being worked on or discussed</h2>



<ul><li><a href="https://github.com/WordPress/gutenberg/labels/%5BFocus%5D%20Blocks%20Adoption">Focus: Blocks Adoption</a> (Label on GitHub)</li><li><a href="https://github.com/WordPress/gutenberg/issues/37943">Allow usage of block based &#8220;template parts&#8221; without using block based &#8220;templates&#8221;</a> (#37943)</li><li><a href="https://github.com/WordPress/gutenberg/issues/41241">Site Editor &amp; Templates Roadmap</a></li><li><a href="https://github.com/WordPress/gutenberg/issues/41232">Global Styles Ongoing Roadmap</a></li><li><a href="https://github.com/WordPress/gutenberg/issues/38167#issuecomment-1132442560">Tracking: Add a Style Engine to manage rendering block styles</a> (Updated May 20th, 2022) </li><li><a href="https://github.com/WordPress/gutenberg/issues/39281#issuecomment-1134481258">Pattern as Sectioning Elements</a></li><li><a href="https://github.com/WordPress/gutenberg/pull/41156">Add a zoomed out view to the site editor</a> (#41156)</li><li><a href="https://github.com/WordPress/gutenberg/discussions/41349">Improving FSE for the Agency Use Case</a>&nbsp;#41349</li></ul>



<p class="has-large-font-size">Stay in Touch</p>



<div class="wp-container-1 wp-block-group"><div class="wp-block-group__inner-container">
<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/maryojob">@maryojob </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>
</div></div>



<p class="has-larger-font-size" id="transcript">Transcript</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Hello, and welcome to our 67th episode of the Gutenberg Fran Podcast. In today&#8217;s episode, we will talk about Gutenberg 13.2 and free WordPress 6.0 and discussions that are taking place and would need your opinion. I&#8217;m Birgit Pauli-Haack, curator at the Gutenberg Times and WordPress developer advocate.</p>



<p>And I&#8217;m here today with my special guest and former co-host Grzegorz Ziolkowski, JavaScript developer at Automattic and virtual school contributor. For WordPress 6.0 release co-lead for editor responsible for the merge of the Gutenberg bits and bites into core. Mary Job sends her regards and is taking a break this week. Good evening, Greg. Thank you so much for joining me again tonight. How are you?</p>



<p><em>Grzegorz Ziolkowski</em>: I&#8217;m great. I&#8217;m so happy that the release went out. Everything works, the work didn&#8217;t collapse, so that&#8217;s great. Also, want to thank you also for being part of the release team and also, I need to mention that I was also a co-lead for the editor with Adam Hevinski, his help was so important to making that happen, because that was a lot of work to bring all the changes from the editor to WordPress core and making sure that everything works.</p>



<p>The group that helped was so huge. There was, I don&#8217;t know, 20 people, at least helping all the time with different type of tasks, which was an amazing experience to see how everyone cooperates.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: And also the release team was much bigger. You and the documentation team also having a core lead like Milana, right?</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: Oh yeah. So it&#8217;s really interesting to be part of the team and see how it works. Also, the team was bigger than ever, as far as I know, and I think that it still could be bigger. In my opinion. We have so many tasks that are necessary to make all that happen.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; I was on the release course now as a rookie and of course I needed co-leads because as a rookie, you don&#8217;t know what to get yourself into. But there are so many pieces that go into this release and it all has been a mystery and most still are mystery to me. Yeah. But I learned a lot. I learned a lot from all of the people on the release squad. But it&#8217;s also the more I know, the more I know what I don&#8217;t know.</p>



<p>And so it&#8217;s kind of that really overwhelming feeling that, okay, I have watched so many times, but I still had no idea what is really behind it in all the different pieces that are there. So, and as you said, I&#8217;m in awe of all the brilliant people that make these run smoothly and are always there to help each other out. It&#8217;s an amazing experience.</p>



<p>Yeah, absolutely. I&#8217;m glad I did it. It was a lot of work and, but wrangling dev notes, it&#8217;s a unique experience anyway. But yeah, congratulations that you helped bring it over the finish line.&nbsp;</p>



<h3><strong>Announcements</strong></h3>



<p>So yes, WordPress 6.0, Arturo was released this week named after the contemporary Latino jazz musician, Arturo O&#8217;Farrill with a good Irish name. And there are many features and enhancements that are rolled out with a new version. We talk probably about all of them during the months, leading up to the release on this podcast, we will share again, of course, the release post, and then the field guide with the dev notes. And we will also share two videos with you. One is the release video by the design team. If you haven&#8217;t seen it yet on the about page or in the release post, watch it.</p>



<p>It&#8217;s a great design and cutting from screen to screen, to highlight all the features that are in there. It&#8217;s a great piece of art, so definitely watch it. And then the second video is by Anne McCarthy and she covered the site building process between WordPress 5.0 and WordPress 6.0. 5.0 was released just to repeat that December 6th, 2018. So it&#8217;s three and a half years ago. And in that video, you&#8217;ll see how it changed from the early versions to how you build sites now. It&#8217;s a great, interesting video to watch. If you haven&#8217;t tried out the block editor yet, if you&#8217;re one who hasn&#8217;t started using it yet, I think you will be surprised, or it&#8217;s eye opening to see how it really changed and maybe it intrigues you to start using it again.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It&#8217;s a huge change. How it all has evolved from starting small to edit only the content that&#8217;s post and pages. And throughout all that time, how data change itself, by bringing more tools that are supported and allow you to do more and more things with the content to add some styling and create beautiful designs without using a single line of code. And now even you can create the whole experience. And there&#8217;s many block themes that empower users to edit everything without ever opening and edit or code the detail where you need to deal with PHP files, CSS, and all that big stuff that are becoming more and more complex every year.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. And I think the biggest piece that helps a user to one part be in control, but on the other hand, not have to think about too much about design or the block patterns. And I think they have come really a long way from the first idea of a reusable block that people used this kind of templates or block patterns, but then they were changing it and then they changed it over the whole page site. But now combining just core blocks into this amazing designs and design system, it&#8217;s really remarkable. Yeah.</p>



<p>So that&#8217;s definitely part of that show notes today is that video. And we also shared the article that the WP Tavern posted about that. And then just today I found that Pantheon published an article by yours truly like what to expect from WordPress 6.0. And it goes a little bit more on the developer side. And apart from the enhancements, talk about the enhancements for the writing experience. It&#8217;s more about develop oriented, how to code, with code examples for the new pattern features on pulling in patterns from the directory wire theme, JSON Slug, or also create page layouts on the create page action, and then some block locking examples, and also how to establish those style variations in the theme, JSON. So it&#8217;s a little bit different than the release post on WordPress.org. So, Greg, what are the most intriguing features that you found for WordPress 6.0?</p>



<p><em>Grzegorz Ziolkowski</em>: So you already mentioned them, from the coding perspective, you covered how to integrate them on, on the owners of the site. And I think for the user, very exciting possibility is to use style variation when they are provided with theme because everyone have different taste and style variation allow you to quickly change colors, fonts have presets that you can quickly pick one and another, and another until it&#8217;s something that clicks with you and you don&#8217;t have to go and change every setting on the website yourself is just, you have bigger chance to&#8230; The other thing block locking. I think it&#8217;s great and it has a lot of value, but it&#8217;s still missing much more detailed control because everyone can lock and unlock now, which is nice, but you can change that.</p>



<p>Yeah. But the idea is that in the future, you could have permission-based rules. So, as a site admin, you could just block everything you want for everyone else or whatever else you would like. So this still needs some development, but it&#8217;s the step in the right direction. And also all the work on patterns that how it evolves. You mentioned that how it was limiting and the beginning, and it was introducing with classic themes in WordPress 5.5. And it didn&#8217;t have so much power because for the content of the post, you don&#8217;t use design so often, but with templates, it&#8217;s just so powerful having a way to insert a footer, a header. And now this is even integrated more contextual. If you use this in line inserter and you are on the bottom of the page, it&#8217;ll propose you some footer patterns in other places, it will propose other patterns.</p>



<p>So it tries to be smart and help you to do the right choice. So it&#8217;s no longer, only core blocks in those inline researcher, but also patterns. And yeah, in general, I really like how all the concepts that we already know, they build on top of each other that you mentioned reusable block. So you can now do sort of magic things. You find the block pattern you like, you convert that to reusable block and suddenly you have something you like, and it syncs with all other places the same applies with template parts.</p>



<p>You can pick from the block directory pattern of footer and just magically it&#8217;s there and synced suddenly with all other places. So I&#8217;m looking forward to seeing more and more things like that, so people no longer have to worry that they open a new template or new post and they see blank canvas and they don&#8217;t know what to do. Now they open an inserter. There is so much inspiration in there and that you&#8230; it&#8217;s just a different experience. It&#8217;s so much easier to create the same website that you see on the themes demo side than it was before.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, well said, Greg. That said, I also like the writing experience. So the favorite feature that I have, it&#8217;s not a big deal, but it&#8217;s actually helping, when you are doing a lot of in-line linking you have the two square brackets, and then you get a list of all the latest posts or pages that you&#8217;ve had. And then you can do in in-line linking for your site. And before you had to kind of look for that and search for it, and what&#8217;s the name of it? And you had to go out and then you had this. Yeah, so this is really nice. And I liked all those keyboard shortcuts that make it, I don&#8217;t have to change from keyboard to mouse and have a very smooth experience yeah. So 6.0 is out.</p>



<p><em>Grzegorz Ziolkowski</em>: It&#8217;s definitely for experienced users because there are lot more gems like that. Once you discover you never want to go back and you use all the methods. But it takes time, but&#8230;</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. And then the same, what trips me up. So the WordPress had this for a long time that when you have a highlighted text, and if you have a see a link on the browser and you copy the link and you highlight text, and then you can just Ctrl V you can actually, it uses the URL as a link on that highlighted text. That trips me up everywhere else.</p>



<p><em>Grzegorz Ziolkowski:</em> Yeah.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Especially, so I know that GitHub took it over. Yeah, now when you want to highlight, or have a link there, you highlight the text on that. You have to URL Ctrl V works. Yeah. That&#8217;s really cool. And I use a user note taking app called LogSync. They have taken that on too, but the Google docs, every link I put in Google logs, I have to do twice because it just over click. I can&#8217;t do it anymore. It&#8217;s just so interesting. Yeah.&nbsp;</p>



<p><em>Grzegorz Ziolkowski</em>: Another experience.</p>



<h3><strong>Community Contributions</strong></h3>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Google docs get on it. We need that there too. Yeah. So another experience that I had during the WordPress 6.0 release cycle, during the beta and release candidates, I used a great plugin that I want to do a shout out for. And it&#8217;s called the Core Rollback Plugin. And it was created by Andy Fragen, who is a long time contributor to WordPress and also part of the beta tester plugin crew. And it allows me to select all the WordPress versions back to 4.0 and install it on a test site. So I was able to test the upgrade from 4.0.23, to 6.0, and does it work or does it bomb?</p>



<p>And then at first I was a bit disappointed because when I started it, I had a block theme enabled. And of course, then I can only have a WordPress version that actually can handle block theme. So I was only rolling back to 5.9, which didn&#8217;t help me much, but then I realized that, okay, I needed to change the theme. So I changed it to Twenty Ten theme. And then the other part was, how do I get to 4.0? I also needed to change the PHP version to 5.6 and I lose local WP. So that was really interesting. And then it took me maybe a minute or two to install the old version and then upgrade was WCLI to the next version. And that was so fast to test. And then I just went into the site again and did a comment or something like that, just to make sure it works. But that is really, it was very helpful.</p>



<p>So I&#8217;m sad that I didn&#8217;t know about it before, because sometimes when you had a WordPress install and the new version came out and you were way on the cutting edge, you had a plugin conflict or something like that. And then how do you roll it back to the previous version? And this plugin will save you so much time and headaches. So just make it sure that&#8217;s in your toolbox when you manage other people&#8217;s websites, because it can really help you with that, go back to the safe version within five minutes or so. And wait, the next two weeks till the next version comes out from workers. Yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It&#8217;s also fascinating that warper still supports some old version that to get it working, you need to use PHP version that is no longer even developed like 5.6. But still, if people have that, they can use WordPress, which is mind blowing.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. It totally is. And I think Serge is watching that percentage of users that still use PHP 5.0 very closely, because I think it&#8217;s going to be real soon that WordPress is going to skip it and say, &#8220;okay, yeah, from now on, we are not supporting 5.6 anymore. You got to have to be on 7.4&#8221; or something like that, but it&#8217;s that promise of backwards compatibility and not kicking users out just because they don&#8217;t know they are hosting environment that still uses these old PHP variations.&nbsp;</p>



<h3><strong>What’s Released</strong></h3>



<p>All right, but this were two interesting weeks. So we had not only WordPress 6.0 come out, but in the last two weeks, we also had two plugin releases. One was 3.2 and the other one was 3.3 and we will cover them both today. So let&#8217;s get started. So Gutenberg 3.2 was released on May 11th and it had a few new features in there.</p>



<p>One was the new preference, persistence API, and we are also happy that it&#8217;s there. Now. It saves now the editor preference in user meta, not in local storage anymore for that the preference handling needed to be revamped before. So we talked about it a little bit in the last episode, but now it&#8217;s here in Gutenberg 13.2. So you won&#8217;t see the welcome guide. You dismiss the welcome guide and it will remember on the site. If you prefer the top toolbar, it will remember. And if you don&#8217;t like the full screen anymore, it will remember, but only on a site basis. So you can access the same site over and over again. And the user settings will be there for you.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It might be also per editor screen. I mean, if you are on the edit site page might be different and on edit post page or widget page could be different. I don&#8217;t know, because I didn&#8217;t play with that, but I would expect that to happen this way, because in the past, those changes were independent, but it&#8217;s a huge change. We waited for so long to make it happen. It wasn&#8217;t a trivial task, but we finally have that. And it&#8217;s a huge improvement for all users.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, definitely for new users and long time users. Yes. I probably will miss the welcome guide popping up once in a while&#8230;</p>



<p><em>Grzegorz Ziolkowski</em>: And you can always enable it. There is a setting.</p>



<h3><strong>Enhancements</strong></h3>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. So in that version also received a visualizer for the panning and margin of all blocks. So when you use the dimension settings of your block, blue outline appears on the screen around the block and expands and contracts, depending on the width of your padding and your margins. And that is really helpful for people that don&#8217;t know what padding and margins are, but they know they want the distance and they want the distance inside or outside. Yes.</p>



<p><em>Grzegorz Ziolkowski</em>: The other change was for the comment query loop. So there is a new block, which is post comments form. And the idea was to reach the alt experience. When on the post page you would have comments section, which usually is a list of comments and there is also the form. So the form was missing. And now inside the editor, you have something that isn&#8217;t interactive, but just presents a preview of what you will see on the front end. So it&#8217;s on the front end, of course, there will be interactive form that you can use to comment on the website, which is a great change. And that brings the feature priority with the old approach that we had in WordPress 5.9 with the post comments block that is now hidden from the insert it&#8217;s still there.</p>



<p>But the idea is just to combine those blocks together in the future. So depending on what you use, what the team prefers, whether the new version of the comments log which allows you to move all the pieces around the rapid with group blocks, with all the blocks you can imagine within its template. And the old one is still based on PHP functions that all team authors know from the past, you can provide your own template with template PHP file. There is a lot of hooks, all the things. So I&#8217;m looking forward to see that combined to have a full experience for all the use cases we have for the classic blocks and for the new blocks.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; No, it&#8217;s wonderful. And I, there were about 10 new blocks coming to 6.0, with a common section. And this one, unfortunately it didn&#8217;t make it, but it&#8217;s coming then in 6.1.</p>



<p><em>Grzegorz Ziolkowski</em>: No we made it, it was so important to bring the same experience that we added that, that was still during beta phase because, the release happens, but that change was already one or two weeks ago so that there was still time to include that.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Oh, okay. Excellent. So there&#8217;s a full common suite. Suite of blocks for, for the common settings for themes and templates.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It also came from user testing during beta phase that people were complaining that they cannot replicate, their old designs without this block.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. So makes sense to backboard it to 6.0 yes. So we talked about the next version of the quote block and the next version of the list blocks are in experimental stage and you have to switch them on through the experience menu item on the Gutenberg plugin. And now with this release, the quote block version one now has the feature that you can exit the block just by hitting enter we know this from other blocks that works here with the list you have to hit enter twice, out of the block and then a paragraph block and the code block has now too, before you actually had to physically get out of the block by using the mouse or hitting tab or something like that. Yeah. So that&#8217;s really good. So explain to me, Greg, I&#8217;m glad you&#8217;re here. Explain to me, so I&#8217;m at the block API section where now it&#8217;s allowing the custom domain path for the view scripts, assuming that&#8217;s through register that&#8217;s for blocks and that you can have a different path than before.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. So that&#8217;s coming, if you ever build the theme or plugin, there is this domain pet metadata field that you can provide. It&#8217;s just when you are using translations, there is a default folder for that inside every WordPress, but as an author of the theme, you can generate all the translations yourself and put it in every folder you want. So because plugin, authors and team authors use that, we added a change that allows to provide the same type of functionality when you are registering view script, it&#8217;s mostly for plugin and team authors. And when they, if they want to have some special JavaScript code that is for many blocks, they add additional functionality, then it&#8217;s going to be useful.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Excellent. So I know there was something important, but I couldn&#8217;t explain it. Thank you. What&#8217;s also in 13.2, is that the style engine now added typography and color to the back end for the editor so you can, can add it to the block styles and is it for the blocks, Jason, right?</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. As far as I know the study in gen, at least at this stage of development, it&#8217;s mostly about extracting existing code to something that in the future could evolve into something more sophisticated. So it&#8217;s more on the refactor side for now, but it&#8217;s a preparation for bigger things that we have planned for the future with having unified of way of the handing styles for blocks on the PHP and JavaScript side to ensure that it&#8217;s the same on both sides and in the future, we can do interesting things, we will cover that probably with the next release, it might be going in the next release. So one of the changes that recently landed in the Gutenburg is that because of the style in gen, you can only serve CSS styles for blocks that are actually displayed on the page, which is mind blowing that you can can think about all the savings you have because of that, because you exactly know, not only the blocks you used, but also what type of styles were enabled for those blocks.</p>



<p>And I think that&#8217;s the biggest win for this whole refactoring.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. There&#8217;s a whole discussion about, is of one of the implementation about standardizing, how themes interact with the styling of the blocks and as well as plugins. And I think that&#8217;s also necessary to standardize that in terms of when, when plugins want to introduce new blocks, they need to be able to use the variables that are introduced with the theme JSON file to just seamlessly integrate with, with an existing theme. Yeah. So what&#8217;s, I&#8217;m really sad to see that go. But what was removed was the experimental PWA support for the WP admin, which pretty much was playing around with the idea that you might get an offline and still would be able to write your post and manage your site. There was an experiment by Ella Van Durpe I think. And I think it was a good experiment, but it wasn&#8217;t pursued any further because of course, had other priorities.</p>



<p><em>Grzegorz Ziolkowski</em>: But there is PWA plugin from Google and you can also check it out and it has a lot of similar functionality but for the front end, which is also a nice thing.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Excellent. Yeah. And I will dig that up and show it in the show notes link in the show notes, the Google PWA plugin.</p>



<p><em>Grzegorz Ziolkowski</em>: Yes. And one interesting, I think from the release and being on the team, so together with Adam Janinski, we work on several improvements to the workflow of bringing code from the Google plugin to WordPress core. And we are using NPM packages as a way to share code from Gutenberg and use that directing core. And we introduce a change in workflow that is automated with GitHub actions. So if someone is using GitHub and actions that they know how powerful those tools are. And now we are tagging for the WordPress major release those packages and we can easily update all of them, by using only the distribution tax, little change in the code, but it simplifies so much things inside WordPress core and how the code is shared between those two code bases, which is quite interesting. Someone wants digging into strategies for managing deep projects. I recommend that reference.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. you should write about those little tools or little ideas that make such a difference on the release of WordPress, because I can see.</p>



<p><em>Grzegorz Ziolkowski</em>: Oh yes.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; That other people can really benefit from that. But I think it takes a little bit more strategic approach than just a PR that it has been in the release. Yeah. And the Gutenberg release. So that would be really great.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah, it&#8217;s interesting because usually the code you need to write is the easiest part because all the tools are so advanced these days, Github has APIs tools for that. And so it&#8217;s not an issue to code something. The issue is to come up with all the steps, what needs to happen after what, so it works together. So we definitely will be updating documentation for the release team for future releases, how we use the tools we improved and yeah, also for NPM packages, that&#8217;s also something I plan to write to describe how the process has changed with this release and to benefit everyone.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, definitely. So I found with the release that quite a few things have been done by the same people over and over again. Yeah. So the documentation is kind of the shortcuts for them, but if a new person would step in, then it kind of needs a little bit more flesh and strategy kind of yeah. High level information in there. Yeah. So what&#8217;s again, is there anything else in Gutenberg 13.2, we wanted to talk about? I guess that&#8217;s it for 13.2 and we are going right into Gutenberg release 13.3, that was released yesterday. Ryan Welcher wrangled the release over the finish line and posted the release notes. There are comments from 55 contributors among them with their first time contribution. Yay.</p>



<p>That&#8217;s really good. I was really amazed at the 6.0, sorry. Just digress again. Those WordPress 6.0 release was interesting that there were also 25% of the 500 plus contributors when new contributors, they had never done this before. So it was very interesting. It wasn&#8217;t, as I think previous releases 5.8 and nine were a little bit higher, but still, that&#8217;s a very high number of new contributors and&#8230;</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah, the number of contributors is really interesting thing we know for Gutenberg about people who contributed with scope. It&#8217;s now over 900 people and, it&#8217;s only code and there&#8217;s so many more people that help with testing with finding issues, trying to, provide designs, documentation. That&#8217;s a lot. And for core, we don&#8217;t know the exact number for all releases because we have core commuters. So which is a smaller group, like 60 or 70 people only. But I would love to do to get the exact number of people who ever got props for WordPress core, that would be a huge number.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, must have been in the tens of thousands of people there.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, and you said it right. It&#8217;s not only those people that commit code, but it&#8217;s also those who, who argue about the best features, how to approach it. Yeah. and comment on things or review PRs or patches. So yeah. It must be a huge number and it&#8217;s still a huge number if you also consider the people that write documentation, the people that organized meetups, the people, they alone, 780 meetups in the world. Of course, the last two years, they were a little bit crippled because of the pandemic situation, but they will come up again and organizing months over months of meet up Wordcamp meet up, Wordcamp organizers that it&#8217;s just really amazing, people that test things. There are 20 different themes on make.wordpress.org that people could join and see what they can do.</p>



<p>So if you want to do something, just a little pitch here, it&#8217;s the end user documentation team still needs writers. They triage a lot of things and all in GitHub now where you can look for the first night issues, good first issues that you could start writing and help beef up the documentation. And if you are interested in doing just that, feel free to write to me or ping me on slack or on Twitter. And I&#8217;ll have you get onboarded on that.&nbsp;</p>



<h3><strong>Gutenberg 13.3</strong></h3>



<p>Well, let&#8217;s dive into 13.3 release. So the first thing is you can now transform a cover block into a media text block and keep most of the design too. And that&#8217;s fantastic. Because sometimes you want to do that and you couldn&#8217;t. So you had to delete the cover block and start all over again.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It&#8217;s really intriguing how far you can go with transform these days and also how block adjust, because now it&#8217;s not only content, but also a lot of styles and those styles are also, taken from one place from version to another, which is quite a complex thing to do.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. I tested it in WordPress 6.0 there is this feature where you can transform from a paragraph into a quote block or a list block. And it also keeps background color and text color. And it is really amazing. Yeah. And this transformation from cover to media text did not make it, but it&#8217;s now in the Gutenberg plugin,</p>



<p><em>Grzegorz Ziolkowski</em>: I&#8217;m a little bit surprised to see that, but also it&#8217;s a great news that table of contents block is back in the Gutenberg plugin. I mean, it was disabled at some point because it&#8217;s hard to sell. I mean, it wasn&#8217;t ready for pride time for some reasons, but now it&#8217;s back and it&#8217;s still experimental. So that means it still needs some testing, but it&#8217;s really nice, especially for posts where you have a lot of headings because it automatically generates tables of contents, how the name says. And because of that, you will have a nice overview of what&#8217;s inside the post. And it&#8217;s also super handy to be able to go to the section when the post is very long. So that should have a lot of usage on some websites.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. And it automatically detects your headings and creates if they&#8217;re not already in there anchor links for them. That&#8217;s how it works. So you could also use the same anchor links if you want to link from outside of the post, into the post to a certain section. So that&#8217;s definitely a nice side effect for that. And it also does it, if you have on page breaks, it detects the heading over all the pages. And it also can jump from two headings that are on subsequent pages for that post. So it&#8217;s quite sophisticated in the feature set. One feature set that I&#8217;m actually missing is that it automatically creates the table of content as a numbered list. And I have never used a number table of content on a website. So it was always in a bullet list, but I cannot change it back into a bullet list.</p>



<p>What you have to do is to kind of create a static block out of that. And then it does a bullet list. But it does not update anymore when you add a heading. So then you have to delete it and start all over again. So that&#8217;s a little bit cumbersome, but I think I will file a feature request for that to have it as a real feature I advocated for it, but it didn&#8217;t make it in the first version. So what&#8217;s also interesting actually in this release is that the post terms, you can now add dynamic variations for custom taxonomies. So when you have the post term block, it kind of also lists every taxonomies that are registered with your site. And then the other part, what I really like is that query loop block now has a parents filter.</p>



<p>So when you&#8217;re working with, with a page, you can now use the parent filter to display content from the children of a particular parent page, which eliminates the need for a plugin again. Yeah. I think I need to count all the plugins that I have that I won&#8217;t use anymore because work has it built in, and the place on a list of the sub pages, or you can, even if you have featured images with it, you can even make some nice cards with that on the parent page and show up the next subsequent pages. At the agency. We had quite a few requests for that because some people couldn&#8217;t rock the post kind of post page thing and they always want the pages that&#8217;s so static. They never change, but you want them a different path of discovery and not just through the navigation menu, but also through imagery on the page where it can say, &#8220;okay, now you go here, then here and here and here,” it&#8217;s really interesting.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It&#8217;s also, the way query loop evolves and how many new features gets with every plugin. It&#8217;s really interesting to follow.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; So let me ask you this, are teams working, or is a team working on the idea that you have a developer ahead who wants to kind of modify the query a little bit more granular than just what you offer through the interface, kind of handled SQL statements or something like that.</p>



<p><em>Grzegorz Ziolkowski</em>: So to also support SQL, I don&#8217;t think that it&#8217;s on the roadmap mostly because it&#8217;s way too complex and you still can go and code yourself something very custom if you want to right? So it wouldn&#8217;t be that hard to replicate, maybe let me put it this way, replace the server implementation of the query loop, the wrapping block and provide your custom query from that. That&#8217;ll be much easier in my opinion than allowing users to start filling with as well and all the square injection, vulnerabilities and stuff like that.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. I hear you. It&#8217;s a small thing, but in the new version, you now have tool tips on the split border radios control. So when you&#8217;re in the sidebar work on the border radios, you actually get tool tips where you are actually working on it. Is it the top part of the border or is it the left or the right part or the bottom part? And that&#8217;s really some quality interface and you can actually have a radio separate. And I didn&#8217;t know that, it&#8217;s kind of here now. You can have a radius control just for the left border. Yeah. It&#8217;s a little round, but the other three, they don&#8217;t have a radius at all. And it makes for nice, interesting forms. Now you can do this with Gutenberg in there.</p>



<p>And I also like the color controls are now merged with a dropdown component that is a little bit more helpful. It shows when you change the background color to a gradient, it now also shows you in the sidebar when you just open it, what is the current color? And it also shows the gradient instead of just the breakdown color. And you surprised that&#8217;s not the background color that I had. It&#8217;s a gradient. And now you see it all. But the color panel has gotten quite complicated as well. With the same with you click on it and then it comes out and then you have two tabs on there, one the solid color, then the gradient color. And then in the gradient, you can then change the radius and it&#8217;s gotten quite complicated. And I can see that certain things take a little longer or need to be tested first with one block before it&#8217;s rolled out to the other blocks yeah. But that makes also for sometimes it&#8217;s not consistent over all the blocks.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. But it also makes a lot of sense to combine all those related tools into one. So the sidebar is not so overwhelming for users. So before we had many colors, if you would open that, a year ago, that would be all those things that you see now in this tool table dropdown, they were inside the sidebar, it&#8217;s just the necessary step to organize all that better.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. I like that curation of settings, then there is for each section heading for the color there&#8217;s on the right end side, sometimes a little too subtle, the three dot menu where you can also switch on and off some features. Yeah. By default, you only see the color for the text for the background, but when you click on the three dot menu, you also see that you could actually manage the link color, but it&#8217;s not offered for every block, but you can switch it on if you need it, for instance, for a quote block or for a list block. But sometimes you need to kind of really go beyond the obvious and click on that three dot menu to find additional features that you knew were there before, but now are a little bit hidden. Yeah, that is&#8230;</p>



<p><em>Grzegorz Ziolkowski</em>: Yes, but if you are a new WordPress user, I&#8217;m curious how it works, because it might take some time for people to discover that the three dots actually allows you to enable more controls or remove the controls that are there, but they don&#8217;t like.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. So the same&#8230;</p>



<p><em>Grzegorz Ziolkowski</em>: Feeling of similar changes, there is one, I would say big change because the block list, the thing you see on the sidebar, but the other side, the one we were talking was on the right side. But on the left side, you can see all the list of all the blocks that are on a given page or template. And that&#8217;s very important for the editing experience, especially for templates where there&#8217;s a lot of nesting involved. And now there is an option in your settings to show openly view as default. So before you have to click a button to open that list, but you can just dock it and it&#8217;ll be there all the time.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. I really like that, especially. Yeah, you&#8217;re right. The list view is such an integral part working with templates with all the nested blocks. Yeah. So having that open all the time really cuts down on the load time of the editor and your work workflow when you work quite a few templates or even in, on a normal post. Yeah. But I don&#8217;t think that setting is available for the post editor. I think it&#8217;s only for the site editor.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. I don&#8217;t know about that.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. It&#8217;s only for the site editor it&#8217;s post editor. Well, has that too always open list view. Yeah. So I looked at the preference tables that were in the screenshots. It&#8217;s for both the post editor and for the site editor. Yeah. A lot of people ask me about that when I demoed some of the new features. So what else do we have?</p>



<p><em>Grzegorz Ziolkowski</em>: There&#8217;s there is still no official post with all the change lock files. So we are using something that was prepared earlier. And so we might need to jump a little bit.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah.</p>



<p><em>Grzegorz Ziolkowski:</em> To find other items that we have highlighted today. And one of the change is for the heading block. And now we have font family support there. So it was available in other places now it&#8217;s been enabled there for future party.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. And a lot of people have been waiting for that our user can now change the font family for the heading block and not just the theme developer. And there&#8217;s also a enhancement for the gallery block, but especially for converting a classic block gallery into a gallery block to also include the image caption up until now it didn&#8217;t come over with it. So that&#8217;s definitely a plus for those who converting galleries to gallery blocks. Yeah. And the other two things that are highlighted here are actually part of the table of contents block. And we already talked about that. So I think we are through with that. Was there anything in the three 13.3 that you wanted to point out</p>



<p><em>Grzegorz Ziolkowski</em>: There is a lot of items as you rule in the change logs from two releases. And also we discussed work 6.0. So I think we covered a lot today.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. But we didn&#8217;t cover all and we never cover all. So dear listeners, definitely check out the change log that will be on the make.Wordpress.org blog when it comes out as a what&#8217;s new in Gutenberg 13.3. Yeah.&nbsp;</p>



<h3><strong>What’s Discussed and in the Works</strong></h3>



<p>And we are at the section, what&#8217;s discussed and what&#8217;s in the works that hasn&#8217;t been released yet? But it&#8217;s definitely top of mind and or discussed quite a bit. So there were some discussions on what keeps theme developers or agency developers who build themes for on taking, for instance, block themes or other features of the site editor.</p>



<p>So those issues come up quite a bit, not quite a bit, but once in a while, and to have some ideas on what would be good for an agency. So one of them was that made it into WordPress 6.0 was for instance, that themes could register blocks. And I think Grzegorz, you were quite instrumental in that to get it fixed or get it implemented that although the recommendation says that blocks are the territory of plugins. But we heard from agencies that we are building custom themes just for that one site implementation that had additional cost also to deploy a theme as well as blocks in plugins to make it available for them. So that was one of the discussions that came out of&#8230;</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah, also the use case was that sometimes themes require some very custom design and this is a way for them to bundle a block that just is targeting that specific theme. And it wouldn&#8217;t make sense in all, all other places. And, but yeah, it&#8217;s not the recommendation blocks belong to plugins.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, but just because it&#8217;s technically possible, doesn&#8217;t have to be, you have to use it, but it&#8217;s available for those who really, really need it. Now, before they had each agency or each freelancer who needed it, came up with their own hacks to make that. And now it&#8217;s just the standard way of using register block type on the theme PHP theme.</p>



<p>So to alleviate some of the adoption hurdles or blockers for adoption there&#8217;s now a new label on the Gutenberg rebuild called focus blocks adoption. And it&#8217;s used on the Gutenberg repo to identify those specific issues that if they would be solved, they could remove the blockers from adopting blocks or block themes. And I think it&#8217;s an interesting concept now to highlight those one of them is one issue. He got that label is by Fabien who has issues C7943 titled allow the usage of block based template parts without using block based templates. And that&#8217;s an interesting idea for classic themes that want to gradually adopt what&#8217;s possible now with the site editor also for their themes and how to implement that.</p>



<p>And part of it is already Grzegorz told me, and Ari has it in the issue is already available since 5.9. But what this particular issue is talking about that it also activate the site editor to edit those template parts without editing any other templates or sections.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. So idea was that if you have a classic theme, you can also provide a template part HTML file that will contain this template particular template part, and that worked, but you wouldn&#8217;t be able to edit that. But the proposal is to open the UI for the same, that is inside in block themes for classic themes, which is an interesting way might be a challenge. But the more we open those solutions for classic themes, the better everything becomes.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. And it follows the narrative that Matias actually had when he joined us here at the show, after he published the preliminary roadmap of 6.0, when he said that all the things that come with the block theme are not there necessarily to replace how themes work. It&#8217;s more to expand the reach that classic themes can offer to their users or the site owners. And I really like that narrative because it kind of, has that new can come in, but in piece and bits and you don&#8217;t have to adopt it completely, it&#8217;s a gradual adoption. And even in two or three years, you still have a need for classic themes, but there might be a need to open that up for some of the user controls or for the site owners controls. So yeah. Block themes are not replacing or making themes totally redundant. It&#8217;s actually opening up the whole place for new things.</p>



<p><em>Grzegorz Ziolkowski</em>: It also opens an interesting world where you have a block theme, but you&#8217;ll like it, you could switch to the classic block and still retain template parts that you build in your previous theme, it&#8217;s WordPress, everyone can do whatever they like.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. And now you can do even more and you didn&#8217;t know that you liked it. Yeah. Like gradients.&nbsp;</p>



<p>So then another discussion that came up now that 6.0 is out Matias Ventura, the lead architect also updated already some of the tracking issues. And I&#8217;m sure there is a new blog post in the making in outlining the roadmap for 6.1. But he already has a site editor and template roadmap tracking issue about 19 tasks. And that&#8217;s about the site editor and how to create template and template parts changes to the interface or updates to the interface to make it for impossible, to edit a template part properties and focus mode. What is a focus mode? It&#8217;s another way of seeing the editor. There&#8217;s also a browse mode coming to the site editor that you look at it from, you just browse the designs, but you&#8217;re not editing.</p>



<p>So yeah. And other things like restricting block editing capabilities, we talked about the block locking at the beginning of the show that comes in 6.0, and that is now that needs to be expanded on. You mentioned that it needs to be role based of course, but also you probably want to lock down the editing part of a footer or header that people can edit it. Not just remove it or move it, but also not edited that is still missing.</p>



<p>So there are quite a few in this tracking issue, hints of what&#8217;s to come. And if you&#8217;re curious, we of course share the link in the show notes and what he did for template for the site, edit 10 templates, roadmaps Matias Ventura also published a global style, ongoing roadmap that he updated. And that covers some of the style engine that we talked about. If you want to learn more about it, also the main interface for making changes to the global styles, browsing styles, without having to edit things, web fonts that would just have the web fonts for the style variations right now. But the big part of the web funds API didn&#8217;t make it into 6.0, but it will hopefully make it into 6.1.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. Also interesting discussion on Twitter where Matias were involved about the future of web phones that maybe openverse could host some web phones and having those open source version of phones, integrated with the WordPress for everyone. That&#8217;s also interesting perspective and general openverse opens so many new ways of reusing content created by other people, which is images, videos, music, and whatever&#8230; Phones. That would be another way.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, and color palettes would actually be also quite interesting. Yeah. So you can swap out the color palette of your theme and just by bringing it in from the openverse. Yeah. Oh, did you see that there&#8217;s a new contributor batch if you added photos to the openverse, to the WordPress photo directory, you can now see that on your profile. Open verse open so many different things for WordPress. It&#8217;s amazing, yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: I already have this batch. I just checked.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah me, too</p>



<p><em>Grzegorz Ziolkowski</em>: I Uploaded two photos.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. I think I uploaded four or so but yeah, it doesn&#8217;t matter. It&#8217;s a contribution and it will be honored. Yeah. So you have the site editor, the template, the global styles tracking issue. And then the last one is pattern as the section elements. That&#8217;s kind of the next phase for patterns and interesting proof of concept there&#8217;s first a tracking issue. And then James Costa has quite a few little videos and what he kind of considers as a browse mechanism for where you can browse through certain block patterns for the header, for instance, but you see the full page and that will make working on their site so much easier when you&#8217;re actually not only just looking at that section, that&#8217;s visible in your screen, but you can see the full page. And that&#8217;s also available for posts, for instance, or for pages that you create. So there are quite a few things in the works that hopefully make it.</p>



<p><em>Grzegorz Ziolkowski</em>: It, the idea for those sectioning element is really interesting. You mentioned that you can just have the recent exploration is to have zoom out mode. So, you focus on the header and then you get ways to quickly switch the versions of this header by using block patterns or maybe pre-existing template parts, and you just use arrows or something else depending, or how you use that. And how&#8217;s going to maybe implement, and it just quickly switch to another version. Another, until you find something that clicks for you, but it&#8217;s inside the page. It&#8217;s not that you open a model, then you see only just some preview of these things, but you exactly see how it fits to your website.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah, and so we will share the links to those comments and PRs in the show notes. And if you&#8217;re interested in where things are going, definitely look at those and see what it does for you. And if you have ideas, how it&#8217;s made better or what does not look right or how it can be augmented. Yeah. Chime in now is the time because now people are working on it. And the last discussion that I wanted to point out is that during the FSE program Anne McCarthy did a hallway hangout to talk about the FSE programs and how it works and all that. And then there&#8217;s an issue created or it&#8217;s not an issue, it&#8217;s a discussion post on the developer experience category on the GitHub discussions. And what the full site editing for agency use case is what are the existing features that work that are available and then what are missing features.</p>



<p>And then as well as the features that can be improved, for instance, as a missing features, it identifies the robust permission system for the template editing, as Grzegorz mentioned earlier, or another one is allow editing for only template parts or only specific template parts, but not other parts or other templates that is much more granular. Another interesting thought was that WordPress inland CSS does not always respect the editor font sizes. That might be a bug, but it could also be that some of the mechanics don&#8217;t work as well.</p>



<p>But that comes all out of a hangout meeting, which is a hallway hangout meeting is kind of an informal meeting of brains, people that discuss certain things. And this came out of it. I shared the hangout notes, hangout recap, post by Anne McCarthy, as well as this discussion at the GitHub repo. So for all you interested people. All right. So Gregorz, we are at the end of our show. I&#8217;m so glad that you were able to jump in for Mary Job this week and walk us through some of the things. Thank you so much.&nbsp;</p>



<p><em>Grzegorz Ziolkowski</em>: That was a pleasure to meet with you again and talk about Gutenberg.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yeah. And as always the listeners, the show notes will be published on Gutenbergtimes.com/podcast. And if you have questions and suggestions or news, you want us to include sent 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>. So this was it from me. Thank you for listening. Thank you for stopping by. I&#8217;m glad you were here and I will talk to you in two weeks. I say goodbye and goodbye, Greg, to you until I see you again.&nbsp;</p>



<p><em>Grzegorz Ziolkowski</em>: You for having me, Birgit. It&#8217;s always a pleasure. See you goodbye.</p>



<p><em>Birgit Pauli-Haack</em>:&nbsp; Yes. And come see us all at Wordcamp Europe. Bye bye.</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, 28 May 2022 20: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:19:"Gutenberg Changelog";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:"
	
	
	
	
	
	
";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:50:"Post Status: What’s a WordPress “Developer?”";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=98436";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:51:"https://poststatus.com/whats-a-wordpress-developer/";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:383:"It’s a good time to celebrate growth, maturity — and longevity. This is our 500th issue. WordPress is 19! And the 6.0 release is just a few days old, with new and old hands contributing from all over the world. Many are "developers" of some kind. Those who are showing up every day to make the project work and to make a living in WordPress are the professionals. Here's to them!";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, 28 May 2022 00:35:15 +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:10:"Dan Knauss";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:"
	
	
	
	
	
	
";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:28:"WPTavern: WordPress Turns 19";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=134868";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:39:"https://wptavern.com/wordpress-turns-19";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:3626:"<p>Today marks 19 years since 19-year old Matt Mullenweg partnered with Mike Little to <a href="https://wordpress.org/news/2003/05/wordpress-now-available/">release</a> the first version of WordPress based on the b2/cafelog software. The blog where he shared his thoughts on life and tech was starting to get more traffic and he wanted to ensure its future after the b2/cafelog&#8217;s main developer disappeared. </p>



<p>Mullenweg had the vision for what WordPress should be, even before it had a name. It centered on extensibility, a hallmark feature that has made the platform as popular as it is today:</p>



<blockquote class="wp-block-quote"><p>What should it do? Well, it would be nice to have the flexibility of MovableType, the parsing of TextPattern, the hackability of b2, and the ease of setup of Blogger.</p><cite>Matt Mullenweg &#8211; <a href="https://ma.tt/2003/01/the-blogging-software-dilemma/">The Blogging Software Dilemma</a>, January 24, 2003 </cite></blockquote>



<p>Although Textpattern, the interesting new publishing tool at the time, had everything Mullenweg might want in a blogging tool, he wasn&#8217;t sure about its licensing at the time. He decided to fork b2/cafelog, which lives on today in a different form as WordPress, thanks to its GPL licensing. Mike Little joined the effort and the rest is history.</p>



<p>The highlight of this year&#8217;s anniversary celebrations is the <a href="https://wp19.day/">wp19.day</a> website created by <a href="https://profiles.wordpress.org/dimensionmedia/">David Bisset</a> and his daughter<a href="https://twitter.com/lemonadecode"> Olivia Bisset</a>, who also managed the project. WordPress users and contributors from all over the world left their heartfelt greetings to celebrate the occasion. Reading through, it&#8217;s easy to get a sense of the tremendous good WordPress has done for the world, giving so many a voice, a livelihood, and a chance to live their dreams.</p>



<img />



<img />



<p>The wp19.day website also featured video submissions from WordPress enthusiasts. Although many first came for the software, the common thread among those who have stayed is the value of the community that has grown up around the project and the leadership it has cultivated. WordCamp and meetup organizer Joe Simpson said WordPress empowered him to take a leadership role in his local community.</p>



<p>&#8220;Our community here is nurturing &#8211; it&#8217;s a family,&#8221; Simpson said. &#8220;I&#8217;m excited to see where we go from here. Happy birthday, WordPress.&#8221; </p>



<div class="wp-block-embed__wrapper">

</div>



<p>Matt Mullenweg also joined in the fun of celebrating the milestone by contributing his own greeting to the wp19.day project. In his video submission, he said it&#8217;s very rare for a 19-year-old software project and its community to not just still be surviving but actually thriving and &#8220;doing better than ever.&#8221; He thanked contributors of all kinds who have helped people find their way with WordPress.</p>



Matt Mullenweg on WordPress&#8217; 19th Birthday &#8211; video source: <a href="http://wp19.day">wp19.day</a>



<p>&#8220;That is a testament to every single person who has ever told a friend about WordPress, participated on the forums, had a translation, contributed code,&#8221; Mullenweg said. &#8220;Anything that&#8217;s been part of the WordPress ecosystem is part of why WordPress is transforming the web and making it into a place that is more open, more inclusive, more democratic, and a place that we want our future generations to grow up in.&#8221;</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, 27 May 2022 22:12: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: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:8;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:54:"Post Status: WooCommerce Function of the Week: add_fee";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=98289";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:64:"https://poststatus.com/woocommerce-function-of-the-week-add_fee/";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:321:"Before we dive in this week's function, please note that it's usually against any payment provider's Terms of Service (like PayPal's) to add fees to a transaction based on the customer's chosen payment gateway, so please make sure to use &#8220;cart fees&#8221; in a legal way. You got it — in this issue we'll study...";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, 27 May 2022 21:29:47 +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:"Rodolfo Melogli";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:"
	
	
	
	
	
	
";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:72:"WPTavern: Gutenberg 13.3 Introduces Experimental Table of Contents Block";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=134845";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://wptavern.com/gutenberg-13-3-introduces-experimental-table-of-contents-block";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:1960:"<p><a href="https://make.wordpress.org/core/2022/05/26/whats-new-in-gutenberg-13-3-0-may-25/">Gutenberg 13.3</a> was released this week with support for an experimental new Table of Contents block. It is perfect for longform content that is organized by multiple headings within the document. The block automatically detects Heading blocks within the content and will display them with anchor links that jump to each section.</p>



Table of Contents block &#8211; video credit: <a href="https://make.wordpress.org/core/2022/05/26/whats-new-in-gutenberg-13-3-0-may-25/">Gutenberg 13.3 release post</a>



<p>Users may select the block without knowing how it works with headings. If the post or page doesn&#8217;t contain any headings, the block inserts a message prompting users to start adding Heading blocks in order to display a Table of Contents. </p>



<img />



<p>For sites that have registered custom taxonomies, Gutenberg&#8217;s Post Terms Block now automatically generates a block variation for each term. That means users can select a block to display all the terms associated with that custom taxonomy.</p>



<img />



<p>Other notable additions in 13.3 include the following: </p>



<ul><li>Query block now supports a &#8220;parent&#8221; filter that will display content of children from the defined parent</li><li>Heading block now supports Font Family controls</li><li>Save Block List default view preference &#8211; allowes users to set a preference for having the Blost Lick view open or closed by default</li><li>New transforms between the Cover and Media &amp; Text blocks</li></ul>



<p>The latest release also brings dozens of enhancements and bug fixes to preferences, border controls, error messages, tooling, accessiblity, and performance. Check out the <a href="https://make.wordpress.org/core/2022/05/26/whats-new-in-gutenberg-13-3-0-may-25/">release post</a> for the full list of changes.</p>



<p></p>



<p></p>



<p></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, 27 May 2022 18:21:58 +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:10;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:18:"Matt: WordPress 19";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:22:"https://ma.tt/?p=56325";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:35:"https://ma.tt/2022/05/wordpress-19/";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:1096:"<p>Today is the 19th anniversary since <a href="https://wordpress.org/news/2003/05/wordpress-now-available/">WordPress&#8217; first release</a>, which is especially exciting for a number of reasons:</p>



<ol><li>The community put together <a href="https://wp19.day/">an awesome site celebrating the occasion at wp19.day</a>.</li><li>We just had an <a href="https://wordpress.org/news/2022/05/arturo/">awesome 6.0 &#8220;Arturo&#8221; release</a>.</li><li>Next week June 2-4 <a href="https://europe.wordcamp.org/2022/">WordCamp Europe returns in-person in Porto, Portugal</a>, and I&#8217;ll be there and so excited to connect with the community! Tickets are still available.</li><li>Nineteen seems like an in-between number, but actually it&#8217;s very salient for me because now WordPress is the same age I was when the first release came out.</li><li>Which means I&#8217;ve now been working on WordPress half my life! </li></ol>



<p>Cheers and here&#8217;s to many more years together. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f942.png" alt="🥂" class="wp-smiley" /></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, 27 May 2022 18:14:23 +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:4:"Matt";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:"
	
	
	
	
	
	
";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:35:"Post Status: Post Status Notes #500";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=98171";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:45:"https://poststatus.com/post-status-notes-500/";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:17546:"<p class="has-small-font-size">By <a href="https://poststatus.com/author/dan-knauss/">Dan Knauss</a> and <a href="https://poststatus.com/author/david-bisset/">David Bisset</a> <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f5d3.png" alt="🗓" class="wp-smiley" /> May 27, 2022</p>



<div class="wp-container-1 wp-block-group has-theme-palette-8-background-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">It's the 500th issue of Post Status Notes and the Post Status newsletter coinciding with WordPress's 6.0 release and its 19th anniversary! <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f382.png" alt="🎂" class="wp-smiley" /> </p></div></div></div>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_f5fe16-0a"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="wordpress-6-0">WordPress 6.0 Released</h2>



<p><strong>WordPress 6.0</strong> &#8220;Arturo&#8221; was <a href="https://wordpress.org/support/wordpress-version/version-6-0/">released on schedule</a> (May 24th) with many new features and enhancements related to full site editing.</p>



<ul><li><strong>Gutenberg 13.3</strong> was <a href="https://github.com/WordPress/gutenberg/releases/tag/v13.3.0">released yesterday</a>. </li><li>Check out <strong>Anne McCarthy</strong>&#8216;s post on <a href="https://make.wordpress.org/core/2022/05/20/core-editor-improvement-creating-containing-containers/" target="_blank" rel="noreferrer noopener">the latest core editor improvements</a>&nbsp;to container blocks and block locking. Anne shows off some new features to explore with rows, stacks, and groups.</li><li>Anne also has <a href="https://make.wordpress.org/test/2022/05/25/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-25-may/" target="_blank" rel="noreferrer noopener">a recap</a> (video and written highlights) of yesterday's hallway hangout&nbsp;on <strong>Full Site Editing</strong> topics.</li></ul>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_39de4e-45"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="global-community">The Global Community of Contributors</h2>



<p><strong>Jean-Baptiste Audras</strong> offers <a href="https://jeanbaptisteaudras.com/en/2022/05/wp-6-0-arturo-contribution-stats/">some interesting stats for the 6.0 release</a> as he's done with six previous releases —&nbsp;<a href="https://jeanbaptisteaudras.com/en/2019/11/distribution-of-wordpress-5-3-contributors-by-country-2/">5.3</a>,&nbsp;<a href="https://jeanbaptisteaudras.com/en/2020/03/wordpress-5-4-core-contribution-statistics/">5.4</a>,&nbsp;<a href="https://jeanbaptisteaudras.com/en/2020/08/wordpress-5-5-core-stats-contributions-by-country-company/">5.5</a>,&nbsp;<a href="https://jeanbaptisteaudras.com/en/2020/12/wordpress-5-6-core-stats-contributions-by-country-company/">5.6</a>,&nbsp;<a href="https://datastudio.google.com/u/0/reporting/a496c333-7e64-412c-9299-9ea2c84e5d2c/page/j595B">5.7</a>, not 5.8, and <a href="https://jeanbaptisteaudras.com/en/2022/01/wordpress-5-9-core-contribution-statistics/">5.9</a>) so we can see compare them. Some highlights:</p>



<ul><li>519&nbsp;people&nbsp;(~25% were first-time contributors) from at least&nbsp;53 countries&nbsp;and 134 identified companies contributed.</li><li>The <strong>United States</strong>&nbsp;leads in contributions followed by&nbsp;<strong>Russia</strong>, thanks to <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey</a>, who had the highest number of individual contributions to 6.0. Then comes Jean-Baptiste himself in <strong>France</strong> and <strong>George Mamadashvili</strong> in <strong>Georgia</strong>.</li><li><strong>Automattic</strong> (with its 70 contributors) had the most contributions, followed by <strong>Yoast</strong>, <strong>Whodunit</strong> (France), and <strong>GoDaddy</strong>.</li></ul>



<p>It's interesting to see how national populations, the number of their contributors, and their total contributions are independent variables that can vary widely. <strong>Automattic</strong>&#8216;s <strong>Jorge Filipe Costa</strong> from Portugal is in the top 20 by contributions, and Portugal ranks high despite having only three contributors in all. </p>



<p>Some standout individuals, like Sergey, George, Jean-Baptiste, and Jorge do an enormous amount for the project, and there are quite a few of them! It is ultimately a community effort. </p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_b47443-2c"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="wordpress-is-19">WordPress's Last Year as a Teenager</h2>



<p><strong>Nyasha Green</strong> <a href="https://masterwp.com/olivia-bisset-on-wordpress-and-wp19/">interviewed</a> <strong>Olivia Bisset</strong> about her work on <a href="http://wp19.day">wp19.day</a>. Olivia is also an intern here at <strong>Post Status</strong>. (An enthusiastic WordPresser, coder, WordCamp speaker and volunteer, Olivia is slightly younger than WordPress itself.)</p>



<p>Newly posted to WP19.day: brief video greetings from <strong>Matt Mullenweg</strong>, <strong>Lindsey</strong> and <strong>Cory Miller</strong>, <strong>Syed Balkhi</strong>, <strong>Vito Peleg</strong>, much of the team at <strong>Yoast</strong>, and many others. </p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_899dfb-51"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="wordcamps">WordCamp Updates</h2>



<p><strong>Hari Shanker R</strong> <a href="https://make.wordpress.org/community/2022/05/23/regional-in-person-wordcamps-going-forward/">passed along the news</a> that regional <strong>WordCamps</strong> will not need to go through a proposal process anymore — they can directly apply to organize a camp for their region <a href="https://central.wordcamp.org/wordcamp-organizer-application/">using the WordCamp application form</a>. From now on, &#8220;WordCamp Central will evaluate the health of local communities when assessing a regional WordCamp application.&#8221;</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_ec3f4f-b1"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Bob Dunn</strong> has some <a href="https://dothewoo.io/woocommerce-tips-speakers-wordcamp-europe/">nice, bite-sized tips</a> on building WordPress sites from some of the speakers at the upcoming <a href="https://dothewoo.io/woocommerce-tips-speakers-wordcamp-europe/">WordCamp Europe 2022</a>.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_40cd25-29"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="giving-back">Giving Back and Looking Forward</h2>



<p><strong>Thomas Fanchin</strong> at <strong>Weglot</strong> has <a href="https://weglot.com/blog/wceu-weglot-wordpress-community/">a great post</a> about his company enthusiastically embracing <strong>Five for the Future</strong> and becoming a <strong>WordPress Global Sponsor</strong>. He notes how much there is to look forward to in events, worldwide, in 2022. </p>



<p>Weglot has been sponsoring <strong>Juan Hernando</strong>, a <strong>WCEU</strong> organizer (among other things) and now <strong>Pedro Mendonça</strong> on the core Polyglot team.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_496a58-9b"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="5ftF">What Contributions Count for Five for the Future?</h2>



<p><strong>Josepha Haden Chomphosy</strong> has taken a stab at defining <a href="https://make.wordpress.org/project/2022/05/20/defining-five-for-the-future-pledges-contributions/">activities that can be considered contributions</a> to <strong>Five For the Future</strong>, and she is looking for feedback. </p>



<p>Josepha says valid 5ftF contributions should clearly benefit the WordPress project and not an individual person or company. Contributions related to creating or supporting (third-party) WordPress themes, plugins, or blocks &#8220;are critical to extending the reach and utility of the WordPress project,&#8221; but they are also in a &#8220;grey area.&#8221; Generally they shouldn't be associated with the Five For the Future mission or count toward corporate commitments to the program. </p>



<p>In the comments, <strong>Adam Warner</strong> asked if <a href="https://make.wordpress.org/project/2022/05/20/defining-five-for-the-future-pledges-contributions/#comment-90">completely free code</a> like <strong>Contact Form 7</strong> might be worth counting, and <strong>Brian Gardner</strong> <a href="https://make.wordpress.org/project/2022/05/20/defining-five-for-the-future-pledges-contributions/#comment-91">asked</a> about contributions to the <strong>Pattern Directory</strong> with <strong>Courtney Robertson</strong> <a href="https://make.wordpress.org/project/2022/05/20/defining-five-for-the-future-pledges-contributions/#comment-94">chiming in</a> about <strong>CC0</strong> images contributed to <strong>Openverse</strong>.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_e17dc8-44"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="managed-wordpress-com">Managed WordPress(.com) Hosting Starter Plan</h2>



<p><strong>WordPress.com</strong> has launched <a href="https://wordpress.com/blog/2022/05/25/introducing-wordpress-starter-make-your-mark/">a new plan called &#8220;<strong>WordPress Starter</strong>&#8220;</a> for $5/month. It seems to be a the &#8220;in-between&#8221; option some were looking for earlier <a href="https://wordpress.com/blog/2022/04/05/introducing-wordpress-pro-one-plan-infinite-possibilities/">when the &#8220;Pro&#8221; level was first announced</a>. The &#8220;Starter&#8221; level includes custom domains, additional storage, simple payment processing, and <strong>Google Analytics</strong> to the free option.</p>



<p>Notably, <a href="https://poststatus.com/what-might-wordpress-coms-pricing-changes-mean-for-the-wordpress-ecosystem/">WordPress.com is increasingly being marketed as a web host</a> for &#8220;managed WordPress hosting,&#8221; and it can claim to be <a href="https://wordpress.com/blog/2021/06/08/fastest-wordpress-host-2021/">the fastest on the planet</a>.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_472e6e-52"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="wordpress-sustainability">WordPress and Sustainability</h2>



<p><strong>Joost De Valk</strong> explains <a href="https://joost.blog/optimize-crawling-for-the-environment/">how optimizing search engine crawling</a> can help save energy — and therefore the environment. Remember that search engines will crawl almost any URL they can find in your page source.</p>



<p><strong>Tom Greenwood</strong> shares <a href="https://opensource.com/article/22/4/zero-waste-web-design">some tips on reducing waste in web design</a>. Even if you just stop autoplaying videos, that's a start. <br /><br />Over at the <strong>Matt Report</strong>, <strong>Hanna Smith</strong> asks, &#8220;<a href="https://mattreport.com/can-wordpress-save-the-planet/">Can WordPress save the planet?</a>&#8221; </p>



<p>It's good to see these economic and ecological concerns emerging more in the WordPress space. If you'd like to take a hard look at the situation, try starting with the <strong>Stockholm Resilience Centre</strong>&#8216;s <a href="https://www.stockholmresilience.org/research/planetary-boundaries.html">Planetary Boundaries Framework</a> (CC BY 4.0).</p>



<p>One of <strong>Bill Gates</strong>&#8216; favorite authors, <strong>Vaclav Smil</strong>, is also worth <a href="https://en.wikipedia.org/wiki/Vaclav_Smil">a weekend deep dive</a>. Smil is a Czech-Canadian scientist and policy analyst on the <strong>Faculty of Environment</strong> at the <strong>University of Manitoba</strong>. His new book, <em>How The World Really Works</em>, was <a href="https://sentiers.media/notes/modern-world-cant-exist-without-four-ingredients/">summarized nicely</a> in the latest issue of <strong>Sentiers</strong> by <strong>Patrick Tanguay</strong>.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_c14da2-51"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="lean-ops">Opportunities for Lean WordPress  and WooCommerce Solutions?</h2>



<p><strong>Rob Howard</strong> asks what growth opportunities <strong>WooCommerce</strong> <a href="https://masterwp.com/what-does-shopifys-crash-mean-for-woocommerce/">might see ahead</a> as <strong>Shopify</strong> suffers a post-pandemic decline in its stock price and market share. <strong>Shopify</strong> will likely stabilize as pressure from <strong>Wix</strong>, <strong>Squarespace</strong>, and WooCommerce increases. Some would say — unfavorably — this is an &#8220;Apple-like&#8221; tactic. But Rob's right — there's an opportunity here for WordPress and Woo:</p>



<blockquote class="wp-block-quote"><p>&#8220;Let <strong>Shopify</strong>, <strong>Squarespace</strong> and <strong>Wix</strong> duke it out for the low-end market, and do everything you can to help <strong>WooCommerce</strong> corner the market for higher-end, highly custom e-commerce solutions.&#8221;</p></blockquote>



<p>There's also a good opportunity for a &#8220;build a store on a mobile device quickly&#8221; experience now.</p>



<p>Check out the new <strong>Fruits</strong> platform — <a href="https://fruits.de/">it seems to do just that</a>. </p>



<p>What if something similar existed based on <a href="https://poststatus.com/post-status-comments-wordpress-lite/">a trimmed-down WordPress install</a>? Want a full store with custom features? Click a button, and it becomes the full <strong>WordPress + Woo</strong> experience ready for customization. </p>



<p><strong>Christina Warren</strong> and <strong>Dan Knauss</strong> have <a href="https://twitter.com/post_status/status/1529962415000940544">similar thoughts</a> about a <strong>Substack</strong> or <strong>Ghost</strong>-like distribution of WordPress. </p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_b00cb9-c0"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="wordpress-job-titles">WordPress Job Titles and Skills – Where Do We Stand? (2015-22)</h2>



<p>This recent <strong>Woo DevChat</strong>, with <strong>Zach Stepek</strong>, <strong>Till Krüss</strong>, and <strong>Carl Alexander</strong> is a deep, funny, and much more thoughtful (and generously, even inclusive) take on the age-old question &#8220;What is a WordPress Developer?&#8221;</p>



<p>Ten years ago this topic was reliable clickbait for much wp-drama because it was often expressed as &#8220;who counts&#8221; or &#8220;who deserves to be called a Developer?&#8221; Will the <em>real</em> developers please stand up? Perspectives have changed and matured a lot. </p>



<p>Maybe today there is such a thing as a &#8220;No-Code Developer&#8230;&#8221;</p>



<p>Zach, Till, and Carl's conversation is <a href="https://mariopeshev.com/wordpress-job-titles-skills-stand/">reminiscent of this 2015 post</a> by <strong>Mario Peshev</strong> and the comment discussion it provoked. It's worth a read still, and so are the comments.</p>



<p>Maybe that's where Bob locked onto Site/WordPress/Woo &#8220;Builder.&#8221; I knew &#8220;Integrator&#8221; and &#8220;Customizer&#8221; would never be widely used.</p>



<p>2015 is probably about when (if not exactly where) a lot of us locked onto the inclusive but specific term, &#8220;WordPress Professional&#8221; that <strong>Jenny Beaumont</strong> introduced in the discussion over Mario's post.</p>



<p>&#8220;WordPress Professional&#8221; slid into Post Status's self-understanding too and grew to become quite central to <a href="https://poststatus.com/new-membership-options-at-post-status/">our idea of membership</a>.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_439d14-a8"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<div class="wp-container-2 wp-block-group has-theme-palette-7-background-color has-background"><div class="wp-block-group__inner-container">
<h2 id="h-do-you-enjoy-our-weekly-notes"><strong>Do you enjoy our weekly notes? </strong></h2>



<p>Get them and more in Post Status' <a href="https://poststatus.com/news/week-in-review/">Week in Review</a>. We gather WordPress and WooCommerce news along with significant writing, videos, and podcast episodes from the WordPress community and beyond. Don't miss the latest updates from the people making WordPress in our <a href="https://poststatus.com/make-wordpress/">This Week at WordPress.org</a> summaries. It's all in <a href="https://poststatus.com/newsletter">our newsletter</a>! <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>
</div></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:"Fri, 27 May 2022 16:30:11 +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:12;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"Do The Woo Community: WooBits: Happy Birthday WordPress_Community";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:28:"https://dothewoo.io/?p=71839";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:48:"https://dothewoo.io/happy-19-birthday-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:386:"<p>WordPress turns 19 today. And as I did my first draft of this podcast, I found myself redoing it. I have it all wrong.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/happy-19-birthday-wordpress/">WooBits: Happy Birthday WordPress_Community</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</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, 27 May 2022 09:09: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:5:"BobWP";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:"
	
	
	
	
	
	
";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:69:"Post Status: WordPress Podcast and Video Picks for the Week of May 22";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=98170";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/wordpress-podcast-and-video-picks-for-the-week-of-may-22/";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:3836:"<div class="has-background has-theme-palette-7-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">Catch up on the gold at Wordsesh! Mark Ashton on the success of UiPress. Hanna Smith on web sustainability. Michelle and Allie on sponsored events. Mark Root-Wiley on CSS Standards for WordPress. Takis and Taeke on organizing WCEU. </p></div>


<h2 id="h-my-podcast-picks">My Podcast Picks <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png" alt="🎙" class="wp-smiley" /></h2>



<ul><li><strong>Make Lemonade</strong>: <strong>Mark Ashton</strong> shares <a href="https://make-lemonade.simplecast.com/episodes/mark-ashton-from-uipress-fhSWcpax">his story of success</a> with his product <strong>UiPress</strong>, a plugin that provides a white label WordPress admin experience.</li><li><strong>Matt Report</strong>: <strong>Hanna Smith</strong> talks about <a href="https://mattreport.com/can-wordpress-save-the-planet/">web sustainability</a>.</li><li><strong>Underrepresented in Tech</strong>: This episode contains <a href="https://www.underrepresentedintech.com/a-conversation-about-wordpress-event-sponsorships/">a discussion about the challenges of sponsored events</a> in WordPress.</li><li><strong>WP Tavern Jukebox</strong>: <strong>Mark Root-Wiley</strong> talks about <a href="https://wptavern.com/podcast/28-mark-root-wiley-on-creating-standards-for-css-in-wordpress">creating standards for CSS</a> in WordPress.</li><li><strong>Do the Woo:</strong> Two of the <strong>WCEU</strong> organizing team members, <strong>Takis Bouryouris</strong> and <strong>Taeke Reijenga</strong>, talk about <a href="https://dothewoo.io/episode-223/">that upcoming conference</a>. </li><li><strong>Woo DevChat</strong>: <a href="https://dothewoo.io/what-is-a-wordpress-developer/">What is a WordPress Developer?</a> with <strong>Zach Stepek</strong>, <strong>Till Krüss</strong>, and <strong>Carl Alexander</strong>.</li></ul>



<h2 id="h-my-video-picks">My Video Picks <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f4fa.png" alt="📺" class="wp-smiley" /></h2>



<ul><li><strong>WordSesh</strong>: Learn the path <strong>From Agency Owner to Plugin Shop</strong> from <strong>Lesley Sim, Aurooba Ahmed</strong> describes how to <strong>Hack the Block Editor for Faster Content Creation</strong>, <strong>Vikas Singhal</strong> has <strong>5 Easy Ways to Fix your WordPress Workflow</strong>, and <strong>Leonardo Losoviz</strong> asks, <strong>Will WordPress be Better with the Block Protocol?</strong> Keynotes include <strong>Anil Gupta</strong> explaining <strong>How Big Enterprises Use WordPress for Publishing</strong>, the <strong>10up</strong> team on <strong>Rebuilding WhiteHouse.gov in Six Weeks</strong>, and <strong>Susan Enners</strong>, <strong>Matthew Haines-Young</strong>, and <strong>Wisdom HamboluI</strong> on <strong>Building and Defending a Free Press</strong>. <a href="https://wordsesh.com/recordings/">It's all there — and more</a>!</li></ul>



<div class="wp-container-5 wp-block-group has-theme-palette-8-background-color has-background"><div class="wp-block-group__inner-container">
<p><strong>Get our weekly WordPress community news digest</strong> — Post Status' <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f48c.png" alt="💌" class="wp-smiley" />  </p>



<p>And don't miss <strong>the latest updates from the people making WordPress</strong>. We've got you covered with <a href="https://poststatus.com/make-wordpress/">This Week at WordPress.org</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2699.png" alt="⚙" class="wp-smiley" /></p>
</div></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:"Fri, 27 May 2022 07:38: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: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:14;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:77:"WPTavern: Community Team Removes Red Tape From Regional WordCamp Applications";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=134814";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:88:"https://wptavern.com/community-team-removes-red-tape-from-regional-wordcamp-applications";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:4777:"<img />photo credit: <a href="https://stocksnap.io/author/worldmaps">World Maps</a>



<p>After a lengthy discussion, the Community Team has <a href="https://make.wordpress.org/community/2022/05/23/regional-in-person-wordcamps-going-forward/">decided</a> to make it easier for organizers to apply for regional in-person WordCamps. These are events that pull in a community from a geographical area larger than one city or metro area.</p>



<p>In past years, WordPress Community Support (WCS) saddled regional events with numerous <a href="https://make.wordpress.org/community/handbook/wordcamp-organizer/become-an-organizer/regional-wordcamps/">additional requirements</a> beyond regular WordCamps, such as preparing a proposal and a minimum of three cities in the region hosting local events, with at least one having hosted a WordCamp. </p>



<p>&#8220;The Community Team has decided to simplify the guidelines for regional in-person WordCamps,&#8221; Automattic-sponsored WordPress.org community manager Hari Shanker said.</p>



<p>&#8220;Moving forward, regional WordCamps will not need to go through additional steps (such as writing a proposal), and can directly apply to organize a camp for their region&nbsp;<a href="https://central.wordcamp.org/wordcamp-organizer-application/">using the regular WordCamp application form</a>.&#8221;&nbsp;</p>



<p>Shanker asummarized community feedback that influenced the decision to ease up on the requirements and move towards using common sense as guide for hosting regional WordCamps: </p>



<ul><li>Regional WordCamps could be beneficial in restarting events in a region in a post-pandemic situation. It would be a great way to revive the community.</li><li>WordCamps should be evaluated on a case-by-case basis, with conditions such as the region, geographic size, country, etc.</li><li>Successful Country-based WordCamps were held in the past, and the community team should not police event organizers based on the region. The event organizing process could be simplified.</li><li>City-based events could be difficult to organize because it’s difficult for a small group to organize a big event. It also causes repetition and a lack of repeat value for sponsors. Regional WordCamps might be a great way to solve this problem.</li></ul>



<p>Shanker emphasized that while guidelines are being simplified, it&#8217;s imperative that local meetups are presesrved when regional WordCamps are organized. </p>



<p>&#8220;Local communities offer more accessible ways to connect over WordPress, and more supportive pathways to participation in larger, more complex events,&#8221; he said.</p>



<p>Organizers who are interested in starting up regional WordCamps are encouraged to continue developing local leadership and will be required to impose a strict, two-year term limit on lead organizers.</p>



<p>More simplified guidelines for these events is particularly beneficial in Europe where many smaller countries find that regional WordCamps have a strong unifying effect for their WordPress communities.</p>



<p>&#8220;There is a reason that a &#8216;small country&#8217; like The Netherlands is now in the top of WordPress contributors and companies,&#8221; WordCamp organizer Dave Loodts <a href="https://make.wordpress.org/community/2022/03/17/discussion-revisiting-in-person-regional-wordcamps/#comment-30060">commented</a> on the previous discussion. &#8220;It all started in the lap of all the previous&nbsp;WordCamp&nbsp;The Netherlands. Never underestimate the power of these kinds of events.&#8221;</p>



<p>Shanker is requesting feedback on the proposal, particularly on what metrics should be in place to determine the health of regional communities. The proposed change has already started receciving positive feedback.</p>



<p>&#8220;Switzerland is like the Atlanta metropolitan area in term of population (8 millions vs 6 millions = &#8216;similar&#8217;) and about 10 meetup groups,&#8221; &nbsp;Geneva meetup organizer and WordCamp Switzerland co-organizer Patricia BT <a href="https://make.wordpress.org/community/2022/05/23/regional-in-person-wordcamps-going-forward/#comment-30158">commented</a>.</p>



<p>&#8220;Since we had to rename Switzerland to city name after 2015, we knew it was unrealistic to have more than one per year in the country (like if you asked people of Atlanta to have one WordCamp per meetup group) so we moved it from city to city year after year, which was awesome to onboard new organisers, but still missing a &#8216;united&#8217; event.</p>



<p>&#8220;It’s really cool that we can now go forward with WC Switzerland next year, as I feel we had lost a bit of the &#8216;Swiss community momentum.&#8217; We will recreate that feeling again next year.&#8221;</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, 26 May 2022 18:55:12 +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:15;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:59:"Post Status: Post Status Upgrade: Group Facilitation Skills";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=98118";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://poststatus.com/post-status-upgrade-group-facilitation-skills/";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:2893:"<p class="has-background">Learn new skills and build your knowledge to enhance your career in WordPress! <strong>Post Status Upgrade</strong> is an ongoing series of live workshops centered around a particular skill or learning activity.</p>



<p class="has-drop-cap">Post Status' motto — <strong>Give</strong>, <strong>Grow</strong>, <strong>Together</strong> — is more than just a phrase we repeat a lot. We live our motto. This training will give you key insights into how to facilitate group conversations with an eye to giving and growing together.</p>



<p>This is a training workshop for anyone who wants to be a facilitator or a participant in the small groups that Post Status will be rolling out soon for its members. </p>



<div class="wp-block-embed__wrapper">

</div>Group Facilitation Skills with Corey Wilks. 



<div class="wp-container-7 wp-block-group"><div class="wp-block-group__inner-container">
<div class="wp-block-image"><img src="https://cdn.poststatus.com/wp-content/uploads/2022/05/corey-wilks-150x150.png" alt="Corey Wilks" class="wp-image-98120" width="150" height="150" /></div>



<p class="has-theme-palette-8-background-color has-background">Corey Wilks is a Licensed Clinical Psychologist and Executive Coach. His mission is to help founders, creators, and entrepreneurs build an Intentional Life using evidence-based psychology.<br /></p>
</div></div>



<blockquote><p>&#8220;How do I define an Intentional Life? Spending your most precious resource—time—doing meaningful, purpose-driven work that fulfills you. It’s about clarifying your Core Value, embracing your authenticity, and reaching your potential by building your life, and your business, around what resonates with you on a fundamental level.&#8221;</p><cite>Dr. Corey Wilks</cite></blockquote>



<div class="wp-block-columns has-theme-palette-7-background-color has-background">
<div class="wp-block-column is-vertically-aligned-center">
<div id="StellarWP" class="wp-block-image is-style-default"><a href="https://poststat.us/stellarwp"><img width="300" height="300" src="https://cdn.poststatus.com/wp-content/uploads/2022/02/stellarwp-black-1-300x300.png" alt="StellarWP" class="wp-image-93207" title="StellarWP" /></a></div>
</div>



<div class="wp-block-column">
<p class="has-small-font-size"><strong>StellarWP</strong> is a collective of WordPress innovators empowering business owners and creators with plugins and tools to help them thrive. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. Our solutions include <a href="https://poststat.us/stellarwp"><strong>the most trusted names in WordPress</strong></a>, with more than 2.5 million installs. Since 2021, we’ve grown to encompass seven brands and dozens of plugins. StellarWP is part of the Liquid Web family of brands. <br /></p>
</div>
</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:"Thu, 26 May 2022 18:38:21 +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:16;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:89:"Do The Woo Community: Woo DevChat, What is a WordPress Developer with Zach, Till and Carl";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:28:"https://dothewoo.io/?p=71694";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:50:"https://dothewoo.io/what-is-a-wordpress-developer/";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:409:"<p>Zach Stepek, Till Kruss and Carl Alexander have a conversation on how and if you can define a WordPress developer. </p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/what-is-a-wordpress-developer/">Woo DevChat, What is a WordPress Developer with Zach, Till and Carl</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</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, 26 May 2022 09:33: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:5:"BobWP";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:13:"
	
	
	
	
	
	
";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:54:"Post Status: This Week at WordPress.org (May 23, 2022)";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=98186";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://poststatus.com/this-week-at-wordpress-org-may-23-2022/";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:14991:"<p class="has-theme-palette-7-background-color has-background">Each week we are highlighting the news from WordPress.org that you don't want to miss.  If you or your company create products or services that use WordPress, we've got the news you need to know. Be sure to share this resource with your product and project managers. <br /><br /><strong>Are you interested in giving back and contributing your time and skills to WordPress.org?</strong> <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://wordpress.org/support/article/contributing-to-wordpress/">Start Here ›</a><br /><br /><strong>Get our weekly WordPress community news digest</strong> — Post Status' <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — covering the WP/Woo news plus significant writing and podcasts. It's also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>



<h2 id="h-news">News</h2>



<ul><li><a href="https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-3-rc3-now-available-for-testing/"></a><a href="https://wordpress.org/news/2022/05/arturo/">WordPress 6.0 “Arturo”</a></li><li><a href="https://wordpressfoundation.org/news/2022/the-kim-parsell-memorial-scholarship-returns-for-wordcamp-us-2022/">The Kim Parsell Memorial Scholarship Returns for WordCamp US 2022</a></li><li><a href="https://make.wordpress.org/project/2022/05/20/defining-five-for-the-future-pledges-contributions/">Defining Five for the Future Pledges & Contributions</a></li><li><a href="https://make.wordpress.org/project/2022/05/23/request-for-feedback-recording-five-for-the-future-contributions/">Request for feedback: Recording Five for the Future contributions</a></li></ul>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_a98156-c2"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<div class="wp-block-columns">
<div class="wp-block-column">
<h2 id="h-accessibility"><a href="https://make.wordpress.org/accessibility">Accessibility</a></h2>



<ul><li>Request for feedback on the&nbsp;<a href="https://make.wordpress.org/project/2022/04/01/discussion-contrib-handbook-part-1/">WordPress Accessibility Statement</a>.</li></ul>



<h2 id="h-central"><a href="https://central.wordcamp.org">Central</a></h2>



<ul><li><a href="https://central.wordcamp.org/news/2022/05/wordcamp-europe-2022-is-just-around-the-corner/">WordCamp Europe 2022 is just around the corner</a></li><li><a href="https://central.wordcamp.org/news/2022/05/join-the-european-wordpress-community-in-porto-portugal/">Join the European WordPress Community in Porto, Portugal!</a></li></ul>



<h2 id="h-core"><a href="https://make.wordpress.org/core">Core</a> </h2>



<p></p>



<ul><li><a href="https://make.wordpress.org/core/2022/05/20/core-editor-improvement-creating-containing-containers/">Core Editor Improvement: Creating & containing containers</a></li><li><a href="https://forms.gle/Fv1q9arLoCbHdPcaA">Survey to hosting providers</a> from <a href="https://make.wordpress.org/core/2022/05/24/performance-team-meeting-summary-24-may-2022/">Performance team</a></li><li><a href="https://make.wordpress.org/core/2022/05/24/performance-team-meeting-summary-24-may-2022/">Performance team</a> is seeking points of contact to contribute to Site Health iniatives</li><li><a href="https://docs.google.com/document/d/1NzURb3u-KZTgYYHK9Gx_KPvSCX4N8Ci3oZfLsfVF7Tk/edit">Measurement overview doc</a></li><li><a href="https://docs.google.com/document/d/1elY0vgrLU2373mX3jSUj_vFZeGDyhED1WMPYwzSYiVA/edit">Capturing front-end performance metrics in WordPress doc</a> from <a href="https://make.wordpress.org/core/2022/05/24/performance-team-meeting-summary-24-may-2022/">Performance team</a></li></ul>



<h2 id="h-community"><a href="https://make.wordpress.org/community">Community</a></h2>



<ul><li><a href="https://make.wordpress.org/community/2022/04/22/wpdiversity-is-expanding-to-apac/"></a><a href="https://make.wordpress.org/community/2022/05/11/join-the-community-team-for-a-wpdiversity-writing-sprint-may-23-to-may-30/"></a><a href="https://make.wordpress.org/community/2022/05/23/regional-in-person-wordcamps-going-forward/">Regional In-person WordCamps Going Forward</a></li><li><a href="https://make.wordpress.org/community/2022/05/11/join-the-community-team-for-a-wpdiversity-writing-sprint-may-23-to-may-30/"></a><a href="https://make.wordpress.org/community/2022/05/20/seeking-feedback-on-annual-meetup-survey-for-2021-2022/">Seeking Feedback on Annual Meetup Survey for 2021-2022</a></li><li><a href="https://make.wordpress.org/community/2022/05/11/join-the-community-team-for-a-wpdiversity-writing-sprint-may-23-to-may-30/"></a><a href="https://make.wordpress.org/community/2022/05/20/meetup-organizer-newsletter-may-2022/">Meetup Organizer Newsletter: May 2022</a></li><li><a href="https://make.wordpress.org/community/2022/05/11/join-the-community-team-for-a-wpdiversity-writing-sprint-may-23-to-may-30/"></a><a href="https://make.wordpress.org/community/2022/05/20/wordcamp-europe-2022-contributor-day-plans-for-the-community-team-table/">WordCamp Europe 2022 Contributor Day: Plans for the Community Team Table</a></li></ul>



<h2 id="h-docs"><a href="https://make.wordpress.org/docs">Docs</a></h2>



<ul><li><a href="https://make.wordpress.org/updates/2022/05/23/documentation-team-update-may-23-2022/">Documentation Team Update – May 23, 2022</a></li></ul>



<h3 id="h-support-docs"><a href="https://wordpress.org/support/articles">Support Docs:</a></h3>



<ul><li><a href="https://wordpress.org/support/article/site-title-block/">Site Title Block</a></li><li><a href="https://wordpress.org/support/article/additional-guide-to-using-the-site-editor/">Additional guide to using the Site Editor</a></li></ul>



<h3 id="h-developer-docs">Developer Docs: </h3>



<ul><li><a href="https://developer.wordpress.org/reference/classes/wp_widget_media/reset_default_labels/">WP_Widget_Media::reset_default_labels()</a></li><li><a href="https://developer.wordpress.org/reference/classes/wp_widget_media/get_l10n_defaults/">WP_Widget_Media::get_l10n_defaults()</a></li><li><a href="https://developer.wordpress.org/reference/classes/wp_widget_media/get_default_description/">WP_Widget_Media::get_default_description()</a></li><li><a href="https://developer.wordpress.org/reference/hooks/term_exists_default_query_args/">term_exists_default_query_args</a></li><li><a href="https://developer.wordpress.org/reference/hooks/registered_taxonomy_taxonomy/">registered_taxonomy_{$taxonomy}</a></li><li><a href="https://developer.wordpress.org/reference/hooks/the_author_link/">the_author_link</a></li><li><a href="https://developer.wordpress.org/reference/classes/wp_taxonomy/get_default_labels/">WP_Taxonomy::get_default_labels()</a></li><li><a href="https://developer.wordpress.org/reference/classes/wp_taxonomy/reset_default_labels/">WP_Taxonomy::reset_default_labels()</a></li><li><a href="https://developer.wordpress.org/reference/classes/wp_post_type/get_default_labels/">WP_Post_Type::get_default_labels()</a></li><li><a href="https://developer.wordpress.org/reference/hooks/register_taxonomy_taxonomy_args/">register_{$taxonomy}_taxonomy_args</a></li></ul>



<h2 id="h-design"><a href="https://make.wordpress.org/design">Design</a></h2>



<ul><li><a href="https://make.wordpress.org/design/2022/05/23/design-share-may-9-20/">Design Share:&nbsp;May&nbsp;9–20</a></li></ul>



<h2 id="h-meta"><a href="https://make.wordpress.org/meta">Meta</a></h2>



<ul><li><a href="https://make.wordpress.org/meta/2022/04/28/proposal-make-wordpress-team-or-project-updates/">Proposal: Make WordPress Team or Project Updates</a></li></ul>
</div>



<div class="wp-block-column">
<h2 id="h-mobile"><a href="https://make.wordpress.org/mobile">Mobile</a></h2>



<ul><li><a href="https://make.wordpress.org/updates/2022/05/18/mobile-team-update-may-18th-3/">Mobile Team Update – May 18th</a></li><li><a href="https://make.wordpress.org/mobile/2022/05/17/call-for-testing-wordpress-for-android-19-9/">Call for Testing: WordPress for Android 19.9</a></li><li><a href="https://make.wordpress.org/mobile/2022/05/16/call-for-testing-wordpress-for-ios-19-9/">Call for Testing: WordPress for iOS 19.9</a></li></ul>



<h2 id="h-plugins"><a href="https://make.wordpress.org/plugins">Plugins</a></h2>



<ul><li><a href="https://make.wordpress.org/updates/2022/05/24/plugin-review-team-update-23-may-2022/">Plugin Review Team Update: 23 May 2022</a></li></ul>



<h2 id="h-polyglots"><a href="https://make.wordpress.org/polyglots">Polyglots</a></h2>



<ul><li><a href="https://make.wordpress.org/polyglots/2022/05/02/wordpress-6-0-ready-to-be-translated/">WordPress 6.0 ready to be translated</a></li></ul>



<h2 id="h-project"><a href="https://make.wordpress.org/project">Project</a></h2>



<ul><li><a href="https://make.wordpress.org/project/2022/05/23/request-for-feedback-recording-five-for-the-future-contributions/">Request for feedback: Recording Five for the Future contributions</a></li><li><a href="https://make.wordpress.org/project/2022/05/20/discussion-contrib-handbook-part-3/">Discussion: Contrib Handbook, Part 3</a></li><li><a href="https://make.wordpress.org/project/2022/05/20/defining-five-for-the-future-pledges-contributions/">Defining Five for the Future Pledges & Contributions</a></li><li><a href="https://make.wordpress.org/project/2022/04/29/discussion-contrib-handbook-part-2/">Discussion: Contrib Handbook, Part 2</a></li><li><a href="https://make.wordpress.org/project/2022/04/01/discussion-contrib-handbook-part-1/">Discussion: Contrib Handbook, Part 1</a></li></ul>



<h2 id="h-test"><a href="https://make.wordpress.org/test">Test</a></h2>



<ul><li><a href="https://make.wordpress.org/test/2022/04/28/fse-program-testing-call-14-rallying-recipe-reviewers/"><a href="https://make.wordpress.org/test/2022/05/25/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-25-may/">Hallway Hangout: Discussion on Full Site Editing Issues/PRs/Designs (25 May)</a></a></li><li><a href="https://make.wordpress.org/test/2022/04/28/fse-program-testing-call-14-rallying-recipe-reviewers/"><a href="https://make.wordpress.org/test/2022/05/24/test-test-rep-call-for-nominations-for-remaining-current-term/">Test Team Rep: Call for Nominations for Remaining Current Term</a></a></li></ul>



<h2 id="h-themes"><a href="https://make.wordpress.org/themes">Themes</a></h2>



<ul><li><a href="https://make.wordpress.org/updates/2022/05/24/themes-team-update-may-24-2022/">Themes team update May 24, 2022</a></li></ul>



<h2 id="h-support"><a href="https://make.wordpress.org/support">Support</a></h2>



<ul><li><a href="https://make.wordpress.org/support/2022/04/off-forum-support-requests/">Off forum support requests</a></li></ul>



<h2 id="h-training"><a href="https://make.wordpress.org/training">Training</a></h2>



<ul><li><a href="https://make.wordpress.org/training/2022/04/19/migrating-contributor-training-to-learn-wordpress/"></a><a href="https://make.wordpress.org/training/2022/05/03/may-2022-sprint/">May 2022 Sprint</a></li><li><a href="https://make.wordpress.org/training/2022/05/05/the-training-team-faculty-program-is-now-live/">The Training Team Faculty Program is now live</a></li></ul>



<h4>Lesson Plan</h4>



<ul><li><a href="https://learn.wordpress.org/lesson-plan/intro-to-site-editor-and-templates/">Intro to the Site Editor and Templates</a></li></ul>



<h4>Workshop</h4>



<ul><li><a href="https://learn.wordpress.org/workshop/getting-to-know-the-wordpress-dashboard/">Getting to know the WordPress Dashboard</a></li><li><a href="https://learn.wordpress.org/workshop/understanding-the-page-editor-vs-site-editor/">Understanding the Page Editor vs. Site Editor</a></li></ul>



<h4 id="h-social-learning-spaces">Social Learning Spaces:</h4>



<ul><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"></a><a href="https://learn.wordpress.org/?meeting=i-want-a-website-not-a-blog">I want a Website, not a Blog!</a></li><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"></a><a href="https://learn.wordpress.org/?meeting=bloggers-own-your-content-and-share-it-everywhere">Bloggers: Own your Content and Share it Everywhere</a></li><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"></a><a href="https://learn.wordpress.org/?meeting=hello-blocks-creating-a-custom-block">Hello Blocks! Creating a Custom Block</a></li><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"></a><a href="https://learn.wordpress.org/?meeting=design-with-me-create-a-simple-website-for-your-small-business">Design With Me: Create a Simple Website for your Small Business</a></li></ul>
</div>
</div>



<h2 id="5ftf"><a href="https://wordpress.org/five-for-the-future/">Five for the Future</a></h2>



<p>What's happening specific to Five for the Future? Provide your feedback on these posts:</p>



<ul><li><a href="https://github.com/WordPress/five-for-the-future/issues/194">Default workflow for team membership lifecycle?&nbsp;</a></li><li><a href="https://github.com/WordPress/five-for-the-future/issues/192">Add activity when Meetup organizers host events</a></li><li><a href="https://github.com/WordPress/five-for-the-future/issues/189">Update Usermeta with latest 5ftf contribution.</a></li></ul>



<div class="wp-block-spacer"></div>



<div class="wp-block-media-text alignwide is-stacked-on-mobile has-background"><a href="https://poststatus.com/"><img src="https://cdn.poststatus.com/wp-content/uploads/2021/09/vertical-post-status-logo-250.png" alt="Post Status" class="wp-image-85823 size-full" /></a><div class="wp-block-media-text__content">
<p class="has-text-align-left has-normal-font-size" id="h-get-ready-for-remote-work">You — and <a href="https://poststatus.com/business-membership/">your whole team</a> can <a href="https://poststatus.com/post-status-membership-club/">Join Post Status</a> too!</p>



<p class="has-text-align-left has-small-font-size"><strong>Build your network. Learn with others. Find your next job — or your next hire.</strong> Read the <strong>Post Status</strong> <a href="https://poststatus.com/newsletter/">newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2709.png" alt="✉" class="wp-smiley" /> Listen to <a href="https://poststatus.com/podcasts/">podcasts</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png" alt="🎙" class="wp-smiley" /> Follow <a href="https://twitter.com/post_status/">@Post_Status</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f426.png" alt="🐦" class="wp-smiley" /></p>
</div></div>



<div class="wp-block-spacer"></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:"Thu, 26 May 2022 01:00: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:"Courtney Robertson";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:13:"
	
	
	
	
	
	
";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:63:"WPTavern: WordPress.com Announces New Starter Plan For $5/Month";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=134782";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://wptavern.com/wordpress-com-announces-new-starter-plan-for-5-month";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:4495:"<p>WordPress.com <a href="https://wordpress.com/blog/2022/05/25/introducing-wordpress-starter-make-your-mark/">announced</a> a new &#8220;Starter&#8221; plan today for customers that bridges the <a href="https://wordpress.com/pricing/">pricing</a> gap between the free plan and its $15/month Pro plan. The Starter plan is $5/month and includes a  custom domain name, along with 6GB storage, and the ability to use payment collection blocks (Donations Form, Premium Content, and Payment Button).</p>



<img />WordPress.com Pricing &#8211; 5/25/2022



<p>When WordPress.com <a href="https://wptavern.com/wordpress-com-makes-major-unannounced-pricing-changes-slashes-free-storage-limits">rolled out major, unannounced pricing changes</a> on April 1, slashing free storage limits, users took to the forums to express their profound disappointment in the controversial update and the company&#8217;s lack of communication around it. After receving overwhelmingly negative feedback, WordPress.com <a href="https://wptavern.com/wordpress-com-increases-traffic-and-storage-limits-on-new-plans-after-overwhelmingly-negative-feedback-on-initial-rollout">increased traffic and storage limits</a> on the free plan before officially announcing it. </p>



<p>Seven weeks after WordPress.com began testing the waters with pricing changes, the company has responded to feedback about the wide gap between the free and Pro plans. Many customers were diappointed to learn that they would have to pay $15/month to have access to custom domain names, even though they do not need the commercial themes and plugins included in the Pro plan. Some users expressed that they felt &#8220;trapped in the net&#8221; with the pricing updates and planned to shift their sites to new platforms. </p>



<p>The new Starter plan solves some of these customer issues but it is still partially subsidized by advertising. Customers on this plan and the free plan will have ads displayed on their sites. This is different than the legacy Personal plan, which was $4/month for no ads, a custom domain, and the ability to collect payments. The fact that the new Starter plan costs more but doesn&#8217;t remove ads is a point of contention customers mentioned in the comments on the <a href="https://wordpress.com/blog/2022/05/25/introducing-wordpress-starter-make-your-mark/">announcement</a>. It does, however, include Google Analytics integration, which was previously limited to customers on the legacy Premium plan and higher.</p>



<p>&#8220;The Starter plan is not meant to be a replacement for the old legacy Personal plan,&#8221; WordPress.com CEO Dave Martin told the Tavern. &#8220;Our goal with every additional pricing iteration that we launch will be to learn something new. The Pro plan and the Starter plan are two of many future iterations that we plan to experiment with.&#8221;</p>



<p>Martin also reiterated that customers on the legacy Free, Personal, Premium, Business, or eCommerce plans are able to continue on them.</p>



<p>&#8220;[If] you are happy with your current plan, we have no plans to force you to change,&#8221; Martin said. &#8220;You can stay on your current plan.</p>



<p>&#8220;Finding the right balance between the value that we deliver to our customers and the price that we charge in exchange for that value is something that generally has to be iterated towards. We plan to do just that.&#8221;</p>



<p>Moving forward, Martin said WordPress.com is aiming to do a better job at communicating important updates to customers.</p>



<p>&#8220;I made a mistake with how we communicated the pricing changes with WordPress Pro,&#8221; Martin said. &#8220;We listened to feedback from our customers, I took responsibility for it, and then we worked to correct that with this next phase of our pricing change. We’re constantly working to be better at communicating updates.&#8221;</p>



<p>It&#8217;s interesting to see how WordPress.com is evolving its pricing in response the market and WordPress&#8217; changing capabilities. Whereas the legacy plans leaned heavily on selling access to commercial themes, full-site editing has changed the game, giving users more customization power than before.</p>



<p>The company is still planning to introduce a range of add-ons for the Starter plan to give customers more flexibility. It&#8217;s possible there will be add-ons for removing ads and adding more storage, but the company still hasn&#8217;t announced what they will offer.</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, 25 May 2022 21:54:06 +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:19;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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: #28 – Mark Root-Wiley on Creating Standards for CSS 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:48:"https://wptavern.com/?post_type=podcast&p=134775";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://wptavern.com/podcast/28-mark-root-wiley-on-creating-standards-for-css-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:61298:"<p>On the podcast today we have Mark Root-Wiley.</p>



<p>Mark builds<a href="https://mrwweb.com"> WordPress websites for nonprofits</a> in Seattle, Washington, USA with a focus on accessibility and usability. He&#8217;s a long-time<a href="https://wpseattle.org"> WordPress community member in Seattle</a> and has previously helped organise WordPress Seattle meetups and WordCamp Seattle speakers.</p>



<p>He maintains<a href="https://nonprofitwp.org"> Nonprofit WP</a>, a free guide for people building WordPress websites for their nonprofits, and has a few<a href="https://profiles.wordpress.org/mrwweb/#content-plugins"> free plugins available on WordPress.org</a>.</p>



<p>He’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards.</p>



<p>Over the years, as WordPress has evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You could do what you like, and that worked very well, after all, we all have preferred ways of doing things.</p>



<p>Now however, the reach of WordPress has outgrown those early roots and some 40+ percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites as they try to unpick the way that the CSS is built and implemented.</p>



<p>Mark thinks that it’s time for WordPress to lay out some simple standards which are easy to understand, and if they became universal, would save us a lot of time and head scratching.</p>



<p>He’s not proposing anything radical, just some basic advice for the most commonly used CSS, and it’s quite a compelling idea which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards.</p>



<p>It’s very much the kernel of an idea at present, but thought provoking nonetheless.</p>



<h2>Useful links.</h2>



<p><a href="https://mrwweb.com/standardized-design-tokens-css-wordpress-future/">Standardized Design Tokens and CSS for a consistent, customizable, and interoperable WordPress future</a></p>



<p><a href="https://github.com/WordPress/gutenberg/issues/38998">Standardized block markup, theme.json design tokens, and CSS classes to improve interoperability</a></p>



<p><a href="https://codepen.io/mrwweb/pen/bGYQKae">Variable Design Token Scales with Static CSS Classes (Proof of Concept)</a></p>



<p><a href="https://make.wordpress.org/core/2022/04/13/core-styles-and-theme-customization-the-next-steps/">Core Styles and Theme Customization: the next steps</a></p>



<p><a href="https://github.com/WordPress/gutenberg/issues/38719#issuecomment-1087145463">Explore options to add back semantic classnames to block wrappers</a></p>



<p><a href="https://github.com/WordPress/gutenberg/issues/38167">Add a Style Engine to manage rendering block styles</a></p>



Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, creating standards for WordPress&#8217;s CSS.</p>



<p>If you&#8217;d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy and paste that URL into most podcast players.</p>



<p>If you have a topic that you&#8217;d like us to feature on the podcast well, I&#8217;m very keen to hear from you, and hopefully get you all your idea featured on the show. Head over to WPTavern.com forward slash contact forward slash jukebox, and use the contact form there.</p>



<p>Before we start, I thought that I&#8217;d let you know that there won&#8217;t be an episode of the podcast next week. This is because I&#8217;m hoping to be going to WordCamp Europe. I&#8217;ll be there with my microphone, recording episodes for the coming weeks. If you&#8217;re going to be there too, it would be lovely to meet up.</p>



<p>So on the podcast today we have Mark Root-Wiley. Mark builds WordPress websites for nonprofits in Seattle, Washington with a focus on accessibility and usability. He&#8217;s a long time WordPress community member in Seattle and has previously helped organize WordPress Seattle meetups and WordCamp Seattle speakers.</p>



<p>He maintains NonprofitWP. A free guide for people building WordPress websites for their nonprofits. And has a few free plugins available on wordpress.org.</p>



<p>He&#8217;s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards. Over the years as WordPress&#8217;s evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You can do what you like, and that worked very well. After all, we all have preferred ways of doing things.</p>



<p>Now, however, the reach of WordPress has outgrown those early roots and some 40 plus percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites. As they try to unpick the way that the CSS is built and implemented.</p>



<p>Mark thinks that it&#8217;s time for WordPress to lay out some simple standards, which are easy to understand, and if they became universal would save us a lot of time and head scratching.</p>



<p>He&#8217;s not proposing anything radical. Just some basic advice for the most commonly used CSS. And it&#8217;s quite a compelling idea, which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards. It&#8217;s very much the kernel of an idea at present, but thought provoking, nonetheless.</p>



<p>If you&#8217;re interested in finding out more, you can find all the links in the show notes by heading over to WPTavern.com forward slash podcast, where you&#8217;ll find all the other episodes as well.</p>



<p>And so without further delay, I bring you Mark Root-Wiley.</p>



<p>I am joined on the podcast today by Mark Root-Wiley. Hello Mark.</p>



<p>[00:04:02] <strong>Mark Root-Wiley:</strong> Hello. Thanks for having me.</p>



<p>[00:04:04] <strong>Nathan Wrigley:</strong> You are really, really welcome. I always like to begin the podcast with a bit of orientation. I think it&#8217;s very important that the audience gets to know a little bit about our guests. Who they are, what their journey with WordPress is and so on.</p>



<p>So although the question is a little bit generic, I&#8217;m going to ask it anyway. Please, just give us a little bit of a history about yourself specifically in relation to your WordPress journey.</p>



<p>[00:04:28] <strong>Mark Root-Wiley:</strong> Awesome. Yes, let&#8217;s see. It&#8217;s been a pretty long one at this point. I am a child of the web almost. So, even back in the middle grades, I was learning to make websites. And so, it&#8217;s always been my hobby and my passion. And so when I, when I went off to college and got a degree in sociology, of course, that was much less employable than web work.</p>



<p>So, I looked around at all the systems and I had some jobs and internships where I was working with Joomla and Drupal. And so of course I ended up landing on WordPress. So since 2010, I&#8217;ve been here in Seattle, Washington where I build WordPress websites specifically for nonprofits most of the time, and so, my journey has really been that about serving clients, building custom themes doing some custom plugin work, but really like, deep in the world of WordPress for well over a decade now. And, I got to say, I love it and I&#8217;m not considering going anywhere anytime soon.</p>



<p>[00:05:19] <strong>Nathan Wrigley:</strong> Oh, that&#8217;s excellent news. Now the topic under discussion today is going to be CSS and in particular, we&#8217;re going to reference right at the beginning, an article, which was published by Justin Tadlock on February 22nd on the WP Tavern website. And it was called the case for a shared CSS toolkit in WordPress.</p>



<p>And we&#8217;re going to get into the nuts and the bolts of that in a moment because Mark, I think it&#8217;s fair to say, would like to see some kind of overhaul in the way that WordPress handles CSS. And as I say, we&#8217;ll get into what that means in a moment. But Mark, I know that you may not be able to lay out the history of CSS in WordPress perfectly for us, but clearly you believe there&#8217;s a problem.</p>



<p>I&#8217;m just wondering if you could give us any insight that you&#8217;ve got into the way that the legacy of CSS in WordPress has meant that we&#8217;ve got a problem where we are right now. What has been going on and where are we at now?</p>



<p>[00:06:15] <strong>Mark Root-Wiley:</strong> It&#8217;s such an interesting question, and I think if I had to boil it down to just one sentence answer, you know, it&#8217;d probably be there used to not be very much CSS in WordPress and now there&#8217;s a whole lot more. To really expand upon that, I think what has happened is, you know, it used to be that WordPress really only had a little bit of front-end markup that it would put out. There were things, HTML for menus, HTML for the search form, HTML for widgets and themers just sort of applied their own CSS to that.</p>



<p>Maybe in some limited cases, WordPress had a little bit of CSS that they were adding to the front, but really very little. And with the block editor, we saw the project looking to really empower users to be able to control much more design of the sites they build, through the WordPress editor interface.</p>



<p>And if you want to give people more control over the design, you&#8217;re going to be, at the end of the day, you have to do that with CSS. CSS is the language we use to make design on the web. And so it has just become much, much more complicated. And I think all software, you know, to some extent, right, it&#8217;s always evolving, but I think in our world of open source, that development process can be much messier and much more organic. And I think that that can be a benefit sometimes. But I think that maybe this is one of those instances where, right now there&#8217;s a lot of different ways for accomplishing, you know, similar types of CSS on the front end. Certain blocks handle their CSS in different ways.</p>



<p>And I think we&#8217;re just seeing that, you know, it&#8217;s been what, three or four years now of the block editor and there still isn&#8217;t really a strong opinion of sort of, this is the way that the block editor handles CSS and that has made it really hard for, people in my chair. I&#8217;m trying to make themes that are going to work every time I hit the update button on WordPress.</p>



<p>There&#8217;s just more complex CSS. There&#8217;s more of it. It&#8217;s done in varied ways. With more code comes more complexity and, it&#8217;s time to try to bring some order to that complexity.</p>



<p>[00:08:20] <strong>Nathan Wrigley:</strong> So it&#8217;s a case of the project being older than it was 15 years ago. There&#8217;s more that&#8217;s been added on top. It&#8217;s like a layer cake. We&#8217;ve had update after update, after update and things have been added in and fiddled with. We&#8217;ve had complete turnarounds in the way the interface has been put together and so on Gutenberg and all of those kinds of things.</p>



<p>And, essentially we&#8217;ve now got something which you, I think it&#8217;s fair to say, you would like to have a bit of a reset. You&#8217;d like us to rethink the way that the CSS is handled. And you&#8217;ve got some ideas around that.</p>



<p>Could you give me, before we get into the weeds of it, could you give me examples of pain points that you believe need solving? And you can be as specific as you like, you could describe a particular website that you built and a particular moment where you realized, ah, there&#8217;s things that I wish were different. So pain points that illustrate well what the problem is.</p>



<p>[00:09:12] <strong>Mark Root-Wiley:</strong> Yeah, that is such a, such a good question. I think that in some ways, the WordPress 5.9 release gave us a brief set of examples that I think made things hard for a lot of us themers. What probably looked like fairly small changes to for instance, the HTML and CSS of the cover block.</p>



<p>There was I think one class that was removed from buttons that told you about the orientation of the buttons, how they were vertically aligned. But when that was removed, suddenly all these themes that had written CSS styles where they needed to know the alignment of buttons on their site, they just stopped working because that class had been removed.</p>



<p>So rather than even really an overhaul, I think it&#8217;s a lot more about refining the practices and making a public commitment to, in the future, we are going to include classes in all of these circumstances, so that you can rely on them.</p>



<p>We are going to output all of our CSS rules with a certain specificity. It&#8217;s time for the CSS to sort of be better, organized, more consistent, and just communicated better. Which is not really an issue of code, it&#8217;s more matter of having standards for the project. If anything that&#8217;s really what I am hoping to see.</p>



<p>[00:10:24] <strong>Nathan Wrigley:</strong> You&#8217;re not the first person to suggest that this would be a good idea. It feels in the article, at least anyway, you, you make the point that you are standing on the shoulders of giants, really. And do you just want to give a shout out to some of the people who in the past have elucidated what it is that you&#8217;re trying to do? There&#8217;s several of them, but I think it might be nice to give them some credit along the way.</p>



<p>[00:10:46] <strong>Mark Root-Wiley:</strong> Absolutely. Yes. I completely agree. I hoped that when I wrote my big blog post, this proposal that I know we&#8217;re going to talk about. What I see as one of the strengths is that there&#8217;s very little original thought in it. It&#8217;s really trying to bring together all these other great ideas from other people.</p>



<p>I think it goes back to, and I think you can still find it, the theme user experience standards, or TUX that came from Automattic&#8217;s theme team. And I think they have an example we should talk about in a little while. So, I owe a lot to them. Rich Tabor, I think about two years ago had some really awesome posts about what it would mean if we could standardize how we named font sizes, how we named colors and how we handle spacing and WordPress.</p>



<p>I think that&#8217;s a critical thing that we really do want to make happen. That&#8217;s something that I would love to see. And then, I think if you&#8217;re just tooling around on GitHub and following, you know, people who are filing issues and the Gutenberg repository, or writing about it. I certainly think Matias, one of the lead developers of the Gutenberg project has written really, really smart stuff about CSS.</p>



<p>And there were also I think, a couple of like small folks I want to give shout outs to. Louis herons on Github, talked about having a theme block contract. Things that themers can count on for blocks, making that contract. I love that phrase. I think that is super important. And I think also, uh, Andrew on ocean has written about needing different layers of CSS. And I really liked that idea too.</p>



<p>[00:12:11] <strong>Nathan Wrigley:</strong> Well, thank you. Hopefully, they&#8217;ll be listening in and they&#8217;ll acknowledge your acknowledgement, which is nice. So the idea really is you want there to be some sort of overarching structure. You want there to be some sort of consistency in the way that things are handled, and that WordPress Core would make moves towards that.</p>



<p>Now this is probably something that you&#8217;re going to have an opinion on, but there are out there already, all sorts of different ways of handling CSS. Frameworks, and what have you, you know. Just off the top of my head written a couple of down here, you know, you&#8217;ve got CSS Grid and Bootstrap and so on, but I&#8217;m pretty sure that that&#8217;s possibly not the approach you want us to go down. You don&#8217;t want to bolt those into WordPress Core?</p>



<p>[00:12:52] <strong>Mark Root-Wiley:</strong> Definitely not. Yeah. I think that WordPress has never taken a really strong position on like, this is how your theme code has to be written, and if you&#8217;re going to pull in an entire CSS framework like Bootstrap or Tailwind, that&#8217;s way more opinionated. That would be very limiting to anyone who didn&#8217;t want to do things that way.</p>



<p>So, I think, when I sat down and really thought about like, what is it that I as a themer want. What it was is really baseline standardization more about just making sure that all block HTML and block CSS are done in a similar way. So that they&#8217;re, they&#8217;re sharing styles, they&#8217;re sharing CSS classes.</p>



<p>I think that there is also a ton of power if we can just standardize key styles that every site is going to need. So colors and font sizes. The amount of space between elements, things like that. But certainly not going as far as something like Bootstrap where there&#8217;s, gosh, sliders and drop down menus and modal dialogues and all those things.</p>



<p>It&#8217;s not at all about that. It&#8217;s really, I think the word I really settled on is it&#8217;s, it&#8217;s a toolkit. It&#8217;s providing more tools that all theme developers, all plug in developers, we can all use and share, but we still get to choose how we use them and how much we use them. So that, if we want to play nicely together, you know, those tools are available, but we can still choose to do things in our own way where it makes sense.</p>



<p>[00:14:18] <strong>Nathan Wrigley:</strong> We mentioned at the start that there was a WP Tavern article, which in turn was written because of something that you wrote and I&#8217;m going to include everything that we talk about today as far as possible in the show notes. But if you wish to pause this podcast and go and read Mark&#8217;s piece, it&#8217;s called standardized design tokens and CSS for a consistent, customizable and interoperable WordPress future.</p>



<p>You&#8217;re going to find that over at There&#8217;s no, no hyphens or anything like that. It&#8217;s just M R W web.com. That outlines everything that Mark is talking about. And so that really frames the conversation that we&#8217;re going to have from this moment on.</p>



<p>Now you mentioned that you wanted some sort of standardization. Presumably if that&#8217;s the case, you believe that the standardization at the moment is lacking. It&#8217;s messed up. It&#8217;s a muddle for people to create things. Everybody&#8217;s using their own different ways of doing things. Just kind of outline the specific problems about fragmentation versus standardization. What is it that you&#8217;re trying to overcome? What are the problems in Core that we&#8217;ve got at the moment? Things that need amending. Things that possibly need creating or uncreating?</p>



<p>[00:15:35] <strong>Mark Root-Wiley:</strong> Yeah. I&#8217;m going to answer your question and I think I want to like start us maybe five years in the future and then walk backwards to get there. in five years, I think we&#8217;re going to see a lot of sites that were built with the early years of the block editor.</p>



<p>Like now suddenly they&#8217;re needing to move to new themes. And so what does that look like? And, right now what we have are a lot of what I think of as kind of in the moment decisions that have been made. Both by the themer and the editor. Let&#8217;s take the theme or example first.</p>



<p>So, the block editor from day one has always allowed themers to define named font sizes, right? So, they can call them whatever they want. A lot of themers have something like small, medium, large, extra large, I know. Justin Tadlock on the Tavern posted his extensively researched list of font size names that he likes. Definitely worth a read for anyone who hasn&#8217;t seen that.</p>



<p>But I think the critical thing is that you can call them whatever you want. You can call them broccoli, apple, bicycle. You can call them seven forty, two ninety six, even if that has nothing to do with their sizes. And so what this means is that if we&#8217;re going to switch to a new theme in the future, if we switched to a theme that uses different names, all those font size settings that were set on the last version of the site are just gone. There is no bridge.</p>



<p>And so if we could agree to some like naming schemes, whether it is small through large, or even just 0 1, 2, 3, 4, 5, 6, 7. Now, when you move from one theme to another, you&#8217;re going to inherit, the choices that were made by the editors of the site, and be able to keep content as intact as possible. And right now I think the systems that the block editor is giving us are not really encouraging that consistency.</p>



<p>And it hasn&#8217;t really bitten us yet. The problems I think are coming. And so when I talk about portability of content. That&#8217;s what I&#8217;m talking about is how, what happens when we move from one theme to another. And I think that when you make that process smoother, it&#8217;s because you have good standards and that&#8217;s going to benefit everybody, working all the time.</p>



<p>[00:17:41] <strong>Nathan Wrigley:</strong> So the idea then is that things would become more standard and hopefully the community as a whole would adopt some standards.</p>



<p>Now, although we haven&#8217;t discussed this in our conversation prior to clicking record, I&#8217;m curious about your thoughts about this. Do you have any expectation that this would be something that would be, if you like, top down, in other words, would this be something which you would like to just be reflected in documentation?</p>



<p>And it&#8217;s a thing that you could use, or are you looking for a framework for CSS where really there are standards, which must be adhered to. In other words, you don&#8217;t really get to choose. If you want to be a WordPress theme in the repository, then you must do it in such and such a way. And over time, you mentioned five years in the future, we slowly encourage people to become the writers of CSS in that way.</p>



<p>[00:18:38] <strong>Mark Root-Wiley:</strong> That is such a tough question. I think that I guess I&#8217;ll say a few different things. I mean, I think that whenever possible, it&#8217;s better to use carrots than sticks. And I think that, right now in fact, I think the theme dot json standard is a great one where, if you&#8217;re building, what we&#8217;re now starting to think of is like classic themes.</p>



<p>Like you can use the theme dot json it&#8217;s on, it&#8217;s up to you and you also get like a ton of benefits by doing it. So I think that if we had standards like this, there would just be tremendous benefits to anyone who uses them, because themes would sort of work more similarly and even, there would be ways where plugins could suddenly sort of start referencing theme styles.</p>



<p>I would like to think that maybe this could bubble up, and be, you know, a community standard that people want to buy in, but aren&#8217;t forced to buy into. At the same time, I don&#8217;t know what it&#8217;s going to take to get this moving. Standardizing semantic names is something, we could talk about it forever.</p>



<p>And so I know that I personally, like I put out, in my blog post, a bunch of suggestions for the names. I thought really long and hard about them. I have my reasons. And honestly, like if someone said, nope, we&#8217;re going to use this really weird naming scheme that I don&#8217;t really care for anyway, I would use it in a heartbeat. I think having standards is more important than the specific names of them are. And so I do think that, there could be some room for some top-down decision-making here. As long as it&#8217;s a fairly simple thing, and we&#8217;re not going to punish people for not using it.</p>



<p>In WordPress land, you know, maybe that means we&#8217;re going to maybe throw some errors on occasion if you&#8217;re not using, some warnings, excuse me, not errors warnings. But no errors, nothing&#8217;s going to actually quit working.</p>



<p>[00:20:21] <strong>Nathan Wrigley:</strong> You mentioned in the piece that there are some recent issues They were obviously some kind of catalysts for you, where you thought, okay, these kinds of things are happening and it makes it pretty obvious that we need to rethink this. I&#8217;m just going to read them out, and maybe this will give some context to somebody listening to this.</p>



<p>You say to quote, recent issues make the need for a consistent, transparent approach, clear. Classes that were previously present and used by theme authors have been removed in favor of inline styles. Okay, we&#8217;ll get onto why that&#8217;s bad. Inline styles are redundant, hard to override and remove valuable selectors for theme authors. New instances of important, let&#8217;s just say that, CSS rules catch theme authors by surprise. Markup changes to Core blocks were only announced after the fact.</p>



<p>Now, I don&#8217;t know if you want to take all four of those or just riff on generally why you think these are the core things which need to be addressed, but yeah, there&#8217;s obviously something in there that sparked your interest and made you want to create this framework, if you like. Let&#8217;s just talk about that for a minute. Have you got something to say around that? What is it that you&#8217;ve found problematic?</p>



<p>[00:21:27] <strong>Mark Root-Wiley:</strong> I certainly have things to say. I suspect that honestly, maybe it was just random, how many, how many issues in 5.9 there were that sort of just got my goat as it were. I think that this is maybe one of the areas where there has already been a little bit of movement actually, which is wonderful. So yesterday, was this day when sort of all the dev notes for WordPress 6.0 showed up on the make.wordpress.org/core blog, and it included a lot of announcements about some changes to things, that are coming in WordPress 6.0. And I think that that advanced notice, already feels like, maybe some of what I&#8217;ve been saying has been heard and, and that, that is really great to see.</p>



<p>So, you know, there&#8217;s going to be some changes to like how images get aligned, the quote blocks CSS, some changes around the group block in the block editor. And, I&#8217;m really happy to see that communication. So I do think that some of these smaller things were addressed, but I also think that the fact that some classes disappeared and some markup changed and nobody knew about it, and like important CSS got added. If you ever want to like really get a bunch of people worked up about CSS, just start talking about important.</p>



<p>I think the fact that those all happened at once, I think more than any one specific issue, it just felt like, okay, there&#8217;s a lot of people changing a lot of things all at the same time and there&#8217;s no cohesive vision for we&#8217;re trying to take CSS in WordPress.</p>



<p>[00:22:47] <strong>Nathan Wrigley:</strong> Yeah. So essentially you want there to be far less surprises in the way that things are released and also to have some cohesive framework that everybody can dip into and everybody understands because it&#8217;s been well-documented and everybody can buy into it. As you said, carrot, not stick, because it just makes sense.</p>



<p>The article on the WP Tavern website had a very large amount of commentary on it. More so than anything I&#8217;ve seen in quite a while, to be honest, a lot of praise for the idea of what you&#8217;re doing. A lot of people saying, yes, we need this, we need this right now. And to develop it a little bit further, you are, you&#8217;re keen to get involved in a semantic approach.</p>



<p>Now that might not be obvious to everybody. So what does that mean? What is it you hope would come out of this? We may have a different vocabulary, in use in the end, but the idea is that we&#8217;re going to be substituting words or not as the case may be. So talk to us a little bit about that.</p>



<p>[00:23:43] <strong>Mark Root-Wiley:</strong> Yeah. I when I&#8217;m talking about semantics here, it&#8217;s really about can we establish shared meanings for some naming conventions within our CSS? So, back to the font size example earlier, if we can all agree that every time we name our font sizes, we&#8217;re going to call them small, medium, and large.</p>



<p>And every time we create our color palettes, we&#8217;re going to start with a primary color and a secondary color and maybe an accent color. Having that shared meaning, that&#8217;s what semantics are, is going to just provide so many benefits, and it&#8217;s also going to speed things up.</p>



<p>There&#8217;s going to be less mental overhead, fewer decisions that themers have to make. There&#8217;s just tons of value there. Thinking back I had mentioned that the theme user experience standards were maybe the best spiritual forbearer to this kind of point of the proposal. One of the things they recommended is when you&#8217;re naming your menu positions to call them menu one, menu two, menu three, menu four. Maybe that&#8217;s not what I would have chosen, but I started doing it and I&#8217;ve done it ever since.</p>



<p>And what it means is that any time I switched one of my themes to another themes that uses that same menu naming convention, like, the same main menu just popped up in the header, right where I would want it to be without me having to update any settings at all, just because, our themes knew how to talk to each other.</p>



<p>So it&#8217;s really about, can we make our themes and plugins talk to each other better and, ironically or, or appropriately, I think that just means we all need to do a bit more communication together in the project.</p>



<p>[00:25:10] <strong>Nathan Wrigley:</strong> Let&#8217;s get into weeds of the areas you think ought to be covered off, with some kind of framework. I keep using the word framework. I hope that&#8217;s okay. So for example, you mentioned fonts and you mentioned that the fonts might have things like small, medium, large, and that could probably extend up and down.</p>



<p>But also there&#8217;s obviously other things in CSS that we would like to cover. So before we get into nomenclature of what those things might be, let&#8217;s just talk about the things that you want to cover aside from fonts. What other things do you think are so essential that we need to have a standard that everybody just understands?</p>



<p>[00:25:47] <strong>Mark Root-Wiley:</strong> Great question. So in terms of those kinds of like standard things that we should name, I think beyond font sizes, including font weights, because if you&#8217;ve ever used a font, you know, that some have nine or now in infinite number of weights. So we need a way to sort of have a standardized font scale. Colors and gradients I had mentioned.</p>



<p>And again, that&#8217;s something where WordPress already lets us name our colors and gradients. So let&#8217;s just agree to always call them the same things. I think font families. So what are you using for your copy versus what you&#8217;re using for your heading? And then I would love to also see maybe some border widths, and probably the biggest one that I am most excited about is let&#8217;s agree on one or a few named scales for spacing.</p>



<p>So the space between blocks in a post, also the space between columns. The space between a gallery. If we can all agree on those names, then we can have a gallery with small space, a gallery with large space. And that&#8217;s just always going to look good from theme to theme, even though those values are going to be different and up to the themer.</p>



<p>[00:26:53] <strong>Nathan Wrigley:</strong> So aside from the fact that you would like to take into account things like font sizes and weights, colors, gradients, font, families, borders, spacing gaps, and so on columns and what have you. There would obviously need to be things that are associated with those, and you, you mentioned font sizes, small, medium, and large. Do you have some sort of insight into how far each of these go? Let&#8217;s for example take font sizes or weights? Well, let&#8217;s go for font sizes just for illustrative purposes.</p>



<p>How far would you like to take that, and do you have a system for making it so that it can be extendable indefinitely? So an example might be, one dash large or something like that, or XL large or something like that. Just give us a flavor of how far that scale would go down as well as up.</p>



<p>[00:27:39] <strong>Mark Root-Wiley:</strong> Yeah, that&#8217;s a good question. So I think, if it were up to me, if I were making a top-down decision, I think I would just pick a scale of numbers. Either, you know, starting at zero or going up, or maybe even centered around zero with positive and negative numbers. I like the fact that you don&#8217;t need to know English to use a scale like that, and it is infinitely scalable.</p>



<p>I think the other scaling systems that a lot of people really like is what&#8217;s often called a t-shirt sizing. So instead of small, medium and large, we would just have S M and L. And the nice thing about that one is you can infinitely go in either direction.</p>



<p>So XL, XXL, XXXL. It gets a little silly after a while, but you can do it. Some people like to say like three XL instead of XXXL. And you can do the same with XS, extra small. I will say that I think that when it comes to what WordPress should be standardizing, I don&#8217;t think it makes sense for us to say that every theme needs to have a 15 point scale for font sizes.</p>



<p>Some themes are gonna want three or five and that will be fine. I like to think of, of the 80 20 rule. 80% of needs out in the world can be satisfied by only 20% of the possible names in this case, that we could come up with.</p>



<p>So I think that for something like font sizes, a seven point scale, maybe would probably meet everybody&#8217;s needs in terms of switching from site to site, and keeping things looking pretty good. Again, to go back to sort of like why I like to think of this as a tool kit. I wouldn&#8217;t want to ever say that themes can only have seven font sizes. Right. It would just be that if they want more than that, they&#8217;re on their own to go figure that out.</p>



<p>I will say that I did, I did a lot of thinking about this even after my blog post. And there&#8217;s, there&#8217;s a demo I put together that was showing how maybe we could even have a way of having really big scales that could kind of shift down to only a three point scale, or maybe you want to have a five point scale, but it skipped 0.4. I think there&#8217;s some clever things you can do with CSS custom properties that could allow that to happen. So you can find that demo in the blog blog post.</p>



<p>[00:29:38] <strong>Nathan Wrigley:</strong> Yeah. I ran that demo. That was really useful to look at that. But let&#8217;s move on to colors and much, much more constrained there. You just want a handful really unlike font sizes, which there&#8217;s definitely more scope with colors. You just want a few basic standards that will satisfy most websites I guess?</p>



<p>[00:29:56] <strong>Mark Root-Wiley:</strong> I think that&#8217;s right. And I think that the more colors that we defined, probably the more disagreement there would be. What purpose does the fifth most important color in your palette have versus what purpose does the primary or secondary colors have in your palette?</p>



<p>And so I think that, especially for colors, I think it&#8217;s the best example where if you had a bunch of standards, they probably wouldn&#8217;t actually be that useful. So let&#8217;s just, let&#8217;s keep it simple, right? Let&#8217;s not, over-complicate this. Let&#8217;s make as few things we all need to agree on as possible. So hopefully we can actually agree on them and move forward.</p>



<p>[00:30:28] <strong>Nathan Wrigley:</strong> The font weights and the font size is obviously really dramatically changed the way a website looks. And if you switch from theme to theme and those get messed up, it really can look remarkably different. And you mentioned spacing, so gaps and columns and padding and margin and all that.</p>



<p>Again, it can really catastrophic effect things. What was a very small space can become a gigantic gulf, given a change in theme and so on, and so I was just wondered let&#8217;s ask the basic question again. What kind of constraints are you placing on that? How many different things do you think you need regarding spacing and gaps and all of that? Are we looking at dozens of different options or just three or four?</p>



<p>[00:31:06] <strong>Mark Root-Wiley:</strong> My first thought was, we probably only need maybe five, and I think that that probably would be about enough. If someone wants to do a few more than that, that would be fine. I think that spacing is maybe a really good example of the other key reason why I would love to see themes like shifting to these scales, because right now, for the most part, when an editor wants to change the spacing, of something in their posts, they can, you know, set a specific margin value or a specific padding value.</p>



<p>They can say, I want the top margin of this image to be 24 pixels. And they&#8217;re making that decision based on how their content looks in that moment, on their screen with that specific theme. Let&#8217;s say design trends again in five years are like really into white space. Maybe that 24 pixels is going to look super tiny all of a sudden. So if we can allow editors instead of having to pick a number and on the next page, they forget that they entered 24. And so they entered 20. And like now there&#8217;s just chaotic numbers all over the place. If we just say like, well, at the top of this image, I want to have a large margin.</p>



<p>Now, when they move to their next theme, it&#8217;s going to be not 24 pixels, it&#8217;s going to be whatever that is in the next theme. It&#8217;s always going to look cohesive. And so I think it&#8217;s really important to point out that it&#8217;s not just about standardizing the scales for theme developers, but I think if we provide these scales as options for customizing post content, we&#8217;re going to see editors just having to like not think so specifically, and that&#8217;s actually going to enable them to be more consistent, both in the moment and in the future, when they need to sort of switch their design.</p>



<p>[00:32:43] <strong>Nathan Wrigley:</strong> In a sense, you&#8217;ve read my mind because my next question was really about that because obviously your doing this for a living, you can probably come up with some naming system, some framework that works for you, and just keep executing that over and over again. But, that&#8217;s not the world. We live in the world where you&#8217;ll probably take over a website in a few years&#8217; time that somebody else built, and it will be littered with CSS classes and CSS styling, specific to that exact one little thing on that one page and how on earth did that happen?</p>



<p>But it did. And so you need to go back and unpick all of the problems. So there&#8217;s that. The developers amongst us have probably figured out a system for themselves over the years, and they&#8217;ve got something which works. But when you swap a website, when you go and take on somebody else&#8217;s work, the fact that there&#8217;s consistency and stability in the naming of things would really help.</p>



<p>But then you mentioned the bit, which I thought was really interesting, about the non-technical users and having things in easy to understand, non-technical language that somebody can just get a hold on and okay. All right. It would appear that that thing, okay, might not be the most obvious name in the world, but right, it does that. And it seems to do that consistently over the site. That just makes sense for end users.</p>



<p>You described them as editors, but it could be anybody touching the website who has the capability to edit things. They, they really don&#8217;t want to get involved with CSS. In fact, that&#8217;s probably their worst nightmare that they need to think about CSS. They just want a handful of things, easy to understand. A minimal array of choices. The styling decisions were made months ago, and I&#8217;m just happy to stick with them.</p>



<p>[00:34:17] <strong>Mark Root-Wiley:</strong> You probably described that bit better I ever could. And, I think it really gets to this, there are lots of strong feelings about, is WordPress maybe becoming more like a site builder? Is it forgetting about being a content management system?</p>



<p>I truly believe that I think it can be both. And I also think that a lot of the work, especially around full site editing right now, like it has that more site builder mindset. And so I do think it&#8217;s important to remember that not every person with a WordPress site wants that super, super, super fine-grained control.</p>



<p>You&#8217;re right. I work with folks that just, they are busy professionals in nonprofits in particular. A lot of the organizations I have, you know, whoever is updating the website that is a teeny tiny part of their job. It&#8217;s probably not even in their job description at all sometimes.</p>



<p>They don&#8217;t want to be thinking about pixels or ems or if they don&#8217;t even know what MSR right. Can&#8217;t I just have some large space. That&#8217;s all I want, right. And so I think that not only are there these like huge technical advantages behind the scenes, but I really do want to just call out that I think this could actually like, just bring some simplicity to the editor and like help people make good decisions without constraining them.</p>



<p>[00:35:25] <strong>Nathan Wrigley:</strong> It also provides some kind of muscle memory options as well, in that if you have been working with a WordPress website, let&#8217;s say you&#8217;re working for company A over here, and you&#8217;ve been working with a WordPress website, and you go to interview for another job and they say, have you any experience with WordPress website?</p>



<p>Yeah, that&#8217;s fine. I can do that. Then you don&#8217;t need to relearn it over on this site though. That thing does. Okay, that wasn&#8217;t quite expecting that. That&#8217;s a lot bigger than I thought. It makes the whole process of editors moving from one website to another easier as well. So it just seems like a bit of a win-win.</p>



<p>Now having said all of that, we&#8217;re 15 years plus into the project. Everybody in the comments on the Tavern article seemed to think this was a cracking idea. You seem to think it&#8217;s a cracking idea, the likes of Rich Tabor, they think it&#8217;s a cracking idea. And yet here we are talking about it as an idea.</p>



<p>What&#8217;s holding us back? What is stopping this gaining momentum if it&#8217;s such a sensible idea? Are we, is the project too limited in time? Are we concentrating on other things? You may not have the answers, but you may have some intuitions.</p>



<p>[00:36:33] <strong>Mark Root-Wiley:</strong> I guess I would start with, this is, you know, a little off the cuff, just a theory, but I do think that the block editor is written in JavaScript. And so the amount of JavaScript in the WordPress project in the last few years has just exploded.</p>



<p>To be really clear, that&#8217;s fine. You couldn&#8217;t build the block editor without that level of JavaScript. But I do think it means that a ton of the development is done. When people are thinking in terms of JavaScript, and I will say that, one thing that I&#8217;ve looked for and I don&#8217;t really feel like I&#8217;ve seen a lot of, is people sort of starting with, like, what do we want the output to look like? What is the ideal HTML and CSS to allow a user to select the margins of their images, you know, how do we want to handle that? And then build the interface that&#8217;s going to enable that.</p>



<p>It feels like it&#8217;s sort of working the opposite way. If we&#8217;re worried about what is the settings interface going to look like? And then like, we&#8217;ll figure out what the code, to make it actually work on the front end is going to be last. I do think that maybe working backwards a little bit more frequent. What CSS do we want, and now how are we going to make sure that it can be created in a sensible way? I wonder if that would help, because at least to me looking, somewhat from the outside, it doesn&#8217;t seem like folks are working that way.</p>



<p>And now having said all of that, I think it&#8217;s mostly a people and a communication problem. And I think that&#8217;s just harder than tech problems, right? Give someone an infinite amount of time and by themselves they could build the block editor on their own, but they certainly could not organize an entire community to agree on what to call font sizes.</p>



<p>That just requires folks coming together. And honestly like making compromises and, and trying to think about what&#8217;s best for the community and not just best for themselves. I think that&#8217;s really hard. I think we can do it. I think things like that have happened in the past. I do think that&#8217;s the fundamental issue and so I don&#8217;t, I don&#8217;t know exactly what&#8217;s needed though.</p>



<p>Again, that&#8217;s why I do wonder, could someone maybe make a, a bit of an executive decision on this one and, and just try to say this is happening and we&#8217;re going to be taking comments for this long, and then we&#8217;re going to make a decision and roll with it because we think the advantages to having a system are bigger than the disadvantages to any sort of, in the weeds decision that might make it through.</p>



<p>[00:38:47] <strong>Nathan Wrigley:</strong> I wonder if it&#8217;s because CSS, of all of the different parts of WordPress. The HTML and the CSS bits, they&#8217;re the easy building blocks, aren&#8217;t they? They&#8217;re the bits that a lot of people can get hold of really quickly. And with a quick flick through some kind of 1 0 1 tutorial, you can get yourself up and running with the basics of font sizing and padding and margins and, and quickly gain an understanding of it.</p>



<p>And so everybody&#8217;s been left to their own devices on that. The theme may very well take care of all of that, of all of that for you. And you may need to adjust absolutely nothing. You&#8217;re entirely happy with the theme and you don&#8217;t dabble. But if on that one particular occasion, you just wished to change that one particular thing you want the, I, don&#8217;t know, the, the heading to be slightly bigger, you just fiddle about and locate the CSS for that and modify it, add something to a style sheet, so on. And it&#8217;s fairly straightforward and it can be done by more or less anybody on their own, but it doesn&#8217;t require any consistency. Naming what you like so long as it works.</p>



<p>But your approach is, is slightly different. And yeah, it feels as if maybe it&#8217;s not got the momentum at the moment, but it feels like, you know, maybe with things like this happening, your initiative happening, people talking about it more, maybe somebody could take this on. And as you say, maybe at some point it does need somebody on high to make a decision executively and say, okay, we&#8217;re going to concentrate on this and it&#8217;s going to become important. But I don&#8217;t know that any of that is in the roadmap right now. So you may need to keep banging the gong for a little bit longer I think.</p>



<p>[00:40:23] <strong>Mark Root-Wiley:</strong> I actually, you know, I, I played a lot of percussion growing up, so I love banging a good gong. One thing I noticed is, you mentioned the number of comments on the Tavern post, I certainly got a few comments on my blog post and I published a, sort of a Github issue that the sister of the blog post and it got a lot of comments and, and I do think people are listening.</p>



<p>I&#8217;m not sure what&#8217;s required to sort of get some action steps. But, I will say that, what really made me think that, yes, I, I do think people are listening at this moment is there was a blog post, at this point, I think about a month ago, on the make wordpress.org/core blog called core styles and theme customization, the next steps.</p>



<p>The gist of that post is basically like here&#8217;s a bunch of links to get hub issues, please go read them and leave your feedback. The speed of change in an open source project is never going to be what we want it to be. And I really do try to always remember that when I&#8217;m feeling impatient, which is certainly why I wrote this whole thing.</p>



<p>But I do think that, it is important for folks to always be paying attention, always be sharing their mind, because I do think, at some point, especially if a lot of us keep talking about this, like some decisions will get made. And so, you know, make sure if you&#8217;re interested in this, make sure to go leave some comments on, on these issues and keep bumping them up so people can see that they are high priority for a lot of us in the community. I know it&#8217;s not just me.</p>



<p>[00:41:42] <strong>Nathan Wrigley:</strong> Yeah, it was quite interesting. The article that you mentioned, the core styles and theme customization, the next steps I was highlighting the bits that were basic replications of everything that you were saying. And quite a lot of the article got highlighted. Let&#8217;s put it that way. So it would seem that, on some level, there is movement here and people are definitely in agreement with you.</p>



<p>Do you have any insight into how this might get revved up and get more interest attached to it? In other words, are you willing to put your best foot forward and become somebody in the vanguard? Like I said, banging the gong. Or do you find that there&#8217;s probably a better way of, have you got any insights into where people could go if they agree with you and want to get involved to make this happen?</p>



<p>[00:42:25] <strong>Mark Root-Wiley:</strong> Gosh, it takes everyone in the community weighing in, I think that. One thing I&#8217;ll say is that, you know, I tried to get a lot of people to review my blog post and, even gives me advice on like, how should I publish it and who should I let know about this?</p>



<p>Cause I think that if it&#8217;s just me it&#8217;s ineffective. It does need to be a community. And so, you know, I would say I would love to see other people sharing their own proposals even. I don&#8217;t know. I don&#8217;t even know if you want to include this part, I don&#8217;t think it can just be me.</p>



<p>I it&#8217;s pretty silly actually. I published this blog post and then 24 hours later, we had a new baby. I definitely had to fall off the face of the earth and disappear for a while, but I was so thrilled to see other people, saying like, yeah, this is awesome. And here&#8217;s the couple of things I have to add.</p>



<p>[00:43:08] <strong>Nathan Wrigley:</strong> There&#8217;s a whole lot towards the end of the article where you outline the different problems that your solution may solve. I won&#8217;t list them all now, but all of it kind of makes common sense to me. One can only hope that the ideas that you&#8217;ve suggested go forwards and that people, as a community, can coalesce and come up with an idea.</p>



<p>And as you said, you&#8217;re not bound to any one particular way of doing it. It&#8217;s just the mere idea of standardizing things, whether it be named this or that is not important, it would just be nice to have some standard documented that everybody can adhere to and therefore make it a lot easier for all of us to make websites, whether we&#8217;re building them for clients or we&#8217;re just editing and tweaking them ourselves.</p>



<p>One of the concerns that we may have is the stability of WordPress CSS in the future. And I know that you have possible concerns that in the future, for example, Gutenberg blocks, there&#8217;s no requirement for the CSS, the classes, and so on to be the same today as it will be tomorrow or indeed yesterday.</p>



<p>So in other words, is that a problem, do you think? Is there any problem of consistency where let&#8217;s say that you build something and you ship It, and it goes out to your client. It&#8217;s using blocks, but suddenly unbeknownst to you, the blocks CSS classes all get modified, perhaps ever so slightly, but enough to break things. Is that a concern that you have?</p>



<p>[00:44:36] <strong>Mark Root-Wiley:</strong> It really is. And I think that this is one of the biggest things I sort of learned from this intense period of engagement I&#8217;ve been having with the project is that, in discussing this with other people and really closely going through, uh, lots and lots of issues and the Gutenberg Github repository. I found some core development team members really saying that they viewed the HTML markup and the classes and how the CSS has written as essentially like non-public, which is to say you can&#8217;t count on this stuff not changing in the future.</p>



<p>That was really shocking to me. And I think for a couple of reasons, I mean, th the first is that, you know, that&#8217;s never how it&#8217;s been in WordPress in the past. The HTML for the comment forum, the HTML for the search forum, like those weren&#8217;t always seen as, you can count on this, there are ways to change it if you need to, but if we&#8217;re going to change this stuff, it&#8217;s going to be a huge deal and you&#8217;ll hear about it in advance, and we&#8217;re really gonna try to avoid that.</p>



<p>And so it felt like, uh, that was a departure from how things had previously been. And also as I&#8217;m someone who I think follows the project, like more closely than average, even though I, you know, I&#8217;m certainly not like a day-to-day contributor, or anything, but this was huge news to me as someone who&#8217;s been working with the block editor for years now.</p>



<p>At least to me, I don&#8217;t even really know that it&#8217;s reasonable to just say that like, well, here&#8217;s a bunch of HTML and CSS. Themers I know you have like your job to do and you need to make changes to this, but like, you can&#8217;t count on it. That doesn&#8217;t really seem fair.</p>



<p>And I certainly don&#8217;t think people are really aware of that. They&#8217;re not going to go in and one day, you know, completely change the image block or the block quote block drastically. I don&#8217;t really think they mean we&#8217;re going to just completely change everything. But I do think it just highlights the need again, to really spend some time focusing on what is the HTML that can serve as best going forward. So we don&#8217;t need to change it.</p>



<p>What are the CSS classes and the ways of handling CSS styles that we want to commit to now so that we can all just know what&#8217;s coming in the future. And so that when there are changes made, they are a big deal, and people are given lots of advance warning and they can, they can react.</p>



<p>And so I think I&#8217;m seeing more advanced warning in WordPress 6.0, which is awesome. It&#8217;s time to have that conversation about how can we just reduce the number of times we need to make big changes like that. Cause people are going to style HTML, no matter what.</p>



<p>[00:46:58] <strong>Nathan Wrigley:</strong> Yeah. I wonder if it&#8217;s a product of the fact that the block editor is now basically a conduit to put in lots and lots of little components. So you might have a paragraph block and you might have a, an image block or a cover block or whatever it might be. You&#8217;ve got all of these different blocks and the functionality of that is not yet a hundred percent certain. In other words, aspects of it could change. And so I wonder if them communicating CSS will change is a product of that. They&#8217;re just not sure exactly what those blocks will look like in a few years time. And if they become radically different, maybe the functionality changes. Let&#8217;s hope it doesn&#8217;t. I&#8217;m sure it won&#8217;t, but if it did, some of the CSS may need to change. I don&#8217;t know.</p>



<p>[00:47:42] <strong>Mark Root-Wiley:</strong> I think you&#8217;re right on the money there. I mean, the block editor is so much more powerful and I want to be really clear that like, that&#8217;s awesome. Like the folks I work with generally, like love that they can do more complex things like columns, or like finally putting text on top of an image for the cover block.</p>



<p>Those are good things. And we had to have a more complex system to make that possible. So I&#8217;m not against the complexity, but I just think it&#8217;s really important that the folks who are building the product, don&#8217;t forget about those of us in the real world who, you know, have to make things work every day. And we have, we have new sites we&#8217;re constantly working on, the impact of even what can seem like a really tiny change can be really big.</p>



<p>To bring it all back around, I really do think that if we can have just a few more standards and right, if we can have that kind of contract between themes and blocks, I think we can reduce the amount of times that those kinds of changes happen.</p>



<p>I totally acknowledge that they&#8217;re going to have to happen every once in a while. If we want to have this like big, nice thing, we&#8217;re going to have to put up with probably more changes. Cause there&#8217;s more things that can change, but, let&#8217;s really, let&#8217;s take a minute and figure out how we can make that as infrequent unpainful as possible.</p>



<p>[00:48:51] <strong>Nathan Wrigley:</strong> Yeah. It&#8217;s interesting your language there. You described it as a big, nice thing. And in a sense it&#8217;s a big, nice thing made up of lots of smaller little nice things. Each of those little nice things is completely independent. And you may not use those on your website, but you may.</p>



<p>And if there&#8217;s modifications made to the CSS classes and what have you, the downstream effect could be pretty catastrophic. You know, if you&#8217;ve just built 50 websites and they&#8217;re all using the exact same block and some tiny little change affects you 50 times, that&#8217;s suddenly created a lot of work for you that potentially was not even thought about elsewhere.</p>



<p>[00:49:27] <strong>Mark Root-Wiley:</strong> It has. In some extreme cases, this is maybe the reason why some people are often building custom blocks that really they could just be using the core block, but I&#8217;ve, I&#8217;ve at least anecdotally heard that folks do that sometimes because they know that their block isn&#8217;t going to change, even if they don&#8217;t want to have to take the time to build it.</p>



<p>[00:49:44] <strong>Nathan Wrigley:</strong> If people Mark wants to find you. They want to actually reach out to you. You may wish to share a Twitter handle or a website or an email address. Totally up to you. Yeah, any place that you could be found if people are inspired to join you?</p>



<p>[00:49:58] <strong>Mark Root-Wiley:</strong> Yes. I am M R W web pretty much everywhere. So that&#8217;s, uh, MRW web with two W&#8217;s, uh, I&#8217;m MRW web.com. I&#8217;m M R W web on GitHub and Twitter and in the WordPress Slack and Post Status Slack. All these other places. I have a highly Googleable namee. If you want to come find me, I would love to hear from you I&#8217;m. I am not that hard to find.</p>



<p>[00:50:23] <strong>Nathan Wrigley:</strong> Well, Mark, thank you very much for being on the podcast today. I really appreciate.</p>



<p>[00:50:28] <strong>Mark Root-Wiley:</strong> Thanks so much for having me. This was a blast Nathan. Great, great questions. I got to say.</p>
</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:"Wed, 25 May 2022 14:15:05 +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:"Nathan Wrigley";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:20;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:83:"Do The Woo Community: dev_life snippet: Timing the Perfect Follow-up Customer Email";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:54:"https://bobwp-com.e73eumvj-liquidwebsites.com/?p=26034";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:64:"https://dothewoo.io/timing-the-perfect-follow-up-customer-email/";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:442:"<p>Although as a WooCommerce builder, you likely don’t sell fish, but here is a story to get you thinking creatively about follow-up emails. </p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/timing-the-perfect-follow-up-customer-email/">dev_life snippet: Timing the Perfect Follow-up Customer Email</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</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, 25 May 2022 02: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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";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:21;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:108:"WPTavern: WordPress 6.0 “Arturo” Adds More Templates and Patterns, Style Switching, and Block Locking UI";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=134698";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:111:"https://wptavern.com/wordpress-6-0-arturo-adds-more-templates-and-patterns-style-switching-and-block-locking-ui";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:6321:"<p><a href="https://wordpress.org/news/2022/05/arturo/">WordPress 6.0</a> &#8220;Arturo&#8221; was released today, named for Latin jazz musician and director <a href="https://en.wikipedia.org/wiki/Arturo_O'Farrill">Arturo O’Farrill</a>, who has 15 albums to his credit.</p>



<p>Check out the official release video for a quick overview of some of the most important changes.</p>



<div class="wp-block-embed__wrapper">

</div>



<p>This release introduces sweeping improvements to the block editor and its utilities and design tools. Most notably, users can now <a href="https://wptavern.com/text-selection-across-multiple-blocks-is-coming-to-wordpress">select text across multiple blocks</a>, manipulating the highlighted portion as a group while keeping the rest of the content blocks in tact.</p>



<img />image credit: <a href="https://make.wordpress.org/core/2022/04/14/whats-new-in-gutenberg-13-0-14-april/">Gutenberg 13.0 Release Post</a>



<p>The List View has been updated to offer a more intuitive display that helps with navigating blocks on a page. Select multiple blocks using keyboard shortcuts, make changes, and drag-and-drop inside the list. List View is closed by default but will expand to the current selection when a block is selected.</p>



<img />image credit: wordPress 6.0 About Page



<p>WordPress 6.0 also introduces a <a href="https://wptavern.com/wordpress-6-0-to-ship-new-block-locking-feature">new interface for locking blocks</a>, which allows useres to prevent blocks from being moved or removed. It is useful for preventing accidental edits but also for theme developers who want to prevent users from removing blocks inside templates, preserving more complex layouts.</p>



<img />image credit: WordPress 6.0 About Page



<p>Other block editor improvements include the following:</p>



<ul><li>New Blocks: Avatar, Post Author Biography, Read More, Comments Query Loop, and Stack block</li><li>Type two open brackets <code>[[</code> to quickly access the link menu</li><li>Improved support for preserving unrecognized content in the editor</li><li>Preserve existing styles transforming blocks from one kind to another—from a Paragraph block to a Code block, for instance</li><li>New block style transformation options: Tag Cloud > Categories, Calendar > Archives, Paragraph > Code, and Group > Row</li><li>Create customized buttons and any new buttons will retain the style customizations automatically</li><li>New drop-down based color picker UI</li><li>Make tag clouds and social icons more appealing with updated settings and controls, and a new outline style for the tag cloud</li><li>Instant block style previews</li><li>Featured images <a href="https://wptavern.com/featured-cover-blocks-and-the-future-of-binding-data-to-generic-wordpress-blocks">now available in Cover block</a></li><li>New border controls for more precise control when setting borders</li><li>Transparency levels for colors offers more creative control</li></ul>



<p>WordPress 6.0 also introduces a gaggle of new layout controls for page building. Users can now control gaps, margins, typography, and more on multiple blocks inside a Group block. Creating layouts is easier with the ability to position groups of blocks by quickly switching between stack, row, and group variations. The Gallery block is now more flexible with gap support for custom spacing. </p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Biggest stuff is in the editor itself, and there are many minor but big updates facing the end-user like how: <br /><br />&#8211; we no longer have to rely on group block for block spacings<br />&#8211; we now have row block for horizontal stuff<br />&#8211; visual aids getting better and better.</p>&mdash; Onur Oztaskiran (@onuro) <a href="https://twitter.com/onuro/status/1528897439876497408?ref_src=twsrc%5Etfw">May 24, 2022</a></blockquote>
</div>



<h2>Full-Site Editing Updates: More Templates, More Patterns, and Style Switching</h2>



<p>Patterns are now available in more places and better integrated with the Site Editor. <a href="https://make.wordpress.org/core/2022/03/02/whats-new-in-gutenberg-12-7-2-march/">Gutenberg 12.7</a> brought major improvements to the patterns experience by making them easier to discover. The block inserter has been updated to display patterns, as opposed to blocks, when users are editing a template in the post or site editor. It also favors showing patterns when the inserter is at the root level or the content being inserted is between other blocks. WordPress will now show existing template parts, as well as block patterns in the template creation process. </p>



<img />image credit: WordPress 6.0 About Page



<p>Theme authors can now <a href="https://make.wordpress.org/core/2022/05/02/new-features-for-working-with-patterns-and-themes-in-wordpress-6-0/">register patterns from the official Pattern Directory using theme.json</a>, so that users have quick access to patterns the author has highlighted.</p>



<p>WordPress 6.0 introduces five new template options for full-site editing: author, date, categories, tag, and taxonomy. </p>



<p>One of the most anticipated features of this release is the Style Switcher. It allows userse to apply quick style changes within the same theme, and includes the ability to further edit the font weight, style options, and color palette. </p>



<img />



<p>Theme authors can <a href="https://make.wordpress.org/core/2022/05/03/global-styles-variations-in-wordpress-6-0/">create multiple different theme.json style variations</a> and place them into their themes&#8217; <code>/styles</code> folder. Users will then see the styles under the Styles menu in the top toolbar of the site editor.</p>



<img />



<p>WordPress 6.0 is the product of collaboration from more than 500 contributors in 58+ countries. It introduces more than 1,000 updates and bug fixes, including many that make the platform more performant and accessible.  </p>



<p>Check out the <a href="https://make.wordpress.org/core/2022/05/03/wordpress-6-0-field-guide/">6.0 Field Guide</a> and the <a href="https://wordpress.org/support/wordpress-version/version-6-0/">release notes</a> for a more detailed look at all the changes in the latest release.</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, 24 May 2022 20:29:58 +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:22;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:46:"WordPress.org blog: WordPress 6.0 “Arturo”";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=12879";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:42:"https://wordpress.org/news/2022/05/arturo/";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:52729:"<img width="4161" height="2822" src="https://i2.wp.com/wordpress.org/news/files/2022/05/Main-image-News-post.png?fit=4161%2C2822&ssl=1" alt="WordPress 6.0 Arturo" class="wp-image-12919" />



<h2>Welcome to &#8220;Arturo&#8221;</h2>



<p>Say hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, <a href="https://en.wikipedia.org/wiki/Arturo_O'Farrill">Arturo O’Farrill</a>. Known for his influence on contemporary Latin jazz, Arturo has pressed more than 15 albums spanning a body of work across five decades.&nbsp;</p>



<p>Take some time to explore WordPress 6.0, built to help you unlock your creative aspirations and make your site-building experience more intuitive. And check out some of Arturo’s inspirational sounds that span Afro Cuban jazz, contemporary Latin jazz, and so much more.</p>



<p>With nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. <a href="https://wordpress.org/wordpress-6.0.zip">Download it now</a>! As of today, WordPress powers more than 42% of websites worldwide.<sup><a href="https://wordpress.org/news/feed/#footnote">1</a></sup></p>



<p>Site owners and administrators should upgrade to take full advantage of the many stability, performance, and usability enhancements today. WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.</p>



<blockquote class="wp-block-quote"><p>Expanding Gutenberg into a full site editing experience in WordPress means that all of the problems the community had to address were complex and far-reaching. WordPress 6.0 is an example of the community’s commitment to tackling these tough challenges together. With thoughtful updates to the writing experience, building better block functionality, and adding a new intuitive style switcher, I’m really proud of the work that’s been done in this release to make a great site editing experience.</p><cite>Josepha Haden Chomphosy, Executive Director</cite></blockquote>



<div class="wp-container-1 wp-block-buttons">
<div class="wp-block-button"><a class="wp-block-button__link" href="https://wordpress.org/wordpress-6.0.zip">Download WordPress 6.0</a></div>
</div>



<h2>What’s Inside</h2>



<img width="1204" height="700" src="https://i2.wp.com/wordpress.org/news/files/2022/05/Writing-Improvements-1.png?fit=1204%2C700&ssl=1" alt="Selecting multiple lines of text from two blocks" class="wp-image-12887" />



<h3>Enhanced Writing Experience</h3>



<p>Writing improvements abound, whether you’re writing a brand new post or adding elements to an existing page. Explore more ways to streamline your content creation process, including:</p>



<ul><li>Select text across multiple blocks for easier copying and pasting.</li><li>Type two open brackets `<code>[[</code>` to quickly access a list of recent posts and pages.</li><li>Keep existing styles when you transform some blocks from one kind to another—from a Paragraph block to a Code block, for instance.</li><li>Create customized buttons and any new buttons you make will retain the style customizations automatically.</li><li>Make tag clouds and social icons even more appealing with updated settings and controls, and a new outline style for the tag cloud.</li></ul>



<img width="1204" height="700" src="https://i0.wp.com/wordpress.org/news/files/2022/05/Style-switcher-big.gif?fit=1204%2C700&ssl=1" alt="Style variations of Twenty Twenty Two theme" class="wp-image-12893" />



<h3>Style Switching&nbsp;</h3>



<p>Block themes now include the option to contain multiple style variations. This expands the new Style system even further and enables shortcuts to switch the look and feel of your site all within a single theme. In block themes that support this feature, you can change both the available settings, like the font-weight, and the style options, like the default color palette. Change the look and feel of your site with just a few clicks.</p>



<img width="1204" height="700" src="https://i2.wp.com/wordpress.org/news/files/2022/05/Expanded-templates.png?fit=1204%2C700&ssl=1" alt="Popover listing available templates" class="wp-image-12889" />



<h3>More Template Choices</h3>



<p>WordPress 6.0 includes five new template options for block themes: author, date, categories, tag, and taxonomy. These additional templates provide greater flexibility for content creators. Tailor each with the tools you already know or with the following new options in this release:&nbsp;</p>



<ul><li>Featured images can be used in the cover block.</li><li>New featured image sizing controls make it easier to get the results you want.</li><li>While editing a template, at the root, or between blocks, the quick inserter shows you patterns and template parts to help you work faster and discover new layout options.</li><li>The query block supports filtering on multiple authors, support for custom taxonomies, and support for customizing what is shown when there are no results.</li></ul>



<img width="1204" height="700" src="https://i1.wp.com/wordpress.org/news/files/2022/05/Integrated-Patterns.png?fit=1204%2C700&ssl=1" alt="Browsing footer patterns in the quick inserter" class="wp-image-12890" />



<h3>Integrated Patterns</h3>



<p>Patterns will now appear when you need them in even more places, like in the quick inserter or when creating a new header or footer. If you’re a block theme author, you can even <a href="https://developer.wordpress.org/block-editor/reference-guides/block-api/block-patterns/">register patterns from the Pattern Directory using `<code>theme.json</code>`</a>, enabling you to prioritize specific patterns that are most helpful to your theme’s users.</p>



<h3>Additional Design Tools</h3>



<p>Design tools grow more powerful and intuitive with each release. Some highlights for 6.0 include:&nbsp;</p>



<ul><li>A new color panel design saves space, but still shows your options at a glance.&nbsp;</li><li>New border controls offer a simpler way to set your border exactly as you like it.&nbsp;</li><li>Transparency levels for your colors allow for even more creative color options.</li><li>Control gaps, margins, typography, and more on a collection of blocks, all at once, in the Group block.</li><li>Switch between stack, row, and group variations to position groups of blocks with more layout flexibility.</li><li>Use the gap support functionality in the Gallery block to create different looks – from adding spacing between all images, to removing spacing altogether.</li></ul>



<img width="1204" height="700" src="https://i0.wp.com/wordpress.org/news/files/2022/05/List-view.png?fit=1204%2C700&ssl=1" alt="Selecting multiple blocks in the list view" class="wp-image-12891" />



<h3>Better List View</h3>



<p>New keyboard shortcuts enable you to select multiple blocks from the list view, modify them in bulk, and drag and drop them within the list. List View can be opened and closed easily; it comes collapsed by default and it automatically expands to the current selection whenever you select a block.&nbsp;</p>



<img width="1204" height="700" src="https://i1.wp.com/wordpress.org/news/files/2022/05/Block-Locking-Controls.png?fit=1204%2C700&ssl=1" alt="Unlocking the block in the block toolbar" class="wp-image-12892" />



<h3>Block Locking Controls</h3>



<p>Now you can lock your blocks. Choose to disable the option to move a block, remove a block, or both. This simplifies project handover, allowing your clients to unleash their creativity without worrying about accidentally breaking their site in the process.</p>



<h2>Improved Performance in WordPress 6.0</h2>



<p>This release includes several updates focused on improving the performance of WordPress. These enhancements cover a range of performance areas including improving the page and post-load speed, reducing the execution time of various query types, caching, navigation menus, and much more. The performance team working group is an important focus area of the core development team. For more information on this group’s work, please follow their work on Making WordPress with the <a href="https://make.wordpress.org/core/tag/performance/">#performance hashtag</a>.</p>



<h2>Enhancing WordPress 6.0 Accessibility</h2>



<p>Accessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.0 includes more than 50 updates specifically focused on enhancing the accessibility of the platform. You can <a href="https://make.wordpress.org/core/2022/04/20/wordpress-6-0-accessibility-improvements/">read about these updates</a> and learn more about the accessibility initiatives that are ongoing.</p>



<h2>Learn More About WordPress 6.0</h2>



<p>See WordPress 6.0 in action! <a href="https://www.youtube.com/watch?v=oe452WcY7fA">Watch a brief overview video</a> highlighting some of the major features debuting in WordPress 6.0.</p>



<div class="wp-block-embed__wrapper">

</div>



<p>Explore <a href="https://learn.wordpress.org/">learn.wordpress.org</a> for quick how-to videos and lots more on new features in WordPress. Or join a live <a href="https://learn.wordpress.org/social-learning/">interactive online learning session</a> on a specific WordPress topic.</p>



<p>Developers can explore the <a href="https://make.wordpress.org/core/2022/05/03/wordpress-6-0-field-guide/">WordPress 6.0 Field Guide</a>. It is overflowing with detailed developer notes to help you build with and extend WordPress.</p>



<p>Read the <a href="https://wordpress.org/support/wordpress-version/version-6-0/">WordPress 6.0 Release Notes</a> for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.</p>



<h2>The WordPress 6.0 Release Squad</h2>



<p>The group listed below tirelessly supported the release, from conception to ship date, and beyond:</p>



<ul><li>Release Lead: <a href="https://profiles.wordpress.org/matt/">Matt Mullenweg</a>&nbsp;</li><li>Release Coordinators: <a href="https://profiles.wordpress.org/priethor/">Héctor Prieto</a> and <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a></li><li>Core Tech Lead: <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a></li><li>Editor Tech Leads: <a href="https://profiles.wordpress.org/zieladam/">Adam Zieliński</a> and <a href="https://profiles.wordpress.org/gziolo/">Greg Ziółkowski</a></li><li>Core Triage Leads: <a href="https://profiles.wordpress.org/chaion07/">Ahmed Chaion</a> and <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a></li><li>Editor Triage Lead: <a href="https://profiles.wordpress.org/ndiego/">Nick Diego</a></li><li>Documentation Leads: <a href="https://profiles.wordpress.org/bph/">Birgit Pauli-Haack</a>, <a href="https://profiles.wordpress.org/milana_cap/">Milana Cap</a>, and <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a></li><li>Marketing &amp; Communications Lead: <a href="https://profiles.wordpress.org/dansoschin/">Dan Soschin</a></li><li>Test Leads: <a href="https://profiles.wordpress.org/boniu91/">Piotrek Boniu</a> and <a href="https://profiles.wordpress.org/ironprogrammer/">Brian Alexander</a></li><li>Design Lead: <a href="https://profiles.wordpress.org/critterverse/">Channing Ritter</a></li></ul>



<h2>Thank you to 500+ Contributors</h2>



<p>WordPress 6.0 would not have been possible without the contributions of more than 500 people in at least 58 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.</p>


<p class="is-style-wporg-props-long alignfull"><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/abdullahramzan/">Abdullah Ramzan</a> · <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</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/adi64bit/">adi64bit</a> · <a href="https://profiles.wordpress.org/aadilali/">Adil Ali</a> · <a href="https://profiles.wordpress.org/agepcom/">agepcom</a> · <a href="https://profiles.wordpress.org/chaion07/">Ahmed Chaion</a> · <a href="https://profiles.wordpress.org/wildworks/">Aki Hamano</a> · <a href="https://profiles.wordpress.org/atachibana/">Akira Tachibana</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/alansyue/">alansyue</a> · <a href="https://profiles.wordpress.org/aljullu/">Albert Juh&#233; Lluveras</a> · <a href="https://profiles.wordpress.org/albertomake/">albertomake</a> · <a href="https://profiles.wordpress.org/alefesouza/">Alefe Souza</a> · <a href="https://profiles.wordpress.org/alex897/">Aleksandar Kostov</a> · <a href="https://profiles.wordpress.org/xknown/">Alex Concha</a> · <a href="https://profiles.wordpress.org/ajlende/">Alex Lende</a> · <a href="https://profiles.wordpress.org/viper007bond/">Alex Mills</a> · <a href="https://profiles.wordpress.org/alexstine/">Alex Stine</a> · <a href="https://profiles.wordpress.org/aliakseyenkaihar/">aliakseyenkaihar</a> · <a href="https://profiles.wordpress.org/alkesh7/">Alkesh Miyani</a> · <a href="https://profiles.wordpress.org/alokstha1/">Alok Shrestha</a> · <a href="https://profiles.wordpress.org/shedonist/">Amanda Giles</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/_smartik_/">Andrei Surdu</a> · <a href="https://profiles.wordpress.org/aandrewdixon/">Andrew Dixon</a> · <a href="https://profiles.wordpress.org/nacin/">Andrew Nacin</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/oandregal/">André</a> · <a href="https://profiles.wordpress.org/afragen/">Andy Fragen</a> · <a href="https://profiles.wordpress.org/la-geek/">Angelika Reisiger</a> · <a href="https://profiles.wordpress.org/rilwis/">Anh Tran</a> · <a href="https://profiles.wordpress.org/ankit-k-gupta/">Ankit K Gupta</a> · <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a> · <a href="https://profiles.wordpress.org/anoopranawat/">Anoop Ranawat</a> · <a href="https://profiles.wordpress.org/antpb/">Anthony Burchell</a> · <a href="https://profiles.wordpress.org/paranoia1906/">Anthony Ledesma</a> · <a href="https://profiles.wordpress.org/antonvlasenko/">Anton Vlasenko</a> · <a href="https://profiles.wordpress.org/antonrinas/">antonrinas</a> · <a href="https://profiles.wordpress.org/antonynz/">Antony Booker</a> · <a href="https://profiles.wordpress.org/arcangelini/">arcangelini</a> · <a href="https://profiles.wordpress.org/aristath/">Ari Stathopoulos</a> · <a href="https://profiles.wordpress.org/arnee/">Arne</a> · <a href="https://profiles.wordpress.org/arpitgshah/">Arpit G Shah</a> · <a href="https://profiles.wordpress.org/artdecotech/">artdecotech</a> · <a href="https://profiles.wordpress.org/madeinua/">ArteMa</a> · <a href="https://profiles.wordpress.org/arthur791004/">Arthur Chu</a> · <a href="https://profiles.wordpress.org/asaquzzaman/">Asaquzzaman mishu</a> · <a href="https://profiles.wordpress.org/atomicjack/">atomicjack</a> · <a href="https://profiles.wordpress.org/ajoah/">Aur&#233;lien Joahny</a> · <a href="https://profiles.wordpress.org/aurooba/">Aurooba Ahmed</a> · <a href="https://profiles.wordpress.org/barryhughes/">Barry</a> · <a href="https://profiles.wordpress.org/barryceelen/">Barry Ceelen</a> · <a href="https://profiles.wordpress.org/bartoszgadomski/">Bartosz Gadomski</a> · <a href="https://profiles.wordpress.org/bedas/">Beda</a> · <a href="https://profiles.wordpress.org/scruffian/">Ben Dwyer</a> · <a href="https://profiles.wordpress.org/utz119/">Benachi</a> · <a href="https://profiles.wordpress.org/bernhard-reiter/">Bernhard Reiter</a> · <a href="https://profiles.wordpress.org/bettyjj/">BettyJJ</a> · <a href="https://profiles.wordpress.org/bhrugesh12/">Bhrugesh Bavishi</a> · <a href="https://profiles.wordpress.org/binarymoon/">binarymoon</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/supercleanse/">Blair Williams</a> · <a href="https://profiles.wordpress.org/blogaid/">BlogAid</a> · <a href="https://profiles.wordpress.org/boonebgorges/">Boone Gorges</a> · <a href="https://profiles.wordpress.org/wpe_bdurette/">Brandon DuRette</a> · <a href="https://profiles.wordpress.org/kraftbj/">Brandon Kraft</a> · <a href="https://profiles.wordpress.org/ironprogrammer/">Brian Alexander</a> · <a href="https://profiles.wordpress.org/bronsonquick/">bronsonquick</a> · <a href="https://profiles.wordpress.org/brookemk/">Brooke Kaminski</a> · <a href="https://profiles.wordpress.org/brookedot/">Brooke.</a> · <a href="https://profiles.wordpress.org/ribaricplusplus/">Bruno Ribaric</a> · <a href="https://profiles.wordpress.org/caraya/">caraya</a> · <a href="https://profiles.wordpress.org/cbravobernal/">Carlos Bravo</a> · <a href="https://profiles.wordpress.org/carlosgprim/">Carlos Garcia</a> · <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a> · <a href="https://profiles.wordpress.org/cbigler/">cbigler</a> · <a href="https://profiles.wordpress.org/shireling/">Chad Chadbourne</a> · <a href="https://profiles.wordpress.org/critterverse/">Channing Ritter</a> · <a href="https://profiles.wordpress.org/charleyparkerdesign/">charleyparkerdesign</a> · <a href="https://profiles.wordpress.org/charlyox/">charlyox</a> · <a href="https://profiles.wordpress.org/chintan1896/">Chintan hingrajiya</a> · <a href="https://profiles.wordpress.org/cbringmann/">Chloe Bringmann</a> · <a href="https://profiles.wordpress.org/chouby/">Chouby</a> · <a href="https://profiles.wordpress.org/clubkert/">Chris Lubkert</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/clonemykey/">clonemykey</a> · <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a> · <a href="https://profiles.wordpress.org/conner_bw/">conner_bw</a> · <a href="https://profiles.wordpress.org/cr0ybot/">Cory Hughart</a> · <a href="https://profiles.wordpress.org/courane01/">Courtney Robertson</a> · <a href="https://profiles.wordpress.org/mitogh/">Crisoforo Gaspar</a> · <a href="https://profiles.wordpress.org/dansoschin/">Dan Soschin</a> · <a href="https://profiles.wordpress.org/danielbachhuber/">Daniel Bachhuber</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/darerodz/">darerodz</a> · <a href="https://profiles.wordpress.org/htdat/">Dat Hoang</a> · <a href="https://profiles.wordpress.org/get_dave/">Dave Smith</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/dgwyer/">David Gwyer</a> · <a href="https://profiles.wordpress.org/dlh/">David Herrera</a> · <a href="https://profiles.wordpress.org/dshanske/">David Shanske</a> · <a href="https://profiles.wordpress.org/devutpol/">Deb Nath Utpol</a> · <a href="https://profiles.wordpress.org/delowardev/">Delowar Hossain</a> · <a href="https://profiles.wordpress.org/denishua/">denishua</a> · <a href="https://profiles.wordpress.org/dennisatyoast/">Dennis Claassen</a> · <a href="https://profiles.wordpress.org/dmsnell/">Dennis Snell</a> · <a href="https://profiles.wordpress.org/dhanendran/">Dhanendran</a> · <a href="https://profiles.wordpress.org/dharm1025/">Dharmesh Patel</a> · <a href="https://profiles.wordpress.org/dhusakovic/">dhusakovic</a> · <a href="https://profiles.wordpress.org/dilipbheda/">Dilip Bheda</a> · <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</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/drago239/">drago239</a> · <a href="https://profiles.wordpress.org/drewapicture/">Drew Jaynes</a> · <a href="https://profiles.wordpress.org/dromero20/">dromero20</a> · <a href="https://profiles.wordpress.org/eddystile/">Eddy</a> · <a href="https://profiles.wordpress.org/ehtis/">ehtis</a> · <a href="https://profiles.wordpress.org/eliezerspp/">Eliezer Pe&#241;a</a> · <a href="https://profiles.wordpress.org/ellatrix/">Ella van Durpe</a> · <a href="https://profiles.wordpress.org/manooweb/">Emmanuel Hesry</a> · <a href="https://profiles.wordpress.org/lopo/">Enrico Battocchi</a> · <a href="https://profiles.wordpress.org/eric3d/">eric3d</a> · <a href="https://profiles.wordpress.org/kebbet/">Erik Betshammar</a> · <a href="https://profiles.wordpress.org/espiat/">espiat</a> · <a href="https://profiles.wordpress.org/estelaris/">Estela Rueda</a> · <a href="https://profiles.wordpress.org/etaproducto/">etaproducto</a> · <a href="https://profiles.wordpress.org/everpress/">EverPress</a> · <a href="https://profiles.wordpress.org/fabiankaegy/">Fabian K&#228;gy</a> · <a href="https://profiles.wordpress.org/iogui/">Fabio Blanco</a> · <a href="https://profiles.wordpress.org/faison/">Faison</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/femkreations/">Femy Praseeth</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/foliovision/">FolioVision</a> · <a href="https://profiles.wordpress.org/francina/">Francesca Marano</a> · <a href="https://profiles.wordpress.org/fcoveram/">Francisco Vera</a> · <a href="https://profiles.wordpress.org/frankei/">frankei</a> · <a href="https://profiles.wordpress.org/furi3r/">furi3r</a> · <a href="https://profiles.wordpress.org/gadhiyaravi/">gadhiyaravi</a> · <a href="https://profiles.wordpress.org/garrett-eclipse/">Garrett Hyder</a> · <a href="https://profiles.wordpress.org/voldemortensen/">Garth Mortensen</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/genosseeinhorn/">genosseeinhorn</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/">Gerardo Pacheco</a> · <a href="https://profiles.wordpress.org/glendaviesnz/">Glen Davies</a> · <a href="https://profiles.wordpress.org/greglone/">Gr&#233;gory Viguier</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/gregoiresailland/">gregoiresailland</a> · <a href="https://profiles.wordpress.org/wido/">Guido Scialfa</a> · <a href="https://profiles.wordpress.org/gumacahin/">gumacahin</a> · <a href="https://profiles.wordpress.org/gvgvgvijayan/">gvgvgvijayan</a> · <a href="https://profiles.wordpress.org/hareesh-pillai/">Hareesh</a> · <a href="https://profiles.wordpress.org/hasanuzzamanshamim/">Hasanuzzaman</a> · <a href="https://profiles.wordpress.org/hasnainashfaq/">Hasnain Ashfaq</a> · <a href="https://profiles.wordpress.org/azhiyadev/">Hauwa Abashiya</a> · <a href="https://profiles.wordpress.org/hazdiego/">Haz</a> · <a href="https://profiles.wordpress.org/helen/">Helen Hou-Sandi</a> · <a href="https://profiles.wordpress.org/helgatheviking/">HelgaTheViking</a> · <a href="https://profiles.wordpress.org/henrywright/">Henry Wright</a> · <a href="https://profiles.wordpress.org/hilayt24/">Hilay Trivedi</a> · <a href="https://profiles.wordpress.org/hitendra-chopda/">Hitendra Chopda</a> · <a href="https://profiles.wordpress.org/hristok/">HristoK</a> · <a href="https://profiles.wordpress.org/hlashbrooke/">Hugh Lashbrooke</a> · <a href="https://profiles.wordpress.org/priethor/">Héctor Prieto</a> · <a href="https://profiles.wordpress.org/ianbelanger/">Ian Belanger</a> · <a href="https://profiles.wordpress.org/iandunn/">Ian Dunn</a> · <a href="https://profiles.wordpress.org/ianatkins/">ianatkins</a> · <a href="https://profiles.wordpress.org/ianmjones/">ianmjones</a> · <a href="https://profiles.wordpress.org/credo61/">ImanGM</a> · <a href="https://profiles.wordpress.org/imokol/">imokol</a> · <a href="https://profiles.wordpress.org/isabel_brison/">Isabel Brison</a> · <a href="https://profiles.wordpress.org/ishitaka/">ishitaka</a> · <a href="https://profiles.wordpress.org/itsamoreh/">itsamoreh</a> · <a href="https://profiles.wordpress.org/iulia-cazan/">Iulia Cazan</a> · <a href="https://profiles.wordpress.org/ivanlutrov/">Ivan Lutrov</a> · <a href="https://profiles.wordpress.org/jadpm/">jadpm</a> · <a href="https://profiles.wordpress.org/whyisjake/">Jake Spurlock</a> · <a href="https://profiles.wordpress.org/jakeparis/">jakeparis</a> · <a href="https://profiles.wordpress.org/jameskoster/">James Koster</a> · <a href="https://profiles.wordpress.org/codente/">Jamie VanRaalte</a> · <a href="https://profiles.wordpress.org/rumpel2116/">Jan Weiss</a> · <a href="https://profiles.wordpress.org/janh2/">janh2</a> · <a href="https://profiles.wordpress.org/jarretc/">Jarret</a> · <a href="https://profiles.wordpress.org/jsnjohnston/">Jason Johnston</a> · <a href="https://profiles.wordpress.org/madtownlems/">Jason LeMahieu (MadtownLems)</a> · <a href="https://profiles.wordpress.org/javiarce/">Javier Arce</a> · <a href="https://profiles.wordpress.org/jprieton/">Javier Prieto</a> · <a href="https://profiles.wordpress.org/grandeljay/">Jay Trees</a> · <a href="https://profiles.wordpress.org/jazbek/">jazbek</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/jeffmatson/">Jeff Matson</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/jdy68/">Jenny Dupuy</a> · <a href="https://profiles.wordpress.org/miss_jwo/">Jenny Wong</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/sausajez/">Jez Emery</a> · <a href="https://profiles.wordpress.org/jhned/">jhned</a> · <a href="https://profiles.wordpress.org/jhnstn/">jhnstn</a> · <a href="https://profiles.wordpress.org/jigar-bhanushali/">jigar bhanushali</a> · <a href="https://profiles.wordpress.org/jiteshdhamaniya/">jiteshdhamaniya</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/goaroundagain/">Johannes Kinast</a> · <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a> · <a href="https://profiles.wordpress.org/johnjamesjacoby/">John James Jacoby</a> · <a href="https://profiles.wordpress.org/johnregan3/">John Regan</a> · <a href="https://profiles.wordpress.org/johnwatkins0/">John Watkins</a> · <a href="https://profiles.wordpress.org/jb510/">Jon Brown</a> · <a href="https://profiles.wordpress.org/jrchamp/">Jonathan Champ</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/jorgecontreras/">Jorge</a> · <a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a> · <a href="https://profiles.wordpress.org/josearcos/">Jos&#233; Arcos</a> · <a href="https://profiles.wordpress.org/chanthaboune/">Josepha</a> · <a href="https://profiles.wordpress.org/jostnes/">Josepha Dambul</a> · <a href="https://profiles.wordpress.org/joshf/">Joshua Fredrickson</a> · <a href="https://profiles.wordpress.org/joyously/">Joy</a> · <a href="https://profiles.wordpress.org/jrivett/">jrivett</a> · <a href="https://profiles.wordpress.org/jsnajdr/">jsnajdr</a> · <a href="https://profiles.wordpress.org/juanlopez4691/">juanlopez4691</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/junaidkbr/">Junaid Ahmed</a> · <a href="https://profiles.wordpress.org/justinahinon/">Justin Ahinon</a> · <a href="https://profiles.wordpress.org/justinbusa/">Justin Busa</a> · <a href="https://profiles.wordpress.org/certainstrings/">Justin Tucker</a> · <a href="https://profiles.wordpress.org/kafleg/">KafleG</a> · <a href="https://profiles.wordpress.org/kevin940726/">Kai Hao</a> · <a href="https://profiles.wordpress.org/kajalgohel/">Kajal Gohel</a> · <a href="https://profiles.wordpress.org/kapacity/">kapacity</a> · <a href="https://profiles.wordpress.org/kapilpaul/">Kapil Paul</a> · <a href="https://profiles.wordpress.org/karolinakulinska/">karolinakulinska</a> · <a href="https://profiles.wordpress.org/kasparsd/">Kaspars</a> · <a href="https://profiles.wordpress.org/kbat82/">kbatdorf</a> · <a href="https://profiles.wordpress.org/ryelle/">Kelly Choyce-Dwan</a> · <a href="https://profiles.wordpress.org/w33zy/">Kemory Grubb</a> · <a href="https://profiles.wordpress.org/gwwar/">Kerry Liu</a> · <a href="https://profiles.wordpress.org/kprovance/">Kev Provance</a> · <a href="https://profiles.wordpress.org/kharisblank/">Kharis Sulistiyono</a> · <a href="https://profiles.wordpress.org/kirtan95/">Kirtan Gajjar</a> · <a href="https://profiles.wordpress.org/kjellr/">Kjell Reigstad</a> · <a href="https://profiles.wordpress.org/kmix39/">KMix</a> · <a href="https://profiles.wordpress.org/knutsp/">Knut Sparhell</a> · <a href="https://profiles.wordpress.org/konradyoast/">Konrad.K</a> · <a href="https://profiles.wordpress.org/obenland/">Konstantin Obenland</a> · <a href="https://profiles.wordpress.org/kpegoraro/">kpegoraro</a> · <a href="https://profiles.wordpress.org/kubiq/">kubiq</a> · <a href="https://profiles.wordpress.org/sainthkh/">Kukhyeon Heo</a> · <a href="https://profiles.wordpress.org/laurlittle/">Lauren</a> · <a href="https://profiles.wordpress.org/0mirka00/">Lena Morita</a> · <a href="https://profiles.wordpress.org/lenasterg/">lenasterg</a> · <a href="https://profiles.wordpress.org/uzumymw/">leskam</a> · <a href="https://profiles.wordpress.org/layotte/">Lew Ayotte</a> · <a href="https://profiles.wordpress.org/linux4me2/">linux4me2</a> · <a href="https://profiles.wordpress.org/lschuyler/">Lisa Schuyler</a> · <a href="https://profiles.wordpress.org/lkraav/">lkraav</a> · <a href="https://profiles.wordpress.org/louislaugesen/">Louis</a> · <a href="https://profiles.wordpress.org/thelovekesh/">Lovekesh Kumar</a> · <a href="https://profiles.wordpress.org/karpstrucking/">Lucas Karpiuk</a> · <a href="https://profiles.wordpress.org/zaguiini/">Luis Felipe Zaguini</a> · <a href="https://profiles.wordpress.org/luisherranz/">luisherranz</a> · <a href="https://profiles.wordpress.org/lukecavanagh/">Luke Cavanagh</a> · <a href="https://profiles.wordpress.org/pyrobd/">Lukman Nakib</a> · <a href="https://profiles.wordpress.org/michelangelovandam/">M. van Dam</a> · <a href="https://profiles.wordpress.org/macbookandrew/">macbookandrew</a> · <a href="https://profiles.wordpress.org/mashikag/">Maciej</a> · <a href="https://profiles.wordpress.org/onemaggie/">Maggie Cabrera</a> · <a href="https://profiles.wordpress.org/maguijo/">maguijo</a> · <a href="https://profiles.wordpress.org/mhimon/">Mahbub Hasan Imon</a> · <a href="https://profiles.wordpress.org/malthert/">malthert</a> · <a href="https://profiles.wordpress.org/manfcarlo/">manfcarlo</a> · <a href="https://profiles.wordpress.org/fullofcaffeine/">Marcelo de Moraes Serpa</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/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/mkox/">Markus Kosmal</a> · <a href="https://profiles.wordpress.org/marv2/">marv2</a> · <a href="https://profiles.wordpress.org/marybaum/">Mary Baum</a> · <a href="https://profiles.wordpress.org/mat-lipe/">Mat Lipe</a> · <a href="https://profiles.wordpress.org/paapst/">Mathieu</a> · <a href="https://profiles.wordpress.org/matveb/">Matias Ventura</a> · <a href="https://profiles.wordpress.org/mmaattiiaass/">matiasbenedetto</a> · <a href="https://profiles.wordpress.org/mattchowning/">Matt Chowning</a> · <a href="https://profiles.wordpress.org/sivel/">Matt Martz</a> · <a href="https://profiles.wordpress.org/matt/">Matt Mullenweg</a> · <a href="https://profiles.wordpress.org/themattroyal/">Matt Royal</a> · <a href="https://profiles.wordpress.org/mjstoney/">Matt Stoney</a> · <a href="https://profiles.wordpress.org/mattwiebe/">Matt Wiebe</a> · <a href="https://profiles.wordpress.org/mauriac/">maur</a> · <a href="https://profiles.wordpress.org/azouamauriac/">Mauriac AZOUA</a> · <a href="https://profiles.wordpress.org/maxkellermann/">Max Kellermann</a> · <a href="https://profiles.wordpress.org/mehedi890/">Mehedi Foysal</a> · <a href="https://profiles.wordpress.org/meher/">Meher Bala</a> · <a href="https://profiles.wordpress.org/mgol/">mgol</a> · <a href="https://profiles.wordpress.org/mburridge/">Michael Burridge</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/mauteri/">Mike Auteri</a> · <a href="https://profiles.wordpress.org/mikeschroder/">Mike Schroder</a> · <a href="https://profiles.wordpress.org/miken32/">miken32</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/multidots1896/">Minal Diwan</a> · <a href="https://profiles.wordpress.org/mirkolofio/">Mirco Babini</a> · <a href="https://profiles.wordpress.org/mmdeveloper/">MMDeveloper</a> · <a href="https://profiles.wordpress.org/mohadeseghasemi/">Mohadese Ghasemi</a> · <a href="https://profiles.wordpress.org/ahsan03/">Mohammad Ahsan Habib</a> · <a href="https://profiles.wordpress.org/opurockey/">Mohammad Rockeybul Alam</a> · <a href="https://profiles.wordpress.org/mjkhajeh/">MohammadJafar Khajeh</a> · <a href="https://profiles.wordpress.org/mor10/">Morten Rand-Hendriksen</a> · <a href="https://profiles.wordpress.org/moushik/">moushik</a> · <a href="https://profiles.wordpress.org/computerguru/">mqudsi</a> · <a href="https://profiles.wordpress.org/muhammadfaizanhaidar/">Muhammad Faizan Haidar</a> · <a href="https://profiles.wordpress.org/mukesh27/">Mukesh Panchal</a> · <a href="https://profiles.wordpress.org/amustaque97/">Mustaque Ahmed</a> · <a href="https://profiles.wordpress.org/nabil_kadimi/">Nabil</a> · <a href="https://profiles.wordpress.org/nagpai/">Nagesh Pai - a11n</a> · <a href="https://profiles.wordpress.org/nalininonstopnewsuk/">Nalini Thakor</a> · <a href="https://profiles.wordpress.org/nhadsall/">Nathan</a> · <a href="https://profiles.wordpress.org/nayana123/">Nayana Maradia</a> · <a href="https://profiles.wordpress.org/eidolonnight/">Nicholas Garofalo</a> · <a href="https://profiles.wordpress.org/nickciske/">Nick Ciske</a> · <a href="https://profiles.wordpress.org/ndiego/">Nick Diego</a> · <a href="https://profiles.wordpress.org/rahe/">Nicolas Juen</a> · <a href="https://profiles.wordpress.org/nidhidhandhukiya/">nidhidhandhukiya</a> · <a href="https://profiles.wordpress.org/ntsekouras/">Nik Tsekouras</a> · <a href="https://profiles.wordpress.org/knilkantha/">Nil</a> · <a href="https://profiles.wordpress.org/nmschaller/">nmschaller</a> · <a href="https://profiles.wordpress.org/noahtallen/">Noah Allen</a> · <a href="https://profiles.wordpress.org/oakesjosh/">oakesjosh</a> · <a href="https://profiles.wordpress.org/oguzkocer/">oguzkocer</a> · <a href="https://profiles.wordpress.org/domainsupport/">Oliver Campion</a> · <a href="https://profiles.wordpress.org/alshakero/">Omar Alshaker</a> · <a href="https://profiles.wordpress.org/opr18/">opr18</a> · <a href="https://profiles.wordpress.org/otshelnik-fm/">Otshelnik-Fm</a> · <a href="https://profiles.wordpress.org/overclokk/">overclokk</a> · <a href="https://profiles.wordpress.org/ovidiul/">ovidiul</a> · <a href="https://profiles.wordpress.org/paaljoachim/">Paal Joachim Romdahl</a> · <a href="https://profiles.wordpress.org/pablohoneyhoney/">Pablo Honey</a> · <a href="https://profiles.wordpress.org/pls78/">Paolo L. Scala</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/pbearne/">Paul Bearne</a> · <a href="https://profiles.wordpress.org/pbiron/">Paul Biron</a> · <a href="https://profiles.wordpress.org/figureone/">Paul Ryan</a> · <a href="https://profiles.wordpress.org/pschrottky/">Paul Von Schrottky</a> · <a href="https://profiles.wordpress.org/paulkevan/">paulkevan</a> · <a href="https://profiles.wordpress.org/pavanpatil1/">Pavan Patil</a> · <a href="https://profiles.wordpress.org/malinevskiy/">Pavlo</a> · <a href="https://profiles.wordpress.org/pbking/">pbking</a> · <a href="https://profiles.wordpress.org/pedromendonca/">Pedro Mendon&#231;a</a> · <a href="https://profiles.wordpress.org/petaryoast/">Petar Ratković</a> · <a href="https://profiles.wordpress.org/psmits1567/">Peter Smits</a> · <a href="https://profiles.wordpress.org/westi/">Peter Westwood</a> · <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a> · <a href="https://profiles.wordpress.org/petrosparaskevopoulos/">petrosparaskevopoulos</a> · <a href="https://profiles.wordpress.org/walbo/">Petter Walb&#248; Johnsg&#229;rd</a> · <a href="https://profiles.wordpress.org/pgpagely/">pgpagely</a> · <a href="https://profiles.wordpress.org/johnstonphilip/">Phil Johnston</a> · <a href="https://profiles.wordpress.org/nekojonez/">Pieterjan Deneys</a> · <a href="https://profiles.wordpress.org/pikamander2/">pikamander2</a> · <a href="https://profiles.wordpress.org/boniu91/">Piotrek Boniu</a> · <a href="https://profiles.wordpress.org/webtechpooja/">Pooja Derashri</a> · <a href="https://profiles.wordpress.org/pooja1210/">Pooja N Muchandikar</a> · <a href="https://profiles.wordpress.org/pravinparmar2404/">Pravin Parmar</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/priyank9033/">Priyank</a> · <a href="https://profiles.wordpress.org/pypwalters/">pypwalters</a> · <a href="https://profiles.wordpress.org/r-a-y/">r-a-y</a> · <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a> · <a href="https://profiles.wordpress.org/rafiahmedd/">Rafi Ahmed</a> · <a href="https://profiles.wordpress.org/superpoincare/">Ramanan</a> · <a href="https://profiles.wordpress.org/rahmohn/">Ramon Ahnert</a> · <a href="https://profiles.wordpress.org/ramonopoly/">Ramon James</a> · <a href="https://profiles.wordpress.org/nextend_ramona/">Ramona</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/razvanonofrei/">Razvan Onofrei</a> · <a href="https://profiles.wordpress.org/rehanali/">Rehan Ali</a> · <a href="https://profiles.wordpress.org/tabrisrp/">Remy Perona</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/richtabor/">Rich Tabor</a> · <a href="https://profiles.wordpress.org/richybkreckel/">Richard B. Kreckel</a> · <a href="https://profiles.wordpress.org/ricomoorman/">ricomoorman</a> · <a href="https://profiles.wordpress.org/r0bsc0tt/">Rob Scott</a> · <a href="https://profiles.wordpress.org/noisysocks/">Robert Anderson</a> · <a href="https://profiles.wordpress.org/ravanh/">Rolf Allard van Hagen</a> · <a href="https://profiles.wordpress.org/rolfsiebers/">Rolf Siebers</a> · <a href="https://profiles.wordpress.org/costasovo/">Rostislav Woln&#253;</a> · <a href="https://profiles.wordpress.org/rufus87/">Rufus87</a> · <a href="https://profiles.wordpress.org/ryan/">Ryan Boren</a> · <a href="https://profiles.wordpress.org/bookdude13/">Ryan Fredlund</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/sebastienserre/">S&#233;bastien SERRE</a> · <a href="https://profiles.wordpress.org/soean/">S&#246;ren Wrede</a> · <a href="https://profiles.wordpress.org/sabbir1991/">Sabbir Ahmed</a> · <a href="https://profiles.wordpress.org/sabbirshouvo/">Sabbir Hasan</a> · <a href="https://profiles.wordpress.org/samiff/">Sami Falah</a> · <a href="https://profiles.wordpress.org/sanzeeb3/">Sanjeev Aryal</a> · <a href="https://profiles.wordpress.org/santosguillamot/">santosguillamot</a> · <a href="https://profiles.wordpress.org/mikachan/">Sarah Norris</a> · <a href="https://profiles.wordpress.org/arasae/">Sarah Snow</a> · <a href="https://profiles.wordpress.org/sarayourfriend/">sarayourfriend</a> · <a href="https://profiles.wordpress.org/sathyapulse/">Sathiyamoorthy V</a> · <a href="https://profiles.wordpress.org/sayedulsayem/">Sayedul Sayem</a> · <a href="https://profiles.wordpress.org/sbossarte/">sbossarte</a> · <a href="https://profiles.wordpress.org/sclayf1/">sclayf1</a> · <a href="https://profiles.wordpress.org/swb1192/">Scott Buscemi</a> · <a href="https://profiles.wordpress.org/coffee2code/">Scott Reilly</a> · <a href="https://profiles.wordpress.org/wonderboymusic/">Scott Taylor</a> · <a href="https://profiles.wordpress.org/omaeyusuke/">Segayuu</a> · <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a> · <a href="https://profiles.wordpress.org/sheepysheep60/">sheepysheep60</a> · <a href="https://profiles.wordpress.org/shital-patel/">Shital Marakana</a> · <a href="https://profiles.wordpress.org/shreyasikhar26/">Shreyas Ikhar</a> · <a href="https://profiles.wordpress.org/rsiddharth/">siddharth</a> · <a href="https://profiles.wordpress.org/nomnom99/">Siddharth Thevaril</a> · <a href="https://profiles.wordpress.org/silb3r/">silb3r</a> · <a href="https://profiles.wordpress.org/lumpysimon/">Simon Blackbourn</a> · <a href="https://profiles.wordpress.org/pross/">Simon Prosser</a> · <a href="https://profiles.wordpress.org/simonhammes/">simonhammes</a> · <a href="https://profiles.wordpress.org/siobhyb/">Siobhan</a> · <a href="https://profiles.wordpress.org/smit08/">Smit Rathod</a> · <a href="https://profiles.wordpress.org/snapfractalpop/">snapfractalpop</a> · <a href="https://profiles.wordpress.org/socalchristina/">socalchristina</a> · <a href="https://profiles.wordpress.org/spencercameron/">Spencer Cameron-Morin</a> · <a href="https://profiles.wordpress.org/stacimc/">stacimc</a> · <a href="https://profiles.wordpress.org/stefanfisk/">stefanfisk</a> · <a href="https://profiles.wordpress.org/satollo/">Stefano Lissa</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/stephenharris/">Stephen Harris</a> · <a href="https://profiles.wordpress.org/stevegrunwell/">Steve Grunwell</a> · <a href="https://profiles.wordpress.org/subrataemfluence/">Subrata Sarkar</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/csesumonpro/">Sumon Sarker</a> · <a href="https://profiles.wordpress.org/sunil25393/">SunilPrajapati</a> · <a href="https://profiles.wordpress.org/sunyatasattva/">sunyatasattva</a> · <a href="https://profiles.wordpress.org/mahype/">Sven Wagener</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/inc2734/">Takashi Kitajima</a> · <a href="https://profiles.wordpress.org/karmatosed/">Tammie Lister</a> · <a href="https://profiles.wordpress.org/tharsheblows/">tharsheblows</a> · <a href="https://profiles.wordpress.org/legendusmaximus/">Theo H</a> · <a href="https://profiles.wordpress.org/thimalw/">Thimal Wickremage</a> · <a href="https://profiles.wordpress.org/twistermc/">Thomas McMahon</a> · <a href="https://profiles.wordpress.org/thomasplevy/">Thomas Patrick Levy</a> · <a href="https://profiles.wordpress.org/xiven/">Thomas Pike</a> · <a href="https://profiles.wordpress.org/tillkruess/">Till Kr&#252;ss</a> · <a href="https://profiles.wordpress.org/waterfire/">Tim Blankenship</a> · <a href="https://profiles.wordpress.org/tnolte/">Tim Nolte</a> · <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a> · <a href="https://profiles.wordpress.org/tobifjellner/">tobifjellner (Tor-Bjorn Fjellner)</a> · <a href="https://profiles.wordpress.org/tomjdevisser/">Tom</a> · <a href="https://profiles.wordpress.org/tomasztunik/">Tomasz Tunik</a> · <a href="https://profiles.wordpress.org/tomalec/">Tomek</a> · <a href="https://profiles.wordpress.org/shimotomoki/">Tomoki Shimomura</a> · <a href="https://profiles.wordpress.org/ttahmouch/">Tony Tahmouch</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/zodiac1978/">Torsten Landsiedel</a> · <a href="https://profiles.wordpress.org/sierratr/">Tracy</a> · <a href="https://profiles.wordpress.org/trex005/">trex005</a> · <a href="https://profiles.wordpress.org/tszming/">tszming</a> · <a href="https://profiles.wordpress.org/tumas2/">tumas2</a> · <a href="https://profiles.wordpress.org/twstokes/">twstokes</a> · <a href="https://profiles.wordpress.org/junsuijin/">Tynan Beatty</a> · <a href="https://profiles.wordpress.org/tzipporahwitty/">tzipporahwitty</a> · <a href="https://profiles.wordpress.org/uday17035/">Uday Kokitkar</a> · <a href="https://profiles.wordpress.org/ugljanin/">ugljanin</a> · <a href="https://profiles.wordpress.org/ugyensupport/">Ugyen Dorji</a> · <a href="https://profiles.wordpress.org/grapplerulrich/">Ulrich</a> · <a href="https://profiles.wordpress.org/utkarshpatel/">Utkarsh</a> · <a href="https://profiles.wordpress.org/valer1e/">valer1e</a> · <a href="https://profiles.wordpress.org/versusbassz/">versusbassz</a> · <a href="https://profiles.wordpress.org/vcanales/">Vicente Canales</a> · <a href="https://profiles.wordpress.org/elifvish/">Vishal Kumar</a> · <a href="https://profiles.wordpress.org/vladolaru/">vlad.olaru</a> · <a href="https://profiles.wordpress.org/volodymyrkolesnykov/">Volodymyr Kolesnykov</a> · <a href="https://profiles.wordpress.org/vortfu/">vortfu</a> · <a href="https://profiles.wordpress.org/webmandesign/">WebMan Design &#124; Oliver Juhas</a> · <a href="https://profiles.wordpress.org/wendyjchen/">Wendy Chen</a> · <a href="https://profiles.wordpress.org/west7/">Wes Theron</a> · <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a> · <a href="https://profiles.wordpress.org/whoisnegrello/">whoisnegrello</a> · <a href="https://profiles.wordpress.org/skorasaurus/">Will Skora</a> · <a href="https://profiles.wordpress.org/wpmakenorg/">wpmakenorg</a> · <a href="https://profiles.wordpress.org/wpsoul/">wpsoul</a> · <a href="https://profiles.wordpress.org/wraithkenny/">WraithKenny</a> · <a href="https://profiles.wordpress.org/wslyhbb/">wslyhbb</a> · <a href="https://profiles.wordpress.org/upsuper/">Xidorn Quan</a> · <a href="https://profiles.wordpress.org/fierevere/">Yui</a> · <a href="https://profiles.wordpress.org/dolphingg/">Yunus Ertuğrul</a> · <a href="https://profiles.wordpress.org/zebulan/">Zebulan Stanphill</a> · <a href="https://profiles.wordpress.org/znuff/">znuff</a> · <a href="https://profiles.wordpress.org/chesio/">Česlav Przywara</a></p>



<p>By release day, 76 locales had translated 90-percent or more of WordPress 6.0 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in 205 languages.</p>



<p>Many thanks to all of the community volunteers who contribute to the <a href="https://wordpress.org/support/">support forums</a> by answering questions from WordPress users around the world.</p>



<p>If contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to <a href="https://make.wordpress.org/">Make WordPress</a> and explore the product roadmap on the <a href="https://make.wordpress.org/core/">core development blog</a>.</p>



<h2>The WordPress Mission &amp; You</h2>



<p>WordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.</p>



<p>WordPress believes in democratizing publishing and <a href="https://opensource.org/osd-annotated">the freedoms that come with open source</a>. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.</p>



<p><a href="https://wordpress.org/about/">Learn more about WordPress</a> and how you can join our community to help shape the future of the world’s most popular website platform.</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2>A Release Haiku</h2>



<p>Six-point-oh is here<br />Time to download and upgrade<br />Let’s pause, celebrate</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<p id="footnote">1&nbsp;<a href="https://w3techs.com/technologies/overview/content_management">According to W3Techs as of May 5, 2022</a>. </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, 24 May 2022 20:01:05 +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:"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:"";}}}}}i:23;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:69:"Do The Woo Community: Builder Tips from WordCamp Europe 2022 Speakers";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:28:"https://dothewoo.io/?p=71730";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://dothewoo.io/woocommerce-tips-speakers-wordcamp-europe/";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:454:"<p>Tips from Daisy Olsen, Dave Lockie, Devin Walker, Greg Ziolkowski, Jonathan Wold, Milana Cap, Nev Harris, Paul Bearne, Ryan Welcher, Vassilena Valchanova and Vito Peleg</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/woocommerce-tips-speakers-wordcamp-europe/">Builder Tips from WordCamp Europe 2022 Speakers</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</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, 24 May 2022 09:01: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:5:"BobWP";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:24;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:64:"WPTavern: Open Source Initiative Launches News Blog on 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=133438";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:75:"https://wptavern.com/open-source-initiative-launches-news-blog-on-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:7242:"<p>The <a href="https://opensource.org/">Open Source Initiative</a> (OSI), a public benefit corporation and steward of the <a href="https://opensource.org/docs/osd">Open Source Definition</a>, has launched a <a href="https://blog.opensource.org/">news blog</a> on WordPress. In 2021, OSI&#8217;s board appointed Stefano Maffulli as its first Executive Director, and he is leading the organization in overhauling its web presence.</p>



<p>&#8220;One of the main objectives for OSI in 2022 is to reinforce our communication channels,&#8221; Maffulli said. &#8220;We’re improving the perception of OSI as a reliable, trustworthy organization. The OSI didn&#8217;t have a regular publishing schedule before, nor a content plan. Now we have established a regular cadence, publishing at least once a week (often more), commenting on recent news like a <a rel="noreferrer noopener" href="https://blog.opensource.org/gnome-patent-troll-stripped-of-patent-rights/" target="_blank">winning against a patent troll</a> or <a rel="noreferrer noopener" href="https://blog.opensource.org/modified-agplv3-removes-freedoms-adds-legal-headaches/" target="_blank">court decisions about open source licenses</a>, featuring our <a rel="noreferrer noopener" href="https://blog.opensource.org/category/sponsors/" target="_blank">sponsors</a>, and offering <a rel="noreferrer noopener" href="https://blog.opensource.org/category/opinions/" target="_blank">opinions</a> on topics of interest for the wider community. It’s a starting point to affirm OSI as a convener of conversations among various souls of the open source communities.&#8221;</p>



<p>The blog was launched on a subdomain of the <a href="https://opensource.org/">opensource.org</a> website, which uses Drupal 7, self-hosted on a droplet from Digital Ocean. It&#8217;s also tightly integrated with CiviCRM to manage members&#8217; subscriptions, donations from individuals, tracking sponsorships, and sending the newsletter. </p>



<p>As Drupal 7 is approaching EOL in November 2022, the team is planning to move everything to WordPress. They explored managed hosting with Drupal but found it was more expensive and also required them to migrate to a more recent version of Drupal. Themes and plugins made for D7 are not compatible with D9+, so they didn&#8217;t see an advantage in terms of time or simplicity.</p>



<p>&#8220;Unfortunately we don&#8217;t have staff to manage a self-hosted Drupal installation and nobody on staff really knows how to use it,&#8221; Maffulli said. &#8220;Tasks like creating landing pages proved to be quite time consuming for us.</p>



<p>&#8220;With money, knowledge and time constraints and an urgent need to increase our publishing rate, ramping up the organization’s visibility online we decided to migrate the website in two phases: First, we migrate the blog so we have a fresh look together with the improved publishing schedule. This phase is complete &#8211; the blog is on a managed hosting offered by DreamHost. The second phase is the migration of the rest of the site: this is ongoing with the help of Automattic and will take a few months to complete.&#8221;</p>



<p>Although Maffulli wanted to avoid creating a blog under a subdomain, and preferred using the old URL (<a rel="noreferrer noopener" href="http://opensource.org/blog." target="_blank">opensource.org/blog.</a>..), mixing Drupal self-hosted with a managed WordPress site was not a common use case with straightforward solutions. If the new blog design looks familiar, that&#8217;s because it was inspired by WP Tavern&#8217;s new design.</p>



<img />Open Source Initiative&#8217;s new WordPress-powered blog



<p>&#8220;Once we decided to go with a subdomain, the new site took really only a few days to launch: I knew I wanted to have a simple site, minimal amount of plugins, no page builders and a very clean design based on WP Tavern, of which I&#8217;m a fan,&#8221; he said. </p>



<p>Since the Tavern&#8217;s theme wasn&#8217;t yet on GitHub, Maffulli contracted a developer who used WordPress&#8217; new full-site editing features to create a simple child theme based on the Twenty Twenty-Two default theme. He said he is glad overseeing the project gave him a chance to learn the basics of FSE.</p>



<p>Some members of the OSI staff were already familiar with WordPress, which contributed to the decision to use the software. The wide range of functionality and third-party integrations were also a factor.</p>



<p>&#8220;We rely a lot on content calendar solutions that allow to manage schedule posts and social media promotions from one tool,&#8221; Maffulli said.</p>



<p>&#8220;We’re addicted to CoSchedule. That tool is far from perfect, primarily because it’s not Open Source. But it’s so incredibly powerful and convenient for a small team like us. We track our publishing calendar and tasks with CoSchedule, making it so easy not to miss a beat: every blog post has it’s social media attachment, same with the newsletter, that becomes a blog post for archive. Soon, we’ll add podcasts.&#8221;</p>



<p>Maffulli said he wishes the WordPress media library offered a more standardized way of storing and tracking copyright information, like the author, source, and license. </p>



<p>&#8220;I think this unnecessarily exposes WP users to copyright infringement claims where trolls could threaten successfully people who may have not kept their records clean,&#8221; he said. &#8220;It&#8217;s something to think about for future releases of Instant Images and similar plugins.&#8221;</p>



<p>The OSI team has opted to keep comments closed on posts at this time, since they do not have the capicity to properly moderate comments.</p>



<p>&#8220;I have a lot of experience managing online communities and I know it can become very time consuming,&#8221; Maffulli said. &#8220;We just don’t have staff but we’re raising funds to solve that.&#8221;</p>



<p>OSI is also looking into creating a way to give its members the privilege of commenting. This would require a way to integrate authentication with CiviCRM to access members&#8217; records. </p>



<p>&#8220;While we build staff and upgrade <a rel="noreferrer noopener" href="http://opensource.org/" target="_blank">opensource.org</a>, I hope to setup services from the <a href="https://indieweb.org/">IndieWeb</a> community into Voices of Open Source,&#8221; Maffulli said. &#8220;This will allow for comments made on various social networks to be aggregated back into <a rel="noreferrer noopener" href="http://blog.opensource.org/" target="_blank">blog.opensource.org</a>.&#8221;</p>



<p>The new Voices of Open Source blog has started by featuring the network of OSI affiliates, which boasts 80 organizations, including Mozilla, Wikimedia, Linux Foundation, OpenUK, and more.</p>



<p>&#8220;We&#8217;d like to share OSI&#8217;s unique position to highlight open source stories, challenges, and successes of companies and people around the world,&#8221; Maffulli said. OSI is in communication with its affiliates to make them aware of this opportunity and is aiming to open guest posting on the blog to indvidual members in the wider community sometime in the future.</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, 23 May 2022 21:31:09 +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:25;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"Post Status: WooCommerce Function of the Week: wc_get_product_category_list";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=97560";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:85:"https://poststatus.com/woocommerce-function-of-the-week-wc_get_product_category_list/";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:8904:"<p class="has-drop-cap">Here's yet another time-saving WooCommerce function. No need to reinvent the wheel — with a single line of code and no custom queries, you can get all the categories a product belongs to.</p>



<p>This week's function is <code>wc_get_product_category_list</code>, and there's no need to explain what it does as its name is self-explanatory.</p>



<p>As usual, we'll study the WooCommerce core function code, see where and why it's used, and finally we'll cover a quick case study. Enjoy!</p>



<span id="more-97560"></span>



<h2 id="h-function-code">Function code</h2>



<p>The function <code>wc_get_product_category_list</code> can be found under <code>woocommerceincludeswc-product-functions.php</code>:</p>



<pre class="wp-block-code"><code>/**
 * Returns the product categories in a list.
 *
 * @param int    $product_id Product ID.
 * @param string $sep (default: ', ').
 * @param string $before (default: '').
 * @param string $after (default: '').
 * @return string
 */
function wc_get_product_category_list( $product_id, $sep = ', ', $before = '', $after = '' ) {
	return get_the_term_list( $product_id, 'product_cat', $before, $sep, $after );
}</code></pre>



<p>First of all, let's look at the function parameters: </p>



<ul><li><code>$product_id</code>, which is of course the product we want to get the categories for.</li><li><code>$sep</code>, by default a comma, which defines the list separator.</li><li><code>$before</code> and <code>$after</code>, by default empty strings, which define what shows before and after the list of categories. (prefix / suffix)</li></ul>



<p>Now to the function statements — actually, <em>statement</em>, as there is only one:</p>



<pre class="wp-block-code"><code>return get_the_term_list( $product_id, 'product_cat', $before, $sep, $after );</code></pre>



<p>That really sounds like a WordPress function as there is no mention of &#8220;woo,&#8221; &#8220;wc,&#8221; or any other WooCommerce prefixes. Let's look it up in the WordPress developer code reference documentation. (<a href="https://developer.wordpress.org/reference/functions/get_the_term_list/" target="_blank" rel="noreferrer noopener">https://developer.wordpress.org/reference/functions/get_the_term_list/</a>)</p>



<p>Here we go:</p>



<pre class="wp-block-code"><code>function get_the_term_list( $post_id, $taxonomy, $before = '', $sep = '', $after = '' ) {
    $terms = get_the_terms( $post_id, $taxonomy );
 
    if ( is_wp_error( $terms ) ) {
        return $terms;
    }
 
    if ( empty( $terms ) ) {
        return false;
    }
 
    $links = array();
 
    foreach ( $terms as $term ) {
        $link = get_term_link( $term, $taxonomy );
        if ( is_wp_error( $link ) ) {
            return $link;
        }
        $links&#91;] = '&lt;a href="' . esc_url( $link ) . '" rel="tag"&gt;' . $term-&gt;name . '&lt;/a&gt;';
    }
 
    /**
     * Filters the term links for a given taxonomy.
     *
     * The dynamic portion of the hook name, `$taxonomy`, refers
     * to the taxonomy slug.
     *
     * Possible hook names include:
     *
     *  - `term_links-category`
     *  - `term_links-post_tag`
     *  - `term_links-post_format`
     *
     * @since 2.5.0
     *
     * @param string&#91;] $links An array of term links.
     */
    $term_links = apply_filters( "term_links-{$taxonomy}", $links );  // phpcs:ignore WordPress.NamingConventions.ValidHookName.UseUnderscores
 
    return $before . implode( $sep, $term_links ) . $after;
}</code></pre>



<p>Simple enough — <code>get_the_term_list</code> accepts basically the same parameters we covered above, plus the <code>$taxonomy</code> parameter, which in our case is passed as <code>product_cat</code> to tell WordPress we're retrieving WooCommerce product categories.</p>



<p>Here's how it works:</p>



<ul><li><code>get_the_terms( $post_id, $taxonomy )</code> gets the product ID category objects.</li><li><code>$links</code> array gets filled with the list of categories, each with its own link.</li><li><code>return $before . implode( $sep, $term_links ) . $after</code> gives us the content we need: &#8220;prefix + $links separated with $sep + suffix&#8221;</li></ul>



<h2>Function usage</h2>



<p>Define a product ID (e.g., 57) — and that's all you need to do!</p>



<p>Call the function:</p>



<pre class="wp-block-code"><code>echo wc_get_product_category_list( 57 );</code></pre>



<p>And see the magic happen:</p>



<pre class="wp-block-code"><code>cat1 link, cat2 link, cat3 link, ...</code></pre>



<p>Of course, if you have access to the <code>$product global</code>, you can call the function dynamically. For example, if you want to call the function on every single product pages, you could do this:</p>



<pre class="wp-block-code"><code>echo wc_get_product_category_list( $product-&gt;get_id() );</code></pre>



<p>Now I want to see where and when the function is called, so we give it a bit of context. With a quick search through the WooCommerce plugin, I find a single result in <code>woocommercetemplatessingle-productmeta.php</code>, line 34:</p>



<pre class="wp-block-code"><code>&lt;?php echo wc_get_product_category_list( $product-&gt;get_id(), ', ', '&lt;span class="posted_in"&gt;' . _n( 'Category:', 'Categories:', count( $product-&gt;get_category_ids() ), 'woocommerce' ) . ' ', '&lt;/span&gt;' ); ?&gt;</code></pre>



<p>Which generates this output on my single product page:</p>



<div class="wp-block-image"><img width="752" height="357" src="https://cdn.poststatus.com/wp-content/uploads/2022/05/image-752x357.png" alt="" class="wp-image-97562" /></div>



<p>Now we know <code>wc_get_product_category_list</code> is responsible for showing the list of categories in the single product page where it comes with a prefix (&#8216;Category:' or &#8216;Categories:' based on category count) plus the default comma separator and no suffix.</p>



<p>Let's use <code>wc_get_product_category_list</code> for our custom development example now and consider a quick case study.</p>



<h2 id="h-case-study">Case study</h2>



<p>Where could <code>wc_get_product_category_list</code> come in handy? Surely, in the shop page.</p>



<p>By default, WooCommerce shows the list of products with image, title, price and button. There is no mention of product categories there, so let's add them ourselves.</p>



<p><strong>Before</strong>:</p>



<div class="wp-block-image"><img width="752" height="398" src="https://cdn.poststatus.com/wp-content/uploads/2022/05/image-1-752x398.png" alt="" class="wp-image-97563" /></div>



<p><strong>The custom snippet:</strong></p>



<pre class="wp-block-code"><code>/**
 * @snippet       Show Categories | WooCommerce Shop
 * @how-to        Get CustomizeWoo.com FREE
 * @author        Rodolfo Melogli
 * @testedwith    WooCommerce 6
 * @donate $9     https://businessbloomer.com/bloomer-armada/
 */

add_action( 'woocommerce_after_shop_loop_item', 'bbloomer_show_product_categories', 9 );

function bbloomer_show_product_categories() {
	global $product;	
	echo wc_get_product_category_list( $product-&gt;get_id(), ' - ', '&lt;p&gt;In: ', ' ' . _n( 'category', 'categories', count( $product-&gt;get_category_ids() ), 'woocommerce' ) . '&lt;/p&gt;' );
}</code></pre>



<p><strong>After</strong>:</p>



<div class="wp-block-image"><img width="752" height="383" src="https://cdn.poststatus.com/wp-content/uploads/2022/05/image-2-752x383.png" alt="" class="wp-image-97564" /></div>



<p>A few notes:</p>



<ul><li>I used the <code>woocommerce_after_shop_loop_item</code> hook with priority 9, which is just before priority 10 (the add-to-cart button). TLDR: I'm outputting the category list above the add to cart button.</li><li>I declare the global <code>$product</code> so that I can access the product ID.</li><li>I then call the <code>wc_get_product_category_list function</code>, with the following parameters:<ul><li><code>$product-&gt;get_id() <strong>-&gt; the product ID</strong></code></li><li><code>' - ' <strong>-&gt; the separator</strong></code></li><li><code>'&lt;p&gt;In: ' <strong>-&gt; the prefix</strong></code></li><li><code>' ' . _n( 'category', 'categories', count( $product-&gt;get_category_ids() ), 'woocommerce' ) . '&lt;/p&gt; ' <strong>-&gt; the suffix</strong></code></li></ul></li></ul>



<p>It's interesting how I reused this line from the single product page, as I mentioned above:</p>



<pre class="wp-block-code"><code>_n( 'category', 'categories', count( $product-&gt;get_category_ids() ), 'woocommerce' )</code></pre>



<p>Basically, if <code>count = 1</code> the first string is returned (singular &#8220;category&#8221;), while if <code>count &gt; 1</code> you get the plural &#8220;categories.&#8221; You can see the difference in the last screenshot above.</p>



<p>Any other use cases you have in mind? Let me know in the comments!</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, 22 May 2022 21:00:12 +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:"Rodolfo Melogli";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:26;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"Gutenberg Times: WordCamp Europe, 75 Themes, Thunks and Filters –  Weekend Edition 216";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://gutenbergtimes.com/?p=21184";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:92:"https://gutenbergtimes.com/wordcamp-europe-75-themes-thunks-and-filters-weekend-edition-216/";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:11675:"<p>Howdy, </p>



<p>Greetings from Porto, Portugal. It&#8217;s a wonderful city. You cn walk and walk and walk, up the hill, down the hill, with ever changing view. The ratio of restaurants and bar per block is on average three. In certain areas, every single doorwar offers you a different place to eat or drink. </p>





<p>Last week, WordCamp Europe organizers announced that <a href="https://europe.wordcamp.org/2022/wceu-livestreamed/">there will be a livestream</a> of the sessions&#8217; in track one and two. That&#8217;s good news, as there are amazing t<a href="https://europe.wordcamp.org/2022/schedule/">alks and speakers on the schedule.</a> If you want to casually run into me, <a href="https://europe.wordcamp.org/2022/the-wordpress-community-booth-at-wceu2022/">I will be at the Community Booth</a> Friday and Saturday around 10 am 🙂</p>



<p>Before people from the WordPress Community descend to Porto, core contributors will release WordPress 6.0 on May 24, 2022. The signs seem in their favor, and <a href="https://make.wordpress.org/core/2022/05/20/wordpress-6-0-release-candidate-4-rc4-now-available-for-testing/">RC candidate four is now available.</a> <strong><a href="https://twitter.com/priethor">Hector Prieto</a></strong>, release co-coordinator, outline the <a href="https://make.wordpress.org/core/2022/05/19/wordpress-6-0-release-day-process/">WordPress 6.0 Release Day Process</a>, just in case you are interested in how the sausage is made, so to speak. </p>



<p>Stay well, and safe! </p>



<p>Yours, 💕<br />Birgit</p>






<div class="wp-container-2 wp-block-group has-light-background-background-color has-background"><div class="wp-block-group__inner-container">
<p>Table of Contents</p>



<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#theme-building-and-full-site-editing">Theme Building and Full-Site Editing</a></li><li><a href="https://gutenbergtimes.com/feed/#update-for-site-owners-and-site-builders">Update for site owners and site builders. </a><ul><li><a href="https://gutenbergtimes.com/feed/#now-available-on-wordpress-tv">Now available on WordPress TV </a></li></ul></li><li><a href="https://gutenbergtimes.com/feed/#3-b">Block Buidling and Tools for Developers</a></li><li><a href="https://gutenbergtimes.com/feed/#upcoming-wordpress-events">Upcoming WordPress Events</a><ul><li><a href="https://gutenbergtimes.com/feed/#social-learning-events">Social Learning Events</a></li></ul></li><li><a href="https://gutenbergtimes.com/feed/#wordcamp-and-other-events">WordCamp and other Events</a></li></ul></div>
</div></div>




<h2 id="theme-building-and-full-site-editing">Theme Building and Full-Site Editing</h2>



<p><strong><a href="https://twitter.com/nickmdiego">Nick Diego</a></strong>, developer advocate at WPEngine, has been teaching the <em>Working with Template in Full Site Editing</em> series on the Meetup Social Learning space. Part 1 and Part 2 are now available on WordPress.tv</p>



<ul><li><a href="https://wordpress.tv/2022/05/06/nick-diego-builder-basics-working-with-templates-in-full-site-editing-part-1/"><strong>Working with Templates in Full Site Editing (Part 1)</strong></a></li><li><a href="https://wordpress.tv/2022/05/15/nick-diego-builder-basics-working-with-templates-in-full-site-editing-part-2/"><strong>Working with Templates in Full Site Editing (Part 2)</strong></a></li></ul>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />



<p>If you want to know how far the Gutenberg project and the block editor in WordPress has come, watch this video by <strong>Anne McCarthy</strong>: <a href="https://www.youtube.com/watch?v=MjDhfW7FpAc"><strong>Building a site with WordPress 5.0 vs WordPress 6.0</strong></a></p>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />



<p>The <a href="https://wordpress.org/patterns/new-pattern/"><em>Pattern Creator </em></a>is a online tool which allows you to create block patterns for inclusion into the WordPress Patterns Directory, a place where you can access freely available patterns for your websites. On this podcast episode of the WPTavern&#8217;s Jukebox, <a href="https://wptavern.com/podcast/27-ana-segota-and-kelly-choyce-dwan-on-how-to-use-the-new-pattern-creator"><strong>Ana Segota and Kelly Choyce-Dwan on How To Use the New Pattern Creator,</strong></a> <strong>Nathan Wrigley </strong>talked to Ana Segota and Kelly Choyce-Dwan, who share two different perspectives. Segota is a themer and Choyce-Dwan is on the team, that built the Pattern Creator.</p>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />



<p>Now that the Style Switcher is coming to WordPress 6.0, it might be time to learn <strong><a href="https://fullsiteediting.com/lessons/global-style-variations/">how to create Style variations for your theme</a></strong>. A style variations is a user-selectable skin of the same theme. Everything stays that same except the color palette or the available fonts. <strong>Caroline Nymark</strong> published <a href="https://fullsiteediting.com/lessons/global-style-variations/">a lesson for you on her site.</a></p>



<p>Justin Tadlock also wrote about <strong><a href="https://wptavern.com/global-style-variations-skins-for-themes-have-landed-in-gutenberg">Global Style Variations, “Skins” for Themes, Have Landed in Gutenberg</a></strong> earlier this year. </p>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />



<p><strong>Carolina Nymark</strong> aslo pursued the question: <a href="https://fullsiteediting.com/lessons/accessibility-in-full-site-editing-themes/"><strong>Can a full site editing theme be accessibility-ready?</strong></a> and shares her throughts and knowledge</p>



<h2 id="update-for-site-owners-and-site-builders">Update for site owners and site builders. </h2>



<p>75 Block Themes in the WordPress Theme Directory, <a href="https://wordpress.org/themes/catch-fse/">Catch FSE</a> is one of them. Justin Tadlock took it for a spin and published his review. <a href="https://wptavern.com/catch-fse-is-a-bold-business-friendly-wordpress-block-theme"><strong>Catch FSE Is a Bold, Business-Friendly WordPress Block Theme</strong></a>. </p>



<p>Take a look at the others: <a href="https://wordpress.org/themes/tags/full-site-editing/"><em>WordPress Theme Directory, Full-Site Editing</em></a></p>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />



<p><strong><a href="https://twitter.com/kevinbatdorf">Kevin Batdorf,</a></strong> developer at Extendify, published a plugin called <a href="https://wordpress.org/plugins/image-filters/">Image Filters</a> that adds 22 more filters to your choices, even better than Instagram and you can do it all on your website!  </p>



<img />



<p>Read more about it on the WPTavern: <a href="https://wptavern.com/the-image-filters-plugin-adds-over-20-filters-including-vintage-pastel-pink-and-more"><strong>The Image Filters Plugin Adds Over 20 Filters, Including Vintage, Pastel Pink, and More</strong></a></p>



<h3 id="now-available-on-wordpress-tv">Now available on WordPress TV </h3>



<p><a href="https://wordpress.tv/2022/05/19/using-the-navigation-block/"><strong>Using the Navigation Block</strong></a> with Wes Theron, a 45 minute walk through the ins and outs of the new Navigation block. </p>



<p>And when you are done with that, or if you already know it you might want to T<a href="https://wordpress.tv/2022/05/12/taking-advantage-of-query-loops-2/"><strong>ake Advantage of Query Loops</strong></a> also with Wed </p>



<h2 id="3-b">Block Buidling and Tools for Developers</h2>



<p>In his live stream, <a href="https://www.youtube.com/watch?v=SjaBjNmewPQ"><strong>reviewing the changes to the @wordpress/scripts package and trying out Thunks for the first time</strong></a>, <strong>Ryan Welche</strong>r looked at the new changes to the @wordpress/scripts package that make using it much easier for developers. He then get into using Thunks in the datastore created for the pre-publish checklist.</p>



<p>What are Thunks you might ask? Here is a post by <strong><a href="https://twitter.com/adamzielin">Adam Zielinsky</a></strong>: <a href="https://make.wordpress.org/core/2021/10/29/thunks-in-gutenberg/"><strong>Thunks in Gutenberg</strong></a></p>



<h2 id="upcoming-wordpress-events">Upcoming WordPress Events</h2>



<h3 id="social-learning-events">Social Learning Events</h3>



<p><strong>May 23, 2022 1pm EDT / 17:00 UTC</strong> <br /><strong><a href="https://www.meetup.com/wordpress-social-learning/events/285798142/">Hello Blocks! Coding a custom block</a></strong> w/ Ryan Welcher</p>



<p><strong>May 25, 2022 &#8211; 7pm EDT / 23:00 UTC </strong><br /><strong><a href="https://www.meetup.com/wordpress-social-learning/events/285577455/">Design With Me: Create a Simple Website for your Small Business</a></strong> w/ Sarah Snow</p>



<p><strong>May 26, 2022 &#8211; 5 pm EDT / 19:00 UTC </strong><br /><strong><a href="https://www.meetup.com/wordpress-social-learning/events/285952290/">I want a Website, not a Blog!</a></strong> w/ Destiny Kano</p>



<p><strong>June 16, 2022 &#8211; 5pm EDT / 19:00 UTC </strong><br /><strong><a href="https://www.meetup.com/wordpress-social-learning/events/286028824/">Let&#8217;s build a homepage together</a></strong> w/ Wes Theron. </p>



<h2 id="wordcamp-and-other-events">WordCamp and other Events</h2>



<p><strong>June 2 &#8211; 4th, 2022 </strong><br /><strong><a href="https://europe.wordcamp.org/2022/">WordCamp Europe</a></strong></p>



<p><strong>June 11 + 12, 2022 </strong> <br /><a href="https://warsaw.wordcamp.org/2022/"><strong>WordCamp Warsaw</strong></a></p>



<p><strong>June 20 &#8211; 24, 2022</strong> <br /><strong><a href="https://pagebuildersummit.com/">Page Builder Summit </a></strong></p>



<p><strong>June 25, 2022 </strong><br /><strong><a href="https://montclair.wordcamp.org/2022/">WordCamp Montclair, NJ</a></strong></p>



<p><strong>September 9 &#8211; 11, 2022</strong><br /><strong><a href="https://us.wordcamp.org/2022/">WordCamp US</a></strong>, San Diego, California</p>



<p><strong>September 15 + 16, 2022</strong> <br /><a href="https://netherlands.wordcamp.org/2022/"><strong>WordCamp Netherlands</strong></a></p>



<p><strong>February 17-19 2023</strong> (tent)<br /><a href="https://asia.wordcamp.org/2023/"><strong>WordCamp Asia</strong></a>, Bangkok, Thailand</p>




<hr class="wp-block-separator has-css-opacity is-style-wide" />



<p class="has-text-align-left"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>



<form class="wp-block-newsletterglue-form ngl-form ngl-portrait" action="https://gutenbergtimes.com/feed/" method="post"><div class="ngl-form-container"><div class="ngl-form-field"><label class="ngl-form-label" for="ngl_email"><br />Type in your Email address to subscribe.</label><div class="ngl-form-input"><input type="email" class="ngl-form-input-text" name="ngl_email" id="ngl_email" /></div></div><button class="ngl-form-button">Subscribe</button><p class="ngl-form-text">We hate spam, too and won&#8217;t give your email address to anyone except Mailchimp to send out our Weekend Edition</p></div><div class="ngl-message-overlay"><div class="ngl-message-svg-wrap"></div><div class="ngl-message-overlay-text">Thanks for subscribing.</div></div><input type="hidden" name="ngl_list_id" id="ngl_list_id" value="26f81bd8ae" /><input type="hidden" name="ngl_double_optin" id="ngl_double_optin" value="yes" /></form>



<hr class="wp-block-separator has-css-opacity is-style-wide" />";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, 21 May 2022 05:43: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: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:27;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:77:"WPTavern: New Video Explores Site Building Progress From WordPress 5.0 to 6.0";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=134617";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:88:"https://wptavern.com/new-video-explores-site-building-progress-from-wordpress-5-0-to-6-0";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:4086:"<p>Do you remember what it was like to use WordPress 5.0? Three years and ten major releases have radically changed the site building experience, but it&#8217;s not always easy to see recognize when focused on some of the smaller, iterative changes that slowly add up. Anne McCarthy, WordPress product liaison at Automattic and co-release coordinator for 6.0, has created a short 13-minute video that shows the immense amount of progress contributors have made on site building features.</p>



<div class="wp-block-embed__wrapper">

</div>



<p>McCarthy takes viewers back in time to WordPress 5.0, released in December 2018, which introduced the block editor and the Twenty Nineteen default theme through the work of 400+ contributors. She demonstrates using the Customizer with the default theme. These were simpler days and it&#8217;s clear now how limited the Customizer was for implementing the most basic changes. </p>



<p>The video contrasts that experience with the upcoming 6.0 release, which features the work of 500+ contributors on features that didn&#8217;t exist three years ago.</p>



<p>McCarthy quickly demonstrates the 6.0 site editing experience, swapping out template parts, and showcasing the breadth of the customization available for images, colors, typography, controlling the posts that are displayed, style variations, and the impressive array of design tools available.</p>



<img />



<p>Ten major versions later, nearly every aspect of a WordPress site is customizable through the site editor. For those who have not yet made the leap into full-site editing &#8211; it&#8217;s essentially like the old Customizer but with super powers, better instant previews, and the interface is a panel on the right. At this point, I don&#8217;t think the usability is at a level where someone can just get in there and immediately know what they are doing. It takes a little bit of exploring, but it&#8217;s moving in the right direction.</p>



<p>Videos like this one show what is possible and just how far WordPress has come since it first introduced the block editor. It also indirectly answers Joost de Valk&#8217;s recent claims that <a href="https://joost.blog/wordpress-market-share-shrinking/">the full-site editing project not being done yet is partially to blame</a> for WordPress&#8217; recent <a href="https://wptavern.com/wordpress-community-attributes-declining-market-share-to-performance-issues-increased-complexity-and-the-lagging-full-site-editing-project">decline in market share</a>. </p>



<p>While WordPress remains the uncontested market leader among CMS&#8217;s, some say this small percentage of a decline is inconsequential. Matt Mullenweg has stated in previous interviews that he views market share stats as a &#8220;<a href="https://wptavern.com/matt-mullenweg-and-david-heinemeier-hansson-discuss-wordpress-market-share-monopolies-and-power-in-open-source-communities">trailing indicator</a>&#8221; in the quest to create the best possible experience for users and developers. A growing market share, in that sense, is a signal of user satisfaction. </p>



<p>WordPress jumped into the block paradigm at the right time, just as many other apps began adopting the concept of composable blocks for creating content and designs. Full-site editing is the extension of that vision but it takes time to make it something polished and delightful to use. McCarthy&#8217;s video is a good reminder of the limitations that users previously labored under while trying to edit their sites, and the &#8220;why&#8221; behind all the effort going into FSE.</p>



<p>&#8220;As someone who&#8217;s currently on the WordPress 6.0 Release Team, I can attest that the project needs more contributors,&#8221; WordPress contributor Nick Diego <a href="https://twitter.com/nickmdiego/status/1524456236518940672">said</a> in response to the recent market share discussion. &#8220;The fact that FSE has taken so long is not a lack of effort. There are many contributors pouring their hearts and souls into the project. We just need more help.&#8221;</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, 21 May 2022 01:14:09 +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:28;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:67:"Post Status: Post Status Upgrade — Zen and the Art of Lockpicking";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=97950";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:54:"https://poststatus.com/zen-and-the-art-of-lockpicking/";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:2550:"<p class="has-background">Learn new skills and build your knowledge to enhance your career in WordPress! <strong>Post Status Upgrade</strong> is an ongoing series of live workshops centered around a particular skill or learning activity.</p>



<p class="has-drop-cap">Watch Robert Rowley explain the basics of lock picking in this live, hands-on workshop for Post Status members that took place on May 5th, 2022. Watch as Robert teaches participants how to open locks, as well as their minds. He shares stories about emotional intelligence and the life cycle of skill practice from the beginner's mind to the expert's. You'll laugh at some entertaining mishaps Robert has had with lock picks!</p>



<div class="wp-container-9 wp-block-group"><div class="wp-block-group__inner-container">
<div class="wp-block-image"><img width="132" height="150" src="https://cdn.poststatus.com/wp-content/uploads/2022/03/robert-snow-1-132x150.png" alt="Robert Rowley" class="wp-image-95165" />Robert Rowley</div>



<p><strong>Robert Rowley</strong> is <strong>Patchstack</strong>&#8216;s Security Advocate and has been picking locks since 2004. Between 2016 and 2019 Robert ran a retreat for his information security friends and colleagues called <strong>Disconnect Camp</strong>. This is where he first combined skills like lock picking with reflection on mental health, wellness, skill development and more.</p>
</div></div>



<div class="wp-block-embed__wrapper">

</div>



<div class="wp-block-columns has-theme-palette-7-background-color has-background">
<div class="wp-block-column is-vertically-aligned-center">
<div id="StellarWP" class="wp-block-image is-style-default"><a href="https://poststat.us/stellarwp"><img width="300" height="300" src="https://cdn.poststatus.com/wp-content/uploads/2022/02/stellarwp-black-1-300x300.png" alt="StellarWP" class="wp-image-93207" title="StellarWP" /></a></div>
</div>



<div class="wp-block-column">
<p class="has-small-font-size"><strong>StellarWP</strong> is a collective of WordPress innovators empowering business owners and creators with plugins and tools to help them thrive. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. Our solutions include <a href="https://poststat.us/stellarwp"><strong>the most trusted names in WordPress</strong></a>, with more than 2.5 million installs. Since 2021, we’ve grown to encompass seven brands and dozens of plugins. StellarWP is part of the Liquid Web family of brands. <br /></p>
</div>
</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:"Fri, 20 May 2022 21:15:11 +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:29;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:35:"Post Status: Post Status Notes #499";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=97724";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:45:"https://poststatus.com/post-status-notes-499/";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:14089:"<div class="wp-container-11 wp-block-group has-theme-palette-8-background-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">Kim Parsell Memorial Scholarship returns to WCUS › Think like a platform again! › Leo Gopal on support for mental health in the community › WP Accessibility Day › Performance Lab 1.1.0 › The WordPress Way › Dropping jQuery for speed › More to WP than Headless and FSE for devs › and more&#8230; </p></div></div></div>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_f5fe16-0a"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>With <strong>WordCamp US</strong> being held in-person (September 9-11), that also means the <strong>WordPress Foundation’s Kim Parsell Memorial Scholarship</strong> has returned! This <a href="https://wordpressfoundation.org/news/2022/the-kim-parsell-memorial-scholarship-returns-for-wordcamp-us-2022/">scholarship provides financial assistance</a> — including travel costs — so the recipient can attend the conference. It's good to see three scholarships will be awarded this time, thanks to COVID-19 taking out in-person events for us in 2020 and 2021. </p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_39de4e-45"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Brian Coords</strong> says <a href="https://masterwp.com/wordpress-needs-to-start-thinking-like-a-platform-again/">WordPress “needs to start thinking like a platform again.”</a> While I don't agree that <strong>Full Site Editing</strong> feels like or is the next “Google Plus or Apple’s Ping,” I do believe it could distract from user experience elsewhere and other things that need attention. (My take: <strong>Google</strong> abandoned Plus without putting much effort into it, and <strong>Apple</strong> is just bad at social full stop.) <strong>[DB]</strong></p>



<p>I talked about what WordPress needs in <a href="https://poststatus.com/the-state-of-wordpress-market-share/">a recent Post Status Comments episode</a> on the prospects of declining market share with <strong>Joost de Valk</strong>, <strong>Alex Denning</strong>, and <strong>Jessica Frick</strong>. <strong>[DB]</strong></p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_fd78c8-ed"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Leo Gopal</strong> from <strong>Cape Town, South Africa</strong> writes about <a href="https://heropress.com/essays/community-saved-life-falling-lifted/">depression and mental illness</a>, and how the WordPress community has rallied around him.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_db5284-f4"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>Here's <a href="https://wordpress.org/plugins/local-google-fonts/">a new plugin</a> from <strong>Xaver Birsak</strong> that hosts the <strong>Google Fonts</strong> you use on your own server.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_c22000-0a"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>If you're a <strong>Gravity Forms</strong> user and have ever needed charts and graphs, then <strong>GravityView</strong>&#8216;s <a href="https://www.gravityforms.com/blog/gravitycharts-by-gravityview/">new plugin might be of interest</a>.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_adb0bf-ec"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>The <strong>WP Accessibility Day</strong> <a href="https://wpaccessibility.day/">website is live</a>! The date for this event is November 2-3, 2022.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_ced27d-52"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><a href="https://twitter.com/carolinapoena" target="_blank" rel="noreferrer noopener"><strong>Carolina Nymark</strong></a> took to Twitter for <a href="https://twitter.com/carolinapoena/status/1525352306576961536">an insightful investigation and survey</a> about the <strong>Full Site Editing</strong> themes already in the .org theme directory. She shares stats like the number of core blocks styled in <code>theme.json</code> and common color slugs.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_9c2be9-8a"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>Here's a good two part series (<a href="https://hidde.blog/common-a11y-issues/">part one</a> and <a href="https://hidde.blog/more-common-a11y-issues/">part two</a>) from <strong>Hidde de Vries</strong> on common accessibility issues that you can address and fix on your site today.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_f1538e-8b"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Ross Wintle</strong> has combined a searchable command palette with &#8220;fancy browser APIs&#8221; to <a href="https://twitter.com/magicroundabout/status/1525230664911560704">enable voice-controlled WordPress</a>. Fun experiment!</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_db75ff-27"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>If you are new to <strong>WooCommerce</strong> and looking into performance enhancements, <a href="https://convesio.com/blog/wordpress-performance/how-to-speed-up-woocommerce-backend/">this post</a> from <strong>Ibad Rehman</strong> might be a good place to start.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_8a8a7d-2a"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Bernhard Kau</strong> has <a href="https://wordpress.org/plugins/campaign-archive-block-for-mailchimp/">released a WordPress plugin</a> for <strong>MailChimp</strong> users. &#8220;If you are using <strong>MailChimp</strong> and want to show a nice archive on your page, you can now <a href="https://twitter.com/2ndKauBoy/status/1525512618538160130">add it with a block</a>.&#8221;</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_d21cc5-ef"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>The <strong>WordPress Performance Team</strong> has <a href="https://wordpress.org/plugins/performance-lab/">published the 1.1.0 release</a> of the <strong>Performance Lab</strong> plugin. It includes an enhancement that &#8220;replaces the featured image with a <strong>WebP</strong> version when available.&#8221;</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_6e457e-68"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>A nice take here from <strong>Ollie Williams</strong> <a href="https://css-tricks.com/colrv1-and-css-font-palette-web-typography/">on color fonts</a>. Modern web typography, fonts, and CSS have come very far in a relatively short period of time.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_8fc5e9-38"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>While <strong>Jason Coleman</strong>&#8216;s &#8220;<a href="https://therealjasoncoleman.com/2022/04/26/the-wordpress-way/">The WordPress Way</a>&#8221; post is a few weeks old, if you haven't read it, you should. Jason explains the core values of his team at <strong>Paid Memberships Pro</strong>, which includes the idea that the <strong>GPL</strong> license will result in &#8220;the best code.&#8221;</p>



<p>Jason explains what this means in specific terms in a time of debate and discussion about what should happen to WordPress software when a paid support license expires. For Jason, the WordPress way &#8220;means our code will continue to work as expected if your paid license expires.&#8221;</p>



<p>While I think there are slightly different takes on what is best for customers and that experiments in the WordPress ecosystem should be encouraged, I also would like to see more people follow in Jason's footsteps and publish their core values.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_372a0e-f5"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>WooCommerce</strong> has opened up <a href="https://developer.woocommerce.com/2022/05/16/call-for-early-testing-custom-order-table-migrations/">a call for testing</a> regarding the move to custom tables. It's the first milestone for a large effort but the goal of the call &#8220;is to test the migration process across various hosts and server combinations.&#8221;</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_349556-68"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Courtney Robertson</strong> shows you <a href="https://www.godaddy.com/garage/configure-client-access-with-block-locking-in-wordpress/">how to lock blocks</a> in WordPress, a new feature coming in 6.0. Good for when a client takes over writing and revising content and hits a button accidentally.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_59033e-69"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p>Here's <a href="https://www.tweetic.io/">a free and open source tool</a> that converts tweets into static HTML — perfect for testimonials.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_3a6a83-45"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><a href="http://gov.uk/" target="_blank" rel="noreferrer noopener">GOV.UK</a>&nbsp;dropped <a href="https://web.dev/gov-uk-drops-jquery/">their jQuery dependency</a> from their front end, with <a href="https://twitter.com/TheRealNooshu/status/1509487050122276864">some impressive numbers</a> in the performance results. Great takeaway: &#8220;Don't shortchange your users if the web platform can easily do the job a framework can.&#8221;</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_b17e8b-ab"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Héctor Prieto</strong> <a href="https://make.wordpress.org/core/2022/05/19/wordpress-6-0-release-day-process/">shares the WordPress 6.0 release process</a> (starting next week), including the timeline and how you can help.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_04d673-2b"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Tom McFarlin</strong> thinks <a href="https://tommcfarlin.com/more-to-wordpress/">there is more to WordPress than FSE and Headless</a>. He feels &#8220;we’re spending a lot of time talking about the same things in WordPress as of late.&#8221;</p>



<p>I can understand where Tom is coming from — there are lots of technologies beyond <strong>React</strong> we can use. Getting off the beaten path is a good way for developers to get new ideas, have fun, and prevent nimble competitors from dominating certain niches.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_899dfb-51"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Jonathan Bossenger</strong> explains <a href="https://spinupwp.com/wordpress-database-optimization-indexing/">why it's important to think about indexes</a> for custom database tables — and when <em>not</em> to use them. He shows how you can diagnose and add indexes, offering valuable tips. One example: &#8220;When you are filtering or joining data based on specific fields, adding indexes to those fields is a crucial step in ensuring your queries are optimized.&#8221;</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_ec3f4f-b1"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<p><strong>Sari Azout</strong> says <a href="https://future.a16z.com/the-future-of-search-is-boutique/">it’s no longer enough to organize the world’s information</a> — it's more important to organize the world’s <em>trustworthy</em> information with &#8220;boutique search engines that index, curate, and organize things in new ways.&#8221; This article rings true to me, as I find some Google searches less effective than they have been in the past.</p>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_e17dc8-44"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<div class="wp-container-12 wp-block-group has-theme-palette-7-background-color has-background"><div class="wp-block-group__inner-container">
<h2 id="h-do-you-enjoy-our-weekly-notes"><strong>Do you enjoy our weekly notes? </strong></h2>



<p>Get them and more in Post Status' <a href="https://poststatus.com/news/week-in-review/">Week in Review</a>. We gather WordPress and WooCommerce news along with significant writing, videos, and podcast episodes from the WordPress community and beyond. Don't miss the latest updates from the people making WordPress in our <a href="https://poststatus.com/make-wordpress/">This Week at WordPress.org</a> summaries. It's all in <a href="https://poststatus.com/newsletter">our newsletter</a>! <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>
</div></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:"Fri, 20 May 2022 21:04:35 +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:30;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:34:"Post Status: Getting Uncomfortable";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=97996";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:45:"https://poststatus.com/getting-uncomfortable/";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:1243:"<blockquote class="wp-block-quote"><p>Growth is uncomfortable; you have to embrace the discomfort if you want to expand.</p><cite><strong>Jonathan Majors</strong></cite></blockquote>



<p class="has-drop-cap">Have you ever had to work outside of your comfort zone? It’s something I’m trying to get used to. But it sure isn’t easy.</p>



<p>This week and next I’m working from my dad’s home office in Tennessee while we prepare to sell his house.</p>



<p>This place is beautiful, and the view from the office is breathtaking. It’s easy to see why my dad loved it here.</p>



<p>But beautiful things can still be uncomfortable.</p>



<p>Traveling to WCEU has many people anxious about traveling after so long, and attending a WordCamp after a number of years. </p>



<p>But discomfort can help us grow, connect, and be more than we were before.</p>



<p>Whatever you’re doing, I hope you’ve built in a little discomfort to help you evaluate where you are, plan a course for the future, and thrive wherever you end up.</p>



<p>If you're going to WCEU, here are <a href="https://poststatus.com/make-the-most-of-wceu/">some tips on getting the most out of it!</a></p>



<p>Have a great weekend,</p>



<p>— Michelle</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, 20 May 2022 19:22:17 +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:"Michelle Frechette";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:31;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:69:"Post Status: WordPress Podcast and Video Picks for the Week of May 15";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=97722";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/wordpress-podcast-and-video-picks-for-the-week-of-may-15/";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:3617:"<div class="has-background has-theme-palette-7-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt"><strong>Good viewing and listening for you this weekend!</strong> Krogsgard on memberships and churn. Web 2.0 tech leaders reflect. Mike McAlister on the journey from Atomic Blocks and Array Themes to the Liftoff Creator Course. Paid services at Underrepresented in Tech. The Pattern Creator and Directory. WCEU. Inclusive Open Source Processes and Governance. </p></div>


<h2 id="h-my-podcast-picks">My Podcast Picks <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png" alt="🎙" class="wp-smiley" /></h2>



<ul><li><strong>How I Built It</strong>: <strong>Post Status</strong> founder <strong>Brian Krogsgard</strong> <a href="https://howibuilt.it/podcast/brian-krogsgard-on-determining-membership-benefits-and-preventing-churn">on determining membership benefits and preventing churn</a>.</li><li><strong>Techmeme Ride Home:</strong> Not WordPress-related, but <a href="https://www.ridehome.info/show/techmeme-ride-home/twtr-spc-how-the-web-evolved-the-reunion-of-the-social-web-tv-crew-fixed/">this reunion of some key web 2.0 tech leaders</a> is a fascinating retrospective.</li><li><strong>Make Lemonade</strong>: <strong>Mike McAlister</strong> on <a href="https://make-lemonade.simplecast.com/episodes/mike-mcalister-kE4L0KDp">how he went from selling his WordPress business</a> to <strong>WP Engine</strong> to launching the <strong>Liftoff Creator Course</strong>.</li><li><strong>Underrepresented in Tech</strong>: It's <strong>Allie Nimmons</strong> and <strong>Michelle Frechette</strong> on <a href="https://www.underrepresentedintech.com/episode-53-underrepresented-services/">the paid services they provide</a> and why these are important additions to the UiT database.</li><li><strong>WP Tavern Jukebox</strong>: <strong>Ana Segota</strong> and <strong>Kelly Choyce-Dwan</strong> on the new <a href="https://wptavern.com/podcast/27-ana-segota-and-kelly-choyce-dwan-on-how-to-use-the-new-pattern-creator">Pattern Creator</a> and the <strong>WordPress Patterns Directory</strong>.</li><li><strong>Do The Woo:</strong> Two of the <strong>WCEU</strong> organizing team members, <strong>Takis Bouryouris</strong> and <strong>Taeke Reijenga</strong>, <a href="https://dothewoo.io/episode-223/">talk about the upcoming conference</a>.</li></ul>



<h2 id="h-my-video-pick">My Video Pick <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f4fa.png" alt="📺" class="wp-smiley" /></h2>



<ul><li><strong>Inclusive Open Source Processes and Governance</strong> is <a href="https://www.youtube.com/watch?v=-c85eLPHCNI">a great presentation</a> by <strong>Silona Bonewald</strong> via <strong>Open Source 101</strong> in early April 2022.</li></ul>



<div class="wp-container-15 wp-block-group has-theme-palette-8-background-color has-background"><div class="wp-block-group__inner-container">
<p><strong>Get our weekly WordPress community news digest</strong> — Post Status' <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f48c.png" alt="💌" class="wp-smiley" />  </p>



<p>And don't miss <strong>the latest updates from the people making WordPress</strong>. We've got you covered with <a href="https://poststatus.com/make-wordpress/">This Week at WordPress.org</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2699.png" alt="⚙" class="wp-smiley" /></p>
</div></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:"Fri, 20 May 2022 13:41:15 +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:32;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"Akismet: Version 4.2.4 of the Akismet WordPress Plugin is Now Available";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:"http://blog.akismet.com/?p=2390";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:99:"https://blog.akismet.com/2022/05/20/version-4-2-4-of-the-akismet-wordpress-plugin-is-now-available/";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:591:"<p>Version 4.2.4 of <a href="http://wordpress.org/plugins/akismet/">the Akismet plugin for WordPress</a> is now available. This update contains the following improvements:</p>



<ul><li>Improved translator instructions for comment history.</li><li>Bumped the &#8220;Tested up to&#8221; tag to WP 6.0.</li></ul>



<p>To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in <a href="http://wordpress.org/plugins/akismet/">the WordPress plugins directory</a>.</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, 20 May 2022 10:01:38 +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:"Stephane Daury";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:33;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:86:"Do The Woo Community: Do the Woo is Heading to WordCamp Europe 2022 as a Media Partner";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:28:"https://dothewoo.io/?p=71779";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:24:"https://dothewoo.io/235/";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:385:"<p>WCEU is happening in Porto, Portugal. Find Do the Woo there and join us in a podcast or let's just have a conversation. </p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/235/">Do the Woo is Heading to WordCamp Europe 2022 as a Media Partner</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</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, 20 May 2022 09: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:5:"BobWP";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:34;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:29:"WPTavern: WP Tavern Is Hiring";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=134578";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:40:"https://wptavern.com/wp-tavern-is-hiring";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:1256:"<p>WP Tavern is looking for talented writers who are eager to report on WordPress news every day. We cover a wide range of topics, including (but not limited to) the Gutenberg project, core development, e-commerce, community, plugin and theme ecosystems, events, and the wider world of open source software.&nbsp;We are looking for writers who can inform, engage, and inspire readers with their work.</p>



<p>The position requires the ability to discern the immediacy of news stories that need to be told, attention to accuracy, and the ability to cultivate sources. Applicants must be willing to engage positively with the WordPress community and maintain an unwavering commitment to serve the public interest, without corporate influence. A deep knowledge of the WordPress ecosystem and the Gutenberg project is helpful for this position.</p>



<p>WP Tavern is WordPress’ newspaper of record. We are looking for writers who can approach this community with a critical and unbiased point of view, preserving the independent and provocative spirit of the Tavern. Applicants should use the&nbsp;<a href="https://wptavern.com/contact">contact form</a>&nbsp;to get in touch, and be prepared to submit at least three writing samples for consideration.</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, 19 May 2022 18:25:55 +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:35;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"Do The Woo Community: WooCommerce Checkout and Cart Blocks with Nadir Seghir";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:28:"https://dothewoo.io/?p=71766";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:75:"https://dothewoo.io/woocommerce-checkout-and-cart-blocks-with-nadir-seghir/";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:436:"<p>Automattic engineer Nadir Seghir chats about where we are at with the WooCommerce cart and checkout blocks and where we are going.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/woocommerce-checkout-and-cart-blocks-with-nadir-seghir/">WooCommerce Checkout and Cart Blocks with Nadir Seghir</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</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, 19 May 2022 09:28: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:5:"BobWP";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:36;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"WPTavern: WooCommerce Calls for Early Testing on Custom Order Table Migrations";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=134456";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:89:"https://wptavern.com/woocommerce-calls-for-early-testing-on-custom-order-table-migrations";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:2217:"<p>At the beginning of this year, WooCommerce <a href="https://wptavern.com/woocommerce-aims-to-produce-mvp-of-custom-tables-for-orders-by-q3-2022">announced</a> its plan to produce an MVP of custom order tables by Q3, 2022, a long-awaited improvement that promises significant performance gains for stores. The plugin&#8217;s development team is now <a href="https://developer.woocommerce.com/2022/05/16/call-for-early-testing-custom-order-table-migrations/">calling</a> for developers, agencies, and hosting companies to test migration to its first implementation of customer order tables. </p>



<p>The process involves migrating orders from <code>wp_posts</code> and <code>wp_postmeta</code> to four new custom orders tables:</p>



<ol><li>wp_wc_orders</li><li>wp_wc_order_addresses</li><li>wp_wc_order_operational_data</li><li>wp_wc_orders_meta</li></ol>



<p>It requires a staging environment configured with WP-CLI and a staging database pre-loaded with order data.</p>



<p>WooCommerce developer Vedanshu Jain has created a <a href="https://developer.woocommerce.com/2022/05/16/call-for-early-testing-custom-order-table-migrations/">migration testing guide</a>, which details the custom code developers will need to add in order to enable the custom order tables. Once enabled, developers will have the option to migrate tables using WP-CLI or via Action Scheduler.</p>



<img />



<p>Jain is <a href="https://developer.woocommerce.com/2022/05/16/call-for-early-testing-custom-order-table-migrations/">requesting feedback</a> from anyone who runs the migration process with details about how many orders, server memory size, DB version, and whether or not it timed out or responded better to a different batch size.  </p>



<p>WooCommerce updating to use custom order tables will be a major change that will impact extension developers in different ways. The development team intends to publish an upgrade guide to support adoption of custom order tables after migrations have been ironed out. Later this year, when the update is anticipated to be rolled out to the core plugin, WooCommerce is aiming to make it strictly opt-in at first to allow shop owners time to make their sites compatible.</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, 18 May 2022 21:05: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: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:37;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"WordPress Foundation: The Kim Parsell Memorial Scholarship Returns for WordCamp US 2022";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://wordpressfoundation.org/?p=262042";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:108:"https://wordpressfoundation.org/news/2022/the-kim-parsell-memorial-scholarship-returns-for-wordcamp-us-2022/";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:1709:"<p>The wait is over! WordCamp US is once again being held as an in-person, and with that the WordPress Foundation’s Kim Parsell Memorial Scholarship returns.</p>



<p>Kim’s commitment and valuable contributions to the WordPress open source project are honored at each in-person WordCamp US by the WordPress Foundation. The Foundation’s goal is to further the efforts of other contributors demonstrating Kim’s spirit by helping to ease the burden that travel can bring.</p>



<p><strong>This scholarship is awarded to someone who:</strong></p>



<ul><li>Identifies as a woman.</li><li>Is a WordPress contributor.</li><li>Has never attended WordCamp US before.</li><li>Requires financial assistance to attend.</li></ul>



<p>This scholarship provides financial assistance so that the recipient can attend WordCamp US, including travel from the recipient’s home city, hotel stay for the duration of the event, and a ticket to WordCamp US.</p>



<p>Finally, since the WordPress Foundation was unable to offer the scholarship in 2020 and 2021 due to the COVID-19 pandemic, <strong>this year only there will be three (3) scholarships awarded</strong> for 2022, 2021, and 2020.</p>



<p>If you meet these requirements and would like to be considered, please <strong>apply no later than Sunday, June 26, 2022</strong> at 12 am Pacific. All applicants will be notified by July 5, 2022.</p>



<p>For more details, please visit the WordPress Foundation’s <a href="https://wordpressfoundation.org/projects/kim-parsell-memorial-scholarship/">About the Kim Parsell Memorial Scholarship</a> page.</p>



<p><a href="https://wordcampcentral.survey.fm/wcus-kim-2022">Apply for the scholarship today.</a></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, 18 May 2022 20:42: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:12:"Cate DeRosia";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:38;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:54:"Post Status: This Week at WordPress.org (May 16, 2022)";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=97849";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://poststatus.com/this-week-at-wordpress-org-may-16-2022/";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:15949:"<p class="has-theme-palette-7-background-color has-background">Each week we are highlighting the news from WordPress.org that you don't want to miss.  If you or your company create products or services that use WordPress, we've got the news you need to know. Be sure to share this resource with your product and project managers. <br /><br /><strong>Are you interested in giving back and contributing your time and skills to WordPress.org?</strong> <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://wordpress.org/support/article/contributing-to-wordpress/">Start Here ›</a><br /><br /><strong>Get our weekly WordPress community news digest</strong> — Post Status' <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — covering the WP/Woo news plus significant writing and podcasts. It's also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>



<h2 id="h-news">News</h2>



<ul><li><a href="https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-2-rc2-now-available-for-testing/"><a href="https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-3-rc3-now-available-for-testing/">WordPress 6.0 Release Candidate 3 (RC3) Now Available for Testing</a></a></li><li><a href="https://make.wordpress.org/core/2022/05/03/wordpress-6-0-field-guide/">WordPress 6.0 Field Guide</a></li><li><a href="https://wordpress.org/news/2022/05/episode-31-open-source-accessibility-celebrating-global-accessibility-awareness-day-with-guest-joe-devon/">WP Briefing: Episode 31: Open Source & Accessibility– Celebrating Global Accessibility Awareness Day With Guest Joe Devon</a></li></ul>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_a98156-c2"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<div class="wp-block-columns">
<div class="wp-block-column">
<h2 id="h-accessibility"><a href="https://make.wordpress.org/accessibility">Accessibility</a></h2>



<ul><li>Request for feedback on the&nbsp;<a href="https://make.wordpress.org/project/2022/04/01/discussion-contrib-handbook-part-1/">WordPress Accessibility Statement</a>.</li></ul>



<h2 id="h-central"><a href="https://central.wordcamp.org">Central</a></h2>



<ul><li><a href="https://central.wordcamp.org/news/2022/05/wordcamp-europe-2022-is-just-around-the-corner/">WordCamp Europe 2022 is just around the corner</a></li><li><a href="https://central.wordcamp.org/news/2022/05/join-the-european-wordpress-community-in-porto-portugal/">Join the European WordPress Community in Porto, Portugal!</a></li></ul>



<h2 id="h-core"><a href="https://make.wordpress.org/core">Core</a> </h2>



<p>Reminder: <a href="https://developer.wordpress.org/block-editor/contributors/versions-in-wordpress/">Gutenberg 13.0 ships with WordPress 6.0</a>.</p>



<ul><li><a href="https://docs.google.com/forms/d/e/1FAIpQLSenO7SibDfYYTivz46YGDoeXcY64H_3Ur_x8taze7Hzi9U11g/viewform">WordPress Hosting Image/Storage questions</a> </li><li><a href="https://github.com/WordPress/performance/issues/160">Ensure WebP/Image/Optimization plugins can integrate & use existing WebP images </a></li><li><a href="https://github.com/WordPress/performance/issues/289">Research: Impact of additional WebP images on upload</a></li><li><a href="https://github.com/WordPress/performance/issues/290">Research: WebP compatibility</a></li><li><a href="https://github.com/WordPress/wordpress-develop/pull/2722">Prime users in cache in WP_Query </a></li><li><a href="https://docs.google.com/document/d/1NzURb3u-KZTgYYHK9Gx_KPvSCX4N8Ci3oZfLsfVF7Tk/edit">Measurement overview doc</a></li><li><a href="https://docs.google.com/document/d/1elY0vgrLU2373mX3jSUj_vFZeGDyhED1WMPYwzSYiVA/edit">Capturing front-end performance metrics in WordPress doc</a> </li><li><a href="https://github.com/WordPress/performance/pull/330">Module proposal workflow</a></li><li><a href="https://core.trac.wordpress.org/ticket/55749">Large-site inefficiency in REST users endpoint used by Gutenberg editor</a></li><li><a href="https://make.wordpress.org/core/2022/05/16/a-week-in-core-may-16-2022/">A Week in Core – May 16, 2022</a></li><li><a href="https://make.wordpress.org/core/2022/05/12/whats-new-in-gutenberg-13-2-may-11/">What’s new in Gutenberg 13.2? (May 11)</a></li></ul>



<h3 id="h-devnotes">DevNotes</h3>



<p>Leading up to releasing WordPress 6.0, DevNotes and release-related information will remain.</p>



<ul><li><a href="https://make.wordpress.org/core/2022/05/03/wordpress-6-0-field-guide/">WordPress 6.0 Field Guide</a></li><li><a href="https://make.wordpress.org/core/2022/05/05/block-locking-settings-in-wordpress-6-0/">Block Locking Settings in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/04/wordpress-6-0-release-candidate-phase/">WordPress 6.0 Release Candidate Phase</a></li><li><a href="https://make.wordpress.org/core/2022/05/03/miscellaneous-dev-notes-for-wordpress-6-0/">Miscellaneous Dev Notes for WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/03/block-editor-miscellaneous-dev-notes-for-wordpress-6-0/">Block Editor miscellaneous Dev Notes for WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/03/page-creation-patterns-in-wordpress-6-0/">Page creation patterns in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/03/global-styles-variations-in-wordpress-6-0/">Global Styles variations in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/03/separator-block-updated-to-use-block-supports-color-settings/">Separator block: Updated to use block supports color settings</a></li><li><a href="https://make.wordpress.org/core/2022/05/03/block-markup-updates-for-image-quote-list-and-group-blocks/">Block markup updates for image, quote, list, and group blocks</a></li><li><a href="https://make.wordpress.org/core/2022/05/03/support-for-handling-resolution-errors-for-editor-data-module/">Support for handling resolution errors for Editor data module</a></li><li><a href="https://make.wordpress.org/core/2022/04/28/taxonomy-performance-improvements-in-wordpress-6-0/" target="_blank" rel="noreferrer noopener">Taxonomy performance improvements in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/04/27/changes-to-do_parse_request-filter-in-wordpress-6-0/">Changes to the do_parse_request filter in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/04/29/caching-improvements-in-wordpress-6-0/">Caching improvements in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/04/27/new-filter-to-modify-content-images-in-wordpress-6-0/">New filter to modify content images in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/02/media-storing-file-size-as-part-of-metadata/">Media: storing file size as part of the metadata</a></li><li><a href="https://make.wordpress.org/core/2022/05/05/updates-to-the-wordpress-create-block-templating-system/">Updates to the @wordpress/create-block templating system</a></li><li><a href="https://make.wordpress.org/core/2022/05/02/object-type-specific-registration-hooks-in-6-0/">Object type-specific registration hooks in 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/04/28/taxonomy-performance-improvements-in-wordpress-6-0/">Taxonomy performance improvements in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/02/new-features-for-working-with-patterns-and-themes-in-wordpress-6-0/">New features for working with patterns and themes in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/05/02/theme-export-in-wordpress-6-0/">Theme export in WordPress 6.0</a></li><li><a href="https://make.wordpress.org/core/2022/04/29/wp_user_query-now-accepts-fields-options-in-wordpress-6-0/">WP_User_Query now accepts fields options in WordPress 6.0&nbsp;</a></li><li><a href="https://make.wordpress.org/core/2022/05/02/performance-increase-for-sites-with-large-user-counts-now-also-available-on-single-site/">Performance increase for sites with large user counts (now also available on a single site)</a></li></ul>



<h2 id="h-docs"><a href="https://make.wordpress.org/docs">Docs</a></h2>



<ul><li><a href="https://make.wordpress.org/updates/2022/05/16/documentation-team-update-may-16-2022/">Documentation Team Update – May 16, 2022</a></li></ul>



<h3 id="h-support-docs"><a href="https://wordpress.org/support/articles">Support Docs:</a></h3>



<ul><li><a href="https://wordpress.org/support/article/working-with-blocks/">Working with blocks</a></li></ul>



<h3 id="h-developer-docs">Developer Docs: </h3>



<ul><li><a href="https://developer.wordpress.org/block-editor/how-to-guides/data-basics/4-building-a-create-page-form/">Part 4: Building a <em>Create page</em> form</a></li></ul>
</div>



<div class="wp-block-column">
<h2 id="h-community"><a href="https://make.wordpress.org/community">Community</a></h2>



<ul><li><a href="https://make.wordpress.org/community/2022/04/22/wpdiversity-is-expanding-to-apac/"></a><a href="https://make.wordpress.org/community/2022/05/11/join-the-community-team-for-a-wpdiversity-writing-sprint-may-23-to-may-30/">Join the Community Team for a #WPDiversity Writing Sprint: May 23 to May 30</a></li></ul>



<h2 id="h-design"><a href="https://make.wordpress.org/design">Design</a></h2>



<ul><li><a href="https://make.wordpress.org/design/2022/05/13/poll-finding-a-new-meeting-time/">Poll: Finding a new meeting time</a></li></ul>



<h2 id="h-hosting"><a href="https://make.wordpress.org/hosting">Hosting</a></h2>



<ul><li><a href="https://make.wordpress.org/hosting/2022/05/04/get-ready-for-wordpress-6-0/">Get ready for WordPress 6.0</a></li></ul>



<h2 id="h-meta"><a href="https://make.wordpress.org/meta">Meta</a></h2>



<ul><li><a href="https://make.wordpress.org/meta/2022/04/28/proposal-make-wordpress-team-or-project-updates/">Proposal: Make WordPress Team or Project Updates</a></li></ul>



<h2 id="h-mobile"><a href="https://make.wordpress.org/mobile">Mobile</a></h2>



<ul><li><a href="https://make.wordpress.org/updates/2022/05/18/mobile-team-update-may-18th-3/">Mobile Team Update – May 18th</a></li><li><a href="https://make.wordpress.org/mobile/2022/05/17/call-for-testing-wordpress-for-android-19-9/">Call for Testing: WordPress for Android 19.9</a></li><li><a href="https://make.wordpress.org/mobile/2022/05/16/call-for-testing-wordpress-for-ios-19-9/">Call for Testing: WordPress for iOS 19.9</a></li></ul>



<h2 id="h-plugins"><a href="https://make.wordpress.org/plugins">Plugins</a></h2>



<ul><li><a href="https://make.wordpress.org/updates/2022/05/17/plugin-review-team-update-16-may-2022/">Plugin Review Team Update: 16 May 2022</a></li></ul>



<h2 id="h-polyglots"><a href="https://make.wordpress.org/polyglots">Polyglots</a></h2>



<ul><li><a href="https://make.wordpress.org/polyglots/2022/05/02/wordpress-6-0-ready-to-be-translated/">WordPress 6.0 ready to be translated</a></li></ul>



<h2 id="h-project"><a href="https://make.wordpress.org/project">Project</a></h2>



<ul><li><a href="https://make.wordpress.org/project/2022/04/29/discussion-contrib-handbook-part-2/">Discussion: Contrib Handbook, Part 2</a></li><li><a href="https://make.wordpress.org/project/2022/04/01/discussion-contrib-handbook-part-1/">Discussion: Contrib Handbook, Part 1</a></li></ul>



<h2 id="h-test"><a href="https://make.wordpress.org/test">Test</a></h2>



<ul><li><a href="https://make.wordpress.org/test/2022/04/28/fse-program-testing-call-14-rallying-recipe-reviewers/">FSE Program Testing Call #14: Rallying Recipe Reviewers</a></li></ul>



<h2 id="h-themes"><a href="https://make.wordpress.org/themes">Themes</a></h2>



<ul><li><a href="https://make.wordpress.org/themes/2022/04/28/latest-changes-in-gutenberg-themes-13-0-release/">Latest changes in Gutenberg + Themes: 13.0 release</a></li><li><a href="https://make.wordpress.org/updates/2022/05/10/themes-team-update-may-10-2022/">Themes team update May 10, 2022</a></li></ul>



<h2 id="h-support"><a href="https://make.wordpress.org/support">Support</a></h2>



<ul><li><a href="https://make.wordpress.org/support/2022/04/off-forum-support-requests/">Off forum support requests</a></li></ul>



<h2 id="h-training"><a href="https://make.wordpress.org/training">Training</a></h2>



<ul><li><a href="https://make.wordpress.org/training/2022/04/19/migrating-contributor-training-to-learn-wordpress/"></a><a href="https://make.wordpress.org/training/2022/05/03/may-2022-sprint/">May 2022 Sprint</a></li><li><a href="https://make.wordpress.org/training/2022/05/05/the-training-team-faculty-program-is-now-live/">The Training Team Faculty Program is now live</a></li></ul>



<h4 id="h-social-learning-spaces">Social Learning Spaces:</h4>



<ul><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"><a href="https://learn.wordpress.org/?meeting=i-want-a-website-not-a-blog">I want a Website, not a Blog!</a></a></li><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"><a href="https://learn.wordpress.org/?meeting=bloggers-own-your-content-and-share-it-everywhere">Bloggers: Own your Content and Share it Everywhere</a></a></li><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"><a href="https://learn.wordpress.org/?meeting=hello-blocks-creating-a-custom-block">Hello Blocks! Creating a Custom Block</a></a></li><li><a href="https://learn.wordpress.org/?meeting=open-source-principles-and-wordpress"><a href="https://learn.wordpress.org/?meeting=design-with-me-create-a-simple-website-for-your-small-business">Design With Me: Create a Simple Website for your Small Business</a></a></li></ul>
</div>
</div>



<h2 id="5ftf"><a href="https://wordpress.org/five-for-the-future/">Five for the Future</a></h2>



<p>What's happening specific to Five for the Future? Provide your feedback on these posts:</p>



<ul><li><a href="https://github.com/WordPress/five-for-the-future/issues/194">Default workflow for team membership lifecycle? </a></li><li><a href="https://github.com/WordPress/five-for-the-future/issues/192">Add activity when Meetup organizers host events</a></li><li><a href="https://github.com/WordPress/five-for-the-future/issues/189">Update Usermeta with latest 5ftf contribution.</a></li></ul>



<div class="wp-block-spacer"></div>



<div class="wp-block-media-text alignwide is-stacked-on-mobile has-background"><a href="https://poststatus.com/"><img src="https://cdn.poststatus.com/wp-content/uploads/2021/09/vertical-post-status-logo-250.png" alt="Post Status" class="wp-image-85823 size-full" /></a><div class="wp-block-media-text__content">
<p class="has-text-align-left has-normal-font-size" id="h-get-ready-for-remote-work">You — and <a href="https://poststatus.com/business-membership/">your whole team</a> can <a href="https://poststatus.com/post-status-membership-club/">Join Post Status</a> too!</p>



<p class="has-text-align-left has-small-font-size"><strong>Build your network. Learn with others. Find your next job — or your next hire.</strong> Read the <strong>Post Status</strong> <a href="https://poststatus.com/newsletter/">newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2709.png" alt="✉" class="wp-smiley" /> Listen to <a href="https://poststatus.com/podcasts/">podcasts</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png" alt="🎙" class="wp-smiley" /> Follow <a href="https://twitter.com/post_status/">@Post_Status</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f426.png" alt="🐦" class="wp-smiley" /></p>
</div></div>



<div class="wp-block-spacer"></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:"Wed, 18 May 2022 20: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:"Courtney Robertson";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:39;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:126:"WPTavern: Software Freedom Conservancy Receives Court Ruling Affirming GPL as Both Copyright License and Contractual Agreement";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=134452";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:137:"https://wptavern.com/software-freedom-conservancy-receives-court-ruling-affirming-gpl-as-both-copyright-license-and-contractual-agreement";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:4584:"<p>The <a href="https://sfconservancy.org/">Software Freedom Conservancy</a> (SFC),  a non-profit that provides infrastructure support for free and open source software projects, has received a favorable ruling in its <a href="https://wptavern.com/software-freedom-conservancy-takes-on-vizio-in-lawsuit-alleging-gpl-violations">right-to-repair lawsuit against Vizio</a>, an American TV manufacturer. The SFC alleges that Vizio has demonstrated “repeated failures to fulfill even the basic requirements of the General Public License (GPL),&#8221; after the company refused to provide the source code for software with copyleft licenses that it bundles with its products.</p>



<p>Vizio had filed a request to “remove” the case from California State Court into U.S. Federal Court. After hearing oral arguments from both sides, the court has granted SFC&#8217;s motion to remand the case back to California State Court. </p>



<p>In the <a href="https://storage.courtlistener.com/recap/gov.uscourts.cacd.837808/gov.uscourts.cacd.837808.30.0.pdf">ruling</a>, US District Court judge Josephine L. Staton stated that the GPL introduces &#8220;an additional contractual promise separate and distinct from any rights provided by the copyright laws:&#8221;</p>



<blockquote class="wp-block-quote"><p>The Court finds Versata’s reasoning persuasive, and it finds here, as the court<br />found there, that the enforcement of “an additional contractual promise separate and distinct from any rights provided by the copyright laws” amounts to an “extra element,” and therefore, SFC’s claims are not preempted. Id. at *5. There is an extra element to SFC’s claims because SFC is asserting, as a third-party beneficiary of the GPL Agreements, that it is entitled to receive source code under the terms of those agreements. There is no right to receive certain works—or source code in particular—under the Copyright Act; indeed, the Act’s primary purpose is to limit who may reproduce, prepare derivative works, distribute, and display protected works. As SFC points out in its briefing, the right to receive the source code would appear to be “the very opposite” of those exclusive rights. (Reply, Doc. 26, at 17.) The fact that SFC claims status as a third-party beneficiary to the GPL Agreements and not the actual copyright holder—and therefore, has no authority to impose limitations on the reproduction and distribution of the software—only underscores that the contractual right at issue is qualitatively different from the rights under the Copyright Act. Thus, there can be no question that the extra element—that SFC is third-party enforcing its right to receive source code under the terms of a contract—transforms the nature of the action.</p></blockquote>



<p>One of the functions of the SFC is to assist member projects in enforcing the terms of FLOSS licenses, including through litigation. This particular case is unique because 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>



<p>“The ruling is a watershed moment in the history of copyleft licensing,&#8221; SFC executive director Karen Sandler said. &#8220;This ruling shows that the GPL agreements function both as copyright licenses and as contractual agreements.&#8221;</p>



<p>SFC  contends that many electronics products are built for planned premature obsolescence and that companies often do this by violating the GPL. If the product is bundled with copyleft software, a consumer has the right to modify, improve, and repair the software. For this the be possible, the companies producing the products must make the source code available. This also enables consumers to find skilled people to repair their products when a device fails after updates have been disabled so that products do not become nonfunctional. This ruling is not just a major win for the GPL but also for consumers who may not know that companies violating the GPL significantly impact their ability to find repairs for electronic products.</p>



<p>“Software Freedom Conservancy looks forward to our opportunity to prove, in state court, our third-party beneficiary right to the complete, corresponding source code as defined by the GPL and related agreements,” Sandler said. “This claim is central to the right to software repair, as it allows users to exercise the right to copy, share, modify, and reinstall the software on the devices that they receive.”</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, 18 May 2022 18:03:35 +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:40;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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: #27 – Ana Segota and Kelly Choyce-Dwan on How To Use the New Pattern Creator";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:48:"https://wptavern.com/?post_type=podcast&p=134337";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:102:"https://wptavern.com/podcast/27-ana-segota-and-kelly-choyce-dwan-on-how-to-use-the-new-pattern-creator";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:48510:"<p>On the podcast today we have <a href="https://twitter.com/ana_segota">Ana Segota</a> and <a href="https://twitter.com/ryelle">Kelly Choyce-Dwan</a>.</p>



<p>I suspect that you might have heard about block patterns, but if you haven’t, you’re in for a treat. Patterns are collections of blocks which anyone can assemble for easy reuse at a later date. You can make them as simple or as complex as you, style them and save them away. When you’re ready to reuse them, they’re just one click away. It’s a great time saver.</p>



<p>Having said that, not all of us are great at design, or perhaps we’ve just not had the time to explore how block patterns are created. Wouldn’t it be great if there was a source of patterns which we could use in our WordPress websites, safe in the knowledge that they were completely free to use? There is, &nbsp; and it’s called the Pattern Directory. You simply find a pattern you like and copy / paste it into your site.</p>



<p>You could stop there, but you could also use this as a way of learning how blocks are constructed. Open up the pattern to see how it’s laid out. What settings were used to create the styling?</p>



<p>Right now, the Pattern Directory is quite small. There’s a few hundred patterns to explore, but it could certainly do with some more contributions, and that is what this podcast is all about.</p>



<p>The Pattern Creator is the way to create patterns so that they can be submitted, reviewed, and hopefully accepted into the Pattern Directory.</p>



<p>We’ve got two perspectives on the podcast today from people who come at it from different angles.</p>



<p>Ana is a self taught WordPress themer and designer who is making use of patterns at <a href="https://www.anarieldesign.com/">Anariel Design</a>, her website building business, and Kelly is an Automattician who has been working with the team building the Pattern Directory and Creator.</p>



<p>We talk about how the Creator works, how you can submit your patterns and what constraints are there for having your submissions accepted.</p>



<p>So, if you’re curious about how patterns can speed up your website building workflow, this episode is for you.</p>



<h2>Useful links.</h2>



<p><a href="https://wordpress.org/news/2022/03/get-creative-with-the-all-new-pattern-creator/">https://wordpress.org/news/2022/03/get-creative-with-the-all-new-pattern-creator/</a></p>



<p><a href="https://wordpress.org/patterns/">https://wordpress.org/patterns/</a></p>



<p><a href="https://wordpress.org/patterns/about/">https://wordpress.org/patterns/about/</a></p>



<p><a href="https://wordpress.org/patterns/new-pattern/">https://wordpress.org/patterns/new-pattern/</a></p>



<p>Ana is <a href="https://twitter.com/ana_segota">@ana_segota</a> on Twitter, and @anasegota on the Make Slack Channel.</p>



<p>Kelly is <a href="https://twitter.com/ryelle">@ryelle</a> on both Twitter and the Make Slack Channel.</p>



Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast, which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, learning about the new pattern creator.</p>



<p>If you&#8217;d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WP Tavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.</p>



<p>If you&#8217;ve got a topic that you&#8217;d like us to feature on the podcast, well, I&#8217;m very keen to hear from you, and hopefully get you, or your idea featured on the show. Head over to WP Tavern.com forward slash contact forward slash jukebox, and use the contact form there.</p>



<p>So on the podcast today, we have Ana Segota and Kelly Choyce-Dwan. I suspect that you&#8217;ve heard about block patterns, but if you haven&#8217;t, you&#8217;re in for a treat.</p>



<p>Patterns are collections of blocks which anyone can assemble for easy reuse at a later date. You can make them as simple or as complex as you like. Style them and save them away. When you&#8217;re ready to reuse them, they&#8217;re just one click away. It&#8217;s a great time-saver .</p>



<p>Having said that, not all of us are great at design, or perhaps we&#8217;ve just not had the time to explore how block patterns are created. Wouldn&#8217;t it be great if there was a source of patterns which we could use in our WordPress websites, safe in the knowledge that they were completely free to use? There is, and it&#8217;s called the pattern directory. You simply find a pattern that you like and copy paste it into your site.</p>



<p>You could stop there, but you could also use this as a way of learning how blocks are constructed. Open up the pattern and see how it&#8217;s laid out. What settings we&#8217;ll use to create the styling?</p>



<p>Right now, the pattern directory is quite small. There&#8217;s a few hundred pounds to explore, but it could certainly do with some more contributions. And that is what this podcast is about. The pattern creator is the way to create patterns so that they can be submitted, reviewed, and hopefully accepted into the Pattern Directory. We&#8217;ve got two perspectives on the podcast today from people who come at it from different angles.</p>



<p>Ana is a self-taught WordPress themer, and a designer who is making use of patterns in her website builds. And Kelly is an Automattician who has been working with the team building the Pattern Directory and Creator. We talk about how the creator works, how you can submit your patterns and what constraints are there for having your submissions accepted.</p>



<p>So, if you&#8217;re curious about how patterns can speed up your website building workflow, this episode is for you.</p>



<p>If you&#8217;re interested in finding out more, you can find all the links in the show notes by heading over to WP tavern.com forward slash podcast, where you&#8217;ll find all the other episodes as well.</p>



<p>And so without further delay, I bring you Ana Segota and Kelly Choyce-Dwan.</p>



<p>I am joined on the podcast today by Ana Segota and Kelly Choyce-Dwan. Hello.</p>



<p>[00:04:01] <strong>Ana Segota:</strong> Hi.</p>



<p>[00:04:01] <strong>Kelly Choyce-Dwan:</strong> Hello.</p>



<p>[00:04:02] <strong>Nathan Wrigley:</strong> Very nice to have you both here. As we always do at the beginning of the podcast, I&#8217;m going to give both of you an opportunity to introduce yourselves, to give us a bit of an orientation.</p>



<p>If you&#8217;ve listened to the introduction to this podcast, you probably know that we&#8217;re going to be talking about the pattern creator. And so it would be important to know why the two guests today are coming on talking about that. So, we&#8217;ll take it one at a time. We&#8217;ll begin with Ana. Ana, just tell us a little bit about your journey with WordPress and how come it is that you became involved with the pattern creator.</p>



<p>[00:04:33] <strong>Ana Segota:</strong> So, hi Nathan, nice to meet you and thank you for inviting me. So I&#8217;m Ana Segota, and I am a themer, and I love creating WordPress themes using block patterns. I always was more as a designer, but I learned to code to be able to create WordPress themes myself, but now having a block patterns is such a relief for me because I can concentrate on design more.</p>



<p>[00:05:04] <strong>Nathan Wrigley:</strong> That&#8217;s really nice. Thank you. Yeah. The intention of the tool is to make all of those decisions a little bit easier. So it&#8217;s nice, nice to know that in your case, it&#8217;s working. So, okay that&#8217;s going to be one perspective that we&#8217;ve got in the show today. And another perspective comes from Kelly. So Kelly, just spend a moment, tell us who you are please.</p>



<p>[00:05:21] <strong>Kelly Choyce-Dwan:</strong> Sure. So my name is Kelly Choyce-Dwan, also ryelle online. I work at Automattic and I have for over seven years. I started with WordPress in 2009, and I&#8217;m now working on the Meta team where my focus recently has been on the pattern directory and pattern creator.</p>



<p>[00:05:41] <strong>Nathan Wrigley:</strong> Now many people listening to this podcast will be very up-to-date users of WordPress. There&#8217;ll be using the tools that are shipping all of the time, and they may well have discovered patterns and be using them to great effect.</p>



<p>On the other hand, I suspect that there&#8217;ll be a fair amount of people who as yet have not delved into patterns. They may know what they are. They may not. So I&#8217;m wondering if we could really just rewind a little bit, make no assumptions about anybody&#8217;s knowledge about patterns and just lay out what they are. So it&#8217;s a very general question. Either of you feel free to answer it. What are patterns in WordPress and why might you wish to use them?</p>



<p>[00:06:24] <strong>Ana Segota:</strong> So for me block patterns, I like predefined and ready to use layout that you can click or drug and create pages. It&#8217;s like a collection of blocks arranged together to help you create different layouts. If you&#8217;ve used sometimes page builders, or Elementor templates, for example, it&#8217;s the same thing. You can use them on your website. You can adjust them, change the layout, change the colors. And I think they&#8217;re very useful.</p>



<p>[00:06:59] <strong>Nathan Wrigley:</strong> Thank you. So they are basically quick ways to build websites. You&#8217;re using other people&#8217;s predefined layouts. The work, in great measure, has been done for you. You can discover collections of blocks, which are generically called patterns, and you can click on those and import them into your post or page or whatever it might be.</p>



<p>So it speeds things up. I&#8217;m curious, for those of you, who&#8217;ve never used this before again, how do you actually build them? What&#8217;s the process that one might find themselves in, and bear in mind, we might be speaking to users of WordPress who are familiar with page builders, and don&#8217;t really find themselves interacting with the WordPress block editor.</p>



<p>So we may need to have a little bit of a description around there. What are we actually doing? How do we create and build patterns?</p>



<p>[00:07:51] <strong>Ana Segota:</strong> Okay. so mostly, I&#8217;m building block patterns for the themes. As a background, I first start, with niche, different niche, and what can be useful for that niche. And then I start creating block patterns directly in the editor, where you have all the options of block that you can combine in one block pattern.</p>



<p>So mostly I started with a group block, where I put then columns or cover or images, and start creating different ideas and different layout.</p>



<p>[00:08:34] <strong>Nathan Wrigley:</strong> Are you able to save those, as WordPress currently stands? Are you able to save those and I&#8217;ll stay with Ana. Are you able to save those Ana so that they can be reused on other websites. In other words, can you save more time by having your own little collection of blocks, which you then can use on this website over here and this other completely different website?</p>



<p>[00:08:58] <strong>Ana Segota:</strong> Maybe Kelly knows better, the other way, but what I know you can always copy the block you have and paste it on other website. Or you can export it. But not sure if you can save it inside the editor for like a gallery or something. I&#8217;m not sure that you can, or if you can do this, maybe Kelly knows that.</p>



<p>[00:09:22] <strong>Kelly Choyce-Dwan:</strong> Well, I know that you can, if you copy the block code into like a code file, the you can register it that way, but it requires code.</p>



<p>[00:09:33] <strong>Ana Segota:</strong> I think, there is no easy way to save it in a gallery for the beginner user, for example.</p>



<p>[00:09:41] <strong>Nathan Wrigley:</strong> At the moment, it feels as though it is the domain of people who are fairly experienced with WordPress. All of the tooling, with things like Elementor that you described, where you, you might have a private cloud of things that you&#8217;ve created in the past, and you can log in, and there&#8217;s a cloud service attached and you can download those to all of the other websites. We&#8217;re not quite at that point yet, although maybe some of the discussion that we&#8217;ll have today will revolve around that.</p>



<p>[00:10:10] <strong>Ana Segota:</strong> Yeah, I would love that.</p>



<p>[00:10:12] <strong>Nathan Wrigley:</strong> Yeah, that would be a really nice addition.</p>



<p>[00:10:14] <strong>Ana Segota:</strong> But I think the, pattern creator is doing some kind of saving those block patterns and one place where you can reuse it. But we will come to it.</p>



<p>[00:10:24] <strong>Nathan Wrigley:</strong> That&#8217;s okay. We&#8217;ll come to that in a moment. Just to say, patterns are collections of blocks and you piece them together, akin to a jigsaw and you build up designs, and style those designs, add images, add forms, add whatever it might be, background, color, padding, and so on, until you&#8217;ve got something that you&#8217;d like to look off. And at the moment, it probably lives within one WordPress website. But you can copy and paste that over somewhere else, but there&#8217;s no sort of cloud functionality.</p>



<p>And so, to the main conversation today, which is the pattern creator. Just so that you know, the links will be in the show notes to everything that we talk about today. And the pattern creator may well be something that you want to go and play with because it enables you to do a very large amount more than potentially you can do in your normal WordPress website. So, whoever wishes to take this. What is the pattern creator? Hopefully we&#8217;ll be providing people with the link so they can find that. That&#8217;s all good. But what&#8217;s the purpose of it? Why was it built? Why did the WordPress team decide that a tool like this needed to exist?</p>



<p>[00:11:33] <strong>Kelly Choyce-Dwan:</strong> So the pattern creator is a place to go and create patterns to share with anyone who uses WordPress, and it was created to make the process of making a sharing patterns easier. It&#8217;s a place that you can go and make a pattern and you know that it can be reused without having to write that code.</p>



<p>[00:11:54] <strong>Nathan Wrigley:</strong> So, at the moment it&#8217;s not only is it a place where you can go and create patterns. It&#8217;s a place where you can go and discover other people&#8217;s already created patterns. And if you&#8217;re, if you&#8217;re coming to this podcast from another page builder, think about it as rows. You&#8217;re essentially grabbing rows from websites or component parts of websites. And so it serves that double purpose. Not only can you create your own, but you can also go and freely download other people&#8217;s work. Have I got that right? Have I misstated that?</p>



<p>[00:12:25] <strong>Kelly Choyce-Dwan:</strong> That&#8217;s correct?</p>



<p>[00:12:26] <strong>Nathan Wrigley:</strong> So in terms of how the editor works, we need to go to the website, the pattern creator website. And once we&#8217;re there, my understanding is that you need a, a wordpress.org account.</p>



<p>Once you&#8217;ve got yourself, a wordpress.org account, you can log in and you are presented with something which looks very, very similar to the usual WordPress block editor interface. It&#8217;s a little bit more spartan because the menu on the left kind of basically doesn&#8217;t exist. So all of those options for posts and pages and what have you are gone. Let&#8217;s talk about the design decisions.</p>



<p>So the menu on the left is gone. We&#8217;ve got the option to add blocks. Are we just dealing with a subset of the core blocks or can we add any of the core blocks?</p>



<p>[00:13:15] <strong>Kelly Choyce-Dwan:</strong> It is a subset currently, because we don&#8217;t have the dynamic content that might be on your website. So we can&#8217;t replicate the full experience of using that block. But almost all of the core blocks are available.</p>



<p>[00:13:30] <strong>Nathan Wrigley:</strong> Okay, so you can log in and you can start building out your blocks, or rather, I should say you can start building out your patterns. Then presumably there&#8217;s some kind of save process. And if you&#8217;re happy with things, can you use this if you chose to do it this way, can you use this as a private repository of your own blocks, that you&#8217;re maybe not ready to share with the world? Maybe they have to be kept in a draft state or something like that. Could it be used in that way? I know that&#8217;s not the intention. The intention is to have them shareable, but you were to design something and be not entirely satisfied with it, could you keep it there and come back to it at a later date and tweak it?</p>



<p>[00:14:13] <strong>Kelly Choyce-Dwan:</strong> Yeah, totally. You can save things as drafts. Actually, when we were first building it out, one of the ideas was that it could be a private repo for you to put your own patterns in. That isn&#8217;t built yet, but it could be in the future.</p>



<p>[00:14:26] <strong>Nathan Wrigley:</strong> So there is a kind of workaround to make it a directory of your own, if you simply save things as draft. But that isn&#8217;t the point. The intention is to make it universally available to everybody. And so on.</p>



<p>Does this require an up to date version of Gutenberg on the backend? So just to be clear, it&#8217;s like a SaaS product. You&#8217;re not installing WordPress anywhere. You are just going to a website and interacting with it. But I&#8217;m just curious to know, as Gutenberg is updated and modified and the blocks change, we&#8217;re several years in, and there&#8217;s been a great deal of change in the way that certain things work.</p>



<p>Do you have confidence that everything that you build today will look the same in, let&#8217;s say a couple of years time. In other words, do you anticipate that some things may break in the future or are you trying as hard as possible to mitigate against that?</p>



<p>[00:15:18] <strong>Kelly Choyce-Dwan:</strong> Well, I hope it won&#8217;t, but the pattern creator is using always the stable version of Gutenberg. So it will always be up-to-date when you&#8217;re creating patterns. Patterns created a few months ago, we&#8217;re created with an older version of Gutenberg, but between backwards compatibility block transformation, Gutenberg is trying not to break your content too. So I&#8217;m fairly confident that things will continue to work. If there are patterns that do brake, we have a reporting mechanism for reporting that.</p>



<p>[00:15:51] <strong>Nathan Wrigley:</strong> So it&#8217;s just Core blocks that we need to worry about. And it&#8217;s a subset of the Core blocks. Now, I&#8217;m looking on the interface at the moment. There&#8217;s the option for me to add a title? Obviously that&#8217;s just for the purposes of knowing what the pattern is that I&#8217;m saving somewhere. And then I can, in the normal way, click the little plus icon and I can add blocks as I choose. Put a group in, put some columns in and so on, and fiddle with those blocks just as I would do on my regular WordPress website.</p>



<p>And I&#8217;ve got the list view where I can see the stack of all of the different things that. I&#8217;ve created. And then on the right-hand side, you&#8217;ve got a title and a description. Do both of those serve the purpose of showing to somebody, once it&#8217;s been submitted to the pattern directory, which we&#8217;ll get onto in just a moment. Those titles and descriptions would give the people, browsing the pattern directory, some orientation as to what it was about and what it was designed to achieve.</p>



<p>[00:16:46] <strong>Kelly Choyce-Dwan:</strong> Yeah, that&#8217;s right. The title is the pattern title, and it&#8217;s the same when you&#8217;re in that little sidebar and the top title, they&#8217;re just two inputs for the same thing. Good title would describe what the pattern is, like one of the pattern contains, what it should be used for.</p>



<p>[00:17:01] <strong>Nathan Wrigley:</strong> Then in order to presumably aid search on the other end in the pattern directory. Currently we have six categories. There&#8217;s no option to create categories of your own. At the minute we look like we&#8217;ve got buttons, columns, gallery, header, images, text, and then there&#8217;s the option to add in keywords, maximum of 10.</p>



<p>Again, is this all just to help the taxonomy of it, to help assist people on the other side to locate things which you&#8217;ve got buttons in and specifically columns and galleries and so on? Is that the That&#8217;s the sole purpose of that.</p>



<p>[00:17:34] <strong>Kelly Choyce-Dwan:</strong> That&#8217;s right. And, they&#8217;re also used, those are the same properties that are used in WordPress Core when you&#8217;re registering patterns.</p>



<p>[00:17:41] <strong>Nathan Wrigley:</strong> So I could spend hours happily building out my new blocks and constructing them up into patterns and saving them away. And once I&#8217;ve got something that I&#8217;m happy with, there&#8217;s a blue submit button at the top right hand corner in the same way that you would have publish in WordPress typically, but this is submit.</p>



<p>What is the process, what&#8217;s going on there? What is the list of things which happen after that? So I&#8217;m thinking in terms of, I just clicked submit, but presumably at that point, all sorts of other things are set in motion. Maybe it&#8217;s sent to a particular team and people have to authorize things and check that it doesn&#8217;t break any guidelines. And that might be a long list of things that go on in the background there.</p>



<p>[00:18:24] <strong>Kelly Choyce-Dwan:</strong> Yeah. So when you submit a pattern, it asks you a few things more just to make sure you filled out all of your details. there are a few things that we&#8217;ll check for automatically, making sure you&#8217;re using a decent title. We&#8217;ve had a few patterns that are just called my pattern, which isn&#8217;t helpful for other people. So we detect things like that.</p>



<p>So after the automated checks, it does get submitted as pending. So it does not automatically approved yet. And there is a pattern review team that will look through the pending patterns and publish things that are valid. Most things do get published. So you probably would get published within a day or two.</p>



<p>[00:19:02] <strong>Ana Segota:</strong> It&#8217;s mostly hours or a day. I submitted here, so top, one day</p>



<p>[00:19:08] <strong>Nathan Wrigley:</strong> Yeah, it&#8217;s really quick. A big gripe about the, let&#8217;s say the theme review team or the plugin review team was that there was quite a long wait, sometimes very long. There&#8217;s a lot more complexity, I guess, within a theme, a lot more code floating about. So at the moment. if you submit something, as of, let&#8217;s say May 2022, you&#8217;re very likely to have a decision fairly quickly.</p>



<p>In terms of that being authorized, what are the guidelines? What are the kinds of things that are allowed and disallowed? In other words, so you mentioned that a good title, a good descriptive title is going to set you on the road to having its, authorized and put on the pattern directory.</p>



<p>Are there any other guidelines that need to be, you need to be mindful of? Not only in terms of getting it submitted, but things that you don&#8217;t want people to submit because it contravenes certain rules or regulations.</p>



<p>[00:20:03] <strong>Ana Segota:</strong> I think the most important part is to combine multiple blocks together, so not just to use one block and post it. So multiply blocks together and create some interesting and useful layouts. So maybe front design part and also something that can be creative and useful to the users. Also to highlight the capabilities of the blocks they contain and provide a starting point to customize the content.</p>



<p>Good pattern book needs to be, has a well-defined purpose too. And for don&#8217;ts, maybe to avoid to design patterns for a single theme. So to think about it to be used in different websites. Not to create a pattern that is like a full page. Or just a simple pattern that is using a paragraph. And I think you need to use photos from the gallery there. You can&#8217;t import your photos or from some other website, and that&#8217;s probably it.</p>



<p>[00:21:11] <strong>Nathan Wrigley:</strong> So the photos are coming in from, Kelly, maybe you can help us out here. Are they coming in from Openverse?</p>



<p>[00:21:18] <strong>Kelly Choyce-Dwan:</strong> They are yeah. It&#8217;s all CC0 photos from Openverse. So they&#8217;re able to be used by anyone without any, without worry about crediting people.</p>



<p>[00:21:27] <strong>Ana Segota:</strong> Yeah, that&#8217;s very helpful.</p>



<p>[00:21:30] <strong>Nathan Wrigley:</strong> Another podcast episode altogether isn&#8217;t it? The whole Openverse project&#8217;s fabulous. Yeah. so obviously there&#8217;s constraints in terms of the do&#8217;s, you know, it needs to be usable on multiple websites, and so on, just as Ana said, but there&#8217;s some certain don&#8217;ts as well. We&#8217;ve prevented the ability to upload images by just using Openverse images, which is great.</p>



<p>But also, I guess that would be in terms of the text that you write into paragraph or heading fields, there would be a requirement for it to be, let&#8217;s call it family friendly. You know, we don&#8217;t want anything which might cause anybody any hassle and presumably that&#8217;s a trip wire which the team would immediately reject it on.</p>



<p>So, okay. Let&#8217;s let&#8217;s imagine that we&#8217;ve built this fabulous pattern. It&#8217;s absolutely hit the guidance on the head and it&#8217;s been approved. What then? Where does it go? Where does it live? How can other people find it?</p>



<p>[00:22:24] <strong>Kelly Choyce-Dwan:</strong> So it&#8217;s in the pattern directory, which is just wordpress.org/patterns. You can use that website to search through patterns. Once you found a pattern that you like, you&#8217;re able to use it in your own website, just by simply copying it. And there is a copy button on each pattern that you can use to copy the code for it.</p>



<p>And if you just paste that straight into your editor, you have that pattern.</p>



<p>[00:22:48] <strong>Nathan Wrigley:</strong> So, you go to the pattern directory, presumably you would then search and filter against the things which you created when you were submitting your pattern. And then there&#8217;s a simple copy and paste button. You copy it. It&#8217;s in the clipboard of your computer and you just go over to your website and in an empty block, there&#8217;s no sort of container or wrapper that you need to stick it in. You literally just paste it into a brand new empty text block and all will work?</p>



<p>[00:23:18] <strong>Kelly Choyce-Dwan:</strong> Yep.</p>



<p>[00:23:19] <strong>Ana Segota:</strong> Yeah.</p>



<p>[00:23:19] <strong>Nathan Wrigley:</strong> Are there any gotchas there? Because that process, whilst it&#8217;s not necessarily quite as optimal as the cloud that we were talking about earlier, where you could actually see it within your WordPress website, which I guess ultimately would be an easier experience?</p>



<p>Does it always work? Are there any situations where copying and pasting that code has unexpected consequences. I don&#8217;t mean things breaking. I just mean that the styling, for example, something that the theme brings to bear might make things look peculiar and not quite how you intended.</p>



<p>[00:23:51] <strong>Kelly Choyce-Dwan:</strong> Yeah, I think that&#8217;s possible because it is, I mean it uses the Core blocks. So if your theme styles the core blocks minimally, maybe, you&#8217;ll probably be fine, but if your theme is doing anything really creative with some of the blocks, I suppose you could have some trouble where a quote that you copied from the pattern directory looks totally different on your site.</p>



<p>[00:24:12] <strong>Ana Segota:</strong> But if you are using a full site editing theme, I think you are good with.</p>



<p>[00:24:17] <strong>Nathan Wrigley:</strong> It should just work. Yeah. Do you know if there&#8217;s any intention to bring any of this kind of functionality into WordPress Core. And what I&#8217;m meaning by that is that I could hook up my let&#8217;s say wordpress.org account to my website. And then I could create patterns inside my website and then authorize them to be submitted to the pattern directory.</p>



<p>I feel like that might be quite a useful workflow at some point in the future, because then you&#8217;re not necessarily having to go out and go to a different website in order to create the patterns and publish them and so on. And equally, I wonder if in the future there are any plans to make it so that I can pull these patterns in, in the same way that we described that page builders like Elementor and so on, have their cloud templates and so on, and so forth.</p>



<p>[00:25:11] <strong>Kelly Choyce-Dwan:</strong> Yeah, I think the second is much more likely than the first. So if you were to create a pattern on your own website. Uh, you might be using any number of blocks that are not Core blocks. So I don&#8217;t know that creating a pattern on your website and pushing it up is on the roadmap at least, because there&#8217;s a lot more gotchas. We can&#8217;t control the media that you&#8217;re using. Like we&#8217;re able to use Open verse images on the pattern creator.</p>



<p>So there&#8217;s a lot more, a lot more like gotchas that way. But, having an ability to pull patterns from the pattern directory on wordpress.org into your own site. I do think that that is probably going to happen soon.</p>



<p>Already, you can call out, well already in WordPress 6.0, you&#8217;ll be able to register pattern slugs when you&#8217;re building a theme, and then it will pull down those patterns from the pattern directory. So you can pull patterns like that.</p>



<p>[00:26:06] <strong>Nathan Wrigley:</strong> Yeah. That&#8217;s, that&#8217;s interesting. So imagine that I&#8217;ve submitted one of my patterns. I&#8217;m very happy with it, but a year or two passes and I now for goodness knows what reason, I now don&#8217;t wish that pattern to be part of the directory. I&#8217;m wondering if either of you have any knowledge about whether things can be removed or once I&#8217;ve submitted it, is it up there for life? And I have essentially given it over to the community in perpetuity.</p>



<p>[00:26:36] <strong>Kelly Choyce-Dwan:</strong> You can revert your pattern to draft, if you want to take it down. You can also trash it. We&#8217;re not tied to always supporting things the way that the theme and plugin directories are because there isn&#8217;t really as much of a tie to your content and this thing on wordpress.org, because once you copy a pattern down, you have it, you don&#8217;t need to sync back up with the parent. So we don&#8217;t need to, we don&#8217;t have the same issues of keeping something around.</p>



<p>[00:27:00] <strong>Nathan Wrigley:</strong> Yeah, so you can curate that yourself. You can just, if you like return it to a draft status. So there&#8217;s a permanent connection between the wordpress.org repository that I can access with my user login and password, and the pattern being published. In other words, when I clicked submit, it&#8217;s not just taken from my submission and put into some other SaaS, if you like.</p>



<p>So my expectation was that when I submitted it, much in the same way that I was submitting a form on a website, that form can then live somewhere else. You know, the form submission can come to me via email. I can&#8217;t rescind that form being sent. But in the directory the submit button and the draft status button is directly connected to whether it&#8217;s on the pattern directory.</p>



<p>So if I click draft again, it will immediately, without any human supervision, it will suck it out of the directory and mean that it&#8217;s no longer there.</p>



<p>[00:28:03] <strong>Kelly Choyce-Dwan:</strong> Yeah, that that&#8217;s correct.</p>



<p>[00:28:05] <strong>Nathan Wrigley:</strong> Yeah, I really didn&#8217;t understand that. I just assumed that I was submitting it rather like a form. Somebody would inspect it, check it into another platform. So that&#8217;s kind of good to know.</p>



<p>[00:28:15] <strong>Kelly Choyce-Dwan:</strong> Yeah. It also means that you can edit. So if you make your pattern and then you decide that you actually, you&#8217;ve submitted it, it&#8217;s been a week though. And you don&#8217;t like the color of the button. You can make that change. It&#8217;ll submit it back to pending, and it has to go through that review again. But, once it&#8217;s published, your pattern will have the new change now.</p>



<p>[00:28:34] <strong>Nathan Wrigley:</strong> Okay. So we have to go through the process. Do you have any insight into how popular patterns have become over time? I mean, I still feel that the editing experience for proprietary page builders is something that people are keen for Gutenberg to have. You know, in other words, what you see is literally what you get.</p>



<p>There&#8217;s no ifs or buts, it&#8217;s just exactly the same on the backend as it is on the front end. And I feel that a lot of people are not moving over to Gutenberg because that experience is not there yet. So, this one may be for Kelly, it may be for Ana. Ana, you might like to draw on, you know, your experience or maybe your friends and colleagues. Is it as usable yet? Are patterns as useful to you as your page builder that you may have used in the past yet? Or if we still got a way to go, what are your, what are your instincts on that?</p>



<p>[00:29:25] <strong>Ana Segota:</strong> From my point of view, I think the block patterns are now really well made and they can be really useful. And I think they are mostly easier to use them. So for the user&#8217;s point of view, but they come more to the problem where we are starting to use templates, for example. Full site editing and templates. Block patterns are I think easiest part from the whole full site editing,.</p>



<p>From my experience, mostly they like block patterns but, I think we are still in early stage because there is not a lot of themes that are full site editing themes. And sometimes we also have older themes that we are updating with block patterns, but it&#8217;s like a mix of old way and new way. So I think when we start doing more full site editing themes, it will get easier and user will get to know znd to accept it more.</p>



<p>But I think block patterns are really useful from the user side, but templates are a bit tricky now, I must say, a bit confusing because we have a two editors now, like site editor and normal editor that they know from past. And they&#8217;re asking why I see now here block pattern, but in the old editor I need to click on the edit template to edit the template. It&#8217;s a bit tricky and confusing at the moment I must confess.</p>



<p>[00:31:00] <strong>Nathan Wrigley:</strong> We&#8217;re on the cusp of WordPress 6.0 being released, and as each different, a new release comes around, there is more being added and the complexity sometimes goes up and hopefully at some point the complexity will go down again and be more straightforward to use.</p>



<p>I guess that one of the biggest wins of using patterns and the pattern directory, which you would submit things to with the creator, is that all of this is just free. It&#8217;s completely freely available. You can use it in any which way you&#8217;d like, there&#8217;s no constraints over how you might use it. And if we rewind the clock about, oh, I don&#8217;t know, let&#8217;s go for about 12 or 13 years.</p>



<p>I imagine that the plug-in directory felt like a similar thing, you know, you would submit your plugin and within a few hours, somebody would say yes. That&#8217;s great, thank you very much. We now know that WordPress has 50,000 plus plugins. The directory whilst being very useful is quite hard, it&#8217;s very difficult to track things down. We&#8217;ve got certain things being recommended because they&#8217;re popular and it may be hard for people to have their bits and pieces discovered.</p>



<p>I&#8217;m just wondering, Kelly I&#8217;ll fire this one at you. I&#8217;m just wondering if in the future there are plans to make it so that as you submit patterns, there&#8217;s maybe more options around curating it, more taxonomy, terms, greater ways of being able to search and discover things. Because at the moment, it&#8217;s easy.</p>



<p>There&#8217;s a handful of patterns, well, that&#8217;s not quite true, but you get point. There aren&#8217;t 50,000 of them. But in the future, when this takes off, I could see there being literally hundreds of thousands of patterns. And at that point it&#8217;s going to be extremely difficult to separate the ones that you would like from the ones which are just there in front of you, but you don&#8217;t necessarily feel able to use. So really I&#8217;m just wondering how that may be curated in the future. Any roadmap plans for that?</p>



<p>[00:33:00] <strong>Kelly Choyce-Dwan:</strong> Yeah. you&#8217;re right there are, what did you say, 50,000 plugins?</p>



<p>[00:33:03] <strong>Nathan Wrigley:</strong> Yeah,</p>



<p>[00:33:04] <strong>Kelly Choyce-Dwan:</strong> Yeah, there&#8217;s 400 patterns.</p>



<p>[00:33:06] <strong>Nathan Wrigley:</strong> Yeah, yeah.</p>



<p>[00:33:07] <strong>Kelly Choyce-Dwan:</strong> So a little different. I don&#8217;t know that there&#8217;s any concrete roadmap for what the future of this directory might look like. There are some discussions about whether there should be different categories, like buttons, columns, taxonomy. There&#8217;s questions about how we should handle patterns that are more for site building versus just content patterns. So I do think that this is all very much still like to be decided, and really if anyone has opinions, I&#8217;m sure we&#8217;d love to hear them.</p>



<p>[00:33:39] <strong>Nathan Wrigley:</strong> Yeah, we&#8217;ll get onto that actually now because that feels like a good point. So obviously this is being built out in the open. The pair of you have obviously taken a great interest in it, but it may be that people listening to this, this is new to them. And they think that they would like to play with this a little bit, become involved with the team.</p>



<p>So maybe again, I&#8217;ll direct this one at Kelly first off. Are there any ways, better ways where people can get involved in the project of the directory or the creator? Where are the best places to go and hang out?</p>



<p>[00:34:12] <strong>Kelly Choyce-Dwan:</strong> If you want to have feedback about the future of the pattern directory or if you just want to report that something&#8217;s not working. The project is on GitHub. It&#8217;s at github.com/wordpress/patterndirectory.</p>



<p>[00:34:27] <strong>Nathan Wrigley:</strong> So that&#8217;s the best place to go if you wish to find out about becoming involved. Ana, just wondering about your experiences of being involved with this. Have you got any, any insights? Is there a thing that you found the most useful? A, I don&#8217;t know, a Slack channel or a website where people are helping each other out. A group of some kind, maybe a community online somewhere where this is all happening?</p>



<p>[00:34:50] <strong>Ana Segota:</strong> I was in contact per Slack, with Anne McCartney also and, mostly Slack and Twitter, but yeah, mostly Slack or Github, yeah.</p>



<p>[00:35:01] <strong>Nathan Wrigley:</strong> Now, I know that neither of you will be able to answer this question directly, but the theme repository and the plugin repository, they feel like there&#8217;s no way that they are going away. They&#8217;re going to be here for the long-term. You know, I can imagine decades from now, they&#8217;ll still be in existence. Do you both have confidence that this journey that we&#8217;ve taken on where blocks and patterns are becoming the new, the new way of creating quick and easy websites. Do you feel confident that this is the way it&#8217;s going to be done? You know, that we ought to sail our ship in this direction?</p>



<p>Your long-term thoughts really on whether or not this is the way it&#8217;s going to be done in the future.</p>



<p>[00:35:40] <strong>Ana Segota:</strong> I hope so. I really hope so. I think this way is, better way of making, for example, I am in theme business, so, it&#8217;s easier to create themes. Especially to offer easier way of using themes to users. So finally theme can be a design for me, and that&#8217;s a really big step in the right direction. So I really hope it will stay. And also be better with the time and more easier to use.</p>



<p>[00:36:12] <strong>Nathan Wrigley:</strong> Thank you. And Kelly.</p>



<p>[00:36:14] <strong>Kelly Choyce-Dwan:</strong> Yeah, I do think that this is the way forward. I think that using blocks and making patterns is really only going to become more, more standard. Easier to use. And so I think that this is going to be the way to make websites</p>



<p>[00:36:28] <strong>Nathan Wrigley:</strong> Yeah. Just one last quick thought. I mentioned something similar earlier and Ana talked about it, I&#8217;m going to direct this one at you, Kelly, if that&#8217;s all right. I don&#8217;t know what your experience is with other website building tools. And we mentioned page builders, such as Elementor and, I just wondered what your thoughts are on where the user interface is and the user experience is at the moment.</p>



<p>Maybe you&#8217;ve got some insight into that. Maybe you don&#8217;t, but I just wondered whether you thought that it was yet at a point of maturity. And that kind of ties into the question I&#8217;ve just asked about whether it would be widely adopted, because it feels like there&#8217;s a big holdout of people the moment who simply cannot make the move because the experience as yet doesn&#8217;t have that, it&#8217;s exactly the same on the front end, as it is on the backend. And Ana, I think you just said, Yeah in the background. You can identify. You&#8217;ve committed, you&#8217;ve jumped over and you&#8217;ve made that journey and put the investment of time into&#8230;</p>



<p>[00:37:24] <strong>Ana Segota:</strong> Yeah, but it takes a lot of challenges, yeah. Because I get the input from the user side and I also used Elementor before to see how it works. And I must say it&#8217;s still a long way. But, what is most confusing now to the users, what I said before, also, those two editors and two different phase. We now have again templates that you can edit.</p>



<p>And they&#8217;re a bit confused. Like, okay, I go on out to edit the template and I saved it and now it&#8217;s applied to all my pages and now you need to explain it that they need to refresh it and pull it back. And it&#8217;s a bit confusing. So we don&#8217;t have one editor where you can do all the things. For example, you come to one editor and click, for example, to choose a layout and this layout is there and you can edit it and that&#8217;s it. Yeah, it&#8217;s a bit struggle for now.</p>



<p>[00:38:25] <strong>Nathan Wrigley:</strong> I do wonder if that struggle, and I&#8217;m going to see what Kelly makes on this, I do wonder if that&#8217;s going to be for a little while into the future, if that&#8217;s going to be a limitation in terms of adoption, is the fact that there are difficulties. There&#8217;s a lot of learning which needs to take place to wean you off those tools and, whilst the WordPress Core way of doing blocks and patterns and so on is free, widely available, done in the open, open source and all of that kind of stuff. I wonder if the adoption is going to be stifled because of the constraints that Ana just mentioned. What do you think about that?</p>



<p>[00:39:04] <strong>Ana Segota:</strong> I think it depends also on us, on themers a lot. How we will implement this and make it easier for the users. And we also need to educate now the users, how they can use it and make it as easier as possible. And sometimes there&#8217;s not that easy because you need to follow updates and to do the updates all the time and to educate people about it.</p>



<p>But I think it&#8217;s a good step in the right direction. And I think with the time and with the education people will adopted it yeah. Just by creating a pages using just block pattern it&#8217;s a really a big step. And it&#8217;s a great thing. You can really create most everything with block patterns without using templates for example.</p>



<p>[00:39:54] <strong>Nathan Wrigley:</strong> Yeah, I think people just need time, the inspiration to get into it&#8230;</p>



<p>[00:39:59] <strong>Ana Segota:</strong> It&#8217;s a new, it&#8217;s a new thing and you always need time to learn something new.</p>



<p>[00:40:03] <strong>Nathan Wrigley:</strong> That&#8217;s right. We actually interviewed Courtney Robertson from the Learn initiative last week. And there&#8217;s an awful lot of content. And I think that&#8217;s maybe a piece that was missing in the past, the ability to go and find video tutorials, which answer the exact question that you&#8217;re looking for.</p>



<p>Kelly, can I put that one to you? Is it basically the same question? You said that you hadn&#8217;t got a great deal of experience with page builders and so on, but I&#8217;m just wondering if you had any intuitions around there, whether or not the UI and the UX is, is everything that you guys had hoped it would be, or do you feel that there&#8217;s still quite a lot of work going through WordPress six and seven and maybe even, eight.</p>



<p>[00:40:39] <strong>Kelly Choyce-Dwan:</strong> Yeah, I haven&#8217;t used page filters. I am definitely a pretty vanilla WordPress user. But I have been, you know, working with the site editor and I can see that it is a little confusing still. I do think that it needs to be iterated on, but I think that the future is going to be good.</p>



<p>I think the plans are there and it&#8217;s constantly getting better. So I&#8217;m very positive about it. Yeah.</p>



<p>[00:41:02] <strong>Nathan Wrigley:</strong> Thank you. Okay, just to wrap up, if people have listened to this podcast today and they would like to get in touch with you and make contact and use your expertise. What&#8217;s the best way of getting in touch with you? It could be a Twitter handle could be an email address, or it could be nothing. You might wish to share nothing at all, but I&#8217;ll start with Ana. What&#8217;s the best way to get in touch with you, Ana?</p>



<p>[00:41:24] <strong>Ana Segota:</strong> Twitter, or Slack or email. It&#8217;s all good. Maybe you can add a later?</p>



<p>[00:41:31] <strong>Nathan Wrigley:</strong> Yeah, I will definitely add your Twitter and Slack into the show notes. And same question to you, Kelly. What&#8217;s the best way to get in touch with you?</p>



<p>[00:41:40] <strong>Kelly Choyce-Dwan:</strong> You can find me on Twitter, Ryelle, R Y E L L E or on wordpress.org Slack. I can also chat there.</p>



<p>[00:41:49] <strong>Nathan Wrigley:</strong> Okay, Ana and Kelly, thank you so much for talking to me on the podcast today, and I appreciate you giving me an hour of your time. Thank you very much, indeed.</p>
</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:"Wed, 18 May 2022 14: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:14:"Nathan Wrigley";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:41;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:63:"Post Status: WooCommerce 6.5, 6.5.1, and WooCommerce Blocks 7.6";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=97704";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:72:"https://poststatus.com/woocommerce-6-5-6-5-1-and-woocommerce-blocks-7-6/";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:3050:"<p class="has-drop-cap">Well, the week started the release of  <a href="https://developer.woocommerce.com/2022/05/10/woocommerce-6-5-released/"><strong>WooCommerce 6.5</strong></a>  and ended with a  <a href="https://developer.woocommerce.com/2022/05/13/woocommerce-6-5-1-fix-release/"><strong>6.5.1 bug fix</strong></a> release. Between all of that, <strong><a href="https://developer.woocommerce.com/2022/05/10/woocommerce-blocks-7-6-0-release-notes/">WooCommerce Blocks 7.6</a> </strong>was also released.</p>



<p>Over on <strong>Do the Woo</strong>, we had <a href="https://dothewoo.io/the-woocommerce-roundtable-dives-into-wordpress-6-0/">a conversation about the upcoming release</a> of <strong>WordPress 6.0</strong>. The <strong>Woo Roundtable</strong>, consisting of <strong>Ronald Gijse</strong>l, <strong>Robbie Adair</strong>, <strong>Robert Jacobi</strong>, and <strong>Tammie Lister</strong> dove in to offer some insights about 6.0 and how WooCommerce plays into it. </p>



<p>Then <strong>Ronnie Burt</strong> from <strong>Sensei LMS</strong> and <strong>Automattic</strong> shared his extensive experience in the wider education space and his journey to move into the WordPress ecosystem, and LMS space:</p>



<blockquote class="wp-block-quote"><p>&#8220;And so when I think about democratizing education, I think about how do we help [provide] the best content [so the] best learning experiences bubble to the top and be found.&#8221;</p></blockquote>



<p>A little bird told me about <a href="https://poststatus.com/the-state-of-wordpress-market-share/">a drop in the WordPress market share</a>. Or actually, a Tweet from Joost de Valk. As a result I had to add <a href="https://dothewoo.io/woobits-dropping-my-02-about-wordpress-marketshare/">my small take to the influx of reaction we have seen</a>. It's short! </p>



<p>I think we just need to wait and see what shakes out. It's too early to say if this is a new trend.</p>



<blockquote class="wp-block-quote"><p>&#8220;&#8230;I am not losing any sleep over that number right now. To be fair, depending on your own stakes, you may feel differently. And trust me, there are some interesting insights that Joost shared in the post, as well as others that are either agreeing with or serving a rebuttal. And if you dare go down that rabbit hole, well, good luck.&#8221;</p></blockquote>



<p>Trust me, I didn’t spend much time on my response for several reasons:</p>



<blockquote class="wp-block-quote"><p>“I have had touchpoints in the technical space for over 3 decades. If I was someone that could predict what came next for any specific technology, or 100% understood a lot of the ups and downs, well, maybe I wouldn't be rich but I would sure have a lot to talk about.”</p></blockquote>



<div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content"><a href="https://dothewoo.io/woobits-dropping-my-02-about-wordpress-marketshare/">WooBits: Dropping My .02% About WordPress Marketshare</a></blockquote>
</div>



<h2 id="h-">&nbsp;</h2>";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, 17 May 2022 21:00:06 +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:8:"Bob Dunn";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:42;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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: How To Start Testing Your WordPress Code With the Pest PHP Testing Framework";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=134402";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:97:"https://wptavern.com/how-to-start-testing-your-wordpress-code-with-the-pest-php-testing-framework";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:9024:"<p>We can all agree that WordPress has come a long way since its beginning and that it grew into something a lot more than blogging software.</p>



<p>At its core, it’s still a content management system (CMS), but with over 59,000 plugins in the <a href="http://wordpress.org/">wordpress.org</a> directory, you can customize it to be much more.</p>



<p>The reason for its popularity is its low entry barrier for both content creators and developers. Sometimes this comes with a cost. It’s no secret that WordPress has a bad reputation when it comes to development. It has a lot of legacy baggage and die-hard rules that prevent any backward compatibility breaking change when it comes to PHP code (Gutenberg is another story I won’t get into).</p>



<p>That legacy PHP code is often used by the developers that are starting to enter the world of programming, and the issue with that is they can learn some bad programming patterns. That in turn means they will reuse the poorly written code, increasing the amount of bad code in the world.</p>



<p>This is where WordPress gets its bad reputation in the developer community.</p>



<h3><strong>Breaking the cycle</strong></h3>



<p>So how can we break this cycle of bad code? By teaching new developers how they should write good code. One example of teaching new developers (but also old ones that are still clinging to the ‘WordPress’ way of doing things) is by writing tutorials.</p>



<p>Another way is to encourage them to use tools that can help them write better code.</p>



<p>I’m currently involved in the work which aims to release the new version of the <a href="https://github.com/WordPress/WordPress-Coding-Standards/">WordPress Coding Standards</a>, a set of rules used for the <a href="https://github.com/squizlabs/PHP_CodeSniffer/">PHP_CodeSniffer</a> tool that will let you know if your code has some potential issues (security, best practices, code style).</p>



<p>Another tool that I’ve recently developed is a <a href="https://github.com/dingo-d/wp-pest-integration-test-setup">package</a> that will help developers set up WordPress integration tests that use the <a href="https://pestphp.com">Pest</a> testing framework.</p>



<h3><strong>Ok, so why do we need this new tool?</strong></h3>



<p>The main motivation behind creating this package is to encourage more people to write tests for their code, especially plugin developers.</p>



<p>A lot of developers in the WordPress community go with the mantra: I can see that it works because I’ve tried it out in my browser. That’s OK, but there are issues with that.</p>



<p>First, it’s time-consuming. Every time you make some change, you need to make sure it works, but also that you didn’t break anything.</p>



<p>Second, people make mistakes. We are not foolproof, and code may be misused in ways you never thought possible. You would be amazed at how creative people can be when writing code.</p>



<p>Automated tests are quick and can help you in testing various cases that will happen when you execute your code.</p>



<p>You test for the intended behavior (happy path), and in a quick way, you can add examples of how your code can be used in a way you didn’t intend it to be used (unhappy path).</p>



<p>It also safeguards your code from regressions. A code regression is when you unintentionally break one part of your code by adding new code.</p>



<h3><strong>The problem with tests set up so far</strong></h3>



<p>Testing in WordPress is not a new thing. And it’s not like you couldn’t set up tests for your code before. There are amazing libraries out there that will help you set everything up like <a href="https://wpbrowser.wptestkit.dev/">wp-browser</a>.</p>



<p>But the problem is that the setup procedure is often clunky.</p>



<p>You need to set up a separate database for tests, and you need to run certain scripts, then change files to make it all work.</p>



<p>Let’s face it, it’s not a straightforward thing to do, and developers are by nature lazy creatures (that’s why we write code to do things for us <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f604.png" alt="😄" class="wp-smiley" />).</p>



<p>The aim of the wp-pest integration test setup is to eliminate all that extra work.</p>



<h3><strong>How to set it up</strong></h3>



<p>In order to set it up, your project must use <a href="https://getcomposer.org/">Composer</a>. It’s a de-facto standard way of adding packages to your code.</p>



<p>In your terminal type</p>



<pre class="wp-block-code"><code>composer require dingo-d/wp-pest-integration-test-setup --dev</code></pre>



<p>After you’ve downloaded the package and its dependencies you can set up the theme tests by typing</p>



<pre class="wp-block-code"><code>vendor/bin/wp-pest setup theme</code></pre>



<p>Or, in the case you want to set up tests for your plugin, you can write</p>



<pre class="wp-block-code"><code>vendor/bin/wp-pest setup plugin --plugin-slug=your-plugin-slug</code></pre>



<p>Optionally, you can provide a <code>--wp-version</code> parameter, to specify which WordPress version you&#8217;d like to test your code on.</p>



<p>In the background, a WordPress instance will be downloaded, and an in-memory database will be set up, along with two examples of tests that you can run.</p>



<p>Then, running either</p>



<pre class="wp-block-code"><code>vendor/bin/pest --group=unit</code></pre>



<p>or</p>



<pre class="wp-block-code"><code>vendor/bin/pest --group=integration</code></pre>



<p>will run the tests.</p>



<p>The beauty of Pest is that its syntax is developer-friendly. It has <a href="https://pestphp.com/docs/installation">amazing documentation</a> and great syntax. Let’s look at a simple example. Say you are registering a custom post type called &#8216;Books&#8217;:</p>



<pre class="wp-block-code"><code>&lt;?php

/**
 * Plugin Name: Test plugin
 * Desctiption: Test plugin
 * Version: 1.0.0
 * License: MIT
 */

function test_plugin_register_books_cpt() {
    $args = array(
        'label'              =&gt; esc_html__( 'Books', 'test-plugin' ),
        'public'             =&gt; true,
        'publicly_queryable' =&gt; true,
        'show_ui'            =&gt; true,
        'show_in_menu'       =&gt; true,
        'query_var'          =&gt; true,
        'rewrite'            =&gt; array( 'slug' =&gt; 'book' ),
        'capability_type'    =&gt; 'post',
        'has_archive'        =&gt; true,
        'hierarchical'       =&gt; false,
        'menu_position'      =&gt; null,
        'supports'           =&gt; array( 'title', 'editor', 'author', 'thumbnail', 'excerpt', 'comments' ),
    );
 
    register_post_type( 'book', $args );
}
 
add_action( 'init', 'test_plugin_register_books_cpt' );
</code></pre>



<p>After running the setup command that adds an example, a test called <code>BooksCptTest.php</code> would look like this:</p>



<pre class="wp-block-code"><code>&lt;?php

namespace TestsIntegration;

beforeEach(function () {
	parent::setUp();
});

afterEach(function () {
	parent::tearDown();
});

test('Books custom post type is registered', function () {
	// We can use assertions from PHP_Unit.
	$this-&gt;assertNotFalse(has_action('init', 'test_plugin_register_books_cpt'));

	$registeredPostTypes = get_post_types();

	// Or we can use expectations API from Pest.
	expect($registeredPostTypes)
