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:53:"WPTavern: WordPress Rebrands FSE as “Site Editor”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=139286";s: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:58:"https://wptavern.com/wordpress-rebrands-fse-as-site-editor";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2480:"<p>While WordPress&#8217; site editing capabilities have been in development, the term full-site editing (FSE) has been widely used but sometimes poorly understood outside of contributor groups. Three months ago, WordPress&#8217; Executive Director Josepha Haden Chomphosy <a href="https://wptavern.com/wordpress-contributors-consider-renaming-full-site-editing">proposed</a> renaming FSE to something more user friendly. </p>



<p>After a lengthy <a href="https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/">discussion</a>, Haden Chomphosy has <a href="https://make.wordpress.org/updates/2022/11/04/site-editor-a-more-user-friendly-name/">announced</a> the decision to use &#8220;Site Editor&#8221; going forward:</p>



<blockquote class="wp-block-quote">
<p>Landing on Site Editor was the result of two key considerations. Firstly, Site Editor offers a clear and simple description to users with a range of technical skills. Secondly, there was substantial support for Site Editor, particularly from the Polyglot community, as the term that translates most effectively into hundreds of different languages.<em>&nbsp;</em><a href="https://videopress.com/v/BJyPZJNx?at=1420">As we heard at WordCamp US 2022</a>, better multilingual support is an important future direction for WordPress, so choosing easily translated terms is an important step.&nbsp;</p>



<p>Site Editor also keeps the spirit of its original FSE codename as the powerful, full collection of features it encompasses. As a bonus, it also doesn’t cost us anything from an SEO or marketing standpoint, since it’s a simplification of the existing term.</p>
</blockquote>



<p>Haden Chomphosy said the change is not necessarily a rebranding, but WordPress&#8217; official documentation, including Learn.WordPress videos, and many third-party resources are replete with references to FSE. The <a href="https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/">Full Site Editing Outreach Program</a> may also need to be renamed. Haden Chomphosy said WordPress users can still expect to see or hear the term FSE around &#8211; it&#8217;s not a situation where every instance needs to erased. </p>



<p>The recent decision to use the term &#8220;Site Editor&#8221; should be considered an official update to WordPress&#8217; shared lexicon, and Haden Chomphosy encouraged contributors to begin updating the documentation immediately to reflect the change.</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, 07 Nov 2022 22:32:18 +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:41:"Donncha: How to add your blog to Mastodon";s: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://odd.blog/?p=89504202";s: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:61:"https://odd.blog/2022/11/06/how-to-add-your-blog-to-mastodon/";s: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:6888:"<p><strong>Introduction</strong></p>



<p>Before we start, do you know what Mastodon is? It&#8217;s sort of like email, where you can send an email from gmail.com to a yahoo.com account, except it looks very like Twitter. This <a href="https://www.pcmag.com/how-to/how-to-get-started-on-mastodon-and-leave-twitter-behind">pcmag article</a> is a good introduction to it. Jeff Jarvis wrote a <a href="https://medium.com/whither-news/hope-for-a-post-musk-net-f156d0cdf431">good post</a> too, and Time Magazine <a href="https://time.com/6229230/mastodon-eugen-rochko-interview/">interviewed Eugen Rochko</a>, the founder of Mastodon that you should read.</p>



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

</div>



<p>This weekend, a probably sizeable chunk of <a rel="tag" class="u-tag u-category" href="https://odd.blog/tag/irishtwitter/">#IrishTwitter</a> migrated to Mastodon. We&#8217;re not the only ones. Twitter has been getting more hateful and acting as an echo chamber for lots of horrible people over the years. The sale of Twitter to Elon Musk, the firing of half the staff, his pronouncements of &#8220;free speech&#8221; all point towards the site being less regulated, less maintained and less moderated. You can&#8217;t deal with complaints if there&#8217;s nobody there listening to complaints of harassment or hate.</p>


<div class="wp-block-image is-style-default">
<img />(No we didn&#8217;t)</div>


<p></p>



<p>I don&#8217;t doubt that many of us will continue to visit and contribute to whatever Twitter becomes. Over the last few years, most of my interactions there have been publicising my blog posts. All I could see on there was angry tweets from different people, or people who were broadcasting their top ten ways of doing X, Y or Z. Hardly any actual conversation.</p>



<p>So, Mastodon. I woke up early on Saturday morning and discovered there was a <a rel="tag" class="u-tag u-category" href="https://odd.blog/tag/twittermigraton/">#TwitterMigraton</a> to Mastodon. I already had an account on mastodon.social but Irish Twitter was moving to mastodon.ie, and that&#8217;s where I went too, creating <a href="https://mastodon.ie/@donncha">@donncha@mastodon.ie</a>. </p>


<div class="wp-block-image is-style-default">
<a href="https://mastodon.ie/@Drharoldnews/109297557723889180"><img /></a></div>


<p></p>



<p>Judging from what I&#8217;ve read elsewhere, all mastodon instances are <a href="https://bitcoinhackers.org/@mastodonusercount">experiencing a HUGE surge in user registrations</a> as people look for an alternative to the <s>stinking</s> sinking ship that is Twitter.</p>


<div class="wp-block-image is-style-default">
<a href="https://bitcoinhackers.org/@mastodonusercount/109298398614165507"><img /></a></div>


<p></p>



<p>On Saturday, the admins of mastodon.ie ran into performance difficulties as they dealt <a href="https://mastodon.ie/@dregin/109296394011395383">with the influx of new users</a>. The site slowed down and people couldn&#8217;t upload images. Over 6,000 people are on that instance now.</p>


<div class="wp-block-image is-style-default">
<img />Remember the early days of Twitter?</div>


<p></p>



<p>The admins increased their hosting plan, eventually maxing out at the top tier. To pay for hosting they <a href="https://opencollective.com/mastodonie">asked for donations</a>. Right now they have raised over €4100!</p>



<p><strong>How do I add my WordPress blog to Mastodon?</strong></p>



<p>It&#8217;s mostly straight forward. Install these two plugins:</p>



<ol>
<li><a href="https://wordpress.org/plugins/activitypub/">ActivityPub</a></li>



<li><a href="https://wordpress.org/plugins/webfinger/">WebFinger</a></li>
</ol>



<p>The installation instructions are unfortunately not great. After you install both plugins, go to your Profile page (Users-&gt;Profile) and scroll right to the end. Down there you will find your profile identifier. It will look like @author@hostname.tld. For this blog that is <strong>@donncha@odd.blog</strong>, and I have my photoblog at <strong>@donncha@inphotos.org</strong>. Search for those on Mastodon and you will find my two blogs. Please feel free to follow!</p>


<div class="wp-block-image is-style-default">
<img /></div>


<p></p>



<p>When a post is made and shared on Mastodon, it allows others to reply. Those replies to the <a href="https://mastodon.social/@Gargron/108352419081380277">toot</a> on Mastodon will be sent to your WordPress blog as a <a href="https://inphotos.org/2022/11/06/on-stage-in-coughlans-bar/#comment-385708">comment</a>! That <a href="https://mastodon.ie/@donncha/109296714735893201">blew my mind</a> when I discovered that!</p>



<p><strong>Troubleshooting</strong></p>



<p>I discovered that running the plugins on a multi-site WordPress install will cause problems. Instead of activating it on the root install, you need to activate it on each one. I presume that&#8217;s maybe because the rewrite rules are added on plugin activation, but that&#8217;s just a guess.</p>



<p>If you have caching you might want to turn it off, or at the very least disable caching in /.well-known/ as that&#8217;s where Mastodon and other services will query your server for updated information.</p>



<p>It can take 10 to 15 minutes before a new post is seen. Be patient!</p>



<p><strong>Why not?</strong></p>



<p>There&#8217;s one reason you might not want to do this. Your blog will be on a Fediverse instance by itself. Your blog posts will only show if someone is following it, or <a href="https://inphotos.org/2022/11/06/on-stage-in-coughlans-bar/">you boost the toots on Mastodon</a>, or in the Federated feed. They won&#8217;t show in the Local Feed of your Mastodon instance. The best way around this is by careful use of relevant hashtags, but please don&#8217;t spam them, or you&#8217;ll be blocked.</p>


<div class="wp-block-image is-style-default">
<img /></div>


<p></p>



<p><strong>Alternatives</strong></p>



<p>You can hook your WordPress blog to your account too. I haven&#8217;t used them, but I saw two people use these plugins. Those posts will appear in the Local Feed of your Mastodon instance, which is a plus for discoverability.</p>



<ol>
<li><a href="https://wordpress.org/plugins/autopost-to-mastodon/">Mastodon Autopost</a></li>



<li><a href="https://wordpress.org/plugins/syndication-links/">Syndication Links</a></li>
</ol>



<p>You can also use IFTTT if your site can&#8217;t run plugins, and you have an RSS feed. Some details in <a href="https://hyperborea.org/journal/2017/12/mastodon-ifttt/">this blog post</a>. Thanks Sandy for that link!</p>



<p>I&#8217;m very excited about this. Is it too early to say that there&#8217;s enough momentum to sustain a <a rel="tag" class="u-tag u-category" href="https://odd.blog/tag/irishmastodon/">#IrishMastodon</a> community? I hope it succeeds.</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, 06 Nov 2022 19:57:18 +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:7:"Donncha";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:95:"Gutenberg Times: Layout Styles, Query Loop, Site Editor and WordPress 6.1- Weekend Edition #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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=22560";s: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:100:"https://gutenbergtimes.com/block-styles-query-loop-on-site-editor-wordpress-6-1-weekend-edition-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:20800:"<p>Howdy, </p>



<p>Today, you find additional information about contributors, known issues and new features of WordPress 6.1 below. Furthermore,  plenty of educational posts, videos and first-person explorations into Block Themes. The team around Learn.WordPress scheduled a heap of awesome events on Meetup and a new free course. </p>



<p>Find also new plugins, themes and so much more. </p>



<p>If you feel the uncertainty of time, space, and being, <a href="https://www.themarginalian.org/2020/04/03/virginia-woolf-to-the-lighthouse/">Maria Popova wrote about Virginia Woolf</a>&#8216;s To the Lighthouse and how Woolf finds beauty in the those dread moments. <a href="https://www.themarginalian.org/">The Marginalian</a> is always worth visiting. </p>



<p>Enjoy and have a wonderful weekend! </p>



<p>Yours, ?<br /><em>Birgit</em></p>






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



<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#0-word-press-release-information">Developing Gutenberg and WordPress</a></li><li><a href="https://gutenbergtimes.com/feed/#0-p">Plugins, Themes, and Tools for #nocode site builders and owners</a></li><li><a href="https://gutenbergtimes.com/feed/#2-word-press-6-0-1-and-6-1-scheduled">Theme Development for Full Site Editing and Blocks</a></li><li><a href="https://gutenbergtimes.com/feed/#3-building-themes-for-fse-and-word-press">Building Blocks and Tools for the Block editor. </a></li><li><a href="https://gutenbergtimes.com/feed/#4-up">Upcoming WordPress Events</a><ul><li><a href="https://gutenbergtimes.com/feed/#1-l">Learn WordPress Online Meetups</a></li></ul></li></ul></div>
</div></div>




<h2 id="0-word-press-release-information">Developing Gutenberg and WordPress</h2>



<p>Finally, <a href="https://wordpress.org/news/2022/11/misha/"><strong>WordPress &#8220;Misha&#8221; 6.1 is here</strong></a>! 800 contributors from 60 countries created one of the largest WordPress releases. </p>



<p>If you want to dive deeper into information about contributors, <strong><a href="https://twitter.com/AudrasJb">Jean-Baptist Audras</a></strong>, core team rep and data wizard at the Whodunit agency, published  <a href="https://jeanbaptisteaudras.com/en/2022/11/contribution-stats-for-wordpress-6-1-misha/"><strong>Contribution Stats for WordPress 6.1 « Misha »</strong></a>. </p>



<img />



<ul>
<li>Watch a&nbsp;<a href="https://www.youtube.com/watch?v=1w9oywSa6Hw">brief overview video</a>&nbsp;highlighting some major features debuting in WordPress 6.1. </li>



<li>The <a href="https://make.wordpress.org/core/2022/10/12/wordpress-6-1-field-guide/">Fieldguide</a> has been available for a couple of weeks. </li>



<li><strong>Steven Stern</strong>, team rep of the support team published a <strong><a href="https://wordpress.org/support/topic/read-this-first-wordpress-6-1/#post-15661769">list of known issues on the forum</a>. </strong></li>



<li>The core team is working on a quick turn-around on a minor release. <strong>Jeff Paul</strong> shared his notes for <a href="https://make.wordpress.org/core/2022/11/04/wordpress-6-1-1-planning/"><strong>WordPress 6.1.1 Planning</strong></a></li>
</ul>



<p><strong>Sarah Gooding</strong> reported on the release for the WP Tavern: <a href="https://wptavern.com/wordpress-6-1-introduces-new-default-theme-and-fluid-typography-expands-design-tools-and-template-options"><strong>WordPress 6.1 Introduces New Default Theme and Fluid Typography, Expands Design Tools and Template Options</strong></a></p>



<div class="wp-block-group has-light-background-background-color has-background is-layout-flow"><div class="wp-block-group__inner-container">
<p><strong>?️ </strong> New episode:  <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-75-gutenberg-14-4-upcoming-wordpress-6-1-release-whats-next-for-6-2/">Gutenberg Changelog #75 – Gutenberg 14.4, Upcoming WordPress 6.1 Release, What’s Next for 6.2</a> with special guest, Anne McCarthy, and host Birgit Pauli-Haack</p>
</div></div>



<p>And, <strong>Site Editor</strong> it is. <strong>Josepha Haden Chomphosy</strong> summarized the discussion from a few weeks ago in her clarifying post: <a href="https://make.wordpress.org/updates/2022/11/04/site-editor-a-more-user-friendly-name/"><strong>Site Editor: a More User-Friendly Name</strong></a></p>



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



<p>Last week, I got excited about the <a href="https://github.com/artemiomorales/gutenberg-interactive-fiction-engine/releases/tag/v0.1.0">Interactive Fiction Engine</a> and I also shared the call for <a href="https://gutenbergtimes.com/what-art-can-you-create-with-wordpress-6-1/">submission for the Museum for Block Art</a>. Guess what happened?</p>



<p><strong>Anne McCarthy</strong> created a beautiful and <strong><a href="https://block-museum.com/interact/">interactive tour of the Museum of Block Art</a></strong>. Enter the museum and discover the works exhibited on the website, McCarthy highlighted for you. </p>



<h2 id="0-p">Plugins, Themes, and Tools for #nocode site builders and owners</h2>



<p><strong>Justin Tadlock</strong> published another single-block plugin in the plugin repository called: <a href="https://wordpress.org/plugins/x3p0-progress/"><strong>X3P0 Progress</strong></a>. It is a block that allows users to create progress bars using a straightforward interface. You can select different units to set your progress on the bar, percentage or in currency (for instance for a donation goal). For the layout, it sports plenty of choices for colors to border settings and spacing options. </p>



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



<p><strong><a href="https://twitter.com/andersnoren">Anders Noren</a></strong> published his sixth block theme, called <a href="https://wordpress.org/themes/oaknut/">Oaknut</a>, built to help you  to create Linktree-esque profile pages. It includes 23 Style Variations, 14 fonts, 8 button styles and 5 different social link styles. On his website, Noren wrote that it &#8220;include less than 150 lines of CSS and no JavaScript at all.&#8221;. On the WordPress Theme directory you can test each of the Style variations, before you make a decision. The screenshot area changes when you select one of the style variations in the little slider below. </p>



<img /><a href="https://wordpress.org/themes/oaknut/">Screenshot of Oaknut Theme</a> with the Style variation &#8220;night shift&#8221; 



<p><strong>Sarah Gooding</strong> posted on WP Tavern: <a href="https://wptavern.com/anders-noren-releases-oaknut-a-new-profile-block-theme-with-23-style-variations"><strong>Anders Norén Releases Oaknut, a New Profile Block Theme with 23 Style Variations</strong></a></p>



<p>Over at Castos&#8217; YouTube Channel, <strong><a href="https://twitter.com/mattmedeiros">Matt Mederios</a></strong> gives a demo of the new theme, <a href="https://www.youtube.com/watch?v=imzyyGLI8wE"><strong>Linktree alternative for WordPress &#8211; Oaknut theme</strong></a>. Further, into the video, Mederios also shows site owners how to create a new template. </p>



<p>Anders Noren&#8217;s other block themes are: </p>



<ul>
<li><a href="https://wordpress.org/themes/beaumont/">Beaumont</a>,</li>



<li><a href="https://wordpress.org/themes/bjork/">Björk</a>,</li>



<li><a href="https://wordpress.org/themes/poe/">Poe</a>,</li>



<li><a href="https://wordpress.org/themes/davis-blocks/">Davis Blocks</a>, and</li>



<li><a href="https://wordpress.org/themes/tove/">Tove</a></li>
</ul>



<p>Noren also shares his code on <a href="https://github.com/sponsors/andersnoren">GitHub and you can sponsor him</a> for his consistently brilliant open-source work.</p>



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



<p><a href="https://twitter.com/joyofwp"><strong>Bud Kraus</strong></a>, Joy of WP conducted a webinar with the team of GoDaddyPro. The recording is now available on YouTube: <a href="https://www.youtube.com/watch?v=RryB7PT0c34"><strong>Don’t Let The WordPress Query Loop Block Throw You For A Loop!</strong></a> &#8220;Query Loop block unlocks the potential of what an Archive page can be without knowing any PHP!&#8221; </p>



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



<p>You can watch an <a href="https://wordpress.tv/2022/11/03/intro-to-the-site-editor-and-template-editor-2/"><strong>Intro to the Site Editor and Template&nbsp;Editor</strong></a>, created by Wes Theron, educator on Learn.WordPress, on WordPressTV. Learn more about using a block theme and how the Site Editor and Template Editor work.</p>



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



<h2 id="2-word-press-6-0-1-and-6-1-scheduled">Theme Development for Full Site Editing and Blocks</h2>



<p>In his post, <strong><a href="https://www.smashingmagazine.com/2022/10/wordpress-full-site-editing/">WordPress Full-Site Editing: A Deep Dive Into The New Feature</a></strong>,  <a href="https://twitter.com/nschaeferhoff"><strong>Nick Schäferhoff</strong></a> examines the tools of full-site editing provides for theme development, and provides a tutorial on how to use it to modify your site.</p>



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



<p><strong>Mike McAlister</strong> explains in his post how you can <a href="https://olliewp.com/spice-up-your-wordpress-content-with-block-styles/"><strong>spice up your WordPress content with Block Styles.</strong></a> &#8220;Block styles is one of those features that seems to have been lost in the rush to full-site editing. In this post, we’ll learn how to add style variations to your blocks.&#8221; he started his post. </p>



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



<p><strong>Justin Tadlock</strong> takes you on <a href="https://gutenbergtimes.com/a-walk-through-of-layout-classes-in-wordpress-6-1/"><strong>A Walk-Through of Layout Classes in WordPress 6.1</strong></a> The primary goals  for this post are to provide developers with an overall view of the system and to know which classes can be targeted via CSS.  The &#8220;TL;DR: just let WordPress handle the layout while you tinker with fun stuff like colors and fonts.&#8221; Tadlock <a href="https://twitter.com/justintadlock/status/1588620591762112513">tweeted.</a>  </p>



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



<p>In the video, <a href="https://wordpress.tv/2022/11/03/intro-to-the-site-editor-and-template-editor-2/"><strong>Using block template parts in classic themes</strong></a>, <strong>Jonathan Bossenger</strong> shows off a new feature in WordPress 6.1, the ability to register block template parts in classic themes and allows users to modify specific parts of the theme with blocks, without affecting the rest of the site layout or design.</p>




<div class="ngl-articles colored ngl-articles-30_70 ngl-articles-frontend">

	
	<div class="ngl-articles-wrap ngl-articles-webview">
	
						
			<div class="ngl-article-mobile">
				<table width="100%" border="0" cellpadding="0" cellspacing="0">
					<tr>
						<td valign="top">
							<div class="ngl-article-mob-wrap">
							<div class="ngl-article-featured"><a href="https://gutenbergtimes.com/block-based-template-parts-for-classic-themes/" target="_self" rel=""><img src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2022/09/block-based-template-parts.png?w=652&ssl=1" /></a></div><div class="ngl-article-title"><a href="https://gutenbergtimes.com/block-based-template-parts-for-classic-themes/" target="_self" rel=""><span>Block-Based Template Parts: A Happy Medium Between Classic and Block Themes</span></a></div><div class="ngl-article-excerpt">I was one of the early adopters of the block editor as a developer. Despite the flak that the Gutenberg plugin was catching before it was merged into core WordPress, …a post by Justin Tadlock) <a href="https://gutenbergtimes.com/block-based-template-parts-for-classic-themes/" class="ngl-article-read-more" target="_self">Read more.</a></div>							</div>
						</td>
					</tr>
				</table>
			</div>
			
			
			

		
						
			<div class="ngl-article-mobile">
				<table width="100%" border="0" cellpadding="0" cellspacing="0">
					<tr>
						<td valign="top">
							<div class="ngl-article-mob-wrap">
							<div class="ngl-article-featured"><a href="https://gutenbergtimes.com/building-a-block-based-header-template-in-a-classic-theme/" target="_self" rel=""><img src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2022/09/tt1-block-header-video.jpg?w=652&ssl=1" /></a></div><div class="ngl-article-title"><a href="https://gutenbergtimes.com/building-a-block-based-header-template-in-a-classic-theme/" target="_self" rel=""><span>Building a Block-Based  Header Template in a Classic Theme</span></a></div><div class="ngl-article-excerpt">WordPress 6.1 will allow classic theme authors to begin using block-based template parts. It is one of the most exciting features of the release and one that has long been&hellip; <a href="https://gutenbergtimes.com/building-a-block-based-header-template-in-a-classic-theme/" class="ngl-article-read-more" target="_self">Read more.</a></div>							</div>
						</td>
					</tr>
				</table>
			</div>
			
			
			

		
		
		</div>

</div>




<p>The first part of the  <a href="https://learn.wordpress.org/course/a-developers-guide-to-block-themes-part-1/"><strong>Developers Guide to Block Themes</strong></a> course is now available on Learn.WordPress. &#8220;If you’re used to developing WordPress themes using PHP, HTML, CSS, and JavaScript, but you don’t know where to start with block themes, this course is for you.&#8221; </p>




<p><strong>&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/" target="_blank" rel="noreferrer noopener">&#8220;Keeping up with Gutenberg &#8211; Index 2022&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly.  <a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/"><em>The index 2020 is here</em></a></p>




<p><strong>Brian Coords</strong> explored the intricacies of content width and layout options in his post <a href="https://www.briancoords.com/normal-width-websites-in-the-block-editor/"><strong>Normal width websites in the block editor</strong></a>. &#8220;The best advice I can give for FSE is to&nbsp;<em>start with the global styles</em>&nbsp;before you start messing with the template files. Get your defaults in a good place.&#8221; Coords wrote. Start reading to learn how he arrived at the conclusion. </p>



<h2 id="3-building-themes-for-fse-and-word-press">Building Blocks and Tools for the Block editor. </h2>



<p><strong><a href="https://twitter.com/tomfinley">Tom Finley</a></strong> curated a list of <a href="https://tomfinley.co/modern-wordpress-dev-coursework/"><strong>Modern WordPress Dev Coursework</strong></a>; websites with   educational material for WordPress developers who want to learn more about building blocks or block themes. Many people on Twitter who were inquiring about more information especially full site editing inspired Finely to collect the best resources. </p>



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




<p><strong><a href="https://gutenbergtimes.com/need-a-zip-from-master/">Need a plugin .zip from Gutenberg&#8217;s master branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>



<p><img alt="GitHub all releases" src="https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge" /></p>




<h2 id="4-up">Upcoming WordPress Events</h2>



<p><strong>WPCampus</strong> published a <a href="https://www.wpcampus.org/blog/2022/10/opening-nominations-for-wpcampus-board-of-directors/"><strong>call for nominations to their Board of Directors</strong></a>. </p>



<p>November 18, 2022<br /><strong><a href="https://www.wordfest.live/2022/november/">WordFest Live Returns</a></strong>&nbsp;– the 24-hour Festival of WordPress</p>



<p>February 17 – 19, 2023<br /><a href="https://asia.wordcamp.org/2023/"><strong>WordCamp Asia 2023</strong></a> </p>



<p class="has-light-background-background-color has-background has-normal-font-size"><a href="https://central.wordcamp.org/schedule/"><strong>Have a look at the schedule of upcoming WordCamps</strong></a> to find one near you. </p>



<a href="https://central.wordcamp.org/schedule/"><img /></a>Screenshot of the list of <a href="https://central.wordcamp.org/schedule/">WordCamp schedule</a> for the rest of 2022



<h3 id="1-l">Learn WordPress Online Meetups</h3>



<p>November 7, 2022 &#8211; 3 pm ET / 20:00 UTC <br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289466943/"><strong>Padding, Margin and Block Spacing</strong></a> with Wes Theron</p>



<p>November 10, 2022 &#8211; 3 pm ET / 20:00 UTC <br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289518084/"><strong>Builder Basics: How to Curate the Editing Experience</strong></a> with Nick Diego</p>



<p>November 14, 2022 &#8211; 3 pm ET / 20:00 UTC<br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289535966/"><strong>Using the Navigation Block</strong></a> with Wes Theron</p>



<p>November 16, 2022 &#8211; 7 pm ET / 24:00 UTC <br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289512806/"><strong>WordPress 6.1 Exploration</strong></a> with Destiny Kanno</p>



<p>November 17, 2022 &#8211; 3 pm ET / 20:00 UTC <br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289520419/"><strong>Builder Basics: Exploring Block Layout, Alignment, and Dimensions</strong></a> with Nick Diego</p>



<p>November 18, 2022 &#8211; 2 pm ET / 19:00 UTC <br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289507999/"><strong>The Creative Side of Blocks, Vol. 3</strong></a> with Rich Tabor</p>



<p>November 21, 2022 &#8211; 3 pm ET / 20:00 UTC<br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289536031/"><strong>Intro to the Site Editor &amp; Template Editor</strong></a> with Wes Theron</p>



<p>December 1, 2022 &#8211; 3 pm ET / 20:00 UTC <br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289520991/"><strong>Builder Basics: Building with Columns, Groups, Rows and Stacks</strong></a> with Nick Diego </p>



<p>December 8, 2022 &#8211; 3 pm ET / 20:00 UTC <br /><strong><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289521234/">Builder Basics: Demystifying theme.json and Global Styles</a></strong> with Nick Diego</p>



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




<p><strong>Featured Image: </strong><a href="https://wordpress.org/photos/photo/325632c838/">Rooftops panorama of central Madrid (Spain)</a> by JM Puertas on WordPress.org/photos</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 type="submit" 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, 05 Nov 2022 14:30:28 +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: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:77:"WPTavern: WordPress 6.1 Retires Default Site Tagline in Favor of Empty String";s: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=139247";s: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/wordpress-6-1-retires-default-site-tagline-in-favor-of-empty-string";s: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:3280:"<p>WordPress&#8217; default site tagline, &#8220;Just another WordPress site,&#8221; is now a thing of the past, though not yet fully retired to the realm of nostalgia. The recent 6.1 release resolved a <a href="https://core.trac.wordpress.org/ticket/6479">ticket</a> that lead developer Mark Jaquith opened 15 years ago to encourage people to change their taglines. The tagline has now been changed to an empty string for new installations. This was added as a note of interest in the 6.1 release post, which was the first place many learned about it:</p>



<p><em>&#8220;The site tagline is empty by default in new sites but can be modified in General Settings.&#8221;</em></p>



<p>For those who are sentimental about the tagline, rest assured that it has been preserved as placeholder text in the admin. </p>



<p>&#8220;I do think the easier solution is to replace the &#8216;Just another WordPress site&#8217; value with a placeholder,&#8221; WordPress Core Committer Jb Audras said in the discussion on the ticket. &#8220;By doing this, we keep this sentence which is in my opinion part of the WordPress history —by doing so, it would at least appear on the Settings screen, so we keep this signature sentence somewhere on the admin— but the value is empty by default for new installs.&#8221;</p>



<p>This is the solution he committed, which landed in 6.1.  The commit message identifies the reasoning behind the change: </p>



<blockquote class="wp-block-quote">
<p>Administration: Change default site tagline to an empty string.</p>



<p>This changeset replaces the default &#8220;Just another WordPress site&#8221; tagline with an empty string for new installations. The reasoning is:</p>



<ol>
<li>Not all themes display the tagline;</li>



<li>Not everyone changes the default tagline;</li>



<li>When people don&#8217;t see the tagline in their theme, they may not realize it is still visible in some places, like feeds.</li>
</ol>



<p>The string &#8220;Just another WordPress site&#8221; and the related multisite string: &#8220;Just another {NETWORK} site&#8221; are now only used as a placeholder for the tagline admin option.</p>
</blockquote>



<p>The advent of block themes was also another factor, since the Customizer was where users often managed their taglines in the past. Contributors concluded that the increasing use of block themes might result in more people who have the default tagline on their sites without even knowing about it. The conclusion was it is better to make it an empty string than to add a bunch of admin prompts to update it.</p>



<p>This is a welcome change to how taglines are presented, and it was past time to update it. Although most WordPress professionals had become accustomed to it, more casual users often searched for how to get rid of it, sometimes without knowing it could be customized. The message also wasn&#8217;t doing WordPress any favors, unless it was originally written to imply WordPress&#8217; ubiquity on the web &#8211; a claim that was aspirational at the time it was first committed to core. In that case, it has long since served its purpose. An empty string ensures that the only taglines showing up for new installations are ones that admins intentionally wrote for their sites.</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, 05 Nov 2022 01:13: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: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: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:91:"WPTavern: Anders Norén Releases Oaknut, a New Profile Block Theme with 23 Style Variations";s: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=139197";s: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:100:"https://wptavern.com/anders-noren-releases-oaknut-a-new-profile-block-theme-with-23-style-variations";s: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:3134:"<p><a href="https://andersnoren.se/">Anders Norén</a>, a Swedish designer and prolific WordPress theme developer, has released <a href="https://wordpress.org/themes/oaknut/">Oaknut</a>, a new profile block theme reminiscent of services like <a href="https://linktr.ee/">Linktree</a> and <a href="https://carrd.co/">Carrd</a>. The theme is for users who want a simple profile landing page with relevant social and work links, but it could also be easily expanded to capture email addresses for a newsletter, add a blog, or serve as a placeholder for a coming soon website.</p>



<img />



<p>Oaknut includes just three templates: Home (displays posts on the homepage, or on the Posts page if a static homepage is set), Index (displays posts), and 404 (displays when no content is found). Users who want to expand the theme beyond the basic use case can add more templates through the Site Editor or even create their own custom templates.</p>



<p>The <a href="https://wp-themes.com/oaknut/">demo</a> looks just like the screenshot, and there are no other pages to view. After installing and activating the theme, clicking on Customize will go to the Site Editor where everything you see in the demo is already in place, ready to be replaced with your own profile data and links.</p>



<p>If the bright mustard color is too much for your taste, you&#8217;re in luck with Oaknut, because it packages a whopping 23 different style variations. Norén has also included 14 font families, eight button styles, and five styles for social links.</p>



<img />



<p>As one of the pioneers in the block themes category Norén ensured Oaknut was ready to showcase new features released in <a href="https://wptavern.com/wordpress-6-1-introduces-new-default-theme-and-fluid-typography-expands-design-tools-and-template-options">WordPress 6.1</a>. The theme supports fluid typography, spacing sizes, root padding aware elements, pseudo selector styles in theme.json, and theme.json styling for elements like buttons, captions, and headings.</p>



<p>&#8220;This enables Oaknut to have a really small CSS file,&#8221; Norén said. &#8220;It comes in at less than 150 lines, and 120 of those lines are for the custom block styles included in the theme. Combine that with locally hosted variable fonts and the complete lack of JavaScript in the theme, and you end up with some pretty speedy profile pages.&#8221;</p>



<p>Norén shared a screenshot of a website using the theme with a Lighthouse performance score of 100.</p>



<img />



<p>Oaknut is a good choice for WordPress users who want a simple, attractive theme that shows how people can connect with them. It is also great for those who are just starting out with a web presence or domains that need a nicely- designed placeholder. </p>



<p>The theme is <a href="https://wordpress.org/themes/oaknut/">available on WordPress.org</a> to download for free. Norén has also created a <a href="https://github.com/sponsors/andersnoren">GitHub Sponsors account</a> for anyone who wants to support the continued development of his 26 free WordPress themes and future theme releases.</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, 04 Nov 2022 20:42:27 +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: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:93:"Post Status: What is the WordPress community capable of? A lot of good. And a few bad apples.";s: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:32:"https://poststatus.com/?p=142906";s: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:101:"https://poststatus.com/what-is-the-wordpress-community-capable-of-a-lot-of-good-and-a-few-bad-apples/";s: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:2834:"<p><strong>The Good:</strong> This week a team of people from around the world released <a href="https://wordpress.org/news/2022/11/misha/">WordPress 6.1, Misha</a>. The number of people who contributed to this release is HUGE. Folks, WordPress takes <em>more</em> than a village, it takes a small city to keep the momentum moving forward, keep the technology on the cutting edge, and keep the community itself vibrant. There are literally thousands of people who bring positivity to and work hard for the WordPress community. <em>Kudos to each and every one of them!</em></p>



<p><strong>The Bad Apples: </strong>Usually we try to not talk about the negative things. (Well, most of us do, you all know I don’t mind shining a light where it can help, for sure.) And <strong>Mika Epstein</strong> is no different than most of us. If someone is a personal problem to one of us, it’s usually kept out of the public eye. We soldier on and do our best to ignore minor pests. But sometimes those pests aren’t just pests. Sometimes they are intent on destruction, and they will use any means necessary to hurt others. My hat is off to Mika for being strong through the entirety of what she has endured over years of stalking, attack, malignment, and worse — all as part of her commitment to the <strong>Plugins Team</strong>. <em>No one should ever have to go through what she has.</em> It’s beyond brave of her to <a href="https://halfelf.org/harassment-rst/">share with the community</a>, and I, for one, am grateful that she has. </p>



<h2 id="h-bf-cm">BF/CM</h2>



<ul>
<li>Black Friday/Cyber Monday is coming quickly! <a href="https://poststatus.com/submit-black-friday-cyber-monday-deals/">Submit your deals here</a>. </li>



<li><a href="https://poststatus.com/2022-black-friday-cyber-monday-wordpress-deals/">Find this year’s deals here</a>. (More being added weekly!)</li>
</ul>



<h2>In the Spotlight</h2>



<ul>
<li>This week's <strong>Business Spotlight</strong> this week: <a href="https://poststatus.com/business-spotlight-xwp/">XWP</a> →</li>



<li>Our Member Spotlight features <a href="https://poststatus.com/member-spotlight-igor-ligay/">Igor Ligay</a> →</li>
</ul>



<h2>Upcoming Events</h2>



<ul>
<li>Post Status <a href="https://poststatus.com/huddles/">Member Huddles </a>every week for Europe and the Americas.</li>



<li><a href="https://www.wordfest.live/2022/november/">WordFest</a> is happening on <strong>December 16</strong>. (New Date!)</li>



<li>Calls for Speakers and Sponsors are open at the <a href="https://www.wpwealthbuilder.com/">WP Wealthbuilder Summit</a>.</li>



<li>WordCamps are back! <a href="https://central.wordcamp.org/schedule/">Check the schedule</a>.</li>
</ul>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 04 Nov 2022 19:50:18 +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: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:66:"Gutenberg Times: A Walk-Through of Layout Classes in WordPress 6.1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=22646";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"https://gutenbergtimes.com/a-walk-through-of-layout-classes-in-wordpress-6-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:15080:"<p>WordPress 6.1 introduced several necessary changes to its layout framework. Namely, core has now centralized its layout definitions, created semantic class names, and reduced code duplication on container blocks.</p>



<p>Originally, this post was intended to be a quick look at the changes to the system for theme authors. However, given the heftiness of the topic, it has evolved into a full overview of the layout framework.</p>



<p>The primary goals for this walk-through are to provide developers with an overall view of the system and to know which classes are able to be targeted via CSS. </p>



<div class="wp-block-group has-light-background-background-color has-background is-layout-constrained"><div class="wp-block-group__inner-container">
<p class="has-large-font-size"><strong>Table of contents</strong></p>



<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#0-an-overview-of-layout-related-classes">An Overview of Layout-Related Classes</a></li><li><a href="https://gutenbergtimes.com/feed/#1-block-gaps-and-vertical-rhythm">Block Gaps and Vertical Rhythm</a></li><li><a href="https://gutenbergtimes.com/feed/#2-constrained-and-flow-layouts">Constrained and Flow Layouts</a></li><li><a href="https://gutenbergtimes.com/feed/#3-flex-layouts">Flex Layouts</a></li><li><a href="https://gutenbergtimes.com/feed/#4-content-justification">Content Justification</a></li><li><a href="https://gutenbergtimes.com/feed/#5-avoid-code-wp-container-code-classes">Avoid .wp-container-* Classes</a></li><li><a href="https://gutenbergtimes.com/feed/#6-future-layout-types">Future Layout Types</a></li><li><a href="https://gutenbergtimes.com/feed/#7-resources-to-learn-more">Resources to learn more</a></li></ul></div>
</div></div>



<h2 id="0-an-overview-of-layout-related-classes">An Overview of Layout-Related Classes</h2>



<p>Layout-related classes are given to container-type blocks in WordPress. They define how nested blocks are aligned within their parent.</p>



<p>Most extenders will immediately associate layout classes with the Group block and its Row and Stack variations. However, WordPress uses the classes for other blocks, such as Social Icons, Navigation, and Buttons. Layouts may also be used with third-party blocks, even though support is currently marked as an experimental feature.</p>



<p>The following list is a bird&#8217;s-eye view of the currently-available classes in WordPress 6.1. Most of the class names should describe their roles, but don&#8217;t worry if you don&#8217;t understand all of them yet. In this walk-through, you will learn what each does.</p>



<ul>
<li><strong>Layout Classes:</strong>
<ul>
<li><code>is-layout-constrained</code></li>



<li><code>is-layout-flow</code></li>



<li><code>is-layout-flex</code></li>
</ul>
</li>



<li><strong>Flex Orientation (Direction) Classes:</strong>
<ul>
<li><code>.is-vertical</code></li>



<li><code>.is-horizontal</code></li>
</ul>
</li>



<li><strong>Content Justification Classes:</strong>
<ul>
<li><code>.is-content-justification-left</code></li>



<li><code>.is-content-justification-center</code></li>



<li><code>.is-content-justification-right</code></li>



<li><code>.is-content-justification-space-between</code></li>
</ul>
</li>



<li><strong>Flex Wrap Classes:</strong>
<ul>
<li><code>.is-nowrap</code></li>
</ul>
</li>



<li><strong>Container Classes:</strong>
<ul>
<li><code>.wp-container-{id}</code></li>
</ul>
</li>
</ul>



<h2 id="1-block-gaps-and-vertical-rhythm">Block Gaps and Vertical Rhythm</h2>



<p>Before diving into each layout type, it&#8217;s important to understand how vertical spacing between blocks works. Much of the system relies on this feature.</p>



<p>As any good designer will tell you, vertical rhythm is a crucial aspect of any design. And vertical spacing between elements, while only one aspect of the rhythm, plays a vital part in getting the design right.</p>



<p>In WordPress, this is the <code>blockGap</code> property. Do not let the name confuse you. While it maps to the CSS <code>gap</code> property in some layouts, it is also used to set <code>margin-block-start</code> in others.</p>



<p>Any theme can set the default via <code>styles.spacing.blockGap</code> in their <code>theme.json</code>, as shown in the following code snippet:</p>


<pre class="wp-block-code"><div><code class="hljs language-json">{
    <span class="hljs-attr">"$schema"</span>: <span class="hljs-string">"https://schemas.wp.org/trunk/theme.json"</span>,
    <span class="hljs-attr">"version"</span>: <span class="hljs-number">2</span>,
    <span class="hljs-attr">"styles"</span>: {
        <span class="hljs-attr">"spacing"</span>: {
            <span class="hljs-attr">"blockGap"</span>: <span class="hljs-string">"2rem"</span>
        }
    }
}</code></div><small class="shcb-language" id="shcb-language-4"><span class="shcb-language__label">Code language:</span> <span class="shcb-language__name">JSON / JSON with Comments</span> <span class="shcb-language__paren">(</span><span class="shcb-language__slug">json</span><span class="shcb-language__paren">)</span></small></pre>


<p>Themes can also target the <code>blockGap</code> property for blocks that support it. The following code example shows how to set the default spacing while customizing it for the Group block:</p>


<pre class="wp-block-code"><div><code class="hljs language-json">{
    <span class="hljs-attr">"$schema"</span>: <span class="hljs-string">"https://schemas.wp.org/trunk/theme.json"</span>,
    <span class="hljs-attr">"version"</span>: <span class="hljs-number">2</span>,
    <span class="hljs-attr">"styles"</span>: {
        <span class="hljs-attr">"spacing"</span>: {
            <span class="hljs-attr">"blockGap"</span>: <span class="hljs-string">"2rem"</span>
        },
        <span class="hljs-attr">"blocks"</span>: {
            <span class="hljs-attr">"core/group"</span>: {
                <span class="hljs-attr">"spacing"</span>: {
                    <span class="hljs-attr">"blockGap"</span>: <span class="hljs-string">"1rem"</span>
                }
            }
        }
    }
}</code></div><small class="shcb-language" id="shcb-language-5"><span class="shcb-language__label">Code language:</span> <span class="shcb-language__name">JSON / JSON with Comments</span> <span class="shcb-language__paren">(</span><span class="shcb-language__slug">json</span><span class="shcb-language__paren">)</span></small></pre>


<p>There may be edge cases where you need to overrule the default via CSS. For those scenarios, it&#8217;s typically best to change the value of the <code>--wp--style--block-gap</code> CSS property rather than targeting a block&#8217;s <code>gap</code> or <code>margin</code>. You would do this as shown in the following CSS code:</p>


<pre class="wp-block-code"><div><code class="hljs language-css"><span class="hljs-selector-class">.some-target-class</span> {
    <span class="hljs-attribute">--wp--style--block-gap</span>: <span class="hljs-number">3rem</span>;
}</code></div><small class="shcb-language" id="shcb-language-6"><span class="shcb-language__label">Code language:</span> <span class="shcb-language__name">CSS</span> <span class="shcb-language__paren">(</span><span class="shcb-language__slug">css</span><span class="shcb-language__paren">)</span></small></pre>


<p>That may not always work. If a block (via <code>theme.json</code>) or user (via the interface) has defined a specific value for <code>blockGap</code>, that value will be used instead of the CSS property. In those cases, you should not attempt to overwrite the choice via CSS.</p>



<p>With an understanding of how the space between blocks is defined, you now have the foundation for seeing how that operates within different layout types.</p>



<h2 id="2-constrained-and-flow-layouts">Constrained and Flow Layouts</h2>



<p>Both of these layout types are technically flow layouts. This is how browsers handle the normal flow of a webpage without any intervention from CSS. WordPress defines the spacing between blocks by applying the <code>blockGap</code> value to the <code>margin-block-start</code> property of nested blocks (<code>margin-block-end</code> is zeroed out).</p>



<p>There is one key difference between the two layouts in WordPress:</p>



<ul>
<li>Nested blocks within a <strong>constrained</strong> layout are limited by the theme&#8217;s content width by default (this can be overwritten with wide/full alignments).</li>



<li>Nested blocks within a <strong>flow</strong> layout fill up the width of their parent block.</li>
</ul>



<p>As of WordPress 6.1, the constrained layout type is the default for the Group block. Other blocks may define different defaults.</p>



<p>In the following screenshot, you can see a wide-aligned Group block with a Paragraph and Image nested inside. However, these child blocks are &#8220;constrained&#8221; to the content width by the <strong>Inner blocks use content width</strong> setting in the sidebar:</p>



<img />



<p>If you toggle the switch for <strong>Inner blocks use content width</strong> to the off position, the layout would become a &#8220;flow&#8221; layout.</p>



<p>WordPress handles all of this out of the box. Theme authors should primarily be aware of the classes associated with each layout, which are <code>.is-layout-constrained</code> and <code>.is-layout-flow</code>. For the majority of use cases, there will never be a need to use those. However, when you need to style blocks or elements specifically within those layouts, target the specific layout class.</p>



<h2 id="3-flex-layouts">Flex Layouts</h2>



<p>Flex layouts in WordPress work on the Flexbox system in CSS. In reality, it is a limited subset of what is possible with Flexbox that fits within WordPress&#8217; design framework.</p>



<p>One major difference between flex and constrained/flow layout types is how they handle block spacing. Instead of applying the <code>blockGap</code> value to a block&#8217;s <code>margin-block-start</code> property, the value is applied to the containing block&#8217;s <code>gap</code> property.  Flex layouts also have options between vertical and horizontal layouts. </p>



<p>Several container-type blocks have flex layouts by default, including:</p>



<ul>
<li>Buttons</li>



<li>Social Icons</li>



<li>Navigation</li>
</ul>



<p>Looking at the Group block example from earlier, you should see <strong>Layout</strong> variations for creating a <strong>Stack</strong> and <strong>Row</strong> in the block inspector. Take a look at the Row variation, which has a horizontal layout:</p>



<img />



<p>If the Stack variation had been chosen, the blocks would have been aligned vertically.</p>



<p>With the addition of vertical and horizontal options, there are a few layout-specific classes that theme authors can target when necessary:</p>



<ul>
<li><code>.is-layout-flex</code>: Whether the layout has the flex type.</li>



<li><code>.is-vertical</code>: Whether the layout has a vertical orientation.</li>



<li><code>.is-horizontal</code>: Whether the layout has a horizontal orientation.</li>
</ul>



<p>Those last two map to the <code>flex-direction</code> CSS property. Horizontal layouts are given the <code>row</code> value and vertical layouts the <code>column</code> value.</p>



<p class="has-body-background-color has-accent-background-color has-text-color has-background"><strong>Note:</strong> The the default orientation for a block may not exist as a class in the block&#8217;s HTML, so you would need to target the layout class directly in that case.</p>



<p>Flex layouts also have another option to disallow nested blocks from wrapping to a new line as they grow. This is tied to the <code>flex-wrap</code> CSS property. The default value is for blocks to wrap, which is noticeable as you add multiple blocks to a horizontal layout. However, this can be disabled via the editor. In those cases, WordPress applies the <code>.is-nowrap</code> class to the element.</p>



<h2 id="4-content-justification">Content Justification</h2>



<p>In WordPress 6.1, the constrained and flex layout types both have content justification classes. These handle how the nested elements are aligned within their parent block.</p>



<p>Looking at the same example Group block from earlier, the following screenshot has a constrained layout with the content justified right:</p>



<img />



<p>There are four different content justification options for container blocks, each with their own CSS class:</p>



<ul>
<li><code>.is-content-justification-left</code>: Nested blocks are aligned left.</li>



<li><code>.is-content-justification-center</code>: Nested blocks are aligned center-aligned.</li>



<li><code>.is-content-justification-right</code>: Nested blocks are aligned right.</li>



<li><code>.is-content-justification-space-between</code>: Nested blocks are allowed to spread evenly with equal space between each. <em>For flex layouts only.</em></li>
</ul>



<h2 id="5-avoid-code-wp-container-code-classes">Avoid .wp-container-* Classes</h2>



<p>Some blocks may have a <code>.wp-container-*</code> class attached to them. In the past, there have been instances when it was necessary to target those classes to address some shortcoming of the layout system. However, this should be avoided altogether. There is no way to know whether the classes will exist in the future or whether their behavior will change.</p>



<p>Always opt for one of the specific classes outlined earlier. They are the standard going forward.</p>



<h2 id="6-future-layout-types">Future Layout Types</h2>



<p>CSS allows for all types of layouts, so it should be interesting to see what the future of the block editor brings&#8212;<em>perhaps even a grid layout type</em>. The goal is not necessarily to cover every potential use case. Rather, it is to offer a solid foundation that can be iterated upon as the web continues to change.</p>



<p>The layout system in WordPress is still marked as an &#8220;experimental&#8221; block feature, which means it is under active development. However, WordPress 6.1 has brought us one step closer to a well-rounded and standard framework for how current and future layouts will work.</p>



<h2 id="7-resources-to-learn-more">Resources to learn more</h2>



<ul>
<li><a href="https://make.wordpress.org/core/2022/10/10/updated-editor-layout-support-in-6-1-after-refactor/">Updated editor layout support in 6.1 after refactor</a> (Dev Note WordPress 6.1 release)</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/45055#issuecomment-1303815045">Layout Styles</a> explanations in the handbook</li>



<li><a href="https://developer.wordpress.org/block-editor/reference-guides/theme-json-reference/theme-json-living/#spacing">BlockGap in theme.json</a></li>



<li><a href="https://developer.wordpress.org/block-editor/reference-guides/block-api/block-supports/#spacing">Spacing  (incl BlockGap in block.json) </a></li>
</ul>";s: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, 04 Nov 2022 19:03:50 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:47:"Post Status: Who’s Going to Pay for All This?";s: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:32:"https://poststatus.com/?p=142747";s: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/whos-going-to-pay-for-all-this/";s: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:11740:"<div class="is-layout-flow wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt"><strong>Magne Ilsaas</strong> wants WordPress to be more than the pragmatic choice for enterprise clients. He wants WordPress agencies to be known for a distinct WordPress culture and mindset. <strong>Alain Schlesser</strong>, <strong>Carole Olinger</strong>, <strong>Carl Alexander</strong>, and <strong>Zach Stepek</strong> have a frank talk with <strong>Bob Dunn</strong> about the costs of not supporting WordPress contributors. Post Status members including <strong>Dave Loodts</strong>, <strong>Marius Jensen</strong>, <strong>Jeremy Ward</strong>, and <strong>Chris Reynold</strong>s discuss the looming <strong>PHP 7.4 EOL</strong>. Plus <strong>Jb Audras</strong>&#8216; breakdown of contributions to the <strong>WordPress 6.1</strong> release. For your weekend reading, some news and insights from business, workplace, webtech, and govtech writers beyond the WordPress bubble. </p></div>


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



<p class="yoast-reading-time__wrapper"><span class="yoast-reading-time__icon"></span><span class="yoast-reading-time__spacer"></span><span class="yoast-reading-time__descriptive-text">Estimated reading time:  </span><span class="yoast-reading-time__reading-time">6</span><span class="yoast-reading-time__time-unit"> minutes</span></p>
</div></div>



<h2 id="h-the-wordpress-enterprise-paradox"><a href="https://poststatus.com/the-wordpress-enterprise-paradox/">The WordPress Enterprise Paradox</a></h2>



<p><strong>Magne Ilsaas</strong> goes back a long way as a WordPress agency founder serving large enterprise clients. Why WordPress has been such a success in that space is now a barrier to its growth, Magne argues. It is not enough to be the pragmatic choice — the &#8220;tool that gets the job done, cheaply and effectively.&#8221; This leads to short-term engineering-focused solutions while &#8220;other [non-WordPress] agencies are helping clients with strategic decision-making, design and communication, user testing,&nbsp; conversion optimization, and digital marketing.&#8221; Magne wants WordPress agencies to be known for a distinct WordPress culture and mindset:</p>



<blockquote class="wp-block-quote">
<p>What if we did business the same way we've built WordPress? What if we leverage our biggest asset, which is not WordPress the tool. It’s WordPress, the community, the culture, the openness, and the inclusiveness. What if we create our own way of integrating our open-source mindset into how we conduct our businesses?</p>
</blockquote>



<p>While talking with Magne and working on this article, which was originally drafted a few years ago, he confirmed a couple of things that have kept coming up in my reading and conversations. They each represent both threats and opportunities: </p>



<ol>
<li> All the complaints, hazards, frustrations, and wishes of big agencies and their customers are very much aligned with small agencies, freelancers, and their customers. In particular, everyone wants clear quality signals for selecting plugins that meet their needs and don't distort, complicate, or disrupt the user experience, especially in the admin interface.</li>



<li>The agency space has been a boomtown, and there are established companies, some with hundreds of employees, who do work heavily or even exclusively with WordPress but have little or no involvement with the project and community. They hire specifically for WordPress knowledge and expertise with varying degrees of technical fluency. WordPress needs them, and they need WordPress agency peer networks and gatherings whether they know it or not. </li>



<li>Unfortunately, those connecting networks, events, and trade publications don't exist or are very underdeveloped in WordPress compared to the larger digital agency scene and web tech industry at large. It's important for WordPress agencies to be there too, in organizations like <a href="https://www.sodaspeaks.com"><strong>SoDA</strong></a> (founded in 2007) for <a href="https://www.viget.com/articles/viget-joins-soda/">the reasons described</a> by <strong>Brian Williams</strong>, co-founder and CEO of <strong>Viget</strong>, when they joined back in 2013.</li>



<li>Large WordCamps aren't meeting that need, and with the challenges of the volunteer model why should they be expected to? (<a href="https://poststatus.com/market-size-and-market-shares/">We've said this before</a>.)</li>
</ol>



<h2>Supporting WordPress Contributors </h2>



<p>Some of the best conversations that expert listener <strong>Bob Dunn</strong> has recorded for <strong>Do the Woo</strong> are open conversations with people the WordPress community is lucky to have. This time it's <strong>Alain Schlesser</strong>, <strong>Carole Olinger</strong>, <strong>Carl Alexander</strong>, and <strong>Zach Stepek</strong>. An alternative title for this talk could be &#8220;Why Can't Contributors Have Nice Things? (Like a Living Wage).&#8221; Carl's impactful <strong>Twitter</strong> thread <a href="https://twitter.com/twigpress/status/1577668456354238464">a few weeks ago</a> inspired the conversation.</p>



<p>Alain, Carole, Carl, and Zach all speak about the technical debt they see being piled onto WordPress — the project and the community — because of the high cost of contributing without solid or sustainable backing. Carole and Carl discuss the <strong>WordCamp</strong> volunteer model, which Carl thinks may be broken beyond repair, and with it, many years of institutional knowledge will be lost. Deep disconnection from the <strong>PHP</strong> community presents all kinds of risks and missed opportunities Alain addresses.</p>



<p>Behind Alain's voice, it's impossible not to hear <strong>Milana Cap</strong>‘s as they are both pointing out “<a href="https://developerka.org/2022/05/21/wheres-that-elephant-in-wordpress-community/">The Elephant in the WordPress Community</a>.” As <strong>Gutenberg</strong> truly starts to round the corner with the adoption and knowledge-sharing of standard-setters like <strong>10up</strong>, maybe there will be a collective realization: it's time to feed the elePHPant, or at least support some of our best elePHPant handlers.</p>



<p>In that vein, Bob mentioned in the show (and in a conversation we had this week) that next year he will be putting significant funding back into the community from Do the Woo's generous sponsors. But you can support <a href="https://github.com/sponsors/carlalexander">Carl</a> and <a href="https://github.com/sponsors/schlessera?success=true">Alain</a> right now with any amount you choose via <strong>GitHub Sponsors</strong>.</p>



<h2>End of the Line for PHP 7.4 in 23 Days</h2>



<p>On the themes of maintenance, technical debt, and &#8220;pay now, or pay later,&#8221; unless it gets changed as WordPress project leadership has requested, <strong>PHP 7.4</strong> will <a href="https://www.php.net/supported-versions.php">no longer be supported</a> with security patches as of <strong>November 28</strong>. Some hosts are forcing customers to upgrade or leave. <strong>Dave Loodts</strong>, who has found himself in the forced-to-leave category, <a href="https://poststatus.slack.com/archives/CHNM7Q7T8/p1667476104013399">started a discussion about it</a> in <strong>Post Status Slack</strong>. The views offered were broad-ranging, thoughtful, and relevant to the topics mentioned above. </p>



<p><strong>Marius Jensen</strong> pointed out that WordPress developers &#8220;are spending so much time keeping up with changes&#8221; to PHP in a never-ending maintenance loop &#8220;that it's hard to pick up new things [that can be done as PHP evolves] and innovate and use all the goodness PHP offers.&#8221; He feels &#8220;that's hurting our ability to move forward as well.&#8221;</p>



<p><strong>Jeremy Ward</strong> countered that &#8220;three years of support per release feels aggressive, particularly within our community due to the nature of our platform,&#8221; but &#8220;we can do a better job as a community at choosing an entry point with each major release to get things compatible. We knew PHP announced a change to their cadence, and to a degree, I don’t think we took them seriously that they’d stick to it. Until the <strong>PHP Federation</strong>, WordPress has more or less opted out of any language community initiatives, most notably <strong>PHP-FIG</strong>. I think all those smaller decisions kind of contribute to the challenges we face today&#8230;&#8221;</p>



<p><strong>Chris Reynolds</strong> noted that even though WordPress core rarely has problems with a <strong>PHP 8</strong> environment, <a href="https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/">PHP 8 only has beta support</a>, and enterprise customers aren't interested in anything &#8220;beta.&#8221; They need &#8220;official communications&#8221; and documents affirming full support, but WordPress's &#8220;official communication says it's not ready yet.</p>



<h3>Quick Links</h3>



<ul>
<li><strong>Jb Audras</strong> has <a href="https://jeanbaptisteaudras.com/en/2022/11/contribution-stats-for-wordpress-6-1-misha/">another fine report on contribution statistics</a>, now for <strong>WordPress&nbsp;6.1</strong>. Here's the tl;dr in <a href="https://twitter.com/AudrasJb/status/1587795340023005186">a Twitter thread</a> with a bonus graph of company rankings by number of commits. <strong>Automattic</strong> is #4.</li>



<li><a href="https://www.bloomberg.com/features/2022-the-crypto-story/?leadSource=uverify%20wall">The Only Crypto Story You Need</a> by <strong>Matt Levine</strong> at <strong>Bloomberg</strong>: &#8220;Crypto, in its origins, was about abandoning the system of social trust that’s been built up over centuries and replacing it with cryptographic proof. And then it got going and rebuilt systems of trust all over again. What a nice vote of confidence in <em>the idea of trust</em>.&#8221;</li>



<li>From <strong>Workplace</strong>, did you know <a href="https://workweek.com/2022/09/26/performance-reviews-dont-actually-assess-your-performance/">Performance Reviews Don't Actually Assess Performance</a>? And <a href="https://blog.jim-nielsen.com/2022/what-work-looks-like/">What Work Actually Looks Like</a>, from <strong>Jim Nielsen</strong>.</li>



<li><strong>Emily Peck</strong> at <strong>Axios Marketplace</strong> reports that <a href="https://www.axios.com/2022/10/19/remote-work-baby-boom-america">remote work may have fueled a baby boom among U.S. women</a>. This has never happened in a recession before among knowledge workers. Lots of interesting takeaways from this data. </li>



<li><strong>Google</strong> has <a href="https://therecord.media/google-backs-senate-bill-on-securing-open-source-software/">backed the US Senate security bill</a> aimed at &#8220;securing open source software.&#8221; Here's <a href="https://www.scmagazine.com/feature/devops/even-with-all-eyes-on-software-supply-chain-security-open-source-remains-a-neglected-target">a good backgrounder</a> from <strong>Menghan Xiao</strong> at <strong>SC Media</strong>. And here's <a href="https://thecyberwire.com/newsletters/policy-briefing/4/208">what compliance is going to require</a>. Get familiar with <a href="https://www.cisa.gov/sbom">CISA and SBOMs</a>.</li>
</ul>



<p></p>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 04 Nov 2022 16:49:52 +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: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:98:"Post Status: InstaWP: A Conversation and Tour with Founder Vikas Singhal — Post Status Draft 128";s: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:32:"https://poststatus.com/?p=142568";s: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:82:"https://poststatus.com/instawp-a-conversation-and-tour-with-founder-vikas-singhal/";s: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:40528:"<div class="is-layout-flow wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">InstaWP is about a year old now — let's take a tour of it and catch up with Vikas Singhal to see how he hopes it will evolve. Currently, it's a testing, demonstration, training, and marketing tool for WordPress product owners and agencies. Next, Vikas aims for InstaWP to support a marketplace for developers and agencies launching WordPress sites. Finally, he envisions it becoming a platform of platforms — WordPress-as-a-Service for people building their own WPaaS  </p></div>


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



<p class="yoast-reading-time__wrapper"><span class="yoast-reading-time__icon"></span><span class="yoast-reading-time__spacer"></span><span class="yoast-reading-time__descriptive-text">Estimated reading time:  </span><span class="yoast-reading-time__reading-time">6</span><span class="yoast-reading-time__time-unit"> minutes</span></p>
</div></div>







<p><a href="https://poststatus.com/planet/feed/#h-transcript">Transcript</a> ↓</p>



<p class="has-drop-cap">About a year ago, <strong>Vikas Singhal</strong> launched <strong>InstaWP</strong>, a serverless platform for spinning up WordPress sites instantly for demos and sandboxes, development and testing, or training and education. Along with WordPress, any combination of plugins and themes can be included. There’s <strong>GitHub</strong> integration, and InstaWP has the ability to push sites to a large number of hosts or pull them to a local development environment. (InstaWP generates Blueprints — .zip packages for <strong>WP Engine</strong>’s <strong>Local</strong> app.)</p>



<p>InstaWP is being embraced by WordPress product developers and agencies. It has significant product testing and marketing applications since customers can spin up any number of demo sites based on a custom template, and this activity is logged. Vikas has picked up <a href="https://poststatus.com/post-status-notes-501/">seed funding</a> from <strong>Automattic</strong> and looks forward to announcing many new partnerships with WordPress businesses that have found InstaWP and valuable and complementary tool.</p>



<p>Vikas sees InstaWP’s future as a marketplace for agencies, developers, and freelancers. Because of its powerful site templating and cloning capabilities, it could ultimately become a way to generate bespoke WordPress-based SaaS platforms at scale.</p>



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

</div>



<div class="is-layout-flex wp-container-6 wp-block-columns sponsor has-theme-palette-8-background-color has-background" id="StellarWP">
<div class="is-layout-flow wp-block-column">
<h3 class="StellarWP" id="Sponsor"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64f.png" alt="?" class="wp-smiley" /> Sponsor: <a href="https://poststat.us/stellarwp">StellarWP</a><a href="https://poststat.us/wpengine"></a></h3>



<p><strong>StellarWP</strong> provides WordPress solutions for all humankind. We’re a collective of leaders interested in growing WordPress companies. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. <a href="https://stellarwp.com/about/" target="_blank" rel="noreferrer noopener"><strong>Reach out to us if you’re interested in learning more!</strong></a></p>
</div>



<div class="is-layout-flow wp-block-column is-vertically-aligned-top"><div class="wp-block-image stellarwp-logo">
<a href="https://poststat.us/stellarwp"><img width="400" height="400" src="https://cdn.poststatus.com/wp-content/uploads/2022/01/stellarwp-logo-avatar-1.jpg" alt="StellarWP" class="wp-image-101425" title="StellarWP Logo" /></a><a href="https://poststat.us/stellarwp">StellarWP</a></div></div>
</div>



<p> </p>



<h3 class="eplus-wrapper" id="h-mentioned-in-the-show"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f517.png" alt="?" class="wp-smiley" /> Mentioned in the show:</h3>



<ul class="eplus-wrapper">
<li><a href="https://instawp.com/">InstaWP – Instant WordPress Sites for Everyone</a></li>
</ul>



<h3 class="eplus-wrapper" id="h-you-can-follow-post-status-and-our-guests-on-twitter"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f426.png" alt="?" class="wp-smiley" /> You can follow Post Status and our guests on Twitter:</h3>



<ul class="eplus-wrapper">
<li><a href="https://twitter.com/vikasprogrammer">Vikas Singhal</a> (Founder, <a href="https://instawp.com/">InstaWP</a>)</li>



<li><a href="https://twitter.com/dan_knauss">Dan Knauss</a> (Editor, <a href="https://twitter.com/post_status">Post Status</a>)</li>



<li><a href="https://twitter.com/lemonadecode/photo">Olivia Bisset</a> (Intern, Post Status)</li>
</ul>



<p class="eplus-wrapper has-background">The <strong>Post Status Draft</strong> podcast is geared toward WordPress professionals, with interviews, news, and deep analysis. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f4dd.png" alt="?" class="wp-smiley" /><br /><br /><a href="https://poststatus.com/category/post-status-podcasts/" target="_blank" rel="noreferrer noopener">Browse our archives</a>, and don’t forget to subscribe via <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008" target="_blank" rel="noreferrer noopener">iTunes</a>, <a href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zaW1wbGVjYXN0LmNvbS8ySkU5c2M4UA" target="_blank" rel="noreferrer noopener">Google Podcasts</a>, <a href="https://www.youtube.com/c/PostStatus" target="_blank" rel="noreferrer noopener">YouTube</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast" target="_blank" rel="noreferrer noopener">Stitcher</a>, <a href="https://wordpress-post-status-draft-podcast.simplecast.com/" target="_blank" rel="noreferrer noopener">Simplecast</a>, or <a href="https://feeds.simplecast.com/2JE9sc8P">RSS</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f3a7.png" alt="?" class="wp-smiley" /></p>



<h2 class="eplus-wrapper" id="h-transcript">Transcript</h2>



<p><strong>Dan Knauss:</strong> [00:00:00] With Singal here, with Insta, wp get a little tour of where we're at today with with this new and interesting product. I think, I think you've been Pretty familiar in at post status anyway. I know a number of members have been been using this platform.</p>



<p>So how did, how did you put it together? What would you like to people to know who are completely new to it, who haven't seen Insta WP before?</p>



<p><strong>Vikas Singhal:</strong> Yeah. There's an interesting question. First of all means I would like to thank post status because that's where I posted about instead of the. For the first time, and that's where it took off.</p>



<p>I remember you or you were with Dimension Media handle, right? Right. Well that's</p>



<p><strong>Dan Knauss:</strong> David Bi and I Yeah, that was, he was he was [00:01:00] with us then. Right.</p>



<p><strong>Vikas Singhal:</strong> Right. So yeah, you guys shooted about instead of Lupe and then it took off really well. I got initial interest initial kind of early adopters from post status.</p>



<p>So that was great. Mince, how did I put it together, is I started with WordPress about four or five years ago, but, and then I built a plugin theme company over the years, and I also have that in parallel which is still in we are still alive. But the, the biggest thing, which I always wondered that, why don't we have like a good.</p>



<p>To create a workplace website like you do, like a Shopify website or any other SAS-based platform where you just click like a great site and it, it gives you site. Instead, you either have to set up like a clunky local setup which takes away your cpu, and it's, it's, it's not that easy, right? And at the same time when you use your hosting account, it has its own disadvantages.</p>



<p>Then you have to go multiple steps. [00:02:00] You have to do, you have to eat up your hosting credits and other things, right? So you don't, It's not like a really like a playground where you just create a site and then test it and then dispose it. So the initial idea was to give kind of a platform where you can create a disposable site.</p>



<p>At least that's how it started. And then it obviously became something completely like not different, but more wash than the initial idea. And so that's how it started. And it was started about a year ago, I think, September, October 2 21. When I I created MVP and posted and post as, as I said earlier and then obviously about six months, eight months down the line we got funding from Automatic and then it, it bo it became all real and.</p>



<p>All kind of so much pressure, , but yeah, I means we are at this point that we have like a good version, one plus plus kind of project product with, with us. A lot of folks are using it. We have about thousand websites being [00:03:00] created on Insta every day. So I like to think that we, we contribute some part of this to the workplace ecosystem wherein because we have a very generous, free plan.</p>



<p>You get five websites where you can create, in your account you have like 500 MB of disc usage. You can create a template and all that. So I know a lot of folks are using the free account and we are happy with it because that increases the engagement with the platform and that gives us a lot of feedback.</p>



<p>So with that, I think it's time. I give you a small demo of how it looks like. Good. And then you can go from there.</p>



<p><strong>Dan Knauss:</strong> Right. Are you hoping that those who are using the, the free accounts will convert and up upgrade later? Or are they they two different audience segments where people are doing very quick testing, but then maybe maybe another group is ends up using it as, as a more permanent platform or for something that they launch sites to, to other hosting providers?</p>



<p><strong>Vikas Singhal:</strong> Yeah, so I think [00:04:00] we, as I said, we started as a disposable site platform, but then we are now allowing people with a paid account to reserve a site for extended period of time, so you don't need to actually let it expire. So, so these are two different personas of our users. One is someone who are just testing disposing so they don't need to upgrade.</p>



<p>And we don't expect them to upgrade. But then there is obviously another serious users like agency owners product owners, developers. Who, who, who want to ex explore the platform to another dimensions or another levels of what, what it can do. So that's, that's where we want.</p>



<p><strong>Dan Knauss:</strong> Yeah. You have some who are using it as a permanent sandbox for demoing their own products that well they might periodically completely overhaul it, change it, put on, update their their system, but their customers are, are using it.</p>



<p>Is it, I guess they could map it to any domain that they like.</p>



<p><strong>Vikas Singhal:</strong> Right. A lot of our agency customers, what they do is they create a. [00:05:00] The market as a permanent site. So when we say permanent on Insta is not like a hosted site, so we don't provide hosting. But they can still map like a custom domain to, to that Insta site.</p>



<p>And it becomes like a white label site at that point. And you can actually show that to your client once they're okay with it. Who can do one click migrate to they're host. Account or your hosting account, however it is set up. So it doesn't really matter. So, so it's, as I said earlier before our call, that it is kind of a breeding ground, right?</p>



<p>Where you like you nurture your baby and everything is okay, and then you push it off to the world, right? So, and then all your tools, all. So our vision is that we connect. All the plugin provider, all the team providers have a template store, have a product store have the, have our cloud underneath.</p>



<p>So when, when we become the clue, right? So we, we tie them together. And I think you shared one interesting post recently about onboarding on on WordPress. So we are trying to solve that for agencies and freelancers at least, at least for them, right? [00:06:00] And then maybe later on we can bring in DIYs as.</p>



<p>Who want to build their site, and they will have like a ready made starter templates. So, so it, it'll be really, really easy for them to get a new site.</p>



<p><strong>Dan Knauss:</strong> Great. Well, yeah, let's, let's spin one up. You can go from scratch or, or from a, a template it looks like.</p>



<p><strong>Vikas Singhal:</strong> Right? So you can start from a template if you have one.</p>



<p>So we have created some templates, so we can get back to that later. And then you can start from scratch. So you can choose WordPress version. So we, we support all the way to older version and newer, newer versions. Even better versions. I think 6.1 is what , it'll be added. And you can also test on multiple PHP versions all the way to 8.1.</p>



<p>You can choose some presets of configuration wherein it is not actually like a snapshot, but it is like a set of configuration parameters. So you can say that auto in install, Astra auto install, Elementor auto install whatever dv, even if it is premium theme plugin, it doesn't really matter. So [00:07:00] I'll show that in a.</p>



<p>You can provide a site name or you can just keep it blank for a random site. So I am just keeping everything as default and clicking on Create site. Also just to for, for, for the purpose of completion that we have a temporary site option and a reserve site. So this is disabled on a free account.</p>



<p>The free account, you can only do temporary sites. So let's create, let's do. And within a few seconds you should have a new site, new site, ready to go for you. Right. And the one, the detail which we show is obviously the url, username and password. So when you click on it, you should get a site. Up and running.</p>



<p>And you might notice that this particular, in this particular instance we have some faker data already populated. The reason being my default configuration has that. So if I go to configuration tab and choose default and go to Faker, so my core figurer is on, and I have created some posts, some pages, some tags, some categories.</p>



<p>So we, so we are using Yost faker [00:08:00] internally to do all. Right. And then you can also do like a what kind of keyword you want to do for, Oh,</p>



<p><strong>Dan Knauss:</strong> what's a, what's a faker? I was looking at that yesterday and, and wondering, I'm not familiar with that term.</p>



<p><strong>Vikas Singhal:</strong> So a lot of time you want a website filled with some content, right?</p>



<p>It doesn't really matter what kind of content you need, so, This is like that, so, Oh, right.</p>



<p><strong>Dan Knauss:</strong> Okay. So prepopulated content.</p>



<p><strong>Vikas Singhal:</strong> Yeah, Repopulated content. Yes. So, exactly. So some posts, some pages, some authors, so that it gives you somewhere to start, right? Not necessarily. You want to start from scratch. Sure. So you can switch it off, switch it off.</p>



<p>By default it is switched off and there is a lot of other configuration, as I said earlier, so you can make a default configuration of your site language multi-site. Reinstall plugins, pre-install teams and all that. So obviously a lot of options, we can go over them one by one, but let me just explain what is, what are the main features which we have.</p>



<p>So so second [00:09:00] thing is you can do like a quick auto login to your site and you don't need to remember you're using 'em in password and then it straight away goes to the WebPress admin. And then you can imagine you can just work from there. So you, you can imagine that this, these kind of features are not, Kind of not available in all the platforms.</p>



<p>Right? Some features, some platform will have some feature, but our focus is completely on making WordPress cool or WordPress easier to use, right? Right. You don't need to worry about installing a bunch of things to, to make these things happen. So another option is reserving a site. So if you have, let's.</p>



<p>You want this site for a longer period of time. By default, it gives you, like, based on your plan. So if you have a free plan, you, it gives you 48 hours. If you are on a paid plan, it, it goes from seven days to to up to a month, right? And we have add-ons, so you can always increase those options. So you can reserve a site and this will never expire.</p>



<p>And these are, this becomes like a permanent site. And then when you are comfortable, you can [00:10:00] delete it yourself if you want. The second cool option is saving this as a template. So there are multiple kind of para, multiple paradigm how you can use a template. So let me just, let me just first, first create a template.</p>



<p>So template is nothing but like a snapshot of your site. So it saves, it saves the content, it saves the database, it shifts everything. And like a backup of your site. Let's say demo PS, and you can put a description, post status demo template. Somebody has taking this name ops, so let's say obviously add one</p>



<p>So yeah, that was probably me say, yeah. Oh, maybe you , right? So now if you go to your private template staff, this demo, this template creation is in. So it takes few moments depending upon the size of your site, and now within few seconds, you will have it ready. So basically at this [00:11:00] point there are multiple things which, which you can do with the template.</p>



<p>So first, the most easiest option is go back to sites, click on Agnew, and you will have this from template. Now this thing is appearing here, create site. So the new site will have. Whatever you had on the parent's side, right? So, Right. It's that easy now. So it takes a few moment because now it is being created from attempted rather than scratch from, from a blank worker's side.</p>



<p>So it takes few moment based on the size of, of your parent's size. However, we, we do have an like a really interesting option where you can mark your template as an instant template. So that's like an advance option only available in the agency. So a lot of that is actually very useful when you like, do like a sandbox and all, and it'll do, it'll create a site instantly, right?</p>



<p>It, it won't, it won't take even a, even a second. So now this site is completely like a, like a clone of your parent's site [00:12:00] and only the name changes. The URL changes. So you, so whatever changes you make on the parent's side, obviously is not. Those changes are not affected here, right? So, so these are two different sites and you, you can see in your list also that this comes from the template.</p>



<p>There's a small section that shows that. Now this was just the basic operation of a template. However, there are two things which can do here. One is connecting this to a get deployment. So I will not get into much detail with the interest of time, but what happens is if you have, let's say, a plug. Or a team on a, on a gi it can be on GitHub, it can be on Bitbucket.</p>



<p>It doesn't really matter. But we support GitHub more natively for now. But other supports are also coming. What happens is if you, let's say, if you have a Bud Press plugin, and the, the biggest thing, which we have noticed because we also develop plugins, is that. There are multiple developers who are working on, on a plugin.</p>



<p>Let's say one developers [00:13:00] developing one feature. One is fixing another bug. They'll be doing that on their own kind of prs, right? They will have their own branches. They'll raise a pr. What will happen is as soon as they raise a PR and you have set up your get report with, with the template, every time there is a pr per.</p>



<p>They will get a special workplace deployed for them, which is created from the parent side, so it is loaded with all the bells and visuals, all the other companion plugins, all the other content. Right, right. And then it'll pull the latest plug-in code from that pr. So I'll just show that I'll show an example of what we have done in the past rather than connecting the whole thing.</p>



<p>So if you see one of these prs, you will see. Sure. So for example, I changed this file, so I changed the version of my WordPress plugin. So what happens is as soon I raise this pr my new WordPress instance was deployed. Instead of loopy and it had then that new code. So you can [00:14:00] imagine the, the impact of it.</p>



<p>Right. So it, so within moments you get a site and you can test your new feature, and then when you close the pr, that site will be destroyed. Right? Right. So that site is gone. And this is kind of one of the most asked, most used featured by, especially the product developers, the the who are developing for breakfast.</p>



<p>Sure. So the next cool option is the share template. So once you mark a template as share it becomes, it is basically a sandbox at that point, right? So it, now if you go to the share tab and this demo, PS one is actually having a shared link, right? So if I open that, copy that and open in a new. What happens is I get a landing page and the interesting thing thing about is this landing page is that it is available for all users, not just logged in users.</p>



<p>Right? So this is ready to go anybody. [00:15:00] So let me open this in, in Incog mode, and you will see that this is this exact landing page pages available for an anonymous user. Now what, what are you doing exactly? You have offered your template. As like a sandbox for anybody to test. And this is what a lot of folks are doing as you said, as we discussed earlier.</p>



<p>So let me enter an email id and then within seconds it'll start creating a site based on a template, and then it'll give you to the user. Now, if you go back to your panel, we have simple statistics built in. So if you click on statistics you'll see that one site was created today, first November. And then if you go to table, you will see that the site was created, who created it, right?</p>



<p>And there are like tons of options you want to create. If you want to collect email, you want to link it to your MailChimp account, ah, that you want to call a web. So,</p>



<p><strong>Dan Knauss:</strong> so that, that, that initial login box I saw it had a checkbox for a newsletter that could Right. That's not yours. [00:16:00] That's a instant wp. That could be the the right, the user for someone's doing a sandbox for their plugin.</p>



<p><strong>Vikas Singhal:</strong> Right. So you, you can actually change everything. So, so we show a quick preview of why you're changing it. So let's say you don't want to collect email, right? So this thing will be gone. But if you want to collect email and you want to hide the previously check box, you can hide that. You can mark email as required if you want to like change the previous policy text.</p>



<p>Wow. So let's say, yeah, So this is a new policy. Let's see. And you can see it real time changing. We also send out an email when somebody. A website which, so this email can be completely customized based on like your brand, you can upload a brand logo, so this instead of logo will be replaced by that logo.</p>



<p>All this obviously is in paid plan, so not available for paid users. Free users. However, free users can come up to this point with all the options as default, and they can still create a shared template, one shared template in a free.</p>



<p><strong>Dan Knauss:</strong> So this is, this [00:17:00] would be great for marketing purposes than if, or, or if you wanted to have a select group of people test a new feature and, and give feedback.</p>



<p>But this would give you some, some good data back on if you did a campaign of test some new features or, or Try before you buy,</p>



<p><strong>Vikas Singhal:</strong> right? Yeah. A lot of companies, like even Gravity forms, they're using for beta releases. So they're select group of people who are doing beta testing. So they create a template because a template has all the, all the things, as I said earlier, right?</p>



<p>Content plugin, and they can create new instances based on the template and they're ready. Nice. You can also set lifetime of these sites, which I created from the template. So it can go from 30 minutes all up to 15 days. In fact WordPress, full site editing outreach experiment. I don't know if you know that.</p>



<p>Connected by Annie. Oh. Yes. Great. So they are using this as a part of their. Outreach. Does</p>



<p><strong>Dan Knauss:</strong> the does the use data then get logged separately? So if, if a site expires that [00:18:00] someone has, has used, you're still getting An aggregate of, of all the data that, that's been produced by users.</p>



<p><strong>Vikas Singhal:</strong> Right, Right.</p>



<p>So yeah. So basic status effects will include even the expired sites. So here, this, this data will show even if the site expires, because you need to, you need to see the trend. But we are coming up with some advanced statistics on how much time did the user use, how many pages did they visit? Things like that, Right?</p>



<p>What was the actual usage pattern of the user so that you can take informed decisions based on that,</p>



<p><strong>Dan Knauss:</strong> right? Oh, that's terrific.</p>



<p><strong>Vikas Singhal:</strong> Right. And I can export this list as csv and yeah, you can do a lot of stuff. So, yeah, So that was about templates. So sites and templates are. The core of, instead of, But then obviously we have configurations.</p>



<p>We have deployments. Deployments is where you can connect your GitHub account and all. And then we [00:19:00] have mail shift integration and more integrations coming in. We, you can create multiple teams, so these are like workspaces. You can invite team members to different workspaces. We use it for our own team, obviously.</p>



<p>So we eat our own dog food and. So I guess in the sites thing one more thing, a couple of more things maybe shown. So you can use tools like code editor you can use tools like D Editor. So these things are like really quick, right? So, and everything about Insta is instant, right? So it has to be very, very quick.</p>



<p>You don't need to do any configuration. So you can see all the WordPress tables are now open up, right? So it's that easy, right? And same thing. So if you hover a site, you can still get the same thing. So code, I guess you have already used that. So this is something as we want to improve that. But still this is very powerful.</p>



<p>So it is like a multi tab editing experience similar to what Sublime or Visual Code provides. But we are building our own code editor [00:20:00] which will be like similar to Sublime Experience, and then it'll also have like a multi. Party collaboration. So let's say you and I can share a URL and then can, can work on the same work site online.</p>



<p>Right. So you'll see mouse moving, you'll see them editing like similar to in Google Doc. Sure.</p>



<p><strong>Dan Knauss:</strong> Yeah. When I, when I tried this out, I, I found, So you have to go under file and, and click save and then it instantly becomes active on the site. Yeah. So these</p>



<p><strong>Vikas Singhal:</strong> are all active. Yep.</p>



<p><strong>Dan Knauss:</strong> Right. There's, there's not really a, It doesn't give you any feedback on whether you've white screened the site or not, but you, you don't get locked out if there's a, a failure.</p>



<p>Is there any kind of error logging built in here or, or a way to roll back? Changes.</p>



<p><strong>Vikas Singhal:</strong> The first option is built in, so if you can hover over the site, you'll see view locks. Oh, okay. So here you can see error locks and access locks, and you can actually search through the locks. And we are coming up [00:21:00] with debug locks as well.</p>



<p>So we'll switch on W P D bug, and then you can see those logs as well. And then the other one, which you talked about is rolling back is an interesting feature. So what we are trying to do is create versions of your site. So let's say you are working on the site and then you are good with that. You will have an option here itself on, on the top, let's say save snapshot or a save a version.</p>



<p>It'll create like a quick version of the whole website and then you can roll back to any of the version at any point. Wow. And I guess some other cool stuff here is obviously we have this ssh. So you can enable SSH and with SSH you get access to WP cli. That is like very, very easy, very, very quick.</p>



<p>So you can, if, if you have time, I can just show this to you real quickly. So you enable SSH takes a second and you open your ssh. So as a part of our making this even easier we will have [00:22:00] like a SSH console right here, okay? Right next to close, which will say like, open console, web console of ssh, and it'll open the whole thing inside the website, right?</p>



<p>So you don't need to open your ssh client. If you want, you can do that, but you don't need. , right? Same with the same with ftp. So you enter your username password, enter your SSH key, boom. So you are inside your website. So let me clear this up. So you can go to the public folder and yeah, so you have all the sites and then you can do like a lot of stuff obviously.</p>



<p>So you have like W P C I command, you can run them right. Not a problem at all.</p>



<p>All right. I think I've covered at least 70, 80% of what we can do with Insta. Obviously there is some more things to explore and a lot of things coming up right.</p>



<p><strong>Dan Knauss:</strong> And it has an [00:23:00] export feature. A lot of, a lot of us use WP Engines local product for, for local development. And that exports a blueprint right here that you can, you can import to,</p>



<p><strong>Vikas Singhal:</strong> to local, right?</p>



<p>So it'll email you a zip, a link to afi, Uhhuh , which you can download, and then just drag and drop to local w p and you don't need to do any configuration. Nice. Okay. And then, yeah, so map of map domain is where I think we spoke about it, is where you just create a c record to this particular site, and then you can map it to any domain of your choice.</p>



<p>Okay.</p>



<p><strong>Dan Knauss:</strong> So that's, that's great. You're up to a thousand. Regular customers now and are you, are you seeking further investment? What are, what's next for it as, as a growing business and, and what, what do you see happening in your, in your roadmap for the future?</p>



<p><strong>Vikas Singhal:</strong> So we have more, more than that.</p>



<p>We have, we are [00:24:00] actually getting thousand websites created on INTA Per day. Every day. Yeah. Per day. Right, Right, right, right. And we, we have, we are getting, we are getting great reaction from users. We are free to pay. Conversion is about five to 10%, so that is also good. And regarding further investments, we have got interest from the market to be honest.</p>



<p>But then we want to even test the waters even further so that because when you take money from market, it creates tremendous pressure and responsibility because you can't just throw that money around, right? You, you have to be, you have to own it. And so what we are doing right now is figuring out our marketing strategy wherein where, where, who is our ideal customer and who can pay us X amount so that it, it justifies the business.</p>



<p>And that's where we are exploring more and more things. And you will see a lot of things happening. Like we are, we are sponsoring, we sponsored a small sponsorship on work camp. And, and then work Camp Asia is a [00:25:00] bigger sponsorship. I'll be there personally and a lot of stuff, we, we are, our, our stuff is going to be featured in a lot of YouTube channels, lot of guest posts, lot of partnerships.</p>



<p>You'll see a lot of stuff in coming weeks and months. Good.</p>



<p><strong>Dan Knauss:</strong> Good. Do you have, have a sense of who that ideal customer is? Who, where do you think that's leading you</p>



<p><strong>Vikas Singhal:</strong> right now? There are two personas which we are kind of targeting. One is the agency freelancer market who are developing site for clients.</p>



<p>So that's, I, we have got several of those and those guys are like, Really, really happy with the product because it, it gives them like, kind of it empowers them, in fact to, to create WordPress sites without thinking about the underlying infrastructure. And they can, they invite their team, they can invite contractors, they can do a lot of stuff, which they, they would have been doing it, but with.</p>



<p>Connecting several pieces and then creating some something of their own right. And second person persona is the [00:26:00] product. Develop developers, the, the, the plugin and theme authors out there who are developing products. So those guys are like, those folks are using for sandboxes for their data integration their staging testing of their plugins before releasing them, right?</p>



<p>Things like that. So these are the two personas which we are targeting right now. Yeah,</p>



<p><strong>Dan Knauss:</strong> that, that makes a lot of sense. It's, it's very familiar from, for anyone who's, who's worked with, with something like local before but you're actually working live in the browser very. With a very quick response.</p>



<p>You know, that's, I can see the educational purposes too for for opening, opening up WordPress development in general for for people who are new to it or, or trying to to learn or say Bringing in software engineers who, who maybe have less familiarity with WordPress and just, you know, quickly, quickly picking Yep.</p>



<p>Picking things up. Are you seeing that at all too? Any interest from the, [00:27:00] from project itself or, or others who are, who are doing training?</p>



<p><strong>Vikas Singhal:</strong> Yeah. So we have few folks who are doing trainings and education piece both free and paid. So we have got a lot of like non-profits and schools who are using this like a simple WordPress because they don't care about the underlying frustrated all the need is a WordPress site.</p>



<p>Sure. Right. So, and that, that is where we excel and obviously there are a couple of educators who are using this as a. Engagement. So they share like a hidden shared link of their sandbox. So they use that sandbox feature wherein they, they can say that you get a ready made starter template wherein you can, And this here is your study material and here is your ready to go WordPress template, and then you can start from there.</p>



<p>Right? So we have got like Jamie from Poodle Press and other folks who are using this as a, as, as an educated tool. So that is something That's great.</p>



<p><strong>Dan Knauss:</strong> Yeah. Yeah. And being able to collaboratively edit work on code that seems like that would open up [00:28:00] all, all kinds of possibilities for.</p>



<p>Onboarding new developers teaching teaching people who have haven't seen this before at all. Well that's, that's really great. Is there anything else we should look at or that you'd like to. To cover it might be of interest to post status members and, and others in the community.</p>



<p><strong>Vikas Singhal:</strong> Yeah, Miss our vision is actually really, really big.</p>



<p>I don't know whether we will be able to achieve it, but we'll obviously do our best. Though this is step number one, right, to create a cloud or create some kind of infrastructure wherein you get a WordPress site. Step number two will be once we have all the agency, all the freelances the agency owners and the developers on board.</p>



<p>And when we have like a hundred thousand plus users. We will have, we can have actually a marketplace because these, these guys are actually service providers, right? All these folks are service providers. And then when we bring in DIYers who are actually biased, even these, these folks can be biased among themselves, right?</p>



<p>So let's say [00:29:00] a, a person is offering their services like they do on Upwork. We can create such kind of platform on top of instead wp, right? So they, now Dan Orka can offer their services. They can offer their ready met templates, which they have worked on. Let's say they, I'm a designer, I can create a really nice gym training template and then I can offer that for 30 bucks a pop or maybe like a, Something like a theme forest on the steroids, right?</p>



<p>So Uhhuh something, right? So like a template store and then you can sell basically is a marketplace for buying and selling. So that will be step number two. Step number three will be means creating completely like a. Vs. Or a web flow kind of environment where you get a starter template, which is connected to somebody else's hosting account.</p>



<p>So it becomes like a WordPress as a service at that point. So let's say you have some [00:30:00] clients you can have, you can connect your WP Engine account within inta and anytime somebody requests a website from you, you can actually give them a link of your store Sure. Of, of your INTA store link, right? And they then they can go and they can buy a website.</p>



<p>Which is actually internally hosted on your WP Engine account. Right. And everything is automated, right? So, So that will be like the biggest thing. So these things are like, it'll take months and years, but we'll get there. Right.</p>



<p><strong>Dan Knauss:</strong> Oh. Tell me a little bit about the cooperation with Blog Vault. You, that's, that they're providing the the ability to export quickly to, Wow.</p>



<p>It looked like, it looked like there were over a dozen hosting providers that Right. That they can connect you with. How did how did that relationship come about and, and how are you working together there? That's. I imagine that's done. Brought them a, a lot of a lot of activity, a lot of users.</p>



<p><strong>Vikas Singhal:</strong> Yeah, so Blog World is already pretty famous, so, but, and their product is [00:31:00] really robust and that's why we have, we integrated with them, right? So we do like a native integration where you click on migrate and then it shows up like 12, 15 options where you can migrate to however, in coming weeks, as I, as I told you earlier, that.</p>



<p>We are coming up with our own Connect Connect plugin wherein you can connect your hosting account, you can your ok, any WebPress site on, on the internet and they can, you can push even, even easier, right? So the biggest problem which we are trying to solve is pushing. It changes. So let's say you created a staging site.</p>



<p>You like, let's say you. Edit it. Couple of posts. Couple of pages. You installed a plugin, you did some s right? But when you push from staging to production, there is no good product right now on the market. Who can, who can re, who can recognize these changes? Right. The, the, the I creative changes and then push it like a GitHub, like a get come at.</p>



<p>To the production site. Right. So that is something, is something we are researching on internally and we are very, I think we are positive on [00:32:00] that. So once we solve that, it'll become a game changer. Right. So you don't need to touch your production site. All changes will be done on Insta. Right.</p>



<p><strong>Dan Knauss:</strong> Well, very nice.</p>



<p>All right, well, well thank you for the, for the tour. appreciate that. Best of luck to you and thank you. It's exciting to see, see it grow so, so quickly and</p>



<p><strong>Vikas Singhal:</strong> so well. No, thank you for listening to it patiently, and thank you for having me. Thanks.</p>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 04 Nov 2022 04:21:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:74:"WPTavern: WP Rankings Helps Plugin Developers Track Growth and Competitors";s: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=139125";s: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://wptavern.com/wp-rankings-helps-plugin-developers-track-growth-and-competitors";s: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:5056:"<p>Last month, WordPress.org <a href="https://wptavern.com/wordpress-org-removes-active-install-growth-data-for-plugins">removed the active install growth chart from plugins</a>, upsetting plugin authors and leaving them with very little meaningful data. The Meta team is working on making more accurate and useful data available to plugin developers, but this will take some work. In the meantime, the team behind <a href="https://ayecode.io/">AyeCode</a>, makers of the <a href="https://wordpress.org/plugins/geodirectory/">GeoDirectory plugin</a>, has created a tool to help plugin developers get an idea of how their plugins are ranking.</p>



<p>&#8220;The popular plugin list is still there (and hopefully, it won&#8217;t be removed or altered),&#8221; AyeCode co-founder Paolo Tajani <a href="https://meta.trac.wordpress.org/ticket/6511#comment:77">commented</a> on the <a href="https://meta.trac.wordpress.org/ticket/6511">ticket</a> that requests the active install growth charts be restored. &#8220;As far as I know, active install count is the only ranking factor of the popular plugin list. I know it is not ideal, but it is what it is, and that is all we have.</p>



<p>&#8220;Because wp.org only shows 99 pages (the first 1980 plugins), we quickly built a site to provide those basic stats to all plugin authors.&#8221;</p>



<p>AyeCode&#8217;s <a href="https://wp-rankings.com/">WP Rankings</a> website launched one week after the active install growth chart data was pulled. It shows if a plugin is ranking higher or lower than the day before and how many positions it needs to climb to reach the next milestone. The homepage shows the &#8220;top 50 ranking climbers&#8221; of the day, and these can be filtered by the number of active installs. All the data is refreshed daily.</p>



<img />



<p>AyeCode built the site using the GeoDirectory plugin, the Blockstrap theme, and custom code to fetch the data from the WordPress.org API. </p>



<p>&#8220;We also wanted to show how easily GeoDirectory can handle +50k listings with a lot of custom fields on a pretty basic hosting plan,&#8221; Tajani said. &#8220;Most Directory plugins wouldn&#8217;t be able to do that.&#8221;</p>



<p>Plugins can be searched by tag so visitors can see how their plugins are growing compared to others using the same tag.</p>



<p>For example, Tajani said he keeps his eye on the <a href="https://wp-rankings.com/plugins/tags/business-directory/">&#8220;business directory&#8221; tag</a> every day to see how the GeoDirectory plugin is doing. Tajani said the API offers enough info to know if a plugin is growing, shrinking, or plateaued. </p>



<img />



<p>Some of the data in the rankings is taken from the API and some of it is calculated, including the trends, the number of days until the next milestone, the number of five-stars to the next rating, and the number of positions to the next milestone. </p>



<p>Clicking through to the individual plugin pages offers more graphs/charts about their movement on the popular plugin list. The data  from the API is remixed in various ways to extrapolate insights. For example, the number of days to the next milestone is based on the plugin&#8217;s current growth trend.</p>



<img />



<p>The individual plugin pages display a 15-day rank change chart, along with 24-hour and 7-day trends.</p>



<img />



<p>A review stats graph estimates how many 5-star ratings are required to reach the next level. Another graph tracks 15 days worth of resolved support threads against the total number of threads logged.  </p>




<img />



<img />




<p>The last section shows a list of the plugin&#8217;s  competitors and a summary of their rankings and growth trends.</p>



<img />



<p>The <a href="https://wp-rankings.com/statistics/">stats page</a> shows how many plugins there are for each active install range up to 5 million. It&#8217;s interesting to see that there are 8,071 plugins with zero active installs and 13,643 with just 10. Another large concentration of plugins falls within the range of 100-400 active installs and another between 1,000 &#8211; 2,000 active installs.</p>



<img />



<p>Clicking through on the stats page will show the specific plugins in that range. </p>



<img />



<p>Tajani said the next thing on their roadmap is allowing plugin owners to customize the list of competitors and adding the specific plugins they want to see compared against their own. AyeCode plans to keep what they have built with WP Rankings free indefinitely.</p>



<p>&#8220;What we really wanted to do is show another statistical point of view,&#8221; Tajani said. &#8220;We know it&#8217;s not the same and we will receive criticisms, too, but right now it&#8217;s the only way to know if a plugin is growing or not.</p>



<p>&#8220;What we will do with it in the future depends on how much plugin developers will like the idea and what kind of feedback we receive. If enough people start asking for features that could be considered premium, we will consider it.&#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, 04 Nov 2022 02:34:33 +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:39:"Post Status: Make WordPress Sustainable";s: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:32:"https://poststatus.com/?p=142669";s: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://poststatus.com/make-wordpress-sustainable/";s: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:3364:"<div class="is-layout-flow wp-block-group"><div class="wp-block-group__inner-container">
<p class="has-small-font-size">By <a href="https://poststatus.com/planet/feed/#author">Hannah Smith</a> • November 2, 2022 <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f5d3.png" alt="?" class="wp-smiley" /></p>
</div></div>



<h2 id="h-what-does-sustainability-mean-for-wordpress">What does sustainability mean for WordPress?</h2>



<p class="has-drop-cap">In a few weeks' time, world leaders will be gathering for <a href="https://news.un.org/en/story/2022/10/1129947">COP27</a>, the largest annual gathering on climate action. This annual conference is a good focal point for everyone to think more about sustainability, including the WordPress community. We've recently published <a href="https://make.wordpress.org/project/2022/11/01/sustainability-channel-what-should-we-do/">a post on Make WordPress</a> to encourage the community to do just that: openly share their ideas about sustainability.</p>



<p><strong>What does a sustainable WordPress community mean? <em>What does it do?</em></strong> Tell us!</p>



<p>We hope you will get involved by:</p>



<ul>
<li>adding your ideas, responses, and feedback to the post;</li>



<li>spread the word about the post/discussion.</li>



<li>joining the Make WordPress Slack <a href="https://wordpress.slack.com/archives/C03JNV77Y57"><code>#sustainability</code></a> channel.</li>
</ul>



<p>We really want to encourage others to weigh in so we can build on what is already happening, and find ways to make more happen! We hope this effort will start to:</p>



<ul>
<li>Demonstrate to leadership and those with positions of power/resources that the community wants more effort on sustainability;</li>



<li>Help us identify others in the WP space who can collaborate with us;</li>



<li>Gather ideas on what new directions we can take things in.</li>
</ul>



<div class="wp-block-media-text is-stacked-on-mobile has-background" id="author"><a href="https://poststatus.com/"><img width="416" height="416" src="https://cdn.poststatus.com/wp-content/uploads/2022/11/1624637710553-jpg.webp" alt="" class="not-transparent wp-image-142680 size-medium" /></a><div class="wp-block-media-text__content">
<p><strong>Hannah Smith</strong> is a Sustainable Digital Tech Trainer and Ops manager at the <a href="https://www.thegreenwebfoundation.org/">Green Web Foundation</a>. She is Co-founder <a href="https://greentechsouthwest.org/">Green Tech South West</a> and founder of <a href="https://climateaction.tech/projects/letsgreentheweb-campaign/">#LetsGreenTheWeb</a>.</p>



<ul class="is-content-justification-center is-layout-flex wp-container-26 wp-block-social-links alignright has-small-icon-size is-style-default"><li class="wp-social-link wp-social-link-twitter wp-block-social-link"><a href="https://twitter.com/hanopcan" class="wp-block-social-link-anchor"><span class="wp-block-social-link-label screen-reader-text">Twitter</span></a></li>

<li class="wp-social-link wp-social-link-linkedin wp-block-social-link"><a href="https://www.linkedin.com/in/hanopcan/" class="wp-block-social-link-anchor"><span class="wp-block-social-link-label screen-reader-text">LinkedIn</span></a></li></ul>
</div></div>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 03 Nov 2022 20:30:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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: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:95:"Do The Woo Community: Supporting WordPress Contributors with Alain Schlesser and Carole Olinger";s: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=73341";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:66:"https://dothewoo.io/supporting-wordpress-open-source-contributors/";s: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:448:"<p>We discuss how the ecosystem can support those who contribute to WordPress and ideas on how to grow this into something sustainable.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/supporting-wordpress-open-source-contributors/">Supporting WordPress Contributors with Alain Schlesser and Carole Olinger</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, 03 Nov 2022 09:02: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: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:110:"WPTavern: #49 – Matt Cromwell on the Effectiveness of the WordPress.org Repository for Promoting New Plugins";s: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=138983";s: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:124:"https://wptavern.com/podcast/49-matt-cromwell-on-the-effectiveness-of-the-wordpress-org-repository-for-promoting-new-plugins";s: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:44500:"Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My Is Nathan Wrigley.</p>



<p>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, the effectiveness of the wordpress.org repository for promoting new plugins.</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 that URL into most podcast players.</p>



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



<p>So on the podcast today, we have Matt Cromwell. Matt is Senior Director of Operations and Marketing at StellarWP, where he provides marketing and business insights and coaching to burgeoning WordPress product owners. He&#8217;s also one of the founders of GiveWP, a donation plugin, which uses the freemium model. Having a free version on wordpress.org&#8217;s repository as well as a paid premium offering.</p>



<p>The wordpress.org repository is where you find yourself when you click the add new button in the WP admin. It&#8217;s a place where plugin developers can, if they follow the guidelines, hosts to their plugins. It provides a direct line of access to all WordPress websites, and is therefore a convenient, free place to host your plugin.</p>



<p>In return, the plugins in the repository must be freely available by the plugin authors. In the past few weeks, the repository has been in the news. Some statistics were unexpectedly removed, and this has led to a conversation about the governance of the repository, as well as questions about whether or not the repository is still a worthwhile place to offer your free plugins, if you have a premium tier.</p>



<p>Alex Denning wrote a post entitled, &#8220;WordPress.org is ineffective for plugin distribution in 2022&#8221;, in which he lays out his thoughts as to why he no longer recommends the WordPress repository. The battle against already successful plugins, low conversion rates, and the difficulty in gaining visibility are amongst the arguments that he puts forward.</p>



<p>Shortly after Alex&#8217;s post was published, Matt Cromwell posted a rebuttal entitled, &#8220;The case for the WordPress freemium model&#8221;. And this is the basis of the podcast today.</p>



<p>We talk about Matt&#8217;s history in WordPress as a premium plugin owner and how his experience leads him to conclude differently. That the WordPress repository can be successful, given the right expectations and approach. He&#8217;s found using the repository to be an effective channel to drive the plugins premium tier, as well as a way of offering a useful free donation tool to the community.</p>



<p>It&#8217;s a fascinating chat and is sure to be of interest to anyone thinking about starting a freemium plugin.</p>



<p>If you&#8217;re interested in finding out more, you can find all of the links in the show notes by heading over to WPTavern.com forward slash podcast. Where you&#8217;ll find all of the other episodes as well. And so, without further delay, I bring you Matt Cromwell.</p>



<p>I am joined on the podcast today by Matt Cromwell. Hello, Matt.</p>



<p>[00:04:19] <strong>Matt Cromwell:</strong> Hi, thanks for having me.</p>



<p>[00:04:20] <strong>Nathan Wrigley:</strong> You&#8217;re very welcome. We&#8217;ve got a, an interesting subject today, all about the wordpress.org ecosystem and whether or not it would be sensible or otherwise to put your free plugin over there. Before we get stuck into that debate, though properly, anybody that is unfamiliar with Matt, let&#8217;s give him an opportunity to introduce himself. So, Matt, just give us a few moments of your time to tell us who you are, what your relationship is with WordPress, what you&#8217;ve done in the past in the WordPress space.</p>



<p>[00:04:47] <strong>Matt Cromwell:</strong> Sure. I&#8217;ve been in WordPress for a while. I would say about 2012 or so. Jumped in and started building websites with WordPress, mostly helping non-profit organizations, churches, educational institutions. Then ended up partnering up with my longtime business partner, Devin Walker, and he and I decided to tackle a big problem in WordPress, which at that time was how to take online donations.</p>



<p>And so we created a plugin called GiveWP, and that was launched in 2015. That has catapulted us into our career, and has done really well and we&#8217;re really proud of it. So much so that we sold it last year to uh, Liquid Web, which is where we are now in the StellarWP brands. There, we have also just recently been asked to uh, take on a bit more. And so now Devin and I are both managing GiveWP as well as iThemes, Iconic and Kadence WP. So things keep getting more and more exciting.</p>



<p>[00:05:44] <strong>Nathan Wrigley:</strong> Thank you very much. Yeah, really broad and rich history there. We could have spent the podcast talking about those products, but we&#8217;re not going to. Well, I think we might do tangentially as a way of demonstrating different things. But we&#8217;re on the podcast today to talk about a couple of pieces which came out.</p>



<p>I will link correctly to both of the pieces that we&#8217;re in discussions about today. But I&#8217;ll mention them both in turn so that those listening to the podcast could possibly have a quick read of them before they pursue any further. So the first one was produced on the 18th of October by Alex Denning over at getellipsis.com, and that piece was called wordpress.org is ineffective for plugin distribution in 2022.</p>



<p>And then a few days after that, you, Matt Cromwell, wrote a piece and that was at mattcromwell.com and it was called the case for the WordPress plugin freemium model. And in effect, your piece coming a little bit later was a rebuttal about what Alex was saying. Now, if you&#8217;d like to outline what Alex is saying, you are welcome to do that. Alternatively, I could try and outline what Alex was saying, which would you prefer?</p>



<p>[00:06:54] <strong>Matt Cromwell:</strong> I think you are much more fair than I.</p>



<p>[00:06:56] <strong>Nathan Wrigley:</strong> Okay, that&#8217;s very kind of you. The long and the short of Alex&#8217;s piece is that he believes that by the year 2022, we&#8217;ve got to a point where, if you are going to be releasing a plugin, a free plugin, into the WordPress space, he believes that it&#8217;s now no longer effective to do that on wordpress.org. The article is probably about a 10 or 15 minute read, and as always with Alex&#8217;s pieces, there&#8217;s lots and lots of data and so on to back it up. But essentially he believes it&#8217;s ineffective for a variety of reasons.</p>



<p>One of them is that the marketplace seems to be dominated, in his view, by some giant incumbents. We&#8217;ve all seen those plugins before. If you&#8217;ve tried to add a new plugin through the WordPress repository, you&#8217;ll probably know the plugins that we&#8217;re talking about. They always rise to the top. And that&#8217;s largely because, Alex thinks, because of the install base that they&#8217;ve already got. Once they&#8217;ve got over a certain amount, the hump of a 100,000, 500,000 or 1,000,000 installs, then it becomes more likely that they&#8217;re going to be surfaced.</p>



<p>There&#8217;s also the idea that, in the recent past, especially since 2016, he makes the point, it&#8217;s much more difficult for new plugins to breach that number. So getting past a hundred thousand and so on is more difficult, which is compounding the problem.</p>



<p>And then if you add on to that, the fact that the search functionality within the WordPress repository also doesn&#8217;t give the opportunity for new plugins to be discovered. If you go there and you search for particular keywords, his contention would be that it&#8217;s much more likely that the ones with the greater install base are going to be surfaced first. In other words, it&#8217;s a bit of a, an echo chamber, I suppose, in a sense is what he&#8217;s saying.</p>



<p>Given all of that, he contends that you would be better off spending your time, and I guess for time you could read money as well, elsewhere. It might be better to have social campaigns or Google ads or some other channel of distribution, outside of wordpress.org, and so your endeavors would be better served elsewhere.</p>



<p>Alex I hope that I&#8217;ve summed that up correctly. If I&#8217;ve not, pleased do get in touch and let me know where I&#8217;ve mistaken things and I will gladly amend the show notes as such. But that, broadly speaking, is Alex&#8217;s contention. And, a day or so later compelled you to write a rebuttal. Just tell us what your thoughts are.</p>



<p>[00:09:26] <strong>Matt Cromwell:</strong> Yeah. Generally speaking I gave some good caveats in my piece that Alex does know what he&#8217;s talking about, and he has a lot of data to back up his conclusions, and I still believe that strongly um, he has reasons for saying what he says. What compelled me to write a rebuttal were essentially a couple claims that I felt were potentially not as helpful for the WordPress ecosystem.</p>



<p>In particular, one thing I think that&#8217;s important of what he&#8217;s saying is that, he says essentially that if you&#8217;re serious about your business and you want to build plugins then you should do premium only, and not a freemium model. Like basically do not build a free plugin, build a premium only plugin. And I really do believe that is damaging to the WordPress ecosystem overall.</p>



<p>If we start to see an influx of premium only offerings it can be really harder for the common user because, we all know it doesn&#8217;t take one plugin to build your website. It often takes a dozen, or several dozen plugins to build your website. And if you have to go, and be purchasing them across the web all over the place, it suddenly makes WordPress not as optimal to deal with.</p>



<p>So that&#8217;s one of the big downsides of his argument that makes me say, ah, I think this needs a lot more context and I think it needs somebody to say, no, the freemium model still works. And then I spend the rest of the article really talking about how I do see that the freemium model does still work and specifically that .org, while the active install count is significant, it&#8217;s not the only factor, and it is still possible for newer plugins to get adoption on wordpress.org. It just takes some savvy for sure. It&#8217;s not as easy as it used to be. I&#8217;ll give him that for sure. It&#8217;s not a situation anymore where if you build it, they will come. So yeah, the long and the short of it.</p>



<p>[00:11:18] <strong>Nathan Wrigley:</strong> So, one of your contentions is that it&#8217;s damaging to the WordPress ecosystem, if in effect there was only paid for plugins and everything that you wished to have on your website was a paid for plugin. I&#8217;m guessing that over the years you&#8217;ve built websites in which you have utilized free plugins? And some of them may be broad in scope, but some of them may just achieve a couple of smaller things.</p>



<p>And, there&#8217;s something to be said about that, isn&#8217;t there? I guess there is something about the community and about the ecosystem, about the expectations of what you are getting into when you install WordPress, which has this free model to it. I guess that&#8217;s an important component of the community and it would in a sense be a shame if the only things that you could have were paid for.</p>



<p>I remember the day, probably going back about 15 or so years ago, when I was looking around for different models for CMSs that I was going to begin using, and there were a variety of them. And there was Drupal and there was Joomla. But if memory serves, there was one called Expression Engine. I could have got the name wrong there. And it seemed to have a very low install base.</p>



<p>And my perception of that was that was because it took that model, it had the model of, you had to pay for not only the CMS but I think all of the different component parts that you could bolt onto the top of it, AKA plugins, and perhaps that was something that stifled its growth. And if we look back at WordPress, perhaps the free plugin model is one of the big factors of its success?</p>



<p>[00:12:47] <strong>Matt Cromwell:</strong> For sure. Absolutely. I mean, for us with GiveWP and I think many people could think, whenever I say GiveWP, you can also think similarly of WooCommerce, quite honestly. It&#8217;s really important to us that GiveWP is free, because a lot of non, all non-profits basically start from zero in many ways. And they are always very conscious about their expenses. And they&#8217;re in the fundraising space. There are so many dozens and dozens of paid fundraising platforms and they are oftentimes very expensive. So having a free option for folks to be able to start fundraising with, and do it successfully and effectively is really important.</p>



<p>And I say similar to WooCommerce because it is similar, like a lot of small businesses start from zero, and they can&#8217;t afford to be paying for a whole bunch of different plugins, just in order to sell their stuff online. I do worry a little bit on the WooCommerce side that their plugin ecosystem has gotten so large that sometimes it feels like it&#8217;s harder to start a shop with just WooCommerce free. And I wish they might put a little bit more features into the free plugin. But that&#8217;s a whole nother podcast.</p>



<p>[00:13:59] <strong>Nathan Wrigley:</strong> Okay. Let&#8217;s take a couple of different pieces of the wordpress.org repo. One of the first things that Alex talks about is the opportunity is quite low according to his data for converting people over. So let&#8217;s say in the case of GiveWP, he doesn&#8217;t cite GiveWP, let&#8217;s be clear. He talks about other different plugins and you can verify that by looking at the article. His contention is that really the conversion rate from the free plugin, if people install your free plugin, it&#8217;s somewhere between one and 3% of those people will be interested enough to go and explore and look for your, your website or whatever channel it is that you&#8217;ve got for getting the paid version.</p>



<p>So, between one and 3% of your users, and therefore that&#8217;s seems like a fairly small figure. And so the cost in terms of the support that you&#8217;d have to give on .org, and also the fact that you&#8217;re having to update it and maintain two different versions with different features. If it&#8217;s only one or two or 3% that are converting, that does seem to be relatively small, but your experience is clearly different.</p>



<p>[00:15:04] <strong>Matt Cromwell:</strong> Yeah, for sure. Now Alex definitely when he was trying to say which plugins have the benefit of being preferred on the plugin directory search. I do think that he would put Give in the category of kind of an elite plugin. Because he did say plugins with a hundred thousand installs or more that have been there for a long time have this elite status, and it&#8217;s hard to compete with them. And we do have over a hundred thousand installs. We&#8217;ve been there for seven years now. So I think he doesn&#8217;t put us in the same category. But nevertheless, I can say authoritatively that we are converting closer to 28% of our install count to paid customers.</p>



<p>I also gave some data on a newer plugin called Orderable that I&#8217;m also involved with on the Stellar side that just launched last summer. And honestly, it&#8217;s a low estimation honestly. If I really look at everyone who&#8217;s paid for anything with Orderable, it is closer to the 30%. But right now, in terms of active customers, it&#8217;s around 18%. So it&#8217;s converting much higher than one to 2%, or one to 3%. But even if you take that one to 3%, and you think about these large plugins like Elementor or whatnot that have 5 million active installs that&#8217;s 50,000 customers. And that&#8217;s significant regardless.</p>



<p>[00:16:21] <strong>Nathan Wrigley:</strong> Yeah, I wonder what could account for the difference there, because Alex is one, two or 3% which may very well be the case in certain given niches, or given the data that he was talking about. I wonder how we account for the big ocean really between your 28, 30%, whatever it may be, and that much smaller percentage? Perhaps it&#8217;s something to do with the nature of the plugin itself, what it&#8217;s doing, what problem it&#8217;s trying to solve, and whether it&#8217;s more desirable. I don&#8217;t really know. It&#8217;s interesting.</p>



<p>[00:16:52] <strong>Matt Cromwell:</strong> Yeah, it is interesting and I, I do want to get some data from Alex on the specific freemium plugins that he&#8217;s worked on, on that, in that way. I do believe that Vova at Freemius probably has additional data that he might share about this subject as well. I believe that on average plugins that use Freemius convert higher than that 3% as well.</p>



<p>And that one I think is another significant data point to keep in mind. But I know from, I, I know Alex and I adore him, he&#8217;s great. And if I&#8217;m thinking the most optimistically about his perspective, I think it&#8217;s more that he would really expect conversion rates to be at least 5% or higher because that&#8217;s what he can get with organic results. That&#8217;s what he can get with CPC ads most likely. He just knows marketing from a larger perspective and really is expecting a lot more. So, if I&#8217;m trying to be generous that&#8217;s what I would think.</p>



<p>[00:17:44] <strong>Nathan Wrigley:</strong> I wonder if there is something in that, maybe your company Give, in this case that we&#8217;re talking about is unusually effective. So your 27%, 28%, whatever it may be is not the normal. Which is obviously very good for the way that you&#8217;ve done marketing and way that you&#8217;ve pitched yourself into the repo.</p>



<p>I&#8217;m curious, and it may be something that you don&#8217;t know the answer to, what would have been the rate? Given the install base that you&#8217;ve got. So you mentioned that there&#8217;s over a hundred thousand and you may not wish to share the numbers, which is fine. What percentage would have been effective to you? In other words, if it had have been at one or 2%, could you have made the plugin viable or did it need to creep into the 10 and 15% kind of area?</p>



<p>[00:18:30] <strong>Matt Cromwell:</strong> Mm-hmm. Well, we did have other plugins at the time, freemium plugins. And truth be told, I was not analyzing their conversion rates very specifically at that time. We had a bunch of business reviews plugins. We had a really fun plugin called Maps Builder that had a free and a pro version. And my guess would be that the conversion rates at that time for those plugins were probably also a lot lower than the 27%.</p>



<p>But they were viable. So I would just be guessing, I don&#8217;t want to just guess, but I do feel like they would probably be in the single digits in terms of conversion numbers. And at the end of the day, yeah, we did retire those for the most part. The business reviews ones are still out there, but we&#8217;ve made a premium product to kind of replace those. And it&#8217;s because of the success of GiveWP. So even if I look at our own plugins that we&#8217;ve built, we did make choices to sunset products because they weren&#8217;t converting as well. So it&#8217;s not as if I don&#8217;t hear Alex, on his side of things because I have some of that same experience. I just don&#8217;t think the conclusion is that means that .org is not viable. I do think it&#8217;s more of a product fit type of conversation, a marketing conversation, and things like that.</p>



<p>[00:19:38] <strong>Nathan Wrigley:</strong> Just taking a bit of an aside here for a moment. Everything that goes into the .org repository is by nature, it&#8217;s free. You can download it and anybody can access it at any time. I&#8217;m curious, you may have opinions on this, you may not. If you have a commercial variant of the plugin, so you&#8217;ve got two sides of the coin. You&#8217;ve got the free .org side, and the paid for, wherever you may put that, but you&#8217;ve got a paid for version somewhere else. What is the true intent of the free version? Because I could look at it cynically and say, okay, the free version is basically a channel for trying to sweep people towards the paid version.</p>



<p>And then with a less cynical hat, I could be, it&#8217;s offering the kind of functionality that we can support for free. In other words, we&#8217;re doing an altruistic thing, for the community for free, completely for free, with no expectation. Maybe it&#8217;s one side or the other, or maybe it&#8217;s a little bit of both. You&#8217;re being altruistic. You&#8217;re giving away certain set of features and range of options with the hope that some of them will come across. But no expectation, you know, it&#8217;s fine if you want to use the free version forever. As a plugin developer who&#8217;s been in the game for a long time, I wonder which side of the fence you sit on, or perhaps you literally do sit on the fence there.</p>



<p>[00:20:54] <strong>Matt Cromwell:</strong> Yeah, I mean the way that things like this work is essentially that at a certain stage, once you start to get enough users, it&#8217;s going to incur costs, just to have users. So specifically when you&#8217;re doing a plugin, like GiveWP or like WooCommerce that is so foundational to the functionality of a website and so important to that website, it&#8217;s going to start to incur costs. And that is human costs. That&#8217;s in the form of technical support for the most part. And account services. Because the users are going to need support. They&#8217;re gonna want support. And in order to fund that support, we do have to have some sort of funding in one way or another.</p>



<p>So doing the free plugin specifically is in order to serve that niche, in order to serve that functionality with the intention then that we&#8217;re gonna need to fund this in one way or another, and we&#8217;re gonna do that with premium features essentially. But it, it&#8217;s always been our strong conviction that the free plugin needs to be very full featured. That you need to be able to do effective fundraising with it out of the box. Or else folks don&#8217;t know what they&#8217;re getting into when they go to pay for something. So essentially it&#8217;s not just a funnel, which in some ways I think that&#8217;s a little bit of the take that Alex is leaning on, is that is looking at .org as one of your marketing funnels.</p>



<p>Which it is, of course. But it also represents your best foot forward of what your product is supposed to be, and what it&#8217;s supposed to offer. And in business there&#8217;s very often this idea of try before you buy, or there&#8217;s a free trial type of thing. With plugins we can&#8217;t do try before you buy really, and you can&#8217;t do free trials really, so your best option is to provide a free product that then leads to paid products. Am I answering your question?</p>



<p>[00:22:41] <strong>Nathan Wrigley:</strong> Yeah. That&#8217;s good. I know it&#8217;s a difficult tight rope to walk that one because, there isn&#8217;t really a correct answer, is there? It clearly has to be a little bit of a marketing channel. You are offering something in the hope of sweeping up a few of them. But equally, you are offering something in the hope that they&#8217;ll enjoy it and experience it and in many cases the functionality that&#8217;s there is sufficient. But should you wish more functionality, here&#8217;s the option.</p>



<p>It&#8217;s an interesting thing as well that in the community, the whole promotional piece on the .org side is, I think, widely viewed with disdain. That is to say it doesn&#8217;t take much for a plugin author to completely derail their plugin if they abuse the UI that they&#8217;ve got for their plugin. I&#8217;m thinking here of examples in the past where companies have taken the opportunity to fill up portions of the screen with advertising for the paid version and so on.</p>



<p>So, we can see that the community really do feel quite strongly about this. From the plugin side, obviously, the author&#8217;s side, you wish to promote your own products because you want to stay in business. From the user&#8217;s side, there seems to be a groundswell of people who think that the repository version needs to be completely without any upsell features. It&#8217;s just, if it&#8217;s good enough, we&#8217;ll figure that out for ourselves and we&#8217;ll go and discover it for ourselves.</p>



<p>In terms of discovery, let&#8217;s just move back to the piece that you wrote. One of the contentions that Alex has was that being discovered inside of the repository is increasingly difficult. The big incumbents of which you&#8217;ve described GiveWP perhaps is one of them, but we know the names of all the other ones. They dominate the search because of their active install counts, and Alex maintains that that&#8217;s a very important metric. In other words, if you go into the repository and begin a search, it&#8217;s quite likely that the results will skew towards the larger active install count plugins. Therefore, it&#8217;s going to be difficult to break through the ceiling of that, no matter how unique and brilliant your plugin is, just because it&#8217;s difficult to launch something and it takes a lot of time. You have, specifically on that point, your rebuttal is interesting. What did you say there?</p>



<p>[00:24:52] <strong>Matt Cromwell:</strong> Yeah, the active install count is a factor, and the plugin directory has gotten larger. But the active install count is one factor of many of the way in which the plugin search works. And luckily when you&#8217;re working with a open source platform like WordPress, all of the code that creates that search is open source as well.</p>



<p>So folks can take a look at it and see exactly the way that the algorithm works, in complete contrast to Google, for example, where it&#8217;s a big black box and nobody really knows how it works exactly. But .org is actually pretty straightforward and relatively simple. But there are a lot of metrics that they take into account when they create that search. And honestly the title of the plugin is actually one of the more significant ones.</p>



<p>Now that being said, if you are, if in your title of your plugin you wanna say something like Wrigley page builder. Page builder is a very flooded field. Things like Elementor and Beaver Builder and others do have a lot more installs already and they&#8217;re going to show up higher if they also have page builder in their title than Wrigley will.</p>



<p>But that doesn&#8217;t mean that you aren&#8217;t found or aren&#8217;t discovered. You might not be first. You might not be second, but you still have a really good chance of being on page one. Because there&#8217;s really not that many page builders on .org currently. So there&#8217;s still a lot of room overall. That&#8217;s kind of my biggest contention, is simply that the way the search works is more complicated than just simply the active install count. It&#8217;s also these specific tags that you use. It&#8217;s also the way in which you describe the type of functionality you have. Whether or not you have good support is even a factor. Like answering all of your .org tickets and things like that. Those all factor in. How recently you&#8217;ve updated the plugin factors in. There&#8217;s a lot of factors involved.</p>



<p>[00:26:38] <strong>Nathan Wrigley:</strong> So you specifically mentioned the following things, which are thrown into the mix when you do a search. So it would be the title of the plugin, the excerpt, the description, the tags, the slug author name, contributor names, last time it was updated, compatibility with core versions, number of active installs, percentage of support tickets resolved, which is really an interesting one, and the average star rating as well.</p>



<p>So there are quite a few things in there. I guess in a sense, having that knowledge could lead you to be quite sophisticated in gaming that system, and it&#8217;s no different really than something like Google where people spend, I would imagine very large amounts of money in some cases, really manicuring their SEO, but without that insight.</p>



<p>And they may succeed one day, they may succeed another day. The point being, they still need to jump through hoops. It&#8217;s not You go over to Google and suddenly you are a winner. You would still have to spend large amounts of time and money organically to break through the surface against, say, for example, other page builders. I presume the problem would be equal over there than it would be on .org.</p>



<p>[00:27:49] <strong>Matt Cromwell:</strong> Yeah, absolutely. And in this way I think what Alex is speaking to a bit is that, in the past with the plugin directory, it really was easier. It really was a lot easier to simply launch your plugin on .org and you would get found in the WP admin relatively easily. And those days are definitely not there anymore. It&#8217;s not quite as easy as it used to be at all. But I don&#8217;t believe that it means that .org is now no longer viable as a distribution option, or even as a marketing or business option.</p>



<p>[00:28:21] <strong>Nathan Wrigley:</strong> Do you believe that the search algorithm in .org, despite the fact that it&#8217;s going through these whole slew of different things, and I&#8217;m guessing that if you read the code, you can see how the waiting would be and so on and so forth. But, do you believe that the search functionality does need a tweak?</p>



<p>Are there other metrics which you would like to see thrown in? Or, indeed just different areas of the UI which may give a small but potentially important boost to newcomers, in a way that perhaps the current search wouldn&#8217;t? And, I think Alex mentions something like rising stars as an option. The idea that plugins, which are new, potentially, they&#8217;ve gone from zero to 50 in a matter of days. That&#8217;s, on WordPress, that&#8217;s a big leap if you go from nothing to 50 or a hundred in a short period of time, that&#8217;s really quite something. And so maybe there&#8217;s parts of the UI where compliments of that nature could improve visibility.</p>



<p>[00:29:14] <strong>Matt Cromwell:</strong> Absolutely, there&#8217;s always room for improvement when it comes to search algorithms, because they are highly complex systems, and they are so significant. In some ways though, I think, just even if the search algorithm itself didn&#8217;t change, but we were able to add things like categorization, being able to navigate down the directory through categories first and then search. That might be a big advantage right away.</p>



<p>Especially if one of those categories was, new. Something that was recently launched. There&#8217;s actually a really fun free plugin, I think it&#8217;s just called New Plugins, I&#8217;ll have to look it up. I&#8217;ll send you the link. But you can install this plugin in your website, and what it does is it adds, when you go to plugins, add new, there&#8217;s tabs in there that says featured and things like that. It&#8217;ll add a new tab, and it&#8217;ll just show you the newest plugins on the directory. And I think that&#8217;s really cool and I&#8217;d love to see that on .org directly.</p>



<p>[00:30:09] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;s really interesting. You also point out that the, gaming is the wrong word, but you make the point that it is still possible given the way that the search is carried out and the results that are shown, that, as an example, some of your competitors, they seem to have optimized with use of their plugin name or the other things that we mentioned, you know, excerpts and description, tags and so on. They&#8217;ve managed to vault over you in the .org search results, because they&#8217;ve optimized for words, which are well, really important to you, but you haven&#8217;t specifically optimized for those.</p>



<p>So for example, nobody could deny that your plugin GiveWP is to do with fundraising, and yet fundraise as a particular word, you are outcompeted on the marketplace there. And also crowdfunding, which again would be an important part of what it is that you do. Both of those words, you quickly discovered you were not winning, and in some cases you didn&#8217;t even appear in the search results on the first page, despite the fact that GiveWP is really, that is inside your wheelhouse without a doubt.</p>



<p>And so there is opportunity, I guess it&#8217;s more of a sort of long tail search. You&#8217;ve just got to find what those opportunities are. Unfortunately, I guess we don&#8217;t have the sort of metrics that we have with things like Google Ads and so on and so forth, where you can see what people have been searching for over, over a period of time, in a particular geography, given different demographics and so on. You just have to do the grunt work of figuring all this stuff out.</p>



<p>[00:31:35] <strong>Matt Cromwell:</strong> Yeah. One other point related to that, that I pointed out is that your presence on .org isn&#8217;t only about the .org plugin search. It&#8217;s also about Google search because those pages all get found on Google as well. And so because we do have insights from search console and Google Ads and things like that, that does influence the terms that we want to be found with as well.</p>



<p>So it&#8217;s not only about figuring out how .org prioritizes plugins, but also what is going to get found on Google as well, because it&#8217;s really hard for any WordPress plugin to beat the domain authority of wordpress.org. If you build a plugin they most likely are going to be on the first page of Google before you are.</p>



<p>[00:32:17] <strong>Nathan Wrigley:</strong> So the contention there is that the .org repo is kind of doing double duty. It&#8217;s obviously offering your plugin up, should it be found, to people trying to add a new plugin. But also Google itself is scraping the.org repo and surfacing in its own search results. So if people are looking for the same kind of thing over on Google, they may very well be pointed towards your .org page. Have I summarised that correctly?</p>



<p>[00:32:43] <strong>Matt Cromwell:</strong> Yep, absolutely. In this way .org is just a marketplace in many ways. It&#8217;s a public marketplace for folks to find free plugins.</p>



<p>[00:32:50] <strong>Nathan Wrigley:</strong> I do wonder if the algorithm which is running behind Google, obviously complex and probably, took billions of dollars over time to be put together and is very sophisticated. But it&#8217;s not quite such a blunt instrument, is it? It&#8217;s not just taking data from a series of tags and descriptions and metatags and so on. There&#8217;s a lot going on. So for example, if I search for fundraise, Google is probably clever enough to figure out hang on a minute, fundraise is a sort of synonym for crowdfunding. It&#8217;s a synonym for donations and so on. So, we&#8217;ll highlight those results as well. So in, in many ways, it&#8217;s a little bit more sophisticated, and maybe the .org search could have some of that goodness thrown into it in the future. Albeit not with the same budget that Google clearly has.</p>



<p>[00:33:36] <strong>Matt Cromwell:</strong> Yeah, absolutely. That&#8217;s also a real reason why if you do have a free plugin on .org, it&#8217;s really good to make sure that you have folks who actually link to that plugin on .org. Not only linking to your website itself but to your free plugin on .org. Because then Google will pick up, oh, when folks are looking for fundraise plugin, they actually are looking for this Give thing, that might not rank as well on .org, but it is gonna rank great on Google, because Google does figure that out.</p>



<p>[00:34:04] <strong>Nathan Wrigley:</strong> We haven&#8217;t really strayed into this subject, but I&#8217;m wondering if you&#8217;ve had any experience with alternative marketplaces. The only one that really comes into my mind is Envato. Where for many years they&#8217;ve had a kind of rival plugin marketplace. I really haven&#8217;t been looking at how successful that&#8217;s been going, many years since I last visited it. But the option for plugin developers to sort of, corral together and have a completely different space. But it feels to me that in the end, potentially you just end up with the same problem, but in a third party marketplace.</p>



<p>[00:34:36] <strong>Matt Cromwell:</strong> Yeah, and that third party marketplace has very strong priorities around the way it wants to be paid, and the types of products it wants to be highlighting. They are far more opinionated about the way all of the products there are found and discovered. And it is really for the, the bottom line of Envato.</p>



<p>And I think, honestly, that&#8217;s one thing that&#8217;s a bit of an untapped conversation is the significance of having what is essentially a marketplace being owned by a non-profit organization, like the WP Foundation. I do think that&#8217;s a significant conversation and the more folks need to be having and recognize that we&#8217;re not just really all fighting for attention from a LLC or some giant corporation. We&#8217;re really trying to contribute together on a public project that should be primarily influenced by a non-profit organization instead.</p>



<p>[00:35:29] <strong>Nathan Wrigley:</strong> I guess the long and the short of this episode would be, from your perspective, is the Word Press repository perfect? No. Is it useful? Yes. And that perhaps is enough for now. Could it be improved? Another yes, but for now that seems to be, at least for you and your experience, good enough</p>



<p>[00:35:47] <strong>Matt Cromwell:</strong> Absolutely. I think it&#8217;s viable. I think it can be very helpful and beneficial. It doesn&#8217;t have to be your, it shouldn&#8217;t be your only tactic. But it also shouldn&#8217;t be easily ignored either.</p>



<p>[00:35:58] <strong>Nathan Wrigley:</strong> So just to round off the conversation, one final question. How do you view your efforts on the WordPress repository as against all of the other things that you do outside of WordPress. So for example, Google and so on? You may have data to hand, you may not, I don&#8217;t know. But I&#8217;m just wondering if, one is equal to another or if the .org side definitely comes in second place, or perhaps it is the primary channel of your sales funnel.</p>



<p>[00:36:23] <strong>Matt Cromwell:</strong> Because there are different types of freemium models, that answer will be different based on the product owner and the route that they chose. If it&#8217;s a free plugin with a pro version, meaning you have to uninstall the free one in order to install the pro one, their priorities are probably gonna be very different.</p>



<p>But in our case, similar to Woo Commerce, it&#8217;s a core free plugin, and any of the paid add-ons require the free version to be installed. And because of that setup that we have, and WooCommerce has as well, the free plugin is foundational to everything we do. We&#8217;re always improving the free plugin in order for it to be more powerful, more streamlined, and for it to be able to enable us to do more things in the pro add-ons as well.</p>



<p>So being able to really parse it between priorities, it&#8217;s almost impossible. Because for us, the free plugin really encompasses the whole ecosystem of what Give actually does and means for us as a business, and as a product for the users.</p>



<p>[00:37:21] <strong>Nathan Wrigley:</strong> I&#8217;m sure that this will be something which resonates with a lot of people. I don&#8217;t really know which side of the fence the audience will be sitting on, but no doubt there will be some commentary. There&#8217;ll be people wishing to explain their reasoning behind this, one way or another. Please feel free to go to the post on WP Tavern, and leave us some comments there. But for now, thank you so much Matt Cromwell for explaining your position about the WordPress.org repo. I appreciate it.</p>



<p>[00:37:47] <strong>Matt Cromwell:</strong> Absolutely. Thank you so much.</p>
</div>



<p>On the podcast today we have <a href="https://twitter.com/learnwithmattc">Matt Cromwell</a>.</p>



<p>Matt is Senior Director of Operations and Marketing at <a href="https://twitter.com/learnwithmattc">StellarWP</a>, where he provides marketing and business insights and coaching to burgeoning WordPress product owners. He’s also one of the founders of <a href="https://givewp.com/">GiveWP</a>, a donations plugin which uses the freemium model, having a free version on the WordPress.org repository as well as a paid premium offering.</p>



<p>The WordPress.org repository is where you find yourself when you click the ‘add new’ button in the WP admin. It’s a place where plugin developers can, if they follow the guidelines, host their plugins. It provides a direct line of access to all WordPress websites, and is therefore a convenient, free place to host your plugin. In return, the plugins in the repository must be freely available by the plugin authors.</p>



<p>In the past few weeks, the repository has been in the news. Some statistics were unexpectedly removed, and this has led to conversation about the governance of the repository, as well as questions about whether the repository is still a worthwhile place to offer your free plugins, if you have a premium tier.</p>



<p>Alex Denning wrote a post entitled “<a href="https://getellipsis.com/blog/org-is-ineffective-plugin-distribution">WordPress.org is ineffective for plugin distribution in 2022</a>”, in which he lays out his thoughts as to why he no longer recommends the WordPress repository. The battle against already successful plugins, low conversation rates and the difficulty in gaining visibility are amongst the arguments that he puts forward.</p>



<p>Shortly after Alex’s post was published, Matt Cromwell posted a rebuttal entitled “<a href="https://www.mattcromwell.com/the-case-for-the-wordpress-plugin-freemium-model/">The Case for the WordPress Freemium Model</a>”, and this is the basis of the podcast today.</p>



<p>We talk about Matt’s history in WordPress as a premium plugin owner, and how his experience leads him to conclude differently; that the WordPress repository can be successful, given the right expectations and approach. He’s found using the repository to be an effective channel to drive the plugin’s premium tier, as well as a way of offering a useful free donation tool to the community.</p>



<p>It’s a fascinating chat and is sure to interest anyone thinking about starting a freemium plugin.</p>



<h2>Useful links.</h2>



<p><a href="https://getellipsis.com/blog/org-is-ineffective-plugin-distribution">WordPress.org is ineffective for plugin distribution in 2022</a></p>



<p><a href="https://www.mattcromwell.com/the-case-for-the-wordpress-plugin-freemium-model/">The case for the WordPress freemium model</a></p>



<p><a href="https://givewp.com/">GiveWP</a></p>



<p><a href="https://orderable.com/">Orderable</a></p>



<p><a href="https://stellarwp.com/">StellarWP</a></p>



<p><a href="https://wordpress.org/plugins/cubecolour-new-plugins/">Cubecolour New Plugins</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, 03 Nov 2022 08:49: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: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: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:54:"Post Status: WordPress 6.1 • Raghavendra Satish Peri";s: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:32:"https://poststatus.com/?p=142548";s: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:61:"https://poststatus.com/wordpress-6-1-raghavendra-satish-peri/";s: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:15273:"<h2 id="h-this-week-at-wordpress-org-october-31-2022">This Week at WordPress.org (October 31, 2022)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">#WordPress 6.1 was released on November 1. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2728.png" alt="✨" class="wp-smiley" /> Check out all the updated and revised support articles. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f4d6.png" alt="?" class="wp-smiley" /> Learn about #accessibility and contributor Raghavendra Satish Peri from the WordPress India community. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ee-1f1f3.png" alt="??" class="wp-smiley" /> </p></div>


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



<div id="kt-info-box_68609b-a8" class="wp-block-kadence-infobox"><div class="kt-blocks-info-box-link-wrap kt-blocks-info-box-media-align-left kt-info-halign-left"><div class="kt-blocks-info-box-media-container"><div class="kt-blocks-info-box-media kt-info-media-animate-none"><div class="kadence-info-box-icon-container kt-info-icon-animate-none"><div class="kadence-info-box-icon-inner-container"><span class="kt-info-svg-icon kt-info-svg-icon-fe_arrowUpCircle"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title"><a href="https://make.wordpress.org/core/2022/08/10/proposal-stop-merging-experimental-apis-from-gutenberg-to-wordpress-core/">WordPress 6.1 </a>&#8220;Misha&#8221;</h2><p class="kt-blocks-info-box-text"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2b06.png" alt="⬆" class="wp-smiley" /> <a href="https://wordpress.org/news/2022/11/misha/">WordPress 6.1 “Misha”</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/23ea.png" alt="⏪" class="wp-smiley" /> <a href="https://make.wordpress.org/hosting/2022/10/19/call-for-action-testing-rollback-feature/">Call For Action – Testing Rollback Feature</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ee-1f1f3.png" alt="??" class="wp-smiley" /> <a href="https://wordpress.org/news/2022/10/people-of-wordpress-raghavendra-satish-peri/">Raghavendra Satish Peri</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/267b.png" alt="♻" class="wp-smiley" /> <a href="https://make.wordpress.org/project/2022/11/01/sustainability-channel-what-should-we-do/">Call for Comments — What Does Sustainability Mean to You?</a></p></div></div></div>



<h2 id="h-news">News<a href="https://wordpress.org/news/2022/10/wordpress-6-1-release-candidate-3/"></a></h2>



<ul>
<li><a href="https://wordpress.org/news/2022/11/misha/">WordPress 6.1 “Misha”</a></li>



<li><a href="https://wordpress.org/news/2022/10/people-of-wordpress-raghavendra-satish-peri/">People of WordPress: Raghavendra Satish Peri</a></li>



<li><a href="https://wordpress.org/news/2022/10/episode-42-something-spooky-this-way-comes/">WP Briefing: Episode 42: Something Spooky This Way Comes</a></li>
</ul>



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



<div class="is-layout-flex wp-container-13 wp-block-columns">
<div class="is-layout-flow wp-block-column">
<h2 id="h-community">Community</h2>



<ul>
<li><a href="https://make.wordpress.org/community/2022/11/02/recap-of-the-diverse-speaker-training-group-wpdiversity-amer-emea-on-october-26-2022/">Recap of the Diverse Speaker Training group (#WPDiversity) AMER/EMEA on October 26, 2022</a></li>



<li><a href="https://make.wordpress.org/community/2022/10/27/deputy-training-4-wordcamp-process-flow-recap/">Deputy Training #4: WordCamp Process Flow Recap</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2022/11/01/a-week-in-core-october-31-2022/">A Week in Core – October 31, 2022</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/31/wordpress-6-1-release-candidate-6-rc6-now-available-for-testing/">WordPress 6.1 Release Candidate 6 (RC6) Now Available for Testing</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/31/postponed-to-wp-6-2-escaping-table-and-field-names-with-wpdbprepare/">Postponed to WP 6.2: Escaping Table and Field names with <code>wpdb::prepare()</code></a></li>



<li><a href="https://make.wordpress.org/core/2022/10/28/core-editor-improvement-advancing-the-writing-experience/">Core Editor Improvement: Advancing the writing experience</a></li>
</ul>



<h3 id="h-meetings">Meetings</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2022/11/02/dev-chat-agenda-november-2-2022/">Dev Chat agenda, November 2, 2022</a></li>



<li><a href="https://make.wordpress.org/core/2022/11/01/editor-chat-agenda-2-november-2022/">Editor Chat Agenda: 2 November 2022</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/docs/2022/11/02/summary-of-docs-team-meeting-november-1-2022/">Summary of Docs Team Meeting November 1, 2022</a></li>



<li><a href="https://make.wordpress.org/docs/2022/10/28/the-documentation-team-contributor-day-summary/">The Documentation team Contributor Day summary</a></li>
</ul>



<h3 id="h-support-articles"><br />Support Articles</h3>



<ul>
<li><a href="https://wordpress.org/support/article/colors-settings-overview/">Colors Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/layout-settings-overview/">Layout Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/typography-settings-overview/">Typography Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/twenty-twenty-three/">Twenty Twenty-Three</a></li>



<li><a href="https://wordpress.org/support/article/twenty-twenty-three-changelog/">Twenty Twenty-Three Changelog</a></li>



<li><a href="https://wordpress.org/support/article/border-settings-overview/">Border Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/post-author-biography-block/">Post Author Biography Block</a></li>



<li><a href="https://wordpress.org/support/article/comment-template-block/">Comment Template Block</a></li>



<li><a href="https://wordpress.org/support/article/comment-edit-link-block/">Comment Edit Link Block</a></li>



<li><a href="https://wordpress.org/support/article/comment-reply-link-block/">Comment Reply Link Block</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/10/19/call-for-action-testing-rollback-feature/">Call For Action – Testing Rollback Feature</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/marketing/2022/11/02/agenda-wordpress-global-marketing-team-meeting-november-2-2022/">Agenda: WordPress global Marketing Team meeting, November 2, 2022</a></li>



<li><a href="https://make.wordpress.org/marketing/2022/11/01/notes-global-marketing-team-meeting-october-26-2022/">Notes: Global Marketing Team meeting, October 26, 2022</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/10/21/wordpress-org-redesign-update/">WordPress.org Redesign Update</a></li>



<li><a href="https://make.wordpress.org/meta/2022/10/20/displaying-style-variations-for-supporting-themes/">Displaying Style Variations for Supporting Themes</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/mobile/2022/11/01/call-for-testing-wordpress-for-android-21-1/">Call for Testing: WordPress for Android 21.1</a></li>



<li><a href="https://make.wordpress.org/mobile/2022/11/01/call-for-testing-wordpress-for-ios-21-1/">Call for Testing: WordPress for iOS 21.1</a></li>



<li><a href="https://make.wordpress.org/updates/2022/11/02/mobile-team-update-november-2nd-2/">Mobile Team Update – November 2nd</a></li>
</ul>
</div>



<div class="is-layout-flow wp-block-column">
<h2 id="h-performance"><a href="https://make.wordpress.org/performance/">Performance</a></h2>



<ul>
<li><a href="https://make.wordpress.org/core/2022/11/01/performance-team-meeting-summary-1-november-2022/">Performance Chat Summary: 1 November 2022</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/10/31/plugin-review-team-31-oct-2022-%F0%9F%91%BB/">Plugin Review Team: 31 Oct 2022&nbsp;</a></li>
</ul>



<h2 id="h-polyglots">Polyglots</h2>



<ul>
<li><a href="https://make.wordpress.org/polyglots/2022/11/02/agenda-weekly-polyglots-chat-nov-2-2022-700-utc/">Agenda: Weekly Polyglots Chat – Nov. 2, 2022 (7:00 UTC)</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/11/01/sustainability-channel-what-should-we-do/">Now we have a sustainability channel in Making WordPress Slack, what should we do?</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/updates/2022/10/27/support-team-meeting-updates-for-october-27/">Support Team Meeting Updates for October 27</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/10/26/hallway-hangout-discussion-on-wrapping-phase-2-26-oct/">Hallway Hangout: Discussion on wrapping Phase 2 (26 Oct)</a></li>



<li><a href="https://make.wordpress.org/updates/2022/10/31/test-team-update-31-october-2022/">Test Team Update: 31 October 2022</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/11/01/themes-team-update-november-01-2022/">Themes team update November 01, 2022</a></li>
</ul>



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



<ul>
<li><a href="https://learn.wordpress.org/individual-learner-survey/">How did you learn WordPress?</a></li>



<li><a href="https://make.wordpress.org/training/2022/11/01/summary-update-courses-currently-in-development-1-november-2022/">Summary Update: Courses Currently in Development or Published (1 November 2022)</a></li>



<li><a href="https://make.wordpress.org/training/2022/10/31/meeting-agenda-for-november-1-2022/">Meeting Agenda for November 1, 2022</a></li>
</ul>



<h3 id="h-tutorials">Tutorials</h3>



<ul>
<li><a href="https://learn.wordpress.org/tutorial/using-block-template-parts-in-classic-themes/">Using Block Template Parts in Classic Themes</a></li>



<li><a href="https://learn.wordpress.org/tutorial/a-beginners-guide-to-the-wordpress-template-hierarchy/">A Beginners Guide to the WordPress Template Hierarchy</a></li>



<li><a href="https://learn.wordpress.org/tutorial/tools-import-and-export/">Tools: Import and Export</a></li>
</ul>



<h3 id="h-online-workshops">Online Workshops</h3>



<ul>
<li><a href="https://learn.wordpress.org/?meeting=the-creative-side-of-blocks-vol-3">The Creative Side of Blocks, Vol. 3</a></li>



<li><a href="https://learn.wordpress.org/?meeting=padding-margin-and-block-spacing">Padding, Margin and Block Spacing</a></li>



<li><a href="https://learn.wordpress.org/?meeting=lets-code-internationalisation-in-block-themes">Let’s code! Internationalisation in Block Themes</a></li>



<li><a href="https://learn.wordpress.org/?meeting=wordpress-development-live-stream-internationalisation">WordPress development live stream: Internationalisation</a></li>
</ul>



<h3 id="h-courses">Courses</h3>



<ul>
<li><a href="https://learn.wordpress.org/course/a-developers-guide-to-block-themes-part-1/">A Developers Guide to Block Themes – Part 1</a></li>
</ul>



<h2 id="h-wptv">WPTV</h2>



<ul>
<li><a href="https://meta.trac.wordpress.org/ticket/1430">WordPress TV videos now auto-published to Youtube</a></li>



<li><a href="https://wordpress.tv/category/year/2022/">Latest WordPress TV videos</a></li>
</ul>
</div>
</div>



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



<h2 id="h-related-news">Related News:</h2>



<ul>
<li><a href="https://tc39.es/#proposals">ECMAScript Proposals</a></li>
</ul>



<p class="has-theme-palette-7-background-color has-background">Thanks for reading our WP dot .org roundup! Each week we are highlighting the news and discussions coming from the good folks making WordPress possible. If you or your company create products or services that use WordPress, you need to be engaged with them and their work. 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/14.0.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/14.0.0/72x72/1f48c.png" alt="?" class="wp-smiley" /></p>



<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/14.0.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/14.0.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/14.0.0/72x72/1f426.png" alt="?" class="wp-smiley" /></p>
</div></div>



<div class="wp-block-spacer"></div>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 03 Nov 2022 02:53:31 +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: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:45:"Post Status: The WordPress Enterprise Paradox";s: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:32:"https://poststatus.com/?p=142360";s: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:56:"https://poststatus.com/the-wordpress-enterprise-paradox/";s: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:13115:"<div class="is-layout-flow wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">&#8220;WordPress as a platform is putting us on the enterprise path. But what got us here is what makes us irrelevant,&#8221; says Magne Ilsaas, CEO and Founding Partner of Dekode. Magne wants to start an overdue conversation about three big risks — and opportunities — for WordPress agencies: 1) A lack of spaces for professional conversations and knowledge-sharing, including professional events, meetups,  and mastermind groups catering to enterprise WordPress. 2) Successful agencies that use WordPress extensively with little or no community involvement whose work would benefit from enterprise WordPress peer networks. 3) An over-emphasis in WordPress agencies on short-term engineering solutions to the exclusion of long-term business solutions. What's often left out is design, user experience, and most of all the capacity to play a strategic advisory role in partnership with clients.  </p></div>


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



<p class="yoast-reading-time__wrapper"><span class="yoast-reading-time__icon"></span><span class="yoast-reading-time__spacer"></span><span class="yoast-reading-time__descriptive-text">Estimated reading time:  </span><span class="yoast-reading-time__reading-time">6</span><span class="yoast-reading-time__time-unit"> minutes</span></p>
</div></div>



<p class="has-drop-cap">As more and more enterprises move onto WordPress and digital becomes the backbone of modern business, we need to become more than developers and designers. We are now business advisors, thinking on behalf of the companies we work for.</p>



<p>Agencies focusing on open source and WordPress are in a pretty good spot these days. Demand for WordPress development has never been higher, and we continue to see bigger companies building their websites on WordPress.&nbsp;</p>



<blockquote><p>Most clients know WordPress may not be the best choice, but they are starting to understand that “best choice” isn’t relevant.&nbsp;</p></blockquote>



<p>At Dekode we are focusing on enterprise clients, and it's really fun when large, interesting projects come our way — because of WordPress. It is a real contrast to how it used to be when most of our client meetings were spent explaining why WordPress is a good choice. Now it's rarely discussed at all. Most clients that come our way have already decided that WordPress is the right choice for them. Even big public tenders call out for WordPress.</p>



<p>Most of them know it's not necessarily the best choice, but they are starting to understand that “best choice” isn’t relevant.&nbsp;</p>



<p>If a client in 2017 set out to choose a CMS and had the slightest idea of what they were doing, they would have a shortlist of three to five CMSs to choose from. The truth is that any of them would have been a good choice, and any of them could be bent into shape to suit the client’s needs.</p>



<div class="is-layout-constrained wp-block-group has-theme-palette-8-background-color has-background"><div class="wp-block-group__inner-container">
<h2 id="h-the-paradox"><strong>The Paradox</strong>:</h2>



<p><strong>WordPress as a platform is putting us on the enterprise path.&nbsp;</strong></p>



<p><strong>But what got us here is what makes us irrelevant.</strong></p>
</div></div>



<h2 id="h-can-we-overcome-success">Can We <strong>Overcome Success</strong>?</h2>



<p>With the traction WordPress has gained over the last 15 years, we see that more and more enterprise companies are opening their eyes to what we can do with WordPress, but too often it’s for the wrong reasons.&nbsp;</p>



<p>For large parts of the WordPress industry, plugins, themes, and soon-to-be <em>Gutenblocks</em> are the fuel that keeps the WordPress snowball rolling. SMBs spinning up WordPress websites on the fly.&nbsp; The platform is really great at this because it's so easy and flexible. It's a Swiss Army Knife on steroids, able to adapt to anyone's needs.&nbsp;</p>



<blockquote><p>Some of the best WordPress projects are done by agencies that don’t really care about WordPress or the WordPress community. </p></blockquote>



<p>But here is the paradox: this success is holding us back now because the thousands of plugins and DIY articles and solutions generally aren’t meant or relevant for the enterprise market. This means that a lot of enterprise companies are building patchwork WordPress installations that may or may not scale, be secure, or actually work as a modern digital tool for solving business needs.&nbsp; As we build more and more functionality and options, we are strolling farther and farther away from the enterprise playing field.</p>



<p>Some of the best WordPress projects are done by agencies that don’t really care about WordPress or the WordPress community. Why? Because they use WordPress for what it is. A tool that gets the job done, cheaply and effectively. But as the web gets more and more complex, some of these agencies don't have the people with the necessary skills, and we are seeing more high-profile enterprise clients with low-quality WordPress websites.</p>



<p>So we are putting ourselves in a pretty bad position at the moment.&nbsp;</p>



<p>With the rising demand for WordPress experts, everything should be great. But the fact is that there are too many high-profile websites out there with really poor-quality work under the hood. And the reputation WordPress has as an alternative for enterprise will deteriorate as these solutions fall apart piece by piece.</p>



<blockquote><p>Do we actually solve someone's business goal or a user's need? Mileage varies — a lot.</p></blockquote>



<p>Even though we are busy discussing our tool and what it can and cannot do, some WordPress enterprise projects actually do end up with a skillful WordPress agency. But all too often, the decision of what CMS to build on is made after a lot of the important strategic decisions are made—or even after the design is done.</p>



<p>Too often other agencies are helping clients with strategic decision-making, design and communication, user testing,&nbsp; conversion optimization, and digital marketing.</p>



<p>When competing platforms can offer a full spectrum of expertise, it really doesn't matter how good we are as developers. If the solutions we help create don't deliver on basic user needs and business goals, where is the value to the client? But too often we are not in a position to affect quality and business impact. Most of the time we are missing the show by collectively taking ourselves <em>off</em> the playing field.</p>



<h2 id="h-is-wordpress-enterprise-ready"><strong>Is WordPress enterprise ready?</strong></h2>



<p>From a technical perspective, the answer is obviously yes.&nbsp;</p>



<p>From a <em>people</em> perspective, the answer is much less clear: yes and no.</p>



<p>For the enterprise, WordPress is still a pretty risky move. But not because there aren't agencies that can deliver high-quality code, security, and scalability. It's amazing what the best developers can spin up on WordPress, but that doesn't really matter if everyone but the developers understands how they are (or aren’t) delivering a positive user experience and solving the client's business problems.&nbsp;</p>



<blockquote><p>Imagine a way of doing business that is not about redesign loops and short-term decisions but a way to create sustainable digital platforms and deliver long-term value to our clients.</p></blockquote>



<p>Today when we get a project brief, there are no technical reasons why you shouldn't choose WordPress. Subjectively speaking, it's probably the best CMS out there, for many reasons.&nbsp;</p>



<p>But that doesn't mean that it is the right choice for an enterprise business.</p>



<p>There are plenty of examples of enterprise websites that run on WordPress. Technically many of them are flawless, and some even look good, but do they actually solve someone's business goal or a user's need? Mileage varies — a lot.</p>



<h2 id="h-the-secret-sauce"><strong>The Secret Sauce</strong></h2>



<p>Digital is becoming the foundation of modern businesses, and in order to stay relevant, it is not enough to be only designers and developers anymore. We need to develop our skills further and become business designers and long-term digital partners for our clients.</p>



<p>The best solutions can be made when we take our WordPress knowledge and developer skills and use them to create sustainable platforms and design systems that align with business strategy, user needs, and digital marketing.</p>



<p>We need to hold ourselves accountable to a long-term perspective for the decisions we make and the solutions we create. To stay relevant, we need to understand success is the value we deliver — on top of the technology.&nbsp;&nbsp;</p>



<p>There are plenty of WordCamps, seminars, podcasts, blogs, tutorials, and meetups out there.&nbsp;</p>



<blockquote><p>To stay relevant, we need to understand success is the value we deliver — on top of the technology.&nbsp;&nbsp;</p></blockquote>



<p>But what they all have in common is that they are aimed at the mass market side of WordPress where price tags are low and scale is everything. This is fantastic, and it will keep the WordPress snowball rolling.</p>



<p>But why is there no arena for professional conversations around WordPress Enterprise?</p>



<p>Why is there no knowledge sharing about creating value on top of the tools we create?</p>



<p>What if we did business the same way we've built WordPress? What if we leverage our biggest asset, which is not WordPress the tool. It’s WordPress, the community, the culture, the openness, and the inclusiveness. What if we create our own way of integrating our open-source mindset into how we conduct our businesses?</p>



<blockquote><p>We need a WordPress mindset, a WordPress way of doing business, that enables value creation for everyone involved.</p></blockquote>



<p>Imagine a way of doing business that is not about redesign loops and short-term decisions but a way to create sustainable digital platforms and deliver long-term value to our clients.</p>



<p>In my opinion, there are enough strong forces in play to keep WordPress as a platform enterprise-ready and relevant. But I’m not sure that matters without a better understanding and focus on how we can deliver value on top of the tools we create.&nbsp;</p>



<p>My wish is for WordPress to be known as more than the most cost-effective, enterprise-ready technology. I want it to be known for a WordPress mindset, a WordPress way of doing business, that enables value creation for everyone involved.&nbsp;</p>



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



<div class="is-layout-constrained wp-block-group has-theme-palette-7-background-color has-background"><div class="wp-block-group__inner-container">
<h2>Help make it happen! Join <a href="https://poststatus.slack.com/archives/C02TNBDAXLL"><span>#agency-owners</span></a> in Post Status Slack.</h2>



<p>Leave a <a href="https://poststatus.com/planet/feed/#comments">comment</a>, get in touch, or jump into <a href="https://poststatus.slack.com/">Post Status Slack</a> if this is a conversation you'd like to contribute to.</p>
</div></div>



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



<div class="wp-block-media-text is-stacked-on-mobile has-background" id="author"><a href="https://dekode.no/"><img width="752" height="752" src="https://cdn.poststatus.com/wp-content/uploads/2022/11/ab58aa31afffd4af6284f4244b9f61a8-752x752.webp" alt="Magne Ilsaas" class="not-transparent wp-image-142508 size-medium" /></a><div class="wp-block-media-text__content">
<p><strong>Magne Ilsaas</strong> is the founder and manager of <strong><a href="https://dekode.no">Dekode</a></strong>, Norway`s biggest WordPress agency. He works on bridging the gap between design and engineering in order to create the best and most cost-efficient WordPress projects. When he`s not working, you`ll find him skiing or fishing in Lofoten.</p>



<ul class="is-horizontal is-content-justification-center is-layout-flex wp-container-20 wp-block-social-links alignright has-small-icon-size is-style-default"><li class="wp-social-link wp-social-link-twitter wp-block-social-link"><a href="https://twitter.com/dekodeno/" class="wp-block-social-link-anchor"><span class="wp-block-social-link-label screen-reader-text">Twitter</span></a></li>

<li class="wp-social-link wp-social-link-linkedin wp-block-social-link"><a href="https://www.linkedin.com/in/magne-ilsaas-4968b75/" class="wp-block-social-link-anchor"><span class="wp-block-social-link-label screen-reader-text">LinkedIn</span></a></li></ul>
</div></div>



<p></p>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 02 Nov 2022 23:24:56 +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:"Magne Ilsaas";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:61:"WPTavern: WP All Import Is Moving Away from Lifetime Licenses";s: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=139123";s: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://wptavern.com/wp-all-import-is-moving-away-from-lifetime-licenses";s: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:4078:"<p>WP All Import <a href="https://www.wpallimport.com/your-last-chance-to-buy-unlimited-lifetime-licenses/">announced</a> it will soon change its business model to annual licenses. The product, which includes free and commercial versions, allows users to import/export XML, CSV, or Excel data and integrates with more than a dozen popular plugins. Since its founding in 2011, WP All Import has been sold with unlimited, lifetime licenses. The product has more than 12,000 customers.</p>



<p>In a statement published this week, WP All Import explained that the company went with lifetime licenses from the beginning because most commercial plugins were sold this way when they started in 2011 and customers began to expect it. </p>



<p>Some companies have had a rocky transition out of providing lifetime licenses, as the community saw with <a href="https://wptavern.com/delicious-brains-acquires-advanced-custom-fields-plugin">Delicious Brains&#8217; acquisition of ACF</a> in June 2021. Although they assured existing customers that they would honor their lifetime licenses, a few months later on Black Friday, Delicious Brains began <a href="https://wptavern.com/acf-solicits-lifetime-license-holders-for-contributions-urging-them-to-purchase-annual-subscriptions">urging them to purchase annual subscriptions</a>. For many companies transitioning away from old pricing strategies, lifetime license holders become dead weight, requiring support without putting revenue back into the company. WP All Import has found success with offering lifetime licenses for 11 years, but the company is making sure its new customers will be paying every year:</p>



<blockquote class="wp-block-quote">
<p>We are not making this change because because lifetime licenses are inherently unsustainable or support costs are spiraling out of control.</p>



<p>WP All Import is a profitable business, support costs generally follow revenue up and down, and lifetime licenses for WordPress plugins are absolutely a sustainable business model.</p>



<p><strong>We are moving to annual licenses simply because we will make more money.</strong></p>



<p>&#8220;While lifetime licenses work, annual licenses are absolutely more profitable over the long term. This is why you see almost every piece of software on earth now being sold with one.&#8221;</p>
</blockquote>



<p>WP All Import is one of the few remaining companies that is still using a lifetime license pricing strategy. The company noted that over the past ten years, the budgets for WordPress projects have grown along with the quality of their software. </p>



<p>Generally, the response to the news has been positive. Some are considering purchasing lifetime licenses before they are no longer offered. One customer said he appreciated the honest communication but bristled at the notion that &#8220;people just expect to have to renew their software licenses.&#8221; </p>



<p>&#8220;No,&#8221; developer Patrick van Kouteren said. &#8220;It is being forced upon consumers because it generates more revenue for the business selling it.&#8221;</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Well, that's honest from WP All Import. But followed by a bullshit statement: "people just expect to have to renew". No. It is being forced upon consumers because it generates more revenue for the business selling it. <a href="https://t.co/U1p0qy4JJt">pic.twitter.com/U1p0qy4JJt</a></p>&mdash; Patrick van Kouteren (@pvankouteren) <a href="https://twitter.com/pvankouteren/status/1587721931696050182?ref_src=twsrc%5Etfw">November 2, 2022</a></blockquote>
</div>



<p>WP All Import assured existing customers that it will continue to honor their lifetime licenses and offer the same level of support. If the company releases new products in the future, lifetime license holders will be eligible to purchase annual licenses for these products at discounted rates. WP All Import said the company will be making these changes &#8220;sometime later this year or 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:"Wed, 02 Nov 2022 22:07:37 +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: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:116:"WPTavern: WordPress 6.1 Introduces New Default Theme and Fluid Typography, Expands Design Tools and Template Options";s: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=139076";s: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:126:"https://wptavern.com/wordpress-6-1-introduces-new-default-theme-and-fluid-typography-expands-design-tools-and-template-options";s: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:5422:"<p><a href="https://wordpress.org/news/2022/11/misha/">WordPress 6.1 &#8220;Misha&#8221;</a> was released today, named for Soviet-Norwegian jazz pianist <a href="https://en.wikipedia.org/wiki/Mikhail_Alperin">Mikhail “Misha” Alperin</a>, who was born in Ukraine in 1956. A founding member of the first Moldavian jazz quartet, and later the <a href="https://en.wikipedia.org/wiki/Moscow_Art_Trio">Moscow Art Trio</a>, Alperin became known for his distinct and bewitching blend of jazz and folk music.</p>



<p>This release is the culmination of a months-long effort to <a href="https://github.com/WordPress/gutenberg/issues/43241">improve the design tooling consistency</a> of WordPress&#8217; core blocks. That means blocks that were missing things like typography, color, and border support have been updated wherever possible to match the support included in other blocks. Design tools and their controls are also now more consistently presented, so users can intuitively know what to expect when customizing their blocks.</p>



<img />image credit: WordPress 6.1 About page



<p>WordPress 6.1 <a href="https://make.wordpress.org/core/2022/07/21/core-editor-improvement-deeper-customization-with-more-template-options/">expands the templates options</a> available for site editing. Theme authors and users can now create page-specific templates, custom post type and post-specific templates, user-selectable custom templates for all post types, and taxonomy-specific templates for categories or tags.</p>



<p>With all the new block design and template editing capabilities, WordPress 6.1 has added more sophisticated content-locking capabilities. Block-locking can now be applied to all inner blocks in one click. This applies to containing blocks like Group, Cover, and Column blocks.</p>



<img />image credit: WordPress 6.1 About Page



<p>Menu management has also gotten a big update in 6.1, with menu controls relocated to their own place in the block settings. The navigation block now offers new fallback options in case the block isn&#8217;t pre-populated with inner blocks. If the navigation menu is empty, the fallback behavior is to display a list of available pages using the Page List block. If there are multiple block menus, the fallback is to display the most recently created block menu. This ensures that users aren&#8217;t stuck and can more easily understand where their menus will show up.</p>



<h3>New Twenty Twenty-Three Default Theme with 10 Style Variations</h3>



<p>One of the most anticipated parts of this release is the new <a href="https://wordpress.org/themes/twentytwentythree/">Twenty Twenty-Three</a> (TT3) default theme. This is a new kind of default theme that bundles a curated set of style variations, instead of creating a new theme from scratch. It uses a stripped-back version of Twenty Twenty-Two as the base for a theme that features <a href="https://wptavern.com/wordpress-announces-10-style-variation-selections-for-twenty-twenty-three-theme">10 community-contributed style variations</a>.</p>



<img />image credit: WordPress 6.1 About page



<p>The theme is accessibility-ready and puts the spotlight on all of the design tools available in the latest release. It is basically a blank slate for further customization, with both rich and minimalist color palettes and multiple typography options. It will be exciting to see what the world of WordPress users builds with the new theme.</p>



<img />



<p>Fluid typography makes its debut in 6.1. This feature is for theme authors but benefits users and site visitors alike. It allows authors to define font sizes that will smoothly scale between smaller and larger viewports, adapting in a fluid way to varying widths. </p>



<p>The best part of the new fluid typography feature is that it can easily be turned on by setting <code>typography.fluid</code> to be <code>true</code> in theme.json and adding <code>fluid</code> to each of the <code>settings.typography.fontSizes</code> with <code>min</code> and <code>max</code> values. If you want to see an example of fluid typography in action, look no further than the new Twenty Twenty-Three theme.</p>







<p>Other notable new features and updates in 6.1 include the following: </p>



<ul>
<li>List and Quote blocks now support inner blocks</li>



<li>Improved layout and visualization of document settings</li>



<li>Support for starter patterns for any post type</li>



<li>Filter Themes Directory for block themes in the admin</li>



<li>Improved block placeholders that show customization options</li>



<li>New system for persisting user preferences across browsers and devices</li>



<li>Block-based Template Parts now available in Classic Themes</li>



<li>Query Loop block extended to support custom queries</li>



<li>Set preset values for padding, margin and block gap</li>
</ul>



<p>WordPress 6.1 includes more than 60 <a href="https://make.wordpress.org/core/2022/10/11/wordpress-6-1-accessibility-improvements/">accessibility improvements</a> and 25 tickets dedicated to <a href="https://make.wordpress.org/core/2022/10/11/performance-field-guide-for-wordpress-6-1/">performance</a>. This release is the result of the tireless efforts of more than 800 contributors from 60+ countries. For a quick visual tour, check out the official WordPress 6.1 promo video:</p>



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

</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, 02 Nov 2022 02:30:34 +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: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:45:"WordPress.org blog: WordPress 6.1 “Misha”";s: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=13798";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/news/2022/11/misha/";s: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:76074:"<img width="1024" height="683" src="https://i0.wp.com/wordpress.org/news/files/2022/11/inline-image-inline.png?resize=1024%2C683&ssl=1" alt="" class="wp-image-13872" />



<h1>Welcome to “Misha”</h1>



<p>Say hello to WordPress 6.1, “Misha,” inspired by the life and work of Soviet-Norwegian jazz pianist <a href="https://en.wikipedia.org/wiki/Mikhail_Alperin">Mikhail “Misha” Alperin</a>. Misha introduced the work of jazz ensembles in the USSR and globally. He is also celebrated as a founding member of the <a href="https://en.wikipedia.org/wiki/Moscow_Art_Trio">Moscow Art Trio</a>.<br /><br />“Misha” further refines the site-building experience. Inside WordPress 6.1 you’ll interact with enhancements that continue to make site creation more intuitive while pushing your creative boundaries further than ever. Don’t forget to enjoy some of Misha’s <a href="https://www.youtube.com/channel/UCuh5oEm_jJ_jTcv8DmbLi2Q">jazz piano</a> as you take in all WordPress 6.1 has to offer.</p>



<p><span>The third major release of 2022 is here. </span><a href="https://wordpress.org/wordpress-6.1.zip"><span>Download it now</span></a><span>! As of the time of this release, WordPress powers </span><a href="https://w3techs.com/technologies/overview/content_management">43%</a><span> of websites worldwide.</span></p>



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



<blockquote class="wp-block-quote">
<p>This release includes features that many in the WordPress Community have been most excited about since the start of this project. Additional enhancements and improvements to the editor give site owners more control and easier customization while offering a more cohesive experience to users. A lot of writing-focused improvements are included in the release, because if you’re giving voices to the voiceless you’ve got to focus on folks writing the copy. </p>



<p>Some of my favorite enhancements are the refined ability to select partial paragraphs in a block; settings to keep list view open by default; and the keyboard shortcut to add internal links expanded to all blocks.</p>
<cite>Josepha Haden Chomphosy, Executive Director</cite></blockquote>



<div class="is-layout-flex wp-block-buttons">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://wordpress.org/wordpress-6.1.zip">Download WordPress 6.1</a></div>
</div>



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



<h2>What’s Inside</h2>



<h3>Twenty Twenty-Three:<br />A fresh default theme with 10 distinct style variations</h3>



<p>After introducing foundational elements for block themes and style variations in releases 5.9 and 6.0, WordPress site builders welcome a new default theme, Twenty Twenty-Three, that is powered by <a href="https://make.wordpress.org/design/2022/09/07/tt3-default-theme-announcing-style-variation-selections/">10 different styles</a> and tagged as&nbsp; “<a href="https://make.wordpress.org/themes/handbook/review/accessibility/">Accessibility Ready</a>.” These intentionally unique styles ensure users can apply a different look and feel to their site with a single click—all within a single theme.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Style-Variation-News-1.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13843" />



<h3>New templates for an improved creator experience</h3>



<p>New and more refined templates now give site builders more control over the creation of their sites. In this suite of new templates, find a custom template for posts &amp; pages in the Site Editor. Create and edit template parts like headers and footers more quickly with a new search-and-replace tool and easily view your new site.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Templates-News.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13818" />



<h3>Design tools for more consistency and control</h3>



<p>Thoughtful upgrades to the controls for design elements and blocks make laying out and building your new site a more consistent, complete, and intuitive experience.</p>




<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Design-Tools-News.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13819" />




<h3>Manage menus with ease</h3>



<p>New fallback options in the navigation block mean you can edit the menu that’s open; no searching needed. Plus, the controls for choosing and working on menus have their own place in the block settings. The mobile menu system also gets an upgrade with new features, including different icon options, to make the menu yours.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Navigation-1.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13844" />



<h3>Cleaner layouts and document settings visualization</h3>



<p>View and manage post and page settings with a better-organized display improving the use of features like template picker and scheduler.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Document-settings-News-1.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13838" />



<h3>One-click lock setting for all inner blocks</h3>



<p>When locking blocks, a new toggle lets you apply your lock settings to all the blocks in a containing block like the group, cover, and column blocks.</p>




<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Lock-News.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13824" />




<h3>Improved block placeholders</h3>



<p>Various blocks have improved placeholders that reflect customization options to help you design your site and its content. For example, the Image block placeholder displays custom borders and duotone filters even before selecting an image.</p>



<h3>Compose richer lists and quotes with inner blocks</h3>



<p>The List and Quote blocks now support inner blocks, allowing for more flexible and rich compositions like adding headings inside your Quote blocks.</p>



<h3>More responsive text with fluid typography</h3>



<p><a href="https://make.wordpress.org/core/2022/08/04/whats-new-in-gutenberg-13-8-3-august/#fluid-typography-support">Fluid typography</a> lets you define font sizes that adapt for easy reading in any screen size.</p>



<h3>Add starter patterns to any post type</h3>



<p>In WordPress 6.0, when you created a new page, you would see suggested patterns so you did not have to start with a blank page. In 6.1, you will also see the starter patterns modal when you create a new instance of any post type.</p>



<h3>Find block themes faster</h3>



<p>The Themes Directory has a filter for block themes, and a pattern preview gives a better sense of what the theme might look like while exploring different themes and patterns.</p>



<h3>Keep your Site Editor settings for later</h3>



<p>Site Editor settings are now <a href="https://make.wordpress.org/core/2022/10/10/changes-to-block-editor-preferences-in-wordpress-6-1/">persistent for each user</a>. This means your settings will now be consistent across browsers and devices.</p>



<h3>A streamlined style system</h3>



<p>The CSS rules for margin, padding, typography, colors, and borders within the <a href="https://make.wordpress.org/core/2022/10/10/block-styles-generation-style-engine/">styles engine</a> are now all in one place, reducing time spent on layout-specific tasks and helps to generate semantic class names.</p>



<h3>Updated interface options and features</h3>



<p>Updates include <a href="https://make.wordpress.org/core/2022/10/10/styling-elements-in-block-themes/">styling elements</a> like buttons, citations, and links globally; controlling hover, active, and focus states for links using theme.json (not available to control in the interface yet); and customizing outline support for blocks and elements, among other features.</p>



<h3>Continued evolution of layout options</h3>



<p>The default content dimensions provided by themes can now be overridden in the Styles Sidebar, giving site builders better control over full-width content. Developers have <a href="https://make.wordpress.org/core/2022/10/10/updated-editor-layout-support-in-6-1-after-refactor/">fine-grained control over these controls</a>.</p>



<h3>Block Template parts in classic themes</h3>



<p><a href="https://make.wordpress.org/core/2022/10/04/block-based-template-parts-in-traditional-themes/">Block template parts can now be defined in classic themes</a> by adding the appropriate HTML files `parts` directory at the root of the theme.</p>



<h3>Expanded support for Query Loop blocks</h3>



<p><a href="https://make.wordpress.org/core/2022/10/10/extending-the-query-loop-block/">New filters</a> let Query Block variations support custom queries for more powerful variations and advanced hierarchical post types filtering options.</p>



<h3>Filters for all your styles</h3>



<p><a href="https://make.wordpress.org/core/2022/10/10/filters-for-theme-json-data/">Leverage filters</a> in the Styles sidebar to control settings at all four levels of your site—core, theme, user, or block, from less to more specific.</p>



<h3>Spacing presets for faster, consistent design</h3>



<p>Save time and avoid hard-coding values into a theme with <a href="https://make.wordpress.org/core/2022/10/07/introduction-of-presets-across-padding-margin-and-block-gap/">preset margin and padding values for multiple blocks.</a></p>



<h3>Content-only editing support for container blocks</h3>



<p>Thanks to content-only editing settings, layouts can be locked within container blocks. In a content-only block, its children are invisible to the List View and entirely uneditable. So you control the layout while your writers can focus on the content. Combine it with block-locking options for even more advanced control over your blocks.</p>



<h3>Other notes of interest</h3>



<ul>
<li>6.1 includes a new time-to-read feature showing content authors the approximate time-to-read values for pages, posts, and custom post types.</li>



<li>The site tagline is empty by default in new sites but can be modified in General Settings.</li>



<li>A new modal design offers a background blur effect, making it easier to focus on the task at hand.</li>
</ul>



<h2>Enhancing WordPress 6.1 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.1 includes nearly 60 updates specifically focused on enhancing the accessibility of the platform. <a href="https://make.wordpress.org/core/2022/10/11/wordpress-6-1-accessibility-improvements/">Read these updates</a> to learn more about the continual initiatives aimed at improving accessibility.</p>



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



<p>WordPress 6.1 resolves more than 25 tickets dedicated to enhancing performance with improvements for every type of site. A full breakdown can be found in the <a href="https://make.wordpress.org/core/2022/10/11/performance-field-guide-for-wordpress-6-1/">Performance Field Guide</a>.</p>



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



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



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

</div>



<p><br /></p>



<p>Explore <a href="https://learn.wordpress.org/">learn.wordpress.org</a> for brief 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 </a>workshop on a specific WordPress topic.</p>



<p>Developers can explore the <a href="https://make.wordpress.org/core/2022/10/12/wordpress-6-1-field-guide/">WordPress 6.1 Field Guide</a>, complete with detailed developer notes to help you build with and extend WordPress. Read the <a href="https://wordpress.org/support/wordpress-version/version-6-1">WordPress</a><a href="https://wordpress.org/support/wordpress-version/version-6-1/"> 6.1 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.1 Release Squad</h2>



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



<p><span>Release Lead: </span><a href="https://profiles.wordpress.org/matt/"><span>Matt Mullenweg</span></a><span>&nbsp;</span><br /><span>Release Coordinators: </span><a href="https://profiles.wordpress.org/priethor/"><span>Héctor Prieto</span></a><span> and </span><a href="https://profiles.wordpress.org/desrosj/"><span>Jonathan Desrosiers</span></a><span>&nbsp;</span><br /><span>Core Tech Co-Leads: </span><a href="https://profiles.wordpress.org/mikeschroder/"><span>Mike Schroder</span></a><span>, </span><a href="https://profiles.wordpress.org/davidbaumwald/"><span>David Baumwald</span></a><span>, and </span><a href="https://profiles.wordpress.org/jeffpaul/"><span>Jeff Paul</span></a><br /><span>Editor Tech Co-Leads: </span><a href="https://profiles.wordpress.org/czapla/"><span>Michal Czaplinski</span></a><span>, </span><a href="https://profiles.wordpress.org/bernhard-reiter/"><span>Bernie Reiter</span></a><span>, and </span><a href="https://profiles.wordpress.org/cbravobernal/"><span>Carlos Bravo</span></a><br /><span>Core Triage Co-Leads: </span><a href="https://profiles.wordpress.org/audrasjb/"><span>JB Audras</span></a><span> and </span><a href="https://profiles.wordpress.org/chaion07/"><span>Ahmed Chaion</span></a><br /><span>Editor Triage Co-Leads: </span><a href="https://profiles.wordpress.org/ndiego/"><span>Nick Diego</span></a> <span>and </span><a href="https://profiles.wordpress.org/annezazu/"><span>Anne McCarthy</span></a><br /><span>Documentation Co-Leads: </span><a href="https://profiles.wordpress.org/bph/"><span>Birgit Pauli-Haack</span></a><span>, </span><a href="https://profiles.wordpress.org/milana_cap/"><span>Milana Cap</span></a><span>, and </span><a href="https://profiles.wordpress.org/femkreations/"><span>Femy Praseeth</span></a><br /><span>Marketing &amp; Communications Co-Leads:</span> <a href="https://profiles.wordpress.org/jpantani/"><span>Jonathan Pantani</span></a> <span>and </span><a href="https://profiles.wordpress.org/dansoschin/"><span>Dan Soschin</span></a><br /><span>Test Lead: </span><a href="https://profiles.wordpress.org/ironprogrammer/"><span>Brian Alexander</span></a><br /><span>Design Lead: </span><a href="https://profiles.wordpress.org/richtabor/"><span>Rich Tabor</span></a><br /><span>Default Theme Co-Leads: </span><a href="https://profiles.wordpress.org/beafialho/"><span>Beatriz Fialho</span></a><span> &amp; </span><a href="https://profiles.wordpress.org/mikachan/"><span>Sarah Norris</span></a></p>



<blockquote class="wp-block-quote">
<p>Thank you to all the contributors who dedicated time and energy to bring the best WordPress experience to everyone.</p>
<cite>Josepha Haden Chomphosy</cite></blockquote>



<p></p>



<pre class="wp-block-code"><code class=""><p class="is-style-wporg-props-long alignfull"><a href="https://profiles.wordpress.org/1naveengiri/">1naveengiri</a> · <a href="https://profiles.wordpress.org/aaroncampbell/">Aaron D. Campbell</a> · <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a> · <a href="https://profiles.wordpress.org/aaronrobertshaw/">Aaron Robertshaw</a> · <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a> · <a href="https://profiles.wordpress.org/hurayraiit/">Abu Hurayra</a> · <a href="https://profiles.wordpress.org/bosconiandynamics/">Adam Bosco</a> · <a href="https://profiles.wordpress.org/adampickering/">Adam Pickering</a> · <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a> · <a href="https://profiles.wordpress.org/admwgn/">Adam Wiltgen</a> · <a href="https://profiles.wordpress.org/zieladam/">Adam Zielinski</a> · <a href="https://profiles.wordpress.org/addiestavlo/">Addie</a> · <a href="https://profiles.wordpress.org/oztaser/">Adil &#214;ztaşer</a> · <a href="https://profiles.wordpress.org/aduth/">aduth</a> · <a href="https://profiles.wordpress.org/aezazshekh/">Aezaz Shekh</a> · <a href="https://profiles.wordpress.org/afrid1719/">afrid1719</a> · <a href="https://profiles.wordpress.org/chaion07/">Ahmed Chaion</a> · <a href="https://profiles.wordpress.org/engahmeds3ed/">Ahmed Saeed</a> · <a href="https://profiles.wordpress.org/seakashdiu/">Akash Mia</a> · <a href="https://profiles.wordpress.org/wildworks/">Aki Hamano</a> · <a href="https://profiles.wordpress.org/kamig478/">Akram ul haq</a> · <a href="https://profiles.wordpress.org/akshitsethi/">Akshit Sethi</a> · <a href="https://profiles.wordpress.org/schlessera/">Alain Schlesser</a> · <a href="https://profiles.wordpress.org/alamgircsebd/">alamgircsebd</a> · <a href="https://profiles.wordpress.org/alanp57/">AlanP57</a> · <a href="https://profiles.wordpress.org/alansyue/">alansyue</a> · <a href="https://profiles.wordpress.org/albatross10/">albatross10</a> · <a href="https://profiles.wordpress.org/aljullu/">Albert Juh&#233; Lluveras</a> · <a href="https://profiles.wordpress.org/alberuni-azad/">Alberuni Azad.</a> · <a href="https://profiles.wordpress.org/elpanda13gmailcom/">Alejandro J. Sanchez P.</a> · <a href="https://profiles.wordpress.org/zutigrm/">Aleksej</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/acoulombe/">Alexis Coulombe</a> · <a href="https://profiles.wordpress.org/alexstine/">alexstine</a> · <a href="https://profiles.wordpress.org/allancole/">allancole</a> · <a href="https://profiles.wordpress.org/allisonplus/">allisonplus</a> · <a href="https://profiles.wordpress.org/mrfoxtalbot/">Alvaro G&#243;mez</a> · <a href="https://profiles.wordpress.org/amirkamizi/">amirkamizi</a> · <a href="https://profiles.wordpress.org/amjadr360/">Amjad Ali</a> · <a href="https://profiles.wordpress.org/anantajitjg/">Anantajit JG</a> · <a href="https://profiles.wordpress.org/anariel-design/">Anariel Design</a> · <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a> · <a href="https://profiles.wordpress.org/deksar/">Andreas</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/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/eatingrules/">Andrew Wilder</a> · <a href="https://profiles.wordpress.org/andrewnz/">AndrewNZ</a> · <a href="https://profiles.wordpress.org/rarst/">Andrey "Rarst" Savchenko</a> · <a href="https://profiles.wordpress.org/andrija/">Andrija Naglic</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/andykeith/">Andy Keith</a> · <a href="https://profiles.wordpress.org/aniketpatel/">Aniket Patel</a> · <a href="https://profiles.wordpress.org/anitanenova/">anitanenova</a> · <a href="https://profiles.wordpress.org/ankit-k-gupta/">Ankit K Gupta</a> · <a href="https://profiles.wordpress.org/annabansaghi/">Anna Bansaghi</a> · <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a> · <a href="https://profiles.wordpress.org/alaca/">Ante Laca</a> · <a href="https://profiles.wordpress.org/antpb/">Anthony Burchell</a> · <a href="https://profiles.wordpress.org/antonvlasenko/">Anton Vlasenko</a> · <a href="https://profiles.wordpress.org/apedog/">apedog</a> · <a href="https://profiles.wordpress.org/apokalyptik/">apokalyptik</a> · <a href="https://profiles.wordpress.org/arrasel403/">AR Rasel</a> · <a href="https://profiles.wordpress.org/arcangelini/">arcangelini</a> · <a href="https://profiles.wordpress.org/archon810/">archon810</a> · <a href="https://profiles.wordpress.org/aristath/">Ari Stathopoulos</a> · <a href="https://profiles.wordpress.org/yellyc/">Ariel Chinn</a> · <a href="https://profiles.wordpress.org/xylocone/">Arjun Singh</a> · <a href="https://profiles.wordpress.org/armondal/">Arnab Mondal</a> · <a href="https://profiles.wordpress.org/passoniate/">Arslan Kalwar</a> · <a href="https://profiles.wordpress.org/arturgrabo/">Artur Grabowski</a> · <a href="https://profiles.wordpress.org/ideag/">Arunas Liuiza</a> · <a href="https://profiles.wordpress.org/aspexi/">Aspexi</a> · <a href="https://profiles.wordpress.org/aurooba/">Aurooba Ahmed</a> · <a href="https://profiles.wordpress.org/filosofo/">Austin Matzko</a> · <a href="https://profiles.wordpress.org/ayeshrajans/">Ayesh Karunaratne</a> · <a href="https://profiles.wordpress.org/baned/">BaneD</a> · <a href="https://profiles.wordpress.org/barneydavey/">barneydavey</a> · <a href="https://profiles.wordpress.org/bbobnis/">Bartosz Bobnis</a> · <a href="https://profiles.wordpress.org/beafialho/">Beatriz Fialho</a> · <a href="https://profiles.wordpress.org/scruffian/">Ben Dwyer</a> · <a href="https://profiles.wordpress.org/bengreeley/">Ben Greeley</a> · <a href="https://profiles.wordpress.org/utz119/">Benachi</a> · <a href="https://profiles.wordpress.org/benjgrolleau/">Benjamin Grolleau</a> · <a href="https://profiles.wordpress.org/benoitchantre/">Benoit Chantre</a> · <a href="https://profiles.wordpress.org/bernhard reiter/">Bernhard Reiter</a> · <a href="https://profiles.wordpress.org/bernhard-reiter/">Bernie Reiter</a> · <a href="https://profiles.wordpress.org/bhrugesh12/">Bhrugesh Bavishi</a> · <a href="https://profiles.wordpress.org/elten/">Bing</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/blockify/">Blockify</a> · <a href="https://profiles.wordpress.org/boblindner/">Bob</a> · <a href="https://profiles.wordpress.org/bobbingwide/">bobbingwide</a> · <a href="https://profiles.wordpress.org/gitlost/">bonger</a> · <a href="https://profiles.wordpress.org/boonebgorges/">Boone Gorges</a> · <a href="https://profiles.wordpress.org/bjorsch/">Brad Jorsch</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/bgardner/">Brian Gardner</a> · <a href="https://profiles.wordpress.org/cantuaria/">Bruno Cantuaria</a> · <a href="https://profiles.wordpress.org/ribaricplusplus/">Bruno Ribaric</a> · <a href="https://profiles.wordpress.org/burgiuk/">burgiuk</a> · <a href="https://profiles.wordpress.org/burhandodhy/">Burhan Nasir</a> · <a href="https://profiles.wordpress.org/bwbama/">bwbama</a> · <a href="https://profiles.wordpress.org/cadlec/">cadlec</a> · <a href="https://profiles.wordpress.org/cagsmith/">cagsmith</a> · <a href="https://profiles.wordpress.org/cbravobernal/">Carlos Bravo</a> · <a href="https://profiles.wordpress.org/carlosgprim/">Carlos Garcia Prim</a> · <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a> · <a href="https://profiles.wordpress.org/cavalierlife/">cavalierlife</a> · <a href="https://profiles.wordpress.org/cdbessig/">cdbessig</a> · <a href="https://profiles.wordpress.org/shireling/">Chad Chadbourne</a> · <a href="https://profiles.wordpress.org/nhuja/">Chandra M</a> · <a href="https://profiles.wordpress.org/critterverse/">Channing Ritter</a> · <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a> · <a href="https://profiles.wordpress.org/chintan1896/">Chintan hingrajiya</a> · <a href="https://profiles.wordpress.org/cbringmann/">Chloe Bringmann</a> · <a href="https://profiles.wordpress.org/chouby/">Chouby</a> · <a href="https://profiles.wordpress.org/chrisbudd1/">Chris Budd</a> · <a href="https://profiles.wordpress.org/chrishardie/">Chris Hardie</a> · <a href="https://profiles.wordpress.org/czarate/">Chris Zarate</a> · <a href="https://profiles.wordpress.org/chriscct7/">chriscct7</a> · <a href="https://profiles.wordpress.org/chrisguitarguy/">chrisguitarguy</a> · <a href="https://profiles.wordpress.org/cwbudde/">Christian-W. Budde</a> · <a href="https://profiles.wordpress.org/christinavoudouris/">Christina Voudouris</a> · <a href="https://profiles.wordpress.org/apermo/">Christoph Daum</a> · <a href="https://profiles.wordpress.org/cfinke/">Christopher Finke</a> · <a href="https://profiles.wordpress.org/ryno267/">Chuck Reynolds</a> · <a href="https://profiles.wordpress.org/chynnabenton/">chynnabenton</a> · <a href="https://profiles.wordpress.org/ckanderson22/">ckanderson22</a> · <a href="https://profiles.wordpress.org/design_dolphin/">CodePoet</a> · <a href="https://profiles.wordpress.org/codewhy/">codewhy</a> · <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a> · <a href="https://profiles.wordpress.org/collieit/">Collie-IT, Anne K. Frey</a> · <a href="https://profiles.wordpress.org/colonelphantom/">colonelphantom</a> · <a href="https://profiles.wordpress.org/cbirdsong/">Cory Birdsong</a> · <a href="https://profiles.wordpress.org/courane01/">Courtney Robertson</a> · <a href="https://profiles.wordpress.org/craigfrancis/">craigfrancis</a> · <a href="https://profiles.wordpress.org/crazycoders/">crazycoders</a> · <a href="https://profiles.wordpress.org/mitogh/">Crisoforo Gaspar</a> · <a href="https://profiles.wordpress.org/cu121/">Cupid Chakma</a> · <a href="https://profiles.wordpress.org/curdin/">Curdin Krummenacher</a> · <a href="https://profiles.wordpress.org/cyrillbolliger/">cyrillbolliger</a> · <a href="https://profiles.wordpress.org/dxd5001/">Daijiro Miyazawa</a> · <a href="https://profiles.wordpress.org/dainemawer/">dainemawer</a> · <a href="https://profiles.wordpress.org/daisyo/">Daisy Olsen</a> · <a href="https://profiles.wordpress.org/daledupreez/">Dale du Preez</a> · <a href="https://profiles.wordpress.org/colorful-tones/">Damon Cook</a> · <a href="https://profiles.wordpress.org/damonganto/">damonganto</a> · <a href="https://profiles.wordpress.org/danfarrow/">Dan Farrow</a> · <a href="https://profiles.wordpress.org/dansoschin/">Dan Soschin</a> · <a href="https://profiles.wordpress.org/danielbachhuber/">Daniel Bachhuber</a> · <a href="https://profiles.wordpress.org/danieliser/">Daniel Iser</a> · <a href="https://profiles.wordpress.org/talldanwp/">Daniel Richards</a> · <a href="https://profiles.wordpress.org/schutzsmith/">Daniel Schutzsmith</a> · <a href="https://profiles.wordpress.org/mte90/">Daniele Scasciafratte</a> · <a href="https://profiles.wordpress.org/darerodz/">darerodz</a> · <a href="https://profiles.wordpress.org/dariak/">Daria</a> · <a href="https://profiles.wordpress.org/dkotter/">Darin Kotter</a> · <a href="https://profiles.wordpress.org/darkog/">Darko G.</a> · <a href="https://profiles.wordpress.org/darkskipper/">darkskipper</a> · <a href="https://profiles.wordpress.org/uofaberdeendarren/">Darren Coutts</a> · <a href="https://profiles.wordpress.org/htdat/">Dat Hoang</a> · <a href="https://profiles.wordpress.org/datainterlock/">datainterlock</a> · <a href="https://profiles.wordpress.org/dhilditch/">Dave Hilditch</a> · <a href="https://profiles.wordpress.org/dave1010/">dave1010</a> · <a href="https://profiles.wordpress.org/davidanderson/">David Anderson</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/dcowgill/">David C</a> · <a href="https://profiles.wordpress.org/dpcalhoun/">David Calhoun</a> · <a href="https://profiles.wordpress.org/desmith/">David E. Smith</a> · <a href="https://profiles.wordpress.org/dg12345/">David Goring</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/daviedr/">David Rozando</a> · <a href="https://profiles.wordpress.org/get_dave/">David Smith</a> · <a href="https://profiles.wordpress.org/daxelrod/">daxelrod</a> · <a href="https://profiles.wordpress.org/daymobrew/">daymobrew</a> · <a href="https://profiles.wordpress.org/dsas/">Dean Sas</a> · <a href="https://profiles.wordpress.org/deepakvijayan/">Deepak Vijayan</a> · <a href="https://profiles.wordpress.org/denis-de-bernardy/">Denis de Bernardy</a> · <a href="https://profiles.wordpress.org/dingo_d/">Denis Žoljom</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/derekblank/">derekblank</a> · <a href="https://profiles.wordpress.org/pcfreak30/">Derrick Hammer</a> · <a href="https://profiles.wordpress.org/dharm1025/">Dharmesh Patel</a> · <a href="https://profiles.wordpress.org/dhl/">dhl</a> · <a href="https://profiles.wordpress.org/dianeco/">Diane Co</a> · <a href="https://profiles.wordpress.org/dilipbheda/">Dilip Bheda</a> · <a href="https://profiles.wordpress.org/dingdang/">dingdang</a> · <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a> · <a href="https://profiles.wordpress.org/dipakparmar443/">Dipak Parmar</a> · <a href="https://profiles.wordpress.org/divyeshgodhani/">divyeshgodhani</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/dougwollison/">Doug Wollison</a> · <a href="https://profiles.wordpress.org/dougal/">Dougal Campbell</a> · <a href="https://profiles.wordpress.org/drewapicture/">Drew Jaynes</a> · <a href="https://profiles.wordpress.org/drivingralle/">Drivingralle</a> · <a href="https://profiles.wordpress.org/drzraf/">drzraf</a> · <a href="https://profiles.wordpress.org/dwainm/">Dwain Maralack</a> · <a href="https://profiles.wordpress.org/kucrut/">Dzikri Aziz</a> · <a href="https://profiles.wordpress.org/dovyp/">Dōvy Paukstys</a> · <a href="https://profiles.wordpress.org/eclev91/">eclev91</a> · <a href="https://profiles.wordpress.org/chopinbach/">Edwin Cromley</a> · <a href="https://profiles.wordpress.org/eedee/">eedee</a> · <a href="https://profiles.wordpress.org/ehtis/">Ehtisham S.</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/clarkeemily/">Emily Clarke</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/ethitter/">Erick Hitter</a> · <a href="https://profiles.wordpress.org/codekraft/">Erik</a> · <a href="https://profiles.wordpress.org/kebbet/">Erik Betshammar</a> · <a href="https://profiles.wordpress.org/estelaris/">estelaris</a> · <a href="https://profiles.wordpress.org/eugenemanuilov/">Eugene.Manuilov</a> · <a href="https://profiles.wordpress.org/madpixels/">eugene.manuilov</a> · <a href="https://profiles.wordpress.org/eherman24/">Evan Herman</a> · <a href="https://profiles.wordpress.org/aaemnnosttv/">Evan Mattson</a> · <a href="https://profiles.wordpress.org/circlecube/">Evan Mullins</a> · <a href="https://profiles.wordpress.org/fabiankaegy/">Fabian K&#228;gy</a> · <a href="https://profiles.wordpress.org/faisal03/">Faisal Alvi</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/fellyph/">Fellyph Cintra</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/fcoveram/">Francisco</a> · <a href="https://profiles.wordpress.org/fuadragib/">Fuad Ragib</a> · <a href="https://profiles.wordpress.org/furi3r/">furi3r</a> · <a href="https://profiles.wordpress.org/gabri3lmarques/">gabri3lmarques</a> · <a href="https://profiles.wordpress.org/gdetassigny/">Gabriel de Tassigny</a> · <a href="https://profiles.wordpress.org/gabertronic/">Gabriel Rose</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/garymatthews919/">garymatthews919</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/gigitux/">gigitux</a> · <a href="https://profiles.wordpress.org/giox069/">giox069</a> · <a href="https://profiles.wordpress.org/giuseppemazzapica/">giuseppemazzapica</a> · <a href="https://profiles.wordpress.org/glendaviesnz/">Glen Davies</a> · <a href="https://profiles.wordpress.org/goldenapples/">goldenapples</a> · <a href="https://profiles.wordpress.org/greglone/">Gr&#233;gory Viguier</a> · <a href="https://profiles.wordpress.org/graham73may/">graham73may</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/greg24/">greg24</a> · <a href="https://profiles.wordpress.org/gregorlove/">gRegor Morrill</a> · <a href="https://profiles.wordpress.org/gunterer/">gunterer</a> · <a href="https://profiles.wordpress.org/bordoni/">Gustavo Bordoni</a> · <a href="https://profiles.wordpress.org/h2ham/">h2ham (Hiromu Hasegawa)</a> · <a href="https://profiles.wordpress.org/hakanca/">hakanca</a> · <a href="https://profiles.wordpress.org/hakre/">hakre</a> · <a href="https://profiles.wordpress.org/hansjovisyoast/">Hans-Christiaan Braun</a> · <a href="https://profiles.wordpress.org/thakkarhardik/">Hardik Thakkar</a> · <a href="https://profiles.wordpress.org/haritpanchal/">Harit Panchal</a> · <a href="https://profiles.wordpress.org/harshvaishnav/">harshvaishnav</a> · <a href="https://profiles.wordpress.org/hasanuzzamanshamim/">Hasanuzzaman</a> · <a href="https://profiles.wordpress.org/azhiyadev/">Hauwa Abashiya</a> · <a href="https://profiles.wordpress.org/helen/">Helen Hou-Sandi</a> · <a href="https://profiles.wordpress.org/iamarinoh/">Henrique Iamarino</a> · <a href="https://profiles.wordpress.org/henrywright/">Henry Wright</a> · <a href="https://profiles.wordpress.org/here/">here</a> · <a href="https://profiles.wordpress.org/herregroen/">Herre Groen</a> · <a href="https://profiles.wordpress.org/hilayt24/">Hilay Trivedi</a> · <a href="https://profiles.wordpress.org/hiren1094/">hiren sanja</a> · <a href="https://profiles.wordpress.org/hiyascout/">hiyascout</a> · <a href="https://profiles.wordpress.org/howdy_mcgee/">Howdy_McGee</a> · <a href="https://profiles.wordpress.org/hugodevos/">hugodevos</a> · <a href="https://profiles.wordpress.org/huubl/">huubl</a> · <a href="https://profiles.wordpress.org/hztyfoon/">hztyfoon</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/iansvo/">iansvo</a> · <a href="https://profiles.wordpress.org/icaspar/">iCaspar</a> · <a href="https://profiles.wordpress.org/igmoweb/">Ignacio Cruz Moreno</a> · <a href="https://profiles.wordpress.org/igorsch/">Igor</a> · <a href="https://profiles.wordpress.org/igrigorik/">igrigorik</a> · <a href="https://profiles.wordpress.org/ilovecats7/">ilovecats7</a> · <a href="https://profiles.wordpress.org/ilunabar/">ilunabar</a> · <a href="https://profiles.wordpress.org/imadarshakshat/">imadarshakshat</a> · <a href="https://profiles.wordpress.org/ipajen/">ipajen</a> · <a href="https://profiles.wordpress.org/ipstenu/">Ipstenu (Mika Epstein)</a> · <a href="https://profiles.wordpress.org/irecinius/">irecinius</a> · <a href="https://profiles.wordpress.org/isabel_brison/">Isabel Brison</a> · <a href="https://profiles.wordpress.org/iulia-cazan/">Iulia Cazan</a> · <a href="https://profiles.wordpress.org/ivanjeronimo/">ivanjeronimo</a> · <a href="https://profiles.wordpress.org/iviweb/">iviweb</a> · <a href="https://profiles.wordpress.org/jdgrimes/">J.D. Grimes</a> · <a href="https://profiles.wordpress.org/primetimejas/">Jacob Schweitzer</a> · <a href="https://profiles.wordpress.org/jakariaistauk/">Jakaria Istauk</a> · <a href="https://profiles.wordpress.org/jamesckemp/">James Kemp</a> · <a href="https://profiles.wordpress.org/jameskoster/">James Koster</a> · <a href="https://profiles.wordpress.org/jamieburchell/">jamieburchell</a> · <a href="https://profiles.wordpress.org/janthiel/">Jan Thiel</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/trapsta/">Jasper Kinoti</a> · <a href="https://profiles.wordpress.org/javiarce/">Javier Arce</a> · <a href="https://profiles.wordpress.org/javiercasares/">Javier Casares</a> · <a href="https://profiles.wordpress.org/grandeljay/">Jay Trees</a> · <a href="https://profiles.wordpress.org/audrasjb/">Jean-Baptiste Audras</a> · <a href="https://profiles.wordpress.org/jeawhanlee/">jeawhanlee</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/juberstine/">Jeff Uberstine</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/jeroenreumkens/">JeroenReumkens</a> · <a href="https://profiles.wordpress.org/luminuu/">Jessica Lyschik</a> · <a href="https://profiles.wordpress.org/jhart35/">jhart35</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/jnz31/">jnz31</a> · <a href="https://profiles.wordpress.org/joedolson/">Joe Dolson</a> · <a href="https://profiles.wordpress.org/joehoyle/">Joe Hoyle</a> · <a href="https://profiles.wordpress.org/joemcgill/">Joe McGill</a> · <a href="https://profiles.wordpress.org/joelhardi/">joelhardi</a> · <a href="https://profiles.wordpress.org/joen/">Joen Asmussen</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/johnmark8080/">johnmark8080</a> · <a href="https://profiles.wordpress.org/jb510/">Jon Brown</a> · <a href="https://profiles.wordpress.org/jonsurrell/">Jon Surrell</a> · <a href="https://profiles.wordpress.org/psykro/">Jonathan Bossenger</a> · <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a> · <a href="https://profiles.wordpress.org/jpantani/">Jonathan Pantani</a> · <a href="https://profiles.wordpress.org/jonmackintosh/">jonmackintosh</a> · <a href="https://profiles.wordpress.org/spacedmonkey/">Jonny Harris</a> · <a href="https://profiles.wordpress.org/jonny-s/">jonny-s</a> · <a href="https://profiles.wordpress.org/jonoaldersonwp/">Jono Alderson</a> · <a href="https://profiles.wordpress.org/joostdevalk/">Joost de Valk</a> · <a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a> · <a href="https://profiles.wordpress.org/josvelasco/">Jos Velasco</a> · <a href="https://profiles.wordpress.org/joegrainger/">Joseph Grainger</a> · <a href="https://profiles.wordpress.org/jostnes/">Josepha Dambul</a> · <a href="https://profiles.wordpress.org/chanthaboune/">Josepha Haden</a> · <a href="https://profiles.wordpress.org/jhabdas/">Josh Habdas</a> · <a href="https://profiles.wordpress.org/joshuaabenazer/">Joshua Abenazer</a> · <a href="https://profiles.wordpress.org/joyously/">Joy</a> · <a href="https://profiles.wordpress.org/jrbeilke/">jrbeilke</a> · <a href="https://profiles.wordpress.org/jsnajdr/">jsnajdr</a> · <a href="https://profiles.wordpress.org/juhise/">Juhi Saxena</a> · <a href="https://profiles.wordpress.org/juliemoynat/">Julie Moynat</a> · <a href="https://profiles.wordpress.org/jrf/">Juliette Reinders Folmer</a> · <a href="https://profiles.wordpress.org/juliobox/">Julio Potier</a> · <a href="https://profiles.wordpress.org/just0nequestion/">just0nequestion</a> · <a href="https://profiles.wordpress.org/justinahinon/">Justin Ahinon</a> · <a href="https://profiles.wordpress.org/justinsainton/">Justin Sainton</a> · <a href="https://profiles.wordpress.org/greenshady/">Justin Tadlock</a> · <a href="https://profiles.wordpress.org/welenofsky/">Justin Welenofsky</a> · <a href="https://profiles.wordpress.org/jyolsna/">jyolsna</a> · <a href="https://profiles.wordpress.org/kadamwhite/">K. Adam White</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/akabarikalpesh/">Kalpesh Akabari</a> · <a href="https://profiles.wordpress.org/kapilpaul/">Kapil Paul</a> · <a href="https://profiles.wordpress.org/karinclimber/">Kari Anderson</a> · <a href="https://profiles.wordpress.org/karlgroves/">karlgroves</a> · <a href="https://profiles.wordpress.org/karlijnbk/">Karlijn Bok</a> · <a href="https://profiles.wordpress.org/kasparsd/">Kaspars</a> · <a href="https://profiles.wordpress.org/zoonini/">Kathryn Presner</a> · <a href="https://profiles.wordpress.org/kbrownkd/">kbrownkd</a> · <a href="https://profiles.wordpress.org/kkoppenhaver/">Keanan Koppenhaver</a> · <a href="https://profiles.wordpress.org/ryelle/">Kelly Choyce-Dwan</a> · <a href="https://profiles.wordpress.org/kellychoffman/">Kelly Hoffman</a> · <a href="https://profiles.wordpress.org/kevinb/">Kevin Behrens</a> · <a href="https://profiles.wordpress.org/khag7/">Kevin Hagerty</a> · <a href="https://profiles.wordpress.org/khoipro/">Khoi Pro</a> · <a href="https://profiles.wordpress.org/khokansardar/">Khokan Sardar</a> · <a href="https://profiles.wordpress.org/killua99/">killua99</a> · <a href="https://profiles.wordpress.org/kishanjasani/">Kishan Jasani</a> · <a href="https://profiles.wordpress.org/kitchin/">kitchin</a> · <a href="https://profiles.wordpress.org/kjellr/">Kjell Reigstad</a> · <a href="https://profiles.wordpress.org/kkmuffme/">kkmuffme</a> · <a href="https://profiles.wordpress.org/blackawxs/">klewis</a> · <a href="https://profiles.wordpress.org/knutsp/">Knut Sparhell</a> · <a href="https://profiles.wordpress.org/vdwijngaert/">Koen Van den Wijngaert</a> · <a href="https://profiles.wordpress.org/konradyoast/">Konrad.K</a> · <a href="https://profiles.wordpress.org/kovshenin/">Konstantin Kovshenin</a> · <a href="https://profiles.wordpress.org/kanlukasz/">Kris Kelvin</a> · <a href="https://profiles.wordpress.org/krishaweb/">KrishaWeb</a> · <a href="https://profiles.wordpress.org/krupalpanchal/">Krupal Panchal</a> · <a href="https://profiles.wordpress.org/kmadhak/">Kunal Madhak</a> · <a href="https://profiles.wordpress.org/kurtpayne/">Kurt Payne</a> · <a href="https://profiles.wordpress.org/kwillmorth/">kwillmorth</a> · <a href="https://profiles.wordpress.org/kbjohnson90/">Kyle B. Johnson</a> · <a href="https://profiles.wordpress.org/devnel/">Kyle Nel</a> · <a href="https://profiles.wordpress.org/laurelfulford/">laurelfulford</a> · <a href="https://profiles.wordpress.org/laurlittle/">Lauren Stein</a> · <a href="https://profiles.wordpress.org/laurent22777/">laurent22777</a> · <a href="https://profiles.wordpress.org/lazam786/">lazam786</a> · <a href="https://profiles.wordpress.org/leewillis77/">Lee Willis</a> · <a href="https://profiles.wordpress.org/leemon/">leemon</a> · <a href="https://profiles.wordpress.org/0mirka00/">Lena Morita</a> · <a href="https://profiles.wordpress.org/leogermani/">leogermani</a> · <a href="https://profiles.wordpress.org/rudlinkon/">Linkon Miyan</a> · <a href="https://profiles.wordpress.org/linsoftware/">Linnea Huxford</a> · <a href="https://profiles.wordpress.org/lonnylot/">lonnylot</a> · <a href="https://profiles.wordpress.org/thelovekesh/">Lovekesh Kumar</a> · <a href="https://profiles.wordpress.org/lovor/">Lovro Hrust</a> · <a href="https://profiles.wordpress.org/lucasbustamante/">Lucas Bustamante</a> · <a href="https://profiles.wordpress.org/lucilastancato/">lucilastancato</a> · <a href="https://profiles.wordpress.org/luigipulcini/">luigipulcini</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/infolu/">Luiz Ara&#250;jo</a> · <a href="https://profiles.wordpress.org/mitweka/">Lukas Niebler</a> · <a href="https://profiles.wordpress.org/lukecavanagh/">Luke Cavanagh</a> · <a href="https://profiles.wordpress.org/msnewas/">M S Newaz</a> · <a href="https://profiles.wordpress.org/maartenj/">Maarten</a> · <a href="https://profiles.wordpress.org/mashikag/">Maciej</a> · <a href="https://profiles.wordpress.org/maciejmackowiak/">maciejmackowiak</a> · <a href="https://profiles.wordpress.org/mrdollu/">Madhu Dollu</a> · <a href="https://profiles.wordpress.org/madhudollu/">Madhu Dollu</a> · <a href="https://profiles.wordpress.org/onemaggie/">Maggie Cabrera</a> · <a href="https://profiles.wordpress.org/patopaiar/">magicoders</a> · <a href="https://profiles.wordpress.org/maahrokh/">Mahrokh</a> · <a href="https://profiles.wordpress.org/maksimkuzmin/">maksimkuzmin</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/manishsongirkar36/">Manish Songirkar</a> · <a href="https://profiles.wordpress.org/manzoorwanijk/">Manzoor Wani</a> · <a href="https://profiles.wordpress.org/manzurahammed/">Manzur Ahammed</a> · <a href="https://profiles.wordpress.org/marcyoast/">Marc</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/marekdedic/">Marek Dědič</a> · <a href="https://profiles.wordpress.org/nuryko/">Marianna</a> · <a href="https://profiles.wordpress.org/chaton666/">Marie Comet</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/markbiek/">Mark Biek</a> · <a href="https://profiles.wordpress.org/markhowellsmead/">Mark Howells-Mead</a> · <a href="https://profiles.wordpress.org/markjaquith/">Mark Jaquith</a> · <a href="https://profiles.wordpress.org/markparnell/">Mark Parnell</a> · <a href="https://profiles.wordpress.org/markoheijnen/">Marko Heijnen</a> · <a href="https://profiles.wordpress.org/flootr/">Markus</a> · <a href="https://profiles.wordpress.org/mkox/">Markus Kosmal</a> · <a href="https://profiles.wordpress.org/mhkuu/">Martijn van der Klis</a> · <a href="https://profiles.wordpress.org/hinjiriyo/">Martin Stehle</a> · <a href="https://profiles.wordpress.org/martinkrcho/">martin.krcho</a> · <a href="https://profiles.wordpress.org/marybaum/">Mary Baum</a> · <a href="https://profiles.wordpress.org/mashukushibiki/">Mashu</a> · <a href="https://profiles.wordpress.org/masteradhoc/">masteradhoc</a> · <a href="https://profiles.wordpress.org/msurdi/">Mat&#237;as Emanuel Surdi</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/matt/">Matt Mullenweg</a> · <a href="https://profiles.wordpress.org/mattwondra/">Matt Wondra</a> · <a href="https://profiles.wordpress.org/mboynes/">Matthew Boynes</a> · <a href="https://profiles.wordpress.org/mattheweppelsheimer/">Matthew Eppelsheimer</a> · <a href="https://profiles.wordpress.org/matthiaspabst/">Matthias Pabst</a> · <a href="https://profiles.wordpress.org/matthiasreinholz/">Matthias Reinholz</a> · <a href="https://profiles.wordpress.org/mattyrob/">mattyrob</a> · <a href="https://profiles.wordpress.org/azouamauriac/">Mauriac AZOUA</a> · <a href="https://profiles.wordpress.org/maximej/">Maxime J.</a> · <a href="https://profiles.wordpress.org/maximemeganck/">Maxime Meganck</a> · <a href="https://profiles.wordpress.org/mayankmajeji/">Mayank Majeji</a> · <a href="https://profiles.wordpress.org/maythamalsudany/">maythamalsudany</a> · <a href="https://profiles.wordpress.org/mayuge/">Mayuge</a> · <a href="https://profiles.wordpress.org/mcliwanow/">mcliwanow</a> · <a href="https://profiles.wordpress.org/rakibwordpress/">Md Rakib Hossain</a> · <a href="https://profiles.wordpress.org/russel07/">Md. Russel Hussain</a> · <a href="https://profiles.wordpress.org/mdrago/">mdrago</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/mehulkaklotar/">Mehul Kaklotar</a> · <a href="https://profiles.wordpress.org/melchoyce/">Mel Choyce-Dwan</a> · <a href="https://profiles.wordpress.org/meloniq/">meloniq</a> · <a href="https://profiles.wordpress.org/merkys/">Merkys Maliukevičius</a> · <a href="https://profiles.wordpress.org/meysamnorouzi/">meysam norouzi</a> · <a href="https://profiles.wordpress.org/mfgmicha/">Micha Krapp</a> · <a href="https://profiles.wordpress.org/michaelbourne/">Michael Bourne</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/mihaidumitrascu/">Mihai Dumitrascu</a> · <a href="https://profiles.wordpress.org/mihai2u/">Mike Crantea</a> · <a href="https://profiles.wordpress.org/mdgl/">Mike Glendinning</a> · <a href="https://profiles.wordpress.org/mikehansenme/">Mike Hansen</a> · <a href="https://profiles.wordpress.org/mikejolley/">Mike Jolley (a11n)</a> · <a href="https://profiles.wordpress.org/mikeschroder/">Mike Schroder</a> · <a href="https://profiles.wordpress.org/mikemanzo/">mikemanzo</a> · <a href="https://profiles.wordpress.org/milana_cap/">Milana Cap</a> · <a href="https://profiles.wordpress.org/milindmore22/">Milind More</a> · <a href="https://profiles.wordpress.org/mimitips/">mimi</a> · <a href="https://profiles.wordpress.org/multidots1896/">Minal Diwan</a> · <a href="https://profiles.wordpress.org/presents111/">miya</a> · <a href="https://profiles.wordpress.org/mlajo/">Mladen</a> · <a href="https://profiles.wordpress.org/batmoo/">Mohammad Jangda</a> · <a href="https://profiles.wordpress.org/mjkhajeh/">MohammadJafar Khajeh</a> · <a href="https://profiles.wordpress.org/mohitdadhich10/">Mohit Dadhich</a> · <a href="https://profiles.wordpress.org/boemedia/">Monique Dubbelman</a> · <a href="https://profiles.wordpress.org/mt8biz/">moto hachi</a> · <a href="https://profiles.wordpress.org/mreishus/">mreishus</a> · <a href="https://profiles.wordpress.org/mrobit/">mrobit</a> · <a href="https://profiles.wordpress.org/msolution/">msolution</a> · <a href="https://profiles.wordpress.org/mtias/">mtias</a> · <a href="https://profiles.wordpress.org/wparslan/">Muhammad Arslan</a> · <a href="https://profiles.wordpress.org/mukesh27/">Mukesh Panchal</a> · <a href="https://profiles.wordpress.org/mmaumio/">Muntasir Mahmud</a> · <a href="https://profiles.wordpress.org/amustaque97/">Mustaque Ahmed</a> · <a href="https://profiles.wordpress.org/mvraghavan/">mvraghavan</a> · <a href="https://profiles.wordpress.org/mweichert/">mweichert</a> · <a href="https://profiles.wordpress.org/n8finch/">n8finch</a> · <a href="https://profiles.wordpress.org/tushar284/">Nahid Hasan</a> · <a href="https://profiles.wordpress.org/nalininonstopnewsuk/">Nalini Thakor</a> · <a href="https://profiles.wordpress.org/namithjawahar/">Namith Jawahar</a> · <a href="https://profiles.wordpress.org/nareshbheda/">Naresh Bheda</a> · <a href="https://profiles.wordpress.org/nateallen/">Nate Allen</a> · <a href="https://profiles.wordpress.org/nhadsall/">Nathan</a> · <a href="https://profiles.wordpress.org/nathanatmoz/">Nathan Johnson</a> · <a href="https://profiles.wordpress.org/navigatrum/">navigatrum</a> · <a href="https://profiles.wordpress.org/neffff/">neffff</a> · <a href="https://profiles.wordpress.org/nendeb55/">nendeb</a> · <a href="https://profiles.wordpress.org/neychok/">Neycho Kalaydzhiev</a> · <a href="https://profiles.wordpress.org/eidolonnight/">Nicholas Garofalo</a> · <a href="https://profiles.wordpress.org/ndiego/">Nick Diego</a> · <a href="https://profiles.wordpress.org/celloexpressions/">Nick Halsey</a> · <a href="https://profiles.wordpress.org/nico23/">Nico</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/nikkigagency/">nikkigagency</a> · <a href="https://profiles.wordpress.org/im_niloy/">Niloy</a> · <a href="https://profiles.wordpress.org/ninos-ego/">Ninos</a> · <a href="https://profiles.wordpress.org/nithi22/">Nithin John</a> · <a href="https://profiles.wordpress.org/nithins53/">Nithin SreeRaj</a> · <a href="https://profiles.wordpress.org/nlpro/">nlpro</a> · <a href="https://profiles.wordpress.org/noahtallen/">Noah Allen</a> · <a href="https://profiles.wordpress.org/noplanman/">noplanman</a> · <a href="https://profiles.wordpress.org/nouarah/">nouarah</a> · <a href="https://profiles.wordpress.org/numidwasnotavailable/">NumidWasNotAvailable</a> · <a href="https://profiles.wordpress.org/nunomorgadinho/">Nuno Morgadinho</a> · <a href="https://profiles.wordpress.org/zikubd/">Nurul Umbhiya</a> · <a href="https://profiles.wordpress.org/nvartolomei/">nvartolomei</a> · <a href="https://profiles.wordpress.org/obayedmamur/">Obayed Mamur</a> · <a href="https://profiles.wordpress.org/obliviousharmony/">obliviousharmony</a> · <a href="https://profiles.wordpress.org/oguzkocer/">oguzkocer</a> · <a href="https://profiles.wordpress.org/oglekler/">Olga Gleckler</a> · <a href="https://profiles.wordpress.org/oliverstapelfeldt/">Oliver Stapelfeldt</a> · <a href="https://profiles.wordpress.org/olliejones/">OllieJones</a> · <a href="https://profiles.wordpress.org/oneearth27/">oneearth27</a> · <a href="https://profiles.wordpress.org/onnimonni/">Onni Hakala</a> · <a href="https://profiles.wordpress.org/opr18/">opr18</a> · <a href="https://profiles.wordpress.org/ovidiul/">ovidiul</a> · <a href="https://profiles.wordpress.org/p_enrique/">p_enrique</a> · <a href="https://profiles.wordpress.org/paaljoachim/">Paal Joachim Romdahl</a> · <a href="https://profiles.wordpress.org/poliuk/">Pablo Postigo</a> · <a href="https://profiles.wordpress.org/pablohoney/">PabloHoney</a> · <a href="https://profiles.wordpress.org/palmiak/">palmiak</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/xparham/">Parham Ghaffarian</a> · <a href="https://profiles.wordpress.org/swissspidy/">Pascal Birchler</a> · <a href="https://profiles.wordpress.org/patrickgroot/">Patrick Groot</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/paulkevan/">Paul Kevan</a> · <a href="https://profiles.wordpress.org/figureone/">Paul Ryan</a> · <a href="https://profiles.wordpress.org/paulohcruz/">Paulo Cruz</a> · <a href="https://profiles.wordpress.org/paulopmt1/">Paulo Trentin</a> · <a href="https://profiles.wordpress.org/pavanpatil1/">Pavan Patil</a> · <a href="https://profiles.wordpress.org/pavelschoffer/">pavelschoffer</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/westi/">Peter Westwood</a> · <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a> · <a href="https://profiles.wordpress.org/petitphp/">petitphp</a> · <a href="https://profiles.wordpress.org/walbo/">Petter Walbø Johnsgård</a> · <a href="https://profiles.wordpress.org/johnstonphilip/">Phil Johnston</a> · <a href="https://profiles.wordpress.org/phillsav/">Phill</a> · <a href="https://profiles.wordpress.org/strategio/">Pierre Sylvestre</a> · <a href="https://profiles.wordpress.org/nekojonez/">Pieterjan Deneys</a> · <a href="https://profiles.wordpress.org/boniu91/">Piotrek Boniu</a> · <a href="https://profiles.wordpress.org/mordauk/">Pippin Williamson</a> · <a href="https://profiles.wordpress.org/webtechpooja/">Pooja Derashri</a> · <a href="https://profiles.wordpress.org/pooja1210/">Pooja N Muchandikar</a> · <a href="https://profiles.wordpress.org/praful2111/">Praful Patel</a> · <a href="https://profiles.wordpress.org/pratiweb/">Pratiksha</a> · <a href="https://profiles.wordpress.org/nikeo/">presscustomizr</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/priyomukul/">Priyo Mukul</a> · <a href="https://profiles.wordpress.org/prokium/">prokium</a> · <a href="https://profiles.wordpress.org/itsjonq/">Q</a> · <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a> · <a href="https://profiles.wordpress.org/larrach/">Rachel Peter</a> · <a href="https://profiles.wordpress.org/raduiason/">raduiason</a> · <a href="https://profiles.wordpress.org/rafiahmedd/">Rafi Ahmed</a> · <a href="https://profiles.wordpress.org/tan007/">Rahi Prajapati</a> · <a href="https://profiles.wordpress.org/rajanpanchal2028/">Rajan Panchal</a> · <a href="https://profiles.wordpress.org/rajeshraval786/">Rajesh Raval</a> · <a href="https://profiles.wordpress.org/ralucastn/">ralucastn</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/rcorrales/">Ramon Corrales</a> · <a href="https://profiles.wordpress.org/ramon-fincken/">ramon fincken</a> · <a href="https://profiles.wordpress.org/ramonopoly/">Ramon James</a> · <a href="https://profiles.wordpress.org/randhirexpresstech/">randhirexpresstech</a> · <a href="https://profiles.wordpress.org/ravipatel/">Ravikumar Patel</a> · <a href="https://profiles.wordpress.org/rcanepa/">rcanepa</a> · <a href="https://profiles.wordpress.org/rebasaurus/">rebasaurus</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/renathoc/">Renatho (a11n)</a> · <a href="https://profiles.wordpress.org/renegeuze/">renegeuze</a> · <a href="https://profiles.wordpress.org/laboiteare/">Reuhno</a> · <a href="https://profiles.wordpress.org/rflw/">rflw</a> · <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a> · <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a> · <a href="https://profiles.wordpress.org/rinatkhaziev/">Rinat</a> · <a href="https://profiles.wordpress.org/rinkychowdhury9/">Rinky Chowdhury</a> · <a href="https://profiles.wordpress.org/rishishah/">Rishi Shah</a> · <a href="https://profiles.wordpress.org/rkaiser0324/">rkaiser0324</a> · <a href="https://profiles.wordpress.org/noisysocks/">Robert Anderson</a> · <a href="https://profiles.wordpress.org/miqrogroove/">Robert Chapin</a> · <a href="https://profiles.wordpress.org/robertghetau/">robertght</a> · <a href="https://profiles.wordpress.org/robinwpdeveloper/">Robin</a> · <a href="https://profiles.wordpress.org/robmiller/">robmiller</a> · <a href="https://profiles.wordpress.org/rodrigosevero/">rodrigosevero</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/rollybueno/">rollybueno</a> · <a href="https://profiles.wordpress.org/rherault/">Romain Herault</a> · <a href="https://profiles.wordpress.org/romulodl/">romulodl</a> · <a href="https://profiles.wordpress.org/ross_ritchey/">ross_ritchey</a> · <a href="https://profiles.wordpress.org/lev0/">Roy</a> · <a href="https://profiles.wordpress.org/geekstreetwp/">Russell Aaron</a> · <a href="https://profiles.wordpress.org/ryan/">Ryan Boren</a> · <a href="https://profiles.wordpress.org/rmccue/">Ryan McCue</a> · <a href="https://profiles.wordpress.org/ryanmurphy/">Ryan Murphy</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/sergiomdgomes/">S&#233;rgio Gomes</a> · <a href="https://profiles.wordpress.org/soean/">S&#246;ren Wrede</a> · <a href="https://profiles.wordpress.org/sabbirmc/">Sabbir Ahmed</a> · <a href="https://profiles.wordpress.org/sajjad67/">Sajjad Hossain Sagor</a> · <a href="https://profiles.wordpress.org/saggre/">Sakri Koskimies</a> · <a href="https://profiles.wordpress.org/samikeijonen/">Sami Keijonen</a> · <a href="https://profiles.wordpress.org/viralsampat/">Sampat Viral</a> · <a href="https://profiles.wordpress.org/otto42/">Samuel Wood (Otto)</a> · <a href="https://profiles.wordpress.org/sandipmondal/">Sandip Mondal - a11n</a> · <a href="https://profiles.wordpress.org/sandrasanzdev/">Sandra Sanz</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/sarahricker/">sarahricker</a> · <a href="https://profiles.wordpress.org/sathyapulse/">Sathiyamoorthy V</a> · <a href="https://profiles.wordpress.org/isaumya/">Saumya Majumder</a> · <a href="https://profiles.wordpress.org/xconsau/">Saurabh Sharma</a> · <a href="https://profiles.wordpress.org/scofennellgmailcom/">Scott Fennell</a> · <a href="https://profiles.wordpress.org/sc0ttkclark/">Scott Kingsley Clark</a> · <a href="https://profiles.wordpress.org/gmagicscott/">Scott Lesovic</a> · <a href="https://profiles.wordpress.org/wonderboymusic/">Scott Taylor</a> · <a href="https://profiles.wordpress.org/scribu/">scribu</a> · <a href="https://profiles.wordpress.org/sean212/">Sean Fisher</a> · <a href="https://profiles.wordpress.org/sebastianpisula/">Sebastian Pisula</a> · <a href="https://profiles.wordpress.org/monolithon/">seieric</a> · <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a> · <a href="https://profiles.wordpress.org/seedsca/">Sergio Scabuzzo</a> · <a href="https://profiles.wordpress.org/seriouslysenpai/">seriouslysenpai</a> · <a href="https://profiles.wordpress.org/sethta/">Seth Alling</a> · <a href="https://profiles.wordpress.org/shanjidah/">shangidah afroz</a> · <a href="https://profiles.wordpress.org/enchiridion/">Shannon Little</a> · <a href="https://profiles.wordpress.org/sharjeelkhanvmi/">Sharjeel Khan</a> · <a href="https://profiles.wordpress.org/shetheliving/">shetheliving</a> · <a href="https://profiles.wordpress.org/shoaibkarimali/">Shoaib Ali</a> · <a href="https://profiles.wordpress.org/shraboni/">Shraboni</a> · <a href="https://profiles.wordpress.org/shreyasikhar26/">Shreyas Ikhar</a> · <a href="https://profiles.wordpress.org/shuvo586/">shuvo586</a> · <a href="https://profiles.wordpress.org/rsiddharth/">siddharth ravikumar</a> · <a href="https://profiles.wordpress.org/nomnom99/">Siddharth Thevaril</a> · <a href="https://profiles.wordpress.org/siobhyb/">Siobhan</a> · <a href="https://profiles.wordpress.org/sirzooro/">sirzooro</a> · <a href="https://profiles.wordpress.org/slaffik/">Slava Abakumov</a> · <a href="https://profiles.wordpress.org/slobodanmanic/">Slobodan Manic</a> · <a href="https://profiles.wordpress.org/smit08/">Smit Rathod</a> · <a href="https://profiles.wordpress.org/sobatkras/">sobatkras</a> · <a href="https://profiles.wordpress.org/khromov/">Stanislav Khromov</a> · <a href="https://profiles.wordpress.org/steelwagstaff/">SteelWagstaff</a> · <a href="https://profiles.wordpress.org/ste_95/">Stefano</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/camwynsp/">Stephen Page</a> · <a href="https://profiles.wordpress.org/sterlo/">Sterling Hamilton</a> · <a href="https://profiles.wordpress.org/stevenlinx/">Steven Lin</a> · <a href="https://profiles.wordpress.org/steveo2000/">steveo2000</a> · <a href="https://profiles.wordpress.org/studiolxv/">studiolxv</a> · <a href="https://profiles.wordpress.org/sumitbagthariya16/">Sumit Bagthariya</a> · <a href="https://profiles.wordpress.org/sumitsingh/">Sumit Singh</a> · <a href="https://profiles.wordpress.org/5um17/">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/cybr/">Sybre Waaijer</a> · <a href="https://profiles.wordpress.org/synchro/">Synchro</a> · <a href="https://profiles.wordpress.org/system909/">system909</a> · <a href="https://profiles.wordpress.org/tahmidulkarim/">Tahmid ul Karim</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/devtanbir/">Tanbir Ahmod</a> · <a href="https://profiles.wordpress.org/tanvirul/">Tanvirul Haque</a> · <a href="https://profiles.wordpress.org/taskotr/">Taras Dashkevych</a> · <a href="https://profiles.wordpress.org/targz/">targz</a> · <a href="https://profiles.wordpress.org/tlovett1/">Taylor Lovett</a> · <a href="https://profiles.wordpress.org/tazotodua/">tazotodua</a> · <a href="https://profiles.wordpress.org/tbember/">tbember</a> · <a href="https://profiles.wordpress.org/tykoted/">Teddy Patriarca</a> · <a href="https://profiles.wordpress.org/tellyworth/">Tellyworth</a> · <a href="https://profiles.wordpress.org/edent/">Terence Eden</a> · <a href="https://profiles.wordpress.org/tharsheblows/">tharsheblows</a> · <a href="https://profiles.wordpress.org/iamjaydip/">thejaydip</a> · <a href="https://profiles.wordpress.org/tweetythierry/">Thierry Muller</a> · <a href="https://profiles.wordpress.org/thijso/">Thijs</a> · <a href="https://profiles.wordpress.org/griffinjt/">Thomas Griffin</a> · <a href="https://profiles.wordpress.org/hyperbrand/">Thorsten Schraut</a> · <a href="https://profiles.wordpress.org/threadi/">threadi</a> · <a href="https://profiles.wordpress.org/baxbridge/">Tiffany Bridge</a> · <a href="https://profiles.wordpress.org/tillkruess/">Till Kr&#252;ss</a> · <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a> · <a href="https://profiles.wordpress.org/tmooredev/">Titus Moore</a> · <a href="https://profiles.wordpress.org/tobiasbg/">TobiasBg</a> · <a href="https://profiles.wordpress.org/tobifjellner/">tobifjellner (Tor-Bjorn Fjellner)</a> · <a href="https://profiles.wordpress.org/tomjdv/">Tom de Visser</a> · <a href="https://profiles.wordpress.org/tjnowell/">Tom J Nowell</a> · <a href="https://profiles.wordpress.org/tj692/">Tom Janssen</a> · <a href="https://profiles.wordpress.org/tommusrhodus/">Tom Rhodes</a> · <a href="https://profiles.wordpress.org/tomasztunik/">Tomasz Tunik</a> · <a href="https://profiles.wordpress.org/tomepajk/">tomepajk</a> · <a href="https://profiles.wordpress.org/shimotomoki/">Tomoki Shimomura</a> · <a href="https://profiles.wordpress.org/skithund/">Toni Viemer&#246;</a> · <a href="https://profiles.wordpress.org/tonylocalword/">tony.localword</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/transl8or/">transl8or</a> · <a href="https://profiles.wordpress.org/wpsmith/">Travis Smith</a> · <a href="https://profiles.wordpress.org/tremidkhar/">Tremi Dkhar</a> · <a href="https://profiles.wordpress.org/trevorpfromsandee/">TrevorPolischuk</a> · <a href="https://profiles.wordpress.org/nathannoom/">Trinadin</a> · <a href="https://profiles.wordpress.org/dinhtungdu/">Tung Du</a> · <a href="https://profiles.wordpress.org/turtlepod/">turtlepod</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/umesh84/">Umesh Gupta</a> · <a href="https://profiles.wordpress.org/upadalavipul/">upadalavipul</a> · <a href="https://profiles.wordpress.org/utsavmadaan823/">utsavmadaan823</a> · <a href="https://profiles.wordpress.org/eboxnet/">Vagelis</a> · <a href="https://profiles.wordpress.org/evildon/">varma</a> · <a href="https://profiles.wordpress.org/vasartam/">vasartam</a> · <a href="https://profiles.wordpress.org/vdankbaar/">vdankbaar</a> · <a href="https://profiles.wordpress.org/velochicdunord/">Velochicdunord</a> · <a href="https://profiles.wordpress.org/vcanales/">Vicente Canales</a> · <a href="https://profiles.wordpress.org/vikasprogrammer/">vikasprogrammer</a> · <a href="https://profiles.wordpress.org/virgar/">Virginie Garnier</a> · <a href="https://profiles.wordpress.org/vishalkakadiya/">Vishal Kakadiya</a> · <a href="https://profiles.wordpress.org/vortfu/">vortfu</a> · <a href="https://profiles.wordpress.org/webbeetle/">webbeetle</a> · <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a> · <a href="https://profiles.wordpress.org/whaze/">whaze</a> · <a href="https://profiles.wordpress.org/whissi/">Whissi</a> · <a href="https://profiles.wordpress.org/earnjam/">William Earnhardt</a> · <a href="https://profiles.wordpress.org/williampatton/">williampatton</a> · <a href="https://profiles.wordpress.org/withinboredom/">withinboredom</a> · <a href="https://profiles.wordpress.org/woji29911/">woji29911</a> · <a href="https://profiles.wordpress.org/yahil/">Yahil Madakiya</a> · <a href="https://profiles.wordpress.org/yannielsen/">Yan Knudtskov</a> · <a href="https://profiles.wordpress.org/collet/">Yann</a> · <a href="https://profiles.wordpress.org/yoavf/">Yoav Farhi</a> · <a href="https://profiles.wordpress.org/byohann6/">Yohann Billard</a> · <a href="https://profiles.wordpress.org/fierevere/">Yui</a> · <a href="https://profiles.wordpress.org/omaeyusuke/">yuu</a> · <a href="https://profiles.wordpress.org/zaerl/">zaerl</a> · <a href="https://profiles.wordpress.org/zebulan/">Zebulan Stanphill</a> · <a href="https://profiles.wordpress.org/zenaulislam/">Zenaul Islam</a> · <a href="https://profiles.wordpress.org/ziposc/">ziposc</a> · <a href="https://profiles.wordpress.org/chesio/">Česlav Przywara</a> · <a href="https://profiles.wordpress.org/shenyanzhi/">沈唁</a></p><br /></code></pre>



<p>WordPress 6.1 would not have been possible without the contributions of more than 800 people in over 60 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>By release day, 71 locales had translated 90-percent or more of WordPress 6.1 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 over 200 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>Haiku Fun for 6.1</h2>



<p>Another release,<br />Mark it down as completed.<br />Breathe, relax, and cheers!</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, 01 Nov 2022 18:38: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: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: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:54:"Do The Woo Community: Around the Woo Builder 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=73400";s: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:53:"https://dothewoo.io/around-the-woo-builder-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:389:"<p>Discovering what people are doing and thinking in the WooCommerce Builder Community and what you can learn from their insights.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/around-the-woo-builder-community/">Around the Woo Builder 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:"Tue, 01 Nov 2022 10:03: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: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:83:"WPTavern: New Missing Menu Items Plugin Adds Site Building Links to WordPress Admin";s: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=139048";s: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:94:"https://wptavern.com/new-missing-menu-items-plugin-adds-site-building-links-to-wordpress-admin";s: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:2904:"<p>If you are going all in on building sites with the new full-site editing (FSE) experience, then you may have noticed a lack of menu items that will deliver you directly to the tools you need to use. </p>



<p>It may be because the Site Editor is still in beta, or because WordPress leadership may still be <a href="https://wptavern.com/wordpress-contributors-consider-renaming-full-site-editing">discussing whether to rename FSE</a>. Perhaps it&#8217;s better that users don&#8217;t blindly stumble into FSE templates from the main admin menu, but some of these site building features are buried away with no quick access. </p>



<p>For example, you are three clicks deep before arriving at Template Parts. Managing reusable blocks is also a tucked away on a separate screen that can be accessed through the post editor but sends you to a new page. </p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">If you're using the block editor, and reusable blocks<br /><br />Do yourself a favor cut and paste this at the end of your website: <br /><br />/wp-admin/edit.php?post_type=wp_block<br /><br />Then bookmark it.</p>&mdash; Ben LayerWP &amp; WPDeals.email (@benswrite) <a href="https://twitter.com/benswrite/status/1585257042406957058?ref_src=twsrc%5Etfw">October 26, 2022</a></blockquote>
</div>



<p>When LayerWP founder Ben Townsend brought attention to this in a tweet, Roy Sivan responded with a link to a new free plugin that creates quicker access to these menus.</p>



<p><a href="https://wordpress.org/plugins/missing-menu-items/">Missing Menu Items</a> expands the admin menu with links to reusable blocks, navigation menus, templates, and template parts, so they are all one click away. It adds them to the Appearance menu under the Editor (beta) link:</p>



<img />



<p>If you are regularly working with Reusable blocks or editing navigation and templates, this plugin will save you some time and help you zip around the editor faster.  </p>



<img />



<p>Missing Menu Items was made by <a href="https://easilyamusedinc.com/">Easily Amused</a>, the creators of <a href="https://blockstyles.com/">Block Styles</a>, a commercial plugin that lets users further customize core blocks with unique styles and boasts “fully responsive block-level design control.&#8221; The team will be adding more useful menu links and admin improvements in future releases. Users can <a href="https://blockstyles.com/contact/">contact</a> the development team with menu item requests and they will consider them. </p>



<p><a href="https://wordpress.org/plugins/missing-menu-items">Missing Menu Items</a> is available on WordPress.org. Direct support is available for those who have purchased a <a href="https://blockstyles.com/">BlockStyles</a> membership, and community support can be found in the plugin&#8217;s forums on the directory.</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, 01 Nov 2022 03:15: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: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:64:"WordPress.org blog: People of WordPress: Raghavendra Satish Peri";s: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=13705";s: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:79:"https://wordpress.org/news/2022/10/people-of-wordpress-raghavendra-satish-peri/";s: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:12327:"<p><strong>This month, in the run up to WordPress Accessibility Day, we feature Raghavendra Satish Peri, a blogger turned digital entrepreneur based in India, who specializes</strong> <strong>in web accessibility and digital marketing</strong>.</p>



<p><strong>The People of WordPress series shares inspiring stories of how people&#8217;s lives can change for the better through WordPress and its global network of contributors.</strong></p>



<img width="1014" height="627" src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-featured-img.jpg?resize=1014%2C627&ssl=1" alt="Raghavendra speaking at a Blogger event, 2015." class="wp-image-13701" />Raghavendra speaking at a blogger event, 2015



<h2>Expressing myself through WordPress</h2>



<p>Raghavendra Satish Peri says WordPress is more than a way to succeed online. It&#8217;s a community that has always answered his questions and helped him learn, and has enabled his voice to be heard across the world.</p>



<p>These are motivating benefits for Raghavendra, who has a vision impairment that introduces challenges to many of the things he wants to do. The WordPress community has helped him make some of his dreams come true. After chatting with others at WordPress events, about his wish to go trekking and running, he found he was later contacted by people in the community went with him to do just that.</p>



<img width="534" height="748" src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-3.jpg?resize=534%2C748&ssl=1" alt="Raghavendra training for a marathon in 2013." class="wp-image-13702" />Raghavendra training for a marathon in 2013



<p>He also found WordPress events a way to raise the importance of accessibility issues, share tips, and connect local communities so they can collaborate on items both within and outside WordPress.</p>



<h2>Life growing up with an enabling family</h2>



<p>A key asset for Raghavendra has been the support of his family as he coped with his progressive blindness. His sister took charge of teaching him important social and life skills, so he could navigate his country&#8217;s rigorous education system.</p>



<p>Those were the early days of technology everywhere, and nobody much was thinking about using it in education and day-to-day life.</p>



<p>When Raghavendra got his first computer, in 2004, it was a revelation. His sister taught him to use the internet efficiently, and he taught himself a few basics of programming. Soon he was spending 10 to 12 hours a day exploring the online world and learning about the web.</p>



<h2>Discovering WordPress and blogging</h2>



<p>In 2006, he learned basic web design and began to sell website templates. His growing interest in search engines and content led him to WordPress. As the years progressed, his eyesight deteriorated. He had to relearn his skills and acquire new ones to compensate. When he could no longer see the computer screen, he learnt to use screen readers.&nbsp;</p>



<p>At that point there was a gap: he had the same business skills, but he couldn&#8217;t apply them as effectively until he got comfortable with using screen readers.&nbsp;</p>



<img width="800" height="534" src="https://i0.wp.com/wordpress.org/news/files/2022/10/4.jpg?resize=800%2C534&ssl=1" alt="Raghavendra speaking at an event in Bangalore, India in 2014. Photo Credit: Two Feet To Fly - fLaShBuLbZz Photography" class="wp-image-13790" />Raghavendra speaking at an event in Bengalaru, India in 2014



<p>To help achieve that, Raghavendra moved to Bengalaru, where he got a full education in screen-reader technology and took a job as a consultant in digital accessibility.</p>



<p>He recalls learning from that time that, in his words: “Some things are important, but one needs to let them go so that more important things can take the new space.”</p>



<p>During his stay in Bengaluru, he stumbled on the idea of blogging and audiobooks. On his 23rd birthday, he had two firsts: registering a domain and publishing a blog post. At first he wrote about things happening in his daily life, which initially got low responses. But when he started attending blogging and tech meetups, he received encouragement from fellow bloggers who complimented him on his writing style. </p>



<p>Using WordPress to publish his story, Raghavendra found a love for writing and this made him want to learn and understand WordPress much better.</p>



<blockquote class="wp-block-quote">
<h2>“Writing freed my mind and soul from the pain and sorrow; it takes a person into a Zen state where one can understand their soul once they see their own thoughts on paper.”</h2>
<cite>Raghavendra Satish Peri</cite></blockquote>



<p>There were still some ongoing challenges arising from his difficulties with seeing. For example, Raghavendra found coding was made more complicated. But he took it slowly, and he improved steadily.&nbsp;</p>



<p>He started as many WordPressers do, installing themes and plugins, and making minor changes to the code. Ultimately, he moved all of his sites to WordPress, and as he learned more about WordPress, he could help his friends and family more with their projects.</p>



<p>After just a few years, Raghavendra had the skills and the confidence to build just about anything in WordPress, progressing from simple to complex websites.</p>



<p>Today Raghavendra is a successful entrepreneur. He sees his life as full of promise. WordPress still helps him grow every day, professionally and personally.</p>



<blockquote class="wp-block-quote">
<p>“There is always hope for tomorrow! Do not look for the light at the end of the tunnel, embrace the darkness, listen to the quietness, and feel the airflow. You will know that light is ahead even before you see it.&#8221;&nbsp;</p>
<cite>Raghavendra Satish Peri</cite></blockquote>



<h2>Contribute to accessibility and WordPress</h2>



<p>Another thing Raghavendra has in common with many WordPressers is his enthusiasm and involvement in the community. As he has learnt more about the software, he felt he needed to be involved with improving accessibility too. He started to help organize local meetups and conferences and encourages others to give time and skills to contribute too.&nbsp;</p>



<img width="704" height="500" src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-5.jpg?resize=704%2C500&ssl=1" alt="2016, Raghavendra on stage speaking at WordCamp Mumbai" class="wp-image-13699" />2016, Raghavendra speaking at WordCamp Mumbai



<p>He follows software development closely, especially where WordPress meets accessibility.</p>



<p>In 2020, on learning about a global WordPress Accessibility event, he applied and became a speaker. His topic was <a href="https://youtu.be/bvgLjWCRfrQ">Gutenberg Accessibility, A Screen Reader User&#8217;s Perspective</a>. His interest continued as a result of this event, and he wanted to be part of growing its audience and impact, initially through joining its dedicated channel on Slack. Eventually, he joined the organizing team for future events.</p>



<p>Helping run WordPress events brought together all of Raghavendra&#8217;s existing skills. It taught him a lot about what it takes to make an event truly inclusive, from captions and sign language to media players and more.&nbsp;</p>



<p>As his involvement has grown, Raghavendra has found it has become easier to source and use resources that make events and presentations more accessible. But knows there&#8217;s always more that can be learnt in this area, and encourages others to use understanding from events like the Accessibility Days in their conferences.</p>



<p>Join the global WordPress Accessibility Day 2022 online on November 2-3, 2022.&nbsp;It&#8217;s <a href="https://wpaccessibility.day/">free to register</a>!</p>



<a href="https://wpaccessibility.day/" target="_blank" rel="noreferrer noopener"><img width="568" height="173" src="https://i0.wp.com/wordpress.org/news/files/2022/10/wp-accessibility-day-22.png?resize=568%2C173&ssl=1" alt="WordPress Accessibility Day 2022 logo in purple and turquoise" class="wp-image-13783" /></a>



<h2><br />Sharing learning on accessibility can be a motivator </h2>



<p>In 2021, Raghavendra underwent his most challenging event to date, when he had a kidney transplant. To motivate himself, he started a website that focuses on accessibility and inclusive design. This prompted him to start an accessibility community to help fill the gaps in accessibility knowledge. Today, it is one of India’s largest online accessibility communities, educating developers and designers and training people with disabilities to build a career in accessibility testing.</p>



<img src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-6.jpg?resize=680%2C790&ssl=1" alt="Portrait photo of Raghavendra post his organ transplant, 2021." class="wp-image-13698" width="680" height="790" />Raghavendra after his organ transplant in 2021



<p>Raghavendra is also a keen user of the WordPress Gutenberg editor and builds all his websites using it. Though content creation and editing can still pose him difficulties, he finds the front end of the Gutenberg blocks very accessible. He believes in participating in the software to make it a better experience for all.</p>



<blockquote class="wp-block-quote">
<p>&#8220;I decided to live my life to the fullest and make my mark on the world. This thought keeps me motivated.&#8221;</p>
<cite>Raghavendra Satish Peri</cite></blockquote>



<p>After a successful transplant, he lives a disciplined life with a few restrictions. He continues to enjoy working in-depth in disability, accessibility, and inclusion spaces. Raghavendra hopes others will join with him and the thousands of other people who collaborate to make a difference.</p>



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



<p>Thank you to Raghavendra Satish Peri (<a href="https://profiles.wordpress.org/tarkham/" class="mention"><span class="mentions-prefix">@</span>tarkham</a>) for sharing his experiences for this latest edition.</p>



<h2>Contributors</h2>



<p>Thanks to Meher Bala (<a href="https://profiles.wordpress.org/meher/" class="mention"><span class="mentions-prefix">@</span>meher</a>), Abha Thakor (<a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</a>) and Surendra Thakor (<a href="https://profiles.wordpress.org/sthakor/" class="mention"><span class="mentions-prefix">@</span>sthakor</a>) for interviews and writing this feature, to 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>), and Larissa Murillo (<a href="https://profiles.wordpress.org/lmurillom/" class="mention"><span class="mentions-prefix">@</span>lmurillom</a>) for reviews.</p>



<p>The <em>People of WordPress</em> series thanks 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 their support.</p>



<div class="wp-block-media-text is-stacked-on-mobile is-vertically-aligned-center"><img width="180" height="135" src="https://i0.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>";s: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, 31 Oct 2022 19: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:10:"Meher Bala";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:56:"Do The Woo Community: Twitter. Will I Go or Will I Stay?";s: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=73393";s: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:53:"https://dothewoo.io/twitter-will-i-go-or-will-i-stay/";s: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:382:"<p>In the last day or two I have seen a bit more people closing their Twitter accounts. What about Do the Woo on Twitter.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/twitter-will-i-go-or-will-i-stay/">Twitter. Will I Go or Will I Stay?</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:"Mon, 31 Oct 2022 14:59:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:76:"WordPress.org blog: WP Briefing: Episode 42: Something Spooky This Way Comes";s: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=13666";s: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:78:"https://wordpress.org/news/2022/10/episode-42-something-spooky-this-way-comes/";s: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:12472:"<p>In the forty-second episode of the WordPress Briefing podcast, Josepha Haden Chomphosy reads a WordPress Halloween story completed by contributor-submitted Mad Libs. </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>Credits</h2>



<p>Editor:&nbsp;<a href="https://profiles.wordpress.org/dustinhartzler/">Dustin Hartzler</a><br />Logo:&nbsp;<a href="https://profiles.wordpress.org/javiarce/">Javier Arce</a><br />Production:&nbsp;<a href="https://profiles.wordpress.org/santanainniss/">Santana Inniss</a><br />Music: Spooky edit by <a href="https://goodnightnobody.space/">Timothy Volpert</a><br />Mad Lib Contributors: <a href="https://profiles.wordpress.org/juanlucha/">Juan Lucha</a>, <a href="https://profiles.wordpress.org/laurlittle/">Lauren Stein</a>, <a href="https://profiles.wordpress.org/robinwpdeveloper/">robinwpdeveloper</a>, <a href="https://profiles.wordpress.org/bph/">Birgit Pauli-Haack</a>, <a href="https://profiles.wordpress.org/aetherunbound/">Madison Swain-Bowden</a>, <a href="https://profiles.wordpress.org/kgagne/">Ken Gagne</a>, <a href="https://profiles.wordpress.org/juliarosia/">Julia Golomb</a>, <a href="https://profiles.wordpress.org/kawserz/">kawserz</a>, <a href="https://profiles.wordpress.org/sereedmedia/">Sé Reed</a>, <a href="https://profiles.wordpress.org/faguni22/">Mumtahina Faguni</a>, <a href="https://www.linkedin.com/in/cleamahoney/">Clea Mahoney</a></p>



<h2>Download Mad Libs:</h2>



<div class="wp-block-file"><a id="wp-block-file--media-bbc1dbb2-b633-4e46-b53b-4440a449cac4" href="https://wordpress.org/news/files/2022/10/WP-Briefing-Halloween-Mad-Libs.pdf">WP-Briefing-Halloween-Mad-Libs</a><a href="https://wordpress.org/news/files/2022/10/WP-Briefing-Halloween-Mad-Libs.pdf" class="wp-block-file__button wp-element-button">Download</a></div>



<h2>References</h2>



<p><a href="https://make.wordpress.org/core/6-1/">Important Note: WordPress 6.1 is released tomorrow!</a><br /><a rel="noreferrer noopener" href="https://make.wordpress.org/core/2022/10/20/multisite-registration-and-activation-pages-have-new-html-and-css/" target="_blank">Multisite registration and activation pages have new HTML and CSS</a><br /><a rel="noreferrer noopener" href="https://make.wordpress.org/mobile/2022/10/18/call-for-testing-wordpress-for-android-21-0/" target="_blank">Call for Testing: WordPress for Android 21.0</a><br /><a rel="noreferrer noopener" href="https://make.wordpress.org/docs/2022/10/19/new-design-for-helphub-in-wordpress-org/" target="_blank">New design for HelpHub in WordPress.org</a><br /><a rel="noreferrer noopener" href="https://make.wordpress.org/meta/2022/10/21/wordpress-org-redesign-update/" target="_blank">WordPress.org Redesign Update</a><br /><a rel="noreferrer noopener" href="https://make.wordpress.org/test/2022/10/15/fse-program-guiding-the-gutenberg-gallery-summary/" target="_blank">FSE Program Guiding the Gutenberg Gallery Summary</a></p>



<h2>Transcript</h2>



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



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



<p>Howdy, Halloween nerds! And welcome to the WordPress Briefing, a podcast where I&#8217;m normally very serious, but today is Halloween! And gosh, do I love a chance to celebrate. So today, the most serious thing I have is this WordPress themed Halloween Madlib for you. I&#8217;m your host, Josepha Haden Chomphosy. Here we go.</p>



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



<p>I was so excited to learn that WordCamp would be on Halloween this year, and now it&#8217;s finally here. After a full day of workshops and mingling, I am exhausted. But I&#8217;ve got just enough time to return to the hotel and prepare for the after party. It&#8217;s a themed costume event organized by the Docs team, and I cannot wait.</p>



<p>Walking into my room, I give a big yawn and realize just how tired I am. The bed is looking extra comfortable right now. Surely a little nap wouldn&#8217;t hurt, right? As soon as my head hits the pillow, I&#8217;m out like a light, but almost immediately, my eyes snap back open, a flash of lightning lights up the room, and I hear rain pouring down outside.</p>



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



<p>After another flash, the lights in the room start to flicker. That&#8217;s strange, I think to myself, but I have an after party to get to. There must have been a power surge because when I look back at the clock, it&#8217;s reset and flashing 12:00 am. I check my phone, but it&#8217;s dead too. I&#8217;m not quite sure how long I&#8217;ve been sleeping, so I don&#8217;t know if I have enough time to change into my full Ninja Turtles costume.</p>



<p>I just put the mask on and head down to the lobby to meet my WordPress friends. When the elevator dings open in the lobby, it&#8217;s completely empty. No concierge, no hotel staff, and no WordPress friends. That&#8217;s weird. The lights also seem dimmer. And, are those urgent Trac tickets on the lobby lounge chairs?</p>



<p>I&#8217;m wondering where everybody is, but I keep walking toward the convention hall. A shadow suddenly moves in the corner of my eye, and I spin around but only see my own face reflecting in a hallway mirror. Hmm, that&#8217;s odd. I notice that the cute Ninja Turtle mask looks a little less cute somehow. The eyes are angry red, and the teeth are now sharp-looking fangs.</p>



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



<p>Before I can take off the mask for a closer look, I see another shadow move in the corner of the mirror. When I turn around this time, I see the faint outline of a person. It looks familiar. Could that be Matt Mullenweg? Darn it. They disappear into the convention hall before I can even call out, ‘howdy!’ And so I break into a jog to follow after them.</p>



<p>Walking into the hall, I can hear the musical stylings of WordPress Jazzer Duke Ellington playing on a gramophone. I bob my head to the music, super relieved to see the room full of WordPressers dressed up and dancing. I head over to some of the folks from my Make team to chat, but oddly, they won&#8217;t stop dancing. They&#8217;re smiling and dancing and cheering each other on.</p>



<p>Some of them are even doing the electric slide. It&#8217;s actually kind of impressive, but it&#8217;s still a little strange that no one will stop dancing to talk to me. Actually, now that I think about it, none of the party goers seem to be noticing me at all. Wondering what&#8217;s going on, I start backing up toward the door.</p>



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



<p>I jump a little as it slams behind me with the loud sound of an old door creaking and the heavy click of a lock.</p>



<p>That&#8217;s when I noticed the shadowy familiar figure again. This time they&#8217;re standing by an open door on the other side of the hall. They seem to be watching me. They lift a white gloved hand and motion for me to follow before disappearing through the door again.</p>



<p>I run after the mysterious figure weaving between groups of dancing WordCamp goers. Could they be under a spell, I wonder while running past. I exit the convention space and enter a small hallway that seems to twist and turn. It feels a lot longer than I remember. I continue running through it and suddenly find myself back in the Contributor Day conference room.</p>



<p>The shadow person is nowhere to be found, and as I walk around the contributor tables, I quickly notice that the exit back to the hotel has also disappeared. Okay, so this is getting really weird. My first thought is to get my Make team involved, but since they won&#8217;t stop dancing, I know I need to devise a different plan.</p>



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



<p>That&#8217;s when I noticed the big glass box at the center of the room. I am almost certain it wasn&#8217;t there during Contributor Day. I approach the box cautiously. Inside I see a shiny silver goblet of gently fizzing WordPress blue liquid, possibly blueberry flavored if I had to guess. Attached to the goblet stem is a ribbon with a note in EB Garamond that reads: Merge Me.</p>



<p>At first, I chuckle at the poor attempt at a GitHub joke until I spot another note scrolled on the glass in black marker. It says,&nbsp;</p>



<p><em>Bubble, bubble, toil, and trouble;</em><br /><em>Find your escape route on the double;&nbsp;</em><br /><em>Bring back the community and one thing more;&nbsp;</em><br /><em>Merge the elixir with your core.&nbsp;</em></p>



<p>As I&#8217;m trying to decode the odd poem’s meaning, a flash of lightning lurches across the room, and a clap of thunder follows behind.</p>



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



<p>I shield my eyes before looking up to find that I am no longer alone. It&#8217;s the shadowy figure again, except in the light of this room, I can finally see that it&#8217;s not anyone familiar. It is a lumpy-looking being, and it&#8217;s wearing a witch costume. The costume-clad figure looks very unsteady on its feet like it might fall over.</p>



<p>And just as I&#8217;m about to ask if they&#8217;re all right, the person suddenly topples over into a heap of robes and broomsticks. I can see spots of yellow fur and a few pairs of fuzzy ears. Aha! There was a wisdom of Wapuus under that witchy costume.&nbsp;</p>



<p>They blink cutely at me for a moment and then quickly scurry into a surprisingly organized line. I watch, totally confused, as the line of Wapuus starts moving methodically back toward the convention hall. They take three steps, and then they turn to the side, take another three steps, and then turn to the other side.</p>



<p>The last Wapuu in the line turns to look at me and motions with its tiny paw to follow. That&#8217;s when the words on the glass box finally click. I have to bring the community back. All the dancing WordPressers need to return to the contributor tables to break the spell. The Wapuus have started a conga line to help lead the way.</p>



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



<p>So, off I go. Following the tiny conga line through the twisting hallway and into the convention hall. As I&#8217;m dancing behind the Wapuus, I&#8217;m happy to see all my fellow WordCamp attendees falling into step behind me. My steadily growing conga line is weaving its way through the hall, picking up WordPressers, wearing mouse costumes, and Frankensteins and penguin costumes, and that&#8217;s when the Wapuus changed their course, leading us back through the twisting hallway and into the Contributor Day conference room.</p>



<p>With the first part of the riddle solved, I&#8217;m glad to see that everyone has finally stopped dancing. Some folks are happy to sit down and get off their feet. Others are wondering how they ended up back in the contributor room. My Make team waves at me from across the room. I noticed there&#8217;s still no exit, but the glass box has disappeared. With the goblet free, there&#8217;s just one thing left for me to do.</p>



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



<p>I rush toward it, dodging Wapuus and a pile of kicked-off shoes. Except that the closer I think I&#8217;m getting to the goblet, the further away it feels. I run faster, weaving through people and tables, and just when I feel close enough to reach out for the goblet, I trip over a live-streaming cable, and I wake up in my hotel room.</p>



<p>Sitting up quickly, I realize it was all just a very strange dream. Outside, the sun is setting in a clear sky with no storm in sight. I try to shake it off. I change into my Ninja Turtles costume, ready to do my best Monster Mash at the after party with all of my WordPress friends. As I walk out of the hotel room, I pause for a quick costume check in the mirror.</p>



<p>Before heading downstairs, I take a quick glance at the digital clock on the nightstand to see the time. Huh, that&#8217;s odd. Next to the digital clock sits a fuzzy plush Wapuu wearing a witch costume. That wasn&#8217;t there before, was it? And if I didn&#8217;t know any better, I almost think I see it wink.&nbsp;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 31 Oct 2022 12:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:114:"Gutenberg Times: Gutenberg Changelog #75 – Gutenberg 14.4, Upcoming WordPress 6.1 Release, What’s Next for 6.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://gutenbergtimes.com/?post_type=podcast&p=22603";s: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:123:"https://gutenbergtimes.com/podcast/gutenberg-changelog-75-gutenberg-14-4-upcoming-wordpress-6-1-release-whats-next-for-6-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:59653:"<p>Anne McCarthy and Birgit Pauli-Haack discuss Gutenberg 14.4 WordPress 6.1 release and what’s next for WordPress 6.2.</p>



<p><a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-69-gutenberg-releases-wordpress-6-0-1-the-create-block-theme/#shownotes">Show Notes</a> / <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-69-gutenberg-releases-wordpress-6-0-1-the-create-block-theme/#transcript">Transcript</a></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>



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



<h2><strong>Anne McCarthy </strong></h2>



<ul>
<li><a href="https://profiles.wordpress.org/annezazu/">WordPress Profile</a> @annezazu</li>



<li><a href="https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/">FSE Outreach Program</a> </li>



<li><a href="https://make.wordpress.org/test/">WordPress Test team</a></li>
</ul>



<h2>Community Contributions</h2>



<ul>
<li><a href="https://artemiosans.com/2022/10/20/introducing-the-gutenberg-interactive-fiction-engine/comment-page-1/">Introduced Gutenberg Interactive Fiction Engine</a> by Artemio Morales</li>



<li><a href="https://gutenbergtimes.com/what-art-can-you-create-with-wordpress-6-1/">What art can you create with WordPress 6.1?</a> The Museum of Block Art is looking for submissions using WordPress 6.1 and the evolving design tools available.</li>
</ul>



<h2>WordPress 6.1 </h2>



<ul>
<li><a href="https://make.wordpress.org/core/2022/10/28/wordpress-6-1-release-candidate-5-rc5-now-available-for-testing/">WordPress 6.1 Release Candidate 5 (RC5) Now Available for Testing</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/">WordPress 6.1 Release Day Process</a></li>



<li><a href="https://make.wordpress.org/test/2022/09/21/help-test-wordpress-6-1/">Help Test WordPress 6.1</a></li>



<li>Dev note WordPress 6.1: <a href="https://make.wordpress.org/core/2022/10/10/extending-the-query-loop-block/">Extending the Query Loop block</a></li>
</ul>



<h2>Gutenberg 14.4</h2>



<ul>
<li><a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/">What’s new in Gutenberg 14.4? (26 October)</a></li>



<li><a href="https://wptavern.com/gutenberg-14-4-introduces-distraction-free-mode-redesigns-pattern-inserter">Gutenberg 14.4 Introduces Distraction-Free Mode, Redesigns Pattern Inserter</a>&nbsp;</li>
</ul>



<h2>Learn WordPress and other educational sources</h2>



<ul>
<li><a href="https://learn.wordpress.org/course/introduction-to-block-development-build-your-first-custom-block/">Introduction to Block Development: Build your first custom block</a>.</li>



<li><a href="https://learn.wordpress.org/course/using-the-wordpress-data-layer/">Using the WordPress data layer</a></li>



<li>2-part Series:  how to build a <a href="https://www.youtube.com/watch?v=3zJyjYIykQ4&list=PL6D-mnq0bpxMMSoVEiCdos86T7NUO8GoQ">custom WordPress block that supportsAdvanced Custom Fields</a> by Ryan Welcher</li>



<li>Video: <a href="https://www.youtube.com/watch?v=iCF5lssk_oY">Distraction-free mode: my new favorite way to write with the block editor</a></li>



<li><a href="https://developer.wordpress.org/block-editor/explanations/architecture/styles/#styles-in-the-block-editor">Styles in the block editor</a></li>



<li><a href="https://developer.wordpress.org/block-editor/how-to-guides/block-tutorial/extending-the-query-loop-block/">Extending the Query Loop block</a></li>
</ul>



<h2>What&#8217;s Next for 6.2?</h2>



<ul>
<li>GitHub Tracking Issue: <a href="https://github.com/WordPress/gutenberg/issues/33094">Phase 2: Customization</a></li>



<li><a href="https://wptavern.com/gutenberg-contributors-explore-a-new-browse-mode-for-navigating-the-site-editor">Gutenberg Contributors Explore a New Browse Mode for Navigating the Site Editor</a></li>



<li><a href="https://make.wordpress.org/test/2022/10/26/hallway-hangout-discussion-on-wrapping-phase-2-26-oct/">Hallway Hangout: Discussion on wrapping Phase 2 (26 Oct)</a></li>
</ul>



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



<div class="wp-block-group is-layout-flow"><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/gutenbergtimes">@gutenbergtimes </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-large-font-size" id="transcript"><strong>Transcript</strong></p>



<p><em>Birgit Pauli-Haack</em>: Hello and welcome to our 75th episode of the Gutenberg Changelog podcast. In today&#8217;s episode, we will talk about Gutenberg 14.4.0, upcoming WordPress 6.1 release, and what&#8217;s next for 6.2, and so much more. I&#8217;m Birgit Pauli-Haack, curator at the Gutenberg Times, contributor to the WordPress core team and documentation team, and WordPress developer advocate. And I&#8217;m here with Anne McCarthy, WordPress product liaison for WordPress open source project and triage co-lead for WordPress 6.1 release team. Good afternoon, Anne. How are you doing today? How are you doing?</p>



<p><em>Anne McCarthy</em>: I&#8217;m doing great. I&#8217;ve had extra coffee today and I&#8217;m very excited to talk about everything you have on your list. There&#8217;s a lot of fun and complex things happening that really help move WordPress in a solid direction. So we have a lot to cover.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And it&#8217;s going to be a great show, because it also needs to get everybody listeners kind of over the withdrawal that you will have. Yesterday, I looked at the calendar and realized that we will be on a November break almost for the Gutenberg Changelog. Work, travel, and holiday schedule is all going to interfere with our regular programming here. So I&#8217;m glad that Anne is here as my resident expert on all things WordPress 6.2 and we can talk a little bit about the future.</p>



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



<p>But first we have community contributions, and I found a blog post by Artemio Morales who calls himself an electronic literature creator, and he has introduced us to his Gutenberg interactive fiction engine. So what&#8217;s interactive fiction? It&#8217;s software simulating environments in which players use text commands to control characters and influence the environment. Works in this form can be understood as literary narratives either in the form of interactive narratives or interactive narration, that so far Wikipedia.</p>



<p>When using Artemio&#8217;s demo, all you see at the start is an image with some text and then three different links to continue that story. And depending on which link you click on, the story continues differently. So there are two paths. You go into the forest and then you come on two paths, one goes further deeper into the forest. Guess what happens now? Or you go down to the town and see how many people you see there. And these are the choices, and that&#8217;s how the story continues. Of course the creator part is coming up with all those different options and Gutenberg and the plugin that Artemio created helps you with putting the stories together. It&#8217;s really an interesting concept. And so he had some ideas on what you could do with it, and then you can choose your own adventure YouTube series for instance, or interactive comics or audio stories with branching pass, marketing or educational content, or even multimedia posts incorporating elements from all the above. So it was also interesting for me to read about the history of interactive fiction. So yeah, check it out. We will have the links in the show notes, of course.</p>



<p><em>Anne McCarthy</em>: Yeah, I think it&#8217;s such a neat thing that he&#8217;s working on and one of the things that I actually follow up with him whenever I saw that post too, because I run a side project along with a few other community members called the Museum of Block Art, where we create art with the WordPress block editor. And when he was describing and looking at the different interactive elements, I was like, man, you could really, the whole intent of the website right now is to have it be a virtual museum, and what would it look like to actually use this functionality on the Block Museum Site since it&#8217;s meant to be pushing the edges of WordPress and thinking really creatively. What would it look like if the experience of the museum itself was also pushing the limits of it? And it&#8217;s already using site editing and all this sort of stuff. But this would really, I think, take it to another creative element and make it a very, very meta kind of way, even more cutting edge. And so I&#8217;m hopeful that we can maybe get some functionality on there and demo it with the block museum as part of the efforts here.</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s an interesting idea. You kind of have different walks through the museums.</p>



<p><em>Anne McCarthy</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: It&#8217;s going to be really interesting. Yeah, I also could see that that maybe even be a story that is interactive narrative. Yeah, that&#8217;s a fiction and that&#8217;s posted as an art exhibit on it.</p>



<p><em>Anne McCarthy</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: So a writer can put something. Well, there is the November challenge of the National Writing Association or so coming up. Maybe that&#8217;s something to look into it. Yeah. And you mentioned the Block Museum, we had just on the Gutenberg Times, you published a submission to the virtual museum of block art using tools and features for WordPress 6.0. What exactly are you looking for?&nbsp;</p>



<p><em>Anne McCarthy</em>: Yeah, so this actually ties in nicely with all of this. So part of one of the ideas for the walkthrough and interactive element is when thinking about going through a museum, one of the things that I love is you&#8217;re kind of walking through and you see how based on periods of time, especially in a museum with a lot of, maybe not necessarily modern art but more historical art, you see how the tooling changes and access to paper unlocks the ability to do this, or access to different materials becoming more accessible, suddenly everyone&#8217;s using a certain color or whatever it is, or they know depth perception. I think there&#8217;s some interesting elements there. And so one of the ideas that I&#8217;m trying to work on right now is thinking about the Block Museum over a longer period of time. So what was available when WordPress 5.9 versus let&#8217;s say WordPress 6.9, ideally the tooling and what&#8217;s possible for the creation of art evolves, and I think it&#8217;d be so neat to have release-based art exhibits.</p>



<p>So I just set up the site super quick, because it&#8217;s WordPress using just a couple cray loop blocks, which is really cool. So there&#8217;s different exhibits. So there&#8217;s a 5.9 exhibit, a 6.0 exhibit, and now I want to have a 6.1, especially since so many design tools are coming to WordPress 6.1. There&#8217;s kind of an explosion of them, and I&#8217;m very keen to see what that unlocks in terms of art and the submission there. So I&#8217;m just looking for anything you want to create with WordPress 6.1. It can be before the release if you want to test stuff. I know the release is around the corner, and it can be anytime after leading up to 6.2. I just think it&#8217;s going to be a really, this release in particular, feels like it&#8217;s going to unlock a lot of creativity and I think it&#8217;ll be neat to visually show that at the museum.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, I think so too. And I&#8217;m really looking forward to what&#8217;s coming to the workers, to the museum as submissions because now with the be it the border control or be it the background or the gradients and all that, there are a lot of options to apply art, apply color, apply different forms and shapes that you can build with it. And there are some great examples already in the museum. So if you are not so creative and want to see what other people do, head on over to the blockmuseum.com. Is it a block-museum?</p>



<p><em>Anne McCarthy</em>: Block-museum. I always forget sometimes.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So these are the two community contributions today talking about art. I&#8217;m really excited about that because all of a sudden it&#8217;s away from making money or away from, oh I need to get my blog post posted and making products or something like that. Yeah, I&#8217;m really excited that we talk about it together. So what was released is the next section and…</p>



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



<p><em>Anne McCarthy</em>: Yeah, let&#8217;s dive into that. So WordPress 6.1 release candidate four is actually now available for testing. This was not published on our WordPress news site. Just kind of sometimes with release cycles there&#8217;s some additional RCs released candidates that are released right before just to make sure different high-priority bugs are addressed, but they&#8217;re not as necessarily major. So in this case I think two things were fixed. So you may not see it on WordPress news but know that it has happened and there&#8217;s now an RC4. So release squad is working super hard and behind the scenes to get final pieces in place and ready for the dry run. And then the final release is scheduled as a reminder for November 1st. And then Hector shared details about the release day process and earlier post if you&#8217;re a nerd like me and to know what actually happens.</p>



<p>And if you listen to this episode over the weekend before the release, it would be amazing if you could take some time to test 6.1. Brian Alexander, who is the, I think, test team lead and also the test lead for this release has instructions that make this really easy to follow. That will be in the show notes for helping test the different features of 6.1 and truly pick and choose whatever grabs your interest because it all helps. And I&#8217;ll do a special plug for any more developer focused folks, it would be great to test the typography as well as using block to put parts in a classic theme. And if you want to go even further, there&#8217;s a lot of stuff with filters for extending theme JSON and all sorts of things in the field guide. But I&#8217;m particularly keyed up around some of the developer features right now and getting feedback, even if it&#8217;s just like maybe you don&#8217;t find a bug but you find a way that would be more useful for you in the future. It&#8217;d be great.</p>



<p><em>Birgit Pauli-Haack</em>: And then definitely it holds through for the testing part theme and plugin developers, please, please, please see that your products still working for WordPress 6.1. Most of you are already doing that, but there&#8217;s always one out, maybe not. So I just urge you to start that.</p>



<p>And with that, we are coming to the Gutenberg plugin release. It&#8217;s 14.4.0 and I&#8217;m pointing that out because, well this week first time release lead JuanMa Garrido pushed the plugin over the finish line and Michael Burridge contributor on core documentation. He pointed out that Johannes Gutenberg invented the printing press in 1440. That&#8217;s 1-4-4-0. So just a little tidbit there. I like these coincidences.</p>



<p><em>Anne McCarthy</em>: I love that.</p>



<p><em>Birgit Pauli-Haack</em>: Come together. Yeah. Mind you, it took about 144 plugin releases to come to this point. So that&#8217;s also a good number.</p>



<p><em>Anne McCarthy</em>: Wild, to think about. Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And before I forget, Michael Burridge is also the main creator of the newly released course on Learn the WordPress it&#8217;s called Introduction to Block Development: Build Your First Custom Block. And if you are a developer and found block post about getting started with block development not deep enough or too basic, you are invited to step to do the step-by-step tutorial on building a real life example of a block for the editor, from setting up your development environment, using create block scaffolding, that&#8217;s your official tool, to testing your first iteration of the block and also do some debugging. And as you work through the project, you will add configuration options that enable the user of your block to customize the look and feel of it and to the liking in match maybe a style guide. So this is a great course to get started with, and even if you have bits and pieces already in place, I learned a lot from it when I was going through this. So it&#8217;s definitely a worth looking through it.</p>



<p><em>Anne McCarthy</em>: It&#8217;s so cool to see that course out there. I think it&#8217;s going to be huge for so many people.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, and I think within the first week, 40, 50 people already took it and three were already through it. So it definitely fills a need there. But I got us totally sidetracked and I could even go more sidetrack, because there&#8217;s a second course in the Learn site that could be, that&#8217;s an advanced course. It&#8217;s about using the data layer of Gutenberg for others than the editors. So you can use it for your plugin settings pages or something like that. So how far off astray could we go with that?</p>



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



<p>All right, let&#8217;s get back. So in the enhancements, there were two things that are developer related and I&#8217;m just pointing them out, because they might be important. One is the service side render has now a new attribute that skips the block support attribute. So there&#8217;s a little bug in the service side render when it&#8217;s pulled into the block editor admin feature, it duplicates the CSS. This fixes it, but it also adds another attribute to it. And this service side render function, or package actually, is used by 620 plugins. So I&#8217;m giving it a shout out here right away when it actually makes it in a good move plugin. So plugin developers can test it even already before it makes it into 6.2 or something like that. It&#8217;s a small change for most of them, but they might tap into that before that.</p>



<p>And then the second part is that the great block scaffolding we just talked about that&#8217;s used in the course allows now custom keys to be generated for the block JSON file and the package station file. So the use case that kind of triggered that was that a feature that a developer wanted to use the ACF plugin for the custom fields and use the official scaffolding tool to create a block for it. But they needed to do a lot of manual adjustments for the right keys.</p>



<p>And so that kind of got the developers working on it. And now with the variant flag and the no plugin flag that will come in that already available, and there is a dev note out there talking about that by Ryan Welcher. You now can use also the custom key to actually build ACF blocks with the official scaffolding block. And Ryan Welcher also has a three-part series on how to build custom WordPress block that supports advanced custom fields on YouTube. So that gets us another sidetrack here a little bit, but even if you don&#8217;t use advanced custom field plugin in part one, Ryan also walks you through how to retrieve and update post metadata while the block editor using the use entity prop hook and also shows you how to modify it so you can use it in the query loop block. And the field will then also display on archive pages. Yeah, if you want to start with create Block, now is a good time to learn more about it. And even if you don&#8217;t use ACF, the first video of this series will definitely be of interest for you.</p>



<p><em>Anne McCarthy</em>: There&#8217;s so much awesome work has been done around upgrading all these tooling to make it easier for people to get started. And Ryan&#8217;s does a great job of training these things and making it really accessible. So yeah, also if folks have ideas for what they want to see more, I know Ryan&#8217;s always open to suggestions there, too. So yeah, I hope folks dig in, because there&#8217;s a lot of good stuff there.</p>



<p><em>Birgit Pauli-Haack</em>: Big props also to Grzegorz Ziolkowski and also Damon Cook who&#8217;s a developer advocate at WP Engine. They both also commenting on it and also pushing this release over the finish line or the PR and figuring out what the architectural approach would be. So yeah, good way for the tooling. Yay.</p>



<p><em>Anne McCarthy</em>: Yeah, very cool. Next up, we have a couple different items that are all in the kind of block libraries, so expanding what&#8217;s possible, or in one case restricting what&#8217;s possible to start the list block, which has recently been split apart so that you can actually have nested blocks within it and have inner block control. And what&#8217;s neat about this is typography controls are now added to the list block. So now that you have that support in place and that each list item is an individual block, you can actually customize the list so that maybe the first item&#8217;s bigger than the third item, or you have different coloring or you can do all sorts if you control each individual list item on its own and then add in topography controls, it really opens up some neat options for displaying your content. I already have a post that I&#8217;m actually working on, then I&#8217;m like, &#8220;Oh, I needed this.&#8221;</p>



<p>So I&#8217;m very excited to see it out here. I actually didn&#8217;t see it was being worked on until this release. So it&#8217;s another part of the larger effort to address and expand design tooling consistency, which is a really huge part of running the outreach program. Comes up a lot where it&#8217;s like, why can I do this in one block and not this in the other block? And it kind of marries the best of both worlds where it&#8217;s taking advantage of the list block being revamped to use inner blocks and including these tools. So I&#8217;m very excited to see that. I don&#8217;t know. Birgit, you write a lot of posts, too. Do you have anything that you&#8217;re keen to use with that?</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, definitely. I can see that each list item can have a different font. Yeah. Or there&#8217;s some nice cool font that you can now add to your blog post even if you have a very neutral typography normally. So these things stand out and then yeah. But I like it.</p>



<p><em>Anne McCarthy</em>: I think it&#8217;s cool. The next thing we have is block locking and adding to related to block locking. It adds content blocking to the navigation block, meaning the inability to edit the contents of the block. And if you&#8217;ll remember right now, currently for most blocks, you actually can only lock the ability to remove the block or lock down the ability to move it. So to delete the block or to move it. And this adds content locking, which is eventually going to be expanded ideally to all blocks to the navigation block specifically, which kind of matches the functionality of the reusable block. So it&#8217;s kind of bringing this functionality that you see that you would expect elsewhere to a really powerful high impact part of the site. And I can see this being really useful, for example, if someone has a classic theme, they adopt a template part to have a header, and then they&#8217;re adding the navigation block in there for someone to manipulate.</p>



<p>But let&#8217;s say you don&#8217;t want them to actually change the contents of it. You can actually use this new locking option as an admin to lock it down. So maybe an editor or can&#8217;t go in there and mess things up. So it&#8217;s just expanding that kind of support. And I think it&#8217;s a great call for folks who are site owners or agencies. It ties into larger efforts to offer more curation tools for the editor as well. And I&#8217;m really excited to see these experiments and to add specific blocking and very intentionally two different blocks to then get feedback about how that experience is before we roll it out elsewhere. So I think there&#8217;s going to be some good insights coming from that experience as well. So check that out.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, definitely. Yeah, if you look at the bigger picture of that, it almost kind of gives you similar functionality to the reusable block, but you can narrow down the content blocking. So if you have patterns where you want, that the content is reused over multiple pages, you can put it in a template part and the content is also locked and then have the same call to action in the footer or in the header of things. Yeah. So it&#8217;s a really good. 6.1 has a few of the things already for image blocks and also group blocks I think. But now coming into the navigation block is really good as well.</p>



<p><em>Anne McCarthy</em>: Yeah, it&#8217;s great to see. Related to more tooling, the image block is now going to have a toolbar button to add a caption. So basically instead of it being something that to add and remove a caption, you&#8217;re able to just have it built into the block tool toolbar, which is a really easy way to see it at a glance. I&#8217;m very intrigued to see how this lands and what feedback comes up from it. I could see it being really useful. I wonder if people are going to be able to discover it pretty easily, because the icons, I think it&#8217;s a little bit like a couple dots at the bottom of a square. So I&#8217;m curious to see what feedback we have and what that looks like. But ultimately it should help people find the settings they expect in a readily accessible area. Yeah, and I know, Birgit, you were telling me before we started recording that if you add a caption in the media library and then you insert an image that it&#8217;ll appear automatically when you hit the add caption as well in the toolbar.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: It&#8217;ll automatically appear when you add the image to it to their canvas, then it shows the caption. But you can of course remove it, but when it&#8217;s empty you get the button up there. So you&#8217;re right, discoverability might be an issue there because it&#8217;s not always there. It&#8217;s only there when you need it, but sometimes you don&#8217;t know things that you need it if you don&#8217;t see them. Yeah.&nbsp;</p>



<p><em>Anne McCarthy</em>: Yes. Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: But what I really like is that it&#8217;s now one of the efforts to make the editor look like the front end. And the image right now has always a little space on below for the add caption feature. And if you don&#8217;t do it just has a little more space there, and it doesn&#8217;t show you the front end. It&#8217;s not the same as you would see on the front end. So that&#8217;s why I think people worked on it and now we need to figure out what&#8217;s the best approach on the button and the tool.</p>



<p><em>Anne McCarthy</em>: Agreed. Very. Especially as some of the work involves around adding a captions element too, I think it&#8217;s exciting to see all this sort of stuff being wedded together.</p>



<p><em>Birgit Pauli-Haack</em>: And when they manage how that works, the image caption, then once the feedback is in and there&#8217;s an iteration out there, that will be added to audio and video and also to table because for whatever reason tables have a caption.</p>



<p><em>Anne McCarthy</em>: I don&#8217;t know that historical reason behind that. I know that is interesting. Yeah, this is again one of those things where I think it&#8217;s neat where we have functionality we might want to roll out more broadly and instead it&#8217;s done in steps and kind of integrating from there. So I think there&#8217;s some good stuff that can come from that.</p>



<p>Switching gears a little bit, this is kind of headed into the block intersection, and I am stoked about this feature. I have to admit that I was following this PR. So it&#8217;s introducing distraction free mode, and I was following this PR,, I was looking at it and I looked at it months ago and I&#8217;ve been laser focused on 6.1. So I hadn&#8217;t looked at in a while. I hadn&#8217;t used it in a while. And I was writing a post for this week and I was testing it out, and I was absolutely blown away by this feature.</p>



<p>So it really strips down the editor to the bare basics where the block toolbar is gone, the top toolbar also disappears, you can bring it back on hover, and it&#8217;s a mode you can toggle on and off. So I just think I&#8217;m going to be using this constantly going forward, because I write in a fair amount just rambling on my personal site. And I am definitely one of those people who doesn&#8217;t use necessarily a lot of images or have very complex content. I really do just tend to write pretty basic posts with just words and just let it fly. And it felt so nice to be in that editor experience where you&#8217;re not necessarily seeing all the plus signs everywhere. You&#8217;re not needing the block tool bar, you don&#8217;t need the quick inserter at all times. You don&#8217;t need the top toolbar visible.</p>



<p>I&#8217;m hardly using block settings. And instead you can kind of just free your mind up to focus on writing. And I did a quick video because I was so excited. I mean this was literally 11 o&#8217;clock at night and I was like, I couldn&#8217;t stop thinking about how good it felt. And I don&#8217;t have that very often with technology. I&#8217;m pretty critical with technology. So whenever I have that kind of feeling, I just put together a very quick, I think it&#8217;s less than two minute, video showing the distraction of free mode. And so genuinely this is something that I&#8217;m very excited about and I&#8217;m also so deep in the site editing world that I think it&#8217;s really important we pause and think about the core writing experience. So this is one of those improvements that I think a lot of folks will be excited about and saying that they can explore. It&#8217;s also very new. So feedback is very much needed and bugs will be found and we will iterate as open source does. But yeah, I could ran about this for probably a full hour. I don&#8217;t know if you&#8217;re getting…</p>



<p><em>Birgit Pauli-Haack</em>: I&#8217;m there right with you. Yeah, the distraction free mode is certainly something that I was looking into quite early when the Gutenberg editor came into WordPress, and I know that I tested and I wrote about it, the plugin that Rich Tabor and his teammate Jeffery Carandang put together, it&#8217;s called Iceberg. And that was a plugin that you could put on your site and then have distraction free writing, and it almost felt like a typewriter if you had the right fonts to it. And it really helped. I really loved it. And somewhere in the Gutenberg Times is certainly another is a review of it. But now it comes to core, and I&#8217;m really excited about it. I think the feature is driven by, of course we all put our opinions in there, but it is driven by Andrei Drananescu and I had a conversation with him, I said, &#8220;Well, we could even remove more.&#8221; And so I would go back to the classic editor without the toolbar, but I can see how that quite a few writers will actually embrace it and use it just as their editing experience and they go back to just writing and don&#8217;t have to be bothered up paragraphs or blocks or anything of that. Yeah, yeah. I&#8217;m excited to learn what other people think about it, and I hope they&#8217;ll write about it, and let us know.</p>



<p><em>Anne McCarthy</em>: Especially before there&#8217;s a welcome feature. I think that&#8217;s the only concern. I saw there&#8217;s some follow up, there&#8217;s some accessibility stuff and then there&#8217;s also, wait, we need to actually tell people what this feature is. Because it&#8217;s a jarring different when you turn, because you&#8217;re like, wait ,where did everything go?</p>



<p><em>Birgit Pauli-Haack</em>: Is it broken?</p>



<p><em>Anne McCarthy</em>: Yeah, Yeah. It&#8217;s like wait, all my tooling went away. But I think once we get some of those requirements in place, it&#8217;ll be rocking and rolling.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, yeah, absolutely. And what&#8217;s also made it into this release is the redesign of the main pattern inserter. And the difference is that the categories show up and you click on the inserter and then use the pattern tab. What you see is only the categories of the patterns. And then when you click on the category, you see a preview of the patterns that are in there. And that is kind of comes also from some of the feedback that we got for patterns. So it&#8217;s kind of cool to see how that works. I find that inserter be a little bit too crowded when the patterns are actually kind of underneath the category and then I don&#8217;t see all the categories and all that. So it&#8217;s a nicer experience I feel about it.</p>



<p><em>Anne McCarthy</em>: Especially when thinking about scaling up the patterns and all the work that&#8217;s being done there. I think that&#8217;ll be a huge improvement to the experience of finding and managing all the different patterns that are now baked into a lot of themes.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. The next item is just a shout out for that the embed blog has now a variation to support the Tumbler dashboard URLs and of course with Tumbler also coming to use the Gutenberg block editor, it&#8217;s definitely good to have an embed block that can link out to other Tumbler blogs. The next one is toggle the navigation menu sidebar. And that&#8217;s an interesting development or iteration on the navigation block with using the sidebar to actually display the menus that you know from the classic menu editing, now you have a little bit more space to look at the menus and select them. Before it was a little bit cramped just in the navigation block interface. It&#8217;s a little bit, has more air to breathe. So check it out and see what to think about it. Have you tried it out, Anne?</p>



<p><em>Anne McCarthy</em>: No, not yet. I truly have been so deep in 6.1 stuff, and I have tested some of the new UX management generally with the navigation stuff, but this is different. So yeah, I&#8217;m excited to test this out. It&#8217;s probably of one of the things I&#8217;m paying attention to for the outreach program, because once 6.1 ends, we can dig into the next call for testing.</p>



<h3><strong>Documentation</strong></h3>



<p><em>Birgit Pauli-Haack</em>: Right, right. Yeah. And then you have in the documentation settings, there are always changes that come with the release, but those changes are actually available on the block editor handbook right when they&#8217;re merged kind of 15 minutes later. But it&#8217;s good to have them in the release. There are two things that I wanted to do a shout out. One is the document, the current state of the layout block support. It explains in the architecture section and the style sections, how those block supports are supposed to work that come with 6.1. There&#8217;s also a dev note available in the field guide, but that has much more detail in it. And of course our show will share the links in the show note. And also for the extending the query loop block, that is a feature that comes with 6.1 as well. And a lot of people are waiting for that, especially plugin developers and agency developers because they deal with so many custom post types now they can control what the query loop is using as a query or the data that it&#8217;s using. So that&#8217;s published in the block editor handbook as well as have a developer note available in the field types. I&#8217;m really excited about that extension possibilities for the query block.</p>



<p><em>Anne McCarthy</em>: Yeah, I&#8217;m also. It&#8217;s amazing to have that documentation in place so promptly. I know we&#8217;ve struggled with that in the past. And so again, as always, there&#8217;s stuff that you&#8217;re missing that you want to see, especially with career loop stuff. As you mentioned, agencies plugin offers and they really need that there. And I know it&#8217;s a big one that folks have extended the Gray Loop block from Core. And so the hope is rather than needing to fully extend a lot of stuff, you can just use a variation and have what you need baked in core without having to do a lot of maintenance. So please check that out, give us feedback, let&#8217;s make it as useful as possible.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, it&#8217;s really important to kind of see what Core does in a once in a while, even if you have used or develop for the block for the last five years, because some of the things you can take off your plate that you don&#8217;t have to maintain it. it&#8217;s standardized and the Gutenberg developers and core contributors will maintain it for you, and you only need to look at your variations for that. So yeah, there are quite a few things coming, and I think it&#8217;s the time now that once the foundation and the developers know how everything kind of will work together with site editor, with a post block, and also with the theme, there was a lot of moving parts that needed to be together and come together before any extension would be feasible or extension features or hooks and filters would be feasible to put in. And now I think it&#8217;s the time where everybody&#8217;s kind of thinking about how can we standardize extending the block editor. All right. Yeah. Are we at the end? I think we are.</p>



<p><em>Anne McCarthy</em>: I think we are.</p>



<p><em>Birgit Pauli-Haack</em>: At the end of the Changelog for the Gutenberg 14.4.0, and now on the eve of 6.1 release, the developers have already started to look at the next version and what can an updated tracking for various features that are too common. So you have been knee deep, if not year deep, into all the work and what are the highlights that you see coming to 6.2?</p>



<h3><strong>What’s in Active Development or Discussed</strong></h3>



<p><em>Anne McCarthy</em>: Yeah, I know I keep getting the numbers wrong, which is just hilarious. Yeah, it is so exciting to see what&#8217;s going on. I really feel like there&#8217;s a lot of momentum particularly I want to call out attention to the title. The issue is Phase Two Customization. I&#8217;m pretty sure the number is Gutenberg number for the GitHub repo is a 33094 in case you&#8217;re a nerd and want to dig into it. But a lot of work has been done basically even before, way before 6.1 was out the door once there was feature freeze to say okay, what are we doing next and what can we do to actually thoroughly wrap up this phase two work where there&#8217;s a stable foundation, we can begin exploring phase three and what are the main tasks to do. And so there is that main issue that I mentioned that&#8217;s going to be updated on a regular basis going forward.</p>



<p>So a lot of work has been done to pull together the phase two customization issue that will be updated basically going forward until it&#8217;s closed. So I like to call it out. I know it&#8217;s tough to keep on top of GitHub and everything like that, but every once in a while there are issues that, especially overview issues if you look at the label for overview, that really gather efforts and if you want to pay attention at a high level and be a bit more involved and necessarily just paying attention to the next WordPress release, this is one of those. And there are numerous tasks, I&#8217;m going to give a snapshot, which is what I did yesterday in our hallway hangout of just kind of the main task where things are just because I think it&#8217;s interesting. Work has been completed on two tasks.</p>



<p>Dev work is underway on nine, we&#8217;re in the design stage for three tasks, meaning we still need to finish finalizing some design. Dev has been assigned but hasn&#8217;t yet started the work on three tasks as well. Work is stuck on one thing that I&#8217;m following up on, and there were three originally and got that down to one. And then work is stuck. I know to track this down. Work is stuck either due to a problem, like developers aren&#8217;t sure to move forward or design and development are going back and forth, or there&#8217;s been a time lapse of 14 plus days. That&#8217;s how I defined it is basically has there been a lull in activity, and there are 11 of those that are in that state. And so part of the work right now in the next week or so is to get that 11 number way down, get work going, get involved there. If you&#8217;re interested in contributing to the project, this would be a great way to get involved.</p>



<p>Lots of folks are gathering around this and as you mentioned at the top, there are a couple that I want to specifically call out of things that I think will be bigger than others to solve. So one is introducing a browse mode. And we keep using the word mode, which I think is misleading for browse mode actually. I think it&#8217;s more about redefining the experience of navigating in the site editor. So both in terms of when you enter the site editor, what do you see, what&#8217;s the first thing you see, and right now you&#8217;re brought into whatever is powering your homepage, and you&#8217;re placed basically into a template. And imagine instead you&#8217;re being brought into, still maybe your homepage, but the sidebar is automatically open so you can see how to navigate between things, see templates, see your styles interface. It would be in the same sidebar as this other stuff rather than shoved into the right hand side, which unless using right to left languages.</p>



<p>But I currently find that information architecture to be pretty confusing. The browse mode work is both about redefining the information architecture and allowing you to actually navigate between different parts of your site that you&#8217;re editing with more ease. Right now it&#8217;s pretty like you have to leave this, and enter this, and all that sort of stuff and this would allow kind of more fluidity and also potentially in time, part of what&#8217;s being done is bring back actual content editing in terms of posts and pages to the site editor experience and creating more pathways between all the different editors from the template editor, to the post editor, to the site editor, all that sort of stuff. So how can we bring this together to a cohesive experience and present it in a way that allows folks to navigate where they need and edit what they need in a way that actually is a bit more intuitive. So I&#8217;m very excited to call that out, and I don&#8217;t know if you have anything to add around that.</p>



<p><em>Birgit Pauli-Haack</em>: I&#8217;m totally excited about it, because I really hate going from the site editor to the post editor and have to go back, back, back and then kind of come in again and it looks like the same editor, but it&#8217;s a little bit different, and the tools are a little bit different. So I like that this browse mode or whatever you want to call it, will kind of unify the experience. And I know from the outreach program&#8217;s call for testings that there&#8217;s always a little bit confusion on are we editing now a page, or a post, or is the template of a page of a post? I think there&#8217;s quite some confusion around that, and it probably won&#8217;t go away because it&#8217;s such a technical distinction that the visual distinction is fairly close to nothing. So you can get lost in those two editing modes. So bringing it together at least in one section where you&#8217;re just going to switch off, okay, I&#8217;m browsing now. I&#8217;m looking at everything and then now I click and I&#8217;m somewhere, and then I click the edit button and then go back.</p>



<p>It&#8217;s almost like the customizer when you were using that to do some updates on the homepage with site title or changing where you also see where the places are, what you&#8217;re editing in the front end view. And I think there are quite a few hurdles to overcome with that, but I think it will make it class better than it is now with the two modes there.</p>



<p>I don&#8217;t know if the two modes will really go away. You always can probably edit the templates, but it&#8217;s definitely, it will help with the confusion.</p>



<p><em>Anne McCarthy</em>: And I think even being able to see that you have a separate section for content versus templates, I think alone will be helpful. I think that&#8217;s part of what&#8217;s adding to the confusion. So I&#8217;m also very keen to test this. This is one of the top items I have in my mind for the full sighting outreach program. I always have a running list of things that I pay attention to. You would not believe my GitHub notifications, but this is one of the items that I&#8217;ve really been waiting for and wanting to see what we can do to get early feedback on. Because I do think it&#8217;s going to be a game changer, but with anything you implement, there&#8217;s going to be new problems and new confusion that arises in trade offs. So knowing what those trade offs are, and then making sure we&#8217;re able to push people where most of the time they&#8217;re able to get it right. That&#8217;s always the aim.</p>



<p><em>Birgit Pauli-Haack</em>: Right, right.</p>



<p>Anne McCarthy: So yeah, that&#8217;s a big one to call out in that experience.</p>



<p><em>Birgit Pauli-Haack</em>: And we&#8217;ll share the issue number is 36667 just in case you want to rush to the computer and look it up. But I also see that the issue itself is almost a year old, so I&#8217;m also thinking that that was was on hold to kind of finish some of the site editor functionality before you can think about what would need to be in the browse mode displayed or how would it interact with the existing stuff. So I&#8217;m glad that there is some patience there with waiting on things before it&#8217;s released too soon or worked on it too soon when other things are not stable yet. So I really like it. I&#8217;m looking forward to it and see what other people talk about it. Yeah. What else?</p>



<p><em>Anne McCarthy</em>: Ditto. Yeah, so the navigation block I have to call out and that is a big&#8230; I think we kind of do a disservice and we just talk about the navigation block, because it&#8217;s really how do you manage navigation for the entire site and the navigation experience for the entire site. And the block is one piece of that, and it connects to so much. And so there&#8217;s a lot of work from looking at, I was talking to Yellen this morning who&#8217;s a designer who works for Automattic, we&#8217;ve saw a lot of work with the navigation block around what if instead of directly manipulating the navigation block, you actually manipulate it in the block settings so you could actually drag and drop, and it was kind of more familiar to the old menu experience. What would that look like? And part of the work here is everything from that kind of stuff to how can you allow folks to have more control over the responsiveness of a navigation block item.</p>



<p>And so there&#8217;s also some technical underpinnings around using different fallbacks and making sure there&#8217;s more fallbacks in place for when you&#8217;re switching from a classic theme to a block theme and making that as out of the box intuitive as possible. Currently there&#8217;s a really annoying convert to links thing that&#8217;s very confusing and not user friendly and very technical in some of the fallback situations. So there&#8217;s so much work to be done there. And I just want to call that out as something that I know a lot of people bring up as a major pain point. It&#8217;s something I hear about constantly. Did you know the navigation block is not easy to use?&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Some people have other words for it, and I totally agree. Yes,</p>



<p><em>Anne McCarthy</em>: I know. And it&#8217;s very interesting because I think there&#8217;s a split between both people who just want one navigation menu and it&#8217;s very simple and very contained. And then on the flip side, there&#8217;s people who want to create a mega menu. So I hear feedback about all sorts of things and I promise there are people working really hard to get it right. That&#8217;s another thing we&#8217;ll also be testing pretty extensively. And so I had to call that out. Another whole area of work as part of this wrapping up, phase two is around patterns. And so I like to quote Miguel, who is another coworker who said something like, &#8220;Up until this point, it was like&#8230;&#8221; I&#8217;m going to get this wrong, I&#8217;m going to butcher it. But he said something around, up until this point, it was all about blocks and now going forward so much is going to be about patterns, because that&#8217;s the way to really harness the power of blocks.</p>



<p>And so a lot of stuff needs to be done around pattern categorization. We talked about the pattern inserter redesign and how that helps things be more scalable. But right now for example, there&#8217;s a category of patterns called query. What on earth does that mean? Especially what is that? And especially when that&#8217;s probably going to be the most commonly used pattern because the query block is an advanced tool. So why patterns should fill that gap and should make it really easy to do the basics of displaying posts. But people may not actually look into the query pattern, because that is more technical. So we need to do everything from revamping the categories to finishing up bundling the headers and footers so people regardless of theme, have easy access to those patterns. And reevaluating even how we show patterns from a theme versus patterns from the pattern directory and integration with the pattern directory as well. So there&#8217;s a lot of work to be done there across on numerous different things to really bring the power patterns fully into the experience. So that&#8217;s a huge, huge area of work.</p>



<p><em>Birgit Pauli-Haack</em>: But I think we pushed this quite far already with the multiple ways pattern can actually make it into the site, be it the pattern directory, be it with a theme. You can also put it in a plugin and say, yeah, I don&#8217;t know. And it&#8217;s so easy to bring something to a website that is already predesigned and then kind of feels like native to your own site when it kind of follows the theme. And I think that&#8217;s a strong suit from the panel directory that when you add them to your site, it kind of seamlessly. And I think there&#8217;s still some work to be done there, but seamlessly was with your colors, with your theme settings that it kind of picks up on that. That would be really cool. But for that you definitely would need more standardization on color palettes and font sizes and these kind of things.</p>



<p>So I think it will always be mainly theme-driven, the pattern part. And that&#8217;s why I like that you can see the pattern now in the theme directory of the block themes. And also for classic themes if a classic theme has balance. Yeah, they also will show up in the block theme in the theme directory and yeah, I don&#8217;t know if we talked about it.</p>



<p><em>Anne McCarthy</em>: That&#8217;s very cool.</p>



<p><em>Birgit Pauli-Haack</em>: We talked about it. Yeah. I&#8217;m just worrying, the speaking about the theme directory, what you also see now in the theme directory is the style variations. And when you click the style, they are now displayed underneath the screenshot. And when you click on that, the screenshot actually changed into the color setting. So it&#8217;s a really neat system that the meta team came up with. So try this out. It&#8217;s the first iteration, so it might not work for all themes, it definitely works for block themes that have style variations. And if you know that a theme has style variations, but they don&#8217;t show, please let the meta team know so they can fix whatever keeps the style of variations to show. It&#8217;s another kind of tangent. Sorry about that.</p>



<p><em>Anne McCarthy</em>: No no, it&#8217;s a great tangent, because I think it&#8217;s really important. It&#8217;s part of how can we show the power of the next generation of themes and actually bring that into the theme directory? Because that is a weird piece of this is evolving the theme directory as well. And it&#8217;s saying a lot of blocking authors have given feedback around as well as, hey, we&#8217;re doing all this work, this theme is so much more complex, it can do all these sorts of things, but it&#8217;s not reflected in the theme directory. So how can we bring that in?</p>



<p>So I think it&#8217;s a really cool, which actually relates to the final thing I know we talked about, but retaining decoupling templates from themes and having templates be something that when you&#8217;re switching themes, you can actually retain them. And right now themes are tied to templates, so when you&#8217;re switching around, they&#8217;re basically &#8220;lost&#8221; or you can switch back to the theme and get it, but you have to bring it with you manually.</p>



<p>And that has been brought up for a long time. This has been raised as a flag. And I can imagine a future where you&#8217;re in the theme directory, a block name, and you still see those style variations, you see the patterns and then maybe you see the templates, and maybe you can pick and choose from each what you want to use. And so I think we&#8217;ve done some neat expirations around far into the future, blocking, switching and combining and merging and what that looks like. Obviously very futuristic almost, but we&#8217;re getting closer to that and that&#8217;s part of the work being done is improving the experience of switching from classic to block and then also in between blockings themselves. So yeah, lots of exciting stuff being done.</p>



<p><em>Birgit Pauli-Haack</em>: And I like that we are now at the point where we kind of pivot from what we knew before, like template and themes and template parts. They&#8217;re all together, and now we are kind decouple them and make it user friendly, because you don&#8217;t want to put all the work into creating a template for your post or for your categories, and then you switch a theme and then you lose all that. So that&#8217;s definitely not what a user-friendly system would be, but it also adds a little bit, if not quite a big complexity to the system and to see what is what and where does it come from? Especially when you want to debug and you have to figure out where did the user get this pattern and where did the user get this template purge? And how is that same templates still there? Kind of. Yeah. So it&#8217;s going to be really interesting to see what happens next there.</p>



<p>Well, thank you. Yeah, thank you so much for at least giving us a broad overview, and we will certainly share that phase two customization updated tracking issue and keep you up to date here on the Gutenberg Changelog. Yeah.</p>



<p>So this brings us to the end of the show and this was a great way to talk about all of it. What&#8217;s in WordPress, what&#8217;s in Gutenberg, what&#8217;s in the view, what&#8217;s in art and in fiction. So is there anything that you want to give a shout out to that we haven&#8217;t talked about but it&#8217;s really close to your heart or that people should know?</p>



<p><em>Anne McCarthy</em>: I have something cheesy to share, which is we&#8217;re coming up on two years of when the first call for testing for the outreach program started. And I had a hallway hangout yesterday with a group of, I think almost like 10 folks. And I missed people. I&#8217;ve been doing this for two years with people that around the world who I haven&#8217;t seen. And I just want to give a lot of props to the WordPress community for engaging with these things. And a lot of stuff has just been experimentation and figuring out what works and what doesn&#8217;t and people being vulnerable and sharing and showing up. And I just was filled with a lot of gratitude yesterday thinking about, remember the first hallway hang out I ran, I think two people came, and no one knew what it was and it didn&#8217;t seem very useful. And now people come and really give a lot of time and attention, and then I missed people. And that&#8217;s a really wonderful feeling. And at the end of the day, we&#8217;re doing this for each other and for the open internet. So yeah, that&#8217;s just a cheesy way to end, but it just was very much on my mind thinking about how much it really is a collective effort.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, that&#8217;s an excellent way to end the show. Thank you so much.</p>



<p><em>Anne McCarthy</em>: And thank you for all the stuff you do, too. The regular Gutenberg changelog podcasts are just excellent resources for people, so it&#8217;s an honor to be on here and have a chance to nerd out with someone else rather than alone in my apartment.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Well thank you for, yeah, we have been working on this together for quite a while, and yeah, it&#8217;s always a pleasure to have you on the show, and thank you for spending time with me today and working us through that.</p>



<p>And dear listeners, thank you so much also for listening to it. And if you want to write a review on iTunes or Stitcher or Podcaster or wherever we get it, and we would like to read it aloud here. So let other people know how you feel about the Changelog, it helps with the distribution. And as always, the show notes will be published on Gutenbergtimes.com/podcast. This is episode 75, and if you have questions or suggestions or news you want us to include the next time, send them to <a href="mailto:Changelog@gutenbergtimes.com">Changelog@gutenbergtimes.com</a>. That&#8217;s <a href="mailto:Changelog@gutenbergtimes.com">Changelog@gutenbergtimes.com</a>.</p>



<p>So thank you, dear listeners. Thanks again, Anne McCarthy, until the next time.</p>



<p><em>Anne McCarthy</em>: Thank you. Goodbye everyone.</p>



<p><em>Birgit Pauli-Haack</em>: Goodbye.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 30 Oct 2022 17:22:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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: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:154:"Gutenberg Times: Interactive Fiction tool, Introduction course for Block Development, WP Awards, Gutenberg 14.4 and so much more –  Weekend Edition #234";s: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=22461";s: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:156:"https://gutenbergtimes.com/interactive-fiction-tool-introduction-course-for-block-development-wp-awards-gutenberg-14-4-and-so-much-more-weekend-edition-234/";s: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:28709:"<p>Howdy, </p>



<p>Did you miss your weekly Gutenberg fix? I had some great days off, no traveling,  no projects, just my books, my house and hanging out with my husband. It was nice and quiet for a chance. So, well rested, I am here to accompany you into the last week of the WordPress 6.1 release cycle. The <a href="https://make.wordpress.org/core/2022/10/28/wordpress-6-1-release-candidate-5-rc5-now-available-for-testing/">Release Candidate 5 is available</a> and you can read more about the <a href="https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/">WordPress 6.1 Release Day Process</a>. </p>



<p>The&nbsp;<strong><a href="https://thewpweekly.com/awards/">WP Awards</a></strong>&nbsp;are open for voting until November 30. It&#8217;s the second year,&nbsp;<strong>Davinder Singh</strong> <strong>Kainth</strong>, publisher of the <a href="https://thewpweekly.com/">WP Weekly newsletter</a>, created it as a way to bring the community together.</p>



<p><em>Gutenberg Times</em>&nbsp;has been nominated under the category &#8220;WordPress Blogs&#8221; and the Gutenberg Changelog in the category, yep you guessed it, &#8220;WordPress Podcasts&#8221; both categories are further down the ballot sheet, number 18 and 19. </p>



<p>Please consider voting, only, of course, if you find it worthwhile, and it stacks up against the competition ? You can only vote once per email address. Needless to mention, the email address also subscribes you to the weekly newsletter, which is well-rounded and well researched. It&#8217;s a newsletter, I read every week, together with <a href="https://wpowls.co/">WPOwls</a>, <a href="https://www.therepository.email/">The Repository</a>, and <a href="https://poststatus.com/">Post Status</a>.&nbsp;</p>



<p>I would be grateful, if the Gutenberg Times and the Gutenberg Changelog received more than five votes this time around. ?</p>



<a href="https://thewpweekly.com/awards/"><img src="https://i0.wp.com/user-images.githubusercontent.com/39980/196435038-d68f6757-b6e8-4fbc-a515-9945dbeb2238.png?resize=652%2C301&ssl=1" alt="" width="652" height="301" /></a>



<p>Now, dive into the vastness of awesome content produced in the WordPress community about the block editor. The Time to read is 15 minutes, not counted the time it will take to follow all links. Don&#8217;t take it all at one, space it out over the next week ?</p>



<p>Have a fantastic weekend and to those who celebrate it:<br />Happy Halloween! ? ?</p>



<p>Yours, ?<br /><em>Birgit</em></p>




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



<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#0-word-press-release-information">Developing Gutenberg and WordPress</a><ul><li><a href="https://gutenbergtimes.com/feed/#1-gutenberg-plugin-version-14-4">Gutenberg plugin version 14.4 </a></li></ul></li><li><a href="https://gutenbergtimes.com/feed/#0-p">Plugins, Themes, and Tools for #nocode site builders and content creators</a></li><li><a href="https://gutenbergtimes.com/feed/#2-word-press-6-0-1-and-6-1-scheduled">Theme Development for Full Site Editing and Blocks</a></li><li><a href="https://gutenbergtimes.com/feed/#3-building-themes-for-fse-and-word-press">Building Blocks and Tools for the Block editor. </a></li><li><a href="https://gutenbergtimes.com/feed/#5-s">Upcoming WordPress events</a><ul><li><a href="https://gutenbergtimes.com/feed/#1-l">Learn WordPress Online Meetups</a></li></ul></li><li><a href="https://gutenbergtimes.com/feed/#7-p">Photo from around the World</a></li></ul></div>
</div></div>




<h2 id="0-word-press-release-information">Developing Gutenberg and WordPress</h2>



<p><strong>Anne McCarthy </strong>shared with us the list of <a href="https://make.wordpress.org/core/2022/10/28/core-editor-improvement-advancing-the-writing-experience/"><strong>writing flow enhancements</strong></a> of the Block Editor via the latest Gutenberg plugin releases.  My two favorites are the Links automation with &#8220;[[&#8221; and the distraction-free writing mode. I also like how the updated Documents Settings space feels not less busy than before. </p>



<a href="https://make.wordpress.org/core/2022/10/28/core-editor-improvement-advancing-the-writing-experience/"><img /></a>



<p><a href="https://make.wordpress.org/test/2022/10/26/hallway-hangout-discussion-on-wrapping-phase-2-26-oct/">Hallway Hangout: Discussion on wrapping Phase 2 (26 Oct)</a></p>



<h3 id="1-gutenberg-plugin-version-14-4">Gutenberg plugin version 14.4 </h3>



<p>In his post <a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/">What’s new in Gutenberg 14.4? (26 October)</a>, first-time release lead, <strong><a href="https://twitter.com/juanmaguitar">JuanMa Garrido</a></strong>, shared the fun fact that Johann Gutenberg invented the printing press in the year 1440. He highlighted the following from this plugin release: </p>



<ul>
<li><a href="https://make.wordpress.org/core/wp-admin/post.php?post=100516&action=edit#redesigned-the-main-pattern-inserter">Explore easier navigation and larger previews of patterns in the Inserter</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/#introduced-distraction-free-mode">Enjoy distraction free writing</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/#completed-fluid-typography-feature">Control image captions from the block toolbar</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/#added-content-locking-to-the-navigation-block">Lock the ability to edit the navigation block</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/#Improved-Fluid-Typography">Take advantage of improvements to Fluid Typography</a></li>
</ul>



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



<p><strong>Sarah Gooding</strong> also covered the release in her article <a href="https://wptavern.com/gutenberg-14-4-introduces-distraction-free-mode-redesigns-pattern-inserter"><strong>Gutenberg 14.4 Introduces Distraction-Free Mode, Redesigns Pattern Inserter</strong></a>. She started with &#8220;<a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/">Gutenberg 14.4</a>&nbsp;was released today with long-awaited support for distraction-free editing, to the delight of content editors around the world. It hides all non-essential UI and clears the canvas for a focus on text-based content creation.&#8221;</p>



<p>It is a special delighted to have the brilliant <strong>Anne McCarthy</strong> as co-host on the Gutenberg Changelog podcast. We mentioned the Museum of Block Art, Interactive Fiction, Gutenberg 14.4 and what&#8217;s next for the Phase 2 of Gutenberg project. </p>



<img />



<p>The 75th episode will arrive at your favorite podcast app over the weekend. Oh BTW: Last week, Matt Mullenweg announced on his blog that the team of <a href="https://ma.tt/2022/10/open-source-podcasting-client/">Pocket Casts</a> open-sourced the code for the iPhone and Android apps. You can <a href="https://pca.st/7O43">subscribe to the Gutenberg Changelog podcast</a> via Pocket Casts  </p>



<div class="wp-block-group has-light-background-background-color has-background is-layout-flow"><div class="wp-block-group__inner-container">
<p><strong>?️ </strong> New episode:  <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-75-gutenberg-14-4-upcoming-wordpress-6-1-release-whats-next-for-6-2/">Gutenberg Changelog #75 – Gutenberg 14.4, Upcoming WordPress 6.1 Release, What’s Next for 6.2</a> with special guest, Anne McCarthy, and host Birgit Pauli-Haack</p>
</div></div>




<div class="ngl-articles colored ngl-articles-50_50 ngl-articles-frontend">

	
	<div class="ngl-articles-wrap ngl-articles-webview">
	
						
			<div class="ngl-article-mobile">
				<table width="100%" border="0" cellpadding="0" cellspacing="0">
					<tr>
						<td valign="top">
							<div class="ngl-article-mob-wrap">
							<div class="ngl-article-featured"><a href="https://gutenbergtimes.com/what-art-can-you-create-with-wordpress-6-1/" target="_self" rel=""><img src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2022/10/IMG_4949-scaled.jpg?w=652&ssl=1" /></a></div><div class="ngl-article-labels">gutenbergtimes.com</div><div class="ngl-article-title"><a href="https://gutenbergtimes.com/what-art-can-you-create-with-wordpress-6-1/" target="_self" rel=""><span>What art can you create with WordPress 6.1?</span></a></div><div class="ngl-article-excerpt">The Museum of Block Art is looking for submissions using WordPress 6.1 and the evolving design tools available. Create art (and perhaps find some bugs) ahead of the November 1st&hellip;</div><div class="ngl-article-date">22 Oct 2022</div>							</div>
						</td>
					</tr>
				</table>
			</div>
			
			
			

		
		
		</div>

</div>




<h2 id="0-p">Plugins, Themes, and Tools for #nocode site builders and content creators</h2>



<p><strong>Anne McCarthy </strong>also shared their enthusiasm for <a href="https://www.youtube.com/watch?v=iCF5lssk_oY"><strong>Distraction-free writing with you on YouTube</strong></a>. They wrote: &#8220;<em>It drastically reduces tooling options to allow you to focus in on your content. This is such a game changer for me that I quickly recorded this video the same day I explored it&#8217;s current iteration ahead of the next Gutenberg release! I hope any writers out there get excited too. Since this is an early feature as well, please explore and report back any feedback you have, so iterations can continue!</em>&#8220;</p>



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



<p><strong>Sarah Gooding </strong>took a sneak peek at a new feature to come to the Block editor and summarized the discussion in this post: &#8220;<a href="https://wptavern.com/gutenberg-contributors-explore-a-new-browse-mode-for-navigating-the-site-editor"><strong>Gutenberg Contributors Explore a New Browse Mode for Navigating the Site Editor</strong></a>&#8220;. Gooding wrote: &#8220;Although the project’s contributors have been referring to it as “browse mode,” it is essentially a redesign for the existing UI to make it more intuitive for users to navigate. Gutenberg may not need any more new “modes” but the site editor is in dire need design improvements that will unify the experience and make it less chaotic for getting around.&#8221; </p>



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



<p>In earlier Gutenberg Times Weekend Editions, you already got the chance to see the beta version of this. Now it&#8217;s live in its first iteration. <strong>Sarah Gooding</strong> has the scoop for you. <a href="https://wptavern.com/wordpress-themes-directory-adds-style-variation-previews"><strong>WordPress Themes Directory Adds Style Variation Previews</strong></a>. She reports: &#8220;<em>Meta team contributors are also working on adding the ability to filter the directory for themes with style variations. Dufresne proposed creating a new&nbsp;<code>style-variations</code>&nbsp;theme tag as the simplest route towards implementing this</em>.&#8221; You can learn more about this proposal from the <a href="https://meta.trac.wordpress.org/ticket/6545">trac ticket: Add ability to filter for themes with style variations</a></p>



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



<p>The Theme shop <strong><a href="https://twitter.com/olive_themes">Olive Themes</a></strong> has been offering themes in the WordPress.org repository only for two months and just published their third block theme, <a href="https://wordpress.org/themes/arc-fse/"><strong>Arc FSE.</strong></a> They describe it as <em>&#8220;Arc Fse is a free, multi-use block-based theme that adheres to the Full Site Editing features added in WordPress 5.9. As a result, you can alter every component of your site, including the colors, typography, and page layout, to meet your needs.&#8221; </em>The other two themes are <a href="https://wordpress.org/themes/medicity/"><strong>Medcity</strong></a> and <a href="https://wordpress.org/themes/exo/">Exo</a></p>



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



<p><strong>Ana Segota</strong> of Anariel Design <a href="https://twitter.com/AnarielDesign/status/1583888671844884480">announced</a> their new eCommerce Block Theme named <strong><a href="https://woocommerce.com/products/olorien/">Olorien</a></strong> at the WooCommerce Marketplace. According to Segota, the theme is packed with ready-to-use block patterns and makes creating pages from scratch an easy drag-and-drop experience.</p>



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



<p><strong><a href="https://twitter.com/artemiosans">Artemio Morales</a></strong> calls himself an ‘Electronic Literature Creator’ and <strong><a href="https://artemiosans.com/2022/10/20/introducing-the-gutenberg-interactive-fiction-engine/comment-page-1/">introduced the Gutenberg Interactive Fiction Engine</a></strong>, an early experiment. </p>



<p>“Interactive fiction is software simulating environments in which players use text commands to control characters and influence the environment. Works in this form can be understood as literary narratives (..). &#8220;, I learn from <a href="https://en.wikipedia.org/wiki/Interactive_fiction">Wikipedia.</a> </p>



<p>When using the Morales&#8217; <a href="https://artemiosans.com/2022/10/18/gutenberg-interactive-fiction-engine-test/">demo</a>, the story starts with an image of a forest and text. Below you find three choices to continue the story: one leads you deeper into the forest, one guides you to the next clearing and the third has you headed for the town, each giving you a different continuation of the story.  Then on the next station, you get to have a choice again. </p>



<p>The journey, on which you can take  your readers  can be quite elaborate and doesn’t have to be all text. You can use any core block that’s available to you.&nbsp;The interface is still a bit rough, and if you want to try it out I recommend watching Morales&#8217; video walk-through. </p>



<p>Morales also lists a few use cases beyond the interactive story telling. </p>



<ul>
<li>“Choose your own adventure” YouTube stories</li>



<li>Interactive comics</li>



<li>Audio stories with branching paths</li>



<li>Marketing and educational content</li>



<li>Multimedia posts incorporating elements from all the above</li>
</ul>



<p>Morales ends his introduction with ideas how to improve the plugin and what other blocks might enhance the production of such an interactive fiction/non-fiction suite. </p>



<p>The plugin <a href="https://github.com/artemiomorales/gutenberg-interactive-fiction-engine/releases/tag/v0.1.0">Gutenberg Interactive Fiction Engine </a>is available for download on GitHub and the code is open-source for discovery and collaboration. </p>



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



<p>Are you trying to figure out how to use WordPress, the  Block Editor and FSE to make your website? Long-time WordPress educator and early adopter of the block editor, <strong>Bud Kraus</strong> of <em>JoyofWP</em> will hold a paid two-day live class starting 11/8. The second part will take place on 11/15. Learn all the fundamentals of how to make a WordPress website in a hands-on live class. <a href="https://www.learndesk.us/live/6501910058106880/designing-your-wordpress-website-step-by-step"><strong>Designing Your WordPress Website Step By Step</strong></a>.Use the discount code &#8216;Take10&#8217; to get 10% discount. </p>



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



<p><a href="https://wordpress.org/plugins/x3p0-powered-by/"><strong>Justin Tadlock</strong></a> published a fun new single Block plugin called<a href="https://wordpress.org/plugins/x3p0-powered-by/"> <strong>&#8216;Powered by</strong>&#8216;</a> in the plugin repository. It&#8217;s a block that generates a random “Powered by” messages. It is meant to replace the typical “Powered by Theme/WordPress” message in footers, but can be used anywhere. You have the choice of messages with or without emoji. The code is also <a href="https://github.com/x3p0-dev/x3p0-powered-by">available on GitHub</a></p>



<h2 id="2-word-press-6-0-1-and-6-1-scheduled">Theme Development for Full Site Editing and Blocks</h2>



<p><strong><a href="https://twitter.com/mikemcalister">Mike McAllister</a>,</strong> WP Engine and early adopter of the block editor, introduced <strong>OllieWP</strong>, &#8220;a hub for the next generation of WordPress&#8221;. with tutorial blog posts on design tools, full-site editing, patterns and more. The latest post covers&nbsp;<strong><a href="https://olliewp.com/global-styles-and-the-future-of-css-in-wordpress/">Global styles and the future of CSS</a>&nbsp;</strong>and why this feature is a &#8220;complete game-changer&#8221;. </p>



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



<p><strong><a href="https://twitter.com/marktimemedia">Michelle Schlup</a></strong>&#8216;s WordCamp US 2022 talk <a href="https://wordpress.tv/2022/10/28/the-future-of-themes-designing-for-the-block-editor-and-beyond/"><strong>The future of themes: designing for the block editor and&nbsp;beyond</strong></a>. The description reads: &#8220;This talk works through the entire thinking process as it relates to theme design. It offers a thorough checklist of steps and tools for designing themes that support WordPress core functionality, custom templates and content, common plugins, and an array of standard and custom Gutenberg blocks.&#8221; </p>



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



<p>In his <a href="https://wordpress.tv/2022/10/28/a-beginners-guide-to-the-wordpress-template-hierarchy/"><strong>A beginner’s guide to the WordPress template hierarchy</strong></a>, <strong>Jonathan Bossenger</strong> covers how the template hierarchy works, and how it affects both classic and block themes.</p>



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




<p><strong>&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/" target="_blank" rel="noreferrer noopener">&#8220;Keeping up with Gutenberg &#8211; Index 2022&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly.  <a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/"><em>The index 2020 is here</em></a></p>




<p>In the WordPress TV video <a href="https://wordpress.tv/2022/10/28/lets-code-global-styles-variations-in-block-themes/"><strong>Let’s code: global styles variations in block&nbsp;themes</strong></a> also by Jonathan Bossenger, you can follow along and learn how to create a new block theme, and add a few new Style variations to ship with the theme<strong>.</strong></p>



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



<p>Last week, <strong>Daisy Olsen</strong> and <strong>Justin Tadlock</strong> held the <strong><a href="https://wordpress.tv/2022/10/21/hallway-hangout-block-theme-development-features-in-wordpress-6-1/">Hallway hangout: block theme development features in WordPress 6.1</a></strong> &#8211; a  casual chat about some Block Theme features that are planned to land in WordPress 6.1. This is the recording. </p>



<h2 id="3-building-themes-for-fse-and-word-press">Building Blocks and Tools for the Block editor. </h2>



<p><strong><a href="https://twitter.com/michaelburridge">Michael Burridge</a></strong>&nbsp;in collaboration with other contributors, published the course:&nbsp;<a href="https://learn.wordpress.org/course/introduction-to-block-development-build-your-first-custom-block/"><strong>Introduction to Block Development: Build your first custom block</strong></a>&nbsp;to <em>Learn.WordPress</em>. You are invited to a step-by-step tutorial on building a real life example of a block for the editor, from setting up your development environment, using create-block scaffolding to testing your first iteration of the block. As you work through the project, you will add configuration options that enable the user to customize the look and feel of the block to their liking or to match a style guide.</p>



<img />An example of the “newspaper columns” block that you will be developing in this course.



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



<p><strong>Ryan Welcher</strong> published a two-part series of live streams on <a href="https://www.youtube.com/watch?v=3zJyjYIykQ4&list=PL6D-mnq0bpxMMSoVEiCdos86T7NUO8GoQ"><strong>Creating Custom WordPress block that supports Advanced Custom Fields</strong></a> (ACF) on YouTube </p>



<p>Welcher starts developing a custom block that interacts with both, native custom post meta registered via code and with fields created using Advanced Custom Fields. He demos the use of  <code>InspectorControls</code> and the use of the <code>useEntityProp</code> hook to retrieve data from the custom fields and to modify them through the block&#8217;s code. Welcher also shows you how to modify the custom block, so it can be used in a Query Loop block and have the value of the custom field be displayed on Archive pages.</p>



<p>On a side note,  <strong>Welcher</strong> also published the code snippets he has been using during his Twitch stream&#8217;s development projects on VS Code:&nbsp;<a href="https://marketplace.visualstudio.com/items?itemName=ryanwelcher.modern-wordpress-development-snippets">Modern WordPress Developer Snippets</a>. If you use Visual Studio Code as your development tool, you can add them via&nbsp;<code>Code &gt; Prefernces &gt; Extensions</code></p>



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



<p><strong><a href="https://twitter.com/riadbenguella">Riad Benguella</a></strong> posted&nbsp;<a href="https://riad.blog/2022/10/17/secrets-of-gutenberg-the-keyboard-shortcuts-package/"><strong>Secrets of Gutenberg: The keyboard shortcuts package</strong></a>&nbsp;and explains how to use the package with any ReactJS context at first. Further, into the post you also learn how to use the package in your WordPress plugin or Block plugin. If you want to contribute to Gutenberg code, you can use this package to solve a long-standing issue by yours truly and <a href="https://github.com/WordPress/gutenberg/issues/9723">create a keyboard shortcut to open the &#8220;Edit HTML&#8221;</a> on a single block. ?</p>



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



<p><strong><a href="https://twitter.com/maugelves">Mauricio Gelves</a>, </strong>was a speaker at <a href="https://valencia.wordcamp.org/2022/">WordCamp Valencia</a> last week. His talk&#8217;s title was also the title of his latest blog post&nbsp;<a href="https://humanmade.com/2022/10/18/1001-ways-to-implement-gutenberg-blocks/"><strong>1001 ways to implement Gutenberg block</strong></a>&nbsp;for Human Made, where he shared the takeaways of his talk and links to learning more. I was specifically intrigued by the decision tree, that distinguished between three major ways to implement and customize the blocks: Editorial, with PHP and with JavaScript.</p>



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



<p><strong>Carlo Daniele</strong> released the course&nbsp;<a href="https://academy.kinsta.com/dashboard/course/custom-gutenberg-block-development-with-the-wordpress-block-editor/5/19"><strong>Custom Gutenberg Block Development With the WordPress Block Editor</strong></a>&nbsp;on Kinsta Academy. You learn how to set-up your local development space, how to use the official Create-Block scaffolding tool, build your first block with adding controls to the Block Tools bar, the sidebar, and Block Styles. In the final lesson, Daniele covers how to use InnerBlocks, and other fine-tuning steps.</p>




<p><strong><a href="https://gutenbergtimes.com/need-a-zip-from-master/">Need a plugin .zip from Gutenberg&#8217;s master branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>



<p><img alt="GitHub all releases" src="https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge" /></p>




<h2 id="5-s">Upcoming WordPress events</h2>



<p>November 18, 2022<br /><strong><a href="https://www.wordfest.live/2022/november/">WordFest Live Returns</a></strong>&nbsp;– the 24-hour Festival of WordPress</p>



<p>February 17 – 19, 2023<br /><a href="https://asia.wordcamp.org/2023/"><strong>WordCamp Asia 2023</strong></a></p>



<p>Contributors are gathering to organize <a href="https://germany.wordcamp.org/2023/"><strong>WordCamp Germany</strong></a> next year in Munich, Germany.  It&#8217;s so exciting to me, and I can hardly wait for a WordCamp in my hometown! <a href="https://germany.wordcamp.org/2023/">Sign-up for notifications</a> when the organizers have more details. </p>



<p class="has-light-background-background-color has-background has-large-font-size"><a href="https://central.wordcamp.org/schedule/"><strong>Have a look at the schedule of upcoming WordCamps</strong></a> to find one near you. </p>



<h3 id="1-l">Learn WordPress Online Meetups</h3>



<p>October 31, 2022 &#8211; 4 pm EDT / 20:00 UTC <br /><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/288666280/"><strong>Part 2: Re-Creating Block Designs</strong></a> w/ Wes Theron</p>



<p>November 1, 2022 &#8211; 8:30 am EDT / 12:30 UTC <br />On Twitch, <strong><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289395168/">WordPress development live stream: Internationalization</a></strong></p>



<p>November 3, 2022 &#8211;  10am EDT / 14:00 UTC  <br /><strong><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/289395242/">Internationalization in Block Themes</a> </strong>w/ Jonathan Bossenger</p>



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



<h2 id="7-p">Photo from around the World</h2>



<p><em>With in-person meetup rebooting all over the world, I resumed sharing photos from Gutenberg talks at WordCamps today. </em></p>



<p>In this <a href="https://twitter.com/jdmweb/status/1585993802355036167">photo posted by Jeremy Desvaux on Twitter</a> shows, <a href="https://twitter.com/VinceDubroeucq"><strong>Vincent Dubroeucq</strong></a>, author of the <a href="https://vincentdubroeucq.com/wpcookbook/">WPCookBook</a> (in French),  gives a live demo of Block Development at <a href="https://lyon.wordcamp.org/2022/">WordCamp Lyon 2022</a> </p>



<img />




<p></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 type="submit" 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, 29 Oct 2022 19:00:36 +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: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:64:"WPTavern: The WordPress Community Isn’t Ready to Leave Twitter";s: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=139000";s: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://wptavern.com/the-wordpress-community-isnt-ready-to-leave-twitter";s: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:9588:"<p>Elon Musk has bought Twitter in a $44B deal that closed this week, tweeting “<a href="https://twitter.com/elonmusk/status/1585966869122457600">Let the good times roll</a>,” on Friday after taking the helm. Musk fired top executives at the company and <a href="https://twitter.com/elonmusk/status/1585619322239561728">tweeted</a> an appeal to Twitter&#8217;s advertisers to share his motivation in acquiring what is arguably the world&#8217;s most important social network:</p>



<p>&#8220;The reason I acquired Twitter is because it is important to the future of civilization to have a common digital town square, where a wide range of beliefs can be debated in a healthy manner, without resorting to violence,&#8221; Musk said. &#8220;There is currently great danger that social media will splinter into far right wing and far left wing echo chambers that generate more hate and divide our society.&#8221;</p>



<p> Musk also hinted at the importance of content moderation, saying &#8220;Twitter obviously cannot become a free-for-all hellscape, where anything can be said with no consequences!&#8221; The company is forming a council to discuss content moderation, but nobody knows what that will mean for the future of Twitter.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Twitter will be forming a content moderation council with widely diverse viewpoints. <br /><br />No major content decisions or account reinstatements will happen before that council convenes.</p>&mdash; Elon Musk (@elonmusk) <a href="https://twitter.com/elonmusk/status/1586059953311137792?ref_src=twsrc%5Etfw">October 28, 2022</a></blockquote>
</div>



<p>While some Twitter users have considered migrating to Tumblr, the structure and user base isn&#8217;t currently comparable to the Twitter experience. In response to Verge co-founder Nilay Patel&#8217;s provocative article titled &#8220;<a href="https://www.theverge.com/2022/10/28/23428132/elon-musk-twitter-acquisition-problems-speech-moderation">Welcome to hell, Elon</a>,&#8221; Tumblr CEO Matt Mullenweg <a href="https://twitter.com/photomatt/status/1586013950109310977">tweeted</a> his support.</p>



<p>&#8220;This is an unfortunately good summary of why running a social network is so hard, as I’ve learned with Tumblr,&#8221; Mullenweg said. &#8220;I am wishing Twitter the best and also hope this doesn’t slow down Tesla or SpaceX, which I think are critical to the future.&#8221;</p>



<p>Patel aptly communicated the weight of the political challenges Musk will face in his commitment to steering Twitter away from becoming &#8220;a free-for-all hellscape,&#8221; which some think has already happened. If Musk decides to open the doors to unsavory characters who were banned in the past, it may drive the social network into the ground.</p>



<p>While the WordPress community has many online gathering places &#8211; various Slack workspaces, P2 blogs, and Facebook groups &#8211; it has always been Twitter that served as the place for both casual interactions and breaking news. It is the de facto social network for those working in tech. There are many who only use the platform for keeping up with WordPress news and the community.</p>



<p>&#8220;There’s nowhere else to really go!&#8221; WordPress product designer Mike McAlister <a href="https://twitter.com/mikemcalister/status/1586003046399623169">said</a>. &#8220;WordPress people are pretty much exclusively on Twitter it seems.&#8221;</p>



<p>Apart from the few optimistic souls who think Twitter will be better than ever, many community members expressed apprehension about losing the network they have built over the years. As the closing of the sale loomed, people threatened to leave Twitter on principle if Musk gained control. That day has arrived, but for the most part the WordPress community is not abandoning Twitter. </p>



<p>&#8220;Twitter has had too good of an impact on my life to just jump ship,&#8221; Edan Ben-Atar <a href="https://twitter.com/edanbenatar/status/1586009637203083265">said</a>. &#8220;I&#8217;ll stick around for as long as it makes sense. For now, nothing has changed from what is noticeable to the eye.&#8221;</p>



<p>WordPress designer Dustin Henrich says he is staying but also looking up the people he follows on other platforms. </p>



<p>&#8220;I&#8217;ve made too many good connections, enjoy reading about people&#8217;s tech and non tech lives, and learning from some wicked smart people,&#8221; Henrich <a href="https://twitter.com/dhenrich/status/1586017449287503874">said</a>. &#8220;I&#8217;d truly be sad if this just all went away.&#8221;</p>



<p>Decentralized social networking, which has so far failed to gain much mainstream attention, is getting a second look in light of Twitter changing hands. WordPress agency owner Tom Finley is <a href="https://twitter.com/i/web/status/1586099982620594176">experimenting</a> with using the <a href="https://wordpress.org/plugins/activitypub/">Activity Pub plugin</a> to set up his site as a private Mastadon server. It implements the ActivityPub protocol for WordPress so readers can see the site&#8217;s posts on Mastadon and other federated platforms (that support Activity Pub).</p>



<p>Some WordPress community members are flirting with joining Mastadon instances, or have already committed to posting in both networks, but we are not yet seeing a mass exodus flocking to the fediverse.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I’m giving Mastodon a try although I’m still sticking around here for the time being. <br /><br />I hate to say it but what about more use of the official WordPress Slack workspace? I often go there if I need to find someone in the community.</p>&mdash; Shawn Hooper (@ShawnHooper) <a href="https://twitter.com/ShawnHooper/status/1586040039473090560?ref_src=twsrc%5Etfw">October 28, 2022</a></blockquote>
</div>



<p>&#8220;We’ve seen this attempted exodus to the promised land many times before,&#8221; Ross Wintle <a href="https://rosswintle.uk/2022/10/something-about-twitter/">said</a> in a post that explains why he isn&#8217;t optimistic about people successfully leaving Twitter. &#8220;Without a proper mass migration of people and organizations to another service, it doesn’t stick. </p>



<p>&#8220;You end up with people cross posting to multiple services to reach all the people that they want to reach. And then as a reader I’m checking multiple services and seeing the same things. The signal/noise ratio goes down. And most people get fed up and end up back where they were before.&#8221;</p>



<p>The most hopeful speculators ask if this could this be the return of blogs. At the moment blogs are not social enough, and there isn&#8217;t a critical mass of bloggers eager enough to adopt the protocols necessary to connect their sites in a stream of easily digestible, short updates. </p>



<p>Until Elon Musk makes more radical changes, many WordPress community members see no reason to leave Twitter.</p>



<p>&#8220;For now, I don&#8217;t see a reason to leave,&#8221; WordPress developer advocate Birgit Pauli-Haack <a href="https://twitter.com/bph/status/1586069842553344000">said</a>. &#8220;Block, Unfollow, Mute are my friends for curating my feed. I did cancel my subscription to Twitter Blue after 12 months. Being allowed to edit tweets is not worth it.&#8221;</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I've been through so many social networks over time as they come and go. I lost count how many people say they are leaving Twitter.<br /><br />I use Twitter primarily for note taking, links, etc. I see nothing about that to change.</p>&mdash; David Bisset (@dimensionmedia) <a href="https://twitter.com/dimensionmedia/status/1586067272933654528?ref_src=twsrc%5Etfw">October 28, 2022</a></blockquote>
</div>



<p>Overall, most people are taking a &#8220;wait and see&#8221; approach regarding leaving Twitter.</p>



<p>&#8220;I haven&#8217;t found a viable alternative,&#8221; WordPress meetup organizer Sallie Goetsch <a href="https://twitter.com/salliegoetsch/status/1586042212567068672">said</a>. &#8220;I do hang out in various WP Slack groups, but for the wider world&#8230;we&#8217;ll just have to see what happens here.&#8221;</p>



<p>One positive byproduct of this recent shake-up is that the WordPress community is considering a future where important conversations happen on another platform. As users explore other social networks, they may gain an affinity for a different type of social media culture with features that Twitter is lacking. Migrating and settling into a new social home on the web takes time.</p>



<p>&#8220;I’m not saying I wouldn’t love a mass migration to happen,&#8221; Ross Wintle said. &#8220;I’ve just seen so many attempts now and none seem to have been particularly successful, and I don’t see why this one would either.</p>



<p>&#8220;For a big change to happen, I think either the platform has to spontaneously combust itself or it falls out of fashion by a long period of attrition and fades from the public consciousness over time. Facebook may even be at the start of this. Time will tell.</p>



<p>&#8220;Perhaps, one day, we will look back and remember that thing we all used called Twitter the same way we remember Geocities and MySpace. But I struggle to see how that will be next week or next month. It will be in many years.&#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, 29 Oct 2022 02:13:44 +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: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:63:"Post Status: Agency Owners: If You Could Ask Anyone Anything…";s: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:32:"https://poststatus.com/?p=142298";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://poststatus.com/agency-owners-if-you-could-ask-anyone-anything/";s: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:901:"<p>Hey all—<br /><br />In our <a href="https://poststatus.slack.com/archives/C02TNBDAXLL/p1666881400963559?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener">#Agency-Owner channel</a> I asked this week:</p>



<blockquote class="wp-block-quote"><p>If you could ask anyone anything related to your work as an agency — who would it be OR more importantly what would you want to ask?</p></blockquote>



<p>The initial answers are already helping us support your valuable, yet often underserved work here (and of benefit to all).<br /><br />Go chime in when you get a chance or DM me if you want to keep it private. </p>



<p>– Cory</p>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 28 Oct 2022 22:17:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Cory Miller";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:49:"Post Status: Moving and Not Moving With the Crowd";s: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:32:"https://poststatus.com/?p=142275";s: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:60:"https://poststatus.com/moving-and-not-moving-with-the-crowd/";s: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:6968:"<div class="is-layout-flow wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">This week's WordPress business highlights for Post Status: <strong>Lesley Sim</strong> is pivoting <strong>Newsletter Glue</strong> to an upmarket clientele. A discussion starter about WordPress <strong>UX</strong>. Do we need a curated plugin ecosystem, more open standards, and easy access to current expert consensus points in key knowledge areas? Time to bail out of <strong>Twitter</strong>? <strong>PayPal</strong>? <strong>Katie Keith</strong> tells her <strong>HeroPress</strong> story. </p></div>


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



<p class="yoast-reading-time__wrapper"><span class="yoast-reading-time__icon"></span><span class="yoast-reading-time__spacer"></span><span class="yoast-reading-time__descriptive-text">Estimated reading time:  </span><span class="yoast-reading-time__reading-time">6</span><span class="yoast-reading-time__time-unit"> minutes</span></p>
</div></div>



<h2 id="h-to-heck-with-black-friday-i-m-raising-my-prices"><strong>To Heck with Black Friday, I’m Raising My Prices!</strong></h2>



<p>This week in <a href="https://poststatus.slack.com/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener"><strong>Post Status Slack</strong></a>, <strong>Lesley Sim</strong>, the founder of <strong>Newsletter Glue</strong>, dropped this announcement: <em>“While everybody is offering discounts for Black Friday, we’re planning to significantly raise prices. We’ll be narrowing our target audience and focusing mainly on medium-large publishers and online businesses; working with them more closely and providing a high level of customization and support.”</em> What motivated Lesley's decision? Where does she expect it to take her company? How can plugin owners find enterprise customers and agency partners? Find out on <strong>Post Status Draft</strong>. <a href="https://poststatus.com/lesley-sim-newsletter-glue-business-model-pivot/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener"><strong>LISTEN→</strong></a></p>



<h2 id="h-can-we-get-to-yes-on-better-ux"><strong>Can We Get to &#8220;Yes&#8221; on Better UX?</strong></h2>



<p>This week in <a href="https://speckyboy.com/can-wordpress-appeal-to-diy-markets/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener">an article</a> shared in <a href="https://poststatus.slack.com/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener"><strong>Post Status Slack</strong></a>, <strong>Eric Karkovack </strong>suggested some ways to improve the WordPress user experience, especially for DIY users setting up a website for the first time. Some of the things Eric wants to see happen, like a standard interface for plugins and a curated view of the plugin ecosystem, are also commonly expressed by designers, developers, and people in other roles at WordPress agencies serving enterprise clients. Can we get everyone to “yes” on a better UX? Tell us what you think. <a href="https://poststatus.com/wordpress-user-experiences/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener"><strong>LISTEN→</strong></a></p>



<h3 id="h-a-curated-plugin-ecosystem-you-say-how">A curated plugin ecosystem you say? How?</h3>



<p>I've <a href="https://poststatus.com/wordpress-user-experiences/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID#Post" target="_blank" rel="noreferrer noopener">elaborated</a> on some of the ideas discussed on the podcasts this week with Eric and Lesley that can help both plugin businesses, WordPress agencies, and WordPress users in general. It mostly comes down to:</p>



<ul><li><strong>Don't Play Favorites — Recognize Excellence. </strong>What if there was a quality score based on neutral data from WP.org. It might create incentives that make &#8220;gaming&#8221; the system a win for everyone.</li><li><strong>Open Up &#8220;Open Secrets&#8221; — Spread Standards and Expert Knowledge.</strong> What if it was incredibly easy for developers (or anyone) to find and learn best practices and standards? It might create ladders up that are a win for everyone. <a href="https://poststatus.com/wordpress-user-experiences/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID#Post" target="_blank" rel="noreferrer noopener"><strong>READ→</strong></a> &nbsp;</li></ul>



<h2 id="h-quick-links"><strong>Quick Links</strong></h2>



<ul><li>There's a rich <a href="https://poststatus.slack.com/archives/C0413T6GD/p1666821158461799?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener">ongoing conversation</a> in <strong>Post Status Slack</strong> about <strong>PayPal</strong>. The prevailing opinion is <em>very</em> negative, but as usual, <em>it depends</em>. <strong><a href="https://poststatus.slack.com/archives/C0413T6GD/p1666821158461799?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID">SLACK→</a></strong></li><li>Over at <strong>HeroPress</strong>, it's <strong>Katie Keith</strong> of <strong>Barn2 Plugins</strong> telling her story: <a href="https://heropress.com/essays/a-community-that-transcends-labels/?utm_source=Post+Status+Newsletter&utm_campaign=f055253069-EMAIL_CAMPAIGN_2022_10_28_06_26&utm_medium=email&utm_term=0_afc03177a6-f055253069-&mc_cid=f055253069&mc_eid=UNIQID" target="_blank" rel="noreferrer noopener"><strong>A Community that Transcends Labels→</strong></a></li></ul>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 28 Oct 2022 22:02:34 +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: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:96:"Post Status: WordPress 6.1 RC5 • WP-CLI 2.7.1 • Help Test Plugin Dependencies Feature 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:32:"https://poststatus.com/?p=141952";s: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:130:"https://poststatus.com/wordpress-6-1-rc5-6-1-sneak-peek-with-nick-diego-wp-cli-2-7-1-help-test-plugin-dependencies-feature-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:19155:"<h2 id="h-this-week-at-wordpress-org-october-24-2022">This Week at WordPress.org (October 24, 2022)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">WordPress 6.1 rolls out on November 1. Help test 6.1 Release Candidate 3 — and the Rollback feature plugin. Be sure to look over the 6.1 DevNotes, Field Guides, and Team Updates. </p></div>


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



<div id="kt-info-box_68609b-a8" class="wp-block-kadence-infobox"><div class="kt-blocks-info-box-link-wrap kt-blocks-info-box-media-align-left kt-info-halign-left"><div class="kt-blocks-info-box-media-container"><div class="kt-blocks-info-box-media kt-info-media-animate-none"><div class="kadence-info-box-icon-container kt-info-icon-animate-none"><div class="kadence-info-box-icon-inner-container"><span class="kt-info-svg-icon kt-info-svg-icon-fe_gitMerge"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title"><a href="https://make.wordpress.org/core/2022/08/10/proposal-stop-merging-experimental-apis-from-gutenberg-to-wordpress-core/">WordPress 6.1 </a>Release Candidate 5</h2><p class="kt-blocks-info-box-text"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/23f3.png" alt="⏳" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2022/10/28/wordpress-6-1-release-candidate-5-rc5-now-available-for-testing/">WordPress 6.1 Release Candidate 5 (RC5) Now Available for Testing</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f9ea.png" alt="?" class="wp-smiley" /> <a href="https://make.wordpress.org/test/2022/09/21/help-test-wordpress-6-1/">Help Test WordPress 6.1</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f50e.png" alt="?" class="wp-smiley" /> <a href="https://make.wordpress.org/core/tag/dev-notes-6-1/">WordPress 6.1 DevNotes, Field Guides, and Team Updates</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/23ea.png" alt="⏪" class="wp-smiley" /> <a href="https://make.wordpress.org/hosting/2022/10/19/call-for-action-testing-rollback-feature/">Call For Action – Testing Rollback Feature</a></p></div></div></div>



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



<ul><li><a href="https://wordpress.org/news/2022/10/wordpress-6-1-release-candidate-3/"></a><a href="https://make.wordpress.org/core/2022/10/28/wordpress-6-1-release-candidate-5-rc5-now-available-for-testing/">WordPress 6.1 Release Candidate 5 (RC5) Now Available for Testing</a></li><li><a href="https://make.wordpress.org/hosting/2022/10/19/call-for-action-testing-rollback-feature/">Call For Action – Testing Rollback Feature</a></li></ul>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_9ee0ac-7f"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="h-wp-6-1-devnotes-and-team-updates"><a href="https://make.wordpress.org/core/tag/dev-notes-6-1/">WP 6.1 DevNotes</a> and Team Updates</h2>



<ul><li><a href="https://make.wordpress.org/core/2022/10/12/wordpress-6-1-field-guide/">WordPress 6.1 Field Guide</a></li><li><a href="https://make.wordpress.org/core/2022/10/11/performance-field-guide-for-wordpress-6-1/">Performance Field Guide for WordPress 6.1</a></li><li><a href="https://make.wordpress.org/polyglots/2022/10/20/wordpress-6-1-translation-status-october-20-2022/">WordPress 6.1 Translation Status (October 20, 2022)</a></li><li><a href="https://make.wordpress.org/polyglots/2022/10/11/wordpress-6-1-ready-to-be-translated/">WordPress 6.1 ready to be translated</a></li><li><a href="https://make.wordpress.org/core/2022/10/20/multisite-registration-and-activation-pages-have-new-html-and-css/">Multisite registration and activation pages have new HTML and CSS</a></li><li><a href="https://make.wordpress.org/core/2022/10/14/global-terms-removed-in-wordpress-6-1/">Global terms removed in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/11/enhanced-typescript-support-in-wordpress-6-1/">Enhanced TypeScript support in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/11/reference-styles-values-in-theme-json/">Reference Styles values in <code>theme.json</code></a></li><li><a href="https://make.wordpress.org/core/2022/10/11/wordpress-6-1-accessibility-improvements/">WordPress 6.1 Accessibility Improvements</a></li><li><a href="https://make.wordpress.org/core/2022/10/11/miscellaneous-rest-api-improvements-in-wordpress-6-1/">Miscellaneous REST API improvements in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/12/block-api-changes-in-wordpress-6-1/">Block API changes in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/11/content-locking-features-and-updates/">Content locking features and updates</a></li><li><a href="https://make.wordpress.org/core/2022/10/11/simplified-data-access-with-new-react-hooks-in-wordpress-6-1/">Simplified data access with new React hooks in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/09/introducing-wp_list_tableget_views_links-in-wordpress-6-1/">Introducing <code>WP_List_Table::get_views_links()</code> in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/08/escaping-table-and-field-names-with-wpdbprepare-in-wordpress-6-1/">Escaping Table and Field names with <code>wpdb::prepare()</code> in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/07/create-block-scaffolding-tool-updates/">Create-block scaffolding tool updates</a></li><li><a href="https://make.wordpress.org/core/2022/10/07/introduction-of-presets-across-padding-margin-and-block-gap/">Introduction of presets across padding, margin and block gap</a></li><li><a href="https://make.wordpress.org/core/2022/10/07/improved-php-performance-for-core-blocks-registration/">Improved PHP performance for core blocks registration</a></li><li><a href="https://make.wordpress.org/core/2022/10/06/introducing-update-uri-theme-header-in-wordpress-6-1/">Introducing “Update URI” theme header in WordPress&nbsp;6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/04/block-based-template-parts-in-traditional-themes/">Block-based “template parts” in traditional themes</a></li><li><a href="https://make.wordpress.org/core/2022/10/07/improvements-to-wp_query-performance-in-6-1/">Improvements to <code>WP_Query</code> performance in 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/10/06/new-cache-site-health-checks-in-wordpress-6-1/">New cache Site Health checks in WordPress 6.1</a></li><li><a href="https://make.wordpress.org/core/2022/09/27/navigation-block-fallback-behavior-in-wp-6-1-dev-note/">Navigation Block Fallback Behavior in WP 6.1</a></li></ul>



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



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



<ul><li><a href="https://make.wordpress.org/accessibility/2022/10/22/accessibility-team-meeting-notes-october-19-2022/">Accessibility Team Meeting Notes: October 19, 2022</a></li></ul>



<h2 id="h-community">Community</h2>



<ul><li><a href="https://make.wordpress.org/community/2022/10/26/meetup-organizer-newsletter-october-2022/">Meetup Organizer Newsletter: October 2022</a></li><li><a href="https://make.wordpress.org/community/2022/10/21/community-deputy-training-4-wordcamp-process-flow/">Community Deputy Training #4: WordCamp Process Flow</a></li></ul>



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



<ul><li><a href="https://make.wordpress.org/core/2022/10/25/wordpress-6-0-release-day-process-2/">WordPress 6.1 Release Day Process</a></li><li><a href="https://make.wordpress.org/core/2022/10/24/a-week-in-core-october-24-2022/">A Week in Core – October 24, 2022</a></li><li><a href="https://make.wordpress.org/core/2022/10/28/core-editor-improvement-advancing-the-writing-experience/">Core Editor Improvement: Advancing the writing experience</a></li><li><a href="https://make.wordpress.org/core/2022/10/27/whats-new-in-gutenberg-14-4-26-october/">What’s new in Gutenberg 14.4? (26 October)</a></li><li><a href="https://make.wordpress.org/core/2022/10/27/wordpress-6-1-release-candidate-4-rc4-now-available-for-testing/">WordPress 6.1 Release Candidate 4 (RC4) Now Available for Testing</a></li><li><a href="https://wordpress.org/news/2022/10/wordpress-6-1-release-candidate-3/">WordPress 6.1 Release Candidate 3 (RC3) Now Available</a></li></ul>



<h3 id="h-meetings">Meetings</h3>



<ul><li><a href="https://make.wordpress.org/core/2022/10/26/dev-chat-agenda-october-262022/">Dev Chat agenda: October 26,2022</a></li><li><a href="https://make.wordpress.org/core/2022/10/24/editor-chat-summary-wednesday-20-october-2022/">Editor chat summary: Wednesday, 20 October 2022</a></li><li><a href="https://make.wordpress.org/core/2022/10/24/editor-chat-agenda-october-26th-2022/">Editor Chat Agenda: October 26th 2022</a></li><li><a href="https://make.wordpress.org/core/2022/10/24/dev-chat-summary-october-19-2022/">Dev Chat summary, October 19, 2022</a></li><li><a href="https://make.wordpress.org/core/2022/10/24/performance-chat-agenda-25-october-2022/">Performance Chat Agenda: 25 October 2022</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/10/24/design-share-oct-10-oct-21/">Design Share: Oct 10-Oct 21</a></li></ul>



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



<ul><li><a href="https://make.wordpress.org/docs/2022/10/19/new-design-for-helphub-in-wordpress-org/">New design for HelpHub in WordPress.org</a></li><li><a href="https://make.wordpress.org/docs/2022/10/19/the-first-ever-documentation-team-contributor-day-25th-october-2022/">The first ever Documentation team Contributor Day – 25th October, 2022</a></li><li><a href="https://make.wordpress.org/updates/2022/10/24/documentation-team-update-october-24-2022/">Documentation Team Update – October 24, 2022</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/10/19/call-for-action-testing-rollback-feature/">Call For Action – Testing Rollback Feature</a></li></ul>



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



<ul><li><a href="https://make.wordpress.org/marketing/2022/10/26/agenda-global-marketing-team-meeting-october-26-2022/">Agenda: Global Marketing Team meeting, October 26, 2022</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/10/21/wordpress-org-redesign-update/">WordPress.org Redesign Update</a></li><li><a href="https://make.wordpress.org/meta/2022/10/20/displaying-style-variations-for-supporting-themes/">Displaying Style Variations for Supporting Themes</a></li></ul>



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



<ul><li><a href="https://make.wordpress.org/openverse/2022/10/25/community-meeting-recap-25-october-2022/">Community Meeting Recap (25 October 2022)</a></li><li><a href="https://make.wordpress.org/openverse/2022/10/25/handling-very-large-2gb-files/">Handling very large (&gt;2GB) files</a></li><li><a href="https://make.wordpress.org/openverse/2022/10/25/storing-provider-supplied-thumbnails/">Storing provider supplied thumbnails</a></li></ul>
</div>



<div class="is-layout-flow wp-block-column">
<h2 id="h-performance"><a href="https://make.wordpress.org/performance/">Performance</a></h2>



<ul><li><a href="https://make.wordpress.org/core/2022/10/25/performance-team-meeting-summary-11-october-2022-2-2/">Performance Chat Summary: 25 October 2022</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/10/26/plugin-review-team-status-24-oct-2022/">Plugin Review Team Status: 24 Oct 2022</a></li></ul>



<h2 id="h-polyglots">Polyglots</h2>



<ul><li><a href="https://make.wordpress.org/polyglots/2022/10/25/agenda-weekly-polyglots-chat-oct-26-2022-1300-utc/">Agenda: Weekly Polyglots Chat – Oct. 26, 2022 (13:00 UTC)</a></li><li><a href="https://make.wordpress.org/polyglots/2022/10/20/wordpress-6-1-translation-status-october-20-2022/">WordPress 6.1 Translation Status (October 20, 2022)</a></li><li><a href="https://make.wordpress.org/polyglots/2022/10/11/wordpress-6-1-ready-to-be-translated/">WordPress 6.1 ready to be translated</a></li></ul>



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



<ul><li><a href="https://make.wordpress.org/updates/2022/10/27/support-team-meeting-updates-for-october-27/">Support Team Meeting Updates for October 27</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/updates/2022/10/25/test-team-update-24-october-2022/">Test Team Update: 24 October 2022</a></li></ul>



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