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:47:"WordPress.org blog: WordPress 6.4 “Shirley”";s: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=16299";s: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:43:"https://wordpress.org/news/2023/11/shirley/";s: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:66051:"<img width="1024" height="683" src="https://i0.wp.com/wordpress.org/news/files/2023/11/Release_featured_image2-1.png?resize=1024%2C683&ssl=1" alt="Record cover with an image of Shirley Horn, a record sliding down the right side, and the words Shirley WordPress 6.4." class="wp-image-16319" />



<p>Say hello to WordPress 6.4 “Shirley,” named after the iconic jazz artist <a href="https://wikipedia.org/wiki/Shirley_Horn">Shirley Horn</a>. Her distinctive voice and extraordinary connection to the piano established her as one of the leading jazz musicians of her generation. Horn’s journey from the Washington D.C. jazz scene to the international stage is a testament to her dedication and perseverance. Her influence reached far beyond the confines of traditional jazz, breaking boundaries and inspiring audiences worldwide.</p>



<p>Enjoy the easy pace of <a href="https://www.youtube.com/channel/UCS3pUiY9OmzB6bPta3-4ArQ/playlists">Shirley Horn’s music</a> as you take in all that 6.4 offers.</p>



<p>This latest version of WordPress introduces a new, versatile default theme and a suite of upgrades to empower every step of your creative journey. Craft your content seamlessly with further writing improvements. Explore more ways to bring your vision to life and streamline site editing with enhanced tools. Whether you&#8217;re new to WordPress or an experienced creator, “Shirley” has something for you. Discover the unmatched flexibility of building with blocks and let your ideas take flight.</p>



<blockquote class="wp-block-quote has-extra-large-font-size">
<p>Many of the features and enhancements in WordPress 6.4 fall in the “small but mighty” category. Along with the adaptable beauty of the Twenty Twenty-Four theme, these updates help content creators and site developers alike save time and effort while delivering the high value, low hassle WordPress experience the world has grown to expect.</p>
<cite>Josepha Haden Chomphosy, Executive Director of WordPress</cite></blockquote>



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



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



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



<h2 class="wp-block-heading">What’s inside 6.4</h2>



<h3 class="wp-block-heading">Meet Twenty Twenty-Four</h3>



<p>Experience site editing at its finest with <a href="https://make.wordpress.org/core/2023/08/24/introducing-twenty-twenty-four/">Twenty Twenty-Four</a>. This new multi-faceted default theme has been thoughtfully crafted with three distinct use cases in mind, from writers and artists to entrepreneurs. Save time and effort with its extensive collection of <a href="https://2024.wordpress.net/index.php/patterns/">over 35 templates and patterns</a>—and unlock a world of creative possibilities with a few tweaks. Twenty Twenty-Four’s remarkable flexibility ensures an ideal fit for almost any type of site. <a href="https://2024.wordpress.net/">Check it out in this demo</a>.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/tt4.png?resize=1024%2C666&ssl=1" alt="Cropped screenshots of the Twenty Twenty-Four theme, showing its diverse use cases for photographers, bloggers, and small businesses." class="wp-image-16274" />



<h3 class="wp-block-heading">Let your writing flow</h3>



<p><a href="https://make.wordpress.org/core/2023/10/05/core-editor-improvement-ensuring-excellence-in-the-writing-experience/">New enhancements</a> ensure your content creation journey is smooth. Find new keyboard shortcuts in List View, smarter list merging, and enhanced control over link settings. A cohesive toolbar experience for the Navigation, List, and Quote blocks lets you work efficiently with the tooling options you need.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/writing.png?resize=1024%2C666&ssl=1" alt="Screenshot of a Quote block showing its improved toolbar and the text " />



<h3 class="wp-block-heading">The Command Palette just got better</h3>



<p>First introduced in WordPress 6.3, the Command Palette is a powerful tool to quickly find what you need, perform tasks efficiently, and speed up your building workflow. Enjoy a <a href="https://make.wordpress.org/core/2023/09/12/core-editor-improvement-commanding-the-command-palette/">refreshed design and new commands</a> to perform block-specific actions in this release.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/commands.png?resize=1024%2C666&ssl=1" alt="Screenshot of the refreshed UI of the Command Palette. It displays a search bar with the words " for="for" />



<h3 class="wp-block-heading">Categorize and filter patterns</h3>



<p><a href="https://wordpress.org/patterns/">Patterns</a> are an excellent way to leverage the potential of blocks and simplify your site-building process. WordPress 6.4 allows you to organize them with custom categories. Plus, new advanced filtering in the Patterns section of the inserter makes finding all your patterns more intuitive.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/categorize-patterns-1.png?resize=1024%2C666&ssl=1" alt="Screenshot of the Site Editor's patterns view which shows a list of patterns with custom categories, such as " />



<h3 class="wp-block-heading">Get creative with more design tools</h3>



<p>Build beautiful and functional layouts with an expanded set of design tools. Play with background images in Group blocks for unique designs and maintain image dimensions consistent with placeholder aspect ratios. Do you want to add buttons to your Navigation block? Now you can do it conveniently without a line of code.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/design-tools.png?resize=1024%2C666&ssl=1" alt="Decorative image with text " />



<h3 class="wp-block-heading">Make your images stand out</h3>



<p>Enable lightbox functionality to let your site visitors enjoy full-screen, interactive images on click. Apply it globally or to specific images to customize the viewing experience.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/lightbox.png?resize=1024%2C666&ssl=1" alt="Decorative photo of a triangular building structure with a " />



<h3 class="wp-block-heading">Rename Group blocks</h3>



<p>Set custom names for Group blocks to organize and distinguish areas of your content easily. These names will be visible in List View.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/rename.png?resize=1024%2C666&ssl=1" alt="Screenshot of the List View tool. It shows a Group block renamed as " />



<h3 class="wp-block-heading">Preview images in List View</h3>



<p>New previews for Gallery and Image blocks in List View let you visualize and locate where images on your content are at a glance.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/list-view-images.png?resize=1024%2C666&ssl=1" alt="Screenshot of the List View tool, showing the new image previews for the Image and Gallery blocks." class="wp-image-16282" />



<h3 class="wp-block-heading">Share patterns across sites</h3>



<p>Need to use your custom patterns on another site? Import and export them as JSON files from the Site Editor&#8217;s patterns view.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/exporting-patterns-1.png?resize=1024%2C666&ssl=1" alt="Screenshot showing the " />



<h3 class="wp-block-heading">Introducing Block Hooks</h3>



<p><a href="https://make.wordpress.org/core/2023/10/15/introducing-block-hooks-for-dynamic-blocks/">Block Hooks</a> enables developers to automatically insert dynamic blocks at specific content locations, enriching the extensibility of block themes through plugins. While considered a developer tool, this feature is geared to respect your preferences and gives you complete control to add, dismiss, and customize auto-inserted blocks to your needs.</p>



<img width="1024" height="666" src="https://i0.wp.com/wordpress.org/news/files/2023/11/block-hooks.png?resize=1024%2C666&ssl=1" alt="Cropped screenshot showing a mini shopping cart (in a red dotted circle) inserted into a navigation menu by Block Hooks." class="wp-image-16284" />



<h3 class="wp-block-heading">Performance wins</h3>



<p>This release includes more than 100 performance-related updates for a faster and more efficient experience. Notable enhancements focus on <a href="https://make.wordpress.org/core/2023/10/17/improvements-to-template-loading-in-wordpress-6-4/">template loading performance</a> for themes (including Twenty Twenty-Four), <a href="https://make.wordpress.org/core/2023/10/17/script-loading-changes-in-wordpress-6-4/">usage of the script loading strategies</a> “defer” and “async” in core, blocks, and themes, and <a href="https://make.wordpress.org/core/2023/10/17/new-option-functions-in-6-4/">optimization of autoloaded options</a>.</p>



<h3 class="wp-block-heading">Accessibility highlights</h3>



<p>Every release is committed to making WordPress accessible to everyone. WordPress 6.4 brings several List View improvements and aria-label support for the Navigation block, among other highlights. The admin user interface includes enhancements to button placements, &#8220;Add New&#8221; menu items context, and Site Health spoken messages. <a href="https://make.wordpress.org/core/2023/11/03/wordpress-6-4-accessibility-improvements/">Learn more about all the updates</a> aimed at improving accessibility.</p>



<h3 class="wp-block-heading">Other notes of interest</h3>



<ul>
<li>PHP 8.1 or 8.2 are recommended for use with WordPress 6.4. Find in-depth details on PHP support <a href="https://wordpress.org/news/2023/10/wordpress-6-4s-php-compatibility/">in this post</a>.</li>



<li>WordPress 6.4 <a href="https://make.wordpress.org/core/2023/10/16/changes-to-attachment-pages/">disables attachment pages</a> for new installations.</li>
</ul>



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



<h2 class="wp-block-heading">Learn more about WordPress 6.4</h2>



<p>Check out the new <a href="https://wordpress.org/download/releases/6-4/">WordPress 6.4 page</a> to learn more about the numerous enhancements and features of this release.</p>



<p>Explore <a href="https://learn.wordpress.org/">Learn WordPress</a> for quick how-to videos, <a href="https://learn.wordpress.org/social-learning/">online workshops</a>, and other free resources to level up your WordPress knowledge and skills.</p>



<p>If you are looking for detailed technical notes on new changes, the <a href="https://make.wordpress.org/core/2023/10/23/wordpress-6-4-field-guide/">WordPress 6.4 Field Guide</a> is for you. Don&#8217;t forget to subscribe to the <a href="https://developer.wordpress.org/news/">Developer Blog</a> to stay on top of the latest development updates, tutorials, and more.</p>



<p>For more information on installation, fixes, and file changes, visit the <a href="https://wordpress.org/documentation/wordpress-version/version-6-4/">6.4 release notes</a>.</p>



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



<h2 class="wp-block-heading">The 6.4 release squad</h2>



<p>​​The WordPress 6.4 release comes to you from an <strong>underrepresented gender release squad</strong> to welcome and empower diverse voices in the WordPress open source project.</p>



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



<blockquote class="wp-block-quote">
<p class="has-extra-large-font-size">Being part of the 6.4 release coordination team has allowed me to closely observe the intricate release process, where every detail, no matter how minor, is meticulously addressed—taking into account various factors like performance and backward compatibility. There’s still much to learn, but I feel fortunate to have had the chance to contribute to WordPress 6.4.</p>
<cite>Akshaya Rane, 6.4 release coordinator team member</cite></blockquote>



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



<p>Over several weeks, the 6.4 release squad kept the release on track and moving forward by leading collective work, connecting ideas, and removing roadblocks.</p>



<ul>
<li>Release Lead: <a href="https://profiles.wordpress.org/chanthaboune/">Josepha Haden Chomphosy</a></li>



<li>Release Coordinators: <a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a>, <a href="https://profiles.wordpress.org/metalandcoffee/">Ebonie Butler</a>, <a href="https://profiles.wordpress.org/akshayar/">Akshaya Rane</a>, <a href="https://profiles.wordpress.org/francina/">Francesca Marano</a>. Cohort: <a href="https://profiles.wordpress.org/thewebprincess/">Dee Teal</a>, <a href="https://profiles.wordpress.org/jaimieolmstead/">Jaimie Olmstead</a>, <a href="https://profiles.wordpress.org/jyolsna/">Jyolsna J E</a>, <a href="https://profiles.wordpress.org/marybaum/">Mary Baum</a></li>



<li>Core Tech Leads: <a href="https://profiles.wordpress.org/mikeschroder/">Mike Schroder</a>, <a href="https://profiles.wordpress.org/hellofromtonya/">Tonya Mork</a>. Cohort: <a href="https://profiles.wordpress.org/pypwalters/">Stephanie Walters</a></li>



<li>Editor Tech Leads:&nbsp; <a href="https://profiles.wordpress.org/mikachan/">Sarah Norris</a>, <a href="https://profiles.wordpress.org/siobhyb/">Siobhan Bamber</a>, <a href="https://profiles.wordpress.org/karmatosed/">Tammie Lister</a>. Cohort: <a href="https://profiles.wordpress.org/68kheart/">Devan Ferguson</a>, <a href="https://profiles.wordpress.org/battelfred/">Frédérique Battel</a>, <a href="https://profiles.wordpress.org/jessicagoddard/">Jessica Goddard</a>, <a href="https://profiles.wordpress.org/1happyplace/">Katie Ayres</a>, <a href="https://profiles.wordpress.org/martatorre/">Marta Torre</a>, <a href="https://profiles.wordpress.org/ngreennc/">Nyasha Green</a>, <a href="https://profiles.wordpress.org/poojabhimani/">Pooja Bhimani</a></li>



<li>Core Triage Leads: <a href="https://profiles.wordpress.org/nicolefurlan/">Nicole Furlan</a>, <a href="https://profiles.wordpress.org/oglekler/">Olga Gleckler</a></li>



<li>Editor Triage Leads: <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a>, <a href="https://profiles.wordpress.org/bph/">Birgit Pauli-Haack</a>. Cohort: <a href="https://profiles.wordpress.org/emilyatmobtown/">Emily Leffler Schulman</a></li>



<li>Documentation Leads: <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a>, <a href="https://profiles.wordpress.org/femkreations/">Femy Praseeth</a>, <a href="https://profiles.wordpress.org/611shabnam/">Mushrit Shabnam</a>. Cohort: <a href="https://profiles.wordpress.org/itsjustdj/">D.J. Billings</a>, <a href="https://wordpress.org/support/users/codente/">Jamie VanRaalte</a>, <a href="https://profiles.wordpress.org/newyorkerlaura/">Laura Byrne</a>, <a href="https://profiles.wordpress.org/baxbridge/">Tiffany Bridge</a>, <a href="https://profiles.wordpress.org/planningwrite/">Winstina Hughes</a></li>



<li>Marketing and Communications Leads: <a href="https://profiles.wordpress.org/meher/">Meher Bala</a>, <a href="https://profiles.wordpress.org/rmartinezduque/">Reyes Martínez</a>, <a href="https://profiles.wordpress.org/sereedmedia/">Sé Reed</a>. Cohort: <a href="https://profiles.wordpress.org/meaganhanes/">Meagan Hanes</a>, <a href="https://profiles.wordpress.org/michelleames/">Michelle Frechette</a></li>



<li>Test Lead: <a href="https://profiles.wordpress.org/webtechpooja/">Pooja Derashri</a>. Cohort: <a href="https://profiles.wordpress.org/annebovelett/">Anne Bovelett</a>, <a href="https://profiles.wordpress.org/coachbirgit/">Birgit Olzem</a></li>



<li>Design Leads: <a href="https://profiles.wordpress.org/elmastudio/">Ellen Bauer</a>, <a href="https://profiles.wordpress.org/estelaris/">Estela Rueda</a>. Cohort: <a href="https://profiles.wordpress.org/allisonplus/">Allison Tarr</a>, <a href="https://profiles.wordpress.org/acirujano/">Ana Cirujano</a>, <a href="https://profiles.wordpress.org/cathibosco1/">Cathi Bosco</a>, <a href="https://profiles.wordpress.org/nudge/">Sonia Gaballa</a>, <a href="https://profiles.wordpress.org/ohia/">Ohia</a></li>



<li>Performance Lead: <a href="https://profiles.wordpress.org/clarkeemily/">Emily Clarke</a>. Cohort: <a href="https://profiles.wordpress.org/linsoftware/">Linnea Huxford</a></li>



<li>Training Leads: <a href="https://profiles.wordpress.org/courtneypk/">Courtney P.K.</a>, <a href="https://profiles.wordpress.org/courane01/">Courtney Roberston</a></li>



<li>Default Theme Leads: <a href="https://profiles.wordpress.org/luminuu/">Jessica Lyschik</a>, <a href="https://profiles.wordpress.org/onemaggie/">Maggie Cabrera</a></li>
</ul>



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



<h2 class="wp-block-heading">Thank you, contributors</h2>



<p>WordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a global and diverse community of people working together to strengthen the software.</p>



<p>WordPress 6.4 reflects the countless efforts and passion of <strong>more than 600 contributors in at least 56 countries</strong>. This release also welcomed over 170 first-time contributors!</p>



<p>Their collaboration delivered more than 1150 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.</p>



<p class="is-style-wporg-props-long alignfull"><a href="https://profiles.wordpress.org/6adminit/">6adminit</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/aayusha/">aayusha</a> · <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a> · <a href="https://profiles.wordpress.org/omarabid/">Abid Omar</a> · <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a> · <a href="https://profiles.wordpress.org/adhun/">Adhun Anand</a> · <a href="https://profiles.wordpress.org/ajmcfadyen/">admcfajn</a> · <a href="https://profiles.wordpress.org/adrianduffell/">adrianduffell</a> · <a href="https://profiles.wordpress.org/aegkr/">aegkr</a> · <a href="https://profiles.wordpress.org/ahardyjpl/">ahardyjpl</a> · <a href="https://profiles.wordpress.org/ahmedgeek/">Ahmed Hussein</a> · <a href="https://profiles.wordpress.org/chaion07/">Ahmed Kabir Chaion</a> · <a href="https://profiles.wordpress.org/ajakaroth/">ajakaroth</a> · <a href="https://profiles.wordpress.org/wildworks/">Aki Hamano</a> · <a href="https://profiles.wordpress.org/akihiroharai/">Akihiro Harai</a> · <a href="https://profiles.wordpress.org/atachibana/">Akira Tachibana</a> · <a href="https://profiles.wordpress.org/akshayar/">Akshaya Rane</a> · <a href="https://profiles.wordpress.org/alaminfirdows/">Al-Amin Firdows</a> · <a href="https://profiles.wordpress.org/aljullu/">Albert Juh&#233; Lluveras</a> · <a href="https://profiles.wordpress.org/xknown/">Alex Concha</a> · <a href="https://profiles.wordpress.org/alexkingorg/">Alex King</a> · <a href="https://profiles.wordpress.org/ajlende/">Alex Lende</a> · <a href="https://profiles.wordpress.org/alexstine/">Alex Stine</a> · <a href="https://profiles.wordpress.org/alexandrebuffet/">Alexandre Buffet</a> · <a href="https://profiles.wordpress.org/alishabajracharya27/">Alisha Bajracharya</a> · <a href="https://profiles.wordpress.org/allisonplus/">allisonplus</a> · <a href="https://profiles.wordpress.org/alvitazwar052/">Alvi Tazwar</a> · <a href="https://profiles.wordpress.org/amedv/">amedv</a> · <a href="https://profiles.wordpress.org/acirujano/">Ana Cirujano</a> · <a href="https://profiles.wordpress.org/anlino/">Anders Nor&#233;n</a> · <a href="https://profiles.wordpress.org/oandregal/">Andr&#233;</a> · <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a> · <a href="https://profiles.wordpress.org/andraganescu/">Andrei Draganescu</a> · <a href="https://profiles.wordpress.org/andrewhayward/">Andrew Hayward</a> · <a href="https://profiles.wordpress.org/l1nuxjedi/">Andrew Hutchings</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/afragen/">Andy Fragen</a> · <a href="https://profiles.wordpress.org/apeatling/">Andy Peatling</a> · <a href="https://profiles.wordpress.org/wpgurudev/">Ankit Gade</a> · <a href="https://profiles.wordpress.org/ankit-k-gupta/">Ankit K Gupta</a> · <a href="https://profiles.wordpress.org/ankitmaru/">Ankit Panchal</a> · <a href="https://profiles.wordpress.org/annashopina/">Anna</a> · <a href="https://profiles.wordpress.org/askdesign/">Anne Katzeff</a> · <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a> · <a href="https://profiles.wordpress.org/annebovelett/">Anne-Mieke Bovelett</a> · <a href="https://profiles.wordpress.org/anphira/">anphira</a> · <a href="https://profiles.wordpress.org/antpb/">Anthony Burchell</a> · <a href="https://profiles.wordpress.org/aplauche/">Anton Plauche</a> · <a href="https://profiles.wordpress.org/atimmer/">Anton Timmermans</a> · <a href="https://profiles.wordpress.org/antonvlasenko/">Anton Vlasenko</a> · <a href="https://profiles.wordpress.org/anveshika/">Anveshika Srivastava</a> · <a href="https://profiles.wordpress.org/archon810/">archon810</a> · <a href="https://profiles.wordpress.org/arena/">arena</a> · <a href="https://profiles.wordpress.org/aristath/">Ari Stathopoulos</a> · <a href="https://profiles.wordpress.org/armondal/">Arnab Mondal</a> · <a href="https://profiles.wordpress.org/artemiosans/">Artemio Morales</a> · <a href="https://profiles.wordpress.org/arthur791004/">Arthur Chu</a> · <a href="https://profiles.wordpress.org/asafm7/">asafm7</a> · <a href="https://profiles.wordpress.org/aslamdoctor/">Aslam Doctor</a> · <a href="https://profiles.wordpress.org/aurooba/">Aurooba Ahmed</a> · <a href="https://profiles.wordpress.org/austinginder/">Austin Ginder</a> · <a href="https://profiles.wordpress.org/ayeshrajans/">Ayesh Karunaratne</a> · <a href="https://profiles.wordpress.org/azharckra/">azharckra</a> · <a href="https://profiles.wordpress.org/balub/">Balu B</a> · <a href="https://profiles.wordpress.org/bangank36/">bangank36</a> · <a href="https://profiles.wordpress.org/barbmiller/">barbmiller</a> · <a href="https://profiles.wordpress.org/bartkalisz/">Bart</a> · <a href="https://profiles.wordpress.org/basiliskan/">Basilis Kanonidis</a> · <a href="https://profiles.wordpress.org/beafialho/">Beatriz Fialho</a> · <a href="https://profiles.wordpress.org/behoney/">behoney</a> · <a href="https://profiles.wordpress.org/benharri/">ben</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/ubernaut/">Ben Hansen</a> · <a href="https://profiles.wordpress.org/benimub/">benimub</a> · <a href="https://profiles.wordpress.org/bfintal/">Benjamin Intal</a> · <a href="https://profiles.wordpress.org/benjamin_zekavica/">Benjamin Zekavica</a> · <a href="https://profiles.wordpress.org/benjaminknox/">benjaminknox</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/bijayyadav/">Bijay Yadav</a> · <a href="https://profiles.wordpress.org/binsaifullah/">Binsaifullah</a> · <a href="https://profiles.wordpress.org/bplv/">Biplav</a> · <a href="https://profiles.wordpress.org/coachbirgit/">Birgit Olzem</a> · <a href="https://profiles.wordpress.org/bph/">Birgit Pauli-Haack</a> · <a href="https://profiles.wordpress.org/bradley2083/">Block Themes Pro</a> · <a href="https://profiles.wordpress.org/bmalsht/">bmalsht</a> · <a href="https://profiles.wordpress.org/gitlost/">bonger</a> · <a href="https://profiles.wordpress.org/bookwyrm/">bookwyrm</a> · <a href="https://profiles.wordpress.org/boonebgorges/">Boone Gorges</a> · <a href="https://profiles.wordpress.org/bor0/">Boro Sitnikovski</a> · <a href="https://profiles.wordpress.org/bjorsch/">Brad Jorsch</a> · <a href="https://profiles.wordpress.org/crazyjaco/">Bradley Jacobs</a> · <a href="https://profiles.wordpress.org/kraftbj/">Brandon Kraft</a> · <a href="https://profiles.wordpress.org/bvreeman22/">Brandon Vreeman</a> · <a href="https://profiles.wordpress.org/bgardner/">Brian Gardner</a> · <a href="https://profiles.wordpress.org/masteradhoc/">Brian Haas</a> · <a href="https://profiles.wordpress.org/brookemk/">Brooke</a> · <a href="https://profiles.wordpress.org/brookedot/">Brooke.</a> · <a href="https://profiles.wordpress.org/trynet/">Bud Kraus</a> · <a href="https://profiles.wordpress.org/icaleb/">Caleb Burks</a> · <a href="https://profiles.wordpress.org/snicco/">Calvin Alkan</a> · <a href="https://profiles.wordpress.org/karl94/">Carlo Cannas</a> · <a href="https://profiles.wordpress.org/cbravobernal/">Carlos Bravo</a> · <a href="https://profiles.wordpress.org/carlosgprim/">Carlos G. P.</a> · <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a> · <a href="https://profiles.wordpress.org/cathibosco1/">Cathi Bosco</a> · <a href="https://profiles.wordpress.org/ceer/">ceer</a> · <a href="https://profiles.wordpress.org/shireling/">Chad Chadbourne</a> · <a href="https://profiles.wordpress.org/chasedsiedu/">chased@si.edu</a> · <a href="https://profiles.wordpress.org/chintan1896/">Chintan hingrajiya</a> · <a href="https://profiles.wordpress.org/chipbennett/">Chip Bennett</a> · <a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a> · <a href="https://profiles.wordpress.org/crunnells/">Chris Runnells</a> · <a href="https://profiles.wordpress.org/chriscct7/">chriscct7</a> · <a href="https://profiles.wordpress.org/chrisdesrochers/">chrisdesrochers</a> · <a href="https://profiles.wordpress.org/codersantosh/">codersantosh</a> · <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a> · <a href="https://profiles.wordpress.org/coreyw/">Corey Worrell</a> · <a href="https://profiles.wordpress.org/courtneypk/">Courtney Patubo Kranzke</a> · <a href="https://profiles.wordpress.org/courane01/">Courtney Robertson</a> · <a href="https://profiles.wordpress.org/mitogh/">Crisoforo Gaspar</a> · <a href="https://profiles.wordpress.org/crstauf/">crstauf</a> · <a href="https://profiles.wordpress.org/littlebigthing/">Csaba (LittleBigThings)</a> · <a href="https://profiles.wordpress.org/cu121/">Cupid Chakma</a> · <a href="https://profiles.wordpress.org/didierjm/">cybeardjm</a> · <a href="https://profiles.wordpress.org/cyberchicken/">Cyberchicken</a> · <a href="https://profiles.wordpress.org/extendwings/">Daisuke Takahashi</a> · <a href="https://profiles.wordpress.org/dajeema/">Dajeema Rai</a> · <a href="https://profiles.wordpress.org/colorful-tones/">Damon Cook</a> · <a href="https://profiles.wordpress.org/damonsharp/">Damon Sharp</a> · <a href="https://profiles.wordpress.org/dantovbein/">Dan Tovbein</a> · <a href="https://profiles.wordpress.org/danielbachhuber/">Daniel Bachhuber</a> · <a href="https://profiles.wordpress.org/talldanwp/">Daniel Richards</a> · <a href="https://profiles.wordpress.org/danieldudzic/">danieldudzic</a> · <a href="https://profiles.wordpress.org/mte90/">Daniele Scasciafratte</a> · <a href="https://profiles.wordpress.org/queerdevperson/">Danielle Zarcaro</a> · <a href="https://profiles.wordpress.org/danieltj/">danieltj</a> · <a href="https://profiles.wordpress.org/darerodz/">darerodz</a> · <a href="https://profiles.wordpress.org/dkotter/">Darin Kotter</a> · <a href="https://profiles.wordpress.org/darkfate/">darkfate</a> · <a href="https://profiles.wordpress.org/nerrad/">Darren Ethier (nerrad)</a> · <a href="https://profiles.wordpress.org/darshitrajyaguru97/">Darshit Rajyaguru</a> · <a href="https://profiles.wordpress.org/davelo/">Dave Loodts</a> · <a href="https://profiles.wordpress.org/dave03/">dave03</a> · <a href="https://profiles.wordpress.org/davidbaumwald/">David Baumwald</a> · <a href="https://profiles.wordpress.org/davidbinda/">David Biňovec</a> · <a href="https://profiles.wordpress.org/dpcalhoun/">David Calhoun</a> · <a href="https://profiles.wordpress.org/desmith/">David E. Smith</a> · <a href="https://profiles.wordpress.org/dfavor/">David Favor</a> · <a href="https://profiles.wordpress.org/dlh/">David Herrera</a> · <a href="https://profiles.wordpress.org/dryanpress/">David Ryan</a> · <a href="https://profiles.wordpress.org/get_dave/">David Smith</a> · <a href="https://profiles.wordpress.org/dawidurbanski/">Dawid Urbanski</a> · <a href="https://profiles.wordpress.org/daxelrod/">daxelrod</a> · <a href="https://profiles.wordpress.org/arnedb/">De Belser Arne</a> · <a href="https://profiles.wordpress.org/dsas/">Dean Sas</a> · <a href="https://profiles.wordpress.org/thewebprincess/">Dee Teal</a> · <a href="https://profiles.wordpress.org/deepakvijayan/">Deepak Vijayan</a> · <a href="https://profiles.wordpress.org/dingo_d/">Denis Žoljom</a> · <a href="https://profiles.wordpress.org/dmsnell/">Dennis Snell</a> · <a href="https://profiles.wordpress.org/derekblank/">Derek Blank</a> · <a href="https://profiles.wordpress.org/emrikol/">Derrick Tennant</a> · <a href="https://profiles.wordpress.org/68kheart/">Devan Ferguson</a> · <a href="https://profiles.wordpress.org/dhamibirendra/">dhamibirendra</a> · <a href="https://profiles.wordpress.org/dharm1025/">Dharmesh Patel</a> · <a href="https://profiles.wordpress.org/dhrumilk/">Dhrumil Kumbhani</a> · <a href="https://profiles.wordpress.org/dhruvishah2203/">Dhruvi Shah</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/dimitrism/">Dimitris Mitsis</a> · <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a> · <a href="https://profiles.wordpress.org/itsjustdj/">DJ</a> · <a href="https://profiles.wordpress.org/djcowan/">dj.cowan</a> · <a href="https://profiles.wordpress.org/ocean90/">Dominik Schilling</a> · <a href="https://profiles.wordpress.org/doughamlin/">doughamlin</a> · <a href="https://profiles.wordpress.org/drewapicture/">Drew Jaynes</a> · <a href="https://profiles.wordpress.org/elrae/">Earle Davies</a> · <a href="https://profiles.wordpress.org/metalandcoffee/">Ebonie Butler</a> · <a href="https://profiles.wordpress.org/ediamin/">Edi Amin</a> · <a href="https://profiles.wordpress.org/cais/">Edward Caissie</a> · <a href="https://profiles.wordpress.org/ehtis/">Ehtisham S.</a> · <a href="https://profiles.wordpress.org/ellatrix/">Ella van Durpe</a> · <a href="https://profiles.wordpress.org/elmastudio/">Ellen Bauer</a> · <a href="https://profiles.wordpress.org/emailjoey/">emailjoey</a> · <a href="https://profiles.wordpress.org/codex-m/">Emerson Maningo</a> · <a href="https://profiles.wordpress.org/clarkeemily/">Emily Clarke</a> · <a href="https://profiles.wordpress.org/emilyatmobtown/">Emily Leffler Schulman</a> · <a href="https://profiles.wordpress.org/emirpprime/">emirpprime</a> · <a href="https://profiles.wordpress.org/enodekciw/">enodekciw</a> · <a href="https://profiles.wordpress.org/lopo/">Enrico Battocchi</a> · <a href="https://profiles.wordpress.org/kebbet/">Erik Betshammar</a> · <a href="https://profiles.wordpress.org/esratpopy/">Esrat Sultana Popy</a> · <a href="https://profiles.wordpress.org/estelaris/">Estela Rueda</a> · <a href="https://profiles.wordpress.org/fabiankaegy/">Fabian K&#228;gy</a> · <a href="https://profiles.wordpress.org/gaambo/">Fabian Todt</a> · <a href="https://profiles.wordpress.org/fabiorubioglio/">Fabio Rubioglio</a> · <a href="https://profiles.wordpress.org/faisal03/">Faisal Alvi</a> · <a href="https://profiles.wordpress.org/felipeelia/">Felipe Elia</a> · <a href="https://profiles.wordpress.org/flixos90/">Felix Arntz</a> · <a href="https://profiles.wordpress.org/femkreations/">Femy Praseeth</a> · <a href="https://profiles.wordpress.org/floydwilde/">floydwilde</a> · <a href="https://profiles.wordpress.org/foliovision/">FolioVision</a> · <a href="https://profiles.wordpress.org/francina/">Francesca Marano</a> · <a href="https://profiles.wordpress.org/battelfred/">Fredde Battel</a> · <a href="https://profiles.wordpress.org/fzhantw/">fzhantw</a> · <a href="https://profiles.wordpress.org/mintindeed/">Gabriel Koen</a> · <a href="https://profiles.wordpress.org/pauthake015/">Ganesh Dahal</a> · <a href="https://profiles.wordpress.org/garrett-eclipse/">Garrett Hyder</a> · <a href="https://profiles.wordpress.org/garyc40/">Gary Cao</a> · <a href="https://profiles.wordpress.org/pento/">Gary Pendergast</a> · <a href="https://profiles.wordpress.org/soulseekah/">Gennady Kovshenin</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/geriux/">Gerardo Pacheco</a> · <a href="https://profiles.wordpress.org/mokagio/">Gio Lodi</a> · <a href="https://profiles.wordpress.org/glendaviesnz/">Glen Davies</a> · <a href="https://profiles.wordpress.org/gnanasekaran/">Gnanasekaran Loganathan</a> · <a href="https://profiles.wordpress.org/ingeniumed/">Gopal Krishnan</a> · <a href="https://profiles.wordpress.org/90lines/">GOZER</a> · <a href="https://profiles.wordpress.org/gpotter/">gpotter</a> · <a href="https://profiles.wordpress.org/grantmkin/">Grant M. Kinney</a> · <a href="https://profiles.wordpress.org/gregross/">Greg Ross</a> · <a href="https://profiles.wordpress.org/gziolo/">Greg Ziółkowski</a> · <a href="https://profiles.wordpress.org/gregfuller/">gregfuller</a> · <a href="https://profiles.wordpress.org/guss77/">Guss77</a> · <a href="https://profiles.wordpress.org/bordoni/">Gustavo Bordoni</a> · <a href="https://profiles.wordpress.org/gvgvgvijayan/">gvgvgvijayan</a> · <a href="https://profiles.wordpress.org/priethor/">H&#233;ctor Prieto</a> · <a href="https://profiles.wordpress.org/poran766/">H.M. Mushfiqur Rahman</a> · <a href="https://profiles.wordpress.org/hanneslsm/">hanneslsm</a> · <a href="https://profiles.wordpress.org/hztyfoon/">Hanzala Taifun</a> · <a href="https://profiles.wordpress.org/hareesh-pillai/">Hareesh S</a> · <a href="https://profiles.wordpress.org/harshgajipara/">Harsh Gajipara</a> · <a href="https://profiles.wordpress.org/hasanuzzamanshamim/">Hasanuzzaman</a> · <a href="https://profiles.wordpress.org/hazdiego/">Haz</a> · <a href="https://profiles.wordpress.org/helen/">Helen Hou-Sandi</a> · <a href="https://profiles.wordpress.org/tejwanihemant/">Hemant Tejwani</a> · <a href="https://profiles.wordpress.org/hbhalodia/">Hit Bhalodia</a> · <a href="https://profiles.wordpress.org/hlunter/">hlunter</a> · <a href="https://profiles.wordpress.org/howdy_mcgee/">Howdy_McGee</a> · <a href="https://profiles.wordpress.org/huzaifaalmesbah/">Huzaifa Al Mesbah</a> · <a href="https://profiles.wordpress.org/iandunn/">Ian Dunn</a> · <a href="https://profiles.wordpress.org/incursadesigns/">Incursa Designs</a> · <a href="https://profiles.wordpress.org/ironprogrammer/">ironprogrammer</a> · <a href="https://profiles.wordpress.org/isabel_brison/">Isabel Brison</a> · <a href="https://profiles.wordpress.org/itecrs/">itecrs</a> · <a href="https://profiles.wordpress.org/ivanzhuck/">Ivan Zhuck</a> · <a href="https://profiles.wordpress.org/jaimieolmstead/">jaimieolmstead</a> · <a href="https://profiles.wordpress.org/jakariaistauk/">Jakaria Istauk</a> · <a href="https://profiles.wordpress.org/jakemgold/">Jake Goldman</a> · <a href="https://profiles.wordpress.org/whyisjake/">Jake Spurlock</a> · <a href="https://profiles.wordpress.org/bonkerz/">James</a> · <a href="https://profiles.wordpress.org/thelovelist/">James Janco</a> · <a href="https://profiles.wordpress.org/jameskoster/">James Koster</a> · <a href="https://profiles.wordpress.org/james roberts/">James Roberts</a> · <a href="https://profiles.wordpress.org/james0r/">james0r</a> · <a href="https://profiles.wordpress.org/jamiemchale/">Jamie McHale</a> · <a href="https://profiles.wordpress.org/perrelet/">Jamie Perrelet</a> · <a href="https://profiles.wordpress.org/codente/">Jamie VanRaalte</a> · <a href="https://profiles.wordpress.org/jane/">jane</a> · <a href="https://profiles.wordpress.org/jsnajdr/">Jarda Snajdr</a> · <a href="https://profiles.wordpress.org/yari2u/">Jari Vuorenmaa</a> · <a href="https://profiles.wordpress.org/ipajen/">Jarko Piironen</a> · <a href="https://profiles.wordpress.org/pbking/">Jason Crist</a> · <a href="https://profiles.wordpress.org/jastos/">jastos</a> · <a href="https://profiles.wordpress.org/audrasjb/">Jean-Baptiste Audras</a> · <a href="https://profiles.wordpress.org/jblz/">Jeff Bowen</a> · <a href="https://profiles.wordpress.org/jeffeverhart383/">Jeff Everhart</a> · <a href="https://profiles.wordpress.org/jffng/">Jeff Ong</a> · <a href="https://profiles.wordpress.org/jeffikus/">jeffikus</a> · <a href="https://profiles.wordpress.org/jeffpaul/">Jeffrey Paul</a> · <a href="https://profiles.wordpress.org/jeflopodev/">jeflopo</a> · <a href="https://profiles.wordpress.org/jeremyfelt/">Jeremy Felt</a> · <a href="https://profiles.wordpress.org/jeherve/">Jeremy Herve</a> · <a href="https://profiles.wordpress.org/jeremyyip/">Jeremy Yip</a> · <a href="https://profiles.wordpress.org/jeryj/">jeryj</a> · <a href="https://profiles.wordpress.org/jesin/">Jesin A</a> · <a href="https://profiles.wordpress.org/jessplease/">Jessica Duarte</a> · <a href="https://profiles.wordpress.org/jessicagoddard/">Jessica Goddard</a> · <a href="https://profiles.wordpress.org/luminuu/">Jessica Lyschik</a> · <a href="https://profiles.wordpress.org/jick/">Jick</a> · <a href="https://profiles.wordpress.org/jipmoors/">Jip Moors</a> · <a href="https://profiles.wordpress.org/jivygraphics/">jivygraphics</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/joen/">Joen A.</a> · <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a> · <a href="https://profiles.wordpress.org/bitmachina/">John Hooks</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/jb510/">Jon Brown</a> · <a href="https://profiles.wordpress.org/duck_/">Jon Cave</a> · <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a> · <a href="https://profiles.wordpress.org/spacedmonkey/">Jonny Harris</a> · <a href="https://profiles.wordpress.org/jonoaldersonwp/">Jono Alderson</a> · <a href="https://profiles.wordpress.org/varjodesigns/">Joona</a> · <a href="https://profiles.wordpress.org/joostdevalk/">Joost de Valk</a> · <a href="https://profiles.wordpress.org/jordanpak/">JordanPak</a> · <a href="https://profiles.wordpress.org/jordesign/">jordesign</a> · <a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a> · <a href="https://profiles.wordpress.org/dunhakdis/">Joseph G.</a> · <a href="https://profiles.wordpress.org/chanthaboune/">Josepha Haden</a> · <a href="https://profiles.wordpress.org/joshcanhelp/">joshcanhelp</a> · <a href="https://profiles.wordpress.org/joshuatf/">joshuatf</a> · <a href="https://profiles.wordpress.org/jrtashjian/">JR Tashjian</a> · <a href="https://profiles.wordpress.org/juanfra/">Juan Aldasoro</a> · <a href="https://profiles.wordpress.org/juanmaguitar/">JuanMa Garrido</a> · <a href="https://profiles.wordpress.org/jrf/">Juliette Reinders Folmer</a> · <a href="https://profiles.wordpress.org/greenshady/">Justin Tadlock</a> · <a href="https://profiles.wordpress.org/jyolsna/">Jyolsna J E</a> · <a href="https://profiles.wordpress.org/ashikur698/">K M Ashikur Rahman</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/kalmang/">Kalmang</a> · <a href="https://profiles.wordpress.org/kalpeshh/">Kalpesh</a> · <a href="https://profiles.wordpress.org/bosskhj/">Kamrul Hasan</a> · <a href="https://profiles.wordpress.org/karlijnbk/">Karlijn Bok</a> · <a href="https://profiles.wordpress.org/karmacharya50/">karmacharya50</a> · <a href="https://profiles.wordpress.org/karolmanijak/">Karol Manijak</a> · <a href="https://profiles.wordpress.org/thekt12/">Karthik Thayyil</a> · <a href="https://profiles.wordpress.org/1happyplace/">Katie Ayres</a> · <a href="https://profiles.wordpress.org/kawsaralameven/">kawsaralameven</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/kevinfodness/">Kevin Fodness</a> · <a href="https://profiles.wordpress.org/p51labs/">Kevin Miller</a> · <a href="https://profiles.wordpress.org/khleomix/">khleomix</a> · <a href="https://profiles.wordpress.org/khokansardar/">Khokan Sardar</a> · <a href="https://profiles.wordpress.org/kimannwall/">Kim Coleman</a> · <a href="https://profiles.wordpress.org/kishanjasani/">Kishan Jasani</a> · <a href="https://profiles.wordpress.org/kkmuffme/">kkmuffme</a> · <a href="https://profiles.wordpress.org/olein/">Koji Kuno</a> · <a href="https://profiles.wordpress.org/kovshenin/">Konstantin Kovshenin</a> · <a href="https://profiles.wordpress.org/obenland/">Konstantin Obenland</a> · <a href="https://profiles.wordpress.org/kopila47/">Kopila Shrestha</a> · <a href="https://profiles.wordpress.org/krokodok/">krokodok</a> · <a href="https://profiles.wordpress.org/krupalpanchal/">Krupal Panchal</a> · <a href="https://profiles.wordpress.org/ktaron/">ktaron</a> · <a href="https://profiles.wordpress.org/labunchemjong/">Labun Chemjong</a> · <a href="https://profiles.wordpress.org/lancewillett/">Lance Willett</a> · <a href="https://profiles.wordpress.org/lhe2012/">LarryWEB</a> · <a href="https://profiles.wordpress.org/lastsplash/">lastsplash (a11n)</a> · <a href="https://profiles.wordpress.org/laumindproductscomau/">lau@mindproducts.com.au</a> · <a href="https://profiles.wordpress.org/launchinteractive/">launchinteractive</a> · <a href="https://profiles.wordpress.org/lada7042/">Laura Adamonis</a> · <a href="https://profiles.wordpress.org/newyorkerlaura/">Laura Byrne</a> · <a href="https://profiles.wordpress.org/laurelfulford/">laurelfulford</a> · <a href="https://profiles.wordpress.org/oncecoupled/">Lauren</a> · <a href="https://profiles.wordpress.org/luckybhumkar/">Laxmikant Bhumkar</a> · <a href="https://profiles.wordpress.org/leewillis77/">Lee Willis</a> · <a href="https://profiles.wordpress.org/0mirka00/">Lena Morita</a> · <a href="https://profiles.wordpress.org/lgladdy/">Liam Gladdy</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/lloydbudd/">Lloyd Budd</a> · <a href="https://profiles.wordpress.org/thelovekesh/">Lovekesh Kumar</a> · <a href="https://profiles.wordpress.org/gigitux/">Luigi</a> · <a href="https://profiles.wordpress.org/zaguiini/">Luis Felipe Zaguini</a> · <a href="https://profiles.wordpress.org/luisherranz/">Luis Herranz</a> · <a href="https://profiles.wordpress.org/lukecavanagh/">Luke Cavanagh</a> · <a href="https://profiles.wordpress.org/lunaluna/">lunaluna</a> · <a href="https://profiles.wordpress.org/lyndauwp/">lyndauwp</a> · <a href="https://profiles.wordpress.org/pagelab/">M&#225;rcio Duarte</a> · <a href="https://profiles.wordpress.org/maciejmackowiak/">maciejmackowiak</a> · <a href="https://profiles.wordpress.org/madejackson/">madejackson</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/mhimon/">Mahbub Hasan Imon</a> · <a href="https://profiles.wordpress.org/maahrokh/">Mahrokh</a> · <a href="https://profiles.wordpress.org/mai21/">Mai</a> · <a href="https://profiles.wordpress.org/travel_girl/">Maja Benke</a> · <a href="https://profiles.wordpress.org/maltfield/">maltfield</a> · <a href="https://profiles.wordpress.org/maneshtimilsina/">Manesh Timilsina</a> · <a href="https://profiles.wordpress.org/manfcarlo/">manfcarlo</a> · <a href="https://profiles.wordpress.org/manzoorwanijk/">Manzoor Wani</a> · <a href="https://profiles.wordpress.org/marcelle42/">marcelle42</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/pereirinha/">Marco Pereirinha</a> · <a href="https://profiles.wordpress.org/marcoevich/">Marcoevich</a> · <a href="https://profiles.wordpress.org/margolisj/">margolisj</a> · <a href="https://profiles.wordpress.org/tyxla/">Marin Atanasov</a> · <a href="https://profiles.wordpress.org/santosguillamot/">Mario Santos</a> · <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a> · <a href="https://profiles.wordpress.org/markjaquith/">Mark Jaquith</a> · <a href="https://profiles.wordpress.org/markoserb/">Marko Ivanovic</a> · <a href="https://profiles.wordpress.org/martatorre/">Marta Torre</a> · <a href="https://profiles.wordpress.org/mhkuu/">Martijn van der Klis</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/masoudnkh/">Masoud NKH</a> · <a href="https://profiles.wordpress.org/mathsgrinds/">mathsgrinds</a> · <a href="https://profiles.wordpress.org/mmaattiiaass/">Matias Benedetto</a> · <a href="https://profiles.wordpress.org/matveb/">Matias Ventura</a> · <a href="https://profiles.wordpress.org/mattkeys/">Matt Keys</a> · <a href="https://profiles.wordpress.org/mwtsn/">Matt Watson</a> · <a href="https://profiles.wordpress.org/mklute101/">Matthaus Klute</a> · <a href="https://profiles.wordpress.org/mattheweppelsheimer/">Matthew Eppelsheimer</a> · <a href="https://profiles.wordpress.org/matthewfarlymn/">Matthew Farlymn</a> · <a href="https://profiles.wordpress.org/mattheu/">Matthew Haines-Young</a> · <a href="https://profiles.wordpress.org/maurodf/">maurodf</a> · <a href="https://profiles.wordpress.org/maxinacube/">Maxwell Morgan</a> · <a href="https://profiles.wordpress.org/maysi/">maysi</a> · <a href="https://profiles.wordpress.org/hrshahin/">Md HR Shahin</a> · <a href="https://profiles.wordpress.org/meaganhanes/">meagan hanes</a> · <a href="https://profiles.wordpress.org/iammehedi1/">Mehedi Hassan</a> · <a href="https://profiles.wordpress.org/meher/">Meher Bala</a> · <a href="https://profiles.wordpress.org/melchoyce/">Mel Choyce-Dwan</a> · <a href="https://profiles.wordpress.org/mer00x/">mer00x</a> · <a href="https://profiles.wordpress.org/merel1988/">merel1988</a> · <a href="https://profiles.wordpress.org/michael-arestad/">Michael Arestad</a> · <a href="https://profiles.wordpress.org/mburridge/">Michael Burridge</a> · <a href="https://profiles.wordpress.org/mshowes/">Michael Showes</a> · <a href="https://profiles.wordpress.org/czapla/">Michal Czaplinski</a> · <a href="https://profiles.wordpress.org/michalooki/">Michalooki</a> · <a href="https://profiles.wordpress.org/michelleblanchette/">Michelle Blanchette</a> · <a href="https://profiles.wordpress.org/michelleames/">Michelle Frechette</a> · <a href="https://profiles.wordpress.org/michi91/">Michi91</a> · <a href="https://profiles.wordpress.org/mcsf/">Miguel Fonseca</a> · <a href="https://profiles.wordpress.org/simison/">Mikael Korpela</a> · <a href="https://profiles.wordpress.org/mikejolley/">Mike Jolley (a11n)</a> · <a href="https://profiles.wordpress.org/mmcalister/">Mike McAlister</a> · <a href="https://profiles.wordpress.org/mikeschinkel/">Mike Schinkel</a> · <a href="https://profiles.wordpress.org/mikeschroder/">Mike Schroder</a> · <a href="https://profiles.wordpress.org/mikestraw/">Mike Straw</a> · <a href="https://profiles.wordpress.org/mikinc860/">Mikin Chauhan</a> · <a href="https://profiles.wordpress.org/gonzomir/">Milen Petrinski - Gonzo</a> · <a href="https://profiles.wordpress.org/mimitips/">mimi</a> · <a href="https://profiles.wordpress.org/mitchellaustin/">mitchellaustin</a> · <a href="https://profiles.wordpress.org/mhshujon/">Monir</a> · <a href="https://profiles.wordpress.org/mrinal013/">Mrinal Haque</a> · <a href="https://profiles.wordpress.org/mrwweb/">mrwweb</a> · <a href="https://profiles.wordpress.org/wparslan/">Muhammad Arslan</a> · <a href="https://profiles.wordpress.org/devmuhib/">Muhibul Haque</a> · <a href="https://profiles.wordpress.org/mujuonly/">mujuonly</a> · <a href="https://profiles.wordpress.org/mukesh27/">Mukesh Panchal</a> · <a href="https://profiles.wordpress.org/faguni22/">Mumtahina Faguni</a> · <a href="https://profiles.wordpress.org/611shabnam/">Mushrit Shabnam</a> · <a href="https://profiles.wordpress.org/webdev8800/">Myles Taylor</a> · <a href="https://profiles.wordpress.org/nalininonstopnewsuk/">Nalini Thakor</a> · <a href="https://profiles.wordpress.org/nandhuraj/">nandhuraj</a> · <a href="https://profiles.wordpress.org/nazgul/">Nazgul</a> · <a href="https://profiles.wordpress.org/nazsabuz/">Nazmul Sabuz</a> · <a href="https://profiles.wordpress.org/neilorangepeel/">Neil Hainsworth</a> · <a href="https://profiles.wordpress.org/nendeb55/">nendeb</a> · <a href="https://profiles.wordpress.org/ndiego/">Nick Diego</a> · <a href="https://profiles.wordpress.org/rahe/">Nicolas Juen</a> · <a href="https://profiles.wordpress.org/nicolefurlan/">Nicole Furlan</a> · <a href="https://profiles.wordpress.org/nicomollet/">nicomollet</a> · <a href="https://profiles.wordpress.org/nidhidhandhukiya/">nidhidhandhukiya</a> · <a href="https://profiles.wordpress.org/nielslange/">Niels Lange</a> · <a href="https://profiles.wordpress.org/nihar007/">Nihar Ranjan Das</a> · <a href="https://profiles.wordpress.org/ntsekouras/">Nik Tsekouras</a> · <a href="https://profiles.wordpress.org/rabmalin/">Nilambar Sharma</a> · <a href="https://profiles.wordpress.org/nilovelez/">Nilo Velez</a> · <a href="https://profiles.wordpress.org/niravsherasiya7707/">niravsherasiya7707</a> · <a href="https://profiles.wordpress.org/dasnitesh780/">Nitesh Das</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/noahtallen/">Noah Allen</a> · <a href="https://profiles.wordpress.org/ngreennc/">Nyasha</a> · <a href="https://profiles.wordpress.org/ockham/">ockham</a> · <a href="https://profiles.wordpress.org/ohia/">Ohia</a> · <a href="https://profiles.wordpress.org/okat/">okat</a> · <a href="https://profiles.wordpress.org/oglekler/">Olga Gleckler</a> · <a href="https://profiles.wordpress.org/domainsupport/">Oliver Campion</a> · <a href="https://profiles.wordpress.org/olliejones/">OllieJones</a> · <a href="https://profiles.wordpress.org/paaljoachim/">Paal Joachim Romdahl</a> · <a href="https://profiles.wordpress.org/pannelars/">pannelars</a> · <a href="https://profiles.wordpress.org/swissspidy/">Pascal Birchler</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/pavelevap/">pavelevap</a> · <a href="https://profiles.wordpress.org/pedromendonca/">Pedro Mendon&#231;a</a> · <a href="https://profiles.wordpress.org/pentatonicfunk/">pentatonicfunk</a> · <a href="https://profiles.wordpress.org/gungeekatx/">Pete Nelson</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/petrosparaskevopoulos/">petrosparaskevopoulos</a> · <a href="https://profiles.wordpress.org/walbo/">Petter Walb&#248; Johnsg&#229;rd</a> · <a href="https://profiles.wordpress.org/phillsav/">Phill</a> · <a href="https://profiles.wordpress.org/nekojonez/">Pieterjan Deneys</a> · <a href="https://profiles.wordpress.org/piyushdeshmukh/">piyushdeshmukh</a> · <a href="https://profiles.wordpress.org/plugindevs/">Plugin Devs</a> · <a href="https://profiles.wordpress.org/poojabhimani/">Pooja Bhimani</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/pranavjoshi/">pranavjoshi</a> · <a href="https://profiles.wordpress.org/prashantbhivsane/">Prashant</a> · <a href="https://profiles.wordpress.org/presskopp/">Presskopp</a> · <a href="https://profiles.wordpress.org/rlmc/">r-c</a> · <a href="https://profiles.wordpress.org/rajinsharwar/">Rajin Sharwar</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/ramonopoly/">Ramon James</a> · <a href="https://profiles.wordpress.org/rebekowitz/">Rebekah Markowitz</a> · <a href="https://profiles.wordpress.org/tabrisrp/">Remy Perona</a> · <a href="https://profiles.wordpress.org/renyot/">ren</a> · <a href="https://profiles.wordpress.org/renathoc/">Renatho (a11n)</a> · <a href="https://profiles.wordpress.org/rmartinezduque/">Reyes Martínez</a> · <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a> · <a href="https://profiles.wordpress.org/rianrietveld/">Rian Rietveld</a> · <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a> · <a href="https://profiles.wordpress.org/noisysocks/">Robert Anderson</a> · <a href="https://profiles.wordpress.org/sanchothefat/">Robert O'Rourke</a> · <a href="https://profiles.wordpress.org/robinwpdeveloper/">Robin</a> · <a href="https://profiles.wordpress.org/robpetrin/">robpetrin</a> · <a href="https://profiles.wordpress.org/ravanh/">Rolf Allard van Hagen</a> · <a href="https://profiles.wordpress.org/ryanduff/">Ryan Duff</a> · <a href="https://profiles.wordpress.org/rmccue/">Ryan McCue</a> · <a href="https://profiles.wordpress.org/ohryan/">Ryan Neudorf</a> · <a href="https://profiles.wordpress.org/welcher/">Ryan Welcher</a> · <a href="https://profiles.wordpress.org/sergiomdgomes/">S&#233;rgio Gomes</a> · <a href="https://profiles.wordpress.org/mi5t4n/">Sagar Tamang</a> · <a href="https://profiles.wordpress.org/sajjad67/">Sajjad Hossain Sagor</a> · <a href="https://profiles.wordpress.org/sakibmd/">Sakib Mohammed</a> · <a href="https://profiles.wordpress.org/salcode/">Sal Ferrarello</a> · <a href="https://profiles.wordpress.org/samba45/">samba45</a> · <a href="https://profiles.wordpress.org/viralsampat/">Sampat Viral</a> · <a href="https://profiles.wordpress.org/mikachan/">Sarah Norris</a> · <a href="https://profiles.wordpress.org/sarahwilliams889/">sarahwilliams889</a> · <a href="https://profiles.wordpress.org/sarathar/">Sarath AR</a> · <a href="https://profiles.wordpress.org/satishprajapati/">Satish Prajapati</a> · <a href="https://profiles.wordpress.org/saulirajala/">saulirajala</a> · <a href="https://profiles.wordpress.org/saxonfletcher/">saxonfletcher</a> · <a href="https://profiles.wordpress.org/sc0ttkclark/">Scott Kingsley Clark</a> · <a href="https://profiles.wordpress.org/wonderboymusic/">Scott Taylor</a> · <a href="https://profiles.wordpress.org/hiyascout/">Scout James</a> · <a href="https://profiles.wordpress.org/scribu/">scribu</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/smrubenstein/">Seth Rubenstein</a> · <a href="https://profiles.wordpress.org/shailu25/">Shail Mehta</a> · <a href="https://profiles.wordpress.org/shawfactor/">shawfactor</a> · <a href="https://profiles.wordpress.org/shooper/">Shawn Hooper</a> · <a href="https://profiles.wordpress.org/shiloey/">shilo-ey</a> · <a href="https://profiles.wordpress.org/shivashankerbhatta/">Shiva Shanker Bhatta</a> · <a href="https://profiles.wordpress.org/shresthaaman/">shresthaaman</a> · <a href="https://profiles.wordpress.org/shubhamsedani/">Shubham Sedani</a> · <a href="https://profiles.wordpress.org/10upsimon/">Simon Dowdles</a> · <a href="https://profiles.wordpress.org/siobhan/">Siobhan</a> · <a href="https://profiles.wordpress.org/siobhyb/">Siobhan Bamber</a> · <a href="https://profiles.wordpress.org/smit08/">Smit Rathod</a> · <a href="https://profiles.wordpress.org/sofiashendi/">sofiashendi</a> · <a href="https://profiles.wordpress.org/nudge/">Sonia Gaballa</a> · <a href="https://profiles.wordpress.org/soean/">Soren Wrede</a> · <a href="https://profiles.wordpress.org/virtality-marketing-solutions/">SourceView</a> · <a href="https://profiles.wordpress.org/spenserhale/">Spenser Hale</a> · <a href="https://profiles.wordpress.org/pypwalters/">Stephanie Walters</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/stephenerdelyi/">Steve Erdelyi</a> · <a href="https://profiles.wordpress.org/stevejonesdev/">Steve Jones</a> · <a href="https://profiles.wordpress.org/subodhsun/">Subodh Sunuwar</a> · <a href="https://profiles.wordpress.org/subrataemfluence/">Subrata Sarkar</a> · <a href="https://profiles.wordpress.org/sujichandran14/">Suji K Chandran</a> · <a href="https://profiles.wordpress.org/sumisubedi/">Sumi Subedi</a> · <a href="https://profiles.wordpress.org/sumitsingh/">Sumit Singh</a> · <a href="https://profiles.wordpress.org/sunitarai/">Sunita Rai</a> · <a href="https://profiles.wordpress.org/suprsam/">suprsam</a> · <a href="https://profiles.wordpress.org/syamraj24/">syamraj24</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/sereedmedia/">Sé Reed</a> · <a href="https://profiles.wordpress.org/tahmidulkarim/">Tahmid ul Karim</a> · <a href="https://profiles.wordpress.org/tahmina1du/">Tahmina Jahan</a> · <a href="https://profiles.wordpress.org/takayukister/">Takayuki Miyoshi</a> · <a href="https://profiles.wordpress.org/karmatosed/">Tammie Lister</a> · <a href="https://profiles.wordpress.org/tanvirul/">Tanvirul Haque</a> · <a href="https://profiles.wordpress.org/tykoted/">Teddy Patriarca</a> · <a href="https://profiles.wordpress.org/tejadev/">tejadev</a> · <a href="https://profiles.wordpress.org/thinkluke/">thinkluke</a> · <a href="https://profiles.wordpress.org/thomasplevy/">Thomas Patrick Levy</a> · <a href="https://profiles.wordpress.org/tibbsa/">tibbsa</a> · <a href="https://profiles.wordpress.org/baxbridge/">Tiffany Bridge</a> · <a href="https://profiles.wordpress.org/tnolte/">Tim Nolte</a> · <a href="https://profiles.wordpress.org/timdix/">timdix</a> · <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a> · <a href="https://profiles.wordpress.org/tmatsuur/">tmatsuur</a> · <a href="https://profiles.wordpress.org/tobiasbg/">TobiasBg</a> · <a href="https://profiles.wordpress.org/tobifjellner/">tobifjellner (Tor-Bjorn Fjellner)</a> · <a href="https://profiles.wordpress.org/tomybyte/">Tom</a> · <a href="https://profiles.wordpress.org/tomjcafferkey/">Tom Cafferkey</a> · <a href="https://profiles.wordpress.org/thomashorta/">Tom H</a> · <a href="https://profiles.wordpress.org/tjnowell/">Tom J Nowell</a> · <a href="https://profiles.wordpress.org/tomluckies/">tomluckies</a> · <a href="https://profiles.wordpress.org/shimotomoki/">Tomoki Shimomura</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/toscho/">toscho</a> · <a href="https://profiles.wordpress.org/rilwis/">Tran Ngoc Tuan Anh</a> · <a href="https://profiles.wordpress.org/trinisha/">Trinisha</a> · <a href="https://profiles.wordpress.org/trishasalas/">Trisha Salas</a> · <a href="https://profiles.wordpress.org/tristanleboss/">tristanleboss</a> · <a href="https://profiles.wordpress.org/tv-productions/">TV productions</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/upadalavipul/">Upadala Vipul</a> · <a href="https://profiles.wordpress.org/utsav72640/">Utsav tilava</a> · <a href="https://profiles.wordpress.org/valentindu62/">valentindu62</a> · <a href="https://profiles.wordpress.org/valmedia2023/">Valerie Blackburn</a> · <a href="https://profiles.wordpress.org/vcanales/">Vicente Canales</a> · <a href="https://profiles.wordpress.org/szepeviktor/">Viktor Sz&#233;pe</a> · <a href="https://profiles.wordpress.org/vipuljnext/">Vipul Ghori</a> · <a href="https://profiles.wordpress.org/vivekawsm/">vivekawsm</a> · <a href="https://profiles.wordpress.org/vortfu/">vortfu</a> · <a href="https://profiles.wordpress.org/vrajadas/">Vraja Das</a> · <a href="https://profiles.wordpress.org/webashrafians/">webashrafians</a> · <a href="https://profiles.wordpress.org/webmandesign/">WebMan Design &#124; Oliver Juhas</a> · <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a> · <a href="https://profiles.wordpress.org/whsajid/">WHSajid</a> · <a href="https://profiles.wordpress.org/skorasaurus/">Will Skora</a> · <a href="https://profiles.wordpress.org/wvega/">Willington Vega</a> · <a href="https://profiles.wordpress.org/planningwrite/">Winstina</a> · <a href="https://profiles.wordpress.org/winterstreet/">winterstreet</a> · <a href="https://profiles.wordpress.org/wraithkenny/">WraithKenny</a> · <a href="https://profiles.wordpress.org/wyrfel/">wyrfel</a> · <a href="https://profiles.wordpress.org/yosephtamang/">Yoseph Tamang</a> · <a href="https://profiles.wordpress.org/fierevere/">Yui</a> · <a href="https://profiles.wordpress.org/zieladam/">zieladam</a> · <a href="https://profiles.wordpress.org/zunaid321/">Zunaid Amin</a> · <a href="https://profiles.wordpress.org/letraceursnork/">Илья</a></p>



<p>Over <a href="https://translate.wordpress.org/stats/">60 locales have translated 90 percent</a> or more of WordPress 6.4 into their language. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200 languages.</p>



<p>Last but not least, thanks to the volunteers who contribute to the <a href="https://wordpress.org/support/">support forums</a> by answering questions from WordPress users worldwide.</p>



<h3 class="wp-block-heading">Get involved</h3>



<p>Participation in WordPress is not limited to coding. If contributing appeals to you, learning more and getting involved is easy. Discover the teams that come together to <a href="https://make.wordpress.org/">Make WordPress</a>, and use <a href="https://make.wordpress.org/contribute/">this interactive tool</a> to help you decide which is right for you.</p>



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



<h2 class="wp-block-heading">Looking ahead</h2>



<p>Over the past <a href="https://wp20.wordpress.net/">two decades</a>, WordPress has transformed the digital publishing landscape and empowered anyone to create and share, from <a href="https://wordpress.org/showcase/">handcrafted personal stories to world-changing movements</a>.</p>



<p>The present and future of WordPress hold exciting opportunities for everyone, builders and enterprises alike. The foundational work for <a href="https://make.wordpress.org/core/tag/phase-3/">Phase 3</a> of the <a href="https://wordpress.org/about/roadmap/">roadmap</a> continues, with efforts focused on fostering real-time collaboration and streamlining publishing flows to improve how creators and teams work together in WordPress.</p>



<p>Stay on top of the latest news and contributing opportunities by subscribing to <a href="https://wordpress.org/news/">WordPress News</a> and the <a href="https://wordpress.org/news/podcast/">WP Briefing podcast</a>.</p>



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



<h2 class="wp-block-heading">A release haiku</h2>



<p>The smooth feel of jazz<br />The cutting-edge of the web<br />Install 6.4</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, 07 Nov 2023 19:59:02 +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:"Josepha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:97:"Do The Woo Community: How to Tell Friends and Family What You Do in WordPress with Topher DeRosia";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"https://dothewoo.io/?p=77925";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://dothewoo.io/how-to-tell-friends-and-family-what-you-do-in-wordpress/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:451:"<p>In this show we talk with Topher about explaining what WordPress pros do for a living, the demographics of WordPress and teaching with video.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/how-to-tell-friends-and-family-what-you-do-in-wordpress/">How to Tell Friends and Family What You Do in WordPress with Topher DeRosia</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</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, 07 Nov 2023 10:48:01 +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:2;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: Newspack Plugin Update Checker Lets Users Update from GitHub";s: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=150972";s: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:81:"https://wptavern.com/newspack-plugin-update-checker-lets-users-update-from-github";s: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:4125:"<p>Adam Schweigert, an independent media and technology consultant, has released a plugin called <a href="https://github.com/aschweigert/newspack-plugin-update-checker?fbclid=IwAR1Z6GWoPLEQvBBuioWJP7wOxO6lRWgam2f1_2JXyTGeB248b6r1Qv6VOl0#newspack-plugin-update-checker">Newspack Plugin Update Checker</a> that enables self-hosted Newspack users to keep their plugins up-to-date. The Newspack project was launched in 2019 by WordPress.com, with support from the Google News Initiative, the Knight Foundation, and The Lenfest Institute. It provides local news organizations a powerful, yet cost effective publishing platform that promotes financial sustainability.</p>



<p>More than 200 news sites are on the hosted version of Newspack, which uses WordPress.com&#8217;s cloud platform. Organizations can also host their own Newspack installations independently, which includes a theme, collection of plugins, and blocks. KinshiPress, which publishes news and updates for WordPress publishers, has <a href="https://kinshipress.com/newspack-self-hosted/">a guide to self-hosting Newspack</a> that walks through the process of getting set up. It also mentions the drawback of the plugins being hosted on GitHub.</p>



<p> Schweigert&#8217;s <a href="https://github.com/aschweigert/newspack-plugin-update-checker?fbclid=IwAR1Z6GWoPLEQvBBuioWJP7wOxO6lRWgam2f1_2JXyTGeB248b6r1Qv6VOl0#newspack-plugin-update-checker">Newspack Plugin Update Checker</a> solves this problem by using a <a href="https://github.com/YahnisElsts/plugin-update-checker">plugin updater library</a> that checks for updates and lets users know when a new version is available. The notice appears in the dashboard in a similar way to how WordPress.org displays updates.</p>



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



<img width="1203" height="107" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/11/image-1.png" alt="" class="wp-image-150980" />



<p>The plugin checks for updates for nine of the most commonly-used Newspack plugins, including the following:</p>



<ul>
<li><a href="https://github.com/automattic/newspack-plugin">Newspack Plugin</a></li>



<li><a href="https://github.com/automattic/newspack-ads">Newspack Ads</a></li>



<li><a href="https://github.com/automattic/newspack-blocks">Newspack Blocks</a></li>



<li><a href="https://github.com/automattic/newspack-popups">Newspack Popups (aka Campaigns)</a></li>



<li><a href="https://github.com/automattic/newspack-listings">Newspack Listings</a></li>



<li><a href="https://github.com/automattic/newspack-sponsors">Newspack Sponsors</a></li>



<li><a href="https://github.com/automattic/newspack-media-partners">Newspack Media Partners</a></li>



<li><a href="https://github.com/automattic/newspack-rss-enhancements">Newspack RSS Enhancements</a></li>



<li><a href="https://github.com/automattic/newspack-supporters">Newspack Supporters</a></li>
</ul>



<p> Schweigert noted that the plugin requires the Newspack plugins be in folders named using their respective slugs. Although the plugin allows users to enable auto-updates, he recommends keeping an eye on the <a href="https://newspack.com/release-notes/">Newspack release notes</a> to be prepared for any potentially breaking changes.</p>



<p>KinshiPress author Steve Burge recently published an article on the <a href="https://kinshipress.com/newspack-ecosystem/">Newspack ecosystem</a>, contending that Newspack has the potential to do for publishers what WooCommerce has done for e-commerce.</p>



<p>&#8220;There’s a big audience out for a publishing platform that is open source, highly extendable, and has the backing of a successful company and a strong community,&#8221; Burge said.&#8221; Where else can newspapers, magazines and radio stations go? They mostly go to WordPress already, but the platform we provide them could be much more targeted and helpful.&#8221;</p>



<p>Although Schweigert&#8217;s plugin is a good stop gap measure, Burge said he thinks putting the Newspack plugins on WordPress.org and improving the documentation would go a long way towards expanding its impact.</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, 04 Nov 2023 03:30:07 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: WordPress Theme Handbook Updates Chapter on Block Templating";s: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=150958";s: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:81:"https://wptavern.com/wordpress-theme-handbook-updates-chapter-on-block-templating";s: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:2584:"<p>WordPress contributors have updated the <a href="https://developer.wordpress.org/themes/">Theme Handbook</a> to include <a href="https://developer.wordpress.org/themes/templates/">a new chapter on block templating</a>. The chapter covers how the WordPress block template system works, how to build custom templates and parts and include them in a theme. This is critical documentation designed to provide a learning path for those who are building their first block themes.</p>



<p>Automattic-sponsored developer advocate Justin Tadlock announced the update on Twitter, noting that it also includes a couple of new docs in the Global Settings and Styles chapter for <a href="https://developer.wordpress.org/themes/global-settings-and-styles/custom-templates/">registering template-related features in theme.json</a>, and the same for <a href="https://developer.wordpress.org/themes/global-settings-and-styles/template-parts/">template parts</a>.</p>



<p>The new chapter on block templating is just one part of a larger effort to overhaul the Theme Handbook for modern day WordPress.  Contributors are transitioning the focus from classic theming to block theming, with just one chapter in the handbook devoted to classic themes.</p>



<p>&#8220;It was created during a time when classic themes were the only method of front-end design for WordPress,&#8221; Tadlock said in the <a href="https://make.wordpress.org/themes/2023/04/04/theme-handbook-overhaul-proposal/">proposal to overhaul the handbook</a>. &#8220;Much of its content now exists in a transitory state between classic and modern block theming. This has created a scenario where the handbook sometimes reads more like patchwork than if it were built with a single vision. That is often a natural result of adding new documentation over years.&#8221;</p>



<p>The proposal does not recommend scrapping all of the existing content but rather carrying some of it forward to be updated and reorganized. A good portion of the existing content is still relevant to be migrated to the Classic Themes chapter.</p>



<p>Overhauling the Theme Handbook is a colossal effort that&#8217;s still ongoing. It&#8217;s being managed under a <a href="https://github.com/WordPress/Documentation-Issue-Tracker/issues/816">tracking ticket</a> on GitHub. The new chapter better supports developers who are just figuring out how the WordPress block template system works, but there are many more chapters that need attention. Anyone who would like to get involved in the project can select any issue on the ticket to get started.</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, 03 Nov 2023 19:36:10 +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:53:"WPTavern: Add Icons to WordPress’ Core Button Block";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=150927";s: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://wptavern.com/add-icons-to-wordpress-core-button-block";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5605:"<p>Nick Diego, a developer advocate at Automattic and core contributor, is the author of the popular <a href="https://wordpress.org/plugins/icon-block/">Icon Block</a> plugin that enables users to add custom SVG icons and graphics to the WordPress block editor. He is often asked if the plugin can add icons to the core Button block, but that is outside the scope of what it does. Last week he wrote a plugin that fulfills this feature request in a separate plugin without building a custom block.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Everyone asks me if <a href="https://twitter.com/theiconblock?ref_src=twsrc%5Etfw">@theiconblock</a> can add icons to the core Button block in <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a>. <br /><br />Unfortunately, the answer is no. <br /><br />But while traveling last week, I built a little demo plugin that does just that.<br /><br />It works quite well, and no need for a custom block <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f609.png" alt="😉" class="wp-smiley" />… <a href="https://t.co/jF3T3T8lOA">pic.twitter.com/jF3T3T8lOA</a></p>&mdash; Nick Diego (@nickmdiego) <a href="https://twitter.com/nickmdiego/status/1719871746818314361?ref_src=twsrc%5Etfw">November 2, 2023</a></blockquote>
</div>



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



<p>The Enable Button Icons plugin is <a href="https://github.com/ndiego/enable-button-icons">available on GitHub</a> as an example that demonstrates how developers can lightly extend core blocks for features like this. Diego said he was inspired by WordPress developer Aki Hamano&#8217;s <a href="https://github.com/t-hamano/enable-responsive-image#enable-responsive-image">Enable Responsive Image</a> plugin that adds settings to the Image block to elegantly display different images depending on the width of the screen.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="ja" dir="ltr">WordPressの画像ブロックで、モバイル時に画像を切り替えたいけど、カスタムブロックを作るまでもなくシンプルにコアブロックを拡張するものが欲しいなと思い、試しに作ってみました。<br />とりあえず追加出来る画像は1枚で、ブレークポイントと解像度だけ切り替えられるように。<a href="https://t.co/3OeUEQcGqQ">https://t.co/3OeUEQcGqQ</a> <a href="https://t.co/NxafBGRDfh">pic.twitter.com/NxafBGRDfh</a></p>&mdash; Aki Hamano / 浜野 哲明 (@tetsuaki_hamano) <a href="https://twitter.com/tetsuaki_hamano/status/1712763117174956324?ref_src=twsrc%5Etfw">October 13, 2023</a></blockquote>
</div>



<p>&#8220;I wanted to use the WordPress image block to switch images on mobile, but I wanted something that would simply extend the core block without having to create a custom block, so I tried making one,&#8221; Hamano said. &#8220;For now, you can only add one image, and only the breakpoint and resolution can be switched.&#8221;</p>



<p> Diego said he doesn&#8217;t plan to add his Enable Button Icons plugin to the official WordPress directory.</p>



<p>&#8220;It works great, but it is not designed to support an entire library of icons, and I know that will be the first thing people ask for,&#8221; he said. &#8220;So, I&#8217;m thinking of keeping it as an example and encouraging people to take it and modify it as they want.&#8221; </p>



<p>I tested the plugin and it works perfectly but is certainly ripe for being extended to support a larger selection of icons. Alternatively, it may be useful for a brand that has a set number of custom designed icons they want to be easily accessible for use in Button blocks.</p>



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



<img width="858" height="610" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/11/image.png" alt="" class="wp-image-150933" />



<p>Diego will be running an event at the end of the month about how to extend core WordPress blocks, and the Enable Button Icons plugin will be part of that. It will be another segment in the &#8220;Developer Hours&#8221; series run through the Learn WordPress Online Workshops group on Meetup. Diego and a team of contributors just wrapped up a Developer Hours <a href="https://www.meetup.com/learn-wordpress-online-workshops/events/296946089">event</a> today featuring a demo/walkthrough of the upcoming Twenty Twenty-Four default theme. Watch for the next event to be added to <a href="https://www.meetup.com/learn-wordpress-online-workshops/events/">the schedule</a> sometime this week.</p>



<p>Developers have been asking for more extensibility, hooks, and filters for the block editor, and an upcoming Hallway Hangout event will focus on <a href="https://make.wordpress.org/core/2023/11/02/hallway-hangout-issues-triage-extending-gutenberg/">triaging issues related to extending Gutenberg</a>. Contributors will discuss the 110 outstanding issues labeled &#8220;<a href="https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22%5BFeature%5D+Extensibility%22+sort%3Areactions-%2B1-desc">Extensibility,</a>&#8221; and 20 issues labeled &#8220;<a href="https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+sort%3Areactions-%2B1-desc+label%3A%22%5BFocus%5D+Blocks+Adoption%22">Blocks Adoption</a>,&#8221; used for issues that directly impact the ability to adopt features of Gutenberg. Anyone who wants to share their opinions about block editor extensibility issues is invited to join.</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, 03 Nov 2023 02: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: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:58:"Do The Woo Community: Do the Woo Day 3 Recap, WooSesh 2023";s: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=77702";s: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://dothewoo.io/do-the-woo-day-3-recap-woosesh-2023/";s: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:367:"<p>Day 3 recap included a deep look at producing WooSesh, the Seshies awards and conversation around the days sessions.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/do-the-woo-day-3-recap-woosesh-2023/">Do the Woo Day 3 Recap, WooSesh 2023</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</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, 02 Nov 2023 11:05: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: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:69:"WPTavern: Wordfence CLI 2.0.1 Update Adds Free Vulnerability Scanning";s: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=150866";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:80:"https://wptavern.com/wordfence-cli-2-0-1-update-adds-free-vulnerability-scanning";s: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:3294:"<p><a href="https://www.wordfence.com/blog/2023/10/wordpress-vulnerability-scanning/">Wordfence CLI 2.0.1</a> introduced free vulnerability scanning this week. The new <a href="https://www.wordfence.com/products/wordfence-cli/">CLI product</a> was <a href="https://www.wordfence.com/blog/2023/08/wordfence-cli/">launched at WordCamp US</a> two months ago with malware detection capabilities, but the latest update brings in the most highly requested feature &#8211; vulnerability scanning at scale. </p>



<p>Wordfence is most well-known for its Web Application Firewall, malware scanner, and login security product, which is packaged as <a href="https://wordpress.org/plugins/wordfence/">a free plugin</a> and installed on more than 4 million websites. The CLI is the first-ever command line malware and vulnerability scanner for WordPress servers. It is targeted at developers, site cleaners who scan large numbers of files for remediation, agencies, and hosting companies that want to scan across entire networks of millions of customers.</p>



<p>&#8220;Vulnerability scanning in Wordfence CLI 2.0.1 uses our own open vulnerability database,&#8221; Wordfence CEO Mark Maunder said. &#8220;The database itself is completely free for anyone to use, and includes APIs that are open, along with web hooks so that developers can build real-time alerting into their applications. Our mission is to secure the Web, and we think that having an open vulnerability database, with an open source, robust and high performance vulnerability scanner for servers furthers that mission.&#8221;</p>



<p>The vulnerability database includes responsible disclosures published by researchers for the benefit of the wider community.<br /><br />&#8220;Because most vulnerabilities come from the research community, we believe they are public property,&#8221; Maunder said. &#8220;While some companies do charge for their collection of vulnerabilities, we don’t think it is appropriate to resell public property, which is why we created an open and completely free vulnerability database.&#8221;</p>



<p>The CLI vulnerability scans use the Wordfence Intelligence Vulnerability API feed, which is free for both personal and commercial use. It contains more than 12,250 unique vulnerability records affecting 7,600 plugins and themes. The Wordfence team adds an average of 82 new vulnerabilities per week. </p>



<p>Version 2.0.1, code named &#8220;Voodoo Child&#8221; simplifies installation so users no longer have to go to the Wordfence site to get an API key. The tool fetches the API key in the background to make it easier to get started.</p>



<p>Wordfence CLI is licensed under the GPLv3 and <a href="https://github.com/wordfence/wordfence-cli/">available on GitHub</a>, along with <a href="https://www.wordfence.com/help/wordfence-cli/">documentation</a> for installing, configuring, and running the application.</p>



<p>&#8220;Wordfence CLI is one of those projects where the product roadmap writes itself because there is such an obvious need for a powerful tool like this in the WordPress server administration space,&#8221; Wordfence lead developer Matt Barry said. &#8220;We’re in this for the long haul and will continue to invest heavily in Wordfence CLI, with your guidance.&#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, 01 Nov 2023 20:48:54 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:"WordPress.org blog: WordPress 6.4 Release Candidate 3";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=16247";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wordpress.org/news/2023/11/wordpress-6-4-release-candidate-3/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8050:"<p>The third release candidate (RC3) for WordPress 6.4 is ready to download!</p>



<p><strong>This version of the WordPress software is under development</strong>. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site.</p>



<p>WordPress 6.4 is <a href="https://make.wordpress.org/core/6-4/">slated for release</a> on <strong>November 7, 2023</strong>—less than a week away. If you haven’t tried it, now is the time.</p>



<p>You can test WordPress 6.4 RC3 in three ways:</p>



<ol>
<li><strong>Plugin</strong>: Install and activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin on a WordPress install (select the “Bleeding edge” channel and “Beta/RC Only” stream).</li>



<li><strong>Direct download</strong>: Download the <a href="https://wordpress.org/wordpress-6.4-RC3.zip">RC3 version (zip)</a> and install it on a WordPress site.</li>



<li><strong>Command line</strong>: Use the following <a href="https://make.wordpress.org/cli/">WP-CLI</a> command:<br /><code>wp core update --version=6.4-RC3</code></li>
</ol>



<p><a href="https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-1/">Read the RC1 announcement</a> for featured highlights, and check the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/6-4/">6.4-related posts</a>. If you are looking for detailed technical notes on new features and improvements, the <a href="https://make.wordpress.org/core/2023/10/23/wordpress-6-4-field-guide/"><strong>WordPress 6.4 Field Guide</strong></a> is for you.</p>



<p>The WordPress 6.4 release is brought to you by an <a href="https://make.wordpress.org/core/2023/06/05/wordpress-6-4-development-cycle/">underrepresented gender release squad</a> to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.</p>



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



<h2 class="wp-block-heading">What’s in WordPress 6.4 RC3?</h2>



<p>Thanks to everyone who has tested the beta and RC releases. Since RC2 was released on October 24, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:</p>



<ul>
<li><a href="https://github.com/WordPress/gutenberg/commits/wp/6.4">GitHub commits for 6.4</a></li>



<li><a href="https://core.trac.wordpress.org/query?status=closed&changetime=10%2F25%2F2023..11%2F01%2F2023&milestone=6.4&col=id&col=milestone&col=owner&col=type&col=priority&order=id">Closed Trac tickets since RC2</a></li>



<li><a href="https://github.com/WordPress/twentytwentyfour/commits/">GitHub commits for Twenty Twenty-Four</a></li>
</ul>



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



<h2 class="wp-block-heading">PHP compatibility update</h2>



<p>It’s recommended to use PHP 8.1 or 8.2 with the upcoming 6.4 release. Refer to <a href="https://wordpress.org/news/2023/10/wordpress-6-4s-php-compatibility/">WordPress 6.4&#8217;s PHP compatibility post</a> for more details.</p>



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



<h2 class="wp-block-heading">Contributing to 6.4</h2>



<p>WordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.</p>



<h3 class="wp-block-heading">Get involved in testing</h3>



<p>Your feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. <a href="https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/">Check out this guide</a> for instructions on testing WordPress 6.4 features.</p>



<p>The core Query block requires more <a href="https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/#query-loop-block-pagination-enhancements">testing and feedback</a> to ensure the latest changes to prevent full page reloads work smoothly. Please note that this setting was called &#8220;Enhanced pagination&#8221; but has recently been renamed, and it&#8217;s now referred to as &#8220;Force page reload&#8221; instead.</p>



<p>If you encounter an issue, please report it to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta area</a> of the support forums or directly to <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a> if you are comfortable writing a reproducible bug report. You can also check your issue against a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>



<p>Curious about testing releases in general? Follow along with the <a href="https://make.wordpress.org/test/">testing initiatives in Make Core</a> and join the <a href="https://wordpress.slack.com/messages/core-test/">#core-test channel</a> on <a href="https://wordpress.slack.com/">Making WordPress Slack</a>.</p>



<h3 class="wp-block-heading">Search for vulnerabilities</h3>



<p>During the release candidate phase of WordPress 6.4, the <a href="https://make.wordpress.org/security/2023/09/26/bug-bounty-for-wordpress-6-4-beta/">monetary reward for reporting new, unreleased security vulnerabilities</a> is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the <a href="https://hackerone.com/wordpress">HackerOne page</a> and in the <a href="https://wordpress.org/about/security/">security white paper</a>.</p>



<h3 class="wp-block-heading">Update your theme or plugin</h3>



<p>Do you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.</p>



<p>Hopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC3, you will want to continue your testing and update the <em>&#8220;Tested up to&#8221;</em> version in your <a href="https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/">plugin&#8217;s readme file</a> to 6.4.</p>



<p>Please post detailed information to the <a href="https://wordpress.org/support/forum/alphabeta/">support forums</a> if you find compatibility issues.</p>



<h3 class="wp-block-heading">Documentation</h3>



<p>Help the Docs team put the finishing touches on end-user documentation in time for the 6.4 release. Find out what’s needed and how you can help <a href="https://make.wordpress.org/docs/2023/10/25/call-for-volunteers-to-help-with-6-4-end-user-documentation/">in this post</a>.</p>



<h3 class="wp-block-heading">Help translate WordPress</h3>



<p>Do you speak a language other than English? ¿Español? Français? Português? Русский? 日本? <a href="https://translate.wordpress.org/projects/wp/dev">Help translate WordPress into more than 100 languages</a>.</p>



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



<h2 class="wp-block-heading">A RC3 haiku</h2>



<p>One more week of prep<br />One more week to test the code<br />One more week til launch</p>



<p><em>Thank you to the following contributors for collaborating on this post: <a href="https://profiles.wordpress.org/meher/" class="mention"><span class="mentions-prefix">@</span>meher</a>, <a href="https://profiles.wordpress.org/rmartinezduque/" class="mention"><span class="mentions-prefix">@</span>rmartinezduque</a>, <a href="https://profiles.wordpress.org/sereedmedia/" class="mention"><span class="mentions-prefix">@</span>sereedmedia</a>, <a href="https://profiles.wordpress.org/jorbin/" class="mention"><span class="mentions-prefix">@</span>jorbin</a>, <a href="https://profiles.wordpress.org/luisherranz/" class="mention"><span class="mentions-prefix">@</span>luisherranz</a>, <a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a></em>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 01 Nov 2023 19:21:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Reyes Martínez";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:108:"WPTavern: #97 – Estela Rueda, Courtney Robertson and Javier Casares on the Future of Translating WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=150878";s: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:121:"https://wptavern.com/podcast/97-estela-rueda-courtney-robertson-and-javier-casares-on-the-future-of-translating-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:56373:"Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast, which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case how translations of the WordPress project are created now and in the future.</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 all your idea featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.</p>



<p>So on the podcast today, we have Estela Rueda, Courtney Robertson and Javier Casares.</p>



<p>Courtney is a former teacher who now focuses on contributing to WordPress. With a background in education, she understands the challenges faced by English second language learners in the American education system. She&#8217;s passionate about providing access to WordPress in multiple languages, as she believes it&#8217;s unfair to expect non-English speakers to simultaneously translate content and understand it.</p>



<p>Estela is a language enthusiast who has spent years navigating the challenges of website localization. As a member of the WordPress community, Estela has come across the intricacies of language differences, and the need for accurate translation in various Spanish locales. With 14 Spanish locales to handle Estela&#8217;s expertise in understanding the subtle nuances, and localizations of each language variation has been indispensable.</p>



<p>Javier is a dedicated member of the WordPress community, with expertise in creating documentation. Javier has been instrumental in developing handbooks for various sites. However, there have been some technical challenges. Despite these obstacles Javier, as you will hear, remains committed to addressing and solving the documentation issues at hand.</p>



<p>This episode covers the important topic of translations, and making WordPress documentation more accessible to people worldwide. Our guests bring a wealth of knowledge and experience to the table, as they discuss the complexities and challenges of language translation in the WordPress ecosystem.</p>



<p>We start by highlighting challenges posed in translating WordPress, such as the tangled processes currently in place, as well as more language focused topics. We talk about the extensive collaborative effort involved in translating WordPress, and the plans to expand translation efforts to documentation with the help of dedicated teams.</p>



<p>We get into how contributors might need to rethink how many of the current translation processes are structured. We discuss the different approaches needed for translating plugins and themes versus documentation. We touch upon how technical aspects of these processes such as content creation and updates also pose significant challenges.</p>



<p>All three guests stress the importance of global involvement in translation efforts, including translators, reviewers, and project managers. They advocate for the development of standardized style guides for each language to maintain consistency. And they explore the possibility of creating software, or tools, to manage translation tasks.</p>



<p>Courtney, Estela and Javier all acknowledge the challenges ahead, but express optimism that their ideas will help make WordPress accessible for all. Communicating how WordPress is built and how it works is an endeavor tightly aligned with the projects overall mission of democratizing publishing.</p>



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



<p>And so without further delay, I bring you Estela Rueda, Courtney Robertson and Javier Casares.</p>



<p>I am joined on the podcast today by three fine people. I&#8217;m joined by Courtney Robertson, Estela Rueda and Javier Casares. Hello all three of you.</p>



<p>[00:04:48] <strong>Javier Casares:</strong> Hello.</p>



<p>[00:04:49] <strong>Estela Rueda:</strong> Hi Nathan.</p>



<p>[00:04:50] <strong>Courtney Robertson:</strong> Hello.</p>



<p>[00:04:51] <strong>Nathan Wrigley:</strong> Very nice to have you on the podcast today. We&#8217;re going to be talking about WordPress translations, and the way that we can make it easier for people from around the globe to get access to WordPress documentation. It&#8217;s a very important subject and there&#8217;s been a lot of work, albeit that you may not know about it. There&#8217;s been an awful lot of work going on over, well more or less a decade, and we&#8217;ll find out more about that in a moment.</p>



<p>But first of all I think it&#8217;s important that everybody gets a little window to introduce themselves, do a quick bio. So if I take you one at a time and lets start with Courtney. Just tell us who you are. And I know that I&#8217;m going to say can we be brief but I know time is short, so let&#8217;s keep it fairly brief if that&#8217;s all right.</p>



<p>[00:05:33] <strong>Courtney Robertson:</strong> Sure thing. I&#8217;ve been contributing to WordPress since 2009. A big part of the training team for many years. These days you can also find me over in Meta, Sustainability, and generally around the project on behalf of GoDaddy these days, and I&#8217;ve been there for about two and a half years. Long time contributor. Big fan.</p>



<p>[00:05:50] <strong>Nathan Wrigley:</strong> Thank you so much. I&#8217;m sure that people have come across Courtney in the past, as would be the case for the next two people. Let&#8217;s go for Estela next. Hello Estela, would you mind giving us your intro?</p>



<p>[00:06:01] <strong>Estela Rueda:</strong> Hi Nathan. Yes. I&#8217;ve been contributing for about five years already and I am mostly in the design and the documentation teams. But you can find me everywhere. I do mess around everywhere, I ask questions. And my goal has been to rearrange, recategorise the end user documentation. And that&#8217;s been the big project that we finished, it took us three years. And now we want to bring it up to the whole world in every single language we can manage.</p>



<p>[00:06:33] <strong>Nathan Wrigley:</strong> Okay thank you. And finally Javier, if you want to just give us your short bio.</p>



<p>[00:06:37] <strong>Javier Casares:</strong> Yeah. Hello everybody. I&#8217;m Javier Casares, I&#8217;m from Spain. I&#8217;ve been involved with WordPress since 2006, so more or less 17 years. I mainly focus on hosting, on the hosting team, and I&#8217;m helping the documentation team mainly with the Advanced Administration Handbook. So that&#8217;s more or less what I do. I do a lot of things but those are the main things.</p>



<p>[00:07:04] <strong>Nathan Wrigley:</strong> Those are the things which are pertinent to today&#8217;s discussion. Yeah, thank you so much.</p>



<p>So if, like me, you are a native English speaker, English is your first language. It may very well be that some of the things that we&#8217;re going to talk about today have either never occurred to you, or you&#8217;ve never bumped up against this problem.</p>



<p>Because broadly speaking, if you are a native English speaker, you can find the documentation, you can find tutorials. You can find almost anything you wish to find out about WordPress, how to use it, how to implement things and so on, by going and doing a Google search. And you&#8217;re off to the races because essentially everything has historically been done in the English language.</p>



<p>So I guess that, in my case, makes me an incredibly fortunate person. But that&#8217;s not the case throughout the world. And as obviously WordPress has grown, we&#8217;re now 40 plus percent of the internet, it would be not really serving the user base of WordPress if everything was simply in English. It would be a laudable goal to get everything translated.</p>



<p>Now I guess we should probably outline where all of the things are at the moment. So it&#8217;s not the case that you can go to one website and there it all is, open a Pandora&#8217;s box, open it all and there it all is.</p>



<p>So let&#8217;s outline that problem first. I don&#8217;t really mind who wishes to tackle this one. Yeah if somebody wants to just outline the problem that we face, where are all the documents stored at the moment?</p>



<p>[00:08:23] <strong>Estela Rueda:</strong> I can&#8217;t give it a go. There are many, many limitations within WordPress. There are the sites that are called the Rosetta sites, or locales and those are the ones that are written in other languages for local teams.</p>



<p>But then we have issues, different issues. For instance, in Spanish, we have 14 locales in Spanish. So we have Spanish from Spain, we have Spanish from Mexico, Spanish from Colombia, Spanish from Costa Rica, et cetera. And everybody will think, well don&#8217;t you understand each other? Yeah we do, we understand each other, but there are so many differences in our languages. And there is the localisation of the words, and a lot of little things that we need to figure out. That&#8217;s one thing.</p>



<p>Then the other thing is that there are never enough contributors to do translations. And then there are all the technical issues that we have, and Javier can talk to you about those, because he&#8217;s more aware than all of the technical issues that we have.</p>



<p>[00:09:25] <strong>Nathan Wrigley:</strong> Okay, in that case, we&#8217;ll hopefully segue over to Javier. Are you able to take it from there?</p>



<p>[00:09:29] <strong>Javier Casares:</strong> Yeah. So the main thing is, we have the Rosetta sites. It&#8217;s local team can create their own documentation in a way, because some of the sites have their own handbooks. But there is some technical things there because, for example, the Spanish from Spain is one of the older sites in the WordPress network.</p>



<p>So it&#8217;s database is in LATIN1, it&#8217;s not in UTF, it&#8217;s a technical thing. But it doesn&#8217;t allow, for example, emojis in the database. That&#8217;s so simple but it&#8217;s something that happens. So we have some problems having documentation there. That&#8217;s one of the things.</p>



<p>But the other one is we have the documentation right now in wordpress.org/documentation. Also we have the developer.wordpress.org. We have the Learn corpus also in with a lot of documentation. In a lot of ways, WordPress TV should, maybe it&#8217;s another place with documentation, in video in this case. And everything usually is focused on English.</p>



<p>So the main idea on this project we started like a year ago is, how can we translate everything into, more or less, at least eight languages? Because eight languages cover more or less eighty percent of the WordPress users. And also, where are we going to put that documentation? Because, for example, we can do ses.wordpress.org/documentation, that&#8217;s the easy one. But, for example, the developer documentation is in a subdomain so, where are we going to put all this documentation?</p>



<p>So that&#8217;s one of the things we are trying to solve. That&#8217;s one technical problem we have to face. And the other one is, where are we going to put all the documentation to be translated? Because we know that WordPress will be multilingual in a way in some years. I hope soon, as soon as possible.</p>



<p>We have now the phase three, the collaboration part. But we have the problem that we cannot give access in this case. This is something concrete for WordPress, not for a translation or a documentation problem. But we cannot give access to thousands of people to the WordPress network, because it won&#8217;t be able to control the security and everything.</p>



<p>We decided to start migrating or having the English documentation in GitHub. That&#8217;s one place. Also GitHub has natively, the Markdown editor, so with some commands and some things we can put everything there in a way that everybody can take the English document and translate it into their language.</p>



<p>For example I&#8217;m doing that, I&#8217;m starting to do that in a beta project for the advanced documentation. That&#8217;s something we&#8217;ve been working on for more or less 8 months. It was a very difficult thing to arrive because it&#8217;s been a big problem. A lot of people have been involved, a lot of languages, people from different countries involved, a lot of teams involved. So it has been a very technical challenge in a way.</p>



<p>[00:13:00] <strong>Nathan Wrigley:</strong> Thank you so much. I don&#8217;t know if Courtney wants to add anything to that before we move on.</p>



<p>[00:13:05] <strong>Courtney Robertson:</strong> Yeah. So my background, before going full time contributing to WordPress, was that of a teacher. And in the education space within America we have a lot of ESL, English Second Language. So we have a lot of people that don&#8217;t primarily speak English, and it&#8217;s a disservice to them in the education system to expect them to understand the content on top of having to simultaneously translate a language. That&#8217;s a really big learning difficulty.</p>



<p>So I very much wholeheartedly believe in providing access for people to learn WordPress in their own languages. Down to reading the captions on videos. If you&#8217;re an English speaker I would encourage you to go over to wordpress.tv, try to find a video that is not in your language, not in your first language, and subject yourselves to reading the captions and think about how fair is that for the rest of the world.</p>



<p>So with that in mind, in Learn WordPress we have a different workflow perhaps than the Docs team. So Docs again think of as the dictionary and the reference manuals, and Learn as the teacher&#8217;s spot to be, or the direct learner&#8217;s spot to go, if they don&#8217;t find reading the manual version to meet their learning style.</p>



<p>And that&#8217;s something that we very much want to consider. Some people need a little more instruction to be able to get the concepts. And so Learn WordPress exists for that, both direct learners and educators. And over there we do not get access to Rosetta sites and instead we rely upon one instance of Learn WordPress.</p>



<p>Whereas in the Rosetta sites and what we&#8217;ve heard from recent episodes with Vagelis and Piermario, just a few episodes back. We could hear that from what they&#8217;ve shared in other parts of the WordPress project there are tools to basically make a whole separate locale instance going on. So if you were in Spain and you wanted to read the same type of content, you would have an entire version of the site that is just for you.</p>



<p>Whereas with Learn WordPress, what we have going on is all the languages all smooshed into one site. And what becomes difficult is we don&#8217;t have good workflows yet established around if the English language version gets an update, how do I assess what content? I speak only a tiny bit of Spanish and a tiny bit of Latin, of all the things. Good conversation starters.</p>



<p>So you won&#8217;t find an easy way to identify even what the other topics are with the same title. Let alone somebody that can&#8217;t assess what that content looks like. So we have some locale ambassadors, Piermario is doing a great job with the folks based out of Italy on rounding up some efforts there. Margarita especially, is someone that&#8217;s participating with Piermario on identifying the content to be translated into the Italian locale.</p>



<p>So we&#8217;re basically duplicating the content, but just in other languages all under the same site. So that&#8217;s not the most efficient way and we&#8217;re using GitHub as well to do some of this work. We have GitHub issues that have a template. So think of GitHub issues as logging something on the WordPress forums, right? It&#8217;s about on par with that. But we prefill what the text of that issue is, and have a workflow to publish that.</p>



<p>But that&#8217;s not necessarily in conjunction with what the English version, last update, is or plans of how do we maintain those updates? And then, how do we also look and see if the Docs team did a certain bit of update? And how do we find the polyglots that really like these specific areas? You can see this becomes quite a challenge as we&#8217;re looking ahead to Gutenberg phase four with multilingual support natively. We&#8217;re still a ways out from that, but you can see where this is something to start untangling and working on internally before we roll it all into Core.</p>



<p>[00:16:59] <strong>Nathan Wrigley:</strong> So it sounds like that this is a spaghetti of things just loosely held together simply by people actually understanding what the processes of the different teams are. But we don&#8217;t have this one workflow, which presumably is some kind of goal. But we do have a moment in time, which would be the release of Gutenberg phase four, where hopefully a large proportion of this would be either in progress or completed, because at that point WordPress itself becomes translatable. And I suppose at that point it would be incredibly useful to have this work done.</p>



<p>I just want to touch on a couple of things that may have confused the listeners because we&#8217;re all speaking, probably in a bit of an echo chamber here. And so there were a couple of things which were mentioned. The first of which was Rosetta, that got dropped a couple of times, and it may be useful for people to actually know what that means. So if anybody&#8217;s willing to just very briefly explain what Rosetta is. I mean we know what the stone is and so we get the connection there but, what is that thing in WordPress?</p>



<p>[00:17:57] <strong>Javier Casares:</strong> The Rosetta sites are the locale sites in WordPress. So we have wordpress.org, everything is in English, it&#8217;s the main site. Most of everything is there. But, for example, for Spain we have es.wordpress.org, or for Catalan we have ca.wordpress.org or I don&#8217;t know for French we have fr.wordpress.org.</p>



<p>Those are translation sites from the main site, but not everything is in there. There are the main contents, for example, the download page, everything is in your language. When you download the WordPress from that site, it&#8217;s in your language. It includes the translation files. But each site can be managed by different people.</p>



<p>For example, in Spain we usually publish one post every week talking about things. It can be translation from general post, or it can be local things about WordCamps in Spain or whatever. So that&#8217;s more or less the thing inside the Rosetta. It&#8217;s the technical name, the project, the Rosetta project is the name or the locale site. So that&#8217;s more or less the thing.</p>



<p>[00:19:12] <strong>Nathan Wrigley:</strong> Yeah thank you, that&#8217;s perfect. That explains it beautifully.</p>



<p>The other thing that was mentioned was eight languages have been put forward as the language is to get us to 80%. So I guess it would be quite nice for the listeners to know what those languages are. I don&#8217;t know if a quick Google search needs to be done there, or if anybody&#8217;s got that information to hand. But it would be nice to know eight languages initially are.</p>



<p>And also to know that isn&#8217;t the entire scope of the project. That&#8217;s more a, let&#8217;s get something over the line with these eight languages, as opposed to that&#8217;s what we&#8217;re doing and that&#8217;s all that we&#8217;ll ever do.</p>



<p>[00:19:44] <strong>Javier Casares:</strong> Yeah. I have some information from the hosting team, and it was like, okay, I&#8217;m going to analyse where and what language are the most downloaded in WordPress. So these languages are not the eight most top languages in the world, they are are the most used in the WordPress ecosystem.</p>



<p>So that&#8217;s the main idea behind having those languages as the main ones. German, more or less the 6% in the WordPress scope. English, the 48%, Spanish 7%, French 5%, Italian 4%, Japanese 6%, Portuguese 5%, and Russian 3%. More or less that covers the 80% of the documentation or languages that WordPress has installations.</p>



<p>[00:20:34] <strong>Nathan Wrigley:</strong> Okay thank you, that&#8217;s great. That clears that one up.</p>



<p>So I guess we&#8217;ve highlighted a problematic past, well not really problematic, it&#8217;s just the way the project evolved where everything is done in a unique way depending on the team, or which part of WordPress you&#8217;re touching. And maybe this one is for Estela. The enterprise of this podcast really is to highlight some future where we improve things and we take things forward, and you have outlined, I guess a project is the best way to describe it.</p>



<p>What is your idea? What is it that you want to happen in the future? We don&#8217;t have to create timelines or anything, but let&#8217;s just imagine that we&#8217;re a decade out from now and it&#8217;s all been achieved, what would be your north star for all of this?</p>



<p>[00:21:16] <strong>Estela Rueda:</strong> This is where we are, you know where we are working at right now, where we are starting. I started with this Spanish team. They are my trial team. And the only reason why I started with them is because I speak Spanish and it&#8217;s easier for me to guide them. We had to start the project in, you know, baby steps, go little by little. The idea is to create a process or a model that we can replicate into other languages.</p>



<p>I started with the style guide and how to write documentation in Spanish, because we have many grammar issues with the language. First of all, you know, we have the way we address each other, like formal, informal or we have the language is genderised, completely genderised. Everything is either female or male, there is no neutral gender in Spanish.</p>



<p>There are so many issues that we need to address. And I&#8217;m pretty sure other languages have the same or similar problems in their grammar, you know, grammatically speaking. And we need to address those and, how are we going to use them in documentation, in order to make it as neutral as possible and as easy to understand? They&#8217;re going to be like, you know, writing rules.</p>



<p>Then we have the translation of the sitemap. Now, what I did with the Spanish team, we spent during a WordC amp, a whole contributor day, translating the site map for end user documentation. But I sat the marketing, the polyglots, and the documentation teams together. And I told them, okay, we&#8217;re going to translate but I don&#8217;t want you to translate literally. I asked marketing, give us words that are searched for, that will help with the SEO of the site. So that way we can localise also, and we can increase the use of the translation of WordPress.</p>



<p>After that, I guess we&#8217;re going to start working into translating documentation. We&#8217;re going to create teams, and we&#8217;re going to start working on it. My idea is to start some sort of triage hours with teams. And let&#8217;s say twice a month, to review what we have written and to continue writing and just that sort of thing.</p>



<p>Because I know that if I leave it to every contributor day for every WordCamp it&#8217;s just never going to happen. And this is something that we need. If we want to progress we need to work, you know, a little bit every day, a little bit every day.</p>



<p>So if we don&#8217;t put set goals then this is not going to happen. But that&#8217;s where I am right now. And I will reach out to the Brazilian team who approached me and may be the second team that I start working with.</p>



<p>[00:23:56] <strong>Nathan Wrigley:</strong> So Estela, just to be clear the intention here is to delve into, in your case, the Spanish language and come up with a rule set, like a workflow. Where, okay, if we receive things in English, these are the set of constraints that we&#8217;ve got when we translate into Spanish. So somebody who is new to the team would be able to look at those guidelines, the workflow document, whatever it may be and have a very strong idea of, okay, this is the way to do it. When you&#8217;re going from English to Spanish, this is how you do it. Have I understood that correctly?</p>



<p>[00:24:29] <strong>Estela Rueda:</strong> Yes. But those writing rules, or the style guide, I call them the writing rules because that&#8217;s what they are. But I want to apply that for every language, just not for the Spanish team. And that style guide has to be according to the language grammar, not to what we like.</p>



<p>[00:24:45] <strong>Nathan Wrigley:</strong> In my head I&#8217;m seeing a website when you say that, but of course, you&#8217;re talking about the style of the language, in your case the sort of gender that you&#8217;ve got to go to and things like that. That&#8217;s interesting. And, can you give us some sort of insight into how that&#8217;s going? Has it proven to be fairly straightforward to put that workflow together or is it a really thorny thing to unpick?</p>



<p>[00:25:03] <strong>Estela Rueda:</strong> We are just at the beginning of it. I just pitched this idea at the WordCamp in Pontevedra, which was last month, two months ago. And I realised that I need to sit down and start writing. So I gave them some sort of topics that might affect the language, and gave it to the team, to the Spanish team actually.</p>



<p>They are going to start writing the style guide. And I said listen, I write something, ideas that I have and if they are not okay, feel free to go ahead and edit and change them. And let&#8217;s see what affects us where. Is it easy? No it&#8217;s not easy. It&#8217;s going to be difficult because like I said, we have 14 locales, or 14 Rosetta sites, for 14 different versions of Spanish. And we need to come together to a point where, what is the most common use for everybody?</p>



<p>[00:26:03] <strong>Nathan Wrigley:</strong> So this question is going to sound a bit meta, meta in the real sense of the word. You are creating a document which then you will be able to share to other teams in order that they can run their own process. So a silly example, the Latin version of WordPress would need to look at what your team have put together, how to go through the process? Which they can then implement with their own locale.</p>



<p>[00:26:28] <strong>Estela Rueda:</strong> Yes. I will be documenting. Actually this week I&#8217;m going to publish a post in the Polyglots team regarding about this step one, step two. So what is the writing style guide and why are we writing it? And what happened to the sitemap and how we came up to what we have.</p>



<p>[00:26:44] <strong>Nathan Wrigley:</strong> So just talking about it on this podcast, it seems like a fairly solvable problem, but of course when you actually apply thought to it, this really is a gigantic plate of spaghetti. There&#8217;s an awful lot to be unpicked. There&#8217;s an awful lot of work to be done. And I&#8217;m just wondering how you feel about this, whether you&#8217;re sanguine.</p>



<p>And it&#8217;s not necessarily for Estela, it&#8217;s for everybody on the call. How you feel about whether this project is going to be able to ship its aspiration in the, well let&#8217;s say, it&#8217;s probably a matter of years not months certainly, but probably under a decade, before Gutenberg four comes out.</p>



<p>Because it does sound, on the face of it, it sounds like you&#8217;ve got an awful lot of work to be done. If you complete the Spanish, then you&#8217;ve got to move on to another one. You&#8217;ve got to get people&#8217;s buy in, you&#8217;ve got to re educate those people who are contributing their time, as translators. They&#8217;ve got to be re educated to do it in a different way. How positive, sanguine do you feel that this is achievable?</p>



<p>[00:27:41] <strong>Courtney Robertson:</strong> Nathan, I&#8217;ll jump in here. One of the ideas that a coach in my life has shared with me, the motto of this company is, a world that works for everyone with no one left out. And I think about that a lot in the context of open source, and how we make WordPress possible for the whole globe, right?</p>



<p>We are trying to make this tool that we have available, be available for as many people as would have used it, and make the best of that situation. And if we take that backwards to a place where we might need a mindset shift to go on, let&#8217;s think about a couple of features in the WordPress project that have rolled out within the last few versions of releases, and the naming that goes into it.</p>



<p>I know the community would like to improve how we name things from this outset, so that we don&#8217;t have to rename them later. So one example that I thought went really, really well is what became the Command Palette. The initial proposal was to call it something along the lines of Wayfinder. And one of the great insights, because we were able to identify and put this kind of call out across social media and other places, it was not something that was just buried and obscure over in GitHub.</p>



<p>It was raised throughout the community and a lot of folks said, that doesn&#8217;t make sense in my language. If you do a direct translation this does not make sense. So it&#8217;s not just about translating after the fact, but it&#8217;s also about how we name things really even before it gets widely publicly released.</p>



<p>And so that&#8217;s a mindset shift that I think, I&#8217;ll say as an English speaker, I really think that we need to experience more of being the second language to truly appreciate and understand the depth of why naming things matters so greatly. The depth of why we need to consider how this will work with other languages. Consider the workflow process. To the point where we&#8217;re not just, yes, it will probably remain English forward first.</p>



<p>But to always tuck in mind the processes that go on downstream after we get the thing out in English or what have you. What are we asking our translation folks to do, and how does this impact somebody in a different language? I learned that when Learn was added the navigation menu across all WordPress sites, that the way it had been translated, particularly into Russian, Olga caught this one, it didn&#8217;t make sense in the way that it was translated. And so we have to think about these things before we just ship sometimes.</p>



<p>[00:30:22] <strong>Nathan Wrigley:</strong> I have this intuition that if the Command Palette had been called something, even adjacent to the Command Palette, it would have stayed like that. It the controversy of it being so poorly named that led the community to sort of say, well that&#8217;s really not the right idea.</p>



<p>And so sometimes I wonder if backing yourself into a corner is the best way to get attention, if you know what I mean. It&#8217;s probably not the desirable outcome but it is possibly a way that, you know, people get enraged by something and so they go out on social media and change happens more quickly.</p>



<p>From what I&#8217;m hearing there Courtney, you&#8217;re basically making a moral argument for this. It&#8217;s the right thing to do. It doesn&#8217;t matter what the goal is, whether we achieve this in a matter of 2 years, 6 years, 10 years, whatever it may be. The journey is the important thing, making the steps now to make this possible is the important point, not the end goal.</p>



<p>[00:31:11] <strong>Courtney Robertson:</strong> Absolutely true. Yes.</p>



<p>[00:31:13] <strong>Nathan Wrigley:</strong> Okay, thank you.</p>



<p>So I guess in order for this to happen, as with many things in WordPress, bodies need to be on the ground. We need people actually doing this work. There&#8217;s probably a whole lot of people listening to this who are already committing their time to translations, but there&#8217;s probably a lot of people who haven&#8217;t. So I guess we need to speak to them.</p>



<p>Firstly, I suppose we need to reassure people that if in the future, if this project has wings and takes off and it all goes in this direction, that they will be educated in the new ways of doing things. But also a call out to people who haven&#8217;t yet committed their time and feel that they could commit their time. How do they go about doing it?</p>



<p>So let&#8217;s tackle it in two parts. The first one, to people who are already translating, will there be education materials? Will there be instruction as to whatever comes out of this whole process?</p>



<p>[00:32:04] <strong>Javier Casares:</strong> Okay. So for me, we will need two different teams. This is not a polyglots project in a way. Obviously everybody will be invited to participate on everything, but I don&#8217;t think that the same people translating WordPress plugins, themes or whatever, needs to be the same people translating documentation.</p>



<p>So in a way, at least for me, because I think those are two very different things. As Courtney was saying, translating a plugin for example, or WordPress per se, maybe you need to be a little more literal in the translation. But documentation is different because people need to learn about what you are explaining. So you need to relate with that person.</p>



<p>So in this case that&#8217;s the work Estela is doing. You need to know how to communicate to these people, and that&#8217;s very different than translating a thing. So for me, it&#8217;s not like translating documentation is adapting or doing your own documentation based on one in another language.</p>



<p>So we don&#8217;t need to have the same documentation because, cultural things or whatever. Because not everybody in all the countries, in all the languages, use the same tools, the same things. So that&#8217;s one thing we need to have in mind. For example, as I was saying at the beginning, I just started leading the advanced administration handbook like one year or two years ago. That&#8217;s something Milana gave me as a gift in a way.</p>



<p>So one thing I started, for me this is the pilot in the technical part, not in the documentation part. But now the only thing, or main thing we have in GitHub, in English, everything synchronised with WordPress, is the advanced admin handbook. So for me the next step is to do the technical part for this translation.</p>



<p>We need to check also the technical part because writing right is one thing, but doing the thing is another step we need to check. And that creates a lot of new problems in a way. Because we have new content, we have updates, and we have changes in the documentation. Because it&#8217;s not the same changing or creating a new feature, because I don&#8217;t know the command palette and everything. It&#8217;s a new thing from one, two versions ago.</p>



<p>So we need to create all the documentation. We need to notify everybody in all the languages that we have this new. So we need to translate everything and we need to check with the Polyglots team, how are you going to name the palette in your language and everything? Everybody should be involved in a way, because documenting in all the languages should be a global thing, not a local thing.</p>



<p>And also, the notifications. We need to have like three levels in the translation part, because we need the translators. We need people doing the translation per se. And we need something like the GTEs. So people can check that the translation is doing fine, the translation is right. And we need project managers because each documentation is not the same. The advanced admin handbook, the end user documentation, the Learn WordPress whatever, the plugins handbook, the themes handbook, developers handbook. Each documentation needs one or two or a team that can control the publication that everything is right.</p>



<p>For example, one thing we talk in WordCamp US was how we are going to relate it&#8217;s language? Because we don&#8217;t have that now. So if we publish the documentation in Spanish and somebody wants to go from this page to another language, how are we going to do that? Because that&#8217;s not something we have now.</p>



<p>So we are trying to solve phase four before we have phase four. So we have a lot of challenge in the organisation and in the technical part. Also with the translation or the organisation about how we are going to talk to people. Because, for example, the Spanish for me is one of the best examples, because in Spain we have a more direct, we talk to people and in Latin American they talk in another way.</p>



<p>So we need to find like a common ground because we cannot maintain the Spanish documentation in 12 or 15 different ways. So we need to create a standard or international Spanish. That&#8217;s something that more or less exists, but we cannot create a lot of different documentation. So we need to have that in the translation part. We need to have that documentation, that style guide. We need to have one international Spanish because we cannot maintain, we don&#8217;t have a lot of people maintaining some little languages or whatever, because it&#8217;s not possible right now in the WordPress ecosystem.</p>



<p>[00:37:35] <strong>Nathan Wrigley:</strong> Thank you. That was really insightful. I got an awful lot out of that. I just have a little question off the back of that. So, is the intention then to build I guess more or less software to take care of this notification problem? And obviously there&#8217;s a lot more than notifications. There&#8217;s, you know, the work that needs to be done, and perhaps the order that it needs to be done, and who it&#8217;s going to be assigned to.</p>



<p>Is the intention to have that as, if you like, paper based web pages or is the intention to have a piece of software that people can log into and assign themselves tasks, and offload tasks, and check things out, and then finally hit publish if something meets all of the different criteria? And it sounded like it was partially done but I don&#8217;t know if that&#8217;s falling on your shoulders Javier. Just a little guidance around that.</p>



<p>[00:38:18] <strong>Javier Casares:</strong> Yeah. that was one of the main things we have pending. We started talking about this in WordCamp US, in the contributor day. Right now, for example, for the advanced admin handbook I&#8217;m going to lead everything in the Spanish part because I think we need to test everything, and I&#8217;m going to test this development part or whatever we are doing. I know Milana is doing it for the end user. She&#8217;s creating like teams in GitHub and doing actions and everything.</p>



<p>She&#8217;s starting to automatising more or less the notifications and everything. So the main idea is we will have translation teams. So for example, the Spanish translation team, or the German translation team. And you will apply in those teams. And when something changed, in the English part, you will get a notification.</p>



<p>For example, there is a new page. This document has changed because of whatever. So we need to inform people that we need a new version, or to update something, or to add something to the documentation. And then we need another step that when somebody translates something, it needs some checking or review or whatever. So we need like the GTEs in Polyglots more or less, the general translation editor. So people that know imperfection, the style guide or whatever. And they will check that this document is ready to be published.</p>



<p>This is something we start talking and I think it will be something good for the project, is to create versions for the documentation. When we have 6.4 or 6.5 or whatever version, we can create a new batch of documentation, and we can create the 1.2 version of the end user documentation. So we can have a history of everything that changed, and we don&#8217;t need to put the documentation every day.</p>



<p>So we can have a weekly or a monthly updating. So it&#8217;s control, it&#8217;s more like the WordPress. So everybody will know where the new version is going to be published. If you need to add this document, priorities or whatever. So that&#8217;s something we are working on now, but there are a lot of people involved testing different things.</p>



<p>So for example, Estela is doing the documentation for Spanish. I&#8217;m testing the technical part. Milana is testing this notification system. So we need to check everything because we don&#8217;t really know if this project is going to be real, but we think it will be. But we need to check everything, and we need to do this in parallel because we cannot wait to have all the work from one person to do the next step.</p>



<p>I think that&#8217;s something we are going to work on in the next contributor days in some places. At least in Spain I&#8217;m going to try to do this. And for example, that&#8217;s my next step in the documentation part, is going to test this technical part. How are we going to organise everything?</p>



<p>So everybody is invited to participate. So if anybody wants to check things, we can talk. Probably in the Polyglots or the documentation channel in Slack. So I think a lot of people are doing the right steps right now, and before 2024 we have some pilot or something finished.</p>



<p>[00:42:02] <strong>Nathan Wrigley:</strong> If you&#8217;ve ever been involved in creating software, you&#8217;ll know that the devil is in the detail. And although it&#8217;s easy to say what you&#8217;ve just said, I suspect that it will be fiendishly challenging.</p>



<p>Firstly, good luck, I hope that your endeavors pay off. And it does sound like you would desperately want some people to cast their eyes over this.</p>



<p>And we&#8217;ll get onto that in a moment. We&#8217;ll figure out a way where people can get in touch if they wish to. But you&#8217;re clearly all good people. You have the, what I&#8217;m going to describe as the right moral intentions here. You are giving up lots of your time for this worthy cause. Nobody could deny that this is a fabulous endeavor.</p>



<p>But for people who are listening to this and sitting on the fence, thinking to themselves, what would I get out of translating? It&#8217;s a bit of an ephemeral question really, but I&#8217;m wondering if you could portray or explain to us, what do you get out of this? Apart from the fact that you&#8217;ve translated a software project, that much is obvious. But, do you get like a warm, fuzzy feeling out of this? Does it make you feel good? Is there a good community? Are there nice people sitting behind translation that you&#8217;ve become friends with? I&#8217;m trying to offer a path for people who kind of want to commit but haven&#8217;t committed, because they just see it as there&#8217;s more things to do on my plate each week.</p>



<p>[00:43:13] <strong>Estela Rueda:</strong> I think that friendships, they just come. They are just like part of it. But that&#8217;s not the reason why I do it. For me it&#8217;s more about empowering people. I think that, you know, if I can translate more of the documentation in another language then there will be more plugin developers, or theme developers, or agencies in that country. And then you will empower people. You will empower more people because they will be able to start their own businesses, you know, create their own little plugins and start small like we all did at some point, and then become bigger and bigger.</p>



<p>I don&#8217;t know, I kind of took into that Matt&#8217;s dream about a hundred years. I think that if we open everything up for more countries, more cultures to join, then WordPress will be bigger and bigger and more people will use it.</p>



<p>[00:44:10] <strong>Nathan Wrigley:</strong> Thank you so much, Courtney. I think maybe you want to chip in there.</p>



<p>[00:44:13] <strong>Courtney Robertson:</strong> I really love solving complex puzzles. And so if we look, devils in the details. Relaying communications between docs and training becomes pretty important. So not only do we want to leverage Milana&#8217;s system about the GitHub actions, some of that automation work that can notify people in other languages. But also the communication between the teams about the same topics or the areas in which our topics overlap. It&#8217;s a fun thing for me to do that.</p>



<p>But then in addition, as I kind of look more broadly like Estela, I firmly believe in empowering others. And that&#8217;s really what open source and the four freedoms give us. You are free to do what you would like with this thing.</p>



<p>So to make that possible my method is to solve big problems, I guess. To work on these interesting challenges so that more people can leverage what&#8217;s going on and get involved along the way, and have mentors and others to connect with. Because for every time that I felt personally like I didn&#8217;t know what was going on, or I didn&#8217;t understand the value that I brought, or understand how I could start contributing with something small, I want to remove those barriers for other people. I want to make their lives a lot better from that process.</p>



<p>[00:45:34] <strong>Nathan Wrigley:</strong> What a fabulous set of answers. Thank you so much.</p>



<p>We&#8217;re running short of time. I guess the only thing that we should say before we wrap up is to give out a shout to people who are sitting on the fence, who haven&#8217;t contributed so far. What is the best way, the quickest route to finding out more? Is there a particular page that you would highlight more than any others? Is there a particular venue to go to? Is this a contributor day kind of thing? What would you recommend? We could take that one at a time. So let&#8217;s start with, well let&#8217;s go back to Courtney.</p>



<p>[00:46:05] <strong>Courtney Robertson:</strong> Sure. Since our process looks a little bit different than what you see in Docs, for instance, I would encourage folks to swing by the training team. You can find our main site at make. wordpress. org slash training. There is a handbook in our top navigation area and inside of that has some information on how to get started with content localization. I&#8217;ll make sure that we have all those show notes. As well as a GitHub issue to log if you want to take part in that translation effort.</p>



<p>And for those inside the WordPress project that are really skilled with amazing things like GitHub Actions, if you understand how to make GitHub automate some stuff, there is a channel if you search for GitHub inside of the channels area, you&#8217;ll find a channel where we share tips and tools about GitHub activity.</p>



<p>[00:46:51] <strong>Nathan Wrigley:</strong> Thank you so much, Courtney. Estela, anything that you wanted to add?</p>



<p>[00:46:55] <strong>Estela Rueda:</strong> You can go into documentation Slack channels. We meet on Tuesdays, 2 PM UTC, and just join us. And then we can talk about it. We are trying to look now for Documentation writers, but they are also bilingual. So they do need to dominate at least one word so that they can help us in the future once we move into their own language.</p>



<p>We have, actually the documentation team is, most of us are non English speakers. English is not our first language, so we have a lot of people that speak other languages, and they do help when it&#8217;s necessary. Now, we have several posts. I&#8217;m posting, like I said, I&#8217;m documenting what I&#8217;m doing, and we&#8217;ll be documenting it both in Documentation and polyglots, and just pick it up from there. Join the polyglots team. They are open to every language, or every Rosetta side, locale team. They all need contributors. They all need translators. So that&#8217;s the best way.</p>



<p>[00:48:01] <strong>Nathan Wrigley:</strong> Thank you so much. And Javier, if you&#8217;ve got anything to add there.</p>



<p>[00:48:05] <strong>Javier Casares:</strong> Yeah. In my case if anybody wants to check the most technical part or be involved in the testing, they can ask me directly in Slack. Because right now it&#8217;s like I&#8217;m doing the test alone. I probably when I do the main testing, I will explain everything because we did the proposal in the make.wordpress.org slash project. You can look for a proposal, documentation, translation, localization.</p>



<p>That&#8217;s the main document explaining everything. It explains why we are doing this. How we are going to do that. I think, right now, Estela, Courtney, Milana, and I are the ones involved. So another way is to, at least for this project, is to contact us, and we will try to put you in the right place to contribute.</p>



<p>Yeah, we are always open to help people. So another way is to contact directly to us.</p>



<p>[00:49:09] <strong>Nathan Wrigley:</strong> Well, Thank you so much, the three of you, for joining us today. Thank you Courtney, Estela, and Javier. I really appreciate it. Obviously, a very complicated set of challenges to come, but hopefully with your and other people&#8217;s contributions, WordPress will be readable by all the world. Thank you so much for your contributions today.</p>
</div>



<p>On the podcast today we have <a href="https://profiles.wordpress.org/estelaris/">Estela Rueda</a>, <a href="https://courtneyr.dev/">Courtney Robertson</a> and <a href="https://wordpress.org/support/users/javiercasares/">Javier Casares</a>.</p>



<p>Courtney is a former teacher who now focuses on contributing to WordPress. With a background in education, she understands the challenges faced by English Second Language (ESL) learners in the American education system. She’s passionate about providing access to WordPress in multiple languages, as she believes it is unfair to expect non-English speakers to simultaneously translate content and understand it.</p>



<p>Estela is a language enthusiast who has spent years navigating the challenges of website localization. As a member of the WordPress community, Estela has come across the intricacies of language differences and the need for accurate translation in various Spanish locales. With 14 different Spanish locales to handle, Estela&#8217;s expertise in understanding the subtle nuances and localizations of each language variation has been indispensable.&nbsp;</p>



<p>Javier Casares is a dedicated member of the WordPress community. With expertise in creating documentation, Javier has been instrumental in developing handbooks for various sites. However, there have been some technical challenges. Despite these obstacles, Javier, as you will hear, remains committed to addressing and solving the documentation issues at hand.</p>



<p>This episode covers the important topic of translations and making WordPress documentation more accessible to people worldwide. Our guests bring a wealth of knowledge and experience to the table as they discuss the complexities and challenges of language translation in the WordPress ecosystem.</p>



<p>We start by highlighting challenges posed in translating WordPress, such as the tangled processes currently in place, as well as more language focussed topics. We talk about the extensive collaborative effort involved in translating WordPress and the plans to expand translation efforts to documentation with the help of dedicated teams.</p>



<p>We get into how contributors might need to rethink the way that&nbsp; many of the current translation processes are structured. We discuss the different approaches needed for translating plugins and themes versus documentation. We touch upon how technical aspects of these processes, such as content creation and updates, also pose significant challenges.</p>



<p>All three guests stress the importance of global involvement in translation efforts, including translators, reviewers, and project managers. They advocate for the development of standardised style guides for each language to maintain consistency, and they explore the possibility of creating software or tools to manage translation tasks.</p>



<p>Courtney, Estela, and Javier all acknowledge the challenges ahead, but express optimism that their ideas will help make WordPress accessible for all. Communicating how WordPress is built and how it works is an endeavour tightly aligned with the project&#8217;s overall mission of democratising publishing.</p>



<h2 class="wp-block-heading">Notes provided by the guests</h2>



<p>We want to offer non-English speaking people the possibility to access all the WordPress documentation in their language. To accomplish that we need to translate all the actual documentation at HelpHub, DevHub, Learn WordPress and some Handbooks.</p>



<p>But, the problems are not to do the translations per sé, but where to put that in each language, how to get the updates from the English primary documentation, and then how to maintain everything in place.</p>



<p>First, we need to know where are we putting the documentation, because this project cannot wait until Gutenberg Phase 4. This means that Local Communities should be involved here (for example, where are we putting the documentation in Spanish? es.wordpress.org/documentation, developer.es.wordpress.org?)</p>



<p>After having the right place&#8230; how are we going to know if something changes? The best way is probably using the same way we are translating right now: translate.wordpress.org, (GlotPress). If we can use this platform, each page can be translated and, when arrived to the 90% threshold, it will be shown in the local language page.</p>



<h2 class="wp-block-heading">Links provided by the guests</h2>



<p><a href="https://make.wordpress.org/polyglots/2023/08/15/discussion-for-a-proposal-for-wp-org-content-translation-and-localization/">Discussion for a proposal for WP.org content translation and localization</a></p>



<p><a href="https://make.wordpress.org/docs/2023/01/24/new-look-new-site-new-helphub/">New look, new site, new HelpHub</a></p>



<p><a href="https://make.wordpress.org/docs/2023/02/07/future-plans-for-helphub/">Future plans for HelpHub</a></p>



<p><a href="https://make.wordpress.org/training/handbook/training-team-how-to-guides/content-localization/">Content Localization</a></p>



<p><a href="https://github.com/WordPress/Learn/issues/new?assignees=&labels=Awaiting+Triage%2C+Translation%2C+Needs+Translation+Reviewer&projects=&template=content-translation.md&title=LANGUAGE+translation+for+CONTENT+TYPE+%22CONTENT+TITLE%22">GitHub&#8230; Issue: Content Translation Template</a></p>



<p><a href="https://make.wordpress.org/project/2023/09/06/documentation-translation-localization/">Proposal: Documentation translation / localization</a></p>



<h2 class="wp-block-heading">Useful links</h2>



<p><a href="https://developer.wordpress.org/advanced-administration/">WordPress Advanced Administration Handbook</a></p>



<p><a href="https://make.wordpress.org/polyglots/handbook/for-locale-managers/rosetta-for-the-community/">Rosetta for the Community</a></p>



<p>Previous podcast episodes with <a href="https://wptavern.com/podcast/93-piermario-orecchioni-on-how-and-why-wordpress-gets-translated">Piermario</a> and <a href="https://wptavern.com/podcast/91-vagelis-papaioannou-on-how-to-learn-to-use-wordpress-and-help-with-events">Vagelis</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 01 Nov 2023 15:15:04 +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: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:58:"Do The Woo Community: Do the Woo Day 2 Recap, WooSesh 2023";s: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=77699";s: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://dothewoo.io/do-the-woo-day-2-recap-woosesh-2023/";s: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:370:"<p>Conversations around AI and customer support, Amazon Pay, personalization and privacy in ecommerce and shipping trends.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/do-the-woo-day-2-recap-woosesh-2023/">Do the Woo Day 2 Recap, WooSesh 2023</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 01 Nov 2023 12:23: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: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:49:"HeroPress: From Sci-fi Dreams to Software Reality";s: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:56:"https://heropress.com/?post_type=heropress-essays&p=5985";s: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:150:"https://heropress.com/essays/from-sci-fi-dreams-to-software-reality/#utm_source=rss&utm_medium=rss&utm_campaign=from-sci-fi-dreams-to-software-reality";s: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:7038:"<img width="1024" height="512" src="https://heropress.com/wp-content/uploads/2023/11/103123.webp" class="attachment-large size-large wp-post-image" alt="Pull Quote: Failures are just milestones, not endpoints." /><p>Growing up, my family didn&#8217;t have much. Yet, a quote always resonated with me: &#8220;If you&#8217;re born poor, it&#8217;s not your fault. But if you die poor, it&#8217;s your fault.&#8221; My humble beginnings never deterred my aspirations.</p>



<p>As a child, my exposure to technology was limited. In our village, neither schools nor homes had computers or mobile phones. My fascination with technology was sparked by sci-fi movies I watched on television, where characters operated these machines called &#8220;computers.&#8221;. That first moment when I laid my eyes on a computer, I knew my life was about to change. The real encounter with a computer came in 2006 when a neighbor purchased one.</p>



<h2 class="kt-adv-heading5985_7896f3-28 wp-block-kadence-advancedheading">Finding The Internet</h2>



<p>In 2008, My family moved to the town and it opened up a world of opportunities. Later that year a friend introduced me to a Cyber Café, where for just 20 Indian Rupees (24 cents US), I could play games for an hour. After saving the money for two weeks, I visited the café for the first time. Over time, my interest shifted from playing games to exploring the computer itself. It was a Windows XP machine, and I recall being intrigued by its features. This exploration continued almost every month for the next two to three years.</p>



<p>By 2011, I had become proficient with the internet and was familiar with operating systems like Windows, Linux, and Mac. That year, my father bought me my first phone, a Nokia 7210 Supernova. While it wasn&#8217;t a smartphone, it sparked my curiosity about the creation of software and websites. </p>



<blockquote class="wp-block-quote">
<p>I researched &#8220;how to make a website&#8221; and encountered HTML and CSS. </p>
</blockquote>



<p>Initially overwhelmed by the complexity, I decided to push forward, and by the end of the year, I had launched my first website using an online builder and my Nokia phone.</p>



<h2 class="kt-adv-heading5985_4d0263-45 wp-block-kadence-advancedheading">Teaching Myself, Teaching Others</h2>



<p>My passion for technology only grew from there. I self-taught programming languages like JavaScript, PHP, Python, Java, C, and C++. I also learned computer hardware maintenance and served as a go-to tech helper in my community. Impressively, I became a full-time Teacher and SysAdmin for a local school, managing five servers and around a hundred computers. All of this knowledge came from internet tutorials.</p>



<p>I truly developed a passion for web technologies. </p>



<blockquote class="wp-block-quote">
<p>My first encounter with WordPress.com in 2012 was underwhelming, as I perceived it to be just another blogging platform like blogger.com. </p>
</blockquote>



<p>Yet, a few months later, my discovery of WordPress.org profoundly shifted my perspective. By 2014, I had set up my own WordPress blog. Despite juggling a demanding college schedule and coursework, I consistently set aside time each night to keep up with the latest developments in WordPress and other web technologies. Much of what I&#8217;ve learned comes from the generosity of online communities. In gratitude, I&#8217;m eager to share my own experiences, hoping to guide others on similar paths.</p>



<p>Being a teacher was a fulfilling and enjoyable experience. One of the highlights for me was the opportunity to share my knowledge with the children and witness their growth and development. Teaching stands out as one of the most rewarding endeavors of my life.</p>



<h2 class="kt-adv-heading5985_5fbc60-f3 wp-block-kadence-advancedheading">Shifting Gears</h2>



<p>Driven by a strong desire to delve deeper into web technology, I realized I had become too comfortable in my current role, working as a Teacher. In October 2020, I made the difficult decision to leave my teaching position and venture into the realm of Web Technologies. This decision did not come easily, as I had no alternate source of income and my savings were limited, only sufficient to last a few months. For the next three months, I found myself unemployed, but I utilized this time to extensively explore web technology, with a particular focus on WordPress.</p>



<p>Despite grappling with imposter syndrome at the time, I was completely unaware of its impact on me. </p>



<blockquote class="wp-block-quote">
<p>I found myself reluctant to apply for job positions at various companies, filled with doubt about my abilities, and questioning whether I had acquired sufficient knowledge or was proficient enough to undertake the work. </p>
</blockquote>



<p>What I failed to realize then was that all I needed was a little push—a smidgen of encouragement—to help me advance with the skills and knowledge I possessed. I am immensely grateful to Topher DeRosia for providing me with that much-needed push. His encouragement was priceless, and it spurred me to send my resume to three different WordPress-related companies. To my delight and relief, I received a response from one of them.</p>



<p>From those early days in the cyber café to securing a position at rtCamp, my journey has been anything but ordinary. In light of my experiences and the passion I developed from my early encounters with technology, I secured a position as a WordPress developer at rtCamp in February 2021. This was a significant milestone for me, especially recalling my days without a computer in my village and the hours spent in cyber cafes learning the complexities of the digital world. The journey to this point was challenging, especially since I navigated it largely on my own, without a mentor or assistance from anyone./</p>



<h2 class="kt-adv-heading5985_0a7790-86 wp-block-kadence-advancedheading">Because Of WordPress&#8230;</h2>



<p>Now, working full-time with WordPress, not only am I able to comfortably cover my bills, but I can also provide for my family. </p>



<blockquote class="wp-block-quote">
<p>Most crucially, it has enabled me to fund my brother’s necessary neurological treatments. </p>
</blockquote>



<p>I’m delighted to share that he has successfully recuperated and no longer requires medication.</p>



<p>Throughout this path, I&#8217;ve faced countless challenges, sleepless nights, and stress. Yet, one truth remains clear: moving forward, no matter the obstacle. Failures are just milestones, not endpoints. With perseverance, success is not just a destination but a beautiful journey. If you’re facing doubts about your abilities, remember, we all start somewhere. It’s the perseverance that counts.</p>
<p>The post <a href="https://heropress.com/essays/from-sci-fi-dreams-to-software-reality/">From Sci-fi Dreams to Software Reality</a> appeared first on <a href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 01 Nov 2023 00: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:11:"Tremi Dkhar";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:37:"WPTavern: WooCommerce Rebrands as Woo";s: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=150841";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/woocommerce-rebrands-as-woo";s: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:2569:"<p>WooCommerce is <a href="https://woo.com/posts/say-hello-to-woo-com/">rebranding</a>  to &#8220;Woo,&#8221; a shorter, more playful version of the company name that many customers are already using.  <a href="https://wptavern.com/automattic-acquires-woocommerce">Automattic acquired WooCommerce</a> in 2015, along with WooThemes. The open source commerce platform now powers more than 4.4 million live websites, including 33% of the top 1 million online stores.</p>



<p>The rebranding extends to the Woo Marketplace, WooExperts program, and all other aspects of the Woo experience. It also includes a migration of WooCommerce.com to the <a href="https://woo.com/">woo.com</a> domain.</p>



<p>&#8220;&#8216;Woo&#8217; is how many loyal customers have referred to us for years. And now we’re leaning into that name for our company and brand,&#8221; Woo VP of Creative and Communications David Callaway said. &#8220;It’s a fun, punchy name that shows how excited we are to empower success for merchants and developers. Switching to Woo.com is part of this larger strategy.</p>



<p>&#8220;The move to Woo also allows us to standardize and streamline the names of our products and services. For example, we recently renamed WooCommerce Payments to WooPayments, and we’re gradually changing other product names to support this simplified naming system and better connect our core software, extensions, and programs.&#8221;</p>



<p>Callaway also noted that while Woo is how they refer to the brand and company, WooCommerce is the open-source e-commerce platform for WordPress, Woo&#8217;s core product. </p>



<p>Woo Express is another recently launched product that already bears the shorter name. During the <a href="https://wptavern.com/state-of-the-woo-2023-woocommerce-highlights-ai-powered-future-and-continued-core-blockification">2023 State of the Woo</a>, delivered at WooSesh, the team highlighted a few milestones for Woo Express, the company&#8217;s all-in-one Woo plan hosted on WordPress.com&#8217;s infrastructure. It launched in 2023 as what the team described as “Woo’s biggest bet ever.” Free trials began in April 2023 and by July 2023, Woo Express had more than 1,000 customers. It features a new onboarding flow and store personlization experience for merchants, with a setup guide and recommendation engine powered by an AI-driven assistant.</p>



<p>Woo customers will not be affected by the name change, although merchants may see a note about it in their dashboard or emails. No action is required from store owners.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 31 Oct 2023 12:51:14 +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: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:44:"Do The Woo Community: Do the … Woo dot Com";s: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=77718";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:39:"https://dothewoo.io/do-the-woo-dot-com/";s: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:335:"<p>Inside Woo. Today the WooCommerce site becomes Woo.com as a strategic part of their branding and product line. </p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/do-the-woo-dot-com/">Do the &#8230; Woo dot Com</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 31 Oct 2023 12:12:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:58:"Do The Woo Community: Do the Woo Day 1 Recap, WooSesh 2023";s: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=77694";s: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://dothewoo.io/do-the-woo-day-1-recap-woosesh-2023/";s: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:372:"<p>Day one started with State of the Woo, conversations on open source and hosting, scalable ecommerce and website security.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/do-the-woo-day-1-recap-woosesh-2023/">Do the Woo Day 1 Recap, WooSesh 2023</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 31 Oct 2023 10:54: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: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:65:"WPTavern: WP Data Dashboard Tracks WordPress.org Themes Ecosystem";s: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=150809";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://wptavern.com/wp-data-dashboard-tracks-wordpress-org-themes-ecosystem";s: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:7244:"<p>Munich-based digital agency owner Hendrik Luehrsen has been <a href="https://docs.google.com/spreadsheets/d/11X38e9w86XcgT4tybqfjKhrL0PIbDlIsUEJwLiKtJ7Q/edit#gid=931695972">tracking the usage of themes with the FSE tag</a> (block themes) using a spreadsheet that pulls in data from the WordPress.org API. Wrangling the data in a spreadsheet became too cumbersome, so Luehrsen launched <a href="https://www.wp-data-dashboard.com/">WP Data Dashboard</a> over the weekend as a &#8220;centralized hub for exploring, analyzing, and visualizing data across the WordPress landscape.&#8221;</p>



<p>The new website is currently tracking 6,017 themes hosted on WordPress.org with 250 snapshots. It offers stats and data-based insights for those interested in getting a bird&#8217;s-eye view on themes hosted in the official directory.</p>



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



<img width="1280" height="684" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/image-4.png" alt="" class="wp-image-150818" />



<p>&#8220;Right now, the WP Data Dashboard has one main function: It crawls the WordPress Theme Repo (API) and crunches the numbers to identify trends,&#8221; Luehrsen said. &#8220;With the data stored in my own database, I can analyze and combine it in exciting new ways.&#8221;</p>



<p>WP Data Dashboard has two unique stats that are interpretations of the data available. The first is a &#8220;Usage Score,&#8221; which is calculated based on a theme&#8217;s active installs vs. total downloads:</p>



<blockquote class="wp-block-quote">
<p>A high score indicates a theme that not only has been downloaded frequently but also remains actively installed on many sites. The score undergoes a significant decay if the proportion of active installs to downloads is low, indicating that while the theme might be frequently downloaded, it&#8217;s not retained by users. This metric provides insight into both the initial appeal of a theme and its lasting utility to users.</p>
</blockquote>



<p>The second unique stat is a &#8220;Diversity Score,&#8221; which compares the downloads of a single theme author to the overall theme directory (or a tag) and scales that value from 0 to 100:</p>



<blockquote class="wp-block-quote">
<p>A high score indicates that downloads are spread across many authors, suggesting a diverse and competitive marketplace. On the other hand, a low score suggests that a few authors dominate the downloads, indicating less diversity. This metric provides insight into the variety of theme offerings and the balance of power in the theme marketplace.</p>
</blockquote>



<p>The Usage Scores can be seen on the <a href="https://www.wp-data-dashboard.com/themes/list">List</a> page, which is an index of all the themes, as well as on the <a href="https://www.wp-data-dashboard.com/themes/tags/">Tag</a> pages.  </p>



<img width="739" height="575" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/image-5.png" alt="" class="wp-image-150825" />



<p>The Diversity Score is only displayed on the <a href="https://www.wp-data-dashboard.com/themes/stats/">Stats</a> page as a percentage representing the entire WordPress.org ecosystem. The Diversity score goes up when the stats are calculated without the default themes, which get a large number of downloads from the same &#8220;WordPress.org&#8221; author every year.</p>



<img width="1057" height="808" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/image-6.png" alt="" class="wp-image-150826" />



<p>In a <a href="https://twitter.com/hluehrsen/status/1718689888848023568">thread on X</a>, Luehrsen highlighted a few data points he has extracted so far from the dashboard. </p>



<p>&#8220;Fun fact: Did you know that the most downloaded themes ever are Twenty Seventeen, Twenty Fifteen, and Astra?&#8221; he said. &#8220;Each has crossed over 10 million downloads! But only Astra managed to retain its users and remains today as one of the most widely used themes.</p>



<p>&#8220;What&#8217;s somewhat surprising is the decline in downloads for the newer default themes. While Twenty-Twenty garnered over 8 million downloads, Twenty Twenty-One managed only 6 million, and Twenty Twenty-Two a mere 3 million.&#8221;</p>



<p>This may be related to the <a href="https://wptavern.com/contentious-review-process-leads-ollie-theme-to-remove-innovative-onboarding-features-amid-stagnating-block-theme-adoption">slow adoption</a> of block themes, which still <a href="https://docs.google.com/spreadsheets/d/11X38e9w86XcgT4tybqfjKhrL0PIbDlIsUEJwLiKtJ7Q/edit#gid=931695972">appears to be stagnating</a> at the end of October. The number of block theme active installs declined from August to September, but is now inching its way back up to previous numbers.  </p>



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



<img width="1138" height="283" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/image-7.png" alt="" class="wp-image-150828" />



<p>&#8220;Did you know that only 2% of overall theme downloads come from themes tagged as &#8216;<a href="https://www.wp-data-dashboard.com/themes/tag/full-site-editing">Full Site Editing</a>&#8216;?&#8221; Luehrsen said. &#8220;Given that they&#8217;re relatively new, it&#8217;s not too surprising!&#8221;</p>



<p>When asked if he has considered trying to include numbers for themes like Elementor and Divi, which make up a large segment of the commercial theme market, Luehrsen said he would like to include external data but the compatibility of that data would be very limited, which in turn limits comparability with WordPress.org-hosted themes.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Have you considered trying to include numbers for themes like Elementor and Divi? At the very least using resources such as BuiltWith? Elementor’s are eye opening. Absolutely dwarfs everything. Divi’s also higher than any on that list. The fragmentation is huge.</p>&mdash; Carl Hancock <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f680.png" alt="🚀" class="wp-smiley" /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1e8-1f1f7.png" alt="🇨🇷" class="wp-smiley" /> (@carlhancock) <a href="https://twitter.com/carlhancock/status/1718762077156757510?ref_src=twsrc%5Etfw">October 29, 2023</a></blockquote>
</div>



<p>The WP Data Dashboard is a useful way to track trends in WordPress.org themes over time, and the site appears primed to add data for plugins at a future date. It would be even more helpful if Luehrsen could make some of the calculated data available for visitors at a glance, such as 2% of overall theme downloads coming from <a href="https://www.wp-data-dashboard.com/themes/tag/full-site-editing">Full Site Editing</a> tagged themes. There are a lot of ways this data could be visualized with graphs and charts in the future, as the database adds more information over time. </p>



<p>The project is <a href="https://github.com/luehrsenheinrich/wp-data-dashboard">hosted on GitHub</a> under a GPL license, so anyone can dig deeper into the code to see how it works or submit contributions to extend its capabilities.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 30 Oct 2023 20:30: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:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:15;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:63:"WordPress.org blog: WP Briefing: Episode 65: Little Sun Success";s: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=16227";s: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:65:"https://wordpress.org/news/2023/10/episode-65-little-sun-success/";s: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:21522:"<p>Join WordPress Executive Director Josepha Haden Chomphosy as she looks at a recent WordPress success story, the clean energy solution Little Sun, and learns about their WordPress story.</p>



<p><em><strong>Have a question you&#8217;d like answered? You can submit them to&nbsp;<a href="mailto:wpbriefing@wordpress.org">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>



<h2 class="wp-block-heading">Credits</h2>



<p>Host:&nbsp;<a href="https://profiles.wordpress.org/chanthaboune/">Josepha Haden Chomphosy</a><br />Special Guest: Romane Guégan<br />Special Guest: Ashley Mrozek <br />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/bjmcsherry/">Brett McSherry</a><br />Song: Fearless First by Kevin MacLeod</p>



<h2 class="wp-block-heading">Show Notes</h2>



<ul>
<li>Website: <a href="https://littlesun.org/">Little Sun</a></li>



<li><strong>Small List of Big Things</strong>
<ul>
<li><a href="https://wordpress.org/news/2023/10/state-of-the-word-2023/" target="_blank" rel="noreferrer noopener">State of the Word</a> &#8211; This year&#8217;s annual keynote, State of the Word, will be on December 11. Save the date to hear the WordPress project&#8217;s co-founder, <a href="https://ma.tt/" target="_blank" rel="noreferrer noopener">Matt Mullenweg</a>, share reflections on the project&#8217;s progress and aspirations for the future of open source.</li>



<li>Celebrating 10,000 Photos in the <a href="https://wordpress.org/photos/">WordPress Photo Directory</a> &#8211; On October 11, the 10,000th photo was approved! <a href="https://make.wordpress.org/photos/" target="_blank" rel="noreferrer noopener">The Photo Team</a> is one of the newest ways to contribute to the WordPress open source project. </li>



<li><a href="https://make.wordpress.org/community/2023/10/18/community-team-training-11-using-the-translate-live-tool/" target="_blank" rel="noreferrer noopener">Community Team Training #11: Using the Translate Live tool</a>&nbsp;&#8211; Uncover the potential of the &#8220;Translate Live&#8221; tool, which is ideal for presenting at local meetups to engage and onboard new translators for your native language. If you&#8217;re organizing a WordCamp, consider introducing this tool during your Contributor Day.</li>



<li><a href="https://wordpress.org/news/2023/10/a-new-wordpress-showcase/" target="_blank" rel="noreferrer noopener">A New WordPress Showcase</a>&nbsp;&#8211; The&nbsp;journey to update&nbsp;<a href="https://wordpress.org/" target="_blank" rel="noreferrer noopener">WordPress.org</a>&nbsp;continues with the launch of a new&nbsp;<a href="https://wordpress.org/showcase/" target="_blank" rel="noreferrer noopener">Showcase</a>&nbsp;design. The Showcase is a natural starting point for visitors arriving on&nbsp;WordPress.org, and it both inspires creativity and demonstrates what&#8217;s possible with WordPress.</li>
</ul>
</li>
</ul>



<h2 class="wp-block-heading">Transcript</h2>



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



<p>[00:00:00] <strong>Josepha:</strong> Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Josepha Haden Chomphosy. Here we go.</p>



<p>[00:00:28] (Intro music)&nbsp;</p>



<p>[00:00:40] <strong>Josepha:</strong> Today, I&#8217;ve got a special guest with me. I have here a couple of folks from Little Sun, a nonprofit organization that recently moved its entire online presence to WordPress. And we&#8217;re talking everything from their mission statement and donations all the way to their blog and shop.</p>



<p>Welcome both to the WordPress Briefing.&nbsp;</p>



<p>[00:00:59] <strong>Ashley:</strong> Thank you.</p>



<p>[00:01:00] <strong>Romane:</strong> Thank you.&nbsp;</p>



<p>[00:01:01] <strong>Josepha:</strong> We have with us Little Sun today. Can you start by introducing yourselves and your organization? Just tell us a little bit about what you all do.&nbsp;</p>



<p>[00:01:08] <strong>Romane:</strong> Hi, my name is Romane Guégan. I&#8217;m a Senior Press and Communications Manager at Little Sun.&nbsp;</p>



<p>[00:01:14] <strong>Ashley:</strong> And I am Ashley Mrozek. I&#8217;m the Senior Digital Manager.&nbsp;</p>



<p>[00:01:17] <strong>Josepha:</strong> So what does Little Sun do for the folks who are listening and maybe don&#8217;t know about it yet?&nbsp;</p>



<p>[00:01:22] <strong>Romane:</strong> Little Sun brings full power and light to communities that live off the grid, with the focus on sub-Saharan Africa because most of the people who lack access to electricity and need them. And we also inspire people to take climate action globally.&nbsp;</p>



<p>[00:01:39] <strong>Ashley:</strong> So access to solar energy helps kids who don&#8217;t have electricity and study at night. They can complete their homework at night. If their schools are in a more rural area, they will have a light to kind of guide them back home.</p>



<p>We also work on a lot of electric vocation projects and hospitals. So we&#8217;re, we&#8217;re kind of supporting labors that are, are taking place in the evening, after the sun goes down, among other things.&nbsp;</p>



<p>[00:02:07] <strong>Josepha:</strong> Yeah. It&#8217;s, I, I think that that is one of the things that folks, probably most of my listeners, probably take for granted, like the easy access to light. And as we all know, the sun is around a lot. And so that is one of our most readily available resources other than potentially wind power. But I think that that is a great mission. And I really think that that&#8217;s wonderful work that y&#8217;all are doing.</p>



<p>So, is there a particular reason that you focus on sub-Saharan Africa? Is that where you find a majority of people who don&#8217;t have access to that kind of resource are?&nbsp;</p>



<p>[00:02:43] <strong>Romane:</strong> Yeah. 70% of those people actually need in sub-Saharan Africa, where solar is actually a viable source of energy. Actually, it&#8217;s only 1% of solar, of the solar capital of the generation when we actually deliver solar energy there because there is so much potential.</p>



<p>[00:03:04] <strong>Josepha:</strong> That&#8217;s amazing. So you said that you all were funded in 2012. I imagine that your business has evolved over time. So, obviously, you all are WordPress users. That&#8217;s why we have you here with us today. But before we get into the questions about WordPress itself. Why don&#8217;t you tell us a bit about how your business needs evolved over time and how you wound up needing a solution that did use WordPress?</p>



<p>[00:03:31] <strong>Ashley:</strong> So I would say our focus and kind of the different initiatives that we&#8217;ve taken on since 2012 have shifted a lot based on various reasons, where our donors are, where we&#8217;ve kind of found the most need, and where we can be the most impactful.</p>



<p>And I think as we go into those new geographies, our online presence has become more and more important.&nbsp;</p>



<p>[00:03:55] <strong>Josepha:</strong> So, before you all switched to WordPress, I understand that you had several sites that you had to merge into one. And so I assume that as you evolved the business and your focus has changed, you realized you needed something a bit more streamlined. So, how was that transition, that migration from a lot of different sites to one big site?&nbsp;</p>



<p>[00:04:17] <strong>Romane:</strong> Yeah, because we started as a global project. And then, with the time, we evolved, actually also getting new donations. And in the past, we used to have one website where we have our webshop and our mission, our vision, all of our project descriptions.</p>



<p>But then we had another website only for the foundation. And then you had another foundation in the U.S. So it was the question, okay, how do we put everything together? So we actually switched from littlesun.com to littlesun.org with WordPress, and it was amazing to see how we managed with the team to create an ecosystem approach, including impact, but also sales, and fundraising.&nbsp;</p>



<p>[00:05:02] <strong>Josepha:</strong> That was a big footprint that you all had, and you kind of consolidated it into one. And for all of our folks listening on the podcast, I&#8217;m going to include some links, not only to their site but then also to a few other things that we&#8217;ve mentioned in here today. So, since you made that change, how has it, how has that impacted the way that you all work with your site or with your online presence?</p>



<p>[00:05:27] <strong>Ashley:</strong> Yeah, I think using WordPress and having access to WordPress has been hugely valuable for us. We&#8217;re a small team, we&#8217;re a nonprofit, so it is pretty scrappy. Everyone is kind of doing a lot of different things. We don&#8217;t have a dedicated development team. And so being able to easily customize our pages and create new landing pages or make adjustments on the site without that development help has been valuable.</p>



<p>[00:05:55] <strong>Josepha:</strong> Yeah, so you don&#8217;t have a developer team now. Did you have a developer team when you had all the sites?&nbsp;</p>



<p>[00:06:01] <strong>Romane:</strong> We just still work with freelancers. </p>



<p>[00:06:03] <strong>Josepha:</strong> Okay, yeah. I am also not a developer, for what it&#8217;s worth, and have been working with nonprofits for a while. And I understand that problem where you have all these things you need to do and want to do, but there are also things you absolutely have to focus on in order to make your mission possible and your vision come true.</p>



<p>[00:06:23] <strong>Ashley:</strong> Yeah, and I think, I think WordPress has given us a lot more, like a lot more flexibility to kind of produce new content quickly. And because of that, it&#8217;s just been a lot more efficient, too, for us, you know.&nbsp;</p>



<p>[00:06:38] <strong>Josepha:</strong> And you all are using Blocks? Are you, like, the best Block builders?</p>



<p>[00:06:42] <strong>Romane:</strong> Yeah, I love Blocks.&nbsp;</p>



<p>[00:06:43] <strong>Josepha:</strong> Blocks are a fairly new innovation for the history of WordPress. WordPress has been around for 20 years, so we&#8217;re a nice, mature project. And we&#8217;ve really only had blocks as a functional part of the CMS for probably the last five or so. We&#8217;ve been working on the project a little bit longer. And it has been fascinating to me, like, in my own work that I have done with WordPress, kind of outside of my work with the project, to see, like, how much autonomy you get to have back as somebody who is not a developer, maybe isn&#8217;t a designer, but you do know exactly what you need to have on your site today, right?</p>



<p>And having to stop and find a freelancer or stop and find some set of developers who can make those changes. For me, when I was specifically working on nonprofit stuff. That was always kind of a moment where I was like, well, I guess I&#8217;ll just go to Facebook and put that on there or something because I was faster than trying to find someone to come help you. And so, I&#8217;m so glad you love the block.</p>



<p>[00:07:48] <strong>Ashley:</strong> We&#8217;ve created many a landing page.&nbsp;</p>



<p>[00:07:50] <strong>Josepha:</strong> Also, your site is adorable, and your brand is adorable, in case no one&#8217;s mentioned that lately. Super cute. Super cute.</p>



<p>[00:07:58] <strong>Josepha:</strong> So, we&#8217;ve talked about how you kind of took a bunch of stuff and made it into one big thing and how that&#8217;s been easier for you all to manage it. But from the standpoint of just, like, somebody who&#8217;s running a nonprofit, someone who&#8217;s running an organization, how has that transition been for your team? I know you said you don&#8217;t have a huge team, but was the move toward WordPress a net benefit over time, or was it immediately beneficial? Like, how has that been for your team? </p>



<p>[00:08:27] <strong>Romane:</strong> So what&#8217;s interesting actually is that we have a team that is spread also all over the world. And so we have teams in Berlin and in U.S., and New York. In Zambia, too. What was really interesting was how people identify to the new website because now we have to really think, okay, what is the content we want people to see, but also we want our critics to see. And so it kind of unified all of our content at Little Sun. And it was much more like much easier to understand afterwards. </p>



<p>[00:09:03] <strong>Josepha:</strong> Yeah.&nbsp;</p>



<p>[00:09:04] <strong>Romane:</strong> And it was because we also work at the intersection of creative communications, impacts, fundraising, technology, and to be able to put everything and have it on the front. And then have the stories to tell the stories from sub-Saharan Africa, from universities who got either a Little Sun lamps or solar systems, and then we have the donation page, so basically everything could be integrated in a super easy way, and it could target different audiences easily, either it&#8217;s someone who wants to partner with us, or a donor, or just someone who wants to be part of our solar training.</p>



<p>[00:09:46] <strong>Josepha:</strong> Yeah, and I mean, I think that no one will be surprised to hear that if you have multiple things that you have to get everybody to, it really increases the amount of marketing that you have to accomplish, rather than having one place for everyone to go too, and they can see everything that they might want once they arrive. So, that&#8217;s wonderful.</p>



<p>[00:10:06] <strong>Ashley:</strong> I think I was just going to say, or kind of echo what Romane said about the fact that we have so many different audiences, we have partners, we have donors, we have people who are just coming to learn about solar energy, or who are interested in purchasing a lamp. I think prior to this, it was a little bit confusing for those different audiences to kind of navigate to where they were intended to go to on the site, and now it&#8217;s much more cohesive. And we often hear that from people where it&#8217;s like, it&#8217;s quite easy to, to kind to find what they need to find on the site.&nbsp;</p>



<p>[00:10:39] <strong>Josepha:</strong> I define the WordPress community as anyone who is using WordPress, regardless of whether they know it or not. And so you all, in my mind, are part of the WordPress Community. And I just wondered if being part of that community has changed your approach to the way that you manage your content online or the way that you have chosen work with your business as like an online entity that also does on-the-ground, in-person thing?</p>



<p>[00:11:06] <strong>Ashley:</strong> I think definitely. I think we&#8217;re kind of going back to what I said before. I think we&#8217;re much more efficient now. I think in the past, it&#8217;s the idea of, like, well, getting this web page live or publishing this is going to be, you know, we have to think about a huge timeline, that&#8217;s, is going to require a lot of resourcing, a lot of different types of expertise and people, and everything now feels like something that we can, we can launch pretty immediately, which is really wonderful too.</p>



<p>I would also say just like being a part of the WordPress community too. It&#8217;s the sort of support that we&#8217;ve gotten from your team. It&#8217;s always really tailored. And I think as a nonprofit working with a, like, a much bigger business, you can be apprehensive sometimes, feeling like you won&#8217;t really get that personalized support.&nbsp;</p>



<p>And I think that&#8217;s something that&#8217;s been so nice with WordPress. Is really feeling like the people we&#8217;re working with are understanding our business and taking the time to understand our needs. And I think that makes us think differently about our online presence as well because then we feel like we have that additional support, which is great.</p>



<p>[00:12:12] <strong>Josepha:</strong> I&#8217;m always a fan of hearing that people who are passionate about WordPress are also passionate about helping others with WordPress. That&#8217;s one of my favorite things about us. That&#8217;s not true. I have like 25 favorite things about us. And so I need to stop saying that I have one favorite, but I never will.</p>



<p>Okay, well, do you all have any last thoughts that you just want to share with me or podcast listeners that we have?&nbsp;</p>



<p>[00:12:36] <strong>Ashley:</strong> Yeah, I think the, the plugins and integrations have been really useful for us. I think it can be really intimidating to bring on, like, a new tech solution or tool and feel like everything that you are already working with or have is going to become outdated or obsolete in some way. And I think it&#8217;s just been really nice to work with WordPress and have all of those transitions be really seamless for everything to connect really well. Yeah, I think that&#8217;s been. That&#8217;s hugely helpful too.&nbsp;</p>



<p>[00:13:07] <strong>Josepha:</strong> So, was that part of the decision-making process? Like, do I know that this software will be around in the future so that you&#8217;re making an investment in the site now and know that it&#8217;s going to hang around now you can find people help? Like, was that part of the decision-making process?</p>



<p>[00:13:21] <strong>Ashley:</strong> I think so. I mean, I guess I wasn&#8217;t completely around during the time, but I would say, like, that&#8217;s definitely something that we&#8217;re considering in any kind of tech that we&#8217;re thinking about is it can require so much work to, to kind of bring something on with such a small team. So we want to ensure that, yeah, it&#8217;s going to last, it has longevity, and it&#8217;s going to work with the tools that we already have. So I think all of that is really important for sure.&nbsp;</p>



<p>[00:13:48] <strong>Josepha:</strong> Well, thank you both so much for joining me. Like I said, we&#8217;ll have a link to littlesun.org in the notes so that you all can learn more about their project and see their beautiful site with their beautiful little solar sunflowers.</p>



<p>Thank you both for being with me today.&nbsp;</p>



<p>[00:14:04] <strong>Romane:</strong> Thank you so much.&nbsp;</p>



<p>[00:14:05] <strong>Ashley:</strong> Thank you so much for having us.</p>



<p>[00:14:07] (Music interlude)</p>



<p>[00:14:11] <strong>Josepha:</strong> What a wonderful organization. I&#8217;m so glad that they found WordPress and that it works for them. Let&#8217;s continue our tour today with the small list of big things.</p>



<p>Item number one, it&#8217;s time to save the date: December 11th, 2023, for this year&#8217;s State of the Word. State of the Word is the annual keynote address delivered by the WordPress Project co-founder Matt Mullenweg. Every year, the event shares reflections on the project&#8217;s progress and aspirations for the future of open source. And so, if that is something that you like to tune into, December 11th is your day.&nbsp;</p>



<p>Second thing on our list is that we are celebrating our 10,000th photo submission. So, on October 11th, the 10,000th photo was approved. The Photo Team is one of the newest ways to contribute to the WordPress open source project, and it feeds all of those photos into Openverse as well.</p>



<p>The third thing on our list today is that I want to tell you about a community team training module that just came out. It&#8217;s specifically about the Translate Live tool, and it is ideal for presenting at your local meetups to engage and onboard new translators for your native language. If you&#8217;re organizing a WordCamp, consider introducing this tool during your Contributor Day. I will leave a link for this in the show notes so that it is easy to find.&nbsp;</p>



<p>And item number four, the journey to update WordPress.org, continues with the launch of a new Showcase design. The Showcase is a natural starting point for a lot of visitors who are on WordPress.org. It inspires creativity and also demonstrates what&#8217;s possible with WordPress. So, stop on by there, it&#8217;s WordPress.org/showcase, and give it a bit of a look.</p>



<p>[00:15:58] <strong>Josepha:</strong> And that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. And don&#8217;t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You&#8217;ll get a friendly reminder whenever a new episode drops. And if you like what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard today, you can share those with me at wprebriefing@WordPress.org. </p>



<p>I&#8217;m your host, Josepha Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks. </p>



<p>[00:16:24] (Music outro)</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 30 Oct 2023 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:"Brett McSherry";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:100:"WPTavern: Gutenberg 16.9 Lets You Rename (Almost) Any Block, Adds Experimental Form and Input Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=150720";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:108:"https://wptavern.com/gutenberg-16-9-lets-you-rename-almost-any-block-adds-experimental-form-and-input-blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4201:"<p>Delivering on an <a href="https://github.com/WordPress/gutenberg/pull/42605#issuecomment-1475904839">highly-requested feature</a>, Gutenberg contributors have made it possible to rename almost any block in the List View. <a href="https://make.wordpress.org/core/2023/10/25/whats-new-in-gutenberg-16-9-25-october-2/">Version 16.9</a> was released this week with the new feature, which builds on <a href="https://make.wordpress.org/core/2023/09/28/whats-new-in-gutenberg-16-7-27-september/">Gutenberg 16.7</a>&#8216;s introduction of the ability to rename Group blocks.</p>



<p>It works in a similar way to naming Photoshop layers. Users can now open the list view, click on the ellipsis menu, select &#8220;Rename,&#8221; and enter a custom name.</p>



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



video credit: Gutenberg <a href="https://github.com/WordPress/gutenberg/pull/54426">PR #54426</a>



<p>&#8220;Allowing users to distinguish between blocks in the List View is becoming increasingly important as the scope of the Site Editor grows,&#8221; Automattic-sponsored contributor Dave Smith said in the original ticket proposing the feature for the Group block. &#8220;Given that all blocks are currently labelled by the block name (e.g. <code>Group</code>) it can be difficult to distinguish between them. This is especially important if your Groups represent distinct &#8216;sections&#8217; of a given page/template.&#8221;</p>



<p>Every block can be renamed with the exception of these four:</p>



<ul>
<li><code>core/block</code></li>



<li><code>core/template-part</code></li>



<li><code>core/pattern</code></li>



<li><code>core/navigation</code></li>
</ul>



<p>More renaming capabilities have been added in 16.9, including the ability to duplicate and rename patterns, as well as pattern categories.</p>



<p>This release <a href="https://github.com/WordPress/gutenberg/pull/44214">introduces new experimental form and inputs blocks</a> to allow building basic forms. It&#8217;s a feature that has taken many by surprise, as few would have predicted WordPress core would be adding form building. A very early version is available under Gutenberg > Experiments, under the &#8220;Form and input blocks&#8221; experiment setting.</p>



<p>&#8220;Why has there been no proactive outreach to the many developers of longstanding WordPress form solutions currently used by millions and millions of WordPress sites?&#8221; Gravity Forms co-founder Carl Hancock commented on the PR.</p>



<p>&#8220;It seems like proactive outreach to people who are experts in this space and who could do the most to help drive adoption (beyond comments/search/etc.) would have been a good thing. On many levels. Trying to get them on board with contributing, learning from their shared historical knowledge, and even more important of all&#8230; building on top of it and adopting it instead of introducing a point of more fragmentation.&#8221;</p>



<p>The forms feature is still in the very early stages of experimentation, and more information may be published to the November edition of &#8220;<a href="https://github.com/WordPress/developer-blog-content/issues/174">What&#8217;s New For Developers?</a>&#8220;</p>



<p>A few other notable highlights from this release include the following:</p>



<ul>
<li>New media categories: <a href="https://github.com/WordPress/gutenberg/pull/55236">Audio and Video</a> for organizing patterns by media type</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/55388">Sort pages by date</a> in the Site Editor&#8217;s page management screen</li>



<li>Command Palette now shows <a href="https://github.com/WordPress/gutenberg/issues/53539">block-specific commands as contextual suggestions</a></li>



<li>Experiments: <a href="https://github.com/WordPress/gutenberg/pull/55246">Added featured image field</a> to the page list</li>
</ul>



<p>Check out the release post for <a href="https://make.wordpress.org/core/2023/10/25/whats-new-in-gutenberg-16-9-25-october-2/">Gutenberg 16.9</a> to see the full changelog and more details on bug fixes and enhancements to performance, tooling, documentation, code quality, and accessibility. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 27 Oct 2023 22:00: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: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:71:"WPTavern: WordPress 6.4 Disables Attachment Pages for New Installations";s: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=150736";s: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://wptavern.com/wordpress-6-4-disables-attachment-pages-for-new-installations";s: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:4090:"<p>The upcoming 6.4 release, expected on November 7, will <a href="https://make.wordpress.org/core/2023/10/16/changes-to-attachment-pages/">disable attachment pages for new installations</a>. Up until now, WordPress automatically created attachment pages when users upload a file through the media upload system. It has been treated as a special post type that holds information about the file and each attachment is accessible under its own URL. SEO plugins have been redirecting attachment pages for years, as they rarely have any significant purpose.</p>



<p>&#8220;Until WordPress 6.4 was released, WordPress created attachment pages by default for every attachment uploaded,&#8221; WordPress contributor Joost de Valk said in the <a href="https://make.wordpress.org/core/2023/10/16/changes-to-attachment-pages/">dev note</a> for this <a href="https://core.trac.wordpress.org/ticket/57913">change</a>. &#8220;On the vast majority of sites, these attachment pages don’t add any meaningful information. They do, however, exist, get indexed by search engines, and sometimes even rank in search results, leading to bad results for users and site owners.&#8221;</p>



<p>There will be no changes to existing sites. They will continue to work as they always have, but new sites will have their attachment pages redirected to the attachment URL. Site admins who want to enable or disable attachment pages can use the new  <code>wp_attachment_pages_enabled</code> database option to control attachment pages&#8217; behavior.</p>



<p>There is no interface for changing whether a site disables attachment pages, which was somewhat controversial in the comments on the Trac <a href="https://core.trac.wordpress.org/ticket/57913">ticket</a> and the dev note.</p>



<p>&#8220;In light of the WordPress mantra &#8216;decisions, not options,&#8217; we’ve decided against making a setting for this,&#8221; de Valk said.</p>



<p>WordPress plugin developer Sybre Waaijer mades a case for <a href="https://make.wordpress.org/core/2023/10/16/changes-to-attachment-pages/#comment-45721">giving users an option</a> with an interface for toggling it on or off:</p>



<blockquote class="wp-block-quote">
<p>The problem with filtering options is that when another&nbsp;plugin&nbsp;provides the option toggle, the option&nbsp;filter&nbsp;will go against user expectations.</p>



<p>This is where “decisions, not options” becomes paradoxical because we’re now deciding to set an option while also not giving the option.</p>



<p>So, as plugins fill in this gap, then A) where will plugins put the option (likely on their custom page instead of options-media.php), and B) of the dozens of types of plugins that are in the market to juggle this, who will ultimately be in control of the option?</p>



<p>If it’s a filter, each plugin promises to set a toggle via a simple condition. But since it’s an option, plugins can add an option to filter an option and add an option to toggle the option. It’ll become a source of bugs because of the logical biconditionals (XNOR).</p>
</blockquote>



<p>While an interface isn&#8217;t in the cards for WordPress 6.4, and may never be back on the table for consideration, contributors are discussing the possibility of putting this in a core plugin.</p>



<p>&#8220;Should we not have a core plugin for re-enabling attachment pages on new sites?&#8221; Automattic-sponsored contributor Justin Tadlock said. &#8220;If there’s not going to be a UI for this, then a plugin that’s not buried in a Trac ticket would be ideal.&#8221;</p>



<p>de Valk agreed this would be a good idea to have a plugin that simply adds a setting to the Options -> Media page. Users likely will not understand the purpose of attachment pages unless they are looking to enable them for a specific, niche use case. A plugin like this would be useful for those who are not able to write the code to change attachment pages&#8217; behavior, as described in the <a href="https://make.wordpress.org/core/2023/10/16/changes-to-attachment-pages/">dev note</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 27 Oct 2023 17:42: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: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:51:"Do The Woo Community: Never Say Never with LinkedIn";s: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=77372";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"https://dothewoo.io/never-say-never-with-linkedin/";s: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:363:"<p>I have had many people in the WordPress and WooCommerce space ask me why I use and like LinkedIn. Here is my answer, finally.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/never-say-never-with-linkedin/">Never Say Never with LinkedIn</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 27 Oct 2023 09:54: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: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:74:"WPTavern: TaxoPress Adds New AI Integrations for Generating Taxonomy Terms";s: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=150700";s: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/taxopress-adds-new-ai-integrations-for-generating-taxonomy-terms";s: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:2498:"<p><a href="https://wordpress.org/plugins/simple-tags/">TaxoPress</a>, a plugin that allows users to create and manage Tags, Categories, and taxonomy terms, has joined a growing number of WordPress products using AI to innovate and enhance user experience. The latest release adds support for <a href="https://taxopress.com/tag/openai/">OpenAI</a> and <a href="https://taxopress.com/tag/ibm-watson/">IBM Watson</a> to auto-detect the best taxonomy terms for content.</p>



<p>&#8220;Honestly, I&#8217;m amazed how good these services are,&#8221; TaxoPress founder Steve Burge said. &#8220;For a long time, TaxoPress supported Dandelion and also LSEG / Refinitiv. These services are from a previous generation of AI tools. They could scan your content and suggest taxonomy terms. They support a couple of languages and have some options.</p>



<p>&#8220;In comparison, I&#8217;m blown away with the potential of these new services, particularly <a href="https://taxopress.com/tag/openai/">OpenAI</a>.&#8221;</p>



<p>This <a href="https://taxopress.com/taxopress-ai/">first version of TaxoPress AI</a> also introduces an updated metabox on the post editing screen with options to manage post terms, suggest existing terms, and connect to external AI services for scanning content and suggesting terms. The AI features are only available in <a href="https://taxopress.com/tag/taxopress-pro/">TaxoPress Pro</a>.</p>



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



<img width="2048" height="701" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/image-2.png" alt="" class="wp-image-150701" />



<p>The inclusion of OpenAI and IBM Watson <a href="https://taxopress.com/docs/comparing-the-ai-integrations/">expands support to nearly two dozen different languages</a>. Users can test different services to see which one produces the best terms for the content.</p>



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



<img width="1352" height="1154" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/image-3.png" alt="" class="wp-image-150703" />



<p>AI-based auto-tagging is an exciting new  way to enhance an otherwise conventional, established utility plugin. It introduces a bit of magic that produces better results with a far wider reach into the world&#8217;s languages.</p>



<p>Burge said TaxoPress will soon be adding more AI features for categorizing WordPress content and will focus on enabling more tools that are available through OpenAI and IBM Watson.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 27 Oct 2023 03:09: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: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:109:"Do The Woo Community: Navigating the WordPress Ecosystem and Marketing Automation Evolution with Rytis Lauris";s: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=77365";s: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:95:"https://dothewoo.io/navigating-wordpress-ecosystem-marketing-automation-evolution-rytis-lauris/";s: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:456:"<p>From political science to tech, Rytis Lauris, co-founder of Omnisend takes us on his product and WordPress journey.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/navigating-wordpress-ecosystem-marketing-automation-evolution-rytis-lauris/">Navigating the WordPress Ecosystem and Marketing Automation Evolution with Rytis Lauris</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 26 Oct 2023 09:01:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:55:"WordPress.org blog: WordPress 6.4’s PHP Compatibility";s: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=16235";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"https://wordpress.org/news/2023/10/wordpress-6-4s-php-compatibility/";s: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:2287:"<img width="2400" height="1350" src="https://i0.wp.com/wordpress.org/news/files/2023/10/WordPress-6.4s-PHP-comp.png?resize=2400%2C1350&ssl=1" alt="" class="wp-image-16236" />



<p>In an effort to keep the WordPress community up to date, this post provides an update on the PHP compatibility of the upcoming WordPress 6.4 release scheduled for November 7, 2023.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Recommended PHP version for WordPress 6.4</strong></h3>



<p>It’s recommended to use PHP 8.1 or 8.2 with this upcoming release. Please refer to the Hosting page for more detailed information, including <a href="https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/">a few known issues</a>.&nbsp;</p>



<p>Reach out to your hosting company to explore PHP upgrade options.</p>



<h3 class="wp-block-heading"><strong>Why does compatibility matter?</strong></h3>



<p>PHP is a programming language on which the WordPress code is based. This language runs on the server, and it is critical to keep it updated for security and functionality. Various teams within the WordPress open source project work to both test and fix any issues with new PHP versions so you can update with confidence that the WordPress core software is compatible.&nbsp;</p>



<p>Happy WordPress-ing!&nbsp;</p>



<p><em>Thank you to <a href="https://profiles.wordpress.org/annezazu/" class="mention"><span class="mentions-prefix">@</span>annezazu</a> <a href="https://profiles.wordpress.org/barry/" class="mention"><span class="mentions-prefix">@</span>barry</a> <a href="https://profiles.wordpress.org/ironprogrammer/" class="mention"><span class="mentions-prefix">@</span>ironprogrammer</a> <a href="https://profiles.wordpress.org/hellofromtonya/" class="mention"><span class="mentions-prefix">@</span>hellofromtonya</a> <a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a> <a href="https://profiles.wordpress.org/costdev/" class="mention"><span class="mentions-prefix">@</span>costdev</a> <a href="https://profiles.wordpress.org/javiercasares/" class="mention"><span class="mentions-prefix">@</span>javiercasares</a> for reviewing and contributing to the effort of this post.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 26 Oct 2023 08:40: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:15:"Chloe Bringmann";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:59:"WPTavern: WordPress 6.4. RC2 Released and Ready for Testing";s: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=150642";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wptavern.com/wordpress-6-4-rc2-released-and-ready-for-testing";s: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:4296:"<p><a href="https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-2/">WordPress 6.4 RC2</a> was released this week with more than 25 issues resolved since RC1. These include a few <a href="https://github.com/WordPress/gutenberg/pull/55481">cherry-picked commits</a> from the Gutenberg repository, additional <a href="https://core.trac.wordpress.org/query?status=closed&changetime=10%2F18%2F2023..10%2F24%2F2023&milestone=6.4&col=id&col=milestone&col=owner&col=type&col=priority&order=id">closed Trac tickets since RC 1</a>, and more than a dozen housekeeping <a href="https://github.com/WordPress/twentytwentyfour/commits/">commits for Twenty Twenty-Four</a>.</p>



<p>The <a href="https://make.wordpress.org/core/2023/10/23/wordpress-6-4-field-guide/">6.4 Field Guide</a> is now published with technical notes. It&#8217;s a lengthy document that collates all the <a href="https://make.wordpress.org/core/tag/dev-notes+6-4/">dev notes</a> for important changes that developers will want to review. A few examples include the following:</p>



<ul>
<li><a href="https://make.wordpress.org/core/2023/10/17/improvements-to-template-loading-in-wordpress-6-4/">Improvements to Template Loading in WordPress 6.4</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/17/new-option-functions-in-6-4/">New option functions in 6.4</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/18/image-loading-optimization-enhancements-in-6-4/">Image loading optimization enhancements in 6.4</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/21/updates-to-the-html-api-in-6-4/">Updates to the HTML API in 6.4</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/24/framework-for-storing-revisions-of-post-meta-in-6-4/">Framework for storing revisions of Post Meta in 6.4</a></li>
</ul>



<p>In addition to these important updates to core, WordPress 6.4 will roll six Gutenberg releases into the core – <a href="https://make.wordpress.org/core/2023/07/14/whats-new-in-gutenberg-16-2-12-july/">16.2</a>, <a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/">16.3</a>, <a href="https://make.wordpress.org/core/2023/08/10/whats-new-in-gutenberg-16-4-9-august/">16.4</a>, <a href="https://make.wordpress.org/core/2023/08/23/whats-new-in-gutenberg-16-5-23-august/">16.5</a>, <a href="https://make.wordpress.org/core/2023/09/06/whats-new-in-gutenberg-16-6-06-september/">16.6</a>, <a href="https://make.wordpress.org/core/2023/09/28/whats-new-in-gutenberg-16-7-27-september/">16.7</a>. </p>



<p>The Documentation team is looking for <a href="https://make.wordpress.org/docs/2023/10/25/call-for-volunteers-to-help-with-6-4-end-user-documentation/">volunteers to assist with updating and revising the End User Documentation</a> on HelpHub. A  <a href="https://github.com/orgs/WordPress/projects/141/views/2" target="_blank" rel="noreferrer noopener">6.4 project board</a> tracks the tasks in the Documentation repository on GitHub, and it has been sorted by priority. New documentation contributors are invited to join, and the onboarding process is well documented for getting started.</p>



<p>The emails have gone out to extension developers, who are encouraged to test against 6.4 and update the current &#8220;Tested up to&#8221; values for each extension.</p>



<p>One of the easiest ways to test the upcoming release is by using Playground: <a href="https://playground.wordpress.net/?wp=beta">https://playground.wordpress.net/?wp=beta</a>.  The Playground environment can be further customized for different storage types, PHP versions, and the WordPress version.</p>



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



<img width="2046" height="1294" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/Screen-Shot-2023-10-25-at-11.32.54-AM.png" alt="" class="wp-image-150646" />



<p>A comprehensive <a href="https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/">6.4 testing guide</a> has been published with video demonstrations of how each of the key new features should behave. This makes it easy for testers to know if something is not working the way it should. </p>



<p>WordPress 6.4 is now under two weeks away from its scheduled release day of November 7, 2023. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 25 Oct 2023 19:42: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: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: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:68:"WPTavern: #96 – Jake Goldman on Agency Mergers and AI in WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=150562";s: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://wptavern.com/podcast/96-jake-goldman-on-agency-mergers-and-ai-in-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:60281:"Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name 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 recent merger of 10up and Fueled, as well as some thoughts on how WordPress will adapt with AI.</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 podcasts 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. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.</p>



<p>So on the podcast today we have Jake Goldman. Jake is the president and founder of 10up, a digital agency that builds websites and tools for content creators, leveraging open platforms like WordPress.</p>



<p>We start the conversation with an exploration of the recent merger with 10up, Fueled and Insignia. For many years 10up has been one of the leading enterprise WordPress agencies. With a roster of well-known clients, Jake has grown the company from himself to hundreds of employees.</p>



<p>Whilst the journey has been exciting and challenging, Jake talks about some of the areas in which 10up has not been able to compete, and how the merger with Fueled will enable them to position themselves for projects which used to be out of reach. Fueled brings their experience of crafting mobile experiences, and Insignia brings their financial expertise, as well as the industry connections they have built up.</p>



<p>Jake shares how this new venture will continue to leverage WordPress as their CMS of choice. These new partners understand and support 10up&#8217;s commitments to contributing to WordPress. There are no plans to immediately alter the structure of either 10up or Fueled. It&#8217;s more about building an understanding of the capabilities of each partner, working towards a future in which the company grows into one entity over time.</p>



<p>We talk about the intentional pursuit of potential partners, and Jake reflects on the importance of cultural alignment and connections. He shares how his prior experience has shaped both his personal journey as a leader, and the success of 10up. And we explore the milestones, challenges, and key moments that have brought them to where they are today.</p>



<p>Towards the end of the podcast, we pivot to talk about the role of AI in the future of WordPress. It&#8217;s clear that AI is coming, and it&#8217;s coming rapidly. Any agency working with WordPress would find this topic hard to ignore. But what impact will it really have? Are we expecting entire websites to be built in seconds by just clicking a button?</p>



<p>Jake expresses his view that these tools are to be seen as accelerants, complementing human website development, rather than replacing it, particularly at the enterprise level. We delve into 10up&#8217;s ongoing exploration and experimentation with AI, discussing some of the tools they have freely released.</p>



<p>If you&#8217;re interested in how enterprise agencies grow or the future of AI with WordPress, this episode is for you.</p>



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



<p>And so, without further delay, I bring you Jake Goldman.</p>



<p>I am joined on the podcast today by Jake Goldman. Hello Jake.</p>



<p>[00:04:31] <strong>Jake Goldman:</strong> Hey!</p>



<p>[00:04:32] <strong>Nathan Wrigley:</strong> Very nice to have you on the podcast today. Really appreciate you joining us. Jake is joining us from 10up.</p>



<p>10up very recently had some really quite seismic news. In the WordPress community 10up is one of those companies that you have probably heard of. They&#8217;re an enterprise level agency, they deal with some of the largest projects in the WordPress space, and they had some news around a merger. So we&#8217;ll get into that in a little bit and we&#8217;ll also get into some AI topics probably towards the end.</p>



<p>Prior to that though Jake, I&#8217;ve just given a little bit of an introduction about where you work, but I&#8217;m curious about your backstory, particularly as regards WordPress, this is after all a WordPress podcast. So would you mind just giving us a little bit of your backstory. Where you fit into the WordPress ecosystem? What is the company that you work for and how did you set that up?</p>



<p>[00:05:22] <strong>Jake Goldman:</strong> Sure. I&#8217;ll see if I can do this concisely. I feel like there&#8217;s so much to the backstory. 10up today is a shop that I have run for twelve and a half years now, as we&#8217;ll talk about. Part of a larger organisation. We are a web agency and we have been very proudly advocates of open source, open technologies, WordPress is our tool of choice. We also very much believe apropos of open source and giving back to the web, and helping continue to make the web an open platform where people, you know don&#8217;t have to pay huge licensing fees to be involved, be able to make websites, be able to learn new technologies and new skills.</p>



<p>And we very much believe that as we have climbed up that ladder of an open web that we need to keep that ladder extended to the next generation. So we are also very large contributors to the project, we donate thousands of hours every year to open source. A large part of that goes to WordPress Core. Goes to a rich ecosystem of extensions that we contribute, that we think solve some hard problems, particularly in the enterprise, the kind of customers that we serve.</p>



<p>Before this new event, just as 10up we&#8217;ve been about 300 people. That is a company that has grown organically from 2011 when we were founded, with just me writing code and doing a little bit of UX, and doing all the business side of things and built it sort of brick by brick.</p>



<p>I got into WordPress circa 2007, 2008. I was working at a shop as many were at the time focused on commercial CMSs and closed platforms. We kind of wanted to diversify, saw the writing on the wall. Started exploring with different popular open platforms at the time that was WordPress. One of the partners in that company was focused on Drupal.</p>



<p>I saw a lot of potential in that platform that came, I thought, to pass over the next few years, and when it was time for me to go out on my own and start my own business, I was pretty determined that if I believed in an open web and wanted to see open technology thrive, that WordPress was a good horse to bet on. And so started 10up. Determined to become one of those agencies of record in the space. I guess the rest is history.</p>



<p>[00:07:02] <strong>Nathan Wrigley:</strong> Did you have any intuition back then that WordPress was, you spoke about it in terms of it being you know a good horse to back. Did you have any intuition that it was the horse to back? Or would you have been prepared at any moment to swap horses mid race you know had Drupal pushed ahead? Because I had all sorts of intuitions, many of them which turned out to be completely wrong in terms of Drupal and other open source platforms.</p>



<p>And eventually after WordPress became successful, I joined that ecosystem. But it sounds like you made a bit of a serendipitous choice. It was a bit of good luck possibly. And I wonder what your thoughts are around that.</p>



<p>[00:07:38] <strong>Jake Goldman:</strong> Yeah I mean there&#8217;s always an element of luck. I could have chosen never to look at WordPress, right? Or taken it seriously as a platform. I certainly thought I saw potential. I mean, you work in web from 1996 to 2007, you&#8217;ve tried and dabbled in lots of different technologies. I think it was, maybe this is the older man in me speaking now, but I think it was easier at the time to move between different technologies. There wasn&#8217;t so much friction trying new things, trying new platforms.</p>



<p>As somebody that&#8217;s very, that likes engineering, and likes tech, and likes the geeky side but also has a strong appreciation for user interface and making things easy and putting myself in the shoes of people that are actually just trying to publish something on a website. Actually trying to manage content, always wanting throughout my entire time in web to be able to like hand off a website, maintain it, but be able to hand off and have a delightful experience for those website owners to keep updating their website and managing the content on their website.</p>



<p>It was very clear to me even 2008, 2009, I think it was around the time of the first big UI change in WordPress, you know the menu on the left and still elements of that echos of that design today in WordPress. It was very clear to me that in terms of platforms that we&#8217;re creating really focused on, what is that website owner, what is that content publisher experience that WordPress was, I thought, just running circles around the other platforms?</p>



<p>So I saw a lot of potential. I was experimenting with even doing things that were custom post type like before there was really custom post types in core, and saw where the core project was heading in terms of adding more taxonomy support, adding more different content types and some of those fundamentals of a bigger CMS.</p>



<p>So I guess a bit lucky that I happened to be stumbling and playing and looking closer at the platform at the time, but I guess the short answer is yeah, I mean it was very palpable to my instincts that this thing was going to go places.</p>



<p>[00:09:11] <strong>Nathan Wrigley:</strong> If you were to look back over the time since 2011, that number of years, the ground will be littered with people who tried to do what you did, but didn&#8217;t quite make it. You know they endeavored to have an enterprise level agency, they wished to grow their agency. But for some people clearly that worked, you being one of them. For other people, perhaps it didn&#8217;t work out.</p>



<p>And I&#8217;m just wondering if you&#8217;ve got any intuitions as to what the key moments were in those years. If you look back and think, okay that was the moment, that was another moment, that was a third moment. What were the pivotal bits, the decisions that you made, the projects that you took up, which allowed you to become the sort of force that you are now?</p>



<p>[00:09:48] <strong>Jake Goldman:</strong> It&#8217;s a great question and, you know, I&#8217;ll be earnest, I never really look at the sort of long journey and arc as, it&#8217;s nice to think of it as like there was this moment and everything changed. But it wasn&#8217;t really like that. It was a brick by brick, year over year kind of effort. I mean when I look back at moments that I could call out, you know certainly when starting the company, I&#8217;m not sure if this is a moment so much as a story you know sort of a narrative about, I think why we were able to be successful.</p>



<p>But I&#8217;ve always emphasised that the trick to, I think, 10up&#8217;s success is that I did not descend out of the sky one day out of college and say I&#8217;m a business owner. Before I started 10up I spent over a decade working for other people, doing side consulting. There was a whole story before 10up started which was time in the industry, building connections, building a network, investing in relationships, learning from mentors about how to think about a budget, and a P and L, and what&#8217;s really involved in hiring people. Having the joy of hiring someone great and the torture of having to let people go before I ever started the company. Knowing how to put numbers together, had fantastic mentors.</p>



<p>If you want the honest answer, the real story of our success is, it was everything that happened before starting 10up. It was the relationships I was able to bring into that company, clients like side consulting projects I had been doing on the side for over a decade that I was able to bring in to the company.</p>



<p>I think there&#8217;s a lot of people today that sort of drop out of the sky and say you know my role in life is to be an entrepreneur and day one I&#8217;m starting a company and I just, I can&#8217;t imagine I would have been nearly as successful, 10up would have been nearly as successful as it was if I didn&#8217;t have that whole backstory.</p>



<p>I can point to some other moments, you know winning in the first year. Getting introductions vis-à-vis those connections to customers like TechCrunch that we still work with to this day, on their site that have obviously become very powerful items in your portfolio. I can point to bringing on strong leaders including our CEO who joined us in 2014, still with us today, John Eckman.</p>



<p>I think one other thing that has made 10up different than some companies in the space is I like to believe it is not a company that revolves around its founder&#8217;s ego. That I&#8217;ve always tried to build it with a mindset of, I want this thing to be much more than Jake Goldman. I want the brand to be 10up not Jake&#8217;s company. I could ramble on but I think, that&#8217;s probably what I would leave you with.</p>



<p>[00:11:51] <strong>Nathan Wrigley:</strong> Well thank you. The thing that we&#8217;re going to talk about from now is the joining of forces between 10up and a company which in the WordPress space maybe people haven&#8217;t heard about, and that is Fueled. We&#8217;ll talk about a piece which went on the 10up blog, I will link to it in the show notes. It&#8217;s called Fueled Up, 10up joins forces with Fueled Digital Media. And so that&#8217;s the direction of travel for the majority of the rest of the podcast.</p>



<p>But I&#8217;m just wondering, in that journey, was the endeavor always growth? Grow, grow, grow, make the agency bigger. And if that was the case, what kind of changed your, direction? Because it seems like you had a bit of an epiphany earlier in the year of 2023. The article paints a picture that you were working with Fueled and then just have this sudden realisation, actually do you know what they are like us. They do something different but their alignment, the sort of direction of travel, their ethics, and all of that seems to match very well.</p>



<p>And then all of a sudden, well I say sudden, probably months and months in the making, you announced that you&#8217;ve joined forces. So I just wonder, what changed about the company that suddenly made you think let&#8217;s do something different, let&#8217;s join with some other company?</p>



<p>[00:12:55] <strong>Jake Goldman:</strong> It&#8217;s a fantastic question and the reality is, I&#8217;ve written about this a little bit online, like my prior story. It was not a wake up one morning, my you know light bulb went off and the next day we closed the transaction kind of a thing. The reality is, I think we have to go all the way back to saying like, per my last remarks, I have always seen 10up as something that is, I want it to be much more than Jake Goldman Inc. That was always my vision.</p>



<p>If you think of me as an engineer at heart, I always sort of believe like the best thing you engineer is a thing that continues to live on and be used well beyond the time you spend on it, well beyond your focus on that project. And I&#8217;ve always felt the same way about a company, like the perfect business, the ideal company, the ideal team that you build.</p>



<p>There&#8217;s a world where you can someday step back and not be worried if I&#8217;m not in the room that this thing doesn&#8217;t keep succeeding, this team doesn&#8217;t keep thriving. That&#8217;s always been on my mind. It was on my mind when I think I surprised a lot of people, again, going all the way back to 2014, and hired a CEO that was not me into the company to help us build it. It&#8217;s always been on my mind as I built out different divisions and empowered strong leaders within the business.</p>



<p>I think there was a moment for me in the, you know the first few years of the 2020s, to me sort of peaking in 2022. Not sure intentionally but probably not accidentally after probably two or three of the most difficult and challenging years to be a business leader probably weighing on my mind as well. Any business leader who does not tell you there was a certain fatigue in 2020, 2021, 2022 is probably not being honest with you.</p>



<p>At the same time, more consciously I just felt like look, we&#8217;re about to break through $40 million in revenue, we think by the end of this year. We think we&#8217;re on a trajectory for 300 people at this company. I have been the overwhelming owner of the business, decision maker for you know, at that point for I guess 11 and a half years. And really felt like as we move forward this company needs to have more governance, a different kind of structure, a different kind of ownership that can A, help keep propelling it forward.</p>



<p>I&#8217;ve never run a company of that scale in size before. I think some of what you have to do to manage and invest in a company of that scale is a little bit different when you start to reach that kind of size. And I frankly want to make sure this company is taken care of in the event that I ever, you know I could get sick, I could get hit by a bus.</p>



<p>I don&#8217;t think the company even as it existed previously, would suddenly just disappear overnight by any means. But there was a certain amount of like legal structure, a certain amount of like ownership management, and share structure. A certain amount of where are the other highly experienced, growing companies of this size kind of leaders and investors that were missing.</p>



<p>And when I thought about I can go through the effort to do that on my own, think about like employee owned companies or think about how to completely restructure stock and legal formations. To be honest with you, when I started thinking about that, I was struggling to imagine being excited to get out of bed for the next two years focused on like legal apparatus, and being that different kind of owner of that larger company which just. You know so I guess I&#8217;m rambling a little bit to say like that mindset that I was in of I think we need something more in terms of governance, ownership, to a degree, diluting the degree to which it sort of sits on my lap as an owner.</p>



<p>Combine that with my sense that the next phase of growth is, I think, going to come from moving even further up market to being even more of a serious competitor to like the Deloitte Digitals and the Code and Theory&#8217;s of the world, the people that are not coming in saying you know we&#8217;re great WordPress integrators, or just great website makers but were true full digital experience shops.</p>



<p>I think those things kind of collided for me in a way that said maybe it&#8217;s time to look at M&amp;A. Maybe it&#8217;s time to look at who we can join forces with. And I&#8217;ll be transparent, we went on a very intentional journey, we had advisors in that process. It was you know help guide me through an exploration of you know who might be the kind of company that you can join forces with. And let&#8217;s not just wait for it to fall in my lap, or just go on this blind exercise and all the you know, all my copious spare time of hunting.</p>



<p>But be intentional about seeking who those partners would be. Spoke to a lot of different companies, had different sort of, I would say suitors, or even offers of which we walked away from. But as we got to know Fueled in particular and then started to do some projects together, and started to understand each other, it felt very clear to me that this was a unique and special fit.</p>



<p>[00:16:45] <strong>Nathan Wrigley:</strong> Okay so let&#8217;s talk a little bit about Fueled. So I&#8217;m curious to know, what is it about them that make that fit special? So presumably you went out and I&#8217;m obviously going to paraphrase the whole process, but there must&#8217;ve been a series of check boxes that needed to be checked. The company needs to behave in this way, it needs to have this, it needs to have this, we need to be going in this direction, whatever it may be.</p>



<p>I&#8217;m just wondering, why was it Fueled as opposed to all the other companies? And you can take that in whichever direction you like. It may have just been personnel, it may have been turnover, it may have been, I don&#8217;t know attitude, roster, anything you like.</p>



<p>[00:17:16] <strong>Jake Goldman:</strong> Yeah it&#8217;s definitely not just a one thing, but I have to say a lot of it sounds very non business like in a sense. But a lot of it was ineffable. A lot of it was just when you go and you meet with these different suitors, or these different potential partners, or companies that you could merge with. And you sit down in the room with them or you have, you know you start with the Zoom chat. I find myself sort of imagining okay, I&#8217;m in a boardroom in a hard time or a good time with them, a year from now, two years from now, how does that feel to me?</p>



<p>It&#8217;s a sort of cultural, does this feel natural? Does this feel like somebody that if I had to have hard conversations it wouldn&#8217;t be stilted, and more painful than it needs to be? Do I feel like I would be energised and sort of like an extroverted kind of way, like walk out of meetings and planning sessions more excited about what we&#8217;re doing, or would I feel a bit tired from that exercise?</p>



<p>And I&#8217;m trying to think how else to express it. It was just like when I sat down with them, when I met with them, when we actually worked on projects together and collaborated. It felt like if I had brought these people to, you know, if I just brought them to my team and said I just hired this person as a new key executive, or a new key director, or leader, everybody would have just said like you know great hire Jake, what an amazing fit for our culture.</p>



<p>And I think that was extraordinarily important to me. Yes, there were other boxes to check. The financial side of everything had to make sense. The legal apparatus had to make sense. They had to be in a, obviously, you know reasonably healthy condition as a business. There were things I did not want in terms of like kind of companies that I thought could like destroy what&#8217;s precious about 10up and its culture.</p>



<p>I could talk about all of those things, but at the end of the day when sort of settling down on that gut feeling of, is this a company that I want to be with, that I want to work with, that I want to join forces with? It was the checking of the boxes, different kind of skills, different kind of capabilities, all of those things.</p>



<p>But at the end of the day, a lot of it came down to these are good people that I would enjoy working with. I would look forward to going to a board meeting. I would look forward to going to an exec planning session. They will make me a better leader. They will make my team better. My team will enjoy collaborating with these people in ways that you know going through this journey and talking to so many companies, even before 2020 like we&#8217;ve been approached before, and we&#8217;ve had conversations with different companies.</p>



<p>You start to realise how precious that match is. We can all sort of like be in our bubbles. But really when you start to talk to a lot of these different companies and agencies, you really realise pretty quickly that there are a lot of companies, a lot of people who are doing fantastic work, impressive businesses, but just very different kind of mindsets, cultures, communication styles, ways of thinking about the world. So when you find someone that you actually go and sit down in the meeting and it&#8217;s like I could hire you, I wish we could do more projects together, that&#8217;s something you latch on to.</p>



<p>[00:19:39] <strong>Nathan Wrigley:</strong> Yeah what a great answer. I really enjoyed listening to that. The next thing I want to talk about is, how Fueled overlaps with you? So I&#8217;m imagining in my head a Venn diagram of two circles. And in the past, in the WordPress space, we&#8217;ve often seen one agency, for want of a better word, consume another agency. And it almost feels like the two circles are now completely overlapping. One is inside the other. So you can no longer see two circles. You just see one slightly bigger circle.</p>



<p>But it does seem as if with Fueled we&#8217;ve got a nicely fitting Venn diagram. There&#8217;s Fueled over here, there&#8217;s 10up over here, and there&#8217;s some elements of overlap but it&#8217;s not entire. The two circles are not colliding. And I&#8217;m just wondering, what it is that they do? What it is that you do? What&#8217;s the differentiators, and what is that lovely sweet spot in the middle where you both overlap?</p>



<p>[00:20:23] <strong>Jake Goldman:</strong> So I&#8217;ll start with the sweet spot in the middle. The sweet spot in the middle, to be a little highfalutin about it for a second, is like the desire to use technology, to use cutting edge innovative tech to create fantastic experiences for clients in an agency setting. It really is in some sense that crisp and that simple. We are a professional services business. We use online technologies to make great experiences for our customers.</p>



<p>Now to be a little less flippant and a little bit more specific about it, like where we have skill set overlap. Fundamentals of doing design systems, whether it&#8217;s on mobile for a product, whether it&#8217;s on a website. Those are not fundamentally different like technical skill sets that you use every single day. There is an overlap and some like you know Next.js, React kind of front end technologies. They do some web applications in addition to mobile. In fact probably a growing part of their business relatively speaking.</p>



<p>But when you get beyond the sort of like core common technologies and practices you use when you&#8217;re a creative agency, and expand out to okay, what do we actually work on day to day? There is a healthy, non overlapping parts of the circles, outside parts of the Venn circles. Which is to say like I would say that they are predominantly focused on what they are good at, what they are known for, what they have repute in, is doing product development in the sense of mobile applications. Some web applications, but not marketing websites and publishing websites. Not CMS driven experiences really. Like applications, you know e commerce kind of functionality. Think of some of the projects they work on where it&#8217;s really you know shopping and user intention driven.</p>



<p>10up is more on the website marketing, web publishing, web content creation. Again, we overlap a little bit, we&#8217;ve even done mobile apps in the past, but we are really strong in how to make a great website that can be put in the hands of those site owners, those site publishers with a strong content management system implementation behind it. And a major focus on content together. That&#8217;s media and publishing, or corporate newsrooms, or you know content marketing, or just flat out marketing websites and informational websites. When that was not something conversely that Fueled had really focused on or was good at.</p>



<p>And we both sort of you know looked at those two sides of the Venn diagram and sort of said, I bet we have a bunch of customers who could use the others services. And there&#8217;s a bunch of customers out there who don&#8217;t want a shop that sort of neatly fits in one bucket and is kind of stretching and reaching to have a compelling story about the other side.</p>



<p>[00:22:35] <strong>Nathan Wrigley:</strong> I don&#8217;t know exactly what the audience demographic is, but I&#8217;m sure there&#8217;ll be a lot of people who don&#8217;t work in enterprise agency land. And so this conversation is really interesting, and I am wondering if you&#8217;ve had to, probably this is the wrong word, but turn down work, or move away from work, or pivot away from work that, you simply as 10up, didn&#8217;t feel you would be doing the best job with. But now you feel, okay we can push forward with projects such as this in the future, because now it&#8217;s this bigger enterprise, it&#8217;s Fueled, it&#8217;s 10up, it&#8217;s whatever that&#8217;s going to be called in the future.</p>



<p>[00:23:06] <strong>Jake Goldman:</strong> Oh yeah for certain. I mean literally can think of projects over the last few years where we had great enterprise, large scale, huge spending customers who needed, just to say it plainly, in some cases needed a mobile application built, put out RFPs for that and probably would have, hoping I&#8217;m not being hubristic here, probably would have loved to work with us, at least would have taken very seriously a submission from 10up. Where we just felt like we would not meet qualifications, we&#8217;re not confident that we could do a good job, in a way that would not diminish our entire relationship with them.</p>



<p>It&#8217;s the more common scenario that I think about is where we are given opportunities to pitch business, we&#8217;re given opportunity, we have an introduction, we have a connection, and we just don&#8217;t quite compete in the right way in terms of coming across as having a real platform that you would describe as a full digital experience solution.</p>



<p>While it&#8217;s true that we have customers, we have business that I would say has been left on the table because we didn&#8217;t have these capabilities. What I&#8217;m more focused on is where do we not compete well for opportunities? Where do we not get invited into the room or just not last long in the conversation? Because to overstate melodramatically for a fact, we come across as a WordPress integrator implementation shop, not a full digital experience business.</p>



<p>[00:24:12] <strong>Nathan Wrigley:</strong> There&#8217;s a third circle in this Venn diagram which we haven&#8217;t mentioned so far and it&#8217;s a venture capital company called Insignia Capital. I confess I don&#8217;t know anything about Insignia Capital. So I&#8217;m just wondering, probably fairly quickly, I don&#8217;t know if you want to dwell on this, but I&#8217;m just wondering if you could explain how that fits in.</p>



<p>[00:24:29] <strong>Jake Goldman:</strong> Sure. So at the risk of splitting hairs for your audience they&#8217;re a private equity company which is a little bit different from venture capital. Probably not a very material difference for most of the people listening to this but it&#8217;s a little bit different. Sort of like, what are the returns they expect? How do they operate? Where do they get their funding? And so forth.</p>



<p>Still the same principle in terms of, I guess the short version would be that they are the money people. So the way that they fit, to try to make it concise, they joined forces with, made a massive investment in Fueled about one year ago. Which is to say they&#8217;re not the full ownership of Fueled. Fueled&#8217;s owners still hold a large share of that company, but they have controlling ownership, vis a vis putting a huge investment into Fueled.</p>



<p>And what Fueled, other than of course some opportunities for some liquidity for their owners wanted out of that, is a real partner who knows how to, from the investor side, has both connections, has both capital, has sort of financial and industry sophistication to help them build a bigger business together.</p>



<p>So to put it in plain terms, what Insignia wants to do is work with a platform, which for them that was Fueled as the initial partnership, the initial investment. To build a bigger, more valuable company that increases the value of the equity that they have in that business. The way that they do that oftentimes, like the strategy in professional and digital services is you do what&#8217;s called add ons.</p>



<p>So you bring in other companies into the fold, you attach them to that company and you end up with something that is much more valuable for a number of reasons. It&#8217;s higher revenue, but it&#8217;s also everything I just described about you have a you know, a shop that looks like a full digital services provider with CRM capability and sales force and CMS and mobile apps, is just a more valuable business than one that&#8217;s kind of pigeonholed in one of those spots.</p>



<p>So you can kind of make smart investments with investors that really raise the overall value of the business. Like 10up, I would say Fueled&#8217;s ownership really did not have the sort of the sophistication, appetite, capital to do that on their own. Which is why they partnered up with Insignia. Insignia has sort of the financial vehicle, all those things I described earlier in the conversation, where it&#8217;s what does it mean to restructure legally 10up to have multiple ownership, and to have shares and to have stock and to have investors with a lot of influence and connections in the space.</p>



<p>So long story short, they help us restructure to be able to join with Fueled, to be able to make one business out of these two companies. And that happens, in large part, by helping purchase a significant amount of 10up equity, so I am no longer the dominant controlling owner of 10up.</p>



<p>It&#8217;s a little muddy, and I guess like the short version of it is like they are the financial backers for this combined entity. They make it possible to restructure the business and combine into one through capital, and they also bring quite a bit of sophistication around how to build these platforms. They have connections with other companies that can be acquired, they have a lot of connections with very senior, influential people in the decision making space, in the agency space and in the B2B space. So it&#8217;s not that they just bring money, they also bring a lot of wisdom about how to build these larger companies as investors, advisors, board members with strong connections.</p>



<p>[00:27:12] <strong>Nathan Wrigley:</strong> Now that the ink is dry on the contracts and you&#8217;ve had a little bit of water flowing under the bridge, I&#8217;m just wondering if you can tell us how 10up particularly has changed? I know that your company is broadly distributed, and I just wondered, what is it that it&#8217;s going to look like if we can cast our eyes forward a year into the future? What are you endeavoring to create there? Is the idea that this one entity, everybody will be mixed? It will be a homogenous entity or will we have, broadly speaking, will we still have the WordPress side? What are you planning?</p>



<p>[00:27:42] <strong>Jake Goldman:</strong> So the first thing to say is when we get like sort of in the weeds of how it&#8217;s going to operate, and a question of like what has changed today. So far that is still a journey of discovery that we are on. That&#8217;s not BS, that is authentic. I can speak to what we all sort of I think share as like a heading and vision and ultimate destination, when you talk about the one, two, three years out.</p>



<p>But we don&#8217;t think that means like jumping in and month one, this is not like shifting around 17 different divisions and immediately restructuring in three months. No, we are learning from each other, we are still deep in the process of teams and project management, and design, and growth, and sales, and engineering. Sort of comparing notes, getting to understand each other better, getting more insight into each other&#8217;s businesses. Sharing leads, sharing opportunities that we think might be better fit to one team or the other. Sometimes sharing personnel where they&#8217;re skillsets overlap and one team or the other could use help.</p>



<p>But really operating essentially as two, continuing to operate as we did before the merger, as two strong partners with a bunch of research, discovery, integration, exploration going on in the background of the company.</p>



<p>In terms of where we are headed. Yes, our goal is ultimately not to be like there&#8217;s a 10up and there&#8217;s a Fueled out there competing in the agency space, and sometimes sharing opportunities. Our ultimate goal is to be a unified business, to have a clear, centralised governance. To be able to go to market as one entity, one brand and sell a story of not two different partners working together, but one fully integrated set of capabilities.</p>



<p>Now what that looks like again, there&#8217;s a lot to color in there that I just don&#8217;t have the answer for. I don&#8217;t even know that I have an answer, a definitive answer today for where like the brand question would even land. We might find ourselves in 12 months in a model that is still fairly divisional. Which is to say maybe more centralised leadership, centralised operations, more marketing and business development consolidation, but could still sort of like operate with divisions within the business.</p>



<p>One more focused on applications. One more focused on web and CMS. Could end up with some teams that are totally cross functional. The honest to god answer is that is what we are exploring and trying to work on with our teams and find the best path today. Better right than quickly is our point of view.</p>



<p>[00:29:35] <strong>Nathan Wrigley:</strong> In terms of the roster that you&#8217;ve currently got. Now you mentioned TechCrunch, and we know that there&#8217;s a whole bunch of other enormous companies that you&#8217;ve worked with. Did you feel compelled to go out and communicate with them prior to heading down the direction of merging with Fueled? Was there any intuition that maybe your clients would be interested to know that information or potentially you know, nervous to hear that you were doing this, and how would it affect their incredibly important property?</p>



<p>[00:30:00] <strong>Jake Goldman:</strong> In a spiritual sense we did not have a lot of concern about it. We thought it would make sense. This is not a case of say it rather crassly like being gobbled up by some international conglomerate that might be controversial to some customers. This was not a case of like changing to foreign ownership of a business.</p>



<p>It was hard to see how any customers would be anything but sort of happy to hear that we have maybe more sophistication as an entity and a governance and ownership model than, one guy in California owning the business. And pleased to hear that we were expanding our capabilities and could offer more solution and more services to them in the future. So we didn&#8217;t really have any sense that like somebody was going to be very upset to hear about this.</p>



<p>There is a process, there is a certain amount of like notifying, interviewing a small number of customers beforehand that are seen as, maybe riskier because they have strong terms in their contracts around change of ownership. Or just large clients where you know nobody&#8217;s going to be happy if for some shocking reason it changed the game afterwards.</p>



<p>So were some that were informed and brought into the loop, not because we had deep existential concern about it, but because it was a part of a due diligence process. We did speak to a few customers but otherwise the process was largely once we knew this was closing, once we knew this deal was going to get done, it was a rapid notification process. A harried two or three weeks right after the deal closed to make sure that we had a very orderly structure. But a quick way, inform those clients, let them know what that meant for them, deal with any contract language implications or updates. And I have to say I think that went exceptionally smoothly.</p>



<p>[00:31:24] <strong>Nathan Wrigley:</strong> Just touching on WordPress, this is after all a WordPress podcast. You have mentioned that your team over the years has contributed really quite large amounts of time and effort and resources to the WordPress project itself. And so I&#8217;m just curious as to whether this has changed anything. Or whether you are still everything pointing towards WordPress going to be contributing in the same way. Still using that as the platform of choice for the web side of things, if nothing else.</p>



<p>[00:31:50] <strong>Jake Goldman:</strong> So in terms of contribution nothing has changed. My hope is that this will open up added opportunities to contribute, make impact in the space. I think all of our new partners, Fueled, Insignia, understand that you know endemic to our strategy, our culture, our core values is that level of contribution that we make to the space.</p>



<p>It is, you know even if you don&#8217;t believe in it from an ethical sense, from a business sense it has made sense for us and it has helped us grow and it&#8217;s helped us acquire business, and helped us have impact, and build culture. So you know there are no plans to change that level of investment that we make.</p>



<p>In terms of WordPress as a CMS platform, yeah, I mean at the end of the day Fueled and Insignia fully understood that that is our preferred CMS platform, that is the dominant platform that we use. Fully understood that, you know making a bet on 10up was also making a bet on WordPress continuing to be healthy and grow as a platform. The CEO, a lovely fellow named Rameet literally spoke to Matt Mullenweg, as I understand, before I even knew he did about WordPress and about 10up.</p>



<p>At the end of the day they are looking, you know they chose to merge with us and are looking for us to be the experts in CMS implementation and looking for us to be the experts in how to make these websites and experiences. They don&#8217;t have a hubris to think they&#8217;re going to come in and tell us, we wanted to merge with you but we think you&#8217;ve been doing it wrong the whole time, and you need to change platforms, right? That&#8217;s almost silly as a way of thinking about it.</p>



<p>The short answer is I mean yes, they very much understand what they were buying. They see us as the experts. They look up for us to continue guiding and we continue to see WordPress as our dominant platform that we work with.</p>



<p>[00:33:14] <strong>Nathan Wrigley:</strong> I hope you don&#8217;t mind me asking you some personal question. I&#8217;m just wondering how this is going to affect you? You may decline to answer this question if you wish, and we can just cut it out entirely. But I&#8217;m just curious. From a lot of what you said there did seem to be some little bits of, you were intimating that some of these things were going to be wonderful for you as well as the company.</p>



<p>And I&#8217;m just wondering if you&#8217;ve had any of those experiences? Has work become more pleasurable? Have you managed to get out of this what you want? Have you managed to make new friendships and new alliances? Is it everything you hoped it would be?</p>



<p>[00:33:46] <strong>Jake Goldman:</strong> That&#8217;s a big question. I mean there&#8217;s two ways to answer that. I think there&#8217;s, I&#8217;m not trying to dodge, I think there&#8217;s a couple of different, two different ways of looking at that question. So the biggest sort of like aspiration that I wanted out of this, which is new partners, having people that are more my equals or even my seniors in this combined business. New advisors, new people that take true, you know in addition to some people on our team, new people, new additions to the team that take real, literal ownership of the business.</p>



<p>Yes, that is the case and it is welcome for me to have that, those kind of additions. I adore many of my new peers, feel energised when I work with them, when we sit down and plot out the future and work together. All of that is true. Now I think in the moment, four weeks in would I say that my life is now flowers and roses and better and easier? Let&#8217;s be earnest here. There&#8217;s two things going on at the moment. One is I had the same full time job that I had the week before, with a little less heavy as the head that wears the crown going on. But the same job that I had the month before in terms of like, again, we didn&#8217;t snap our fingers and transform the business operations overnight.</p>



<p>And now I also have this additional responsibility, which I take very seriously of that, playing a key role in facilitating change management and a longer term integration strategy. So if I was being very honest at the moment, my feeling is delight with the partners that we&#8217;ve chosen. A little bit of overwhelm and fatigue on like how much more there is to do at the moment. The seriousness with which I take this whole process is not a light burden. Doing big change management across a team of our scale is not a light duty for lack of a better word.</p>



<p>[00:35:13] <strong>Nathan Wrigley:</strong> This question would be best answered in a year&#8217;s time.</p>



<p>[00:35:15] <strong>Jake Goldman:</strong> A hundred percent it would.</p>



<p>[00:35:17] <strong>Nathan Wrigley:</strong> Let&#8217;s put that topic behind us and just get onto a subject which is completely nothing to do with what we&#8217;ve been talking about. Just for a few moments. I&#8217;m interested because AI is all the rage, if we were to rewind the clock two years, just two years, I don&#8217;t think anybody really in the WordPress space was really talking about AI. Maybe tangentially or some aspirational talk about what it could do.</p>



<p>And now fast forward to today. We&#8217;ve just had a year of utterly seismic change in the capabilities of what AI can do. Most of it disconnected completely with website building. So we&#8217;ve got OpenAI and Anthropic and a bunch of other companies launching really seismically amazing products. And I&#8217;m just wondering what your thoughts are? What your intuitions are about where this is going to land with website building, with WordPress?</p>



<p>Now I know that&#8217;s an incredibly broad question but I feel that&#8217;s all we&#8217;ve got at the moment because we don&#8217;t have concrete things to pin our discussion to. So I&#8217;m just wondering what your general thoughts are.</p>



<p>[00:36:16] <strong>Jake Goldman:</strong> Great question. Hang on one second while I type that question into ChatGPT. So we have lots of thoughts and lots of initiatives going on there. I think the first one to call out, and this is a bit of a plug, we have an extension we&#8217;ve been working on since before this was cool, since 2018. Back when we called this machine learning more often than artificial intelligence, called Classifai, that&#8217;s C L A S S I F A I, because we&#8217;re too clever with our puns. So ClassifaiPlugin.com, or just look up Classifai or 10up and AI, it&#8217;ll probably come up. I&#8217;m sure I&#8217;ll put it in show notes or something.</p>



<p>That plugin has been an experiment staging ground with us for, again, going back to 2018. It is not focused on like how to, I&#8217;m not sure I buy that this is the right use case for our kind of customers or you know the dominant part of the market. It does not try to be one of these like, we&#8217;re going to build your whole website for you. We&#8217;re going to write your story for you and your content. And those are cool demos, there are probably some very small business kind of use cases where you just need kind of like a boilerplate, you know you need to have the brochure. That just has to be a checkbox put next to we have a website.</p>



<p>But for the kind of market we work with I don&#8217;t think those are more than frankly sort of novelty demos at this point in time. That might change as the technology gets better in a year or two, but I don&#8217;t think a serious marketer is saying I&#8217;m going to write my pages and do my layouts just using AI on its own.</p>



<p>What we do think is that AI integrated with WordPress, which is what Classifai aims to do, can be extraordinarily powerful in simplifying repetitive tasks, and being an assistant and support to people that are creating and publishing content. So it does things like integrate natively with image generation services. If you want to generate a photo for your site, it will do things like create alt tags, and text descriptions for images, smart crop. It&#8217;ll take a pass at making paragraphs shorter or longer, individually in form on your site. It&#8217;ll tag images so you can navigate your media library better. It&#8217;ll suggest alternative titles you might want to consider.</p>



<p>So we are very focused in Classifai on what we would describe as extremely pragmatic, realistic, not novelty demo, kind of integration so that WordPress can compete. You know it&#8217;s completely open source, free plugin. You have to pay sometimes for the third party services, like the image generation services are mostly licensed. But we don&#8217;t make anything off of that, you just buy those services and plug your keys into Classifai settings.</p>



<p>So this very pragmatic setup where we think that customers, we hope other people using WordPress, can look to Classifai to be a very sort of modern, sort of high end, prosumer enterprise solution that gives an answer to, how do you use WordPress and AI?</p>



<p>On the technology, engineering side we have a working group. We have ongoing exploration of how do we in a safe way, in a private way, that respects our customers but in a way that keeps us competitive, continues to make sure that we don&#8217;t fall behind or suddenly become just wildly out of league and what it costs us to make something. Is experimenting with things like GitHub Copilot and more structured ways we can use that across projects. Experimenting with things like code generation with chat GPT. I don&#8217;t think the kind of websites we make are going to be like, build a whole website or 80 percent of the code with those tools.</p>



<p>I see it as an accelerant, no different than like when we had IDEs or even when we shifted from writing machine code to more natural languages like C and C++ and Swift and all the rest. And I think it&#8217;s still early in that exploration. There are certainly signals that there are some kinds of tasks, certain migration tasks, certain repetitive scripting tasks in the shell that you can automate, that you can accelerate.</p>



<p>And our job right now, and that job&#8217;s not done, is to figure out when you have a scale of you know 300 people and 100 or 200 some engineers. How do you create a standard? How do you create a process? What does it mean to create an expectation? Not across one or two people who are smart, curious and hungry to use these, but across an entire team to stay competitive and stay ahead of the curve.</p>



<p>I wish I could bring you all the answers other than to say like I think that technology will keep getting better. I do think it will help. I am not in the camp of at least for the next you know sort of five years. I am not in the camp of, this is going to replace the need for engineers. You know there are certain leaders in the WordPress space who I think would say like they imagine a few years from now their engineering teams go down from like a hundred to like five.</p>



<p>Maybe I&#8217;ll eat these words. I think it&#8217;s a bit silly when we think about the next two, three, four, even five years. I think it&#8217;s more like an extreme version of the leap again to like things that would have seemed very foreign 40 years ago, 50 years ago when the industry was frankly smaller, not larger. Where we started to have tools you know template patterns like you know the internet and access to Stack Overflow and good code completion tools.</p>



<p>These accelerant tools did not obliterate the industry, right? The industry is larger than it&#8217;s ever been. Which is to say like a rapid, rapid, huge changes that make engineering and technical tasks easier has never in the history of tech and computing and the web made for a smaller industry. It has always made a larger industry. It just gives people more time to think, to be creative, to make things that are more advanced. It&#8217;s raised the bar higher on what people expect in terms of quality and completeness of the experiences they get. I think that is more the world that we live in for the next three, four, five years now.</p>



<p>[00:40:59] <strong>Nathan Wrigley:</strong> I&#8217;m just wondering if there is some little part of AI which you&#8217;ve looked at, and again you know if this encroaches on business processes and things like that, you need not divulge what it is. I just wondered if at the level that you&#8217;re working at, if there are certain aspects of AI which you&#8217;re thinking, boy that really would save us a lot of time. That really does look like something which we should invest. It sounded like everything that you were developing, the Classifai is for the end user broadly.</p>



<p>It enables people like me to do my work quicker. But I&#8217;m just wondering if there was something that you were curious about on the AI side which would make your business processes quicker. And again, feel free to not divulge if you don&#8217;t wish to.</p>



<p>[00:41:36] <strong>Jake Goldman:</strong> I mean the short answer is yes, I think there is. I&#8217;m not not divulging anything to say like I&#8217;m not sure in a sustainable way what those things are yet. I know what we&#8217;re experimenting with. I know what we see some promise in. I kind of take the longer view and feel like it&#8217;s not clear yet which of these are sort of novelties in their appeal. Which of these are have enduring power as change forces in our process. It still feels like we&#8217;re in a little bit of a, I think, still in the getting to know it phase. I do think there are some things around like more baseline tasks in an estimate, or when we&#8217;re building certain kind of projects or certain kind of sites.</p>



<p>My suspicion is some migration work, some sort of like more fundamental lower level like set up, the v1 of just setting up a basic added functionality. That will go faster, that will be accelerated. But I have to just be honest. I&#8217;m still not even confident enough that we&#8217;ve done that enough times, tried that enough times, to know whether this is more like when GitHub comes along, becomes popular whether it totally changes the way we work, or it&#8217;s just another tool that helps people be more efficient.</p>



<p>[00:42:39] <strong>Nathan Wrigley:</strong> My intuitions are that anybody that puts their flag in the sand and says AI will enable this is probably setting themselves up for having to admit that they were wrong. Almost everything that I&#8217;ve predicted has not come to pass. Yeah we just have to be, roll with the punches, be flexible I suppose.</p>



<p>Jake it&#8217;s been lovely chatting to you today about all of this. I wonder if you make yourself available elsewhere online. Whether or not you want to divulge a social handle that you use, or a good place where people can contact you. Having listened to this there may be people who wish to do that, and if you wish to spread the word about that please do.</p>



<p>[00:43:14] <strong>Jake Goldman:</strong> Here&#8217;s a phrase I never thought I would say five years ago. So the place to most get my insight and hear what I&#8217;m thinking about business and 10up is LinkedIn. So if you just search for Jake Goldman on LinkedIn I should pop right up, or Jake Goldman in WordPress. That&#8217;s probably the best place to go. I mean go to 10up.com and follow our blog. I mean again all of our business activity as a company is there. In terms of like personal posting, not terribly active on any social media at this point.</p>



<p>[00:43:36] <strong>Nathan Wrigley:</strong> Well thank you Jake for chatting to me on the podcast today. I really appreciate it.</p>



<p>[00:43:40] <strong>Jake Goldman:</strong> Thank you for having me. It was a pleasure.</p>
</div>



<p>On the podcast today we have <a href="https://www.linkedin.com/in/jacobgoldman/">Jake Goldman</a>.</p>



<p>Jake is the President &amp; Founder of 10up, a digital agency that builds websites and tools for content creators, leveraging open platforms like WordPress.</p>



<p>We start the conversation with an exploration of the recent merger with 10up, Fueled and Insignia. For many years, 10up has been one of the leading Enterprise WordPress agencies. With a roster of well-known clients, Jake has grown the company from himself to hundreds of employees.</p>



<p>Whilst this journey has been exciting and challenging, Jake talks about some areas in which 10up has not been able to compete and how the merger with Fueled will enable them to position themselves for projects which used to be out of reach.</p>



<p>Fueled brings their experience of crafting mobile experiences, and Insignia brings their financial expertise, as well as the industry connections they have built up.</p>



<p>Jake shares how this new venture will continue to leverage WordPress as their CMS of choice; these new partners understand and support 10up’s commitment to contributing to WordPress. There are no plans to immediately alter the structures of either 10up or Fueled, It’s more about building an understanding of the capabilities of each partner, working towards a future in which the company grows into one entity over time.</p>



<p>We talk about the intentional pursuit of potential partners, and Jake reflects on the importance of cultural alignment and connections. He shares how his prior experience has shaped both his personal journey as a leader and the success of 10up, and we explore the milestones, challenges, and key moments that have brought them to where they are today.</p>



<p>Towards the end of the podcast, we pivot to talk about the role of AI in the future of WordPress. It’s clear that AI is coming, and it’s coming rapidly. Any agency working with WordPress would find this topic hard to ignore. But what impact will it really have? Are we expecting entire websites to be built in seconds by just clicking a button? Jake expresses his view that these tools are to be seen as accelerants, complementing human website development rather than replacing it, particularly at the Enterprise level. We delve into 10up’s ongoing exploration and experimentation with AI, discussing some of the tools they have freely released.</p>



<p>If you’re interested in how Enterprise agencies grow, or the future of AI with WordPress, this episode is for you.</p>



<h2 class="wp-block-heading">Useful links</h2>



<p><a href="https://10up.com/">10up website</a></p>



<p><a href="https://techcrunch.com/">TechCrunch website</a></p>



<p><a href="https://fueled.com/en-gb">Fueled</a></p>



<p><a href="https://10up.com/blog/2023/10up-joins-forces-with-fueled-digital-media/">Fueling Up: 10up joins forces with Fueled Digital&nbsp;Media</a></p>



<p><a href="https://openai.com/">OpenAI</a></p>



<p><a href="https://www.anthropic.com/">Anthropic</a></p>



<p><a href="https://classifaiplugin.com/">ClassifAI plugin</a></p>



<p><a href="https://www.linkedin.com/in/jacobgoldman/">Jake Goldman on LinkedIn</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 25 Oct 2023 14:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nathan Wrigley";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:24;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:64:"WPTavern: Automattic Acquires Texts, An All-in-One Messaging App";s: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=150606";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:74:"https://wptavern.com/automattic-acquires-texts-an-all-in-one-messaging-app";s: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:2807:"<p>Automattic has acquired <a href="https://texts.com/">Texts</a>, an all-in-one messaging platform, for $50 million. Texts is a newer company founded in 2020 that creates a centralized inbox for all major messaging platforms, including iMessage, WhatsApp, Instagram, Telegram, Signal, Twitter, LinkedIn, Slack, and Discord. </p>



<p>The proliferation of messaging apps and inboxes has made responding to communication more complicated than it was in previous years. Most companies would prefer to keep users on their own platforms, but Texts offers a new level of interoperability between messaging apps that doesn&#8217;t require the use of its own servers. The website states that users&#8217; messages never touch Texts&#8217; servers. They are encrypted and sent directly to the messaging platforms. Texts charges a monthly subscription, instead of making money by selling users&#8217; data. It also offers a number of AI-powered features for chat summaries, drafts, and translation.</p>



<p>Automattic&#8217;s Texts acquisition <a href="https://wordpress.com/blog/2023/10/24/texts-joins-automattic/">announcement</a> states that the company is moving &#8220;into a fourth market that’s integral to the modern web experience: messaging.&#8221;</p>



<p>Mullenweg has been eying the messaging market for years and has previously spoken of his fascination with messaging platforms and their relationship with the independent web. In an <a href="https://youtu.be/P2qbSMdCvis">interview with Om Malik</a> at WordCamp Europe 2017, he mentioned that Automattic was experimenting with Telegram’s group broadcasting feature. More recently, it 2020, <a href="https://wptavern.com/automattic-invests-4-6m-in-new-vector-creators-of-the-matrix-open-standard-for-decentralized-communication">Automattic invested $4.6M in New Vector</a>, a company founded by the creators of <a href="https://matrix.org/">Matrix</a>, an open standard that powers decentralized conversations with end-to-end encryption. </p>



<p>Texts&#8217; founder, Kishan Bagaria, will take on a new role as Head of Messaging at Automattic and the rest of the 10-person team was retained to continue working on the product.</p>



<p>In response to an inquiry about the status of the iOS and Android mobile apps for Texts, a representative from Automattic said the company is currently testing an iOS beta with a subset of users. Android support is on the roadmap. The representative also confirmed there are no plans to change pricing right now but Automattic is considering the addition of a freemium plan in the future.</p>



<p>Texts will be expanding its coverage to streamline messages across more platforms. Matrix, Tumblr, and many more integrations are on the roadmap, including Snapchat, Google Messages, and Reddit.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 25 Oct 2023 02:19: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:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:25;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:28:"Matt: Texts Joins Automattic";s: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:23:"https://ma.tt/?p=102049";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"https://ma.tt/2023/10/texts-joins-automattic/";s: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:3203:"<p><a href="https://texts.com/">Texts is a fun application (desktop only for now) that brings all of your messages into one inbox</a>. It currently supports iMessage, WhatsApp, Telegram, Signal, Messenger, X/Twitter DMs, Instagram DMs, LinkedIn, Slack, and Discord DMs, with more on the way soon. It runs entirely on the desktop so it&#8217;s super fast and secure. It&#8217;s founded and led by <a href="https://kishanbagaria.com/">Kishan Bagaria</a>, a really unique entrepreneur and technical talent, and has a slate of amazing investors including <a href="https://twitter.com/lachygroom">Lachy Groom</a>, <a href="https://rauchg.com/">Guillermo Rauch</a> (former Automattician!), <a href="https://sahillavingia.com/">Sahil Lavingia</a>, and <a href="https://twitter.com/KishanBagaria/status/1716778353439486291">many others</a>—and I&#8217;m excited to announce that it&#8217;s now part of <a href="https://automattic.com/">Automattic</a>!</p>



<p>This was announced today on <a href="https://pca.st/zkesr4d4">the Pivot podcast with Kara Swisher and Scott Galloway (my part starts 48:50 in)</a>, and also covered <a href="https://www.theverge.com/2023/10/24/23928685/automattic-texts-acquisition-universal-messaging">in The Verge</a>, <a href="https://techcrunch.com/2023/10/24/wordpress-com-owner-buys-all-in-one-messaging-app-texts-com-for-50m/">TechCrunch</a>, <a href="https://www.macstories.net/news/automattic-acquires-interoperable-messaging-service-texts/">MacStories</a>, and <a href="https://www.techmeme.com/231024/p10#a231024p10">a few others</a>.</p>



<p>Today is also my 18th anniversary at Automattic! So, an exciting day all around.</p>



<p>Using an all-in-one messaging app is a real game-changer for productivity and keeping up with things. Texts is a paid app, with discounted student pricing, and I think a lot of people will find value in it. It&#8217;s quickly become one of the top three apps I spend time using.</p>



<p>This is obviously a tricky area to navigate, as in the past the networks have blocked third-party clients, but I think with the current anti-trust and regulatory environments this is actually something the big networks will appreciate: it maintains the same security as their clients, opens them up in a way consumers will love and is very user-centric, and because we&#8217;re committed to supporting all their features it can actually increase engagement and usage of their platforms.</p>



<p>We&#8217;re still working out everything for mobile, so if you&#8217;re looking for the all-in-one experience on iOS or Android in the meantime, I recommend checking out <a href="https://www.beeper.com/">Beeper</a>. It really is great to have everything together.</p>



<p>If you&#8217;re a reverse engineer hacker that is interested in working with a super-small elite team in this space with the fun of a startup and the air cover of Automattic, get in touch with <a href="https://twitter.com/KishanBagaria">Kishan on Twitter DM</a> or email (kb at texts). Here&#8217;s a fun video for Texts. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f604.png" alt="😄" class="wp-smiley" /></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:"Tue, 24 Oct 2023 18:58:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:53:"WordPress.org blog: WordPress 6.4 Release Candidate 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=16219";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6558:"<p>The second release candidate (RC2) for WordPress 6.4 is now available!</p>



<p><strong>This version of the WordPress software is under development</strong>. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC2 on a test server and site.</p>



<p>WordPress 6.4 is <a href="https://make.wordpress.org/core/6-4/">slated for release</a> on <strong>November 7, 2023</strong>—two weeks from today. If you haven’t tried it, now is the time.</p>



<p>You can test WordPress 6.4 RC2 in three ways:</p>



<ol>
<li><strong>Plugin</strong>: Install and activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin on a WordPress install (select the “Bleeding edge” channel and “Beta/RC Only” stream).</li>



<li><strong>Direct download</strong>: Download the <a href="https://wordpress.org/wordpress-6.4-RC2.zip">RC2 version (zip)</a> and install it on a WordPress site.</li>



<li><strong>Command line</strong>: Use the following <a href="https://make.wordpress.org/cli/">WP-CLI</a> command:<br /><code>wp core update --version=6.4-RC2</code></li>
</ol>



<p><a href="https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-1/">Read the RC1 announcement</a> for featured highlights, and check the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/6-4/">6.4-related posts</a>. If you are looking for detailed technical notes on new features and improvements, the <a href="https://make.wordpress.org/core/2023/10/23/wordpress-6-4-field-guide/"><strong>WordPress 6.4 Field Guide</strong></a> is for you.</p>



<p>The WordPress 6.4 release is brought to you by an <a href="https://make.wordpress.org/core/2023/06/05/wordpress-6-4-development-cycle/">underrepresented gender release squad</a> to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.</p>



<h2 class="wp-block-heading">What’s in WordPress 6.4 RC2?</h2>



<p>Thanks to everyone who has tested the beta and RC releases. Since RC1 was released on October 17, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:</p>



<ul>
<li><a href="https://github.com/WordPress/gutenberg/commits/wp/6.4">GitHub commits for 6.4</a></li>



<li><a href="https://core.trac.wordpress.org/query?status=closed&changetime=10%2F18%2F2023..10%2F24%2F2023&milestone=6.4&col=id&col=milestone&col=owner&col=type&col=priority&order=id">Closed Trac tickets since RC1</a></li>



<li><a href="https://github.com/WordPress/twentytwentyfour/commits/">GitHub commits for Twenty Twenty-Four</a></li>
</ul>



<h2 class="wp-block-heading">Contributing to 6.4</h2>



<p>WordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.</p>



<h3 class="wp-block-heading">Get involved in testing</h3>



<p>Your feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. <a href="https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/">Check out this guide</a> for instructions on testing WordPress 6.4 features.</p>



<p>If you encounter an issue, please report it to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta area</a> of the support forums or directly to <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a> if you are comfortable writing a reproducible bug report. You can also check your issue against a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>



<p>Curious about testing releases in general? Follow along with the <a href="https://make.wordpress.org/test/">testing initiatives in Make Core</a> and join the <a href="https://wordpress.slack.com/messages/core-test/">#core-test channel</a> on <a href="https://wordpress.slack.com/">Making WordPress Slack</a>.</p>



<h3 class="wp-block-heading">Search for vulnerabilities</h3>



<p>During the release candidate phase of WordPress 6.4, the <a href="https://make.wordpress.org/security/2023/09/26/bug-bounty-for-wordpress-6-4-beta/">monetary reward for reporting new, unreleased security vulnerabilities</a> is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the <a href="https://hackerone.com/wordpress">HackerOne page</a> and in the <a href="https://wordpress.org/about/security/">security white paper</a>.</p>



<h3 class="wp-block-heading">Update your theme or plugin</h3>



<p>Do you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.</p>



<p>Hopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC2, you will want to continue your testing and update the <em>&#8220;Tested up to&#8221;</em> version in your <a href="https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/">plugin&#8217;s readme file</a> to 6.4.</p>



<p>Please post detailed information to the <a href="https://wordpress.org/support/forum/alphabeta/">support forums</a> if you find compatibility issues.</p>



<h3 class="wp-block-heading">Help translate WordPress</h3>



<p>Do you speak a language other than English? ¿Español? Français? Português? Русский? 日本? <a href="https://translate.wordpress.org/projects/wp/dev">Help translate WordPress into more than 100 languages</a>.</p>



<h2 class="wp-block-heading">A RC2 haiku</h2>



<p>You have been waiting<br />Download and give it a test<br />RC2 is here</p>



<p><em>Thank you to the following contributors for collaborating on this post: <a href="https://profiles.wordpress.org/meher/" class="mention"><span class="mentions-prefix">@</span>meher</a>, <a href="https://profiles.wordpress.org/rmartinezduque/" class="mention"><span class="mentions-prefix">@</span>rmartinezduque</a>, <a href="https://profiles.wordpress.org/michelleames/" class="mention"><span class="mentions-prefix">@</span>michelleames</a>, <a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a></em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 24 Oct 2023 16:45:05 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:75:"WordCamp Central: WordCamp Lahore 2023 is looking for Speakers and Sponsors";s: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:39:"https://central.wordcamp.org/?p=4251876";s: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://central.wordcamp.org/news/2023/10/wordcamp-lahore-2023-is-looking-for-speakers-and-sponsors/";s: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:3228:"<p>Are you a WordPress enthusiast looking for an exciting event to attend? WordCamp Lahore 2023 has just the ticket for you! This official conference, organized by WordPress Lahore, is set to be a fantastic opportunity for WordPress users, developers, and open-source enthusiasts to come together, share knowledge, and contribute to the WordPress community.</p>



<p>Here&#8217;s what you need to know about WordCamp Lahore 2023:</p>



<h2 class="wp-block-heading">Early Bird Tickets:&nbsp;</h2>



<p>If you&#8217;re eager to attend this dynamic conference, you&#8217;re in luck! Early bird tickets are now available for registration at a discounted price. It&#8217;s the perfect chance to secure your spot and save some money. Don&#8217;t miss out on this fantastic offer &amp; visit this link to avail this discounted price.<br /><a href="https://lahore.wordcamp.org/2023/tickets/">https://lahore.wordcamp.org/2023/tickets/</a></p>



<h2 class="wp-block-heading">Date and Schedule:</h2>



<p>&#8211; Contributor Day: December 9th, 2023</p>



<p>&#8211; Formal Conference Day: December 10th, 2023</p>



<p>On December 9th, WordCamp Lahore will host a Contributor Day where attendees can receive training on how to contribute to WordPress open-source projects. This is a unique opportunity to learn how to give back to the WordPress community and make a real impact on the world&#8217;s most popular content management system.</p>



<p>The formal conference day on December 10th will feature a diverse range of sessions and workshops, all focused on WordPress. Whether you&#8217;re a beginner looking to learn the basics or an experienced developer seeking advanced insights, there will be something for everyone.</p>



<h2 class="wp-block-heading">Sponsorship Opportunities:</h2>



<p>WordCamp Lahore is currently seeking sponsors to help make this event a success. Sponsoring a WordCamp is not just an excellent way to support the WordPress community, but it also provides visibility for your brand among an audience passionate about WordPress.https://lahore.wordcamp.org/call-for-sponsors/</p>



<p>Each package offers unique benefits, allowing you to choose the level of support that aligns with your goals and budget. If you&#8217;re interested in becoming a sponsor, you can find more information about the packages and their respective benefits on the WordCamp Lahore 2023 website. Just visit this link: <a href="https://lahore.wordcamp.org/2023/call-for-sponsors/">WordCamp Lahore 2023 &#8211; Call for Sponsors</a>.</p>



<h2 class="wp-block-heading">Don&#8217;t Miss Out:</h2>



<p>WordCamp Lahore 2023 promises to be an exciting and enriching experience for anyone passionate about WordPress and open-source technologies. Early bird tickets are available, and sponsorship opportunities await those who want to make a difference in the WordPress community.</p>



<p>Mark your calendar for December 9th and 10th, and be a part of this thriving WordPress community event in Lahore. Get your tickets, explore the sponsorship options, and get ready for a memorable WordCamp!</p>



<p>For more information and updates, visit the official WordCamp Lahore 2023 website. We look forward to seeing you there!</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 24 Oct 2023 14:55: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:15:"Abdullah Ramzan";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:108:"Do The Woo Community: Agency Growth, Challenges, Workflow and Team Building with Matt Nelson and Neil Harner";s: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=77356";s: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://dothewoo.io/woocommerce-agency-growth-challenges-workflow-client-focus/";s: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:462:"<p>Matthew Nelson of FirstTracks Marketing and Neil Harner of Inverse Paradox, share their experiences in growth, workflow and team building.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/woocommerce-agency-growth-challenges-workflow-client-focus/">Agency Growth, Challenges, Workflow and Team Building with Matt Nelson and Neil Harner</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 24 Oct 2023 12:23:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:29;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:58:"WPTavern: The 2024 State of Open Source Survey Is Now Open";s: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=150592";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wptavern.com/the-2024-state-of-open-source-survey-is-now-open";s: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:1481:"<p>The Open Source Initiative (OSI), a non-profit organization that plays an important role in the open source ecosystem as stewards of the <a href="https://opensource.org/docs/osd">Open Source Definition (OSD)</a>, has opened its <a href="https://www.surveymonkey.com/r/open-source-initiative">2024 State of Open Source</a> survey. This is the third year OSI has published the survey in collaboration with OpenLogic by Perforce, who has sponsored it in previous years. The organizations will be joined by the Eclipse Foundation for the 2024 edition.</p>



<p>Both users and contributors to open source software are invited to participate in the survey, but the questions are more geared towards organizations using and building open source software. The survey gathers information on technology trends, how open source is being used, challenges, growth areas, and more. The data will be used in the 2024 State of Open Source Report, which will be freely available on the OpenLogic website in early 2024.</p>



<p>&#8220;The data collected in this survey shines a light on the importance of tracking the evolution of Open Source licenses, especially at a time when those licenses are changing from OSI-approved to proprietary,&#8221; OSI Executive Director Stefano Maffulli said.</p>



<p>The survey is open through November 10, and takes approximately 7-10 minutes to complete. All responses will be anonymized and the data will be published under an open source license.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 24 Oct 2023 04:01:05 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:30;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"WPTavern: LiteSpeed Cache 5.7 Patches XSS Vulnerability ";s: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=150578";s: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://wptavern.com/litespeed-cache-5-7-patches-xss-vulnerability";s: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:2583:"<p>The <a href="https://wordpress.org/plugins/litespeed-cache/">LiteSpeed Cache plugin</a>, used on more than four million WordPress sites, has patched an XSS vulnerability in version 5.7. The plugin provides all-in-one site acceleration capabilities, server-level caching, and a collection of optimization features. It is compatible with WordPress multisite, and popular plugins like WooCommerce, bbPress, and Yoast SEO, which may contribute to its popularity. </p>



<p>Wordfence security researcher István Márton discovered the XSS vulnerability and responsibly disclosed it to the LiteSpeed Cache Team on August 14, 2023. The Wordfence <a href="https://www.wordfence.com/blog/2023/10/4-million-wordpress-sites-affected-by-stored-cross-site-scripting-vulnerability-in-lightspeed-cache-plugin/">advisory</a> describes how the vulnerability might make it possible for an attacker to inject malicious scripts:</p>



<blockquote class="wp-block-quote">
<p>The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘esi’ shortcode in versions up to, and including, 5.6 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.</p>
</blockquote>



<p>Márton also cautioned that previous versions of WordPress contained a vulnerability that allowed shortcodes supplied by unauthenticated commenters to be rendered in certain configurations. All versions since WordPress 5.9 were subject to this vulnerability and if users aren&#8217;t on <a href="https://wordpress.org/news/2023/05/wordpress-6-2-2-security-release/">a patched version of WordPress</a>, the vulnerability would &#8220;make it possible for unauthenticated attackers to exploit this Cross-Site Scripting vulnerability on vulnerable installations.&#8221; </p>



<p>LiteSpeed Cache patched the vulnerability in version 5.7, released to WordPress.org on October 10. Although the update has been available for two weeks, only 30% of the plugin&#8217;s user base is running the latest version.</p>



<p>LiteSpeed Cache users are recommended to update to the latest patched version as soon as possible. Check out the <a href="https://www.wordfence.com/blog/2023/10/4-million-wordpress-sites-affected-by-stored-cross-site-scripting-vulnerability-in-lightspeed-cache-plugin/">advisory</a> from Wordfence for more details and a full technical analysis.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 24 Oct 2023 00:28: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:31;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:63:"WPTavern: Ollie Dash Plugin Now Available for Ollie Block Theme";s: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=150508";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:74:"https://wptavern.com/ollie-dash-plugin-now-available-for-ollie-block-theme";s: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:3324:"<p>The <a href="https://olliewp.com/">Ollie block theme</a>, created by Mike McAlister and Patrick Posner, now has a companion plugin available called Ollie Dash. The theme made headlines earlier this month after <a href="https://wptavern.com/contentious-review-process-leads-ollie-theme-to-remove-innovative-onboarding-features-amid-stagnating-block-theme-adoption">a contentious WordPress.org review process led its authors to remove the innovative onboarding features</a>. Ollie was approved for WordPress.org but without the time-saving onboarding features its authors initially hoped to include. </p>



<p>Testing the plugin, it is a night and day difference between having onboarding for a theme with so many patterns and options, versus getting dropped into a new theme with no direction. </p>



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



<img width="2582" height="1308" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/Screen-Shot-2023-10-21-at-4.07.23-PM.png" alt="" class="wp-image-150521" />



<p>Instead of hunting around for various settings, the plugin helps users get everything set up with just a few clicks. It includes settings for the color palette, brand color, logo, and site icon. </p>



<p>The wizard also enables fast page creation where users can check a box for any of the full-page designs that they want to be created as pages.</p>



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



<img width="2092" height="1202" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/Screen-Shot-2023-10-21-at-4.21.49-PM.png" alt="" class="wp-image-150522" />



<p>One particularly time-saving screen on the onboarding wizard is the one with the homepage settings. Getting the homepage set can be a confusing part of setup for new WordPress users, especially if they don&#8217;t know where to look for the setting.  Ollie Dash allows a user to select the homepage from a dropdown before they even begin customizing the site. </p>



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



<img width="2084" height="1208" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/Screen-Shot-2023-10-21-at-4.26.47-PM.png" alt="" class="wp-image-150524" />



<p>At the end of the onboarding wizard, users have the option to instantly create and activate a child theme. It&#8217;s not necessary for every website, but is a major time saver for those who intend to further customize the theme&#8217;s code.</p>



<p>The onboarding includes docs and video resources for getting started, which can be loaded directly inside the wizard without leaving the site.</p>



<p>McAlister said Ollie Dash will be the foundation for more features his team has in development. They are taking the plugin route as an opportunity to add more functionality than would generally be allowed in a WordPress.org-hosted theme.</p>



<p>McAlister said he plans to make the plugin available on WordPress.org in the future. There are currently 1,062 plugins awaiting review in the queue today, with a wait time of 87 days for an initial review. In the meantime, Ollie Dash can be <a href="https://olliewp.com/download/">downloaded</a> from the Ollie website and can also be found <a href="https://github.com/OllieWP/ollie-dash">on GitHub</a>. Users will be notified in the dashboard when there is an update.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 21 Oct 2023 20:53: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:32;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:44:"WPTavern: Elementor Postpones DreamWeb Event";s: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=150480";s: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:55:"https://wptavern.com/elementor-postpones-dreamweb-event";s: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:2470:"<p><a href="https://elementor.com/">Elementor</a>, the most popular website builder plugin for WordPress with more than 5 million active installations, has postponed its upcoming <a href="https://elementor.com/pages/dreamweb/">DreamWeb</a> event. The Israel-based company was set to host its first in-person conference  on November 2, in Berlin, Germany, but has postponed it due to the circumstances following Hamas&#8217; terrorist attack on Israel on October 7.</p>



<p>In 2022, Elementor hosted more than 400 meetup events. DreamWeb was set to be a one-day event at the <a href="https://alte-muenze-berlin.de/">Alte Münze</a> venue with keynotes, knowledge-sharing, activities, networking opportunities, and an evening gala. Early bird tickets went on sale for 99€ in early October.</p>



<p>The event was postponed shortly after the attacks, with a statement on the DreamWeb page:</p>



<blockquote class="wp-block-quote">
<p>At Elementor we can’t ignore the devastation that has been experienced in Israel over the last few days. We’ve decided to postpone the Dream Web event and announcement of the ShowOff winner, until we return to calmer days.&nbsp;</p>



<p>We stand in solidarity supporting family, friends and fellow citizens.</p>
</blockquote>



<p>Many of the company&#8217;s employees are based in Israel and have friends and family affected by the ongoing conflict. </p>



<p>&#8220;Guided by our values of putting people first, we are diligently taking every measure to ensure the well-being of our employees in Israel, all the while operating to continue our global work with and for Web Creators,&#8221;  Elementor representatives <a href="https://www.facebook.com/elemntor/posts/634991428782709:1405926339959966?__cft__[0]=AZVZJVxprAGYm2s5mHtlJUr-PEOwwzScmGpg2TYLgbzKArtxcBHcZpgHPXW4uNW7zSlR5bBPDtIir6NMIG8tY5z_sg55Kxnh80uwvIY2R9cuMYStNBWEBgE6azpYGwwlWrhj24Bnqgc6jNknY8Jx_479p67M7KoLTp6TwhIY7ZnPx7D8COpVs8R2e_X8WAuKpLY&__tn__=%2CO%2CP-R">wrote</a> on the product&#8217;s Facebook account on October 15.</p>



<p>&#8220;Some of us are hiding with children in shelters as rockets are fired on our cities, and some managed to escape from the Hammas terrorists in the south of Israel to safer places. All of us, unfortunately, know someone who was murdered, or kidnapped.&#8221;</p>



<p>The DreamWeb event has been postponed indefinitely, and Elementor stated that &#8220;a new date will be announced as peaceful days return.&#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, 20 Oct 2023 21:39:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"Do The Woo Community: Do the Woo Podcast Hits Episode 400";s: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=77171";s: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://dothewoo.io/do-the-woo-podcast-hits-episode-400/";s: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:371:"<p>As we hit episode 400, Ronald chats with BobWP with a look back and into the next few months with the Do the Woo podcast.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/do-the-woo-podcast-hits-episode-400/">Do the Woo Podcast Hits Episode 400</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 20 Oct 2023 10:23: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:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:79:"WPTavern: State of the Word 2023 Will Broadcast Live from Madrid on December 11";s: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=150447";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:90:"https://wptavern.com/state-of-the-word-2023-will-broadcast-live-from-madrid-on-december-11";s: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:1494:"<p>WordPress co-founder Matt Mullenweg will be delivering his annual State of the Word (SOTW) address <a href="https://wordpress.org/news/2023/10/state-of-the-word-2023/">from Madrid</a> before a live audience on December 11, at 15:00 UTC. </p>



<p>Last year&#8217;s event took place in New York City with attendance by invitation only, and 2023 will mark the first year the SOTW will take place from a city outside North America. This change may be a deliberate recognition of the majority (<a href="https://wordpress.org/about/stats/">51.4%</a>) of WordPress users who run the software in a non-English language. WordPress adoption has the most potential for growth in emerging markets and locales where Spanish, Arabic, and Chinese languages are spoken. </p>



<p>Traditionally, Mullenweg has used the State of the Word address to make important announcements, share progress, galvanize the contributor base, and recast the vision for WordPress. As the Gutenberg project is now into Phase 3 focusing on collaboration, I would not be surprised to see a demo of functionality that users can expect to see in 2024.</p>



<p>Live attendees will need to reserve a ticket for their seats at the in-person event. A live stream will be available for the vast majority of the WordPress world who will not be able to attend. As in previous SOTW events, anyone will be able to submit questions for the live Q&amp;A portion. The team managing the event plans to release more details in November.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 20 Oct 2023 03:58: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:35;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"WPTavern: WordPress Relaunches Showcase Powered by Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=150376";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"https://wptavern.com/wordpress-relaunches-showcase-powered-by-blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4711:"<p>WordPress.org has launched the redesign of the <a href="https://wordpress.org/showcase/">Showcase</a>, with new block-based components, through a collaboration between the Design, Marketing, and Meta teams that began last year. It&#8217;s part of a larger effort to modernize WordPress.org and comes two months after the project relaunched a <a href="https://wordpress.org/news/2022/08/a-new-wordpress-org-homepage-and-download-page/">new design for the WordPress.org homepage and Download page</a>.</p>



<p> The updated Showcase allows visitors to browse via categories and tags and offers a significantly improved experience on mobile.  It included 101 sites at launch, which can be filtered by five categories: Business, Community, Creative, Publication, and Store, along with nearly half a dozen tags. Visitors can also select from three flavors: WordPress, WordPress Enterprise, and Multisite.</p>



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



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



<img width="1432" height="1196" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/Screen-Shot-2023-10-18-at-11.08.40-PM.png" alt="" class="wp-image-150379" />



<p>The featured listing at the top of the Showcase randomly updates on refresh. Individual listings in the showcase include screenshots of both desktop and mobile views, along with a brief overview of why the site was included. The background for the screenshots is automatically matched to complement the website&#8217;s main colors.</p>



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



<img width="1430" height="1164" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/Screen-Shot-2023-10-18-at-11.27.45-PM.png" alt="" class="wp-image-150382" />



<p>The showcase was designed to inspire visitors and show them what WordPress can do. It contains a diverse representation of some of the best WordPress-powered sites on the web, including the <a href="https://wordpress.org/showcase/meta-newsroom/">Meta Newsroom</a>, <a href="https://wordpress.org/showcase/harvard-university/">Harvard University</a>, <a href="https://wordpress.org/showcase/nasa/">NASA</a>, <a href="https://wordpress.org/showcase/rolling-stone/">Rolling Stone</a>, <a href="https://wordpress.org/showcase/usain-bolt/">Usain Bolt</a>, <a href="https://wordpress.org/showcase/the-white-house/">The White House</a>, among many other high profile web properties. The showcase also includes some lesser known, beautifully designed sites, featuring art and creativity across a wide range of disciplines, highlighting the endless possibilities and versatility of the WordPress platform. </p>



<img width="2402" height="1088" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/Screen-Shot-2023-10-19-at-6.22.19-PM.png" alt="" class="wp-image-150435" />



<p>This new implementation of the showcase is powered by blocks, built on a <a href="https://github.com/WordPress/wporg-showcase-2022">custom child theme</a> for WordPress.org&#8217;s <a href="https://github.com/WordPress/wporg-parent-2021">parent block theme</a>.</p>



<p>&#8220;This structure allows the site to take advantage of Core functionality like Group and Query blocks as well as custom blocks explicitly built for WordPress.org,&#8221; Automattic-sponsored WordPress core contributor Nick Diego said.</p>



<p>&#8220;The Showcase also introduces new block-based functionality and several components that will be used elsewhere on the WordPress.org network. Improvements, such as the standardization of layout and spacing variables (<a href="https://github.com/WordPress/wporg-parent-2021/issues/105">#105</a>) and the new Query Filter block (<a href="https://github.com/WordPress/wporg-mu-plugins/pull/441">#441</a>), will make it easier to update other areas of WordPress.org to blocks.&#8221;</p>



<p>The updated showcase is an invaluable resource for agencies and freelancers who are building sites for clients and need to demonstrate the capabilities of WordPress to scale and serve any industry. It&#8217;s also still <a href="https://wordpress.org/showcase/">open for new submissions</a>, which meet the following criteria:</p>



<ul>
<li>Using WordPress in a unique or innovative way</li>



<li>Representing a notable organization, government entity, or corporation as an official blog or website</li>



<li>Using modern WordPress</li>
</ul>



<p>Contributors are working to streamline and <a href="https://github.com/WordPress/wporg-showcase-2022/issues/223">automate</a> the submission process, although it will still include a manual review.  As this process improves, the showcase will become easier to maintain than it has been in previous years.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Oct 2023 23:15:05 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:36;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:60:"WordPress.org blog: State of the Word 2023 – Save the Date";s: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=16116";s: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://wordpress.org/news/2023/10/state-of-the-word-2023/";s: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:1591:"<img width="1024" height="683" src="https://i0.wp.com/wordpress.org/news/files/2023/10/Web-SOTW-Image-1200x800-2.png?resize=1024%2C683&ssl=1" alt="Madrid State of the Word 2023, Dec 11, 2023 at 15:00 UTC, Madrid, Spain" class="wp-image-16208" />



<p>It’s time to save the date, December 11, 2023, for this year’s State of the Word!</p>



<p>State of the Word is the annual keynote address delivered by the WordPress project’s co-founder, <a href="https://ma.tt/">Matt Mullenweg</a>. Every year, the event shares reflections on the project’s progress and aspirations for the future of open source.&nbsp;</p>



<p>For the first time, State of the Word will take place outside North America–this time with the Spanish community in <strong>Madrid, Spain</strong>. The event will be live-streamed to WordPress enthusiasts around the globe via WordPress.org social media platforms.&nbsp;</p>



<p>Join Matt as he provides a retrospective of 2023, demos the latest in WordPress tech, and comments on the future of the WordPress open source project.</p>



<p>Details including how to reserve a ticket for the in-person event, the link to watch the live stream, and information on how to submit questions for the Q&amp;A portion will be provided in November and shared on <a href="https://wordpress.org">WordPress.org</a> and affiliated social media accounts.</p>



<p></p>



<p><em>Thanks to <a href="https://profiles.wordpress.org/rmartinezduque/">Reyes Martínez</a> and <a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a> for reviewing this post.</em> </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Oct 2023 17:45:03 +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:"Dan Soschin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:100:"Gutenberg Times: Gutenberg Changelog #91 – WordPress 6.4, Gutenberg 16.8 and what’s in the works";s: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=26071";s: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:107:"https://gutenbergtimes.com/podcast/gutenberg-changelog-91-wordpress-6-4-gutenberg-16-8-and-whats-discussed/";s: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:48195:"<p>Joni Halabi and Birgit Pauli-Haack discuss WordPress 6.4, Gutenberg 16.8 and what’s been worked on outside current releases</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>



<p><strong>Joni Halabi</strong>, senior developer at Georgetown University</p>



<ul>
<li><a href="https://gutenbergtimes.com/live-q-a-design-systems-and-theme-json/">Live Q &amp; A: Design Systems and theme.json</a></li>



<li><a href="https://developer.wordpress.org/news/2023/02/static-vs-dynamic-blocks-whats-the-difference/">Static vs. dynamic blocks: What’s the difference?</a></li>



<li>Book: <a href="https://jhalabi.com/book/">Sweet Little You by Joni Halabi</a></li>



<li>X (former Twitter) <a href="https://twitter.com/jonihalabi">@jonihalabi</a></li>



<li>WordPress <a href="https://profiles.wordpress.org/thatdevgirl/">@thatdevgirl</a></li>



<li><a href="https://talks.jhalabi.com/svg-in-wordpress/">Slides: Creating Accessible SVG</a> (WP Accessibility Day) (Recording will be <a href="https://www.youtube.com/@WPA11yDay">published in YouTube</a> soon) </li>
</ul>



<h2 class="wp-block-heading">What&#8217;s released</h2>



<p><strong>First Dev Notes for WordPress 6.4 </strong></p>



<ul>
<li><a href="https://make.wordpress.org/core/2023/10/15/introducing-block-hooks-for-dynamic-blocks/">Introducing Block Hooks for dynamic blocks</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/16/editor-components-updates-in-wordpress-6-4/">Editor Components updates in WordPress 6.4</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/16/new-registerinsertermediacategory-api/">New `registerInserterMediaCategory` API</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/16/wordpress-core-is-now-using-playwright-for-all-browser-based-tests/">WordPress core is now using Playwright for all browser-based tests</a></li>



<li><a href="https://make.wordpress.org/core/2023/10/16/introducing-admin-notice-functions-in-wordpress-6-4/">Introducing admin notice functions in WordPress 6.4</a></li>
</ul>



<p><a href="https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-1/">WordPress 6.4 Release Candidate 1</a></p>



<p><strong>Gutenberg 16.8</strong></p>



<ul>
<li><a href="https://make.wordpress.org/core/2023/10/11/whats-new-in-gutenberg-16-8-11-october/">What’s new in Gutenberg 16.8 (11 October)</a></li>



<li><a href="https://wptavern.com/gutenberg-16-8-makes-cover-block-smarter-adds-experimental-pages-list-in-site-editor">Gutenberg 16.8 Makes Cover Block Smarter, Adds Experimental Pages List in Site Editor</a></li>
</ul>



<p><strong>What&#8217;s discussed and worked on</strong></p>



<ul>
<li><a href="https://github.com/WordPress/gutenberg/pull/53788#top">Site editor: 🥝 Media library proof of concept&nbsp;</a></li>



<li><a href="https://github.com/WordPress/gutenberg/pull/44214#top">Introduce experimental form &amp; inputs blocks to allow building basic forms</a></li>



<li><a href="https://github.com/WordPress/gutenberg/pull/54494#top">Update the default JSX pragma to React instead of @wordpress/element</a></li>



<li><strong>The Gutenberg repo has now a new label:</strong><a href="https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Data%20Views"> Data Views</a></li>
</ul>



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



<div class="wp-block-group is-layout-flow 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 91st episode of the Gutenberg Changelog podcast. In today&#8217;s episode, we will talk about WordPress 6.4 a little bit and Gutenberg 16.8, and then we also will talk about what&#8217;s already been worked outside the current releases. I&#8217;m your host, Birgit Pauli-Haack, curator at the Gutenberg Times and a full-time core contributor for the WordPress Open Source Project, sponsored by Automattic&#8217;s Five for the Future Program. Today, my co-host and special guest is Joni Halabi. She is not a stranger to the Gutenberg Times&#8217; subscribers. She&#8217;s a senior developer at Georgetown University and has been building blocks since forever.&nbsp;</p>



<p>Our recent adventure together was the Gutenberg Life Q&amp;A with David Bowman and Alec Geatches, and a fascinating discussion about design systems and how WordPress slowly becomes one. Joni is also the author of a great article on the WordPress developer blog explaining the difference between a static and a dynamic block. A lot of people have read this, so you made an impact there definitely, Joni. It&#8217;s my great pleasure to have you on the show tonight, Joni. Welcome. How are you today?&nbsp;</p>



<p><em>Joni Halabi</em>: I&#8217;m doing great, thank you. I&#8217;m really excited to be on this show.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Awesome, awesome. Well, we can go right in there.&nbsp;</p>



<h3 class="wp-block-heading">Announcements</h3>



<p>The first developer notes for 6.4 have been published on the Make blog, and one is for a new extensibility feature for the block editor. That&#8217;s about the block box. It&#8217;s only for dynamic blocks and it&#8217;s only the first iteration, though there are some, but it&#8217;s actually the first time that you can, as a developer, automatically insert a block next to another block. You can decide, okay, for every comment block, I want a like button in there. You create the like button block and then you say, &#8220;Okay, put it on every comment.&#8221; The user will be able to see that in the sidebar, but it will be automatically added, but a user can switch them on and off if they want to. So, that&#8217;s definitely for developers to dive in.&nbsp;</p>



<p><em>Joni Halabi:</em> Yeah, I just wanted to say I am particularly excited about this feature. I just recently saw that this was being added, and it&#8217;s probably no secret that I am a very big advocate of dynamic blocks. So, many of the blocks that we&#8217;ve created over at Georgetown are dynamic, and I see so many use cases for that. I think it&#8217;s going to give our users a lot of flexibility. I think it&#8217;s going to give users overall across all WordPress sites, so much flexibility and different options. I can&#8217;t wait to see where this is going. I know that this is a first iteration.</p>



<p><em>Birgit Pauli-Haack</em>: It still has some restrictions on there. Right now, it&#8217;s only working for template post types, template parts or patterns. So, it&#8217;s more usable for theme developers or those who want to change the front end a little bit and add it there. It&#8217;s a great feature to add a little shopping cart in the header of a template, shopping cart block. Yeah, there are quite a few other use cases. I could think about the like button going everywhere.&nbsp;</p>



<p><em>Joni Halabi</em>: Oh, yeah.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Another use case could be to have a little anchor link on every paragraph, so you can share it everywhere and not have to share the full page, but just the paragraph thing if you want to cite it on a different blog post or something like that. Yeah, it would be helpful. I know a few bloggers actually do that in their self-built blog site.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Do you see any other use cases off the top of your head?&nbsp;</p>



<p><em>Joni Halabi</em>: Oh, goodness. Thinking about it, I think you gave some really, really great examples. Yeah, I definitely see a lot for e-commerce usage. Maybe even have a related products block going along that e-commerce theme.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s a good one.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, I think people can get really creative with this one.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, I think so too. Yeah, so check it out. We will have the link in the show note and with all the stuff in there.&nbsp;</p>



<p>Then the editor components updates, that&#8217;s a roundup post of all the different changes in the component&#8217;s package of the editor. It has nothing to do with the WordPress components, which are totally different. There are 60 of those, but that&#8217;s different. So, it talks about the new props for the modal component, making a popup slot available in the sidebar, rewriting tooltip and tab panel to use a better accessibility library for that, improving size consistency, all different.&nbsp;</p>



<p>Those are the few off the top of my head or top of the list of those. Then there is a very nice new feature, it&#8217;s called the registerInserterMediaCategory API and Nick Tsekouras published that about a new hook or API. Yeah, depends on what it is, how you would say it. That is that you can add another category in the inserter for the image block.&nbsp;</p>



<p><em>Joni Halabi</em>: I love categorization. I think this is going to really enable people to better organize their media or organize their images. I don&#8217;t know too much about this, but this one looks like a very, very useful one.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: It definitely comes with an example code that actually adds a new open verse category to it, but it limits the search to exclude some sources. It&#8217;s just an example of that when people search in the open source category, open verse category. But other than that, there are some great comments in the example code and check it out.&nbsp;</p>



<p>Then the next one that I wanted to mention is WordPress Core, and both Gutenberg and Core now are using Playwright for all browser-based unit tests. There had been a great effort to rewrite many of the unit tests to Playwright and downsize the Puppeteer exposure of the code base.&nbsp;</p>



<p>It&#8217;s not done yet, but it&#8217;s definitely progressing very fast. Playwright just has a few advantages over Puppeteer, and most of them have to do with the browser testing. So, visual regression testing is a little bit more stable for both the Core and the Gutenberg.&nbsp;</p>



<p><em>Joni Halabi</em>: The article on this, if anybody is interested, there&#8217;s a link to Playwright documentation. There is a link to migrating tests, so that&#8217;s definitely something that&#8217;s worth checking out. If you&#8217;re in that business of writing automated tests, then it looks like it&#8217;s going to be much more stable now.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, but we still will see some flaky tests coming through the issue tracker, but I think it&#8217;s one of the oddities of the Gutenberg repo that you see flaky tests coming up and then they&#8217;re gone again because it has run through it.&nbsp;</p>



<p>Then there&#8217;s also a new admin notice function in WordPress 6.0 and Colin Stewart wrote the death note for it with new functions get admin notice and then the parameters for it and the filters and the actions and example code for that and also how to create a collection of notices so they can be output at once.&nbsp;</p>



<p>I&#8217;m not sure it&#8217;ll offset what many people see in the WordPress Admin. Right now, that is a page long admin notices for something, if that offsets that, but I think a lot of people were working on it for several years. So, I think that is really cool that it&#8217;s coming in now. Right now, I think it&#8217;s not mandatory to use.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, I think it&#8217;s going to make it easier for plugin authors to create admin notices. So, for example, if your plugin is introducing a breaking change or if your plugin requires a database update, things like that, I see a lot of those notices come across.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, no, it&#8217;s definitely raising the whole field for plugin extenders. So, this and many, many more. There are many more dev note, not many, but I would say six or seven additionally being worked on for the field guide of the release.&nbsp;</p>



<h3 class="wp-block-heading">WordPress 6.4</h3>



<p>Just an update on WordPress 6.4, October 17th is the day of release candidate one and that&#8217;s also the deadline for the field guide. We all know if it weren&#8217;t for the last minute, nothing would get done. So, also, the death notes will come in at the last minute tomorrow to get into the field guide.&nbsp;</p>



<p>People, if you haven&#8217;t tested your theme plugin or sites with a new release, now is the time. The final release is only three weeks away, and that&#8217;s only three weeks to fix things if something doesn&#8217;t work right. Not every plugin or theme developer is that. Best ones are of course updating their plugins and the themes ahead of time, but you definitely need to make sure.&nbsp;</p>



<p><em>Joni Halabi:</em> Yes, super, super important. Use that beta test or plugin and test, test, test.</p>



<p><em>Birgit Pauli-Haack</em>: Test, test, test. I wanted to give a shout-out to a plugin called Site Health and Troubleshooting, because that plugin has saved my bacon many, many times when I was working with clients for our agency. It comes from Core developers and is a switch. Remember when you want to troubleshoot something and support says, &#8220;Did you disable all plugins and themes?&#8221; Yeah, how do you do that on a live site? It&#8217;s really hard and this plugin to the rescue, because you can as an admin switch off all plugins and themes at once without affecting the front end of your website. It&#8217;s really the best plugin testing tool ever. You get all the information from the Site Health features, and then you can enable each theme or plugin one at a time without affecting the front page. You see where the error comes in.&nbsp;</p>



<p>Within minutes, most of the time, you figure out which plugin is the culprit and then get connected with the plugin support of that plugin and to make it. So, Site Health and Troubleshooting, the troubleshooting part isn&#8217;t a plugin. Site Health is built into WordPress. So, if you run into trouble, especially site owners that have no technical knowledge whatsoever, it&#8217;s really hard to disable all the plugins without offsetting this live site. Who does that? But yeah, I did for a while.</p>



<p><em>Joni Halabi</em>: Yeah, and not everybody is lucky enough to have a staging site, for example. I had never heard of this plugin, but I&#8217;m writing that down. I&#8217;m going to check that out.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Of course, there will be a link in the show notes for everyone to check it out and have a better life with updating any plugins as well as themes. Yeah, so that&#8217;s my spiel around 6.4. It was a short release cycle. There were only five Gutenberg plugin releases between 6.3 and 6.4. So, that&#8217;s only half of what other major WordPress releases had before. So, 6.2 had 10 and 6.3 had 10 too, 6.4 is only five. But also, we have very early in the year and I think over all the times when we do major plugin releases during Christmastime or holiday time. So, thank God for that, but that&#8217;s why there&#8217;s also not so many new features in the version.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, that makes sense. Yeah, it did feel fairly light. I was surprised it was coming so quickly. But yeah, no, it has been about that time.&nbsp;</p>



<h3 class="wp-block-heading">What’s Released &#8211; Gutenberg 16.8</h3>



<p><em>Birgit Pauli-Haack</em>: Yeah. Otherwise, if you do five more Gutenberg cycles, 16.8 was released at October 11. So, you would go right into the holiday time with your release, especially with the major part of the release, which is getting everything ready for beta and then getting every documentation death note written for release candidate one. So, I think this is a better way on clearing out the year, which brings us to what&#8217;s released in Gutenberg. Gutenberg 16.8 came out. Vicente Canales released it on October 11. There&#8217;s also a minor release, 16.8.1 available now, and it mainly contains its fixes and improvements that were necessary after WordPress 6.4 beta testing.&nbsp;</p>



<p>Out of the 160 PRs, still a big release. 49 were backport to the WordPress 6.4 beta releases. So, there are definitely additional bug fixes in that release. Of course, we have the show notes for the release post that Vicente published, but we go through the show notes. There is one new feature that I wanted to point out, and that is that when you edit pages in the site editor, it now has a template toggle to show the template. The site editors in 6.3 is now also the place where you can edit your content on pages or edit the page template and now you have a toggle in that. So, it&#8217;s easier and accessible. But yeah, I saw some of the feedback coming back from the call for testing that Anne McCarthy did with the site editor.&nbsp;</p>



<p>There&#8217;s still some really confusion in, &#8220;When are we editing content and when are we adding template?&#8221; There&#8217;s still something that confuses people, including people who do content editing every day and still get confused. Where am I now and what am I doing? So there&#8217;s still something to be had about that.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, I can see that. There are a lot of things that we call editors within the scope of WordPress. So, I mean, there&#8217;s the editor, the site editor, the post editor. Editor is a loaded word. I think it&#8217;s really going to come down to the UI of all of these editing structures that we have.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Then you have the person editor, the editor with the capabilities of editing stuff. So, we use the same word for a lot of things. It&#8217;s confusing and you always need to figure out the context in which you are talking about, but I saw in Gutenberg, there is actually the effort to streamline the post editor with the site editor and the widget editor and all that, the navigation editor. They&#8217;re all coming into the same iframe and have now almost all the same features with a sidebar, with a list view. So, I think that the efforts are really good to streamline those interfaces.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, for sure. There&#8217;s so much going on right now and I&#8217;m really looking forward to that effort being completed because then I think that&#8217;s the point where we&#8217;re going to get to true full site editing where everything is just on the same screen.&nbsp;</p>



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



<p><em>Joni Halabi</em>: That&#8217;s going to be a good day.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Yeah. I&#8217;m never sure if we will ever get to the completion part. Well, this is a web. Yeah, you need to let it go. Yeah. There is no perfect though. There is no complete. It&#8217;s all in flux. Yeah.</p>



<p><em>Joni Halabi</em>: It&#8217;s an evolution. Yeah.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So, what&#8217;s next?&nbsp;</p>



<p><em>Joni Halabi</em>: So the next, there are a number of updates in the block library, and the first one that I&#8217;d like to call out is one about the footnotes. So, the footnotes now using the Core&#8217;s meta revisioning, if it&#8217;s available, which footnotes in general is a very, very interesting new feature that I really want to start diving into. But yeah, this one is specifically in terms of making sure that those revisions stay in line with what&#8217;s going on with Core.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: The new feature, you&#8217;re thinking about footnotes or you&#8217;re thinking about meta revisions?&nbsp;</p>



<p><em>Joni Halabi</em>: Oh, footnotes.&nbsp;</p>



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



<p><em>Joni Halabi</em>: I&#8217;m very hard focused, but yeah, no, footnotes. I think footnotes are going to be really great, especially in terms of the blogging aspects of people&#8217;s sites. I have makeshift footnotes in the posts on my own site, so streamlining the ability to create footnotes like this is….</p>



<p><em>Birgit Pauli-Haack</em>: Especially with academic settings. Yeah, academic settings, yeah. It&#8217;s really important. Also, when you&#8217;re citing other third sources, you cannot always link from the&#8230; I think it&#8217;s easier to put it in footnotes for the reader than getting bogged down and following the link and missing the rest of the post when you link-</p>



<p><em>Joni Halabi</em>: Exactly.</p>



<p><em>Birgit Pauli-Haack</em>: &#8230; in between. Yeah.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, that and annotations too. I tend to write and I also want to annotate my work. I don&#8217;t want to necessarily lead my reader down the same rabbit hole that I am in when I&#8217;m writing the post, but if they want more information, yes, please go down to the footnotes. Take a look at this rabbit hole that I have created and then please go back to my main points.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, but footnotes are stored in post meta, but there has never been a revision feature for post metadata and that&#8217;s why it&#8217;s that particular PR phrased that way. So, it uses the meta revision once available if it&#8217;s available, and there is a track ticket that the meta revisions actually are coming into 6.4. So, it&#8217;s what comes first kind of thing, but they figured it out in that. Yeah. So, the next part I wanted to point out is adding design tools to as many blocks as possible is on the way. The login, logout block now has spacing support, which is really helpful. So, you don&#8217;t have to use the spacer anymore. You can just do it through the block as well, block sidebar.&nbsp;</p>



<p><em>Joni Halabi</em>: Yup, and then the next one is being able to set a custom color when applying an initial background image. So, I love anything that lets somebody set a custom color, because then you can really control the accessibility of that background color in case your image fails for whatever reason. You can default to that custom color and it maintains the accessibility of the page. So, if your text is white and you have a dark background image, for example, then for whatever reason you&#8217;re on a poor connection, for whatever reason, the image doesn&#8217;t load, you&#8217;re not stuck with a page that&#8217;s showing white text on top of a white background because nobody can read that. Being able to set that custom color to be that fallback for the image that hopefully loads but might not.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: I think one of the features here is also that it&#8217;s actually automatically detecting the background of the image that you load and setting it automatically, so you don&#8217;t have to think about it, because I wouldn&#8217;t think about that accessibility piece unless somebody points it out to me. Oh yeah, you&#8217;re right. Yeah, I should have set a custom color, but doing it automatically I think is one of those great features that you don&#8217;t have to think about and it really supports accessibility without making a fuss about it.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, absolutely. Especially if it&#8217;s right on that cusp where if you are a fully cited user, you might be able to read that text and you might not realize, &#8220;Oh wait, this red text on a blue background, I can read it, but maybe somebody else can&#8217;t.&#8221; Yeah, I love automation like that.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So, the next thing is default suggested links to pages. So, that&#8217;s in context of external links. So, that&#8217;s a very interesting diagram in the PR that makes me think, &#8220;Is that too complicated or is that very easy?&#8221; It&#8217;s mainly for the navigation block. When you have a third party link, it suggests that. What does it do?&nbsp;</p>



<p><em>Joni Halabi</em>: So what my takeaway from this was that I actually had a really hard time reading this diagram that&#8217;s in here, because there is a lot going on, but it seems like the suggestions that were originally coming up in the navigation lock were just everything, post pages, what have you. It seems that they are limiting that to only pages, instead of posts, which I think narrows the scope. I like this narrowing of the scope, because when you&#8217;re creating a navigation block, you&#8217;re more likely to want to link to a more evergreen page than to a post that might be fresh now, but might be out of date in six months or a year or what have you. That&#8217;s not necessarily something you want in your navigation. So, narrowing that scope I think makes it a little bit easier to find links.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, thank you so much for jumping in there. I was drawing a blank. Yeah.</p>



<p><em>Joni Halabi</em>: Yeah, absolutely.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: The navigation in terms of posts, you probably would link more to category pages where a list of posts on a certain topic are there. The narrowing down of the scope is really helpful for the user there. Yeah, absolutely. Yeah. The next one I&#8217;m really happy about because now I get a confirmation when I move a post to trash.&nbsp;</p>



<p><em>Joni Halabi</em>: We have had so many accidental deletions of the homepage.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: I was going through the developer notes and somehow I had a post published that was previously by accident deleted, came back from trash, and then had trashed in the permanent link. So, it was really, &#8220;What?&#8221; So I needed to just delete the permanent link and then it would automatically create a normal link, but it was kind of, &#8220;Huh? Why would that be?&#8221; So having a confirmation yes or no, do you really want to trash it, because it had so many ramifications to rectify that situation again. Yes, it was really hard.&nbsp;</p>



<p><em>Joni Halabi</em>: So the next one is it&#8217;s titled add template replace flow to template inspector. What it really boils down to is it looks like there is a change to just the way that you replace a template when you&#8217;re editing a page. When I was diving a little bit deeper into this, I feel like this is maybe a first pass or that there are some more passes of this to come, because I did see some comments that the UI could be streamlined a little bit more than it is, but there&#8217;s a great video that demonstrates this, where you are on the page editor.&nbsp;</p>



<p>You can go and replace a template and then it brings you to this modal where you can choose whatever template that you want. It gives you a bunch of selections. You can choose one and your page just updates to that new template and then you can just go about your day. I recommend checking that out. It might be something, especially if you&#8217;re heavily using templates, something to keep an eye on for future updates as well.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: So before it was just a dropdown box in the site bar for the pages, and now it opens up a modal. So, you actually can preview the template that you would associate it with a page if you want to change it. So, I think that&#8217;s a really good way to think about templates that &#8220;Oh, I can reorganize the content on this page by just changing another template.&#8221; I get a preview on how that&#8217;s going to look because we are all about avoiding that piece where we say safe and pray. I think Helen Hou-Sandi uses it a lot. That&#8217;s the previous way to do editing, is you do something and then you need to look at frontend how it looks, and the block editor is all about what you see is what you get.&nbsp;</p>



<p><em>Joni Halabi</em>: Before I heavily relied on preview, which some of the previous updates to the previous functionality I was very thankful for.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Oh, yeah. Then the next one were updates in the block library. The search block got some enhancements and one is to allow the space for the input field only when the form expands and not when it&#8217;s collapsed. That was always a little bit hard to place. Then the alignment and the icon button got a little correction on the width, so it looks a little bit more streamlined. The search block is an odd block. I really liked it, but it&#8217;s always a little harder for me to add it to a navigation block definitely. But even if you want to have it standalone on top of your blog post or something like that on a template, it&#8217;s always a little bit harder to organize, I think.&nbsp;</p>



<p><em>Joni Halabi:</em> Yeah, I can see that. So, the next changeup is in the site editor, and it&#8217;s something regarding the template parts. So, basically, we are no longer displaying the navigation section in the template parts details when the menu is missing, which sounds very obvious. If there&#8217;s no navigation menu, don&#8217;t display it. So, there&#8217;s some great screenshots that illustrate this in the GitHub issue. Very, very straightforward in those details. If there&#8217;s no navigation menu, you just don&#8217;t see the navigation in the details for that template part.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: These are the quality of life issues or things that you don&#8217;t know unless you read the changelog. Oh, we needed to change that. Yes.&nbsp;</p>



<p><em>Joni Halabi</em>: Right.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: The next one that I want to point out was for the font library, unfortunately, it&#8217;s not going to be in 6.4, but the management screens got a new tab and that is for the font uploads. So, if you as a user want to add additional fonts to your site, you can upload that. That was before, but now you have a separate tab for it. Before it was you needed to scroll all the way down past all the fonts and go to the upload section. Now it&#8217;s just one tab. So, it&#8217;s much easier to find. Unfortunately, for many, many people, we won&#8217;t have it in 6.4. It definitely needed more time to get finished, especially in the rest API endpoints and then have more testing going on, because I think it was only in 16.7 that it actually was merged into Gutenberg.&nbsp;</p>



<p>They tried for two beta sessions to get it actually to a place where users can really use it. There were always something. So, the release team said, &#8220;Well, I think that&#8217;s a sign that we need to have it simmer for more moments, for a few more rounds in the Gutenberg plugin and have some more testing being done because it&#8217;s not ready yet.&#8221; Yeah.</p>



<p><em>Joni Halabi</em>: That makes sense. I&#8217;m looking forward to it for the next version of Core, but that sounds like a really nice update. The next update affects the list views. So, there were some performance issues when a user or a content editor rather would come in and select all the blocks on the page, and there is now a fix for that. So, this affects pages that have just a lot, a lot of blocks. So, the example in the testing instructions says, &#8220;Add 150 or more paragraphs,&#8221; for example. So, before when a content editor would go in, open list view, do a command + A or control + A to select all of the blocks on the page and there are a couple hundred blocks, the editor would just freeze. It would just freeze up on you because that&#8217;s a lot of information.&nbsp;</p>



<p>So, this particular PR that solves that performance issue. So, they&#8217;re noting that there will be a slight delay for rendering items, but there shouldn&#8217;t be any huge, huge slowdowns to the point where it makes you think that your site is broken.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, yeah. No, that&#8217;s for the power users. It&#8217;s not uncommon to have a weakened edition with many, many things and then have a couple hundred blocks in there, because we have a separator block or a spacer block or something like that. Power users really don&#8217;t want their site to be broken especially, or losing content, especially with those large posts. The next one is the image block. With the 6.4 version, the image block becomes a light box feature with it. But this Gutenberg plugin PR that I point out now fixes actually that the duo tone has not been applied to the image in the light box.&nbsp;</p>



<p>So, you had maybe a gray filter on the duo tone filter on your image, and then people clicked on it, and then on the front end, it still has the image original colors and not the duo tone. There is a reason why there&#8217;s duo tone on an image. That was definitely a bug and it was fixed, but it was so visual that I thought we definitely want to talk about that when people tested it before. Yeah.</p>



<p><em>Joni Halabi:</em> Yeah, for sure. Next up is an accessibility fix to what might be my favorite new block or favorite new feature, footnotes. They have added aria labels to the return links. On the footnotes, when you go down, you click on a footnote, you go down to the bottom of the page, you read your footnote. There is a little link at the end of that footnote that will take you back to the main content of the page where you picked up your footnote. Now, there is an aria label, which is great for accessibility. It will tell screen reader users, &#8220;Hey, this is where I&#8217;m going back to.&#8221; Very small but impactful change for people.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, absolutely. You don&#8217;t want to lose your place in the post just because you&#8217;re following a footnote and not going back to where it was. Yeah, same for the table of content block. There have been quite a few accessibility improvements. Them missing was actually part of the reason why the table of content block that&#8217;s in the plugin actually did not make it into WordPress 6.4 because it was not complete from how you access it. Even for the abled people, it was really hard to use the table of content, because it didn&#8217;t have a whole lot of styling options. With additional accessibility of movements, now it can be tested more and in a broader reach as well.&nbsp;</p>



<p><em>Joni Halabi</em>: I would throw this under accessibility as well. There is a small fix to the patterns, where for a block pattern that is not synced, the terminology that was being used for that was they were using standard. So, this change replaces that use of the word standard, to use not synced instead for block patterns that are not synced. I think that makes it more obvious, because standards can be&#8230; What is standard? Some people might have questions, but it just brings a level of clarity to what&#8217;s going on there.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, especially in patterns, because right now, we only have two, but we will have a third type of pattern and that will be partially synced. So, a standard, what is that? So that it really brings it home. Yeah, thank you for pointing that out as well. I think I skipped over one of the documentation items that I wanted to point out for our listeners who are looking a little bit further beyond the WordPress Gutenberg usage. Oh, that&#8217;s the real-time collaboration experiment is now switched. You can switch that on in 16.8, and there&#8217;s also a document now available in the block editor handbook about the current state of the real-time collaboration experiment. So, you can follow along on what&#8217;s going to be next year for the Gutenberg editor.&nbsp;</p>



<p>There have been a lot of documentation changes, don&#8217;t get us wrong, but they&#8217;re mostly removing redundant stuff like remove the full site editing documentation because it will be in the themes handbook. Rename block hooks to block filters, because now block hooks are a different feature. So, it&#8217;s all a little bit, but the team is really working very hard to get the documentation up to par with 6.4 as well. Yeah, I think that was the changelog for 16.8, the Gutenberg plugin version. Thank you so much for going through that with me.&nbsp;</p>



<h3 class="wp-block-heading">What’s in Active Deveopment or Discussed</h3>



<p>We are now at the section what&#8217;s in active development or what&#8217;s in discussed. I would say with WordPress 6.4 almost out the door, Gutenberg developers are shifting gears now and also working on some new things.&nbsp;</p>



<p>Those need your input opinion, design use, and I share with you in the show notes four links. The first one would be a media library proof of concept in the site editor. The contributor has done some really experiment with that on how to add images right through your media library there, have a list view there. Now, list view, not from the editor but from a list of media and how you can navigate that and how you can preview that and all that. So, that&#8217;s really a first version of it. Take a look. It&#8217;s not yet merged. The PR itself has been closed. I just see that, but there is a replacement of that, right?&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah. That PR in particular is labeled as purely an experiment, but at the top of that PR, there is a great video that demonstrates this proof of concept, which I personally really like it. I think it&#8217;s far more intuitive. It only shows the list view. There is also a grid view that if you dive a little bit more into the PR, you can see some screenshots of the grid view as well.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: The developer now that his experiments, he went through them, he now opened a tracking issue on GitHub called Collaboration Media Library. I&#8217;m sure there will be quite a few discussion threads going on there. The whole feature is now divided up into certain tasks and defines a little bit more than scope and all that. So, you can read up more about what the developers are thinking right now.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, this is exciting. It&#8217;s nice to see the media library getting a little bit of love here.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, it definitely needs a lot of love. Yes, I have seen tickets or track tickets that are 18 years old and you say, &#8220;Okay, yeah, I wonder if we ever get categories for our media libraries or better views or bulk updates, all kinds of things.&#8221; So if you look at the track tickets that are concerned in the media library, there are quite a few that could use some love.&nbsp;</p>



<p>All right. The second link of what active development or discussed is introduce an experimental form and input blocks to allow building basic forms. So, the ecosystem of WordPress has a huge amount of plugins that help you with creating forms. Forms are very, very important. A lot of interactivity is built on top of forms and there has been a 15-year history of what forms need to be or could be.&nbsp;</p>



<p>Ari did an experiment to figure out, &#8220;Okay, if we had a standard on how blocks are built for forms, maybe the plugins can build on top of the standards.&#8221; Then when you switch out the plugin for forms, it wouldn&#8217;t destroy all your forms and you had to recreate them. Of course, some of the plugins have imports of other plugins forms, but that&#8217;s just good common sense because otherwise they wouldn&#8217;t be able to sell to existing customers or those who have existing forms. That is definitely something that&#8217;s merged in Gutenberg already.&nbsp;</p>



<p>It&#8217;s an experiment, so when you activate Gutenberg in your website, you could scroll down to the menu Gutenberg and then there is a section there called experiments. There you can switch on the experiment you are interested in. So, this one actually also deals with block bindings, data bindings, and that kind of thing. So, it&#8217;s going to be really interesting to see what you think when you use it.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, this is an exciting one because I can see in the future people creating block patterns for just really common use cases. So, the demo video shows like a send a message pattern, but I see patterns all over the internet for subscribe to my newsletter, get on my mailing list, things like that. Forms are so common on sites in general. I&#8217;m excited about this one too.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, all really good too. There are even some plugins that actually provide input blocks already, but also, it narrows down the openness again when you have to have a separate plugin for your forms and then what happens afterwards when you don&#8217;t use the plugin anymore.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, exactly. Having this just part of Core is great.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, it&#8217;s really good. Then the third one is for the insiders of using React quite a bit is that the default JSX import is done through React rather than the WordPress elements package. So, it automatically updates when React updates and the front page of WordPress elements package is actually a wraparound the React package. So, taking it out, taking the JSX feature out of that makes it more streamlined with React.&nbsp;</p>



<p><em>Joni Halabi</em>: Yeah, for sure. Just for clarity, for block creators, this should not affect your code at all. This is really just how JSX is getting pulled in. So, if you&#8217;re using JSX, you should not need to change anything. This is really a very backend change.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, and the WordPress elements package will still be around because it&#8217;s already in Core and there is this backwards compatibility promise as well. Yeah, yeah. So, thank you for pointing it out. There&#8217;s always this fear. Are there breaking changes? Yeah.</p>



<p><em>Joni Halabi</em>: That was my first thought when I read that one actually. That&#8217;s why I wanted to point it out.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, thank you. So, good to have you on the show, Joni. You pointed out quite a few things that I didn&#8217;t think about. So, yeah.&nbsp;</p>



<p>So, the last one on the section what&#8217;s active or what&#8217;s discussed is that the Gutenberg has now new labels for the data views. Normally, I wouldn&#8217;t point out new labels at the Gutenberg repo that come and go. I think we have about 400 or so labels there. So, yeah, I wouldn&#8217;t do it on the podcast. But with the new admin changes that are coming with the Gutenberg phase number three, many people want to be on the forefront or want to keep track of what&#8217;s happening. Do I have to change things or can I influence how it&#8217;s going and stay on top of it? This new label was created to label for the data views work.&nbsp;</p>



<p>So, every time there is a custom post type list or a media list in various things, so that in the WP Admin, like your post list, it&#8217;ll all be reimagined in the site editor paradigm kind of thing. The label tracks the high level work for that. So, you can really follow along with that and even subscribe to that without getting the fire hose of the rest of the Gutenberg repo that has a lot of issues and PRs every week.&nbsp;</p>



<p>I think we are at the end of our show today, and I ask every special guest in that section now. So, Joni, if there&#8217;s anything that you want to announce or you want to point out that you didn&#8217;t get a chance to talk about because you didn&#8217;t get a chance, now is your chance.&nbsp;</p>



<p><em>Joni Halabi</em>: Oh, my.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: How can people reach you? What are you working on? Is there something exciting in your life that you released?</p>



<p><em>Joni Halabi</em>: Nothing coming just yet. I did a talk a little while ago at WordPress Accessibility Day that I think the recordings are coming out. I don&#8217;t know if they&#8217;re already out, but I will announce it on my socials. I am @JoniHalabi almost everywhere, and you can also find me&#8230; I infrequently blog at my website, which is <a href="https://jhalabi.com/">jhalabi.com</a>.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Well, yeah, thank you for pointing out the WordPress Accessibility Day. So, what did you present about, what&#8217;s your talk about?&nbsp;</p>



<p><em>Joni Halabi</em>: It was actually a plugin that I initially created a while ago. I call it Besan Block, but it is essentially a way to create accessible SVG bar charts on your website and it integrates with Google Sheets. So, you can automatically import your content from a Google sheet and it will create a bar chart. It&#8217;s accessible and tabable and readable by screen readers. So, I walked folks through how to do that. The primary focus of that particular talk was the creation of the accessible SVG.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Okay. Yeah, so I&#8217;m definitely going to mention that in the show notes as well. Is that plugin available in the repo or is it on GitHub?&nbsp;</p>



<p><em>Joni Halabi</em>: It is. It&#8217;s available in GitHub, but it is also in the WordPress plugin directory. It is called Besan Block, B-E-S-A-N.</p>



<p><em>Birgit Pauli-Haack</em>: B-E-S-A-N. Okay. I&#8217;ll find it. Thank you so much. Yeah. Thank you for being on the show. As always, the show notes, dear listeners, will be published on gutenbergtimes.com/podcast. This is episode 91. If you have any questions or suggestions or news that you want us to include the next time, send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. That&#8217;s an email address and it&#8217;s <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. So, thank you so much, Joni, for joining us today. Thank you all of the listeners for listening. If you want, it would be really, really helpful if you would do a review on your favorite podcast app.</p>



<p>We haven&#8217;t had any reviews because we didn&#8217;t ask for it, but it always helps with the distribution of the changelog. Absolutely, you will get it read on the next episode. So, there&#8217;s a little shout-out if it&#8217;s a good review of course. Maybe if it&#8217;s a mediocre review. All right. So, that&#8217;s it. Thank you for listening. Goodbye, and I&#8217;ll talk to you in probably four weeks. Thank you so much.&nbsp;</p>



<p><em>Joni Halabi</em>: Thank you, everybody.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Oct 2023 12:52:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:38;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:119:"Do The Woo Community: Maintaining Client Relationships and Providing Evolving Services with Julia Eden and Matt Woodman";s: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=77154";s: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:118:"https://dothewoo.io/maintaining-client-relationships-and-providing-evolving-services-with-julia-eden-and-matt-woodman/";s: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:510:"<p>In this Woo AgencyChat Julia Eden and Matt Woodman from Atomic Smash talk about evolving services, accessibility, UX/UI design and more.</p>
<p>&gt;&gt; The post <a href="https://dothewoo.io/maintaining-client-relationships-and-providing-evolving-services-with-julia-eden-and-matt-woodman/">Maintaining Client Relationships and Providing Evolving Services with Julia Eden and Matt Woodman</a> appeared first on <a href="https://dothewoo.io">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Oct 2023 11:38: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: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:39;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:12:"Matt: Wowza!";s: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:23:"https://ma.tt/?p=101511";s: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:"https://ma.tt/2023/10/wowza/";s: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:1610:"<img width="604" height="340" src="https://i0.wp.com/ma.tt/files/2023/10/IMG_1643-edited-scaled.jpeg?resize=604%2C340&ssl=1" alt="" class="wp-image-101520" />



<p>Okay, I&#8217;ve seen a lot of things in my life, but this has me fairly floored. I was at an <a href="https://ecoamerica.org/">EcoAmerica</a> board meeting dinner and afterward instead of calling an Uber like I usually would, I tried a self-driving car, a <a href="https://waymo.com/">Waymo</a>. (The name inspired by my friend, <a href="https://jaimewaydo.com/">Jaime Waydo</a>.) As I got home I was so excited to tell my Mom what just happened.</p>



<p>I feel like every cell in my body is charged, it&#8217;s like the first time I got a script to run, or committed code into b2/cafelog, this is definitely a before and after moment. Here&#8217;s a video as the car arrived and I got out. I&#8217;m really at a loss for words. The &#8220;wow&#8221; you hear me say in one of my most genuine in my life. The thing is <em>I know</em> these self-driving cars exist, I&#8217;ve seen them around San Francisco forever, but the <em>experience</em> of being picked up and dropped off by a robot navigating the tricky SF hills and streets just hits different.</p>



		
			<div class="jetpack-videopress-player__wrapper"> </div>
			
		
		


<blockquote class="wp-block-quote">
<p>“The future is already here – it&#8217;s just not evenly distributed.&#8221; </p>
<cite>William Gibson</cite></blockquote>



<p>One thing that always brings me back to San Francisco is you feel like you&#8217;re living in the future. Tonight was no exception.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Oct 2023 03:54:01 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:94:"WPTavern: Kinsta Launches Free Static Site Hosting for Up to 100 Websites, Including WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=150341";s: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:104:"https://wptavern.com/kinsta-launches-free-static-site-hosting-for-up-to-100-websites-including-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4911:"<p>Kinsta <a href="https://kinsta.com/changelog/static-site-hosting/">launched its static site hosting</a> product today, making a strong entrance into the market with a free tier that is competitive with established solutions from Vercel, Netlify, and GitHub Pages. Companies can host up to 100 static sites for free, including static WordPress sites, which Kinsta deploys from its global edge network of more than 300 locations.</p>



<p>Static sites are those that serve HTML pages, media, and assets like JavaScript and CSS. These are usually more suitable for brochure websites, landing pages, personal portfolios, and other simple sites that don&#8217;t require pages to be dynamically generated by code running on a server. Static sites are generally more performant and secure.</p>



<p>Kinsta&#8217;s free static hosting tier comes with the following features and limitations:</p>



<ul>
<li>1 concurrent build/site</li>



<li>100 sites/company</li>



<li>600 build minutes/month/company</li>



<li>100 GB bandwidth/month/company</li>



<li>1 GB build size limit/site</li>



<li>API access</li>



<li>Integration with GitHub, GitLab and BitBucket</li>



<li>Diff-based Uploads</li>



<li>Custom domains</li>



<li>Free SSL support</li>
</ul>



<p>Customers can host pre-built static sites or sites built with static site generator frameworks that use Node.js. Kinsta has created <a href="https://kinsta.com/docs/static-site-hosting/static-site-quick-start-examples/">quick start example repositories</a> for many popular static site generators, including Astro, Cuttlebelle, Docusaurus, Eleventy, Gatsby, Nuxt, Qwik, React, React with Vite, and VuePress.</p>



<p>WordPress users can also deploy static sites to the platform and host it for free by converting an existing site to static. Kinsta published a <a href="https://kinsta.com/blog/static-wp-site/">tutorial</a> on the process for converting a WordPress site using a free plugin. The static hosting can also be used to set up a frontend with any kind of backend or host a headless WordPress site.</p>



<img width="1105" height="1039" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/static-wp-add-static-site.png" alt="" class="wp-image-150366" />



<p>Users can launch a static site to Kinsta&#8217;s infrastructure by deploying from a Git repository hosted by BitBucket, GitHub, or GitLab, selecting a branch, and adding a build command and directory to deploy. Kinsta can detect some static site generators automatically, which makes the process easier. A connection and configuration settings can be managed through the MyKinsta dashboard. </p>



<img width="960" height="935" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/10/kinsta-static-site-build-settings.png" alt="" class="wp-image-150362" />



<p>Kinsta plans to introduce add-ons and other features in the future that might be paid, but is committed to keeping the service and this tier free forever.</p>



<p>&#8220;Just like with every free product or freemium model, our goal is to spread the word with the help of it and let users try out our service, the dashboard in a frictionless way and host a project here for completely free,&#8221; Kinsta Chief Business Officer Tom Zsomborgi said. </p>



<p>&#8220;The ability of using and testing out a platform and getting first hand experience is the ultimate way of forming an opinion about a provider. We let everyone use the service and host their projects. If the developers and agencies like the Static product we hope they will consider us for their other web projects and start using the paid services.&#8221;</p>



<p>Kinsta is targeting enterprises, agencies, and companies that need to create websites and landing pages for high-traffic campaigns. The company is working on more features for static site hosting, including the following on the roadmap:</p>



<ul>
<li>Wildcardless domains</li>



<li>Extended Kinsta API support</li>



<li>Serverless functions, which could be utilized by static sites</li>



<li>Previews</li>



<li>Maintenance mode</li>



<li>Password protection</li>



<li>Ability for HTML Forms to work</li>



<li>More builders</li>



<li>Choose a build template</li>



<li>Detailed Analytics</li>
</ul>



<p>Kinsta&#8217;s static site hosting solution is similar to what the competition offers for building and deploying sites, but Zsomborgi said he thinks that having application, database, and WordPress hosting all under one roof sets them apart. Kinsta also offers analytics for free and unlimited users/seats, the same as Vercel, but Netlify only offers these under paid plans.</p>



<p>&#8220;The biggest things that we are missing are functions (Vercel, Netlify, and Cloudflare Pages have them) and deploy previews,&#8221; Zsomborgi said. &#8220;Both of those are in the backlog and will be released soon.&#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, 18 Oct 2023 22:18:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:44:"WordPress.org blog: A New WordPress Showcase";s: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=16173";s: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://wordpress.org/news/2023/10/a-new-wordpress-showcase/";s: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:4919:"<p>The <a href="https://wordpress.org/news/category/meta/">journey to update WordPress.org</a> continues with the launch of a new <a href="https://wordpress.org/showcase/">Showcase</a> design. The Showcase is a natural starting point for visitors arriving on WordPress.org, and it both inspires creativity and demonstrates what’s possible with WordPress. From unique personal blogs and portfolios to enterprises and celebrity fan sites, the Showcase celebrates WordPress’s flexibility, popularity, and the freedom to own one’s content.</p>




<img width="1024" height="954" src="https://i0.wp.com/wordpress.org/news/files/2023/10/2-showcase-site-1.png?resize=1024%2C954&ssl=1" alt="Screenshots from the new Showcase design" class="wp-image-16187" />



<img width="1024" height="954" src="https://i0.wp.com/wordpress.org/news/files/2023/10/3-showcase-starry-theme-1.png?resize=1024%2C954&ssl=1" alt="A grid of new design elements" class="wp-image-16184" />



<img width="1024" height="576" src="https://i0.wp.com/wordpress.org/news/files/2023/10/4-showcase-websites-curaction-1.png?resize=1024%2C576&ssl=1" alt="A collage of Showcased websites" class="wp-image-16185" />




<p>This new design provides much-needed improvements to the aesthetics and user experience. It emphasizes bold visuals and a more dynamic browsing experience through tags and categories. Individual site pages now include desktop and mobile screenshots, while the site introduces an improved layout on mobile devices.&nbsp;</p>



<p>This redesign also brings new <a href="https://wordpress.org/blocks/">block-based functionality</a> and several components that will be used elsewhere on WordPress.org. All of this was made possible through collaboration between Design, Marketing, and Meta teams. Thank you to everyone.</p>



<p class="is-style-wporg-props-medium"><a href="https://profiles.wordpress.org/adamwood/" class="mention"><span class="mentions-prefix">@</span>adamwood</a> <a href="https://profiles.wordpress.org/alexstine/" class="mention"><span class="mentions-prefix">@</span>alexstine</a> <a href="https://profiles.wordpress.org/annezazu/" class="mention"><span class="mentions-prefix">@</span>annezazu</a> <a href="https://profiles.wordpress.org/bengreeley/" class="mention"><span class="mentions-prefix">@</span>bengreeley</a> <a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a> <a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a> <a href="https://profiles.wordpress.org/dufresnesteven/" class="mention"><span class="mentions-prefix">@</span>dufresnesteven</a> <a href="https://profiles.wordpress.org/eidolonnight/" class="mention"><span class="mentions-prefix">@</span>eidolonnight</a> <a href="https://profiles.wordpress.org/fcoveram/" class="mention"><span class="mentions-prefix">@</span>fcoveram</a> <a href="https://profiles.wordpress.org/joen/" class="mention"><span class="mentions-prefix">@</span>joen</a> <a href="https://profiles.wordpress.org/jonoaldersonwp/" class="mention"><span class="mentions-prefix">@</span>jonoaldersonwp</a> <a href="https://profiles.wordpress.org/jpantani/" class="mention"><span class="mentions-prefix">@</span>jpantani</a> <a href="https://profiles.wordpress.org/laurlittle/" class="mention"><span class="mentions-prefix">@</span>laurlittle</a> <a href="https://profiles.wordpress.org/matt/" class="mention"><span class="mentions-prefix">@</span>matt</a> <a href="https://profiles.wordpress.org/markoserb/" class="mention"><span class="mentions-prefix">@</span>markoserb</a> <a href="https://profiles.wordpress.org/ndiego/" class="mention"><span class="mentions-prefix">@</span>ndiego</a> <a href="https://profiles.wordpress.org/pablohoneyhoney/" class="mention"><span class="mentions-prefix">@</span>pablohoneyhoney</a> <a href="https://profiles.wordpress.org/paulkevan/" class="mention"><span class="mentions-prefix">@</span>paulkevan</a> <a href="https://profiles.wordpress.org/renyot/" class="mention"><span class="mentions-prefix">@</span>renyot</a> <a href="https://profiles.wordpress.org/ryelle/" class="mention"><span class="mentions-prefix">@</span>ryelle</a> <a href="https://profiles.wordpress.org/sereedmedia/" class="mention"><span class="mentions-prefix">@</span>sereedmedia</a> <a href="https://profiles.wordpress.org/_dorsvenabili/" class="mention"><span class="mentions-prefix">@</span>_dorsvenabili</a></p>



<p>If you would like to propose a change or report an issue, please do so in the <a href="https://github.com/WordPress/wporg-showcase-2022">wporg-showcase-2022</a>&nbsp; GitHub repository. Also, make sure to join the <a href="https://wordpress.slack.com/archives/C04U953K77A">#website-redesign</a> Slack channel if you are interested in additional updates coming to WordPress.org and want to contribute.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 18 Oct 2023 17:34: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:17:"Nicholas Garofalo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:42;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:92:"WPTavern: #95 – Pooja Derashri on Diversity, Equity, Inclusion, and Belonging in WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=150290";s: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:103:"https://wptavern.com/podcast/95-pooja-derashri-on-diversity-equity-inclusion-and-belonging-in-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:39320:"Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name 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, how we can promote diversity, equity, inclusion, and belonging in the WordPress project and community.</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. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.</p>



<p>So on the podcast today, we have Pooja Derashri. Pooja is a co-founder of WPVibes, a plugin development company based in India. With a passion for WordPress, pooja has been actively involved in the community since 2013. Her journey as a contributor began in 2017 when she attended her first local WordCamp. Her expertise and dedication have under various key roles in the WordPress ecosystem. She currently serves as co-team rep for the training team, and GTE for the Hindi local. In addition, she holds key positions in the WordPress release squad for version 6.3 and 6.4, where she heads up the test team.</p>



<p>Pooja shares her insights on the importance of diversity, equity, inclusion, and belonging within the WordPress community, and explores how you don&#8217;t need to be a coder to be a part of the community and all that it is.</p>



<p>We discussed the work of teams like polyglots, who focus on translating WordPress projects into different languages, and docs, who provide much needed documentation to help users understand and contribute to the platform. These initiatives alone make it clear that WordPress is reliant on non-coding contributions, and there are more ways to contribute than have a before.</p>



<p>I ask Pooja about her experiences with diversity and inclusivity in the tech industry, and she reflects on the challenges she has faced, discussing the importance of recognizing and addressing unconscious biases. She shares her insights on the need for training and workshops that empower diverse individuals to contribute and speak up within the WordPress community.</p>



<p>We delve into Birgit Olzem&#8217;s proposal to form an official D E I B team within WordPress, aiming to implement diversity, equity, inclusion, and belonging throughout the whole community. I express my excitement about the potential outcome of this proposal, and we think about how WordPress compares to other parts of the tech industry.</p>



<p>We explore the various initiatives and efforts being made to build a more inclusive WordPress culture. From mentorship programs, to targeted outreach and safe spaces, we uncover the ways in which underrepresented voices are being uplifted.</p>



<p>If you&#8217;re interested in creating a more inclusive community, this episode is for you.</p>



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



<p>And so without further delay, I bring you Pooja Derashri</p>



<p>I am joined on the podcast today by Pooja Derashri. Hello Pooja!</p>



<p>[00:04:09] <strong>Pooja Derashri:</strong> Hi Nathan. So glad to join you.</p>



<p>[00:04:12] <strong>Nathan Wrigley:</strong> Yeah thank you for joining me today. We&#8217;re going to be talking a little bit today about a subject which you may well have heard me talk about before. I had an interview with Jill Binder and Birgit Olzem quite recently. This episode is going to follow on shortly after that. We&#8217;re going to be talking about an acronym, DEIB or Diversity, Equity, Inclusion and Belonging.</p>



<p>Before we get into the subject at hand though. Pooja I wonder, would you mind just introducing yourself? Tell us a bit about who you are, where you are, and what it is that brought you to WordPress, what it is that you do within WordPress and so on?</p>



<p>[00:04:50] <strong>Pooja Derashri:</strong> Yeah. My name is Pooja Derashri, and I am from India. I&#8217;m a co founder of WPVibes, a plugin development company, and I am also a WordPress contributor. Currently I&#8217;m a co team rep for the training team and GTE for Hindi locale. Along with this, I&#8217;m also in the WordPress release squad for 6.3 and 6.4, where I&#8217;m leading the test team.</p>



<p>Basically I&#8217;ve been working in WordPress since 2013. But my contribution journey started in 2017 when I was first introduced to WordPress community in one of the local WordCamps.</p>



<p>[00:05:30] <strong>Nathan Wrigley:</strong> That&#8217;s an amazing story. You&#8217;ve got a lot of past, and heritage, and interest in the community. I&#8217;m guessing if you are part of the WordPress community and you&#8217;ve been part of the release squad, and it sounds like you are attending events and things like that as well. You&#8217;ve got a real interest in the community being diverse, equitable, inclusive, and the last word in the acronym, belonging.</p>



<p>Do you want to just tell us a little bit about how you came to be interested in this subject? Obviously, if you&#8217;ve got a plugin development company, one might expect that all of your endeavours would be towards coding and plugins and documentation and all of those kind of things, but clearly not. You&#8217;ve got an interest in all of these things. Tell us why it is that you&#8217;ve found this to be important.</p>



<p>[00:06:13] <strong>Pooja Derashri:</strong> Yes. Basically I have a short story to tell about. In my region, where I&#8217;m belonging, there is a conception that women are not good for tech jobs and women can&#8217;t do coding. In my first job there were members of 10 to 12 in my company. They have a stereotype thinking that women are not for the tech jobs, women are not good for tech jobs. And at that time I feel like an outsider, and I&#8217;m not good for that.</p>



<p>In that company they were not giving me challenging tasks, and they were just giving me simple, easy tasks. So I was thinking like, what am I doing here? Then soon I realised, I switched from that company, in just two months. Then I joined a different company which is far better than that company.</p>



<p>And there I got respected. I was welcomed. They gave me equal chances to work, and they gave me equal opportunities to work on coding. That was quite a nice experience. If I was not being treated unfairly, then I would never know about how that feeling was.</p>



<p>When I got that feeling, then I searched about and heard in a workshop, what is DEIB, and why it matters? And I just connected the dots, like I similarly faced that issue in my first job and I should do something about it. So in my opinion diversity is all about making sure that everyone feels welcome, respected and treated fairly no matter who they ,are.</p>



<p>[00:07:52] <strong>Nathan Wrigley:</strong> Thank you. That&#8217;s a really interesting story that you&#8217;ve got there. I wonder if we might just delve into that a little bit more deeply. You obviously had two fairly different experiences there. One, which was fairly negative, and you wish to separate yourself from that company and go and work at a different company. And it sounds like that was a much better experience.</p>



<p>You&#8217;re obviously coming out of India on this call today. Do you feel that this is a problem which is systemic where you live? Do you, in other words, feel that this bias, for want of a better word, this lack of diversity and equity and inclusion, is something which is endemic where you live? So what I&#8217;m really asking is, do you think that there&#8217;s a problem in your part of the world that maybe isn&#8217;t quite so pronounced in other parts of the world?</p>



<p>[00:08:44] <strong>Pooja Derashri:</strong> Yeah. Actually I come from a rural background where people have held certain fixed mindsets, and they are being biased in some situations. So yeah, we can say that they are not treated, they are thinking like this tech world is only for male or something like that, particularly in my region.</p>



<p>I&#8217;m not talking about the whole of India. We have some better mindsets, and better conceptions in other part of India. But in my region, in my small city, that is a very unfair, or we can say biased, conception or misconception.</p>



<p>[00:09:23] <strong>Nathan Wrigley:</strong> Thank you for that. I wonder if there&#8217;s legislation in place in your part of the world to tackle this kind of thing. And whether or not there&#8217;s legislation, doesn&#8217;t of course mean that it does not happen, I think the same would be true in other parts of the world as well. Simply because there are laws to prevent this kind of thing, doesn&#8217;t mean that those laws are obeyed.</p>



<p>So quick question around that, we&#8217;ll go off piste for a moment. In the part of the world where you are, is there laws around this kind of thing, around discrimination and inclusion? In other words, from a legal point of view, is this not tolerated?</p>



<p>[00:09:58] <strong>Pooja Derashri:</strong> Yes we have very tough laws on these things. But we can&#8217;t change any person&#8217;s conception. But I was lucky enough that my parents were not thinking that if a female can do that. They gave us equal rights. For my in laws, they gave me the equal opportunities and encouraged me, motivated me always to do whatever I wanted to do. So it&#8217;s about the few people in my first company. They had that mindset but not every people is going with the same mindset.</p>



<p>[00:10:35] <strong>Nathan Wrigley:</strong> I have a follow up question, and it&#8217;s about the place where you described first, the job where that organisation wasn&#8217;t particularly diverse, and they certainly don&#8217;t sound like they were particularly inclusive. Was there any part of you that felt like throwing in the towel? And what I mean by that is just thinking okay this is what tech is like, I&#8217;m just going to change industry altogether.</p>



<p>Now it sounds like you have got a background where you described your parents making sure that everything was equal for you. But despite that, did you at any point think well if this is what the tech industry is going to be like, I&#8217;m not going to be a part of it?</p>



<p>And I wonder really if that&#8217;s the root of the problem here. In that we&#8217;re trying to get it to the point where no person, no matter what their background is, no matter what their ethnicity is or religion or whatever it may be. Where they feel that they can&#8217;t be part of the industry because they&#8217;re getting signals from their employers, and the industry more broadly that they don&#8217;t belong. So yeah, the question basically is, did you ever feel like, okay I shan&#8217;t be part of tech if this is what it&#8217;s going to be like?</p>



<p>[00:11:43] <strong>Pooja Derashri:</strong> No, I never thought that. I was always encouraged by my close circle that you should do whatever you want, despite what other people think. You should face that problem and overcome from that.</p>



<p>I thought in my first job that if they are not accepting me and they are not finding me good enough then, why shouldn&#8217;t I change the job? I can&#8217;t change their mindset but I can change my job. I can change my company.</p>



<p>[00:12:13] <strong>Nathan Wrigley:</strong> Yeah that&#8217;s a very enlightening approach, isn&#8217;t it? Okay so you&#8217;ve laid out what the problem is. I think this question may be not particularly relevant, but I would be interested to know. Why do you find this to be so important a cause? I mean it&#8217;s obvious the answer to that, isn&#8217;t it? But I want to hear you express in your own words why you&#8217;ve attached yourself to this and why you believe it&#8217;s important.</p>



<p>[00:12:36] <strong>Pooja Derashri:</strong> DEIB basically means we are making a big circle of friends where everyone is invited, treated fairly and feels like they are one of them. And it is important because when people work, play, and live together with love and respect, then the world becomes a happier and stronger place for everyone.</p>



<p>When we talk about open source projects, open source projects make sure that everyone is included and feels they belong to this community. It encourages other people to come and share their skills.</p>



<p>So it is important basically because our world will be more happier, stronger, and people live with peace and harmony. If they are not biased, they are living together with respect. All person are welcomed.</p>



<p>[00:13:29] <strong>Nathan Wrigley:</strong> What a lovely answer. I&#8217;m really quite touched by that, that&#8217;s beautiful. The next thing that you wanted to talk about is really interesting to me, because I haven&#8217;t given this too much thought. And it&#8217;s the idea that the problem may not be something that people are necessarily conscious of. And in the share notes that you&#8217;ve shared with me, you&#8217;ve talked about this thing called unconscious bias. And I have an intuition as to what you&#8217;re meaning there but I&#8217;d like you to explain that. What is unconscious bias? Let&#8217;s delve into that a little bit.</p>



<p>[00:14:01] <strong>Pooja Derashri:</strong> Basically, a sneaky or hidden friend in your mind, brain. Who sometimes make a decision for you, without you even realising it. For example, imagine your favorite color is blue. Sometimes without thinking much, you choose blue color in everything, because your brain automatically likes them. What if that happens with people not color? If your mind is unconsciously like a certain kind of people then you will be not inclusive in environment.</p>



<p>[00:14:35] <strong>Nathan Wrigley:</strong> So the idea being that, and I guess we can all admit to this in many aspects of our lives, we have things that instinctively, we can&#8217;t quite necessarily understand why, there are certain things that we are drawn to. The taste of a particular meal, a particular color, the kind of vacation that you want to go on, the kind of things that you like to do in your spare time.</p>



<p>We have all of these biases, that have crept into our lives over time, and we may not be aware of them but they impact the decisions that we make. So we may feel that we&#8217;re being equal and thoughtful, and we&#8217;re giving everybody the greatest opportunity possible. But somehow, somewhere, our brain is stepping in and making a slightly different decision.</p>



<p>So if that&#8217;s the case, how do you spot your unconscious bias? Because, by definition, it&#8217;s unconscious. You&#8217;re unaware that it&#8217;s happening, but clearly there must be a way of short circuiting that problem, and figuring out, okay take a step back, have a think about that, was that the right decision? What&#8217;s the conversation that you need to have with yourself or your colleagues, or whatever it may be?</p>



<p>[00:15:38] <strong>Pooja Derashri:</strong> Yeah. When you or your colleague indicate that you are facing unconscious biased to someone, for example, I will explain this with a core contributor example. Like imagine two programmers submitting code changes to a project. One programmer is well known to the community, and the other is new and less known, less famous.</p>



<p>Due to our unconscious bias, the community might pay more attention to the code changes from the well known programmer, assuming that they are of higher quality. But it is not like that. Your newcomer can be a good coder and he might of submitted a nice or similar coding. This can lead to the new programmer&#8217;s contribution being overlooked or undervalued.</p>



<p>If we are doing this kind of bias then we are not doing intentionally. This is something unconsciously we are doing, if we say about in open source. So when someone indicates this to us, first we should accept that we are becoming a biased person for some particular coder, or some particular person. Then we should self realise that how we can give both of them a fair chance by looking into their code or by giving them fair opportunities.</p>



<p>[00:16:59] <strong>Nathan Wrigley:</strong> It&#8217;s very difficult, isn&#8217;t it, to be as reflective as that. So I would imagine that in almost any unconscious bias that you may have, be it towards code or, you know the kind of food that you like, there is something very deep in that. And so when somebody points it out that you have a bias, sometimes the shutters go up if you like, and you feel that that&#8217;s a, well I guess you could describe it as a personal attack.</p>



<p>You&#8217;ve been biased there. You&#8217;ve clearly exhibited some bias. It&#8217;s not always straightforward to admit to yourself that you have these biases. And so I guess that&#8217;s the enterprise that we&#8217;re going to discuss now. How do we build an inclusive culture? In which people are able to recognise that, yes they have biases, yes they need to pay attention to that, or at least listen to other people&#8217;s opinions.</p>



<p>So let&#8217;s move on to that. Your third point, if you like, building inclusive cultures. Before we get into the meat and the bones of that, I&#8217;d like to ask what you think broadly about how WordPress as a community is doing with all of this. Because it feels like at the moment this is a particularly hot topic, for want of a better word. It feels like it&#8217;s getting lots of coverage, lots of endeavors are being made.</p>



<p>I&#8217;m not making the claim that everything is perfect, but it feels like this is a conversation which is becoming increasingly normal. We&#8217;re constantly being told about this and we&#8217;re constantly alert and aware of this. So, how do you think we do as a community, the WordPress community? What can we do, and how are we doing?</p>



<p>[00:18:32] <strong>Pooja Derashri:</strong> Actually in my perspective taking the DEIB initiative doesn&#8217;t mean just ticking the boxes. It is all about where people feel they are among all of us. And nurturing the community of where everyone feels respected, valued, and their voices are heard. As you said, this is already a hot topic that is discussed everywhere in the community right now.</p>



<p>Few of the initiatives, in my opinion, are very great, WordPress community is taking. Like WordPress 6.4 release, it is lead by all women, and non binary people. So that many underrepresented people will get a chance to be part of the release squad, in spite of their background or something.</p>



<p>In another way, if we speak about workshop, that is a great initiative. Like Jill Binder is doing workshops on diversity in every part of the world. And for a few years Jill Binder has been running a workshop, and promoting and uplifting diverse people who are not so comfortable in public speaking, but are expert in their respective fields. There she&#8217;s uplifting them, and creating an inclusive environment. So they feel comfortable, and can deliver their talk, and can be a part of this WordPress family.</p>



<p>And one of the great examples, great initiatives taken by Birgit Olzem, she submitted a proposal for forming an official Make WordPress DEIB team, so that DEIB can be implemented in every aspect of WordPress, with every WordPress Make team, and can align with other make teams.</p>



<p>This will be discussed in the community summit. I guess today this is going to be discussed. I must say I&#8217;m really excited, what happened and what the outcome and decision was made on this topic. And I would be really happy if this team was to be in existence.</p>



<p>And if you heard about a month ago, there was a mentorship program initiated by Hari Shanker. Initiatives taken by Hari Shanker started a project called Mentorship Program, Contributor Mentorship Program. In this a dedicated mentor is assigned to a mentee, or what we say, new contributor who wants to contribute to WordPress, but doesn&#8217;t know how to contribute, how to start.</p>



<p>So the mentor can guide them, and help them to onboard as a contributor. Basically they are creating a path for them to feel included in this environment and get settled. As soon as they join they feel belonging. They have a sense of belonging in this WordPress community as soon as they join.</p>



<p>So it was great I must say. It was a pilot project but it was a great success. So many contributers who are now regularly contributing to the WordPress projects, and bringing their fresh ideas and innovation to that. So these are a few examples or initiatives community is taking now.</p>



<p>[00:21:55] <strong>Nathan Wrigley:</strong> How do you feel then about how the WordPress community is doing? I should add that I will link in the show notes to the make.wordpress.org piece which is talking about the establishment of a diversity, equity, inclusion, and belonging team. And there&#8217;s also, as I said, an episode with Birgit and Jill which you can find in the WP Tavern podcast archive if you want to go a little bit deeper, but I will link to those.</p>



<p>How do you feel that wordPress as a community is doing in comparison to other parts of the tech industry? Do you feel that WordPress is perhaps at the cutting edge? Or are we taking our cues from other communities which have been there, done that, tackled this problem before us?</p>



<p>It feels a lot of the things that WordPress is doing are fairly innovative. So we are having to create, as a community, these things for ourselves. But I could be wrong about that. So perhaps we could just have a chat about whether WordPress is at the vanguard of this or not.</p>



<p>[00:23:00] <strong>Pooja Derashri:</strong> Yes, in my opinion if we go back five or ten years back in WordPress community then the WordPress community was not that diverse. But in the past few years the community is taking diversity very seriously, and taking a great initiative so every person all across the globe can share their feelings, or share their ideas, and they are implemented.</p>



<p>I&#8217;m taking one of my example, when I joined the training team in 2019, the team was gearing up for the initial WordPress launch. Then Courtney Robertson and Hauwa Abashiya was the team rep at that time. And I was like, I was having a coding background, I don&#8217;t know about how content works, and how I can contribute and help in that. They helped me in a lot in onboarding to the training team, and they helped me to learn the process. And soon after I got involved and Learn WordPress launched.</p>



<p>After that we worked hard on the training team to make it as diverse across the globe. That time from basically APAC region, there was not much contribution. So we created an inclusive environment in team, everyone can come and ask everything. We were available. We all work from different parts of the world. So we can say we were available 24 hours at that time.</p>



<p>We were trying our best to treat everyone equally, no matter where they are from. At that time I started APAC meetings to boost the contribution in this region. We run some workshops to explain what the training team, and what it does.</p>



<p>I understand the true meaning of how a diverse team can work together to raise awareness and bring all other members on board, and then they can become a part of the regular contribution.</p>



<p>[00:25:09] <strong>Nathan Wrigley:</strong> Yeah thank you. The fifth part that I&#8217;ve got written down here in our shared show notes is your desire to make sure that underrepresented voices are empowered. And I wonder if you could expand on that a little bit. What was it that you were meaning there? Who are you meaning by underrepresented? What are the things that need to be done in order to empower those voices?</p>



<p>[00:25:35] <strong>Pooja Derashri:</strong> So it depends. If we talk about the tech world, basically in the programming field there are more male coders involved in comparison. Not like I&#8217;m saying all programmers are male, but in comparison to that there are more male representative are there.</p>



<p>The lack of representation can be based on various factors just like gender, race, ethnicity, age, geographic location. There can be a more diverse perspective and less inclusive community that can be underrepresented. Few examples like female minorities, people of color, non English speakers, developing countries, accessibility advocates.</p>



<p>One more example can be non technical roles, LGBTQ+ individuals. It&#8217;s important to address the underrepresented of these groups to ensure that the WordPress community is diverse, inclusive, and welcoming to everyone. No matter who they are and what background they came from. As a community, our efforts to promote diversity and inclusion can include targeted outreach, like some mentorship programs, creating a safe space, providing them resources if they want.</p>



<p>Your question was, how can we empower the underrepresented voices? It&#8217;s crucial for creating a more diverse and inclusive environment in community, or in an organisation, or in industries, including open source or WordPress community. We can amplify their achievements like recognising and highlighting their contributions, and provide them equal opportunities and their voices are heard in bigger roles.</p>



<p>We can provide diverse leadership. We can create a safe space for them so they feel comfortable in speaking, or in putting their skills in front of everyone. Basically a long term commitment, empowering in underrepresented voices is an ongoing effort. It requires consistent dedication, and a commitment to sustainable change.</p>



<p>[00:28:02] <strong>Nathan Wrigley:</strong> I&#8217;m curious in your last little portion there you mentioned quite a few different things. When I hear conversations around diversity and inclusion and DEIB in general, there are certain topics which come into my mind, and it might be things in the community which I&#8217;ve heard of recently. So I don&#8217;t know, it might be that there&#8217;s equal representation at WordPress events, that we make sure that the speaker lineup is diverse.</p>



<p>But curious there that you listed out quite a few other things as well. So for example, just geographical, the spread of where you are on the planet. You need to think perhaps differently depending on where you&#8217;re based, and the metrics by which you would measure how you&#8217;re doing in this sphere may be different in, for example, India than it would be where I am in the UK.</p>



<p>So it doesn&#8217;t feel like there&#8217;s one size fits all. There&#8217;s no standard operating procedure for making sure this is all done correctly. Different parts of the world may be on a different journey and have a different trajectory, and have different things that they need to focus on. Would you say that&#8217;s true?</p>



<p>[00:29:10] <strong>Pooja Derashri:</strong> Yes, different parts of countries may have different perceptions regarding diversity. I agree with your point that our WordPress related events are focusing on diverse speaker lineup. If we check our WordCamp US speaker lineup, that is much diverse. And similarly in WordCamp Asia, where I was part of speaker organising teams, we put our full efforts in creating a diverse speaker lineup. So yeah, I completely add with your point. We might have different perceptions, we might have different geographical location. There are different means of diversity.</p>



<p>[00:29:50] <strong>Nathan Wrigley:</strong> Now inevitably when this kind of conversation comes around, there are always people in the community who have a very different opinion. And they have the opinion that, well really I&#8217;m only here for the code. I want to be able to download the WordPress code base, I want to be able to use WordPress, I want to make it the foundation of my business and so on and so forth.</p>



<p>And they push back and they say look conversations like this, they&#8217;re not relevant. It&#8217;s code, that&#8217;s all it is to me. What do you say to them? Clearly you would have a different opinion but, how do we get those people interested, and make it so that they feel that this is important? Because I feel that there&#8217;s quite a few members of the community who just say oh, can we just concentrate on the code? We don&#8217;t need to be worried too much about all these other tangential things.</p>



<p>[00:30:41] <strong>Pooja Derashri:</strong> If we talk about specifically WordPress, there is nothing we can only do with code. There are other things as well like non code contribution. There are other teams, other contributors that are putting in their efforts to make it a successful project. Like a Polyglots team is putting so many efforts into converting WordPress projects into the other languages, so it can be used by so many other people.</p>



<p>Similarly if we talk about docs team. Docs team is not putting coding efforts, but they are working on providing documentation so everyone can understand the process. Understand how to use WordPress, how you can build something on it, and how you can contribute.</p>



<p>So basically it is not about you can only do it with code. Diversity in terms of every aspect in non code contribution also matters. The whole community came from coding, non coding and other. All the people came together and built a community. Not only one person or one kind of people, like all coders can build a community. It should be a collective effort and it should be a collective output in my opinion.</p>



<p>[00:32:03] <strong>Nathan Wrigley:</strong> Yeah thank you, I think that was really nicely put. A good explanation of the problem at hand. Yeah that&#8217;s brilliant. Thank you.</p>



<p>If we were to be a listener to this podcast and some of the messages that you&#8217;ve talked about click with us, and we think, yeah everything that Pooja said, that&#8217;s vitally important. I&#8217;m not involved in it yet. I&#8217;d like to be more involved with it. I wonder if you could give us some pointers as to how you might get involved. Perhaps you could tell us about places that we could go. I can link to anything that you mention in the show notes, so they&#8217;ll all be in there. But also maybe you could highlight some of the people who are doing good work in this area.</p>



<p>So there&#8217;s obviously, you know you, yourself. But you mentioned Birgit Olzem and you&#8217;ve also mentioned Jill Binder, there&#8217;s a couple of other voices. But maybe there&#8217;s some other literature that you can point us in the direction of. Some websites, some project or endeavour that WordPress itself is doing, so that we can dig into this a little bit more.</p>



<p>[00:33:03] <strong>Pooja Derashri:</strong> Yes. I would like to mention the mentorship program lead by Hari Shanker. More contributors from diverse community come and join the WordPress project. It is a nice initiative in my opinion.</p>



<p>The WordPress six point release, they can join the WordPress six point release Slack channel and people will go through the process of how release works, and how, if they want to be a part of Core. There is not only they can part of Core by just coding. There are so many other areas like testing, like documentation, marketing, content training team. There are so many other teams they can also join.</p>



<p>Courtney Robertson is also raising awareness about diversity and she is putting so much effort into onboarding to people from different parts of the world. So yeah these are the few things I would like to mention.</p>



<p>[00:34:00] <strong>Nathan Wrigley:</strong> Okay, that&#8217;s great. Thank you very much. And on a more personal note, if somebody has listened to this and they would like to make contact with you. Do you have a web page or a social media profile that you would point people towards?</p>



<p>[00:34:17] <strong>Pooja Derashri:</strong> I&#8217;m available on Twitter at PoojaDerashri, the same handle as my name, P O O J A D E R A S H R I. I&#8217;m available on Make WordPress Slack channel. So if anyone wants to contact me they can contact me through Twitter or Make Slack WordPress channel.</p>



<p>[00:34:38] <strong>Nathan Wrigley:</strong> Well Pooja, thank you for joining me today. I think I have asked all of the questions that I wish to ask. I&#8217;ll just end by giving you the opportunity, if there was anything else that you wanted to add. If not I will say thank you very much for joining us and giving us some really important information about this really important subject. So over to you if there&#8217;s anything that I missed.</p>



<p>[00:35:00] <strong>Pooja Derashri:</strong> No actually you have covered everything very well and I think there is nothing I would like to mention in hand. Just one thing I would like to state here, I heard in one of the workshops by Jill Binder that many underrepresented are experts. She shared in one of the workshops where people sometimes have a misconception that there are two different type of people, like WP experts and the underrepresented. But there is not something like that. My personal conception was changed after hearing her workshop that she stated that many underrepresented people are also experts.</p>



<p>[00:35:45] <strong>Nathan Wrigley:</strong> Okay thank you. Pooja Derashri, thank you so much for joining us on the podcast today. I really appreciate it.</p>



<p>[00:35:51] <strong>Pooja Derashri:</strong> Thank you. Thank you so much</p>
</div>



<p>On the podcast today we have <a href="https://twitter.com/poojaderashri">Pooja Derashri</a>.</p>



<p>Pooja is a co-founder of <a href="https://wpvibes.com/">WPVibes</a>, a plugin development company based in India. With a passion for WordPress, Pooja has been actively involved in the community since 2013. Her journey as a contributor began in 2017, when she attended her first local WordCamp. Her expertise and dedication have earned her various key roles in the WordPress ecosystem. She currently serves as a co-team rep for the training team and GTE for the Hindi locale. In addition, she holds key positions in the WordPress release squad for versions 6.3 and 6.4, where she heads up the test team.</p>



<p>Pooja shares her insights on the importance of diversity, equity, inclusion, and belonging within the WordPress community, and explores how you don’t need to be a coder to be a part of the community and all that it is.</p>



<p>We discuss the work of teams like Polyglots, who focus on translating WordPress projects into different languages, and Docs, who provide much needed documentation to help users understand and contribute to the platform. These initiatives alone make it clear that WordPress is reliant on non-coding contributions, and there are more ways to contribute than ever before.</p>



<p>I ask Pooja about her experiences with diversity and inclusivity in the tech industry, and she reflects on the challenges she has faced, discussing the importance of recognising and addressing unconscious biases. She shares her insights on the need for training and workshops that empower diverse individuals to contribute and speak up within the WordPress community.</p>



<p>We delve into Birgit Olzem&#8217;s proposal to form an official DEIB team within WordPress, aiming to implement diversity, equity, inclusion, and belonging throughout the whole community. I express my excitement about the potential outcome of this proposal, and we think about how WordPress compares to other parts of the tech industry.</p>



<p>We explore the various initiatives and efforts being made to build a more inclusive WordPress culture. From mentorship programs, to targeted outreach and safe spaces, we uncover the ways in which underrepresented voices are being uplifted.</p>



<p>If you’re interested in creating a more inclusive community, this episode is for you.</p>



<h2 class="wp-block-heading">Useful links mentioned in the podcast</h2>



<p><a href="https://wptavern.com/podcast/94-birgit-olzem-and-jill-binder-on-creating-a-diverse-and-sustainable-wordpress-community">Jukebox Podcast #94 – Birgit Olzem and Jill Binder on Creating a Diverse and Sustainable WordPress Community</a></p>



<p><a href="https://make.wordpress.org/training/">Training team</a></p>



<p><a href="https://twitter.com/poojaderashri">Pooja&#8217;s Twitter</a></p>



<h2 class="wp-block-heading">Links supplied by Pooja in relation to the podcast</h2>



<p><a href="https://heropress.com/" target="_blank" rel="noreferrer noopener">HeroPress</a> by Topher DeRosia</p>



<p><a href="https://yoast.com/yoast-diversity-fund/" target="_blank" rel="noreferrer noopener">Yoast Diversity Fund</a></p>



<p><a href="https://wordpressfoundation.org/projects/kim-parsell-memorial-scholarship/" target="_blank" rel="noreferrer noopener">Kim Parsell Memorial Scholarship</a></p>



<p><a href="https://opencollective.com/thewpcc" target="_blank" rel="noreferrer noopener">The WP Community Collective</a>&nbsp;by Courtney Robertson, Sé Reed, and Katie Adams Farrell</p>



<p><a href="https://www.underrepresentedintech.com/" target="_blank" rel="noreferrer noopener">Underrepresented in Tech</a>&nbsp;by Allie Nimmons and Michelle Frechette</p>



<p><a href="https://wpspeakers.com/" target="_blank" rel="noreferrer noopener">WP Speakers</a>&nbsp;by Michelle Frechette</p>



<p><a href="https://womeninwp.com/" target="_blank" rel="noreferrer noopener">Women in WP Show</a> by  Amy Masson,  Tracy Apps, and Angela Bow</p>



<p><a href="https://make.wordpress.org/project/2023/07/13/proposal-for-establishing-a-make-diversity-equity-inclusion-and-belonging-deib-team-within-the-wordpress-community/" target="_blank" rel="noreferrer noopener">DEIB Make WordPress team proposal</a> by Birgit Olzem</p>



<p><a href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/diversity-speaker-training-workshop/" target="_blank" rel="noreferrer noopener">Diversity Workshops</a> by  Jill Binder</p>



<p><a href="https://make.wordpress.org/project/2023/08/11/the-inaugural-cohort-of-the-wordpress-contributor-mentorship-program-has-concluded/" target="_blank" rel="noreferrer noopener">Contributor Mentorship Program&nbsp;</a>by&nbsp; Hari Shanker</p>



<p><a href="https://www.youtube.com/@gowithwp" target="_blank" rel="noreferrer noopener">Go with WP</a> podcast by the Nepal Community</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 18 Oct 2023 14:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nathan Wrigley";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"Akismet: 10 Powerful AI Marketing Tools to Grow Your Business in 2023";s: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:"http://akismet.com/?p=281899";s: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:57:"https://akismet.com/blog/ai-marketing-tools-for-business/";s: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:38655:"<p>AI (artificial intelligence) has drastically changed the way many industries operate. In particular, there are tons of AI marketing tools that make it quicker and easier to manage (and expand) your business. But with the growing popularity of these tools, you might find it difficult to keep up with your competitors.&nbsp;</p>


<p>Luckily, you can retain your competitive edge and expand your business by implementing the best AI marketing tools. You can find anti&#8209;spam software, customer service automation tools, email marketing programs, and more that can take care of routine tasks and procedures. This way, you can get more done with less&nbsp;time.</p>

<p>In this post, we’ll take a closer look at the features you should look for in AI marketing tools. Then, we’ll explore ten of the best AI tools for&nbsp;business.</p>


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


<h2 class="wp-block-heading">What features should businesses seek in an AI marketing&nbsp;tool?</h2>


<p>With the emergence of AI in the marketing industry, it’s much quicker and easier to complete many routine tasks. You can find tools that help you automate email campaigns, research keywords, write content, and more.&nbsp;</p>



<p>When you’re able to get these tasks done faster, you can free up time to invest into other aspects of your business. Or, you can implement AI tools that help you improve your current practices. For instance, you can find advanced programs to conduct competitor research or optimize your ad campaigns.&nbsp;</p>


<p>No matter what your motivation for using artificial intelligence marketing tools, there are a few key features to look out for when choosing them. Here are some of the main factors to&nbsp;consider:</p>


<ul><li><strong>Automation. </strong>Automated tools, as the name suggests, work automatically. Since these tasks take place in the background, they often require minimal effort and input once&nbsp;configured.</li>

<li><strong>Customization options. </strong>It’s important to find a solution that offers various customization options. This way, you can create a unique tool that fits in seamlessly with the rest of your business and&nbsp;brand.</li>

<li><strong>Personalization. </strong>The drawback of using automated solutions is that you can end up adopting a one&#8209;size&#8209;fits&#8209;all approach. Still, the best AI marketing tools will provide a great deal of personalization both for you and your&nbsp;customers.</li>


<li><strong>Data analytics. </strong>It’s vital to have access to analytics for any marketing activity for your business. This way, you can identify what’s working and what isn’t. Then, you can adjust your approach accordingly.&nbsp;</li>
</ul>


<p>With these things in mind, you’ll be better equipped to find the right AI marketing tools to complement your marketing&nbsp;strategy.</p>


<h2 class="wp-block-heading">The 10 best AI tools for marketing&nbsp;</h2>


<p>Now that you know what to look for in an AI marketing tool, let’s check out ten of the best options to help grow your&nbsp;business.</p>


<img width="1600" height="866" src="https://akismet455732288.files.wordpress.com/2023/09/image-9.png" alt="Akismet home page design" class="wp-image-282629" />


<h3 class="wp-block-heading">1. <a href="https://akismet.com/">Akismet: AI anti&#8209;spam that boosts conversion&nbsp;rates</a></h3>


<p>Akismet is an automated tool that filters out comment and form spam with an accuracy rating of 99.99 percent. Better yet, the tool analyzes every piece of user-submitted content in real time to protect your site from attacks.&nbsp;</p>


<p>The Akismet plugin provides an easy way to save time, since it can take hours to manually review comments and form submissions. In fact, the average Akismet user saves 20 hours a month by switching over from manual&nbsp;filtering.</p>

<p>One of the most common ways to block spam online is to <a href="https://akismet.com/blog/wordpress-captcha/">implement a CAPTCHA</a>. But this adds friction to the user experience, which can result in fewer conversions and sales. <a href="https://akismet.com/features/">Akismet</a>, on the other hand, blocks spam without disrupting the user experience.&nbsp;</p>


<p>Trusted by companies like Microsoft, Bluehost, <a href="https://akismet.com/blog/convertkit-customerstory/">and ConvertKit</a>, Akismet blocks bots, but provides a quicker, smoother process for real people. Without the need to find all the stop lights or decipher jumbled text, more people will complete your forms and your bottom line can improve overnight.&nbsp;</p>
