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:131:"WPTavern: WordPress 6.2 “Dolphy” Introduces a Revamped Site Editor, Distraction-Free Writing Mode, and Updated Block Inserter ";s:7:"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=143114";s:7:"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:132:"https://wptavern.com/wordpress-6-2-dolphy-introduces-a-revamped-site-editor-distraction-free-writing-mode-and-updated-block-inserter";s: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:4516:"<img />image credit: <a href="https://www.youtube.com/watch?v=vAn_gyNcvN4">Charles Mingus Sextet &#8211; Feat. Eric Dolphy &#8211; Take The A Train</a>



<p><a href="https://wordpress.org/news/2023/03/dolphy/">WordPress 6.2</a> &#8220;Dolphy&#8221; was released today, named in honor of American jazz alto saxophonist, bass clarinetist, and flautist <a href="https://en.wikipedia.org/wiki/Eric_Dolphy">Eric Allan Dolphy Jr</a>. This is the first of three planned major releases in 2023. It includes more than 900 enhancements and bug fixes, with a strong focus on improving the site editing experience.</p>



<p>One of the major highlights of the 6.2 release is the completely revamped Site Editor interface. The browse mode style of navigation lets users quickly slide between editing and previews of templates and template parts, with a new unified design that makes it feel like it&#8217;s all part of the same application. </p>



<p>Color-coded labels have been added in 6.2, which give users more visual cues in finding their template parts and reusable blocks inside the List View, the Block toolbar, and on the Canvas.</p>



<p>With these and other updates, the Site Editor is now out of beta. Inside the admin, the About page includes beautifully designed screenshots of each feature with the vibrant blue color that has become part of WordPress&#8217; identity in the new design that is slowly being rolled out across WordPress.org.</p>



<img />WordPress 6.2 About page



<p>For those switching from a Classic theme to a Block theme, widgets will now automatically become Template Parts to make it an easier transition.</p>



<h3 class="wp-block-heading">Improved Navigation Block Experience for Managing Menus</h3>



<p>Managing Navigation menus just got easier with a new sidebar inside the Site Editor that allows users to quickly add, remove, and reorder menu items.</p>



<img />WordPress 6.2 About page



<h3 class="wp-block-heading">Updated Block Inserter with Media Tab and Openverse Integration</h3>



<p>The Block Inserter is sporting a new design that better integrates media, making it faster to insert images, video, and audio, with a new tab alongside blocks and patterns. Users can select the new tab and select a media type to see the ten most recent items. </p>



<img />



<p>WordPress 6.2 also adds integration with <a href="https://openverse.org/">Openverse</a> to this new media tab. Users now have access to the Openverse library of more than 700 free-to-use openly licensed and public domain works, directly inside the editor. Clicking on an Openverse image will instantly insert it as an Image block with the proper attribution and license automatically added to the caption, a much faster experience than downloading and uploading to the Media Library.</p>



<img />



<h3 class="wp-block-heading">New Distraction-Free Writing Mode</h3>



<p>WordPress 6.2 introduces a distraction-free writing mode that offers a more focused writing experience, hiding unnecessary interface elements from the editor. This video from the 6.2 testing guide shows how it can be enabled and disabled.</p>



video credit: <a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/">WordPress 6.2 Testing Guide</a>



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



<ul>
<li> A new collection of header and footer patterns for block themes</li>



<li>Scaled block settings with split controls to better organize Styles and Settings options</li>



<li>A new Style Book that displays every block in the site’s library at a glance where they can be previewed and edited globally</li>



<li>Copy and Paste styles between blocks</li>



<li>Improved pattern insertion with patterns organized into more categories, like headers and footers</li>



<li>Custom CSS support sitewide and for specific blocks</li>



<li>Sticky positioning to keep top-level group blocks fixed to the top of a page as visitors scroll</li>



<li>Improved privacy for default themes with locally hosted Google Fonts</li>
</ul>



<p>WordPress 6.2 was made possible by more than 600 contributors across 50 countries, with 178 of those contributing for the first time. Update today to get access to all these new features and bug fixes. For the most comprehensive coverage of all the under-the-hood changes for developers and extenders, check out the <a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</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, 29 Mar 2023 20:35:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:90:"Post Status: WordPress 6.2 “Dolphy” • Gutenberg Phase 3 • Test Plugin Dependencies";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=148557";s:7:"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:87:"https://poststatus.com/wordpress-6-2-dolphy-gutenberg-phase-3-test-plugin-dependencies/";s: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:19944:"<h2 id="h-this-week-at-wordpress-org-march-27-2023">This Week at WordPress.org (March 27, 2023)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f973.png" alt="🥳" class="wp-smiley" /> WordPress 6.2 is now available! If you haven&#8217;t started testing yet, now is the time. <br /><br />Gutenberg is a 4 phase approach to nearly all areas of WordPress. Phase 1 was Posts and Pages. Phase 2 included Themes. Matias Ventura shares what we could see in Phase 3.  <br /><br />Andy Fragen has posted a call for testing on the Plugin Dependencies plugin. </p></div>


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



<div class="wp-block-kadence-infobox kt-info-box_94d1bd-77"><div class="kt-blocks-info-box-link-wrap kt-blocks-info-box-media-align-left kt-info-halign-left"><div class="kt-blocks-info-box-media-container"><div class="kt-blocks-info-box-media kt-info-media-animate-none"><div class="kadence-info-box-icon-container kt-info-icon-animate-none"><div class="kadence-info-box-icon-inner-container"><span class="kb-svg-icon-wrap kb-svg-icon-fas_rocket kt-info-svg-icon"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title">WP 6.2, Plugin Dependencies, Phase 3</h2><p class="kt-blocks-info-box-text"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f680.png" alt="🚀" class="wp-smiley" /> <a href="https://wordpress.org/news/2023/03/dolphy/">WordPress 6.2 “Dolphy”</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f5a5.png" alt="🖥" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/03/28/call-for-testing-plugin-dependencies-ux/">Call for Testing: Plugin Dependencies UX</a><br /><br />3&#x20e3; <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">Phase 3: Collaboration</a></p></div></div></div>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_b57166-6e"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="h-news"><a href="https://wordpress.org/news">News</a></h2>



<ul>
<li><a href="https://wordpress.org/news/2023/03/episode-52-phase-three-with-hector-prieto/">WP Briefing: Episode 52: Workflows and Phase Three Visioning with Special Guest Héctor Prieto</a></li>



<li><a href="https://wp20.wordpress.net/wp20-swag-is-here/">WP20 Swag is Here! Order Your Official Merchandise Today</a></li>
</ul>



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



<div class="is-layout-flex wp-container-3 wp-block-columns">
<div class="is-layout-flow wp-block-column">
<h2 id="h-core"><a href="https://make.wordpress.org/core">Core</a> </h2>



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/28/call-for-testing-plugin-dependencies-ux/">Call for Testing: Plugin Dependencies UX</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/28/introducing-a-new-block-editor-handbook-scrub/">Introducing a new block editor handbook scrub</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-day-process/">WordPress 6.2 Release Day Process</a></li>
</ul>



<h3 id="h-wordpress-6-2">WordPress 6.2</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/28/wordpress-6-2-release-date-updated-march-29-2023/">WordPress 6.2 release date updated: March 29, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-day-process/">WordPress 6.2 Release Day Process</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-candidate-4/">WordPress 6.2 Release Candidate 4</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/14/fyi-navigation-section-of-new-site-editor-experienced-removed-for-6-2-rc-2/">FYI: Navigation section of new Site Editor experienced removed for 6.2 RC 2</a></li>



<li><a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-1/">WordPress 6.2 Release Candidate 1</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/14/wordpress-6-2-translation-status-march-14-2023/">WordPress 6.2 Translation Status (March 14, 2023)</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/04/wordpress-6-2-ready-to-be-translated/">WordPress 6.2 ready to be translated</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</a>
<ul>
<li><a href="https://make.wordpress.org/core/2023/03/08/requests-library-upgraded-to-2-0-5-in-wordpress-6-2/">Requests library upgraded to 2.0.5 in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/patterns-api-expanded-to-include-template_types-property/">Patterns API expanded to include template_types property</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introduction-of-block-inspector-tabs/">Introduction of Block Inspector Tabs</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/shadows-in-global-styles-with-wordpress-6-2/">Shadows in Global Styles with WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introducing-the-html-api-in-wordpress-6-2/">Introducing the HTML API in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/miscellaneous-editor-changes-in-wordpress-6-2/">Miscellaneous Editor changes in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introducing-move_dir-in-wordpress-6-2/">Introducing move_dir() in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/sticky-position-block-support/">Sticky position block support</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/upgrading-to-react-18-and-common-pitfalls-of-concurrent-mode/">Upgrading to React 18 and common pitfalls of concurrent mode</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/add-new-prop-to-serversiderender-component/">Add new prop to ServerSideRender component</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/google-fonts-are-included-locally-in-bundled-themes/">Google Fonts are included locally in bundled themes</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/custom-css-for-global-styles-and-per-block/">Custom CSS for global styles and per block</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/minimum-height-dimensions-block-support/">Minimum height dimensions block support</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/03/editor-components-updates-in-wordpress-6-2/">Editor Components updates in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/03/i18n-improvements-in-6-2/">I18N Improvements in 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/28/custom-settings-wordpress-6-2/">Customize settings for any block in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/19/style-book-preview-of-blocks-in-global-styles/">Style Book preview of blocks in global styles</a></li>



<li><a href="https://make.wordpress.org/core/2022/12/09/update-to-content-only-editing-filter-namespace/">Update to content only editing filter namespace</a></li>
</ul>
</li>



<li><a href="https://make.wordpress.org/core/2023/03/02/wordpress-6-2-accessibility-improvements/">WordPress 6.2 Accessibility Improvements</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/28/wordpress-6-2-beta-4-postponed/">WordPress 6.2 Beta 4 Postponed</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/21/wordpress-6-2-beta-3/">WordPress 6.2 Beta 3</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/21/6-2-live-product-demo/">6.2 Live Product Demo</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/04/phase-2-finale/">Phase 2, Finale</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/03/hallway-hangout-performance-improvements-for-wordpress-6-2/">Hallway Hangout: Performance Improvements for WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/06/roadmap-to-6-2/">Roadmap to 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/18/bug-scrub-schedule-for-6-2/">Bug Scrub Schedule for 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/11/early-bug-scrub-schedule-for-wp-6-2/">Early bug scrub schedule for WP&nbsp;6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/17/wordpress-6-2-planning-roundup/">WordPress 6.2 Planning Roundup</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/28/march-29-dev-chat-is-canceled-in-favor-of-wordpress-6-2-final-release-party/">March 29 Dev Chat is canceled in favor of WordPress 6.2 final release party</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/27/editor-chat-summary-march-22nd-2023/">Editor chat summary: March 22nd, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/27/editor-chat-agenda-march-29th-2023/">Editor Chat Agenda: March 29th 2023</a></li>
</ul>



<h3 id="h-developer-blog">Developer Blog</h3>



<ul>
<li><a href="https://developer.wordpress.org/news/2023/03/quick-and-easy-local-wordpress-development-with-wp-env/">Quick and easy local WordPress development with wp-env</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/design/2023/03/13/design-share-feb-13-mar-10/">Design Share: Feb 13–Mar 10</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/docs/2023/03/26/agenda-for-docs-team-bi-weekly-meeting-april-4-2023/">Agenda for Docs Team bi-weekly meeting April 4, 2023</a></li>



<li><a href="https://make.wordpress.org/docs/2023/03/26/summary-for-docs-team-meeting-march-21-2023/">Summary for Docs Team meeting, March 21, 2023</a></li>



<li><a href="https://make.wordpress.org/docs/2023/03/15/call-for-volunteers-to-help-with-6-2-end-user-documentation/">Call for volunteers to help with 6.2 end user documentation</a></li>



<li><a href="https://make.wordpress.org/updates/2023/03/27/documentation-team-update-march-27-2023/">Documentation Team Update – March 27, 2023</a></li>
</ul>
</div>



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



<ul>
<li><a href="https://make.wordpress.org/hosting/2023/03/21/hosting-team-meeting-agenda-2023-03-22/">Hosting Team meeting agenda 2023-03-22</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/marketing/2023/03/28/notes-global-marketing-team-meeting-21-march-2023/">Notes: Global Marketing Team meeting, 21 March 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/meta/2023/03/27/matrix-chat-summary-march-23-2023/">Matrix chat Summary, March 23 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/mobile/2023/03/28/new-mobile-support-forum/">New Mobile Support Forum</a></li>



<li><a href="https://make.wordpress.org/updates/2023/03/25/mobile-team-update-march-25th/">Mobile Team Update – March 25th</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/openverse/2023/03/27/last-week-openverse-2023-03-20-2023-03-27/">A week in Openverse: 2023-03-20 – 2023-03-27</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/28/performance-chat-summary-28-march-2023/">Performance Chat Summary: 28 March 2023</a></li>



<li><a href="https://make.wordpress.org/updates/2023/03/27/core-performance-team-update-march-27-2023/">Core Performance Team Update: March 27, 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/plugins/2023/03/10/advance-notice-of-retirement/">Advance Notice of Retirement</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/polyglots/2023/03/29/agenda-weekly-polyglots-chat-march-29-2023-1300-utc/">Agenda: Weekly Polyglots Chat – March 29, 2023 (13:00 UTC)</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/21/new-translation-project-wp20-wordpress-net/">New translation project: wp20.wordpress.net</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/plugins/2023/03/21/use-of-code-generators-must-remain-gpl-compatible/">Use of Code Generators Must Remain GPL Compatible</a></li>



<li><a href="https://make.wordpress.org/plugins/2023/03/10/advance-notice-of-retirement/">Advance Notice of Retirement</a></li>



<li><a href="https://make.wordpress.org/updates/2023/03/28/plugin-review-team-27-mar-2023/">Plugin Review Team: 27 Mar 2023</a></li>
</ul>



<h2 id="h-project">Project</h2>



<ul>
<li><a href="https://make.wordpress.org/project/2023/02/06/proposal-creating-a-wordpress-contributor-mentorship-program/">Proposal: Creating a WordPress Contributor Mentorship Program</a></li>



<li><a href="https://make.wordpress.org/project/2023/01/27/discussion-ending-the-eternal-september/">Discussion: Ending the Eternal September</a></li>
</ul>



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



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



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



<ul>
<li><a href="https://make.wordpress.org/test/2023/03/28/test-chat-summary-28-march-2023/">Test Chat Summary: 28 March 2023</a></li>



<li><a href="https://make.wordpress.org/test/2023/03/14/hallway-hangout-lets-chat-about-all-things-layout/">Hallway Hangout: Let’s chat about All Things Layout</a></li>



<li><a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/">Help Test WordPress 6.2</a></li>
</ul>



<h2 id="h-theme">Theme</h2>



<ul>
<li><a href="https://make.wordpress.org/themes/2023/03/27/themes-team-meeting-agenda-for-march-28-2023/">Themes team meeting agenda for March 28, 2023</a></li>



<li><a href="https://make.wordpress.org/themes/2023/03/03/hallway-hangout-community-themes-initiative/">Hallway Hangout: Community Themes Initiative</a></li>



<li><a href="https://make.wordpress.org/updates/2023/03/28/themes-team-update-march-28-2023/">Themes team update March 28, 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/training/2023/03/29/introduction-to-wordpress-development-syllabus/">Introduction to WordPress Development syllabus</a></li>



<li><a href="https://make.wordpress.org/training/2023/03/27/meeting-agenda-for-march-28-2023/">Meeting agenda for March 28, 2023</a></li>
</ul>



<h3 id="h-tutorials"><a href="https://learn.wordpress.org/tutorials">Tutorials</a></h3>



<ul>
<li><a href="https://learn.wordpress.org/tutorial/32894-2/">How to use featured images</a></li>



<li><a href="https://learn.wordpress.org/tutorial/wordpress-rest-api-modifying-responses/">WordPress REST API – Modifying responses</a></li>
</ul>



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



<ul>
<li><a href="https://learn.wordpress.org/?meeting=live-stream-reviewing-developer-focused-features-in-gutenberg-15-4">Live stream: Reviewing developer-focused features in Gutenberg 15.4</a></li>



<li><a href="https://learn.wordpress.org/?meeting=%CE%B3%CE%BD%CF%89%CF%81%CE%B9%CE%BC%CE%AF%CE%B1-%CE%BC%CE%B5-%CF%84%CE%B7%CE%BD-%CE%BF%CE%BC%CE%AC%CE%B4%CE%B1-learn">Γνωριμία με την ομάδα Learn</a></li>



<li><a href="https://learn.wordpress.org/?meeting=how-do-you-learn-wordpress">How do you Learn WordPress?</a></li>
</ul>



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



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



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



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



<ul>
<li><a href="https://www.php.net/archive/2023.php#2023-02-14-2">PHP 8.2.4 Released!</a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-03-16-1">PHP 8.1.17 Released!</a></li>



<li><a href="https://262.ecma-international.org/13.0/">TC39</a></li>



<li><a href="https://github.com/composer/composer/releases/tag/2.5.5">Composer 2.5.5</a></li>
</ul>



<p class="has-theme-palette-7-background-color has-background">Thanks for reading our WP dot .org roundup! Each week we are highlighting the news and discussions coming from the good folks making WordPress possible. If you or your company create products or services that use WordPress, you need to be engaged with them and their work. Be sure to share this resource with your product and project managers. <br /><br /><strong>Are you interested in giving back and contributing your time and skills to WordPress.org?</strong> <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://wordpress.org/support/article/contributing-to-wordpress/">Start Here ›</a><br /><br /><strong>Get our weekly WordPress community news digest</strong> — Post Status&#8217; <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — covering the WP/Woo news plus significant writing and podcasts. It&#8217;s also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>



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



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



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



<div class="wp-block-spacer"></div>
<p>This article was published at Post Status — the community for WordPress professionals.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 29 Mar 2023 18:59:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:46:"WordPress.org blog: WordPress 6.2 “Dolphy”";s:7:"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=14659";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"https://wordpress.org/news/2023/03/dolphy/";s: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:56187:"<img width="1024" height="683" src="https://i0.wp.com/wordpress.org/news/files/2023/03/inline-image-x2-1.png?resize=1024%2C683&ssl=1" alt="WordPress 6.2 " />



<p>Say hello to WordPress 6.2 “Dolphy,&#8221; named for the woodwind jazz wiz, the multi-instrumentalist—<a href="https://en.wikipedia.org/wiki/Eric_Dolphy">Eric Allan Dolphy Jr</a>. Dolphy is acclaimed for having brought the bass clarinet to prominence in the jazz scene, creating a place for the flute and extending the lexicon of the alto saxophone. In a career that spanned continents, his artistry was at the forefront of pushing improvisational boundaries, ensemble work, and partnerships with well-respected artists like Charles Mingus and John Coltrane.</p>



<p>This latest version of WordPress reimagines your site editing experience, introduces more ways to style your site, and offers a new distraction-free way to write. Discover improvements that give you more control and freedom to express your creative vision. There’s something for everyone, whether you’re a content creator, developer, site builder, or designer. Let the <a href="https://open.spotify.com/artist/6rxxu32JCGDpKKMPHxnSJp?si=UEYO5JU5TXyEeINuuhN6aQ">music of Eric Dolphy</a> delight you as you take in all that 6.2 has to offer.</p>



<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/wordpress-6.2.zip">Download WordPress 6.2 today</a></div>
</div>



<p>WordPress 6.2 is the first major release of 2023, covering over 900 enhancements and fixes. It’s also a transition point in the WordPress project’s <a href="https://wordpress.org/about/roadmap/">development roadmap</a>, shifting focus from customization to <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">early exploration of workflows and collaboration</a>.</p>



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



<h4 class="wp-block-heading">Meet&nbsp;the reimagined Site Editor</h4>



<img src="https://i0.wp.com/wordpress.org/news/files/2023/03/Site-Editor.png?resize=536%2C536&ssl=1" alt="Image inlay of the reimagined Site Editor. WordPress 6.2 Dolphy" class="wp-image-14661" width="536" height="536" />



<p>Ready for you to dive in and explore: 6.2 is your invitation to discover what the next generation of WordPress—and block themes—can do.&nbsp;</p>



<p>Now out of beta, the Site Editor has an updated interface, giving you a new way to interact with your entire site. Explore full previews of your templates and template parts, then jump in and get to editing your site from wherever you choose.</p>



<h4 class="wp-block-heading">Manage menus in more ways with the Navigation block</h4>



<img src="https://i0.wp.com/wordpress.org/news/files/2023/03/Navigation.png?resize=532%2C532&ssl=1" alt="Image inlay of menu management from the Navigation block" class="wp-image-14662" width="532" height="532" />



<p>Add, remove, and reorder menu items faster—with a new sidebar experience that makes editing your site’s navigation easier.</p>



<h4 class="wp-block-heading">Discover a smoother experience for the Block Inserter</h4>



<img src="https://i0.wp.com/wordpress.org/news/files/2023/03/Patterns-Inserter.png?resize=536%2C536&ssl=1" alt="Image inlay of the Block Inserter" class="wp-image-14663" width="536" height="536" />



<p>A refreshed design gives you easier access to the content you need. Use the Media tab to quickly drag and drop content from your existing Media Library. Find patterns faster with a split view that lets you navigate categories and see previews all at once.</p>



<h4 class="wp-block-heading">Find the controls you want when you need them</h4>



<img src="https://i0.wp.com/wordpress.org/news/files/2023/03/Settings-and-Styles-Tabs.png?resize=540%2C540&ssl=1" alt="Tab between settings and styles in the block settings sidebar" class="wp-image-14664" width="540" height="540" />



<p>Your block settings sidebar is better organized with tabs for Settings and Styles. So the tools you need are easy to identify and access.&nbsp;</p>



<h4 class="wp-block-heading">Build faster with headers and footers for block themes</h4>



<img src="https://i0.wp.com/wordpress.org/news/files/2023/03/Block-themes.png?resize=534%2C534&ssl=1" alt="" class="wp-image-14671" width="534" height="534" />



<p>Discover a new collection of header and footer patterns. Use them with any block theme as a quick, high-quality starting point for your site’s templates.</p>



<h4 class="wp-block-heading">Explore Openverse media right from the Editor</h4>



<img src="https://i0.wp.com/wordpress.org/news/files/2023/03/Openverse.png?resize=544%2C544&ssl=1" alt="" class="wp-image-14670" width="544" height="544" />



<p>Openverse’s library catalogs over 700 million+ free, openly licensed stock images and audio—and now it’s directly integrated into the WordPress experience through the Inserter.&nbsp;</p>



<h4 class="wp-block-heading">Focus on writing with Distraction Free mode</h4>



<img src="https://i0.wp.com/wordpress.org/news/files/2023/03/Distraction-Free.png?resize=542%2C542&ssl=1" alt="" class="wp-image-14665" width="542" height="542" />



<p>For those times you want to be alone with your ideas. You can now hide all your panels and controls, leaving you free to bring your content to life.</p>



<h4 class="wp-block-heading">Meet the new Style Book</h4>



<img width="560" height="560" src="https://i0.wp.com/wordpress.org/news/files/2023/03/Style-Book.png?resize=560%2C560&ssl=1" alt="" class="wp-image-14667" />



<p>Get a complete overview of how every block in your site’s library looks. All in one place, all at a glance, directly in the Site Editor.</p>



<h4 class="wp-block-heading">Copy and paste styles</h4>



<img width="560" height="560" src="https://i0.wp.com/wordpress.org/news/files/2023/03/Copy-_-Paste.png?resize=560%2C560&ssl=1" alt="" class="wp-image-14666" />



<p>Perfect the design on one type of block, then copy and paste those styles to other blocks to get just the look you want.</p>



<h4 class="wp-block-heading">Custom CSS</h4>



<img width="560" height="560" src="https://i0.wp.com/wordpress.org/news/files/2023/03/Custom-CSS.png?resize=560%2C560&ssl=1" alt="" class="wp-image-14669" />



<p>Power up your site any way you wish with design tools and custom CSS for another level of control over your site’s look and feel for maximum creativity and artistry in your designs.</p>



<h3 class="wp-block-heading">Other highlights in 6.2</h3>



<ul>
<li><strong>Sticky positioning</strong>: Choose to keep top-level group blocks fixed to the top of a page as visitors scroll.</li>



<li><strong>Importing widgets</strong>: Options to import your favorite widgets from Classic themes to Block themes.</li>



<li><strong>Local fonts in themes</strong>: Default WordPress themes offer better privacy with Google Fonts now included.</li>
</ul>



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



<p>Explore <a href="https://learn.wordpress.org/workshops/">Learn WordPress</a> for quick how-to videos, courses, and other resources for the latest features in WordPress. Or join a free <a href="https://learn.wordpress.org/social-learning/">live interactive online workshop</a>.</p>



<p>Check out the <a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</a> for detailed developer notes to help you build with WordPress and get the most out of the latest release. Read the <a href="https://wordpress.org/documentation/wordpress-version/version-6-2/">6.2 release notes</a> for additional technical details about this release, including installation information, updates, fixes, file changes, and more.</p>



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



<p>6.2 is made possible by the many folks who have enthusiastically helped keep the release on track and moving forward:</p>



<ul>
<li>Release Lead: <a href="https://profiles.wordpress.org/matt/">Matt Mullenweg</a></li>



<li>Release Coordinators: <a href="https://profiles.wordpress.org/francina/">Francesca Marano</a>, <a href="https://profiles.wordpress.org/priethor/">Héctor Prieto</a></li>



<li>Core Tech Co-Leads: <a href="https://profiles.wordpress.org/hellofromtonya/">Tonya Mork</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a></li>



<li>Editor Tech Co-Leads: <a href="https://profiles.wordpress.org/mamaduka/">George Mamadashvili</a>, <a href="https://profiles.wordpress.org/ntsekouras/">Nik Tsekouras</a></li>



<li>Core Triage Co-Leads: <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a>, <a href="https://profiles.wordpress.org/mukesh27/">Mukesh Panchal</a></li>



<li>Editor Triage Co-Leads: <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a>, <a href="https://profiles.wordpress.org/ndiego/">Nick Diego</a></li>



<li>Design Lead: <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a></li>



<li>Documentation Co-Leads: <a href="https://profiles.wordpress.org/bph/">Birgit Pauli-Haack</a>, <a href="https://profiles.wordpress.org/femkreations/">Femy Praseet</a>, <a href="https://profiles.wordpress.org/milana_cap/">Milana Cap</a>, <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a></li>



<li>Marketing &amp; Communications Co-Leads: <a href="https://profiles.wordpress.org/jpantani/">Jonathan Pantani</a>, <a href="https://profiles.wordpress.org/laurlittle/">Lauren Stein</a>, <a href="https://profiles.wordpress.org/marybaum/">Mary Baum</a></li>



<li>Test Co-Leads: <a href="https://profiles.wordpress.org/robinwpdeveloper/">Robin</a>, <a href="https://profiles.wordpress.org/adeltahri/">Adel Tahri</a></li>



<li>Performance Lead: <a href="https://profiles.wordpress.org/flixos90/">Felix Arntz</a></li>
</ul>



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



<p>WordPress 6.2 couldn’t be here without the countless effort and passion of more than 600 contributors in at least 50 countries. A special thank you to the 178 new contributors who joined a release for the first time. Their collaboration helped deliver hundreds of enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress community.</p>



<p class="is-style-wporg-props-long alignfull"><a href="https://profiles.wordpress.org/10upsimon/">10upsimon</a> · <a href="https://profiles.wordpress.org/254volkan/">254volkan</a> · <a href="https://profiles.wordpress.org/mercime/">@mercime</a> · <a href="https://profiles.wordpress.org/aaroncampbell/">Aaron D. Campbell</a> · <a href="https://profiles.wordpress.org/aeg0125/">Aaron Graham</a> · <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a> · <a href="https://profiles.wordpress.org/aaronrobertshaw/">Aaron Robertshaw</a> · <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a> · <a href="https://profiles.wordpress.org/abidhasan112/">Abid Hasan</a> · <a href="https://profiles.wordpress.org/abitofmind/">abitofmind</a> · <a href="https://profiles.wordpress.org/abtop/">ABTOP</a> · <a href="https://profiles.wordpress.org/ace100/">ace100</a> · <a href="https://profiles.wordpress.org/bosconiandynamics/">Adam Bosco</a> · <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a> · <a href="https://profiles.wordpress.org/admwgn/">Adam Wiltgen</a> · <a href="https://profiles.wordpress.org/adeltahri/">Adel Tahri</a> · <a href="https://profiles.wordpress.org/adhun/">Adhun Anand</a> · <a href="https://profiles.wordpress.org/adityaarora010196/">adityaarora010196</a> · <a href="https://profiles.wordpress.org/aduth/">aduth</a> · <a href="https://profiles.wordpress.org/afshanadiya/">Afshana Diya</a> · <a href="https://profiles.wordpress.org/chaion07/">Ahmed Chaion</a> · <a href="https://profiles.wordpress.org/ajmaurya/">Ajay Maurya</a> · <a href="https://profiles.wordpress.org/ajayver/">ajayver</a> · <a href="https://profiles.wordpress.org/seakashdiu/">Akash Mia</a> · <a href="https://profiles.wordpress.org/wildworks/">Aki Hamano</a> · <a href="https://profiles.wordpress.org/schlessera/">Alain Schlesser</a> · <a href="https://profiles.wordpress.org/alanjacobmathew/">Alan Jacob Mathew</a> · <a href="https://profiles.wordpress.org/albarin/">albarin</a> · <a href="https://profiles.wordpress.org/alberuni-azad/">Alberuni Azad.</a> · <a href="https://profiles.wordpress.org/alecgeatches/">alecgeatches</a> · <a href="https://profiles.wordpress.org/aleksganev/">Aleks Ganev</a> · <a href="https://profiles.wordpress.org/xknown/">Alex Concha</a> · <a href="https://profiles.wordpress.org/ajlende/">Alex Lende</a> · <a href="https://profiles.wordpress.org/alexstine/">Alex Stine</a> · <a href="https://profiles.wordpress.org/alvastar/">alvastar</a> · <a href="https://profiles.wordpress.org/alvitazwar052/">Alvi Tazwar</a> · <a href="https://profiles.wordpress.org/amin7/">amin</a> · <a href="https://profiles.wordpress.org/amirrezatm/">amirrezatm</a> · <a href="https://profiles.wordpress.org/amitbarai013/">Amit Barai Alit</a> · <a href="https://profiles.wordpress.org/paulamit/">Amit Paul</a> · <a href="https://profiles.wordpress.org/anantajitjg/">Anantajit JG</a> · <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a> · <a href="https://profiles.wordpress.org/andreaboe/">andreaboe</a> · <a href="https://profiles.wordpress.org/andraganescu/">Andrei Draganescu</a> · <a href="https://profiles.wordpress.org/apmatthe/">Andrew Matthews</a> · <a href="https://profiles.wordpress.org/nacin/">Andrew Nacin</a> · <a href="https://profiles.wordpress.org/azaozz/">Andrew Ozz</a> · <a href="https://profiles.wordpress.org/andrewserong/">Andrew Serong</a> · <a href="https://profiles.wordpress.org/rarst/">Andrey "Rarst" Savchenko</a> · <a href="https://profiles.wordpress.org/oandregal/">André</a> · <a href="https://profiles.wordpress.org/afragen/">Andy Fragen</a> · <a href="https://profiles.wordpress.org/apeatling/">Andy Peatling</a> · <a href="https://profiles.wordpress.org/aniketpatel/">Aniket Patel</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/annezazu/">Anne McCarthy</a> · <a href="https://profiles.wordpress.org/antpb/">Anthony Burchell</a> · <a href="https://profiles.wordpress.org/ahortin/">Anthony Hortin</a> · <a href="https://profiles.wordpress.org/antonvlasenko/">Anton Vlasenko</a> · <a href="https://profiles.wordpress.org/antonyagrios/">Antony Agrios</a> · <a href="https://profiles.wordpress.org/aparnajl/">Aparna Adhun</a> · <a href="https://profiles.wordpress.org/arrasel403/">AR Rasel</a> · <a href="https://profiles.wordpress.org/arafatjamil01/">Arafat Jamil</a> · <a href="https://profiles.wordpress.org/aravindajith/">Aravind Ajith</a> · <a href="https://profiles.wordpress.org/aristath/">Ari Stathopoulos</a> · <a href="https://profiles.wordpress.org/arnolp/">arnolp</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/artz91/">ArtZ91</a> · <a href="https://profiles.wordpress.org/aryamaaru/">Arun</a> · <a href="https://profiles.wordpress.org/mrasharirfan/">Ashar Irfan</a> · <a href="https://profiles.wordpress.org/ashrafulsarkar/">Ashraful Sarkar Naiem</a> · <a href="https://profiles.wordpress.org/nmutua/">Autumn</a> · <a href="https://profiles.wordpress.org/ayeshrajans/">Ayesh Karunaratne</a> · <a href="https://profiles.wordpress.org/azurseisme/">azurseisme</a> · <a href="https://profiles.wordpress.org/barryceelen/">Barry Ceelen</a> · <a href="https://profiles.wordpress.org/bart/">Bart</a> · <a href="https://profiles.wordpress.org/beafialho/">Beatriz Fialho</a> · <a href="https://profiles.wordpress.org/bedas/">Beda</a> · <a href="https://profiles.wordpress.org/scruffian/">Ben Dwyer</a> · <a href="https://profiles.wordpress.org/benish74/">benish74</a> · <a href="https://profiles.wordpress.org/benjgrolleau/">Benjamin Grolleau</a> · <a href="https://profiles.wordpress.org/benoitchantre/">Benoit Chantre</a> · <a href="https://profiles.wordpress.org/kau-boy/">Bernhard Kau</a> · <a href="https://profiles.wordpress.org/bernhard-reiter/">Bernie Reiter</a> · <a href="https://profiles.wordpress.org/mxbclang/">Bethany Chobanian Lang</a> · <a href="https://profiles.wordpress.org/bgin/">bgin</a> · <a href="https://profiles.wordpress.org/albatross10/">Bhavik Kalpesh</a> · <a href="https://profiles.wordpress.org/birgire/">Birgir Erlendsson (birgire)</a> · <a href="https://profiles.wordpress.org/bph/">Birgit Pauli-Haack</a> · <a href="https://profiles.wordpress.org/bjorn2404/">bjorn2404</a> · <a href="https://profiles.wordpress.org/bogdanungureanu/">BogdanUngureanu</a> · <a href="https://profiles.wordpress.org/bonjour52/">bonjour52</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/bjorsch/">Brad Jorsch</a> · <a href="https://profiles.wordpress.org/bradyvercher/">Brady Vercher</a> · <a href="https://profiles.wordpress.org/kraftbj/">Brandon Kraft</a> · <a href="https://profiles.wordpress.org/bgoewert/">Brennan Goewert</a> · <a href="https://profiles.wordpress.org/bgardner/">Brian Gardner</a> · <a href="https://profiles.wordpress.org/bronsonquick/">bronsonquick</a> · <a href="https://profiles.wordpress.org/brookemk/">Brooke Kaminski</a> · <a href="https://profiles.wordpress.org/brookedot/">Brooke.</a> · <a href="https://profiles.wordpress.org/buutqn/">buutqn</a> · <a href="https://profiles.wordpress.org/cameronjonesweb/">Cameron Jones</a> · <a href="https://profiles.wordpress.org/cbravobernal/">Carlos Bravo</a> · <a href="https://profiles.wordpress.org/carlosgprim/">Carlos Garcia Prim</a> · <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a> · <a href="https://profiles.wordpress.org/shireling/">Chad Chadbourne</a> · <a href="https://profiles.wordpress.org/critterverse/">Channing Ritter</a> · <a href="https://profiles.wordpress.org/mcaskill/">Chauncey McAskill</a> · <a href="https://profiles.wordpress.org/chintan1896/">Chintan hingrajiya</a> · <a href="https://profiles.wordpress.org/chiragrathod103/">Chirag Rathod</a> · <a href="https://profiles.wordpress.org/cbringmann/">Chloe Bringmann</a> · <a href="https://profiles.wordpress.org/chocofc1/">chocofc1</a> · <a href="https://profiles.wordpress.org/chouby/">Chouby</a> · <a href="https://profiles.wordpress.org/chrisbaltazar/">chrisbaltazar</a> · <a href="https://profiles.wordpress.org/apermo/">Christoph Daum</a> · <a href="https://profiles.wordpress.org/chrystl/">Chrystl</a> · <a href="https://profiles.wordpress.org/ckanderson22/">ckanderson22</a> · <a href="https://profiles.wordpress.org/claytoncollie/">Clayton Collie</a> · <a href="https://profiles.wordpress.org/cnspecialcolor/">cnspecialcolor</a> · <a href="https://profiles.wordpress.org/codesdnc/">codesdnc</a> · <a href="https://profiles.wordpress.org/codingchicken/">Coding Chicken</a> · <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a> · <a href="https://profiles.wordpress.org/conner_bw/">conner_bw</a> · <a href="https://profiles.wordpress.org/copons/">Copons</a> · <a href="https://profiles.wordpress.org/corentingautier/">corentingautier</a> · <a href="https://profiles.wordpress.org/coreyw/">Corey Worrell</a> · <a href="https://profiles.wordpress.org/cbirdsong/">Cory Birdsong</a> · <a href="https://profiles.wordpress.org/craigfrancis/">Craig Francis</a> · <a href="https://profiles.wordpress.org/craiglpeters/">craiglpeters</a> · <a href="https://profiles.wordpress.org/geisthanen/">Creative Andrew</a> · <a href="https://profiles.wordpress.org/mitogh/">Crisoforo Gaspar</a> · <a href="https://profiles.wordpress.org/cu121/">Cupid Chakma</a> · <a href="https://profiles.wordpress.org/dperonne/">D.PERONNE</a> · <a href="https://profiles.wordpress.org/daisyo/">Daisy Olsen</a> · <a href="https://profiles.wordpress.org/dalirajab/">dali-rajab</a> · <a href="https://profiles.wordpress.org/dalleyne/">Damien Alleyne</a> · <a href="https://profiles.wordpress.org/colorful-tones/">Damon Cook</a> · <a href="https://profiles.wordpress.org/danielbachhuber/">Daniel Bachhuber</a> · <a href="https://profiles.wordpress.org/wirecat/">Daniel Johnson</a> · <a href="https://profiles.wordpress.org/talldanwp/">Daniel Richards</a> · <a href="https://profiles.wordpress.org/mte90/">Daniele Scasciafratte</a> · <a href="https://profiles.wordpress.org/darerodz/">darerodz</a> · <a href="https://profiles.wordpress.org/datagutten/">datagutten</a> · <a href="https://profiles.wordpress.org/davilera/">David Aguilera</a> · <a href="https://profiles.wordpress.org/davidbaumwald/">David Baumwald</a> · <a href="https://profiles.wordpress.org/davidbinda/">David Biňovec</a> · <a href="https://profiles.wordpress.org/dpcalhoun/">David Calhoun</a> · <a href="https://profiles.wordpress.org/dgwyer/">David Gwyer</a> · <a href="https://profiles.wordpress.org/dlh/">David Herrera</a> · <a href="https://profiles.wordpress.org/davefx/">David Mar&#237;n Carre&#241;o</a> · <a href="https://profiles.wordpress.org/dshanske/">David Shanske</a> · <a href="https://profiles.wordpress.org/get_dave/">David Smith</a> · <a href="https://profiles.wordpress.org/davidvongries/">David Vongries</a> · <a href="https://profiles.wordpress.org/dsas/">Dean Sas</a> · <a href="https://profiles.wordpress.org/dennisatyoast/">Dennis Claassen</a> · <a href="https://profiles.wordpress.org/dmsnell/">Dennis Snell</a> · <a href="https://profiles.wordpress.org/derekblank/">derekblank</a> · <a href="https://profiles.wordpress.org/devanshijoshi/">devanshijoshi</a> · <a href="https://profiles.wordpress.org/dhusakovic/">dhusakovic</a> · <a href="https://profiles.wordpress.org/dilipbheda/">Dilip Bheda</a> · <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a> · <a href="https://profiles.wordpress.org/doctorlai/">doctorlai</a> · <a href="https://profiles.wordpress.org/ocean90/">Dominik Schilling</a> · <a href="https://profiles.wordpress.org/donncha/">Donncha</a> · <a href="https://profiles.wordpress.org/drzraf/">drzraf</a> · <a href="https://profiles.wordpress.org/d-signed/">DSIGNED</a> · <a href="https://profiles.wordpress.org/dustinrue/">dustinrue</a> · <a href="https://profiles.wordpress.org/chopinbach/">Edwin Cromley</a> · <a href="https://profiles.wordpress.org/ellatrix/">Ella van Durpe</a> · <a href="https://profiles.wordpress.org/emanuelx/">emanuelx</a> · <a href="https://profiles.wordpress.org/manooweb/">Emmanuel Hesry</a> · <a href="https://profiles.wordpress.org/enej/">Enej Bajgorić</a> · <a href="https://profiles.wordpress.org/lopo/">Enrico Battocchi</a> · <a href="https://profiles.wordpress.org/ericlewis/">Eric Andrew Lewis</a> · <a href="https://profiles.wordpress.org/edanzer/">Erick Danzer</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/manuilov/">Eugene M</a> · <a href="https://profiles.wordpress.org/eherman24/">Evan Herman</a> · <a href="https://profiles.wordpress.org/fabiankaegy/">Fabian K&#228;gy</a> · <a href="https://profiles.wordpress.org/fosuahmed/">Faisal Ahmed</a> · <a href="https://profiles.wordpress.org/faisal03/">Faisal Alvi</a> · <a href="https://profiles.wordpress.org/fasuto/">fasuto</a> · <a href="https://profiles.wordpress.org/felipeelia/">Felipe Elia</a> · <a href="https://profiles.wordpress.org/felipelavinz/">Felipe Lav&#237;n</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/mista-flo/">Florian TIAR</a> · <a href="https://profiles.wordpress.org/fpodhorsky/">fpodhorsky</a> · <a href="https://profiles.wordpress.org/francina/">Francesca Marano</a> · <a href="https://profiles.wordpress.org/fcoveram/">Francisco</a> · <a href="https://profiles.wordpress.org/bueltge/">Frank Bueltge</a> · <a href="https://profiles.wordpress.org/franz00/">franzaurus</a> · <a href="https://profiles.wordpress.org/fuadragib/">Fuad Ragib</a> · <a href="https://profiles.wordpress.org/galbaras/">Gal Baras</a> · <a href="https://profiles.wordpress.org/gamecreature/">gamecreature</a> · <a href="https://profiles.wordpress.org/garrett-eclipse/">Garrett Hyder</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/gisgeo/">gisgeo</a> · <a href="https://profiles.wordpress.org/glendaviesnz/">Glen Davies</a> · <a href="https://profiles.wordpress.org/gziolo/">Greg Zi&#243;łkowski</a> · <a href="https://profiles.wordpress.org/grl570810/">grl570810</a> · <a href="https://profiles.wordpress.org/gvgvgvijayan/">gvgvgvijayan</a> · <a href="https://profiles.wordpress.org/hvar/">H-var</a> · <a href="https://profiles.wordpress.org/hakre/">hakre</a> · <a href="https://profiles.wordpress.org/hanshenrik/">hanshenrik</a> · <a href="https://profiles.wordpress.org/hareesh-pillai/">Hareesh S</a> · <a href="https://profiles.wordpress.org/haritpanchal/">Harit Panchal</a> · <a href="https://profiles.wordpress.org/hasanmisbah/">Hasan Misbah</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/helgatheviking/">HelgaTheViking</a> · <a href="https://profiles.wordpress.org/ehtmlu/">Helmut Wandl</a> · <a href="https://profiles.wordpress.org/luehrsen/">Hendrik Luehrsen</a> · <a href="https://profiles.wordpress.org/hilayt24/">Hilay Trivedi</a> · <a href="https://profiles.wordpress.org/hiren1094/">hiren sanja</a> · <a href="https://profiles.wordpress.org/patelhitesh/">Hitesh Patel</a> · <a href="https://profiles.wordpress.org/hughiemolloy/">hughie.molloy</a> · <a href="https://profiles.wordpress.org/hugodevos/">hugodevos</a> · <a href="https://profiles.wordpress.org/hztyfoon/">hztyfoon</a> · <a href="https://profiles.wordpress.org/priethor/">Héctor Prieto</a> · <a href="https://profiles.wordpress.org/polevaultweb/">Iain Poulson</a> · <a href="https://profiles.wordpress.org/ianbelanger/">Ian Belanger</a> · <a href="https://profiles.wordpress.org/iandunn/">Ian Dunn</a> · <a href="https://profiles.wordpress.org/iazel/">Iazel</a> · <a href="https://profiles.wordpress.org/ignatggeorgiev/">Ignat Georgiev</a> · <a href="https://profiles.wordpress.org/imanish003/">imanish003</a> · <a href="https://profiles.wordpress.org/ingeniumed/">ingeniumed</a> · <a href="https://profiles.wordpress.org/innovext/">Innovext</a> · <a href="https://profiles.wordpress.org/inwerpsel/">inwerpsel</a> · <a href="https://profiles.wordpress.org/iqbalrony/">iqbalrony</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/itpathsolutions/">IT Path Solutions</a> · <a href="https://profiles.wordpress.org/ivanjeronimo/">ivanjeronimo</a> · <a href="https://profiles.wordpress.org/jhoffmann/">j.hoffmann</a> · <a href="https://profiles.wordpress.org/jackreichert/">Jack Reichert</a> · <a href="https://profiles.wordpress.org/jaedm97/">Jaed Mosharraf</a> · <a href="https://profiles.wordpress.org/jakariaistauk/">Jakaria Istauk</a> · <a href="https://profiles.wordpress.org/outrankjames/">James</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/janthiel/">Jan Thiel</a> · <a href="https://profiles.wordpress.org/janusdev/">janusdev</a> · <a href="https://profiles.wordpress.org/jsnajdr/">Jarda Snajdr</a> · <a href="https://profiles.wordpress.org/ipajen/">Jarko Piironen</a> · <a href="https://profiles.wordpress.org/javiarce/">Javier Arce</a> · <a href="https://profiles.wordpress.org/carazo/">Javier Carazo</a> · <a href="https://profiles.wordpress.org/javiercasares/">Javier Casares</a> · <a href="https://profiles.wordpress.org/jchambo/">jchambo</a> · <a href="https://profiles.wordpress.org/audrasjb/">Jean-Baptiste Audras</a> · <a href="https://profiles.wordpress.org/jeanphilippegreen/">Jean-Philippe Green</a> · <a href="https://profiles.wordpress.org/jeawhanlee/">jeawhanlee</a> · <a href="https://profiles.wordpress.org/jeffmatson/">Jeff Matson</a> · <a href="https://profiles.wordpress.org/jffng/">Jeff Ong</a> · <a href="https://profiles.wordpress.org/jeffpaul/">Jeffrey Paul</a> · <a href="https://profiles.wordpress.org/jmdodd/">Jennifer M. Dodd</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/lobeless14/">Jeremy Lind</a> · <a href="https://profiles.wordpress.org/jeryj/">jeryj</a> · <a href="https://profiles.wordpress.org/luminuu/">Jessica Lyschik</a> · <a href="https://profiles.wordpress.org/jhned/">jhned</a> · <a href="https://profiles.wordpress.org/jigar-bhanushali/">jigar bhanushali</a> · <a href="https://profiles.wordpress.org/jipmoors/">Jip Moors</a> · <a href="https://profiles.wordpress.org/joedolson/">Joe Dolson</a> · <a href="https://profiles.wordpress.org/joemcgill/">Joe McGill</a> · <a href="https://profiles.wordpress.org/joelmadigan/">joelmadigan</a> · <a href="https://profiles.wordpress.org/joen/">Joen Asmussen</a> · <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a> · <a href="https://profiles.wordpress.org/johnjamesjacoby/">John James Jacoby</a> · <a href="https://profiles.wordpress.org/johnwatkins0/">John Watkins</a> · <a href="https://profiles.wordpress.org/jokerrs/">Jokerrs</a> · <a href="https://profiles.wordpress.org/jb510/">Jon Brown</a> · <a href="https://profiles.wordpress.org/psykro/">Jonathan Bossenger</a> · <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a> · <a href="https://profiles.wordpress.org/jpantani/">Jonathan Pantani</a> · <a href="https://profiles.wordpress.org/jongycastillo/">Jong</a> · <a href="https://profiles.wordpress.org/spacedmonkey/">Jonny Harris</a> · <a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a> · <a href="https://profiles.wordpress.org/jornp/">jornp</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/joshuatf/">joshuatf</a> · <a href="https://profiles.wordpress.org/joyously/">Joy</a> · <a href="https://profiles.wordpress.org/jsh4/">jsh4</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/juhise/">Juhi Saxena</a> · <a href="https://profiles.wordpress.org/jrf/">Juliette Reinders Folmer</a> · <a href="https://profiles.wordpress.org/juliobox/">Julio Potier</a> · <a href="https://profiles.wordpress.org/justinahinon/">Justin Ahinon</a> · <a href="https://profiles.wordpress.org/greenshady/">Justin Tadlock</a> · <a href="https://profiles.wordpress.org/welenofsky/">Justin Welenofsky</a> · <a href="https://profiles.wordpress.org/justlevine/">justlevine</a> · <a href="https://profiles.wordpress.org/kadamwhite/">K. Adam White</a> · <a href="https://profiles.wordpress.org/kacper3355/">kacper3355</a> · <a href="https://profiles.wordpress.org/kafleg/">KafleG</a> · <a href="https://profiles.wordpress.org/kevin940726/">Kai Hao</a> · <a href="https://profiles.wordpress.org/kajalgohel/">Kajal Gohel</a> · <a href="https://profiles.wordpress.org/kaneva/">kaneva</a> · <a href="https://profiles.wordpress.org/kapilpaul/">Kapil Paul</a> · <a href="https://profiles.wordpress.org/zoonini/">Kathryn P.</a> · <a href="https://profiles.wordpress.org/kkoppenhaver/">Keanan Koppenhaver</a> · <a href="https://profiles.wordpress.org/ryelle/">Kelly Choyce-Dwan</a> · <a href="https://profiles.wordpress.org/kellychoffman/">Kelly Hoffman</a> · <a href="https://profiles.wordpress.org/kbat82/">Kevin Batdorf</a> · <a href="https://profiles.wordpress.org/kjellr/">Kjell Reigstad</a> · <a href="https://profiles.wordpress.org/obenland/">Konstantin Obenland</a> · <a href="https://profiles.wordpress.org/konyoldeath/">konyoldeath</a> · <a href="https://profiles.wordpress.org/kowsar89/">Kowsar Hossain</a> · <a href="https://profiles.wordpress.org/krunal265/">Krunal Bhimajiyani</a> · <a href="https://profiles.wordpress.org/krupalpanchal/">Krupal Panchal</a> · <a href="https://profiles.wordpress.org/kmadhak/">Kunal Madhak</a> · <a href="https://profiles.wordpress.org/lanacodes/">Lana Codes</a> · <a href="https://profiles.wordpress.org/larsmqller/">larsmqller</a> · <a href="https://profiles.wordpress.org/laurelfulford/">laurelfulford</a> · <a href="https://profiles.wordpress.org/laurlittle/">Lauren Stein</a> · <a href="https://profiles.wordpress.org/0mirka00/">Lena Morita</a> · <a href="https://profiles.wordpress.org/lenasterg/">Lena Stergatou</a> · <a href="https://profiles.wordpress.org/leonidasmilossis/">Leo Milo</a> · <a href="https://profiles.wordpress.org/lifeboat/">lifeboat</a> · <a href="https://profiles.wordpress.org/rudlinkon/">Linkon Miyan</a> · <a href="https://profiles.wordpress.org/lkraav/">lkraav</a> · <a href="https://profiles.wordpress.org/webaxones/">Lo&#239;c Antignac</a> · <a href="https://profiles.wordpress.org/thelovekesh/">Lovekesh Kumar</a> · <a href="https://profiles.wordpress.org/dreadlox/">Lox</a> · <a href="https://profiles.wordpress.org/lozula/">lozula</a> · <a href="https://profiles.wordpress.org/lucius0101/">lucius0101</a> · <a href="https://profiles.wordpress.org/lucymtc/">Lucy Tomas</a> · <a href="https://profiles.wordpress.org/gigitux/">Luigi</a> · <a href="https://profiles.wordpress.org/luisherranz/">luisherranz</a> · <a href="https://profiles.wordpress.org/pyrobd/">Lukman Nakib</a> · <a href="https://profiles.wordpress.org/pagelab/">M&#225;rcio Duarte</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/mahbubshovan/">Mahbub Shovan</a> · <a href="https://profiles.wordpress.org/mahekkalola/">Mahek Kalola</a> · <a href="https://profiles.wordpress.org/manfcarlo/">manfcarlo</a> · <a href="https://profiles.wordpress.org/manojkpatil/">Manoj Patil</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/marekdedic/">Marek Dědič</a> · <a href="https://profiles.wordpress.org/chaton666/">Marie Comet</a> · <a href="https://profiles.wordpress.org/tyxla/">Marin Atanasov</a> · <a href="https://profiles.wordpress.org/santosguillamot/">Mario Santos</a> · <a href="https://profiles.wordpress.org/marissamakes/">Marissa Matthews</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/marksabbath/">marksabbath</a> · <a href="https://profiles.wordpress.org/flootr/">Markus</a> · <a href="https://profiles.wordpress.org/mkox/">Markus Kosmal</a> · <a href="https://profiles.wordpress.org/mhkuu/">Martijn van der Klis</a> · <a href="https://profiles.wordpress.org/marybaum/">Mary Baum</a> · <a href="https://profiles.wordpress.org/matclayton/">matclayton</a> · <a href="https://profiles.wordpress.org/wetah/">Mateus Machado Luna</a> · <a href="https://profiles.wordpress.org/paapst/">Mathieu Paapst</a> · <a href="https://profiles.wordpress.org/matveb/">Matias Ventura</a> · <a href="https://profiles.wordpress.org/mmaattiiaass/">matiasbenedetto</a> · <a href="https://profiles.wordpress.org/mattkeys/">Matt Keys</a> · <a href="https://profiles.wordpress.org/matt/">Matt Mullenweg</a> · <a href="https://profiles.wordpress.org/matthiasreinholz/">Matthias Reinholz</a> · <a href="https://profiles.wordpress.org/h4l9k/">Mauricio</a> · <a href="https://profiles.wordpress.org/wppunk/">Max</a> · <a href="https://profiles.wordpress.org/cadic/">Max Lyuchin</a> · <a href="https://profiles.wordpress.org/maximej/">Maxime J.</a> · <a href="https://profiles.wordpress.org/jamilbd07/">MD Jamil Uddin</a> · <a href="https://profiles.wordpress.org/kawserz/">Md Kawser Ahmed Khan Jami</a> · <a href="https://profiles.wordpress.org/rakibwordpress/">Md Rakib Hossain</a> · <a href="https://profiles.wordpress.org/abirhasandipu/">Md. Abir Hasan Dipu</a> · <a href="https://profiles.wordpress.org/reduanmasud/">Md. Reduan Masud</a> · <a href="https://profiles.wordpress.org/mdviralsampat/">mdviralsampat</a> · <a href="https://profiles.wordpress.org/mehulkaklotar/">Mehul Kaklotar</a> · <a href="https://profiles.wordpress.org/mensmaximus/">mensmaximus</a> · <a href="https://profiles.wordpress.org/meyegui/">meyerdev.ch</a> · <a href="https://profiles.wordpress.org/mgol/">mgol</a> · <a href="https://profiles.wordpress.org/mburridge/">Michael Burridge</a> · <a href="https://profiles.wordpress.org/michael-kelly/">Michael Kelly</a> · <a href="https://profiles.wordpress.org/czapla/">Michal Czaplinski</a> · <a href="https://profiles.wordpress.org/michelmany/">Michel Many</a> · <a href="https://profiles.wordpress.org/miguelaxcar/">Miguel Axcar</a> · <a href="https://profiles.wordpress.org/mcsf/">Miguel Fonseca</a> · <a href="https://profiles.wordpress.org/mmtr86/">Miguel Torres</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/dimadin/">Milan Dinić</a> · <a href="https://profiles.wordpress.org/milana_cap/">Milana Cap</a> · <a href="https://profiles.wordpress.org/multidots1896/">Minal Diwan</a> · <a href="https://profiles.wordpress.org/mitchellaustin/">mitchellaustin</a> · <a href="https://profiles.wordpress.org/presents111/">miya</a> · <a href="https://profiles.wordpress.org/monzuralam/">Monzur Alam</a> · <a href="https://profiles.wordpress.org/mreishus/">mreishus</a> · <a href="https://profiles.wordpress.org/mrwweb/">mrwweb</a> · <a href="https://profiles.wordpress.org/mtias/">mtias</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/tanjimtc71/">Musarrat Anjum Chowdhury</a> · <a href="https://profiles.wordpress.org/amustaque97/">Mustaque Ahmed</a> · <a href="https://profiles.wordpress.org/mw108/">mw108</a> · <a href="https://profiles.wordpress.org/naeemhaque/">Naeem Haque</a> · <a href="https://profiles.wordpress.org/namithjawahar/">Namith Jawahar</a> · <a href="https://profiles.wordpress.org/nathanatmoz/">Nathan Johnson</a> · <a href="https://profiles.wordpress.org/nazmulhasan103/">Nazmul Hasan</a> · <a href="https://profiles.wordpress.org/nendeb55/">nendeb</a> · <a href="https://profiles.wordpress.org/neychok/">Neycho Kalaydzhiev</a> · <a href="https://profiles.wordpress.org/eidolonnight/">Nicholas Garofalo</a> · <a href="https://profiles.wordpress.org/nicholaswilson/">nicholaswilson</a> · <a href="https://profiles.wordpress.org/ndiego/">Nick Diego</a> · <a href="https://profiles.wordpress.org/nick_thegeek/">Nick the Geek</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/ntsekouras/">Nik Tsekouras</a> · <a href="https://profiles.wordpress.org/itsnikhilpatel/">NikhilPatel</a> · <a href="https://profiles.wordpress.org/dhrupo/">Niluthpal Purkayastha</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/rnitinb/">Nitin Rathod</a> · <a href="https://profiles.wordpress.org/nitman43/">nitman43</a> · <a href="https://profiles.wordpress.org/noahtallen/">Noah Allen</a> · <a href="https://profiles.wordpress.org/nuvopoint/">nuvoPoint</a> · <a href="https://profiles.wordpress.org/oakesjosh/">oakesjosh</a> · <a href="https://profiles.wordpress.org/obayedmamur/">Obayed Mamur</a> · <a href="https://profiles.wordpress.org/ockham/">ockham</a> · <a href="https://profiles.wordpress.org/oguzkocer/">oguzkocer</a> · <a href="https://profiles.wordpress.org/oh_hello/">oh_hello</a> · <a href="https://profiles.wordpress.org/hideokamoto/">Okamoto Hidetaka</a> · <a href="https://profiles.wordpress.org/oglekler/">Olga Gleckler</a> · <a href="https://profiles.wordpress.org/olliejones/">OllieJones</a> · <a href="https://profiles.wordpress.org/alshakero/">Omar Alshaker</a> · <a href="https://profiles.wordpress.org/paaljoachim/">Paal Joachim Romdahl</a> · <a href="https://profiles.wordpress.org/pablohoney/">PabloHoney</a> · <a href="https://profiles.wordpress.org/swissspidy/">Pascal Birchler</a> · <a href="https://profiles.wordpress.org/pbearne/">Paul Bearne</a> · <a href="https://profiles.wordpress.org/pbiron/">Paul Biron</a> · <a href="https://profiles.wordpress.org/paulkevan/">Paul Kevan</a> · <a href="https://profiles.wordpress.org/paulschreiber/">Paul Schreiber</a> · <a href="https://profiles.wordpress.org/pavelevap/">pavelevap</a> · <a href="https://profiles.wordpress.org/pbking/">pbking</a> · <a href="https://profiles.wordpress.org/pedromendonca/">Pedro Mendon&#231;a</a> · <a href="https://profiles.wordpress.org/pputzer/">pepe</a> · <a href="https://profiles.wordpress.org/petaryoast/">Petar Ratković</a> · <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a> · <a href="https://profiles.wordpress.org/petitphp/">petitphp</a> · <a href="https://profiles.wordpress.org/walbo/">Petter Walb&#248; Johnsg&#229;rd</a> · <a href="https://profiles.wordpress.org/phil-webster/">Phil Webster</a> · <a href="https://profiles.wordpress.org/phillsav/">Phill</a> · <a href="https://profiles.wordpress.org/iapial/">Pial</a> · <a href="https://profiles.wordpress.org/nekojonez/">Pieterjan Deneys</a> · <a href="https://profiles.wordpress.org/boniu91/">Piotrek Boniu</a> · <a href="https://profiles.wordpress.org/knowingart_com/">PJ Brunet</a> · <a href="https://profiles.wordpress.org/pkolenbr/">pkolenbr</a> · <a href="https://profiles.wordpress.org/pooja1210/">Pooja N Muchandikar</a> · <a href="https://profiles.wordpress.org/pravinparmar2404/">Pravin Parmar</a> · <a href="https://profiles.wordpress.org/presskopp/">Presskopp</a> · <a href="https://profiles.wordpress.org/ptahdunbar/">Ptah Dunbar</a> · <a href="https://profiles.wordpress.org/pypwalters/">pypwalters</a> · <a href="https://profiles.wordpress.org/raduiason/">raduiason</a> · <a href="https://profiles.wordpress.org/initsogar/">Rafael Agostini</a> · <a href="https://profiles.wordpress.org/rafinkhan/">Rafin</a> · <a href="https://profiles.wordpress.org/rajanpanchal2028/">Rajan Panchal</a> · <a href="https://profiles.wordpress.org/rajeshraval786/">Rajesh Raval</a> · <a href="https://profiles.wordpress.org/rahmohn/">Ramon Ahnert</a> · <a href="https://profiles.wordpress.org/ramon-fincken/">ramon fincken</a> · <a href="https://profiles.wordpress.org/ramonopoly/">Ramon James</a> · <a href="https://profiles.wordpress.org/razthee007/">Razthee Md. Yakini</a> · <a href="https://profiles.wordpress.org/renatoagds/">Renato Augusto Gama dos Santos</a> · <a href="https://profiles.wordpress.org/rezakhan995/">Reza Khan</a> · <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a> · <a href="https://profiles.wordpress.org/riccardodicurti/">Riccardo Di Curti</a> · <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a> · <a href="https://profiles.wordpress.org/rinkychowdhury9/">Rinky Chowdhury</a> · <a href="https://profiles.wordpress.org/ritteshpatel/">Ritesh Patel</a> · <a href="https://profiles.wordpress.org/rjasdfiii/">rjasdfiii</a> · <a href="https://profiles.wordpress.org/noisysocks/">Robert Anderson</a> · <a href="https://profiles.wordpress.org/robinwpdeveloper/">Robin</a> · <a href="https://profiles.wordpress.org/robin-labadie/">Robin Labadie</a> · <a href="https://profiles.wordpress.org/rodage/">rodage</a> · <a href="https://profiles.wordpress.org/rodricus/">rodricus</a> · <a href="https://profiles.wordpress.org/ravanh/">Rolf Allard van Hagen</a> · <a href="https://profiles.wordpress.org/digical/">Ross Gile</a> · <a href="https://profiles.wordpress.org/roytanck/">Roy Tanck</a> · <a href="https://profiles.wordpress.org/ruchirj/">Ruchir Goswami</a> · <a href="https://profiles.wordpress.org/re_enter_rupok/">Rupok</a> · <a href="https://profiles.wordpress.org/rryyaanndd/">Ryan</a> · <a href="https://profiles.wordpress.org/ryankienstra/">Ryan Kienstra</a> · <a href="https://profiles.wordpress.org/welcher/">Ryan Welcher</a> · <a href="https://profiles.wordpress.org/looswebstudio/">Ryo</a> · <a href="https://profiles.wordpress.org/sereedmedia/">S&#233; Reed</a> · <a href="https://profiles.wordpress.org/sergiomdgomes/">S&#233;rgio Gomes</a> · <a href="https://profiles.wordpress.org/soean/">S&#246;ren Wrede</a> · <a href="https://profiles.wordpress.org/andy786/">Sahil B.</a> · <a href="https://profiles.wordpress.org/stalukder03/">Sajib Talukder</a> · <a href="https://profiles.wordpress.org/sakibmd/">Sakib Mohammed</a> · <a href="https://profiles.wordpress.org/samful/">Sam Fullalove</a> · <a href="https://profiles.wordpress.org/sam1el/">sam1el</a> · <a href="https://profiles.wordpress.org/samiamnot/">samiamnot</a> · <a href="https://profiles.wordpress.org/viralsampat/">Sampat Viral</a> · <a href="https://profiles.wordpress.org/samruddhikhandale/">samruddhikhandale</a> · <a href="https://profiles.wordpress.org/otto42/">Samuel Wood (Otto)</a> · <a href="https://profiles.wordpress.org/sanjucta/">sanjucta</a> · <a href="https://profiles.wordpress.org/sanketchodavadiya/">Sanket Chodavadiya</a> · <a href="https://profiles.wordpress.org/sannevndrmeulen/">Sanne van der Meulen</a> · <a href="https://profiles.wordpress.org/sapayth/">sapayth</a> · <a href="https://profiles.wordpress.org/mikachan/">Sarah Norris</a> · <a href="https://profiles.wordpress.org/sarathar/">Sarath AR</a> · <a href="https://profiles.wordpress.org/saumil1611/">Saumil Nerpagar</a> · <a href="https://profiles.wordpress.org/ira2910/">Sazia Faizunnessa Ira</a> · <a href="https://profiles.wordpress.org/sc0ttkclark/">Scott Kingsley Clark</a> · <a href="https://profiles.wordpress.org/countrymusicchicago/">Scott Winterroth</a> · <a href="https://profiles.wordpress.org/hiyascout/">Scout James</a> · <a href="https://profiles.wordpress.org/seanchayes/">Sean Hayes</a> · <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a> · <a href="https://profiles.wordpress.org/seriouslysenpai/">seriouslysenpai</a> · <a href="https://profiles.wordpress.org/wandering-aramean/">Seth Miller</a> · <a href="https://profiles.wordpress.org/shahidul95/">Shahidul Islam</a> · <a href="https://profiles.wordpress.org/shamayel007/">Shamayel</a> · <a href="https://profiles.wordpress.org/shamimmiashuhagh/">Shamim Mia</a> · <a href="https://profiles.wordpress.org/smeunus/">Sharif Mohammad Eunus</a> · <a href="https://profiles.wordpress.org/shraboni/">Shraboni</a> · <a href="https://profiles.wordpress.org/shubham1gupta/">shubham1gupta</a> · <a href="https://profiles.wordpress.org/silicium23/">Silicium</a> · <a href="https://profiles.wordpress.org/simongomes02/">Simon Gomes</a> · <a href="https://profiles.wordpress.org/slieschke/">Simon Lieschke</a> · <a href="https://profiles.wordpress.org/siobhan/">Siobhan</a> · <a href="https://profiles.wordpress.org/calvinalkan/">snicco.io</a> · <a href="https://profiles.wordpress.org/sruthi90/">sruthi90</a> · <a href="https://profiles.wordpress.org/steelwagstaff/">SteelWagstaff</a> · <a href="https://profiles.wordpress.org/ryokuhi/">Stefano Minoia</a> · <a href="https://profiles.wordpress.org/stentibbing/">stentibbing</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/stephym/">Stephy Miehle</a> · <a href="https://profiles.wordpress.org/stephymiehle/">stephymiehle</a> · <a href="https://profiles.wordpress.org/stevenkword/">Steven Word</a> · <a href="https://profiles.wordpress.org/subrataemfluence/">Subrata Sarkar</a> · <a href="https://profiles.wordpress.org/sumitsingh/">Sumit Singh</a> · <a href="https://profiles.wordpress.org/sun/">sun</a> · <a href="https://profiles.wordpress.org/sunyatasattva/">sunyatasattva (a11n)</a> · <a href="https://profiles.wordpress.org/codemonksuvro/">Suvro</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/afrin29/">Syeda Sanjida Afrin</a> · <a href="https://profiles.wordpress.org/syhc/">syhc</a> · <a href="https://profiles.wordpress.org/synchro/">Synchro</a> · <a href="https://profiles.wordpress.org/syntaxart/">syntaxart</a> · <a href="https://profiles.wordpress.org/szaqal21/">szaqal21</a> · <a href="https://profiles.wordpress.org/tahmidulkarim/">Tahmid ul Karim</a> · <a href="https://profiles.wordpress.org/tahminar27/">tahminar27</a> · <a href="https://profiles.wordpress.org/inc2734/">Takashi Kitajima</a> · <a href="https://profiles.wordpress.org/tanazmasaba/">Tanaz Masaba</a> · <a href="https://profiles.wordpress.org/devtanbir/">Tanbir Ahmod</a> · <a href="https://profiles.wordpress.org/tanner-m/">Tanner Moushey</a> · <a href="https://profiles.wordpress.org/rahmantasnia/">Tasnia Rahman Raima</a> · <a href="https://profiles.wordpress.org/teebee/">teebee</a> · <a href="https://profiles.wordpress.org/tekapo/">tekapo</a> · <a href="https://profiles.wordpress.org/thedaysse/">thedaysse</a> · <a href="https://profiles.wordpress.org/iamjaydip/">thejaydip</a> · <a href="https://profiles.wordpress.org/theode/">theode</a> · <a href="https://profiles.wordpress.org/griffinjt/">Thomas Griffin</a> · <a href="https://profiles.wordpress.org/thomasplevy/">Thomas Patrick Levy</a> · <a href="https://profiles.wordpress.org/thomask/">thomask</a> · <a href="https://profiles.wordpress.org/timbroddin/">timbroddin</a> · <a href="https://profiles.wordpress.org/sippis/">Timi Wahalahti</a> · <a href="https://profiles.wordpress.org/spaceshipone/">Timoth&#233;e Brosille</a> · <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a> · <a href="https://profiles.wordpress.org/tobiasbg/">TobiasBg</a> · <a href="https://profiles.wordpress.org/tobifjellner/">tobifjellner (Tor-Bjorn Fjellner)</a> · <a href="https://profiles.wordpress.org/tjnowell/">Tom J Nowell</a> · <a href="https://profiles.wordpress.org/dziudek/">Tomasz Dziuda</a> · <a href="https://profiles.wordpress.org/skithund/">Toni Viemer&#246;</a> · <a href="https://profiles.wordpress.org/starbuck/">Tony G</a> · <a href="https://profiles.wordpress.org/hellofromtonya/">Tonya Mork</a> · <a href="https://profiles.wordpress.org/zodiac1978/">Torsten Landsiedel</a> · <a href="https://profiles.wordpress.org/toru/">Toru Miki</a> · <a href="https://profiles.wordpress.org/itowhid06/">Towhidul I Chowdhury</a> · <a href="https://profiles.wordpress.org/travisaxton/">travisaxton</a> · <a href="https://profiles.wordpress.org/triumvirate/">triumvirate</a> · <a href="https://profiles.wordpress.org/dinhtungdu/">Tung Du</a> · <a href="https://profiles.wordpress.org/umesh84/">Umesh Gupta</a> · <a href="https://profiles.wordpress.org/upadalavipul/">upadalavipul</a> · <a href="https://profiles.wordpress.org/eboxnet/">Vagelis</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/virgar/">Virginie Garnier</a> · <a href="https://profiles.wordpress.org/elifvish/">Vishal Kumar</a> · <a href="https://profiles.wordpress.org/vladytimy/">Vlad T</a> · <a href="https://profiles.wordpress.org/vtad/">vtad</a> · <a href="https://profiles.wordpress.org/vykesmac/">vykesmac</a> · <a href="https://profiles.wordpress.org/webmandesign/">WebMan Design &#124; Oliver Juhas</a> · <a href="https://profiles.wordpress.org/webrocker/">Webrocker</a> · <a href="https://profiles.wordpress.org/websitegenii/">websitegenii</a> · <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a> · <a href="https://profiles.wordpress.org/whaze/">whaze</a> · <a href="https://profiles.wordpress.org/winterpsv/">winterpsv</a> · <a href="https://profiles.wordpress.org/wojsmol/">wojsmol</a> · <a href="https://profiles.wordpress.org/wojtekn/">Wojtek Naruniec</a> · <a href="https://profiles.wordpress.org/wojtekszkutnik/">Wojtek Szkutnik</a> · <a href="https://profiles.wordpress.org/fierevere/">Yui</a> · <a href="https://profiles.wordpress.org/yuliyan/">Yuliyan Slavchev</a> · <a href="https://profiles.wordpress.org/zebaafiashama/">Zeba Afia Shama</a> · <a href="https://profiles.wordpress.org/zenaulislam/">Zenaul Islam</a> · <a href="https://profiles.wordpress.org/zevilz/">zevilz</a> · <a href="https://profiles.wordpress.org/zieladam/">zieladam</a> · <a href="https://profiles.wordpress.org/chesio/">Česlav Przywara</a></p>



<p>By release day, <a href="https://translate.wordpress.org/stats/">70 locales had translated 90 percent</a> or more of WordPress 6.2 in their language. Community translators are hard at work ensuring more translations are on their way. Thank you to everyone who helps to make WordPress 6.2 available in 200 languages.</p>



<h2 class="wp-block-heading">A release haiku for 6.2&nbsp;</h2>



<p>Six point two, so new<br />Shiny and ready for you<br />Congrats on hard work!</p>



<p class="has-text-align-left has-tiny-font-size"><em>* Portrait of Eric Allen Dolphy Jr. discovered via <a href="https://openverse.org/image/36720968-690c-4287-a2dd-619573cc23a6">Openverse</a>. Colorization by D. Pountain; Original by F. Wolff</em>.<br />&#8220;<a rel="noreferrer noopener" href="https://www.flickr.com/photos/98119031@N00/39509743850" target="_blank">eric dolphy</a>&#8221; by&nbsp;<a rel="noreferrer noopener" href="https://www.flickr.com/photos/98119031@N00" target="_blank">dick_pountain</a>&nbsp;is licensed under&nbsp;<a rel="noreferrer noopener" href="https://creativecommons.org/licenses/by-nc-sa/2.0/?ref=openverse" target="_blank">CC BY-NC-SA 2.0</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, 29 Mar 2023 18:57:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:65:"WPTavern: #69 – Joost De Valk on What’s Happening After Yoast";s:7:"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=143046";s:7:"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/podcast/69-joost-de-valk-on-whats-happening-after-yoast";s: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:39389:"Transcription<div>
<p>[00:00:00] Nathan Wrigley: 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, what the founder of Yoast is working on now.</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 very 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 Joost de Valk.</p>



<p>If you&#8217;ve been in the WordPress space for any length of time, it&#8217;s likely that you&#8217;ve come across the Yoast SEO plugin. This was the brain child of the guests today, Joost. Same pronunciation, different spelling.</p>



<p>We talk about how Joost found WordPress and quickly started working on his SEO plugin. How it rapidly grew and became his career.</p>



<p>We discussed the WordPress landscape during this time, and whether it&#8217;s more difficult now to have the type of success that his plugin received, given that there are more players vying for our attention.</p>



<p>The conversation then moves into why the plugin was recently sold to Newfold Digital. What were the guardrails that were put in place to ensure that the plugin continued and the employees felt safe?</p>



<p>We then get into a conversation about Joost&#8217;s new role. He&#8217;s been tasked with reaching out to WordPress community members in order to see what projects or initiatives need more thought and support.</p>



<p>This leads us into the topic of the current WordPress UI, and how Joost is hoping for a refresh at some point soon. For years, his plugin team wanted to create their own UI to take advantage of new technologies, but Joost always pushed back, preferring instead to adopt the style of the WordPress UI. Now that&#8217;s changed, and the open sourcing of the UI kit they&#8217;ve made is intended as a starting point for a discussion about the need for a more consistent admin experience for all WordPress users.</p>



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



<p>And so without further delay, I bring you Joost de Valk.</p>



<p>I am joined on the podcast today by Joost de Valk. Hello Joost.</p>



<p>[00:03:32] Joost de Valk: Hey, thank you for having me.</p>



<p>[00:03:34] Nathan Wrigley: You are very, very welcome. It&#8217;s an absolute pleasure to have somebody of your stature in the WordPress community. You&#8217;ve been with WordPress for a really long time. Certainly whilst I&#8217;ve been using WordPress, I joined the party a little bit later than a lot of people. But your company and your name was already a really big deal.</p>



<p>If anybody hasn&#8217;t heard of you, I&#8217;d appreciate it if just for a few minutes, you could just give us a little bit of your background story. Where you are, what companies you&#8217;ve worked for, how on earth did you get into WordPress and so on.</p>



<p>[00:04:05] Joost de Valk: Okay, so that&#8217;s a lot to cover, but let me try. So, I am Joost. I&#8217;m Dutch. I live in the Netherlands with my lovely wife Marieke, who I think you&#8217;ve also had on your show, and our four kids.</p>



<p>I started Yoast coming from a background of working in several different IT companies. I started university, basically failed at university because I wasn&#8217;t a very good student. Then started working in IT, in a web hosting company. And later on moved into an SEO company where I learned SEO consulting.</p>



<p>When I started doing that, I had already been coding a bit. I&#8217;ve actually always been coding since I was 12. I built my first website when I was 12, which was in 1994, so you can do the math. I&#8217;d been working on that and I, I learned SEO at this company. Started blogging, and then also started building plugins for the blog platform that I chose, which happened to be WordPress. Building plugins to basically fix my own SEO needs. This was in 2005, 2006. So that&#8217;s relatively early days.</p>



<p>I started contributing to WordPress Core at basically the same time. I&#8217;d been doing other open source software development. I was a part of the WebKit project, which is the core of Safari, and Chrome. Actually committer in that project before I joined the WordPress world.</p>



<p>And I had two sites. I had one where I blogged about SEO, and one where I blogged about CSS. And my specialty at that time was CSS 3, which was at that point being created, and I was creating CSS 3 previews. So I was doing SEO for that, building my own plugins, just for myself. And I started releasing them and more people started using them. I started speaking at SEO conferences, and people started asking about these plugins.</p>



<p>And one thing led to another. And some point in 2010 I decided to start working on my own. At that point thinking I would never hire anybody, but I would just be an SEO consultant, which is why I called the company after myself. Which in hindsight was a stupid idea, because whilst it is a very beautiful brand name, it is super annoying to hear your own name the whole day, because you can&#8217;t really not hear that.</p>



<p>So, did that in 2010. Basically started SEO consulting. I was consulting for pretty large brands at that time, Facebook, eBay, the Guardian, companies like that. And, well I was still doing that plugin. Decided to bundle the several small plugins that I&#8217;d built into one larger WordPress SEO plugin, which later on became the Yoast SEO plugin.</p>



<p>And then, at some point during 2011, I hit a million users with what was called WordPress SEO at the time. And Marieke said to me, you can&#8217;t keep doing this. You either have to start making money from this, or stop doing it, because this is nonsense. And she was, as always, right.</p>



<p>And then started working on that. And she joined quite quickly. Had a couple of other colleagues who I&#8217;d hired to do part of the other work that I was doing at that point already. And we started building, and that went quite well for a very long time. So we sold in 2021, and at that point we had almost 150 employees, and a very well running business. So we&#8217;d been growing between 30 and 50% year over year for almost a decade. And yeah, it&#8217;s been a very interesting journey. And throughout that time I&#8217;ve been doing WordPress, because I love WordPress as a system, and I love the open source community.</p>



<p>[00:08:05] Nathan Wrigley: I have a quick comment in here and I love how you described it, your successes. We did quite well. To get a million users in the space of, well, it sounds like under a year.</p>



<p>[00:08:17] Joost de Valk: Well, no, it was, it was slightly more because it was, I had small plugins that people were already using, and then I bundled them into one. So I was basically combining all these user bases. But yeah, no, it, it did go very quickly. So a fairly limited amount of companies I&#8217;ve seen that do it quickly, although I have to say if you look at Elementor, similar and better actually.</p>



<p>[00:08:39] Nathan Wrigley: When you look back at that time, do you consider that you entered WordPress at what might be described as halcyon days or something? Was there just something about it at that time, which was ripe for the picking? Because the growth from zero to a million, I mean very, very few plugins managed to jump that hurdle. And the fact that you did it, let&#8217;s say, relatively quickly, really quickly in fact, is pretty amazing. But I just wondered if the, if it was more wild west back then? If it was more possible because there was less competition, there was less rivals in the space. Do you have any insight into why it was so successful?</p>



<p>[00:09:19] Joost de Valk: So part of it is that the people that were building WordPress sites at that time were, almost all of them developers, or at least website maintainers with a fairly good technical grasp. And they switched plugins fairly easily and often. I think that was a bit easier than it is now. Although that group is still there, but it&#8217;s just a smaller portion of the entire user base of WordPress now.</p>



<p>So yeah, it was a bit different. It was a bit more pioneering I think, in a way. The thing is, we build these ginormous websites on WordPress now, right? So these enormously important websites as well to people. And you&#8217;re not going to play around with plugins on sites like that. So it&#8217;s on personal blogs that you can do that. And just a lot more people did have a personal blog at that time. It was probably the best days for the actual blogoshpere in comparison to what later happened with Twitter, et cetera.</p>



<p>[00:10:19] Nathan Wrigley: We probably could spend the entire podcast talking about Yoast over the years, but we&#8217;re not going to do that, because we&#8217;ve decided to take a different route. But I, do want to ask, in terms of your journey since the day that you committed to having Yoast a plugin, right through to maybe today, maybe a year or two ago.</p>



<p>Were you always in love with WordPress, the community and so on? I get the feeling that there might have been a few wrinkles along the way where the whole ecosystem was something that you wanted a little bit of a break from. I could be getting that wrong. If so, ignore the question.</p>



<p>[00:10:53] Joost de Valk: I don&#8217;t think I&#8217;ve ever really wanted a break from WordPress itself. I think the community is a wonderful thing, but at the same time it&#8217;s very brittle. People come and go, and that&#8217;s fine, right? But we, I feel, have failed in the last few years especially to, well to show our excitement for it to each other.</p>



<p>I think part of that is Covid, because there weren&#8217;t as many WordCamps and other things while we did that. Part of that is also, we&#8217;re all growing up and all these companies are becoming bigger and, well the demands on those companies are getting bigger. But it&#8217;s also like we&#8217;re getting more professional, but with that maybe also a bit more dull</p>



<p>[00:11:37] Nathan Wrigley: So you&#8217;re still committed to WordPress. Is that the case? Are you going to be with WordPress do you imagine 3 or 4, 5, 10 years from now? You&#8217;ll still be coming on podcasts like this and talking about WordPress, albeit in a different role?</p>



<p>[00:11:51] Joost de Valk: I absolutely hope so, yeah. If I wasn&#8217;t thinking that, I wouldn&#8217;t have taken on this new role that I took on at Newfold.</p>



<p>[00:11:58] Nathan Wrigley: Yeah, let&#8217;s talk about that. But before we get onto that, I would imagine there&#8217;s a subset of users who know that Yoast as a plugin exists, but they may not know about the ownership and the structure and how it&#8217;s all run and what have you. Just run us through that little piece. A little while ago it was announced that you had sold to Newfold Digital. What was the reasoning behind that? So that could be maybe there were personal reasons behind that. Maybe it was just something that you wanted to get away from and give yourself a bit of head space, try something new. What was going on in the run up to that, and how did it all go?</p>



<p>[00:12:32] Joost de Valk: So, well running a company&#8217;s hard. And as a company becomes bigger, it becomes harder. And during Covid, Marieke and I decided it&#8217;s time. It&#8217;s time to, to sell it and to look at, like, hey, what else do we want to do? And we were talking about that to our other partners. I think we all felt the same at that point.</p>



<p>And so we went into a process. We actually engaged a banker who helped us sell the company. And we ended up with Newfold Digital, which is not really a household name, but it&#8217;s the parent company to companies like Bluehost, Hostgator, domain.com, and multiple dozens of other brands.</p>



<p>They put in a good offer, but they also had a very good story about why they wanted to buy Yoast, and what they would do with it. And that really was very interesting to us. And then, they ended up after acquiring us, quite quickly after that, they also acquired Yith. A WooCommerce plugin shop, also from Europe. It&#8217;s been good. It&#8217;s a very nice group of people.</p>



<p>[00:13:41] Nathan Wrigley: With the transition there, when you went out and as you said, you got some third party in, who obviously had your best interest, but also presumably could be somewhat dispassionate as well. Did you have any sort of guardrails? Because you described that you&#8217;d grown from, well, you solo up to 150 employees, and just before we hit record, you were mentioning that in some cases, some of your employees have been there for as much as a decade. You know, there&#8217;s a real long heritage of people working there. So presumably a lot of these people, you&#8217;re very close to them. Friends you might say.</p>



<p>[00:14:15] Joost de Valk: Absolutely, yes.</p>



<p>[00:14:17] Nathan Wrigley: I presume part of that process was protecting them, knowing that when you stepped away and released the reins, that whoever took over the reins was going to behave in a way that you would have behaved. Did you get into that? Did you struggle with that? Was there any, any pieces that you needed to in place?</p>



<p>[00:14:36] Joost de Valk: It&#8217;s definitely a part of why you&#8217;re thinking very long and hard about who you&#8217;re selling your company to. To some extent, we don&#8217;t need to do all the defense because there&#8217;s Dutch law that will actually prevent them from just firing people. If I lived in an at will firing world, I would probably think about this even more specifically.</p>



<p>But, honestly it was never a question, they wanted the people. And they wanted everyone to come board and to stay on. And actually in the first year after we sold to Newfold, nobody left. Or in the first six months, I should probably say, I don&#8217;t know whether it&#8217;s entirely true for the first year. Nobody left for a long time.</p>



<p>No, I think actually treating your employees well is super important. To be fair, that&#8217;s always been one of the things that Marieke has run at our company. So for a long time I was the CEO, then she took over from me. So she was the CEO for the last three years before we sold. Well, she did a tremendous job at making well, creating that culture and making it even better.</p>



<p>We do indeed have quite a few people that work here for, well, five years or longer. And a couple of them, two people now who are at a decade and one is closing in, yeah.</p>



<p>[00:15:51] Nathan Wrigley: You mentioned, I can&#8217;t remember whether it was in the conversation we&#8217;ve just had or whether I read it in some show notes. But Newfeld Digital, the company that you ultimately sold for. This for now at least, this is the direction of travel for you. What&#8217;s the role that you&#8217;ve taken on there and what are the sort of key points that you are trying to achieve? You also mentioned that it&#8217;s not a household name. I suspect there&#8217;s some will to change that might be part of your role.</p>



<p>[00:16:15] Joost de Valk: Not necessarily, I mean, Newford is a corporate brand mostly aimed at other things than, it&#8217;s not like we need everyone to know Newford. But I do think it&#8217;s, well the combination of Bluehost and Yith and Yoast, and quite a few other things under our umbrella make us quite a big player in the WordPress world. We are, I think, the biggest or the second biggest WordPress host out there. Maybe GoDaddy&#8217;s bigger, I honestly don&#8217;t know.</p>



<p>So my role specifically for the foreseeable future, is to look at hey, what&#8217;s happening in the WordPress world? How can Newfold help WordPress, and what can we do in the WordPress world that would benefit both Newfold and the WordPress world?</p>



<p>And how can we use our knowledge of WordPress internally a bit better as well. It&#8217;s funny how this works at large hosts and these are, Newfold is not unique in that I&#8217;ve found. I&#8217;ve been talking to other people in the hosting space a lot in the last few months. A lot of these hosting companies, only in the last few years have started realizing that they&#8217;re actually WordPress companies.</p>



<p>There&#8217;s a bit of a catch up to do there. Well, it&#8217;s one of the things that I want to focus on is like, how can we see that these large hosts who make a lot of money on WordPress and who together create quite a big economy, that they contribute back to WordPress as well? And what can we do about that?</p>



<p>[00:17:40] Nathan Wrigley: So if I&#8217;m right, your role is head of WordPress strategy for Newfold Digital? That is a part of it. It&#8217;s just trying to figure out where WordPress fits in the overall structure, the products that you&#8217;ve got, the direction that you&#8217;re going to take, the events that you&#8217;re going to show up to, and all of that?</p>



<p>[00:17:57] Joost de Valk: Yeah, absolutely. And it is honestly, it&#8217;s sort of a perfect role because I have no one reporting to me, and yet I get to talk about these things, which I love.</p>



<p>[00:18:08] Nathan Wrigley: What have been some of the things that you have been mulling over that at Newfold you think you might like to get your hands dirty on?</p>



<p>[00:18:15] Joost de Valk: Well, I think it actually ties into one of the other things you wanted to talk about, which is the WordPress Admin UI. So we did a new settings UI for Yoast, and as I was looking at it and we were building that. I was talking to my colleagues at Newfold responsible for the Bluehost interface and for Yith, and we were like, hey, can&#8217;t we just use this across the company?</p>



<p>So it&#8217;s stuff like that where we, we help each other with our knowledge of WordPress. And we also let people who are good at one specific thing inside WordPress do that. But it&#8217;s also like, okay, we have a couple of different teams of WordPress Core contributors within Newfold. How can we effectively use those?</p>



<p>So yeah, there&#8217;s a lot of different angles to it. There&#8217;s how do we make more money from WordPress? What direction does WordPress need to go, and how can we help that? How do we make WordPress better usable for our customers so that we actually maintain our customers better? There&#8217;s a lot of different things to do.</p>



<p>[00:19:17] Nathan Wrigley: You&#8217;ve been really keen publishing statistics over the years about WordPress adoption and WordPress usage and all of those kind of things. So it really does seem like the perfect role for you. You&#8217;re very interested in the bigger picture of WordPress and how widely it&#8217;s adopted and whether the numbers are going up or going down and publishing data about all that. Yeah, it&#8217;s fascinating.</p>



<p>[00:19:35] Joost de Valk: It is. WordPress is just a perfect project for a large number of the websites out there. And honestly, I think that we, that we don&#8217;t always do ourselves a good service as WordPress on marketing what we can do. And we&#8217;ve also, I think, underinvested a little in some parts of WordPress, in terms of performance and in terms of onboarding, that we should probably invest a bit more in.</p>



<p>[00:20:02] Nathan Wrigley: Yeah, that&#8217;s an interesting point. Just as a segue, the whole performance thing, not the onboarding piece, but the performance bit in particular. I feel that&#8217;s, that&#8217;s really been kickstarted over the last 12 months. There seems to be a lot of work going into performance and a lot of chatter about it.</p>



<p>Whether everything should be bundled into one performance plugin or whether it should be split out and become different canonical plugins, if you like. So I think you&#8217;re right. I think it&#8217;s quite interesting that some of the things that you&#8217;ve just mentioned do seem to be getting some attention, and performance is just one that springs to mind.</p>



<p>[00:20:36] Joost de Valk: Things like performance on an individual site level, they&#8217;re important, but if you are the host that is hosting literally millions of WordPress sites. It is just literally also cost to your bottom line.</p>



<p>[00:20:49] Nathan Wrigley: Yeah, I hadn&#8217;t really thought about it from that perspective. But if you can shave, I don&#8217;t know, 5% of CPU cycles out of the whole hosting platform, that&#8217;s quite a large amount of money that you&#8217;ve saved.</p>



<p>[00:20:59] Joost de Valk: Yeah, and we did a lot more than that in recent releases. So it&#8217;s been in the double digits. And that&#8217;s absolutely a good thing for, well, not just for our bottom line, but for nature and for electricity usage. I mean, there&#8217;s tons of reasons to want to do better at that. And I think there&#8217;s still a lot more that we could do.</p>



<p>[00:21:21] Nathan Wrigley: I think it does seem genuinely to be a perfect role given, well, given that I don&#8217;t know you particularly well, but from all of the things that I&#8217;ve read over the years, it seems like this is kind of like a match made in heaven.</p>



<p>[00:21:32] Joost de Valk: Yeah, and it is actually a very nice team. So it&#8217;s, it is very nice to be able to work with these people, and look at like, hey, what can we do here? And yeah, I hope to be able to make an impact.</p>



<p>[00:21:42] Nathan Wrigley: Let&#8217;s talk about the UI, because over the years, if you&#8217;ve been using WordPress for all these years, you must have logged into WordPress, oh, I daren&#8217;t even count. But it&#8217;s probably multiple tens of thousands of times. And each time you&#8217;ve logged in, you&#8217;ve stared at the same UI. And certainly over the last decade, that UI has been exactly the same.</p>



<p>It basically has looked the same since I started WordPress, with tiny, teeny modifications to things like the color blue. There&#8217;s a slight variation in the color blue that&#8217;s being used now than previously. But broadly speaking, it&#8217;s exactly the same.</p>



<p>You guys, and we&#8217;re going to use Yoast as an example, but it really, it could be any company. You guys took it into your own hands to say, enough. We think that the UI, if we stick with WordPress standard UI, it doesn&#8217;t really fit what we&#8217;re doing. Technology&#8217;s moved on. We&#8217;ve got more things available to us. Certainly the way things look in WordPress is beginning to be a little bit tired.</p>



<p>Tell me about that journey. And are you hoping that your free UI kit, that you&#8217;ve open sourced is going to be taken on? Maybe it&#8217;s a cue for the team over at .org to have a look at this and adopt this across WordPress, dare I say?</p>



<p>[00:22:53] Joost de Valk: I honestly doubt that&#8217;ll happen. Yeah, no, I doubt that. Not because they are against using something that we&#8217;ve built, but because what we build is quite opinionated and uses stuff that they might not be willing to use, like Tailwind.</p>



<p>It definitely needs a change. It&#8217;s been a tired look for, well, almost a decade as well now. We&#8217;ve had experiments. We&#8217;ve not really moved on that. Gutenberg itself has changed in what it looks like a couple of times over its development, and now we&#8217;re basically stuck with three different types of designs, even within the WordPress admin.</p>



<p>[00:23:29] Nathan Wrigley: Yeah, tell us what you mean by that because I&#8217;m not sure everybody will pick up the nuance of that.</p>



<p>[00:23:33] Joost de Valk: Well, if you look at the site health page, it uses different styling from say, add a post. And then go into a post and you edit it in Gutenberg, then that looks entirely different as well. And, I just think that&#8217;s weird. I think it&#8217;s weird that we have different types of buttons. I think it&#8217;s weird that we basically teach a user two or three different UIs. And if you use the customizer with it, then even more. So you&#8217;re basically teaching people new user experiences all the time, and that makes it hard to use.</p>



<p>And then because there is no real design system for WordPress anymore, that you can use to build your plugin&#8217;s admin pages, everyone starts building their own and all of them start looking differently. And that means that if you have five plugins, you have five different admin pages. And I just don&#8217;t think that that&#8217;s a good experience.</p>



<p>[00:24:35] Nathan Wrigley: Yeah, I guess if you are a user of WordPress, a frequent user of WordPress, and you&#8217;ve got let&#8217;s say, the one site that you are maintaining all five sites or whatever it may be. Because you&#8217;re in there all the time, that dissonance doesn&#8217;t really happen for you as much, does it? You know, you&#8217;re just familiar with it.</p>



<p>Okay. If I go in here, I&#8217;m going to expect that the menu&#8217;s going to change. The whole color palette and everything. The buttons will look different, but okay, that&#8217;s how it is. But if WordPress continues to grow, and it wants to get into the late forties and early 50%, which is, I guess, a target which is within reach. That isn&#8217;t really going to fly anymore, is it?</p>



<p>Because if you go to any SaaS app, let&#8217;s say for example, I don&#8217;t know, let&#8217;s say you go over to Google and you want to interact with Google Docs, it would be really weird if the UI for Docs was different from spreadsheets. And, I don&#8217;t know, let&#8217;s say that you are using Notion or Evernote or something like that. If when you went into some portion of it, it was just different.</p>



<p>You just fully expect everything to look and feel the same. And in our own experience of WordPress, we just forgive that, don&#8217;t we? We just, oh, okay, that plugin author has done this. But if you are looking to compete against the rising stars, Wix, Squarespace, Shopify, all these other things, that really starts to matter.</p>



<p>It&#8217;s a bit like death by a thousand teeny, tiny little paper cuts. Those things stick in the head of the end user. That just seems a bit unprofessional. Not sure about this WordPress thing. Do you think I&#8217;ve hit the target there?</p>



<p>[00:26:08] Joost de Valk: Yeah, no, absolutely. I think that is our problem. I think it actually ties into the other thing I mentioned, the onboarding. It&#8217;s actually pretty hard to start using WordPress. So you are thrown into a dashboard and then the first thing you&#8217;re greeted with is WordPress meetups. And as much as I love WordPress meetups, if you are just on that page for the first time, why are those in my screen?</p>



<p>And, well there&#8217;s a hundred things like that where I think that we, we could and probably should do better. And the first thing would be, in my opinion, a design system that we all agree on. And I think that is actually an achievable goal. I spoke a bit, before and after I published my post, to a couple of people from the design team, Joan and Mathias, and they also seemed to want something like that.</p>



<p>We seem to disagree a bit on how far, in how far that actually already exists. Because there is a somewhat of a component system within Gutenberg. I just think that as long as I search for WordPress design system and don&#8217;t get a post or page from WordPress.org, that actually explains the design system in simple to use terms for every plugin developer out there, it doesn&#8217;t exist.</p>



<p>That means that we have to build it. We have to market it. We have to think about how it&#8217;s going to be used and then write good docs for that. That&#8217;s quite a bit of work, but it&#8217;s not unconceivable that we do that. There&#8217;s a lot of people in the WordPress world who want to make that happen. We&#8217;re just not prioritizing it at the moment. And I think we&#8217;re doing ourselves a disservice by not doing that.</p>



<p>[00:27:45] Nathan Wrigley: I am going to link in the show notes to an article that you put out recently where you express a lot of these thoughts. And in it you make the point that it was a really difficult decision over at Yoast. Sorry to keep going back to Yoast.</p>



<p>[00:27:59] Joost de Valk: No, it&#8217;s not a problem. It was a very difficult decision. We&#8217;ve been literally been talking about this for five, six years, and my UX team at Yoast had been wanting to do a redesign for a long time, and I basically stopped them all the time because I was like, I want to stay in line with the WordPress admin.</p>



<p>And over time we started moving away from it more and more because we needed stuff that simply wasn&#8217;t there. And then at some point you have to admit like, okay, I&#8217;m wrong. This is not going to happen and we need to build our own. It was sort of like a bittersweet decision. And I&#8217;m happy to add that people are responding well to the library that we built and that, that we open sourced.</p>



<p>Because I want to spare others to work. Because it&#8217;s stupid. It&#8217;s stupid that as a plugin developer, I have to spend time thinking about what do my buttons look like? What do my toggles look like? They should just be the same for everyone.</p>



<p>[00:29:03] Nathan Wrigley: I can completely sympathize with that, in the sense that you&#8217;ve spent years basically saying, no, to your design team. We&#8217;re just going to stick with this. But eventually, I guess there&#8217;s too much water has gone under that bridge that really you&#8217;re stifling your own company&#8217;s enterprise.</p>



<p>[00:29:20] Joost de Valk: Literally, I mean, people moved to others plugins because they thought it looked better. Which I think is a stupid reason to switch SEO plugins. But who am I? But it was literally happening, and I, at some point you go like, okay, I really need to do better at this. And to be fair, the new settings you are that we ended up building, I think our UX team did an amazing job on, and makes the plugin a lot easier to use.</p>



<p>[00:29:49] Nathan Wrigley: I will link to the design library, which has been open sourced again in the show notes, but it&#8217;s a really amazing endeavor. If you are a plugin developer or, you know, you have aspirations to be, it&#8217;s definitely well worth checking out because looks like Yoast have really gone to town. It&#8217;s soup to nuts. Almost every component or element that you could possibly imagine putting inside of a WordPress UI, is there, you know. Progress bars, radio buttons. Every single thing is there with loads of instructions on how to implement it.</p>



<p>I guess if the endeavor was to begin that conversation, then already, I think it&#8217;s been a success. If the endeavor of this blog post and the, the new UI that you&#8217;ve bring into existence. If the endeavor there was to start a conversation about this, then yeah, I think you&#8217;ve done that.</p>



<p>[00:30:39] Joost de Valk: At this point we&#8217;ve invested so much time that I don&#8217;t see us switching to something else anytime soon. But that also sort of saddens. That&#8217;s why I wrote the post on my personal blog. I&#8217;m like, this is not necessarily the decision I would&#8217;ve wanted to make. But yeah, you are sort of forced into it. At that point it&#8217;s better if we build something and we open source it, and then maybe a lot of others can use it as well. And maybe we can actually get to an interface where we all sort of look alike.</p>



<p>[00:31:08] Nathan Wrigley: Have you been in the role at Newfold long enough to have interfaced with customers to know that this is a, a thing which is stifling WordPress growth. The fact that it does look out of date. The fact that it&#8217;s a jumble of different colors and patterns and design libraries being in used in different plugins. Does this turn people off in the real world?</p>



<p>[00:31:28] Joost de Valk: I&#8217;m a hundred percent sure. You test with these things, of course, and you see the data on how many people start. Register with a host. They get a hosting package. They get a WordPress site, and how many then get to a published site? Not everyone gets to a published site, and that I think will never happen, but well the more that do, the more that will basically remain customers. So for a host, that&#8217;s an important metric.</p>



<p>And people just get stuck. And then when you look at where they get stuck, they get stuck at picking a theme. And then when they have a theme, they get stuck at making it look good, especially making it look like the demo.</p>



<p>And then they get stuck at building pages. They get stuck at several phases. And there&#8217;s quite a few of those phases that you have to get through before you get to a website that you&#8217;re happy with. So we&#8217;re trying to make that simpler, and I think we&#8217;re actually doing very cool work on that at Bluehost and Newfold in general. But some of that should also happen in Core.</p>



<p>[00:32:29] Nathan Wrigley: Yeah, it&#8217;s interesting. If you are Squarespace or Wix or whoever it may be, I guess the person who&#8217;s in charge of the way that the platform looks, just makes the decision and it&#8217;s done and everybody then toes the line and does that thing. Okay, we&#8217;re going to make it look different. We&#8217;re going to modify it. 2023, we&#8217;re going to give our entire enterprise a new look and feel. Let&#8217;s get on with it.</p>



<p>Of course, in WordPress, given the nature of the way that the software is developed, that&#8217;s really hard. And getting people to have a consensus on this, like you said, you&#8217;d had several chats with a few people who may be able to push the needle a little bit there, and there&#8217;s not always complete agreement.</p>



<p>It will be difficult, but my personal feeling is that it needs to be quite high on the list of things happening. But given that Gutenberg, we&#8217;re about to enter phase three of Gutenberg. Given that Gutenberg is consuming so much time and resources of developers, I do wonder whether this interface will get much of a makeover in the next, I don&#8217;t know, next year or so.</p>



<p>[00:33:32] Joost de Valk: I wondered that too. I don&#8217;t have an answer because I don&#8217;t know, but it is a conversation that I&#8217;m going to have, be having with people. And I do actually think that it might, it might field counterintuitive, but I actually think that building that design system first might actually speed up the other work.</p>



<p>[00:33:51] Nathan Wrigley: Yeah, well it certainly gives you a benchmark of what can be achieved. Yeah, it&#8217;d be interesting in your new role, whether or not you can corral some people into pushing that forward.</p>



<p>Yoast, we&#8217;re reaching the 40 minute mark. I think that&#8217;s about where I wanted to get to. If there&#8217;s anything that you think I missed, please let me know.</p>



<p>[00:34:10] Joost de Valk: No, there&#8217;s always more to talk about, it&#8217;s WordPress.</p>



<p>[00:34:13] Nathan Wrigley: If that&#8217;s the case and we&#8217;ve covered everything, I&#8217;ll just ask you to let us know where people can find you, given that you&#8217;re in a transitionary period. Where&#8217;s the best place for people to discover you from now on?</p>



<p>[00:34:25] Joost de Valk: That&#8217;s joost.blog, j o o s t.blog. So my first name, not the company name. And Twitter, j d e v a l k, J de Volk is probably the best place. And if people have questions or want to just chat, I&#8217;m on the WordPress Slack as well. So feel free to DM me there.</p>



<p>[00:34:44] Nathan Wrigley: Thank you very much, Joost for chatting to us on the podcast today. I really appreciate it.</p>



<p>[00:34:48] Joost de Valk: Again, thank you for having me, it was a pleasure.</p>
</div>



<p>On the podcast today we have <a href="https://profiles.wordpress.org/joostdevalk/">Joost De Valk</a>.</p>



<p>If you’ve been in the WordPress space for any length of time, it’s likely that you’ve come across the <a href="https://wordpress.org/plugins/wordpress-seo/">Yoast SEO plugin</a>. This was the brainchild of the guest today, Joost, same pronunciation, different spelling.</p>



<p>We talk about how Joost found WordPress and quickly started working on his SEO plugin. How it rapidly grew and became his career.</p>



<p>We discuss the WordPress landscape during this time and whether it’s more difficult now to have the type of success that his plugin received, given that there are more players vying for our attention.</p>



<p>The conversation then moves into why the plugin was recently sold to Newfold Digital. What were the guardrails that were put in place to ensure that the plugin continued and the employees felt safe?</p>



<p>We then get into a conversation about Joost’s new role. He’s been tasked with reaching out to WordPress community members in order to see what projects or initiatives need more thought and support.</p>



<p>This leads us into the topic of the current WordPress UI, and how Joost is hoping for a refresh at some point soon. For years his plugin team wanted to create their own UI to take advantage of new technologies, but Joost always pushed back, preferring instead to adopt the style of the WordPress UI. Now that’s changed, and the open sourcing of the UI kit they’ve made is intended as a starting point for a discussion about the need for a more consistent admin experience for all WordPress users.</p>



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



<p><a href="https://yoast.com/wordpress/plugins/seo/">Yoast SEO plugin</a></p>



<p><a href="https://elementor.com/">Elementor</a></p>



<p><a href="https://newfold.com/">Newfold Digital</a></p>



<p><a href="https://www.bluehost.com/">Bluehost</a></p>



<p><a href="https://www.hostgator.com/">HostGator</a></p>



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



<p><a href="https://yithemes.com/">Yith</a></p>



<p><a href="https://tailwindcss.com/">Tailwind CSS</a></p>



<p><a href="https://joost.blog/wordpress-admin-ui-needs-to-be-better/">Joost&#8217;s post about the WordPress Admin UI</a></p>



<p><a href="https://twitter.com/jdevalk">Joost&#8217;s Twitter</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, 29 Mar 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: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:63:"WPTavern: Pattern Manager Plugin Now Available on 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:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=143093";s:7:"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/pattern-manager-plugin-now-available-on-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2563:"<p>WP Engine&#8217;s <a href="https://wordpress.org/plugins/pattern-manager/">Pattern Manager</a> is now available in the WordPress Plugins Directory. The plugin gives WordPress professionals a dedicated interface for browsing, designing, and organizing patterns with categories, keywords, descriptions, and more. It is still in beta and not recommended for use in production. Although it can be used on a lived website, the plugin&#8217;s intended use is for managing patterns on a locally hosted development site.</p>



<img />



<p>The Pattern Manager makes it possible to use core features for which there isn&#8217;t yet an interface:</p>



<ul>
<li>When a user makes a new page or post, auto-show a modal with your patterns, available to be used.</li>



<li>Make your pattern available in the block inserter, or choose to hide it from the inserter.</li>



<li>Allow users to transform any block into your pattern.</li>
</ul>



<p>WP Engine made several improvements to the plugin based on beta feedback since the time we <a href="https://wptavern.com/wp-engine-pattern-manager-plugin-now-in-beta">reviewed the plugin</a> earlier this month. The matter of where the patterns are stored was one issue the testers were concerned about. Pattern Manager pushes the patterns to PHP files every time the user saves them, which also makes them available for collaboration via git.</p>



<p>&#8220;One of the most requested features was child theme support, so we added that,&#8221; WP Engine Principal Engineer Mike McAlister said. &#8220;Now, if you have a child theme active, Pattern Manager will save your new patterns to the child theme, while all of the patterns in your parent theme are still available.&#8221;</p>



<p>Another common request McAlister&#8217;s team received was the ability to register custom pattern categories. This feature is currently in development and will be available in the plugin in the near future.</p>



<p>&#8220;Other than that, we made a lot of nice little improvements like adding a setting for defining the pattern preview width, deprioritizing the Pattern Manager admin menu item (which was previously at the top of the admin menu), and some light UI touch-ups,&#8221; McAlister said. </p>



<p>&#8220;We had over 300 people in the beta and the feedback was highly positive, which is surprising for a niche developer tool like this. To me, it speaks to the interest in all of this new WordPress technology and how developers are looking for tools like Pattern Manager to help them start working with it.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 28 Mar 2023 19:52:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:72:"WPTavern: WordPress 6.2 Delayed to March 29 Due to Bug With Date Formats";s:7:"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=143080";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:83:"https://wptavern.com/wordpress-6-2-delayed-to-march-29-due-to-bug-with-date-formats";s: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:2304:"<p>WordPress 6.2 was scheduled for release today, but contributors discovered <a href="https://core.trac.wordpress.org/ticket/57998">a bug with date formats</a> during the 24-hour freeze that they believe could have <a href="https://core.trac.wordpress.org/ticket/57998#comment:15">a significant impact</a> on functionality like bookings, date permalinks, and e-commerce stores.</p>



<p>The decision was made this morning to delay with a consensus to apply a revert and release a silent 6.2 RC5 with the fix. WordPress 6.2 Core Tech Co-Lead Tonya Mork <a href="https://wordpress.slack.com/archives/C02RQBWTW/p1680004419127649">proposed reverting</a> as the impact seemed too widespread to risk releasing today with a fix delayed to a minor release. </p>



<p>&#8220;I don&#8217;t think this can wait until 6.2.1 given that this isn&#8217;t just some text that won&#8217;t bold, but something that will have quite a big impact (including stress/financial) on site owners and staff managing bookings and such,&#8221; 6.2 Core Triage Lead Colin Stewart said.</p>



<p>WordPress Core Committer Jonathan Desrosiers also weighed in on the issue in favor of a revert and silent RC5.</p>



<p>&#8220;I also think that [it&#8217;s] impossible to anticipate the full impact of this change,&#8221; Desrosiers said. &#8220;This definitely illustrates the importance of accompanying even the smallest changes with appropriate tests. We owe this due diligence to our users.</p>



<p>&#8220;If we release the issue with 6.2 we could have a much greater problem on our hands. It’s not something that would not be easy to recognize or understand for the large majority of users, and it’s nearly impossible for Core to &#8216;auto-fix&#8217; any occurrences of the bug  in a future minor release. We also should really avoid having to include fixes like that anyway as they’re just a huge maintenance burden/technical debt.&#8221;</p>



<p>Contributors in the discussion this morning agreed that knowingly shipping broken code just to keep the schedule would be a wrong move and that shipping a fix today could introduce additional problems. An announcement will be posted to the Make/Core, followed by the 6.2 RC5 release, which will restart the 24-hour clock ahead of the official 6.2 release tomorrow.</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, 28 Mar 2023 14:26:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:84:"Do The Woo Community: Insights, Tips and Legalities on Accessibility with Bet Hannon";s:7:"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=74647";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:66:"https://dothewoo.io/insights-tips-and-legalities-on-accessibility/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:429:"<p>Bet Hannon, from AccessiCart joins us for a conversation around web design, WooCommerce and the legalities of accessibility.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/insights-tips-and-legalities-on-accessibility/">Insights, Tips and Legalities on Accessibility with Bet Hannon</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 28 Mar 2023 10:06: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: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:56:"WPTavern: Real-Time Collaboration Is Coming to 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=143050";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:67:"https://wptavern.com/real-time-collaboration-is-coming-to-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:6910:"<p>Gutenberg Phase 3 is officially in the planning stage, as the Site Editor is set to exit the beta in 6.2 and the major tasks of Phase 2 are nearing completion.</p>



<p>Gutenberg lead architect Matias Ventura <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">published</a> a preliminary outline of what is planned to be included in the next &#8220;Collaboration&#8221; phase of the project. Real-time collaboration is at the top of the list, the likes of which users have previously experienced in apps like Google Docs.</p>



<p>&#8220;Imagine being able to work together in real-time across all block editors, crafting content and designs seamlessly without being locked out of editing,&#8221; Ventura said. &#8220;The goal is to provide all the necessary infrastructure and UI to handle multiple users working together on the same content simultaneously, making it easier to create, edit, and customize web pages and posts as a team.&#8221;</p>



<p>In a recent episode of the <a href="https://wordpress.org/news/2023/03/episode-52-phase-three-with-hector-prieto/">WP Briefing podcast</a>, WordPress core contributor Héctor Prieto said he predicts this feature will take the most work.</p>



<p>&#8220;I would say, in general, the real-time collaboration sounds the most technically challenging because of what it represents and all the changes needed to how we interact with WordPress from async to sync, basically,&#8221; Prieto said. &#8220;That would be the hardest part. I think there are also already a few prototypes working, but we need to see how that scales, for example.&#8221;</p>



<p>Prieto was referencing Gutenberg engineer Riad Benguella&#8217;s <a href="https://wptavern.com/asblocks-project-uses-gutenberg-to-create-a-collaborative-writing-environment">AsBlocks project</a>, which he <a href="https://riad.blog/2020/06/11/write-as-blocks-in-an-encrypted-collaborative-environment/">introduced</a> on his blog in 2020 and is <a href="https://github.com/youknowriad/asblocks">available on GitHub</a>. Another prototype, &#8220;Block Collab: New package, a framework for collaborative editing,&#8221; currently exists as <a href="https://github.com/WordPress/gutenberg/pull/23129/commits">a draft PR</a> created by Gutenberg contributor Enrique Piqueras.</p>



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

</div>AsBlocks demo video



<p>Asynchronous collaboration will also get some attention in this phase, which includes features like sharing drafts for content and design changes, inline block commenting, assignment review, improved version control, and task management. These are features that are currently available to WordPress users through a variety of different plugins.</p>



<p>&#8220;The goal is to enable users and larger teams to collaborate on projects and its different parts at their own pace and based on their workflows,&#8221; Ventura said.</p>



<p>Ventura also identified Publishing Flows and improvements to the Post Revisions interface as parts of the Collaboration phase. This would include features like an interface for editorial requirements, customized goals, and task completion prerequisites before publishing. Post Revisions would become more visual, inclusive of individual blocks, and may even be updated to to support more complex scheduling requirements across multiple parts of the site.</p>



<p>Collaboration may less critical to WordPress&#8217; success than world-class publishing capabilities but it will be refreshing to look past the editors to begin improving the admin experience. There are a few pieces of the puzzle that will will require contributors to jump in on getting WordPress&#8217; admin to the place where it can handle more modern collaboration workflows. Ventura said part of this project is to begin the process for an <a href="https://make.wordpress.org/design/2022/06/13/thinking-through-the-wordpress-admin-experience/">admin design update and navigation work</a>, improving admin notices and the UI library of design components, as well as the ancient admin list views. </p>



<p>Ventura also loosely outlined a Library focus area that would introduce a place for managing blocks, patterns, styles, and fonts. </p>



<p>&#8220;As part of this work, also look at what improvements can be done to enhance the media library design, interactions, and extensibility,&#8221; Ventura said. He confirmed to commenters that this part of the project was left &#8220;intentionally vague as it needs a bit more thinking.&#8221;</p>



<p>The last item in the Collaboration outline is a global search and command component that would be extensible and allow admins to navigate directly to content or different admin areas as well as run comments like &#8220;create new post&#8221; or &#8220;toggle top toolbar.&#8221; </p>



<p>&#8220;As AI tools are taking the world by storm, this could also play an important role in letting plugin authors integrate novel solutions that are prompt based in nature,&#8221; Ventura said.</p>



<p>Although Ventura assured readers that projects related to prior phases will continue, such as more blocks, improved tables, grid layout system, and the block API roadmap, there are those who would like to see more time spent on editing and customization before moving on.</p>



<p>&#8220;I love the initiative, but I wish they’d slow down and focus on the overall WordPress experience and mobile design tools, which affect virtually every user,&#8221; WP Engine developer Mike McAlister <a href="https://twitter.com/mikemcalister/status/1583290176880922624">said</a> in October 2022. &#8220;Collaboration tools won’t make or break WordPress, but the user experience will.&#8221;</p>



<p>In March, McAlister commented again on the pace of the Gutenberg project&#8217;s phases. &#8220;I would add a new phase of User Experience between 2 and 3,&#8221; he <a href="https://twitter.com/mikemcalister/status/1631023076212191233">said</a>. &#8220;We need a whole phase dedicated to refining the experience of all these great new tools.</p>



<p>&#8220;I am very optimistic about all of the features, but even as a veteran WordPress builder, the experience is still quite maddening at times. I don’t know if we’re spending enough time understanding the problems before implementing solutions and moving on to the next thing.&#8221;</p>



<p>Ventura said the timing for breaking ground on the Collaboration phase would not be the 6.3 release coming in August 2023. Contributors are still working towards refining the customization experience as WordPress prepares to bring the Site Editor out of beta in the 6.2 release. He encouraged people to share feedback in the comments on the <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">post</a> if there are any items they were hoping to see as part of the Collaboration phase.</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, 28 Mar 2023 01:21: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: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:114:"WordPress.org blog: WP Briefing: Episode 52: Workflows and Phase Three Visioning with Special Guest Héctor Prieto";s:7:"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=14697";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"https://wordpress.org/news/2023/03/episode-52-phase-three-with-hector-prieto/";s: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:25420:"<p>On Episode fifty-two of the WordPress Briefing podcast, join WordPress Executive Director Josepha Haden Chomphosy and special guest Héctor Prieto as they discuss phase three and why it&#8217;s more than just collaborative editing!</p>



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



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



<p>Editor:&nbsp;<a href="https://profiles.wordpress.org/dustinhartzler/">Dustin Hartzler</a><br />Logo:&nbsp;<a href="https://profiles.wordpress.org/javiarce/">Javier Arce</a><br />Production:&nbsp;<a href="https://profiles.wordpress.org/santanainniss/">Santana Inniss</a><br />Song: Fearless First by Kevin MacLeod </p>



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



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



<ul>
<li><a href="https://riad.blog/2020/06/11/write-as-blocks-in-an-encrypted-collaborative-environment/">Write as Blocks in an Encrypted Collaborative Environment by Riad Benguella</a> </li>



<li><a href="https://github.com/youknowriad/asblocks">Riad Benguella’s collaborative editing GitHub repository</a></li>



<li><a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella&#8217;s WordPress.org Profile</a></li>



<li><a href="https://github.com/WordPress/gutenberg/pull/23129">Block Collab: New package, a framework for collaborative editing GitHub PR</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">Phase 3: Collaboration</a></li>



<li><a href="https://github.com/WordPress/gutenberg/issues/48457">Matías Ventura Quick Search GH Issue</a></li>



<li><a href="https://profiles.wordpress.org/matveb/">Matías Ventura WordPress.org Profile</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-day-process/">WordPress 6.2 Release Day Process</a></li>



<li><a href="https://wordpress.org/news/2023/03/introducing-the-wordpress-developer-blog/">Introducing the WordPress Developer Blog</a></li>



<li><a href="https://europe.wordcamp.org/2022/contributor-day/">WordCamp Europe Contributor Day Registration</a></li>



<li><a href="https://wp20.wordpress.net/wapuu-coloring-giveaway-style-your-own-party-wapuu/">WP20 Wapuu Coloring Giveaway</a></li>
</ul>



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



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



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



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



<p>[Josepha Haden Chomphosy 00:00:40]<br /><br />I have with me today Hécto Prieto. You all may know him from the WordPress Slack. He recently was, I believe, a release coordinator, maybe for the last release. Was that for 6.1?</p>



<p>[Héctor Prieto 00:00:51]<br /><br />Yes. It was for 6.1 and also 6.0, in fact.</p>



<p>[Josepha Haden Chomphosy 00:00:54]<br /><br />All right. Well, welcome to the WordPress Briefing today. How are you doing?</p>



<p>[Héctor Prieto 00:00:59]&nbsp;</p>



<p>Well, I&#8217;m excited to be here. I&#8217;m a longtime listener of the podcast since the first episode. So I&#8217;m super excited to be here with you today.</p>



<p>[Josepha Haden Chomphosy 00:01:06]<br /><br />Yes. Longtime listener. First-time caller. All right, well, we&#8217;re gonna have a topic that just dumps you right in the soup, as they say in the United States. So we are actually here to talk about phase three of Gutenberg. It&#8217;s been a long time coming, and there are a lot of questions that folks have about what&#8217;s going into it and what&#8217;s not going into it.</p>



<p>And as someone who works really closely with our Gutenberg technical architect, Matías Ventura, I figured you would be exactly the right person to come and talk about your favorite things. From your perspective, what is going to be the biggest enhancement that we start to approach in phase three?</p>



<p>Like which thing, which API is gonna take the most work, do you think?</p>



<p>[Héctor Prieto 00:01:53]<br /><br />Well, the most work, that&#8217;s a very hard question to answer because we are still we are going to start an exploration phase to determine how far we want to go with each of these APIs. So, in general, all these APIs and these products are standalone projects. And some of them are shorter, and some of them are longer.</p>



<p>I would say, in general, the real-time collaboration sounds the most technically challenging because of what it represents and all the changes needed to how we interact with WordPress from async to sync, basically. That would be the hardest part. I think there are also already a few prototypes working, but we need to see how that scales, for example.</p>



<p>[Josepha Haden Chomphosy 00:02:32]</p>



<p>Yeah. So speaking of a few prototypes, I know that there are two or three different prototypes specifically for collaborative editing, but do we have people or groups, working groups in the community that have built any other prototypes? Or is it just kind of first passes at collaborative editing that we&#8217;ve seen?</p>



<p>[Héctor Prieto 00:02:52]<br /><br />Well, apart from Riad Benguella’s exploration, there&#8217;s a public repository with that exploration, there are a few plugins trying the same, trying real-time collaboration.</p>



<p>[Josepha Haden Chomphosy 00:03:03]<br /><br />Yeah, I can think of co-blocks and as blocks, and then I feel like there was a third one.</p>



<p>[Héctor Prieto 00:03:09]&nbsp;</p>



<p>Yeah.</p>



<p>[Josepha Haden Chomphosy 00:03:09]<br /><br />We&#8217;ll find the links to all these</p>



<p>[Héctor Prieto 00:03:12]</p>



<p>Yeah. Let&#8217;s add them to the show notes.</p>



<p>[Josepha Haden Chomphosy 00:03:14]<br /><br />Excellent. So that&#8217;s going to be the biggest one. Is there, of the list of APIs, and this is based on the post that Matías sent out last week. If you all haven&#8217;t seen that, we&#8217;ll put that in the show notes as well. But from the APIs that Matías sort of helped us to identify last week, is there any one that you are particularly excited about for fixing things in WordPress or just generally like an interesting topic of development for you?</p>



<p>[Héctor Prieto 00:03:42]<br /><br />Well, I would say all of them and how they all play together. But, if I need to pick one of them…</p>



<p>[Josepha Haden Chomphosy 00:03:48]<br /><br />Everything&#8217;s the best!&nbsp;</p>



<p>[Héctor Prieto 00:03:50]<br /><br />I&#8217;ll cheat anyway, and I will going to pick two out of them because they solve issues at different levels. I&#8217;m very excited about visual revisions. I think it helps a lot of users, and it affects even non-technical users.</p>



<p>So it&#8217;s one of the projects that lower how hard or complex WordPress can be to use sometimes. It&#8217;s going to be a huge improvement. It&#8217;s going to, I mean, bringing blocks to the revision system. I mean, it&#8217;s just a dream come true for me. I&#8217;m also going to highlight the search everywhere or quick search feature Matías already opened an issue in the GitHub repository right now.&nbsp;</p>



<p>[Josepha Haden Chomphosy 00:04:28]<br /><br />Mm-hmm.</p>



<p>[Héctor Prieto 00:04:28]<br /><br />So the idea for this product is to have a power user shortcut that opens searching, an Alfred-like or Spotlight-like interface for those familiar with MacOS operating systems.</p>



<p>When you can type anything, any place you want to go, or you want to search for any specific text in a document. And it&#8217;s supposed to be your power user command tool. So that you can do most things there.</p>



<p>[Josepha Haden Chomphosy 00:04:53]<br /><br />Oh, and I mean not only power user command tool, but also there are some applications there for folks who have mobility issues, people who are using primarily keyboard as opposed to keyboard and mouse, all that kind of stuff, right?</p>



<p>[Héctor Prieto 00:05:07]<br /><br />Exactly. And just thinking long term with the rise of AI, it could be possible even to add some natural language processing to this interface so that users could just write in, in plain text, in natural language, what they want to do, and WordPress would provide the action for them.</p>



<p>[Josepha Haden Chomphosy 00:05:23]<br /><br />Very nice. My two favorites, since you gave two favorites and I can&#8217;t just give one at that point, my two favorite projects, which are also probably really, really hard projects, are those explorations around fixing notifications. That is a really big project. And one that I think that, in general, the WordPress project is going to be really excited to have some input on.&nbsp;</p>



<p>And so that&#8217;s one that I really will have an eye on. And the other one that I&#8217;m going to definitely have my eye on is the media gallery redesign. I realize that this shows, between you and I, that shows our two specific focuses. Because, of course, you work directly with guiding all of our developers. And I am very much like our user advocate. And WordPress “everyman.”</p>



<p>I don&#8217;t know if that&#8217;s a term that makes sense outside the US. But I do a lot of advocacy for folks who are using WordPress from the user side as opposed to from the developer side because, of course, we have a lot of excellent developers. So y&#8217;all don&#8217;t need my help with your advocacy.</p>



<p>But yeah, that really shows that you and I have different focuses, which I think is good too.</p>



<p>[Héctor Prieto 00:06:32]<br /><br />Yes. Also, it’s worth noting that at the end of the day, any improvement we make for developers is so that developers can build better things for users. So, at the end of the day, everything is in the best interest of the users.</p>



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



<p>That&#8217;s right. That&#8217;s definitely a good point. Yeah. So, a final question about this particular thing because we&#8217;re trying to keep it a little brief and also because we&#8217;ll have a few other podcasts that are specifically about phase three as our explorations get going. Final question here: If you felt like there was one API or one project in particular that could benefit from a lot of community involvement which would you guess that was?</p>



<p>[Héctor Prieto 00:07:20]<br /><br />I don&#8217;t think I can single out any of them. I think getting user feedback is going to be a vital part of this phase, as always. So I would encourage our listeners to just participate in discussions and provide feedback as we start releasing the first prototypes in the Gutenberg plugin. I don&#8217;t think I can pick one of them for you, completely honest.</p>



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



<p>Yeah. My guess for that is going to be the rework of the dashboard, the admin, WP admin. I think that a lot of people are gonna have a lot to say about what they use it for, what they would like to be able to use it for, how to make it look more modern, how to make it feel more modern. I think that that probably is going to benefit from a lot of early testing and possibly some specific user testing around the concepts of design in there.</p>



<p>And so that&#8217;s one that that I think probably is going to take a lot of feedback from the community. And community, in this case, I think, is not only our developers and designers and copy folks who are working to build the CMS, but probably also all of our folks who are extending WordPress, everybody who is working in agencies, things like that.</p>



<p>[Héctor Prieto 00:08:35]<br /><br />Hmm, well, if I need to pick one, I would say the publishing flows could use also lots of feedback and testing because we are going to implement editorial requirements and customized user flows. And, of course, there are many, many different workflows out there that we might not be able to think of ourselves.</p>



<p>So just imagine the sheer amount of different use cases. There&#8217;s going to be, or there currently is with customizations of third-party plugins. So, yeah. I would like to listen to how people would like the publishing flows to be. What are the specific use cases?&nbsp;</p>



<p>[Josepha Haden Chomphosy 00:09:09]<br /><br />So really, just everything, we need a lot of user feedback on everything.</p>



<p>[Héctor Prieto 00:09:13]<br /><br />Yes. That&#8217;s the summary.</p>



<p>[Josepha Haden Chomphosy 00:09:15]</p>



<p>I don&#8217;t think that&#8217;s a bad summary. I know that we talk a bit about how WordPress is made better by the activity of our co-creators, the people who are using the software and testing the software, and telling us how it could be better. Those are the groups of people that make sure that we are the best version or headed in the best direction on any of our things with the software.</p>



<p>And so I guess it&#8217;s probably not super unusual for everyone to hear like we need your feedback on everything because that&#8217;s probably what we do half the time.</p>



<p>[Héctor Prieto 00:09:44]<br /><br />Yeah, absolutely.</p>



<p>[Josepha Haden Chomphosy 00:09:47]<br /><br />So the publishing workflows, that reminds me that there has been a little bit of a conversation lately around the naming of this phase, basically.</p>



<p>And I know that the phases don&#8217;t necessarily need names. Like that&#8217;s why they&#8217;re numbered, and that&#8217;s a great idea. Like numbers are wonderful ways to reference things, but it also is just easier to reference it in kind of general conversation.</p>



<p>So the first phase was easier editing, and it really focused on the editing experience itself. The second one was customization, and now the third phase has been called collaboration for quite a bit of time.</p>



<p>But as we got closer and closer to this phase and we had more and more conversations that were coming out of phases one and two, it became really clear that really what we&#8217;re looking at here is more around workflows. And I love that that is an option for how to refer to this. Probably that&#8217;s how I will refer to it for most of the time that I talk about it as we are looking at phase three. </p>



<p>Because I remember that when we were first building the prototypes of Gutenberg, one of the big flags that I had was that breaking changes are not just about what we can see or any sort of visual regressions or what causes the white screen of death. Also, some of the things that are breaking changes should be considered in those workflows when we change where things are or how you accomplish a task.</p>



<p>And our users weren&#8217;t ready for it. That is something that is breaking for them, right?</p>



<p>[Héctor Prieto 00:11:25]&nbsp;<br /><br />Yes. As you mentioned, this phase was referenced as collaboration, real-time collaboration, for a long time, but if we think of how this collaboration looks, it&#8217;s much more than just editing at the same time. A very big part of collaboration is also asynchronous collaboration by adding in-line comments and improving these notifications when you have a comment in your draft. I think the power of this phase is how everything comes together. These individual pieces come together.</p>



<p>[Josepha Haden Chomphosy 0:11:51]<br /><br />Yes, and I don&#8217;t know where that first flag that sparked the discussion around, like, okay, but collaborative editing is not quite big enough and also means a bunch of different things for a bunch of different people. It depends on the size of your organization or the type of content you&#8217;re writing.</p>



<p>Like, I don&#8217;t know where that conversation started. My guess is, you know, some WordCamp somewhere, and an attendee was like, did you, did anybody ever think about these problems? And then they kind of worked their way around the Make Core site or otherwise made their way around to Matias&#8217;s ears.</p>



<p>But yeah, I think that was a really smart choice. And you&#8217;re exactly right, collaborative editing; that can refer to the synchronous kind or the asynchronous kind, and both of those types of collaboration are equally valuable and probably equally used.</p>



<p>[Héctor Prieto 00:12:40]<br /><br />Yes. And one important point to note here is that this editorial flows, and this collaboration is crucial to implement multilingualism going into phase four. We need to think that as soon as we have posts and pages in different languages, there are going to be requirements in terms of how to translate these pieces of content.</p>



<p>So this will need collaboration, all forms of collaboration.</p>



<p>[Josepha Haden Chomphosy 00:13:02]<br /><br />Yeah, absolutely. This maybe was before your time with the project, but I was team multilingual-first for a long time. Or at least thinking that we could do the multilingual part of this work alongside the collaborative editing part of the work. I&#8217;ve spent a lot of time trying to understand what we think is going in phase three versus what probably we need to be able to do as far as having native multilingual support in the project.</p>



<p>And I have softened my very hard position on that. You know, we&#8217;re big fans of strong positions loosely held, strong opinions loosely held. And this was one of those moments where I had that really strong opinion that we could just do them concurrently. We can do them at the same time.</p>



<p>And I think it was a conversation that you and I were having when you were pointing out the complexities of translating WordPress at all, let alone being able to translate all your content as well. And it makes a lot of sense, and you&#8217;re right. I think that there are a lot of interactions, a lot of workflows that we&#8217;re gonna have to kind of refresh or redesign or rebuild before it really makes sense for us to help make that a nice streamlined option for multilingual offerings.</p>



<p>[Héctor Prieto 00:14:17]<br /><br />Yes, absolutely. As a Spanish-speaking person, I&#8217;m super excited about having multilingual in Core, but I also understand that we need some tooling ready before implementing multilingual in Core.&nbsp;</p>



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



<p>There are no, there really are no easy problems left in WordPress, right? Like, we all agree on this now?</p>



<p>[Héctor Prieto 00:14:36]<br /><br />That&#8217;s correct. And we&#8217;re creating something incrementally. If we look at the phases, they are ordered sequentially. But that doesn&#8217;t mean that when we start phase three, we are, finishing phase two completely in the same way. We have not finished phase one.</p>



<p>That will be like saying, when is WordPress finished, when is the development finished? So it&#8217;s an incremental project, and it&#8217;s always going to be to need refining. So it&#8217;s of course, multilingual needs to come after collaboration because we need those tools.</p>



<p>But that doesn&#8217;t mean we need to finish the collaboration phase or have it very advanced phase three before we can start phase four. That will be determined in the next month as we start explorations.</p>



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



<p>So if you all, which I know you are, are interested in better workflows, more streamlined ways of working inside WordPress, and or interested in how we are gonna get multilingual settled in the future, this is a great time to get involved in this project and in the community. Like I said, we&#8217;ve got that post up that Matías shipped last week, which, again, if you have not read it, go read it because it&#8217;s got excellent, excellent information in there for you.&nbsp;</p>



<p>Héctor, before we head out, is there anything that you wanna make sure that you let the listeners know, either about phase three or just about WordPress in general?</p>



<p>[Héctor Prieto 00:15:57]<br /><br />Well, tomorrow is WordPress 6.2 release day. So happy 6.2, everybody!</p>



<p>[Josepha Haden Chomphosy 00:16:04]<br /><br />Happy 6.2. Oh, yeah. Yeah. Which means today is the dry run; probably in three hours, we&#8217;re doing the dry run.</p>



<p>[Héctor Prieto 00:16:14]<br /><br />Depends on when we&#8217;re listening to this, but yes.</p>



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



<p>Oh, that&#8217;s a good point. Right? Not everybody listens to this the second it becomes available. Time zones. That&#8217;s right. Oh, man. Look at us being a global project and just pretending like everybody listens to this particular thing the moment that it&#8217;s available.</p>



<p>I apologize to everybody who&#8217;s listening to it after the release or in the middle of the release party or whatever you&#8217;re doing. Regardless, tomorrow, if you&#8217;re listening to it today, is the WordPress 6.2 release, and it&#8217;s gonna be great.</p>



<p>Well, Héctor, thank you so much for joining me today. I really enjoyed having you on, and thanks for letting me interview you.</p>



<p>[Héctor Prieto 00:16:59]<br /><br />Thank you for having me. It was my pleasure to be here.</p>



<p>[Josepha Haden Chomphosy 00:17:10]</p>



<p>So that brings us now to our small list of big things, and as is frequently the case, it&#8217;s actually kind of a big list of big things. So we&#8217;re gonna hop right in here. As Héctor and I mentioned in the episode, the release WordPress 6.2 is coming out tomorrow, depending on when you&#8217;re listening to this. If you listen to it on the 27th, it comes out on the 28th of March.&nbsp;</p>



<p>If you have a chance to drop by the release party. I would encourage you to; they&#8217;re pretty interesting just to get an idea of everything that it takes to build WordPress. It is, of course, the last few hours before a release, and so you don&#8217;t get a full scope.</p>



<p>But it&#8217;s always nice to see the way that everybody in the community works together, especially there in that last moment when we&#8217;re trying to package something and test it in a bunch of environments all across the world.&nbsp;</p>



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



<p>I love attending those. And so I encourage it. The next episode of the WordPress Briefing is going to have the release rundown.</p>



<p>I&#8217;ll go through the key features and highlights that finally made it into 6.2. The reason we don&#8217;t do those beforehand is just in case we have to remove anything at the last minute from a release. It doesn&#8217;t happen too often, but it does happen sometimes. And so, next episode of WP Briefing, that&#8217;s what we&#8217;ll be talking about.</p>



<p>The next thing on my list is a new developer blog. So there is a brand new developer blog. It was launched last Wednesday. It&#8217;s a great resource for WordPress developers to stay up to date and hear the latest in the WordPress development world. And also, we had been hearing some feedback from our developers in recent years that if you are like exploring how to extend WordPress, if you&#8217;re in that group of extenders, people who are building themes or building plugins, you&#8217;ve kind of feel like you&#8217;ve lost a place where you can have those exploratory conversations.&nbsp;</p>



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



<p>This is gonna be one of those places. We&#8217;ll put a link in the show notes. So far, the content that&#8217;s planned, I think, is really interesting.</p>



<p>Next thing on our small list, big list, of big things is WordCamp Europe&#8217;s Contributor Day.</p>



<p>So registration for Contributor Day is now open, and it does require a separate registration than regular attendance at WordCamp Europe. So if you are registered for WordCamp Europe, you already have your ticket for that, but you are not registered for Contributor Day, click the link in the show notes and come on down to spend a little time giving back to the WordPress Project.</p>



<p>And the last thing on our list today is that we have a WP20 Wapuu coloring giveaway. So put on your little party hats, and grab your crayons. The 20th anniversary Wapuu coloring giveaway is here. There is an opportunity to color in your own community-driven Wapuu and tweet it to us using #WapuuWP20 for your chance to win a sweet haul of WP20 swag items.</p>



<p>[Josepha Haden Chomphosy 00:20:00]</p>



<p>You can check out the full rules at the link in our show notes.</p>



<p>And that, my friends, is your small list of big things. Thanks for tuning in today for the WordPress Briefing. I&#8217;m your host, Josepha Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks.&nbsp;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 27 Mar 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:"Santana Inniss";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:115:"Gutenberg Times: Phase 3 collaboration, layout, and spacing controls, block visibility 3.0 – Weekend Edition #248";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=23700";s:7:"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://gutenbergtimes.com/phase-3-collaboration-layout-and-spacing-controls-block-visibility-3-0-weekend-edition-248/";s: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:19092:"<p>Howdy, </p>



<p>This week three major things happened: The movers packed up our household into boxes and a big truck, the <a href="https://wordpress.org/news/2023/03/introducing-the-wordpress-developer-blog/"><strong>WordPress Developer Blog</strong></a> came out of beta and is now considered officially launched, and Matias Ventura published a post about what Phase 3 of the Gutenberg project could look like, more about the latter further below. </p>



<p>Have a wonderful weekend! </p>



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






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



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




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



<img />



<p>Next week, WordPress 6.2 is coming to a WordPress instance near you. Are you prepared? You could use the <a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-candidate-4/"><strong>WordPress 6.2 Release Candidate 4</strong></a> for your testing and make sure. </p>



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



<p>If you want to follow along, <strong>Hector Prieto </strong>posted the <a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-day-process/"><strong>WordPress 6.2 Release Day Process</strong></a>, with the schedule for the Dry Run, 24-hour Code Freeze and the Release party on March 28, 2023, which is tentatively set for 2 pm EDT / 6 pm UTC. </p>



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



<p><strong><a href="https://twitter.com/dan_knauss">Dan Knauss</a></strong>, iThemes published <a href="https://ithemes.com/blog/what-to-expect-in-wordpress-6-2"><strong>What to Expect in WordPress 6.2</strong></a>, and highlights all the improvements of Blocks, Site Editor and new tools. He goes into details on the various new Header and Footer Patterns that will be available via WordPress 6.2. </p>



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



<p><strong>Carlo Daniele,</strong> wrote on the Kinsta blog: <a href="https://kinsta.com/blog/wordpress-6-2/"><strong>What’s New In WordPress 6.2: Browse Mode, Style Book, Improved Navigation Menus, New APIs, and Much More</strong></a>. In his post Daniele covers the update coming to 6.2 in four categories: </p>



<ul>
<li><a href="https://kinsta.com/blog/wordpress-6-2/#improved-editing-experience">Improved Editing Experience</a></li>



<li><a href="https://kinsta.com/blog/wordpress-6-2/#extended-block-capabilities">Extended Block Capabilities</a></li>



<li><a href="https://kinsta.com/blog/wordpress-6-2/#enhanced-design-tools">Enhanced Design Tools</a></li>



<li><a href="https://kinsta.com/blog/wordpress-6-2/#changes-for-developers">Changes for Developers</a></li>
</ul>



<div class="wp-block-group has-light-background-background-color has-background is-layout-flow wp-block-group-is-layout-flow"><div class="wp-block-group__inner-container">
<p><strong>🎙️ </strong> New episode:  <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-80-wordpress-6-2-preview-gutenberg-15-2-and-15-3/">Gutenberg Changelog #80 – WordPress 6.2 Preview, Gutenberg 15.2 and 15.3</a> with Birgit Pauli-Haack and special guest Rich Tabor  </p>
</div></div>



<p><strong>Justin Tadlock</strong> and <strong>Ryan Welcher</strong> co-led the <strong>Gutenberg 15.4</strong> plugin release. In the release post, <a href="https://make.wordpress.org/core/2023/03/22/whats-new-in-gutenberg-15-4-22-march/"><strong>What’s new in Gutenberg 15.4 (22 March)</strong></a>, Tadlock wrote: &#8220;The latest release of the plugin is lighter on user-facing features than normal and focuses heavily on bug fixes, testing, and other much-needed improvements.&#8221; The highlights included: </p>



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/22/whats-new-in-gutenberg-15-4-22-march/#color-and-layout-support-for-cover-block">Color and layout support for the Cover block</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/22/whats-new-in-gutenberg-15-4-22-march/#updated-template-descriptions">Updated template descriptions</a></li>
</ul>



<p>Personally, I like the new <code>textColumns</code> property that allows  me to split text-based blocks into self-adjusting columns. </p>



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



<p><strong>Matias Ventura</strong>, lead developer of the Gutenberg projects, posted <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/"><strong>Phase 3: Collaboration</strong></a> and explored briefly, what the next phase of the Gutenberg project would encompass. He identified seven areas: </p>



<ul>
<li><strong>Real-time collaboration</strong> &#8211; more than one person can edit a post at the same time.</li>



<li><strong>Asynchronous collaboration.</strong> Writers and editors share drafts and discuss via a comments assignments, topics etc. This part is all about workflow among a team of editors. </li>



<li><strong>Publishing flows.</strong> Publishing checklists, managing requirements and allowing for customization as every site has different needs. </li>



<li><strong>Post revisions interface.</strong> A way to coordinate updates and add new content in a scheduled manner.  There will be overlap with Theme switching and applying styles, for instance for Christmas, or other occasions. </li>



<li><strong>Admin design.</strong> Ventura wrote about this last year in <a href="https://make.wordpress.org/design/2022/06/13/thinking-through-the-wordpress-admin-experience/">Thinking Through the WordPress Admin Experience</a>. Notifications, list views updated UI to include new features. </li>



<li><strong>Library</strong> &#8211; A space where users manage Patterns, Blocks, Styles, and Fonts. </li>



<li>Develop a <strong>global search &amp; command component</strong></li>
</ul>



<p>I just briefly touched on the seven areas, and might not do it full justice. Ventura provided in his post many more details. <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">It&#8217;s worth a read</a>.  Give it time to digest, too. Then, see if there is something you are missing, that would fit into the third phase and share it in the comments on the post. </p>



<img />



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



<p><strong>Anne McCarthy</strong> organized again a Hallway Hangout and invited Automattic-sponsored design developers, <strong>Isabel Brison</strong> and <strong>Saxon Fletcher</strong> to <a href="https://make.wordpress.org/test/2023/03/14/hallway-hangout-lets-chat-about-all-things-layout/"> </a><strong><a href="https://make.wordpress.org/test/2023/03/14/hallway-hangout-lets-chat-about-all-things-layout/">Chat about All Things Layout</a>.</strong> The recording is available as well as summary of the demos and topics covered. It was a continuation of Brison&#8217;s WordCamp Asia talk <a href="https://gutenbergtimes.com/wordcamp-asia-2023-eight-gutenberg-related-talks/#layout-layout-layout">&#8220;Layout, Layout, Layout&#8221;</a>.</p>



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



<p><strong>Nick Diego </strong>just released version 3.0.0. Learn more in his post <a href="https://blockvisibilitywp.com/block-visibility-3-0-0-a-new-chapter-begins/"><strong>Block Visibility 3.0.0: A New Chapter Begins</strong></a>, in which he announces that he makes most Pro features available for free. With the plugin, you can control show or hide blocks depending on, for instance, a date, a user role, a location, or referral source. It extends the core block editor with additional settings. </p>



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



<p><strong>Wes Theron </strong>posted a new tutorial on WordPressTV <a href="https://wordpress.tv/2023/03/20/intro-to-temaplates-block-theme/"><strong>Intro to Templates </strong>(Block Theme)</a>. A template provides the structure or design for how a page is displayed. That usually includes a header template part, a content area and a footer template part. In this beginner session, we will look closer at the various templates available, the template layout, and how to assign a template to a post or page.</p>



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



<p><strong>Sarah Snow</strong> posted <a href="https://learn.wordpress.org/tutorial/what-kind-of-wordpress-theme-do-i-have-classic-block-or-something-else/"><strong>What kind of WordPress theme do I have: classic, block, or something else?</strong></a> Learn in 2 minutes to quickly identify what kind of theme you are using on your existing WordPress website.</p>



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



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



<p>In this week&#8217;s post on the WordPress Developer Blog, <a href="https://developer.wordpress.org/news/2023/03/everything-you-need-to-know-about-spacing-in-block-themes/"><strong>Everything you need to know about spacing in block themes</strong></a>, <strong>Justin Tadlock </strong> took a deep dive into all the ways, theme developers can control spacing for their block themes, and their users in the Site editor. In addition to description of the conceptual implementation, you&#8217;ll find real life  practical code examples paired with screenshots. </p>




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




<p><strong>Daisy Olsen</strong> uploaded the recording of her livestream <a href="https://www.youtube.com/watch?v=Zc7Y6pXOlPI"><strong>Speed Building a Block Theme</strong></a> to YouTube. In this session, she &#8220;created a completely functional Block Theme based on the templates and parts included in the Underscores Starter theme in just about one hour.&#8221; Olsen used the <a href="https://wordpress.org/plugins/create-block-theme/">Create Block Theme plugin</a> and the Site Editor for this project. <a href="https://www.twitch.tv/videos/1767688887">Part Two covering Styles and theme.json</a> is available on Twitch.tv.</p>



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



<p>Don&#8217;t miss Monday&#8217;s <strong><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/291332837/">Developer Hours: Migrate a plugin to blocks </a></strong>with <strong>Michael Burridge</strong> and <strong>Jonathan Bossenger,</strong> who will provide provide WordPress plugin developers with the opportunity to connect with, and learn from, one another. It&#8217;s a great AMA and you can get your burning questions answered! <strong><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/291332837/">Monday 27, 2023 at 4 am EDT / 8 am UTC / 3 pm Indonesia Time</a> </strong> &#8211; Yeah it&#8217;s a bit early for the US. This is scheduled for the Asia-Pacific developers 🙂 </p>



<img />



<p><strong>Ryan Welcher</strong> posted last week&#8217;s Twich stream session to YouTube: <a href="https://www.youtube.com/watch?v=32Ohee5fos0"><strong>Reviewing Gutenberg 15.3 features. Live stream: March 16, 2023</strong></a>. He went over the features of the Gutenberg 15.3 plugin. He discussed the new time to read block and showed how it works and also highlighted the improvements made to the duotone design tool. Welcher also elaborated on the fast release cycle of Gutenberg and how it can sometimes result in smaller updates. Another topic was the process of creating custom duotones and Welcher suggested that it would be great if the editor could save custom duotones for future use.</p>



<h2 class="wp-block-heading" id="4-word-camps">WordCamps</h2>



<p><strong>WordCamp Phoenix</strong> livestreams talks from two tracks (<a href="https://phoenix.wordcamp.org/2023/schedule/">schedule</a>). There are quite a few talks about blocks, the block, and site editor. </p>



<p><a href="https://phoenix.wordcamp.org/2023/livestream/">You can catch &#8217;em all on the re-runs</a>! </p>



<ul>
<li><a href="https://phoenix.wordcamp.org/2023/session/building-custom-blocks-no-js-required/">Building Custom Blocks. No JS Required!</a> with John Hawkins  works with ACF</li>



<li><a href="https://phoenix.wordcamp.org/2023/session/youre-invited-to-a-block-party/">You’re invited to a Block Party!</a> with Alicia St. Rose  </li>



<li><a href="https://phoenix.wordcamp.org/2023/session/shooting-hoops-with-wordpresss-new-site-editor-tips-and-tricks-for-elevating-your-site-building-game/">Shooting Hoops with WordPress’ New Site Editor: Tips and Tricks for Elevating Your Site-Building Game</a> with James Tryon </li>



<li><a href="https://phoenix.wordcamp.org/2023/session/the-block-editor-and-full-site-editing-crash-course-for-freelancers-and-agencies/">The Block Editor and Full Site Editing Crash Course for Freelancers and Agencies</a> with Keanan Koppenhaver</li>



<li><a href="https://phoenix.wordcamp.org/2023/session/using-blocks-and-block-based-forms-to-build-applications/">Using Blocks (and Block-Based Forms) to Build Applications</a> with Robert Richardson</li>



<li><a href="https://phoenix.wordcamp.org/2023/session/breaking-down-the-block-editors-layout-system/">Breaking Down The Block Editor’s Layout System</a> with Al Ani</li>
</ul>



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



<p>WordCamp Asia &#8211; I just finished collecting all the links for the block related talks. </p>




<div class="ngl-articles colored ngl-articles-50_50 ngl-articles-frontend">

	
	<div class="ngl-articles-wrap ngl-articles-webview">
	
						
			<div class="ngl-article-mobile">
				<table width="100%" border="0" cellpadding="0" cellspacing="0">
					<tr>
						<td valign="top">
							<div class="ngl-article-mob-wrap">
							<div class="ngl-article-featured"><a href="https://gutenbergtimes.com/wordcamp-asia-2023-eight-gutenberg-related-talks/" target="_self" rel=""><img src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2023/02/Screenshot-2023-02-03-at-12.25.29.png?w=652&ssl=1" /></a></div><div class="ngl-article-title"><a href="https://gutenbergtimes.com/wordcamp-asia-2023-eight-gutenberg-related-talks/" target="_self" rel=""><span>WordCamp Asia 2023: Eight Gutenberg related talks</span></a></div><div class="ngl-article-excerpt">It&#8217;s been over a month since WordCamp Asia ended, and I am still browsing through the thousands of photos from the official Flickr album and the public Google Photos were… <a href="https://gutenbergtimes.com/wordcamp-asia-2023-eight-gutenberg-related-talks/" class="ngl-article-read-more" target="_self">Read more.</a></div>							</div>
						</td>
					</tr>
				</table>
			</div>
			
			
			

		
		
		</div>

</div>





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



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




<p class="has-text-align-right has-small-font-size"><em>Questions? Suggestions? Ideas? Don&#8217;t hesitate to send <a href="mailto:pauli@gutenbergtimes.com">them via email</a> or send me a message on WordPress Slack or Twitter @bph</em>. </p>



<p class="has-text-align-right has-small-font-size">For questions to be answered on the <a href="http://gutenbergtimes.com/podcast">Gutenberg Changelog</a>, send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a></p>



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




<p>Featured Image: &#8220;<a href="https://www.flickr.com/photos/16228681@N00/2503685266" target="_blank" rel="noreferrer noopener">Moveable Type</a>&#8221; by&nbsp;<a href="https://www.flickr.com/photos/16228681@N00" target="_blank" rel="noreferrer noopener">Dave DeSandro</a>&nbsp;is licensed under&nbsp;<a href="https://creativecommons.org/licenses/by-nc/2.0/?ref=openverse" target="_blank" rel="noreferrer noopener">CC BY-NC 2.0</a>.</p>



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



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



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



<hr class="wp-block-separator has-css-opacity is-style-wide" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 25 Mar 2023 06:39:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Birgit Pauli-Haack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:118:"WPTavern: Block Visibility 3.0.0 Makes Pro Version Free, Adds Browser and Device Control, Visibility Presets, and More";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=143014";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:126:"https://wptavern.com/block-visibility-3-0-0-makes-pro-version-free-adds-browser-and-device-control-visibility-presets-and-more";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4239:"<p>WordPress contributor and developer Nick Diego has released <a href="https://blockvisibilitywp.com/block-visibility-3-0-0-a-new-chapter-begins/">version 3.0.0</a> of his Block Visibility plugin, which allows users to conditionally display blocks based on specific user roles, logged in/out, specific users, screen sizes, query strings, ACF fields, and more.</p>



<p>The biggest change in this update is that Diego has decided to merge the Pro version with the free plugin so users no longer have to purchase a commercial add-on to get extra features. Diego launched the pro version in 2021 to help support his efforts developing the free plugin but said this is no longer necessary.</p>



<p>&#8220;Originally I had planned on developing a plugin business,&#8221; he said. &#8220;But I found my love for building, contributing, and educating surpassed my desire to be an entrepreneur in the plugin space. This way, I can focus on my passion and also support the community.&#8221;</p>



<p>Version 3.0.0 includes previously pro features such as <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-browser-device-control/">browser and device control</a> that allows for displaying custom content based on the browser and/or device of the current user. It also adds <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-location-control/">Location control</a>, which isn&#8217;t what it sounds like. It allows users to show or hide content based on where the block is located on the website and attributes of its location. Blocks can be conditionally displayed based on post taxonomy, post type, and other rules that offer more control over block visibility than one might ever have imagined possible.</p>



<img />Block Visibility documentation on <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-browser-device-control/">Browser and Device Control</a>



<p>This update brings in controls for <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-cookie-control/">Cookies</a>, <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-metadata-control/">Metadata</a>, <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-referral-source-control/">Referral Source</a>, and <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-url-path-control/">URL Path</a>. It expands the <a href="https://blockvisibilitywp.com/knowledge-base/how-to-use-the-date-time-control/">Date &amp; Time</a> control to include Day of Week and Time of Day. </p>



<p><a href="https://blockvisibilitywp.com/knowledge-base/guide-to-visibility-presets/">Visibility Presets</a> is another mind-blowing new feature in this release, the kind that makes you wonder how this could be a free plugin. It allows users to create a collection of visibility conditions that can be applied to other blocks with a single click. Blocks can have multiple presets applied, and Diego said this is just the first iteration of this feature. </p>



<img />Block Visibility documentation on <a href="https://blockvisibilitywp.com/knowledge-base/guide-to-visibility-presets/">Visibility Presets</a>



<p>This release includes everything except the WooCommerce and Easy Digital Downloads controls, which include conditional block logic for shopping cart contents, product details, customer metrics, and more. Diego plans to add those later in April with the next version (3.1.0), so he can make a few further changes to them before including them in the free version. Users who rely on the WooCommerce or Easy Digital Downloads controls will need to wait until the next release to deactivate the Pro add-on.</p>



<p>The Block Visibility plugin&#8217;s <a href="https://blockvisibilitywp.com/knowledge-base/">documentation</a> is already extensive, with videos, screenshots, and tutorials for nearly every feature. Diego said he will be investing more time into documenting how developers can create their own <a href="https://github.com/ndiego/block-visibility-add-on-example">Block Visibility extensions</a>. The plugin currently has more than 9,000 active users and will likely see more growth now that the pro features are getting rolled into the free version. </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, 25 Mar 2023 02:31: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: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:63:"Post Status: Launching a WordPress Product in Public: Session 6";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=148481";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"https://poststatus.com/launching-a-wordpress-product-in-public-session-6/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:39309:"<div class="is-layout-flow wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">Transcript ↓ Learn from Corey Maass, a master of WordPress plugins and apps, and Cory Miller, a marketing, business, and WordPress experience guru. The two discuss the intimacies of partnering on a product and how solopreneurs can benefit from support. Top Takeaways: <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f517.png" alt="🔗" class="wp-smiley" /> Mentioned in the show: <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f426.png" alt="🐦" class="wp-smiley" /> You can follow Post Status and our&#8230; </p></div>


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



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







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



<p>Learn from <a href="https://twitter.com/coreymaass">Corey Maass</a>, a master of WordPress plugins and apps, and <a href="https://twitter.com/corymiller303">Cory Miller</a>, a marketing, business, and WordPress experience guru. The two discuss the intimacies of partnering on a product and how solopreneurs can benefit from support.</p>



<p><strong>Top Takeaways:</strong></p>



<ul>
<li><strong>The Value of Partnerships.</strong> Starting a business can be a lonely experience. Having someone to bounce ideas off, talk through tough subjects with, and celebrate successes with makes a significant difference. Having that collaborative support system can make managing a business more enjoyable and streamlined, which is a huge benefit, especially for startups and small businesses.&nbsp;</li>



<li><strong>Discussion vs. Decision. </strong>It’s important to be intentional with communication considering the stage you are in when you are improving a product or creating something brand new. Being vocal about whether you are still discussing or whether you are ready to make decisive moves is critical to keep the process moving forward without missteps.&nbsp;</li>



<li><strong>The Art of Failing.</strong> Understanding that taking risks and being willing to fail in order to ultimately achieve success is key for solopreneurs and partnerships. Quantifying your success rate on projects isn’t the ultimate indicator of how successful you truly are. Stumbling through a myriad of shortcomings while still pursuing success is powerful.</li>
</ul>



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

</div>



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



<ul>
<li><a href="https://crop.express/">Crop.Express</a></li>



<li><a href="https://elementor.com/">Elementor</a></li>



<li><a href="https://www.wpbeaverbuilder.com/?mm_campaign=brand&gclid=Cj0KCQjwtsCgBhDEARIsAE7RYh23X1L149jQi21SES3Z61y0aaY770GDRGkCSimg-hDgjtWb6JfA0xEaAqzDEALw_wcB">Beaver Builder</a></li>
</ul>



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



<ul class="eplus-wrapper">
<li><a href="http://twitter.com/coreymaass">Corey Maass</a></li>



<li><a href="https://twitter.com/corymiller303">Cory Miller</a> (CEO, <a href="https://twitter.com/post_status">Post Status</a>)</li>



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



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



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



<h2>Session 6 Corey &amp; Cory Launch a WordPress Product Live</h2>



<p>Cory Miller: [00:00:00] Ooh, cheers are good. . You talented, man.<br />Corey Maass: So yeah, session six. Okay. Impromptu time change, but life happens. And that&#8217;s part of the<br />journey of being a founder. Exactly.<br />Cory Miller: Let me push it to Twitter.<br />Corey Maass: Are we founders? Yeah.<br />Entrepreneurs, founders Starters,<br />for once. I&#8217;m not a solopreneur,<br />Cory Miller: you know, I talked to a lot of people over the years and, um, Like solopreneurs. And the one thing I<br />hear from a lot of &#8217;em, cause I had, I had partners from the beginning, they weren&#8217;t active. But is that, you know,<br />business as lonely as it is and um, [00:01:00] having somebody else to kind of walk with I think is pretty dang<br />awesome.<br />Yeah,<br />Corey Maass: I, I did it best when I worked in a co-working space with, Four other guys that I was friends with and<br />we had formed a little cohort and so regularly, you know, get out of, get out of the house, get to a, a focused place<br />of work. And then have people who you were on a journey with and knew their journey.<br />And so you could grab somebody and say, Hey, can we talk this through for a minute? And that went in all<br />directions. Like it just makes such a difference. Yeah,<br />Cory Miller: it, it really does. Um, I had Matt Daner and I themes, um, On the team. And of course my Lindsay<br />was, um, in and around the team in different ways. Um, and it was just then I have my business group, which I told<br />you I&#8217;m meeting with this afternoon, [00:02:00] I&#8217;ve walked with for 11 years, and I tell you, wow, it&#8217;s such a tough<br />job.<br />You know, where you&#8217;re trying to, like we&#8217;re doing here. Where if it wasn&#8217;t with you, I&#8217;d be sitting here going, okay,<br />what segments are we gonna try to hit? You know, and. And the highs and lows. You know, there&#8217;s things that you<br />celebrate as an entrepreneur that you not, maybe not necessarily celebrate with your team.<br />And just having another group, or a sidekick or a partner or whatever that is, I think is pretty dang healthy for me<br />Corey Maass: at least. Yeah. And yeah, it&#8217;s, it&#8217;s a step better than rubber ducking it also, I find, Because it&#8217;s like,<br />you know, I don&#8217;t, I don&#8217;t always immediately respond to you, and you don&#8217;t always immediately respond to me.<br />But I have a, a real human being to say things at, even if it&#8217;s not to talk about it with, and, you know, when you see<br />the message in the afternoon and, and [00:03:00] celebrate it with me, that I fixed a bug or whatever it is like that.<br />Makes a difference and you ping me out of, you know, whenever you kind of, whenever you need to.<br />Like, that&#8217;s such a difference cuz like, who did I, oh, for a different product. I was having issues with, not issues at<br />all with, um, EDD I was trying to hack the hell out of EDD , let&#8217;s be honest. Um, to make it do things that it has no<br />right doing. Because it&#8217;s the better product. I&#8217;d rather use the core and slap my janky ass code on top of it.<br />Anyway, there&#8217;s my little EDDendorsement. Um, but I know one of the head programmers over there and was like,<br />I would love to have him look at this. And he and I were in a. Co-working group years ago. And so I have a little bit<br />of connection with him, you know, but haven&#8217;t talked to him in a year or two.<br />And so I had to hesitate and I hemmed and hod and was like, let me, let me refactor this five [00:04:00] times<br />before I send it over to him because I don&#8217;t wanna waste his time. I&#8217;m using up a favor. I guess that&#8217;s my long way<br />of saying that I&#8217;m using up a favor. And uh, and if you have somebody. You&#8217;ve lost count of favors or you have a<br />partner, then you don&#8217;t have to hesitate.<br />And honestly, that, that lack of hesitation is huge. I hadn&#8217;t really thought about it like that, but it&#8217;s just that what a<br />waste of time. I mean, it was great that it made me refactor my code because, you know, that&#8217;s never a bad thing.<br />But, uh, have to think that hard about just asking a question rather than just asking a question.<br />Maybe that&#8217;s why we all like chat, GPT or something.<br />Cory Miller: Yeah. You&#8217;re not alone, . No, I, I think that&#8217;s, uh, when I left eye themes, I wanted to do coaching and<br />had some clients my first year before I started with post status and, um, I said, you know, the hardest for me was<br />when I was [00:05:00] in trying to make these big decisions and, and even the little ones, and just having<br />someone.<br />I could bounce things off of. So that, that&#8217;s one of the reasons I did coaching. One of the reasons I talked about my<br />group as much like I left, came back, they were gracious enough to, to let me come back. And, um, these were the<br />several of the guys that were in Phoenix with me and, um, In fact, that&#8217;s who&#8217;s funeral, uh, dad&#8217;s funeral.<br />One of the guys that went with us is where I&#8217;m going today. Mm. Uh, while we couldn&#8217;t meet at a normal time, but,<br />you know, just kind of doing life together, but then having someone just to bounce stuff off of, like, I feel like you&#8217;re<br />very open and we&#8217;re having this conversation where it&#8217;s, it feels like, you know, the whole improv plus one, it&#8217;s like<br />we&#8217;re keeping, we&#8217;re, I think we&#8217;re trying to keep each other kind of.<br />on the trail here, but you know, you&#8217;d let me veer off and like discuss it. Let&#8217;s take a sidebar side trail. Yeah.<br />[00:06:00] And come back, . And that&#8217;s part of my process though, and I really deeply respect that and appreciate<br />it for you. Um, but just having somebody that understands that you can bounce stuff off, it&#8217;s pretty, pretty critical.<br />Corey Maass: Yeah. Well, I, I&#8217;m a big proponent of, uh, discussion, not decision, which I. Once I learned that I, I&#8217;m<br />a, I&#8217;m a big rule person, so like I applied that rule to most conversations and try to make sure that it&#8217;s clear to<br />everybody else. Um, but also I think more often it&#8217;s the. Being vocal about when you&#8217;re switching to decision.<br />So it&#8217;s like, okay, you know, we are still discussing, we are still discussing. Now we are deciding because as you&#8217;ve<br />seen, I&#8217;m prone to go, oh, that sounded cool, and then I just go off and, and do it rather than, you know, is that the<br />best use of my time, is at the highest priority, all [00:07:00] those kinds of things.</p>



<p>So try to impose that upon myself a lot of the time too of like, is. You know, because I&#8217;m also, I&#8217;m the type of<br />extrovert who needs to talk out loud. And so there tends to be a lot of discussion. Um, you know, oh, hold on, I got<br />a barking dog. Come on.<br />Cory Miller: I think that&#8217;s good, especially in the beginning, in the start, you know, um, is making, you know, the<br />whole woodworking thing is measured twice, cut once kind of thing. Not to say to get into overthinking or<br />overanalyzing, but we&#8217;re, we&#8217;re figuring it out, you know? Right. Uh, together. And I think that&#8217;s been pretty critical<br />and really, like last week was huge breakthrough for me.<br />It&#8217;s. Seeing, okay, here&#8217;s v1, or here&#8217;s the free version, I should say, what we&#8217;re gonna do there, and then there&#8217;s<br />all this, we can kind of chase and see what&#8217;s there for [00:08:00] the pro side.<br />Corey Maass: Yep. Yep. One more, one more comment on partnerships too is I think I&#8217;ve talked about like I&#8217;ve,<br />I&#8217;ve looked for people to work with for years and one of those.<br />one of the outstanding questions is always that I&#8217;ve, that I&#8217;ve heard from other people that I&#8217;ve worried about too, is<br />the, like, how do you, how do you quantify compatibility? Right? And it&#8217;s like, I couldn&#8217;t, I think I&#8217;m, I&#8217;m bringing this<br />up rhetorically, like, it&#8217;s not a question necessarily unless you have something, unless you have an answer.<br />But it&#8217;s like, You, you and I sort of talked about it a little bit and then said, okay, let&#8217;s work on this together, and I<br />didn&#8217;t hesitate and, and of course then I&#8217;m like, you know, then we have amazing con like we&#8217;ve had amazing<br />conversations. . And I think that it helps that we both have [00:09:00] been aware of each other for a while and so<br />have some sense of how we operate.<br />And I think I&#8217;ve also, I&#8217;ve heard you speak in public, you&#8217;ve heard me speak in public, so I, I had a sense of you,<br />and I&#8217;m being presumptuous, but I imagine you had some sense of me. Um, but it&#8217;s, it&#8217;s definitely one of those,<br />What does this look like in a year? And if we end up with, you know, an I themes or a, you know, something,<br />something, Of of decent size.<br />You know how, how do you know that that person that you casually said, oh yeah, we should work on this little<br />plugin together with ends up being the person that you partner with. And that&#8217;s, it&#8217;s crazy cuz there&#8217;s so much<br />around pairing people and, you know, meeting co-founders and stuff like that, and, Yeah, I don&#8217;t know.<br />It&#8217;s ju it&#8217;s like I say, I think I&#8217;m bringing it up rhetorically from my perspective. It&#8217;s just, it&#8217;s a crapshoot. You just kind<br />of go with your gut .<br />Cory Miller: [00:10:00] Yeah, I, I totally agree. Um, you know, I, I&#8217;m trying to think how many times I&#8217;ve partnered<br />and it&#8217;s been quite a few, you know, uh, Brian, initially with post status, I had two partners.<br />They weren&#8217;t, weren&#8217;t active in the business. Um, at Ithe, I&#8217;ve had several. Um, partnerships last four years. Um,<br />and, uh, I, I almost think it&#8217;s like this product stuff, partner, partnerships and products are very similar in my<br />experience for me is that . I told Lindsay, I said, you know, when we started Ithe, it&#8217;s like people bought it and they<br />kept buying it and it was pretty, pretty simple, like a good looking theme.<br />You know, and this is 2008, and I did these things and put &#8217;em out there and things that I kind of wanted for myself,<br />but I didn&#8217;t think, like, I didn&#8217;t have a big inner monologue of like, should I do dropdown menu? Should I not?<br />Should I do? [00:11:00] I was just doing things I wanted to do, which spoke to like, I was obviously embedded in<br />our user group that were customers that eventually bought to us.<br />And I think that was first. But like I say, I compare it to baseball, like products and maybe even partnership and<br />people, it&#8217;s like, you know, classic growing up was Tony Gwen, San Diego Padres. He got on base all the time. If<br />you hit 300 in the majors, you&#8217;re, you&#8217;re in the Hall of Fame. If you have a career consistently with 300 in, you&#8217;re,<br />you&#8217;re in the Hall of Fame, even close to it, you&#8217;re probably in the Hall of Fame.<br />And, uh, when I left Ithe and tried to start some new projects, products, and businesses and partnerships, I was<br />like, oh yeah, I just know, I know how to do this, I can do this. And I was like, oh, you know, that means Tony struck<br />out three out of 10 means Tony struck out or got out seven times out of 10, but he&#8217;s in the Hall of Fame.<br />And I&#8217;m like, wow. That&#8217;s kind of like [00:12:00] entrepreneurship and products. And, and I&#8217;m gonna go even<br />further, uh, uh, partnerships, you know, like it&#8217;s, it&#8217;s not a high percentage of wins in my personal experience. , um,<br />from products like, I don&#8217;t know if you, if I told you this, we had 200 s skews that I think were not left 200 plus.<br />How many of those actually made money? Right? Like maybe it&#8217;s, that&#8217;s a little bit low, but like, you know, and uh,<br />then I&#8217;ve gotten crushed cuz things just don&#8217;t go as fast or as easy as I always want them to. And you&#8217;ve done a<br />number of products and I don&#8217;t know where you&#8217;re, you staying with partnerships, but, Just a lot of failure, a lot of<br />learn learning lessons.<br />Corey Maass: I, I learned, I was in New York, uh, I had just moved to New York after college and there was one<br />couple, so I was pursuing mo a music career, mostly, um, DJing, producing dance music, electronic music. And<br />there was one [00:13:00] married couple who threw a party and had started a label and. They were, uh, they were<br />bananas.<br />They were all over the place. They were, they&#8217;re still very eccentric people. I, I love them to death, but they are, uh,<br />sometimes out there. But I would follow them anywhere. And I, and I finally quantified it and I was like, because<br />they. 7% of what they say they&#8217;re gonna do. Everybody in New York City talks a great game.<br />Every bartender is a comedian. You know, every person you meet, working any kind of job is actually writing a<br />script or is in a band or whatever, which is awesome. But most people talk a really good game and don&#8217;t actually<br />do. What they say they&#8217;re gonna do. And so I think that for me, a lot of it is, is exactly what you talked about.<br />Like people don&#8217;t have to have success. Like I didn&#8217;t wanna work with you be necessarily because you had<br />success, [00:14:00] but because you&#8217;ve put yourself out there, you&#8217;ve clearly done a lot, you&#8217;ve tried a lot, and you<br />keep trying. And I think that that, like for me, that&#8217;s the gold standard. Like I try to live by that.<br />Like I put, I put a lot of products out there. Same thing have, how many of my products have actually like done<br />anything made little blips, you know? But you&#8217;ve gotta keep getting up to bat. I think this is the first baseball</p>



<p>analogy I&#8217;ve ever made in my life. But you&#8217;ve gotta keep getting up to bat and eventually you&#8217;re gonna hit<br />something, presumably, you know, big or small.<br />And then you want to keep, you know, practice makes perfect kind.<br />Cory Miller: I tell you, the part of like, keep going on is the one I&#8217;ve really struggled with the last four years. Hmm.<br />Just keep going on. Um, and then last year with the burnout, um, and all that kind of stuff is just like, it&#8217;s, it&#8217;s tough<br />because, uh, it&#8217;s, it&#8217;s one thing if like this, nothing huge, significant, but not like life shattering.<br />Is dependent on [00:15:00] this. Um, but you know, when I left Ithe, I didn&#8217;t really have another business to just<br />kind of walk onto. Now Posttest came next, you know, the next year, and it wa and it was like really good timing for<br />me. Um, but now it&#8217;s, you know, it&#8217;s still a part-time gig for me. So like, It, it&#8217;s been tough cuz you just kind of have<br />these ideas to put &#8217;em out there.<br />And the theme I told people for how I&#8217;ve done business, at least my ithe chapter, is stumbling successfully. Like ,<br />keeping going, tripping but not falling flat on your face. You know, like, just kind of keep a low profile to the ground.<br />Cause you&#8217;re gonna keep stumbling. And, and you know, a lot of the products, for instance, were stumbled like,<br />and I&#8217;m not, I&#8217;m not saying it&#8217;s pure.<br />However, there was healthy blend of right time or a place, um, hard work, right. To get more luck. And then once<br />the first one was rolling, it was easier to add [00:16:00] new, you know, when you get that first hit, it&#8217;s easier to hit<br />to do others. But I still didn&#8217;t have even a like 50% success rate , you know?<br />Corey Maass: Yep. Well look at Google.<br />How many products have they shut down, you know? Yeah. So anyway, sorry. I wanna respect your time. So<br />we&#8217;ve got 10 minutes. I&#8217;ve, I&#8217;ve dragged this out much longer than I needed to. I did too. Um, um, so product, we<br />have version 0 0 2 is in the repo. Uh, the has come a long way. Uh, we have added, uh, a few bells and whistles.<br />I&#8217;ve cleaned up the UI a bit, and then a duplicate. Cropper is now in the media library. So if you go to media library,<br />there&#8217;s now an extra button that says Upload and Crop. Next to add new. I felt a little bad totally ripping out the<br />ADD new button, but we can decide to do that because there is now a [00:17:00] bypass.<br />So you, even if you open the cropper, And select an image. There&#8217;s a button that says, crop it. There&#8217;s a button<br />that says Just upload it so you can bypass the crop. Um, and then the other sort of sneaky thing that I, I added last<br />minute yesterday is if you go to media, add new, it technically opens the media library with the cropper open.<br />So we are totally hijacking media a new, so I mean, all these. Discussions, not decisions, but at this point we&#8217;ve<br />still got fewer than 10 users. And you and I are, are kind of, you know, we are a kitten with a ball. We&#8217;re bating it<br />around just kind of deciding, you know, where we wanna land with it.<br />Cory Miller: Um, it&#8217;s great. The new stuff that you pushed out, I think that&#8217;s awesome. Iterating on some things<br />that you feel like, hey, I, this is a small little check I can do that I think is so good for progress on the product.<br />[00:18:00] So I was looking at it on my personal site and then my test site and um, I&#8217;ll give you, I&#8217;ll give you notes,<br />uh, in chat too.<br />But when I tried to upload from the media library and I just installed the new plugin on my personal, lemme do this<br />real quick. It&#8217;s not showing the preview. Sorry. I should just be showing you.<br />It&#8217;s not showing that preview. And maybe I&#8217;ve got the wrong image or something like that, but, oh, huh. So we got<br />uploading crop<br />so it&#8217;s not preview in here, and then I just click square crop. Huh. So I don&#8217;t, I I, I&#8217;ve done it at least on two sites<br />and it&#8217;s done this, so I wanted to mention it. Ooh. But lemme just say, Thank you for that button iterating on those<br />buttons, these two, because I was testing your previous version [00:19:00] and with my, with images from my<br />phone, and one was like sideways and I was like, Hey, so oh yeah, you got that in like, I don&#8217;t<br />know, an hour after we test.<br />Corey Maass: Well, I, yeah, the, I mean this is, we are still riding the, the happiness that is the library we&#8217;re using.<br />Um, so there&#8217;s, there&#8217;s, they. Rotate. They also have, um, you can actually flip it horizontally and vertically, which is<br />an option, but I don&#8217;t think we need it. Um, I don&#8217;t, I don&#8217;t yet see the use case. Um, but rotate, I was like, I will add<br />it.<br />He must be onto something. And the fact that you pulled it from your phone and we&#8217;re like, oh, instead of rotating it<br />on my phone and then uploading it again, make creative tasks simpler, easier, fun. There you go. Like, you<br />shouldn&#8217;t have to think like, oh, I have to rotate it in one place before I upload it to another.<br />Um, but I will go fix that bug. So, um, the, to me, the outstanding [00:20:00] question is, um, we, I think we did<br />come to the conclusion last week that we want a settings page, which let. The creator of the site or the whoever is<br />controlling the site, which might be the same person who&#8217;s creating content, but to go into a settings page and say,<br />four featured images, we want 16, nine, and we want them to be 1600 pixels wide every single time.<br />Set it once, forget it, and then they go set their featured image right. When we are including that. Originally we&#8217;d<br />said that that was be, that would be a paid thing, but I. I kind of feel like the free version&#8217;s useless without it.<br />Cory Miller: Yeah, I do too. And I think we&#8217;re gonna get more momentum, um, with this, with that thing cuz we, like<br />we talked last week, really becomes a cool utility tool for a, a problem.<br />And so<br />Corey Maass: and, and is and is feature complete? Is product complete? [00:21:00] Yep.<br />Cory Miller: Yeah. So the savings page with the custom. Dimensions. That&#8217;s really our biggest thing left, is that<br />right?<br />Corey Maass: Uh, and, and we want to, there&#8217;s all the other holes, all the other places where you upload an<br />image. So to me, um, after media library, I think block is the next big one.<br />So I think we, I think we need, cuz I, I use the classic editor and I&#8217;m gonna look at. Adding our cropper to featured<br />image. You know, and, and classic editor plugin has, you know, millions of installs. So I, it&#8217;s, it there. I don&#8217;t think<br />there&#8217;s, to me, there&#8217;s not a clear majority one way or the other. Gutenberg block editor over classic editor.</p>



<p>We need, we need the cropper in both. Um, but since we have [00:22:00] the beginning of the block, I think that<br />that&#8217;s, um, the way to go. And I, I, at some point I will look. Also applying it to the classic editor. Okay. But it&#8217;s, it&#8217;s<br />finding all of those primary places and there&#8217;s a lo as we&#8217;ve talked about, there&#8217;s a long, long tail.<br />Like eventually we will build a module for Elementor and, and Beaver Builder. Um, but we need to work, work for<br />vanilla WordPress first. Yeah.<br />Cory Miller: So that leaves me at really, and I&#8217;m with this with process too, is like, we need a lot, it seems like we<br />need a lot of users. Mm-hmm. to start getting more users in there, giving feedback, requesting features.<br />And this next one with the, uh, well the blocks will be big, but that&#8217;s another conversation. But like, I think the<br />custom dimensions, then we&#8217;re getting [00:23:00] something. I ped and ccd you in those. As you know, Robbie<br />from Beaver Builder, Kathy San from Cadence. Um, I need to look at generate press. Um, but then we bumped up<br />against like everybody be gone, being gone for Asia or Camp Asia.<br />Um, but yeah, are you going to any word camps? I&#8217;ll have it down for like a placeholder for Europe and then US is<br />standard for me for sure. You are gonna go, yeah, I was supposed to go to Phoenix, but yeah. What, what about<br />you? Do you have any plans.<br />Corey Maass: I was, uh, thinking about US . So if you&#8217;re gonna be there, then yeah, we need to meet up.<br />That&#8217;s in August, so. Okay. It gives us, um, let&#8217;s do plenty of time to, I think that&#8217;d be a blast. Yeah. We could do<br />this live. That&#8217;d be fun. Do it live.<br />Cory Miller: Let&#8217;s, uh, let&#8217;s plan. Yeah, let&#8217;s plan on that. I&#8217;d be, that&#8217;d be great if another opportunity comes up in<br />between. Um, I know work camps are getting started and [00:24:00] stuff, or, um, we&#8217;ve loosely been throwing<br />around some in-person stuff with.<br />Post, but I&#8217;ll let you know, uh, before we even announce that and see if you&#8217;re able to, to get to it too. Um, nothing,<br />sorry.<br />Corey Maass: Yeah. Um, I derailed us. So you were talking about getting users. Um, do we, to me, I&#8217;m starting<br />more and more, I&#8217;m getting anxious that we don&#8217;t have a website. Okay. Which, I mean, we.<br />crop.express the website that is currently just the cropper, um, but to, with no mention of the plugin. And so I&#8217;d love<br />for you to start thinking about what that looks like,<br />even if it&#8217;s a little banner that then links to a landing. You know, we could have crop.express/wordpress plugin and<br />have a landing page temporarily, but [00:25:00] just cuz it&#8217;s even like I&#8217;m now. I&#8217;m linking people to the plugin in the<br />repo, but I feel like we wanna start expanding the use case, expanding what we&#8217;re talking about, you know, to a<br />website.<br />Cory Miller: Um, yes, absolutely. I think we&#8217;re there<br />Corey Maass: in the coming weeks. It doesn&#8217;t need to be tomorrow. Yeah,<br />Cory Miller: I was thinking about. Um, from the brand we talked about last week too. Mm-hmm. , it&#8217;s like, do we<br />just go ahead and make the keep, keep crop.express like it is? Hmm. Probably link to it, but then at some point<br />we&#8217;ll probably want to change an update plugin to go what our new brand is.<br />And that made me think about, my mind went to. Some discussion that could be recorded like this for users, not<br />about our product [00:26:00] necessarily, or this detailed stuff, but you know, hey, here&#8217;s some sources we can,<br />where you can go find all, you know, all these images. Um, some of those mar more messaging, marketing<br />content, thoughts we had last week.<br />I was like, you know, that might be, um, pretty good. It&#8217;s like having that site. Maybe scheduling, you know, some,<br />like, we outline it loosely and just talk through and then we can take that, you know, put it on our YouTube channel,<br />all that kinda stuff. And then, um, maybe see if we turn that into like our lead magnet or something like that to start<br />building emails.<br />That&#8217;s where my head goes initially, but I&#8217;ve. We&#8217;ve got two things on my list, outreach and website. Um, right now,<br />at least until you tell me otherwise. Um,<br />Corey Maass: well, and, and the other thing that Kathy brought up that I thought was valuable was to aid in your<br />discussions. [00:27:00] She&#8217;s like, oh, what does it do? And we&#8217;re, and you were like, here&#8217;s the plugin.<br />And she&#8217;s like, Oh, thanks. Now I have to go find a WordPress install, install it on this WordPress install. And then<br />because it&#8217;s essentially a a beta, we have no guidance. We have no user docs, we have no anything. And so she&#8217;s<br />like s Now if she even gets that far, she&#8217;s like splashing around trying to figure out what the hell it does and how<br />so?<br />Um, I kind of feel like we are getting close to, like, I could do a. QuickTime, screen capture of here&#8217;s how you re<br />crop your featured image. 1, 2, 3. Mm-hmm. , here&#8217;s how you crop an image going into media library, you know,<br />and put them on YouTube or you know, even just to have them in our back pocket. One for any potential users, we<br />can link to those.<br />If they&#8217;re on YouTube, we can put those in our readme, which goes on the, you know, So it&#8217;s Crop Express in 30<br />seconds, a video in [00:28:00] that, in the Read Me Doc in the, in the repo. Um, and it gives you something to link<br />to when you&#8217;re having dis discussions because rather than you having to do a demo or people trying to figure it<br />out, you know, here&#8217;s, here&#8217;s a quick 32nd video, then let&#8217;s have a conversation.<br />Yeah. So it seems like if you agree that I feel like that should go on my list. Oh,<br />Cory Miller: if you&#8217;re good to put on your list, absolutely. Yeah, I<br />Corey Maass: can bang through those pretty<br />Cory Miller: quick. And that lends back to website is like having something where people can see it. Mm-hmm. .<br />Um, yeah, I&#8217;ll, okay, I&#8217;ll do some thinking on that.<br />Corey Maass: Yeah. Again, I feel like we&#8217;re, right now these are discussions, not decisions, but good ideas, so,<br />Yeah. Uh, ruminate on them a little bit today, and then, you know, this week or next, let&#8217;s make some decisions.</p>



<p>Okay? [00:29:00] All right. And I&#8217;ll continue. No matter what, there&#8217;s this. You know, as a developer, you&#8217;re like<br />building product and it&#8217;s, and it&#8217;s a straight line.<br />It&#8217;s a rocket ship going up, but it&#8217;s inevitable to do everything else. There&#8217;s, there&#8217;s the, the triangle. So as the<br />triangle goes up, it gets wider and wider. and wider. I&#8217;m just seeing it. It&#8217;s like I can just keep adding features. I can<br />just keep making the product better, but nobody&#8217;s gonna know about it.<br />Nobody gives a shit. There&#8217;s no, you know, but it&#8217;s like, Ever so slightly the more features then it&#8217;s like the more<br />you want a website, the more you want docs, the more you want, uh, feedback. The more you want assets, the<br />more you want swag, the more you want, you know, and it just keeps getting broader as, as much as it gets taller.<br />It feels like that<br />Cory Miller: It does, it def definitely blends over time. Um, okay, so I&#8217;ve got outreach and website to continue the<br />outreach outreach. Um, [00:30:00] I think Kathy, I think Robbie, when he&#8217;s back, um, I need to reach out to the<br />Elementor team.<br />Corey Maass: Do you have, um, like the starting in the conversation seemed good. Do you have a plan for<br />specific questions that we&#8217;re trying to get answered?<br />Um, or do you wanna leave it broad?<br />Cory Miller: What I intend to get to them with that is like getting to the heart of what are the things that annoyed<br />the team, building the themes. Mm-hmm. , what are they hearing from customers? Um, and, or even, even seeing<br />like they see sight and like the images just blown out and stuff.<br />And I, I want to keep those conversations open enough where they can tell us something I might surprise us that<br />goes in a particular direction.<br />So, and I think Rob Robbie&#8217;s very open to that. He just is out this week. So yeah, [00:31:00] sure. I&#8217;m really eager<br />to hear what he says. And that&#8217;ll be our first integration or, you know, potential integration for us thinking through<br />that. Um, so that&#8217;s kind of my intention. And then, uh, same thing with, um, any other theme framework from<br />Element towards generate press<br />sounds. But open. Do you have any thoughts or anybody else we should talk to? But you know, and then, well, the<br />story I&#8217;ll share too is like, here&#8217;s what free is gonna be, you know, and then to start to share the story to lead to this.<br />This could be a great tool for y&#8217;all to recommend to your communities kind of thing.<br />So I&#8217;ll, once I get some of those, I&#8217;ll drill down into, okay, cadence. What are the ratios, what are the things that we<br />could build into free to be, you know, that utility tool?<br />Corey Maass: Yeah, for sure. [00:32:00] So that, that&#8217;s kind of my plan there is just kind of digging in and seeing<br />what we hear. Trying to get to that true marrow of it.<br />Like how are people using it? What are you seeing? And hopefully be surprised. Love.<br />Um, and I&#8217;ll, I&#8217;ll do some thought too on the website. I know that&#8217;s been something we&#8217;ve been talking about,<br />um, but I like what you just said, like that solves the problem. If we switch to a branded site that talks ab, that&#8217;s, or<br />a company site that lets us be open up to anything, crop Express can stay the same.<br />Start to talk about the plugin and link back to what ultimately would be the shopping cart or the mm-hmm. , you<br />know, the main marketing site around it. But let crop.express as a website, be a lead magnet, a U [00:33:00] utility<br />site that is a lead magnet for the WordPress plugin. And for anything else, we end up spitting up.<br />Mm-hmm.<br />Cory Miller: Yeah. And then you&#8217;ve got a great free tool out there, so. Right. I do think, like you said, the banner<br />to, do you want the WordPress version, you know, you want this in WordPress and link over to the thing will be<br />helpful as we kind of grow for people to Yep. See the vision. Okay. All right. Anything else you had?<br />Corey Maass: No, I, I just, we&#8217;ve been, I like, I think I talked to you before. I, I&#8217;ve been watching Silicon Valley, so<br />I&#8217;m, I&#8217;m feeling like we need to scale up. We need to get some, um, venture capital. I need at least three more<br />developers under me.<br />Cory Miller: Um, I gotta get back and<br />Corey Maass: watch that. Move all of our operations out to Silicon Valley.<br />Of course. Hey, I&#8217;m in San Francisco in three weeks I&#8217;ll do our first raise. Um, I&#8217;ll talk to some angels out<br />Cory Miller: there. There you go. . When that came out, I, [00:34:00] I actually happened to have at the time a<br />little community car. It was a Ford Escape. Yellow, just like, uh, ,<br />Corey Maass: Avi Avik,<br />Cory Miller: ak a classic.<br />Corey Maass: All right, man. Well, good luck today.<br />Okay. It&#8217;ll be a long day. Hope you&#8217;ll be all right. Yeah. And, uh, I&#8217;ll<br />Cory Miller: appreciate that.<br />Corey Maass: Um, yeah, I&#8217;ll keep you posted.<br />Cory Miller: Okay, sounds good. And I&#8217;ll get these webinars back on the, reschedule them and put &#8217;em on our<br />calendars. Okay. So, sounds<br />Corey Maass: good. All right. Thanks. Thanks, Steve.<br />Cory Miller: Bye.</p>
<p>This article was published at Post Status — the community for WordPress professionals.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Mar 2023 22:38:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Cory Miller";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:99:"WPTavern: WooCommerce Payments Plugin Patches Critical Vulnerability That Would Allow Site Takeover";s:7:"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=142990";s:7:"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:110:"https://wptavern.com/woocommerce-payments-plugin-patches-critical-vulnerability-that-would-allow-site-takeover";s: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:2021:"<p><a href="https://wordpress.org/plugins/woocommerce-payments/">WooCommerce Payments</a>, a plugin that allows WooCommerce store owners to accept credit and debit card payments and manage transactions inside the WordPress dashboard, has patched an Authentication Bypass and Privilege Escalation vulnerability with a 9.8 (Critical) CVSS score. The plugin is active on more than 500,000 websites.</p>



<p>Beau Lebens, WooCommerce&#8217;s Head of Engineering, published an <a href="https://developer.woocommerce.com/2023/03/23/critical-vulnerability-detected-in-woocommerce-payments-what-you-need-to-know/">advisory</a> about the vulnerability today, which he said &#8220;could permit unauthorized admin access to impacted stores&#8221; if exploited. It was discovered by a security researcher participating in WooCommerce&#8217;s HackerOne program.</p>



<p>WooCommerce worked with WordPress.org to push out a forced update for sites running WooCommerce Payments versions 4.8.0 through 5.6.1 to patched versions. Many store owners have automatic updates turned off to ensure proper testing before updating. Now that the vulnerability has been made public, it is imperative that all stores running version 4.8.0+ of the plugin update manually as soon as possible. WooCommerce sites hosted on WordPress.com, Pressable, and WPVIP have already been patched.</p>



<p>At this time WooCommerce does not have any evidence of the vulnerability being exploited but the plugin&#8217;s engineers recommend checking for any unexpected admin users or posts addd to the site. The <a href="https://developer.woocommerce.com/2023/03/23/critical-vulnerability-detected-in-woocommerce-payments-what-you-need-to-know/">advisory</a> includes further details of what to do if you believe your site has been impacted. As a cautionary measure, WooCommerce has temporarily disabled the <a href="https://woocommerce.com/woopay/">WooPay</a> beta program since the vulnerability impacts this new checkout service they have been beta testing.</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, 23 Mar 2023 21:45:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:76:"WPTavern: Navigating the New Era of AI-Assisted Code Generation 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:30:"https://wptavern.com/?p=142932";s:7:"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:87:"https://wptavern.com/navigating-the-new-era-of-ai-assisted-code-generation-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:10059:"<p>The world is learning new ways of moving faster with the help of AI, as the increased availability of the technology is poised to transform the way humans work.  Generitive AI is decades old but recent advances and new tools like DALL-E (launched in January 2021) have made AI more accessible to the public. </p>



<p>When <a href="https://chat.openai.com/chat">ChatGPT</a> arrived in November 2022, it sparked an explosion of tools built to extend its capabilities to nearly every aspect of work. Conversational AI tools can now handle a myriad of mundane tasks like <a href="https://resumeworded.com/">updating your resume</a>, <a href="https://askyourpdf.com/">reading and summarizing PDFs</a>, and <a href="https://www.decktopus.com/">creating slides for presentations</a>. Yesterday Google announced it is testing <a href="https://bard.google.com/">Bard</a>, its AI chatbot rival to ChatGPT and Bing AI. In the fast-moving world of companies innovating with AI, GitHub also announced <a href="https://github.blog/2023-03-22-github-copilot-x-the-ai-powered-developer-experience/">Copilot X</a>, which is powered by GPT-4 and adds Copilot to pull requests, docs, and the command line and introduces chat and voice features for Copilot.</p>



<p>WordPress plugin developers are adopting AI-powered tech and building it into their products, such as <a href="https://rankmath.com/content-ai/">RankMath&#8217;s AI-generated suggestions for creating SEO-friendly content</a>, WordPress.com&#8217;s experimental blocks for <a href="https://wptavern.com/wordpress-com-is-testing-ai-generated-images-and-content">AI-generated images and content</a>, and a Setary&#8217;s plugin that <a href="https://setary.canny.io/changelog/effortlessly-enhance-your-product-descriptions">uses AI to write and bulk edit WooCommerce product descriptions</a>. The wpfrontpage site is <a href="https://wpfront.page/list/ai-plugins/">tracking</a> these plugins but WordPress.org also lists <a href="https://wordpress.org/plugins/search/ai/">dozens</a> of plugins with AI, many of them created to write content or generate images.</p>



<p>In addition to adding AI to plugins, developers have attempted to have ChatGPT build plugins for them, with <a href="https://twitter.com/chuckWnelson/status/1636082994619244547">varying</a> <a href="https://twitter.com/DarrenClasby/status/1638216096363708416">degrees</a> of <a href="https://twitter.com/edyoung_tweets/status/1638324231174864896">success</a>: </p>



<ul>
<li><a href="https://wptavern.com/chatgpt-creates-a-working-wordpress-plugin-on-the-first-try">ChatGPT Creates a Working WordPress Plugin – On the First Try</a></li>



<li><a href="https://thewpminute.com/so-i-built-a-wordpress-plugin-with-chatgpt/">So, I Built a WordPress Plugin With ChatGPT</a></li>



<li><a href="https://www.zdnet.com/article/i-asked-chatgpt-to-write-a-wordpress-plugin-i-needed-it-did-it-in-less-than-5-minutes/">I asked ChatGPT to write a WordPress plugin I needed. It did it in less than 5 minutes</a></li>



<li><a href="https://www.youtube.com/watch?v=PUvdtk1xjso">Unbelievable! How I Built 3 WordPress Plugins In 10 MINUTES using ChatGPT AI!</a></li>
</ul>



<p>So far developers <a href="https://twitter.com/mrvinceo/status/1638574726984486913">report</a> having more success with ChatGPT than Bard. In some cases the creation process is incomplete and requires some expertise to ensure the plugin will work, but it&#8217;s also opening up the world of plugin development to those who would not be able to create one without hiring a developer.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I have never coded a WordPress plugin in my life<br /><br />With the help of Chat GPT 4, I just did<br /><br />In the span of ~30 mins, I was able to work with GPT4 to come up with a solution for my WooCommerce store to add a discount of 1.5% for product quantities above 1 w/ a cap set at 6%<br /><br />INSANE</p>&mdash; Amado Serna (@amado_serna) <a href="https://twitter.com/amado_serna/status/1637170105363886081?ref_src=twsrc%5Etfw">March 18, 2023</a></blockquote>
</div>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">ChatGPT developed a WordPress plugin for us in just 3 minutes. Negotiating with a developer would have taken longer. <a href="https://t.co/lRqjWd9JPV">https://t.co/lRqjWd9JPV</a></p>&mdash; Amperly AI insights (@amperlycom) <a href="https://twitter.com/amperlycom/status/1636370735030738945?ref_src=twsrc%5Etfw">March 16, 2023</a></blockquote>
</div>



<p>WordPress developers who want to share their AI-assisted creations with the community have also started submitting them to WordPress.org.</p>



<p>After receiving a string of violations, WordPress&#8217; Plugin Team is <a href="https://make.wordpress.org/plugins/2023/03/21/use-of-code-generators-must-remain-gpl-compatible/">warning developers</a> that code submitted to the official directory must be GPL compatible.</p>



<p>&#8220;There is no guideline <em>AGAINST</em> using generated code,&#8221; Plugin Review Team rep Mika Epstein said.</p>



<p>&#8220;You’re welcome to use whatever tool you want to build plugins. That said, <em>you</em> are 100% responsible for that code if you chose to host it here&#8230;</p>



<p>&#8220;But the important bit here is that it means if ChatGPT, for example, built your plugin, <strong>you</strong> have to verify that all the code used is GPL compatible. Just like you are expected to validate licenses on libraries and code-snippets, everything in your plugin has to be GPL compatible. Should we determine that your code is a copy of someone else’s or includes code from non-GPL plugins, your submission will be rejected and any live plugins will be closed.&#8221;</p>



<p>Epstein cited an example where a developer built a &#8220;scroll to top&#8221; plugin with code that was copied from another, existing plugin hosted on WordPress.org. It was submitted five times and rejected every time. </p>



<p>&#8220;Yes it’s fine to fork code,&#8221; Epstein said. &#8220;You have to credit them, however, and that’s something those AIs have been pretty bad at doing.&#8221; </p>



<p>Commenters noted that autocomplete in modern IDEs work in a similar way, as well as snippets. These types of tools can enhance productivity but prospective plugin developers who may not be as informed about software licensing, should stay away from wholesale copying another&#8217;s work without crediting them. This may require doing some extra research on the code that AI spits out.</p>



<p>In this new era of AI-assisted creation, we have essentially hitched our wagon to a star, as Ralph Waldo Emerson described in his essay on Civilization in 1870:</p>



<blockquote class="wp-block-quote">
<p>Now that is the wisdom of a man, in every instance of his labor, to hitch his wagon to a star,’ and see his chore done by the gods themselves. That is the way we are strong, by borrowing the might of the elements. The forces of steam, gravity, galvanism, light, magnets, wind, fire, serve us day by day and cost us nothing.</p>
<cite>Ralph Waldo Emerson, <a href="https://emersoncentral.com/essays/civilization/">Civilization</a></cite></blockquote>



<p>That decade brought humanity inventions like the phonograph, telephone, and the incandescent light bulb, followed by the automobile in the next decade. Emerson&#8217;s essay explores man&#8217;s relationship to technology where principles—&#8221;justice, love, freedom, knowledge, utility&#8221;— are the guiding light and accelerant of technology&#8217;s impact.</p>



<p>The GPL is one of those principles for the WordPress community, which has enabled its uncommon growth and its wildly successful ecosystem. There are still a lot of grey areas when it comes to licensing and the code generated by AI. Developers would do well to use AI-generated code for inspiration and give credit where they can.</p>



<p>Web developer Mark Praschan <a href="https://twitter.com/MarkPraschan/status/1636025339926257664">created his first plugin for WordPress.org</a> using ChatGPT. He used the free version, gave it a few prompts describing what he wanted it to do, and ChatGPT produced a functional plugin.</p>



<p><a href="https://wordpress.org/plugins/northstar/">NorthStar</a> allows users to display a message in the WordPress admin bar with settings to customize it along with the text and background colors.</p>



<img />



<p>&#8220;The first version worked great,&#8221; Praschan said. &#8220;I made a few small aesthetic improvements to the settings page and the display of the message, but we were already 95% of the way there!&#8221;</p>



<p>Praschan also had ChatGPT design an ASCII Art logo for the plugin. It required a few back-and-forth prompts but took just a few minutes before it was ready to be copied and pasted into Photoshop. </p>



<img />



<p>The plugin did not pass the code review on the first try for two reasons that Praschan shared on Twitter:</p>



<ul>
<li>Issue # 1: Variables and options must be escaped when echo&#8217;d. There were 2 instances of not &#8220;escaping late&#8221;</li>



<li><a href="https://twitter.com/MarkPraschan"></a>Issue # 2: Generic function/class/define/namespace names. One function was missing the &#8220;northstar_&#8221; prefix.</li>
</ul>



<p>&#8220;How did I fix it? I made ChatGPT do it, of course,&#8221; Praschan said. &#8220;I copy/pasted the problems and a few snippets of my code and it spat out the fixed code.&#8221;</p>



<p>There are more of these plugins coming &#8211; where a person need only dream up the idea and prompt their chosen AI tool for the code. These will more than likely be simple plugins for the time being, but it&#8217;s not too early to establish some best practices for using code generators. WordPress is navigating new territory where anyone can create a plugin with a dash of creative prompts and very little code experience.</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, 23 Mar 2023 04:29: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: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:58:"Post Status: WordPress 6.2 RC4 • Code Generators and GPL";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=148430";s:7:"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://poststatus.com/wordpress-6-2-rc3-code-generators-and-gpl/";s: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:22000:"<h2 id="h-this-week-at-wordpress-org-march-20-2023">This Week at WordPress.org (March 20, 2023)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">We&#8217;re just one week away from WordPress 6.2. Have you tested it and read the field guide yet? If you write code for a plugin that is in the WordPress Plugins Repo, you&#8217;ll want to ensure the code is GPL compatible.  </p></div>


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



<div class="wp-block-kadence-infobox kt-info-box_94d1bd-77"><div class="kt-blocks-info-box-link-wrap kt-blocks-info-box-media-align-left kt-info-halign-left"><div class="kt-blocks-info-box-media-container"><div class="kt-blocks-info-box-media kt-info-media-animate-none"><div class="kadence-info-box-icon-container kt-info-icon-animate-none"><div class="kadence-info-box-icon-inner-container"><span class="kb-svg-icon-wrap kb-svg-icon-fas_robot kt-info-svg-icon"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title">WP 6.2 RC 4, Code Generators</h2><p class="kt-blocks-info-box-text"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f9ea.png" alt="🧪" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-candidate-4/">WordPress 6.2 Release Candidate 4</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64b-1f3fe.png" alt="🙋🏾" class="wp-smiley" /> <a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/">Help Test WordPress 6.2</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f5fa.png" alt="🗺" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f916.png" alt="🤖" class="wp-smiley" /> <a href="https://make.wordpress.org/plugins/2023/03/21/use-of-code-generators-must-remain-gpl-compatible/">Use of Code Generators Must Remain GPL Compatible</a></p></div></div></div>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_b57166-6e"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="h-news"><a href="https://wordpress.org/news">News</a></h2>



<ul>
<li><a href="https://wordpress.org/news/2023/03/introducing-the-wordpress-developer-blog/">Introducing the WordPress Developer Blog</a></li>



<li><a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-3/">WordPress 6.2 Release Candidate 3</a></li>
</ul>



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



<div class="is-layout-flex wp-container-11 wp-block-columns">
<div class="is-layout-flow wp-block-column">
<h2 id="h-central"><a href="https://central.wordcamp.org">Central</a></h2>



<ul>
<li><a href="https://central.wordcamp.org/news/2023/03/wordcamp-buffalo-2023/">WordCamp Buffalo 2023</a></li>



<li><a href="https://central.wordcamp.org/news/2023/03/wordcamp-entebbe-2023-an-amazing-recap/">WordCamp Entebbe 2023: An Amazing Recap</a></li>



<li><a href="https://central.wordcamp.org/news/2023/02/get-your-tickets-for-wordcamp-kerala-2023-on-march-25th/">Get your tickets for WordCamp Kerala 2023 on March 25th!</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/community/2023/03/23/recap-of-contributor-working-group-inaugural-mentorship-chat-on-march-20-2023/">Recap of Contributor Working Group Inaugural Mentorship Chat on March 20, 2023</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/21/meetup-organizer-newsletter-march-2023/">Meetup Organizer Newsletter: March 2023</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/21/community-team-goals-for-2023-chat-session/">Community Team Goals for 2023 :&nbsp;Chat session</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/20/contributor-working-group-mentorship-kick-off-chat-agenda-march-20th-1200-utc-emea-and-2100-utc-amer/">Contributor Working Group: Mentorship Kick-off chat Agenda | March 20th 12:00 UTC (EMEA) and 21:00 UTC (AMER)</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/17/community-team-goals-for-2023-next-step/">Community Team Goals for 2023 : Next Step</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/21/a-week-in-core-march-20-2023/">A Week in Core – March 20, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/22/whats-new-in-gutenberg-15-4-22-march/">What’s new in Gutenberg 15.4 (22 March)</a></li>
</ul>



<h3 id="h-wordpress-6-2">WordPress 6.2</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-day-process/">WordPress 6.2 Release Day Process</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/23/wordpress-6-2-release-candidate-4/">WordPress 6.2 Release Candidate 4</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/14/fyi-navigation-section-of-new-site-editor-experienced-removed-for-6-2-rc-2/">FYI: Navigation section of new Site Editor experienced removed for 6.2 RC 2</a></li>



<li><a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-1/">WordPress 6.2 Release Candidate 1</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/14/wordpress-6-2-translation-status-march-14-2023/">WordPress 6.2 Translation Status (March 14, 2023)</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/04/wordpress-6-2-ready-to-be-translated/">WordPress 6.2 ready to be translated</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</a>
<ul>
<li><a href="https://make.wordpress.org/core/2023/03/08/requests-library-upgraded-to-2-0-5-in-wordpress-6-2/">Requests library upgraded to 2.0.5 in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/patterns-api-expanded-to-include-template_types-property/">Patterns API expanded to include template_types property</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introduction-of-block-inspector-tabs/">Introduction of Block Inspector Tabs</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/shadows-in-global-styles-with-wordpress-6-2/">Shadows in Global Styles with WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introducing-the-html-api-in-wordpress-6-2/">Introducing the HTML API in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/miscellaneous-editor-changes-in-wordpress-6-2/">Miscellaneous Editor changes in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introducing-move_dir-in-wordpress-6-2/">Introducing move_dir() in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/sticky-position-block-support/">Sticky position block support</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/upgrading-to-react-18-and-common-pitfalls-of-concurrent-mode/">Upgrading to React 18 and common pitfalls of concurrent mode</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/add-new-prop-to-serversiderender-component/">Add new prop to ServerSideRender component</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/google-fonts-are-included-locally-in-bundled-themes/">Google Fonts are included locally in bundled themes</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/custom-css-for-global-styles-and-per-block/">Custom CSS for global styles and per block</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/minimum-height-dimensions-block-support/">Minimum height dimensions block support</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/03/editor-components-updates-in-wordpress-6-2/">Editor Components updates in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/03/i18n-improvements-in-6-2/">I18N Improvements in 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/28/custom-settings-wordpress-6-2/">Customize settings for any block in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/19/style-book-preview-of-blocks-in-global-styles/">Style Book preview of blocks in global styles</a></li>



<li><a href="https://make.wordpress.org/core/2022/12/09/update-to-content-only-editing-filter-namespace/">Update to content only editing filter namespace</a></li>
</ul>
</li>



<li><a href="https://make.wordpress.org/core/2023/03/02/wordpress-6-2-accessibility-improvements/">WordPress 6.2 Accessibility Improvements</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/28/wordpress-6-2-beta-4-postponed/">WordPress 6.2 Beta 4 Postponed</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/21/wordpress-6-2-beta-3/">WordPress 6.2 Beta 3</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/21/6-2-live-product-demo/">6.2 Live Product Demo</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/04/phase-2-finale/">Phase 2, Finale</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/03/hallway-hangout-performance-improvements-for-wordpress-6-2/">Hallway Hangout: Performance Improvements for WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/06/roadmap-to-6-2/">Roadmap to 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/18/bug-scrub-schedule-for-6-2/">Bug Scrub Schedule for 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/11/early-bug-scrub-schedule-for-wp-6-2/">Early bug scrub schedule for WP&nbsp;6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/17/wordpress-6-2-planning-roundup/">WordPress 6.2 Planning Roundup</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/21/dev-chat-agenda-wednesday-march-22-2023/">Dev Chat Agenda, Wednesday March 22, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/17/dev-chat-summary-march-15-2023/">Dev chat Summary, March 15, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/21/editor-chat-agenda-march-22nd-2023/">Editor Chat Agenda: March 22nd 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/19/editor-chat-summary-march-15-2023/">Editor chat summary: March 15th, 2023</a></li>
</ul>



<h3 id="h-developer-blog">Developer Blog</h3>



<ul>
<li><a href="https://wordpress.org/news/2023/03/introducing-the-wordpress-developer-blog/">Introducing the WordPress Developer Blog</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/design/2023/03/13/design-share-feb-13-mar-10/">Design Share: Feb 13–Mar 10</a></li>
</ul>



<h2 id="h-do-action"><a href="https://doaction.org/">do_action</a></h2>



<ul>
<li><a href="https://doaction.org/event/ruralhackers/">Rural Hackers Do_Action 2023 in Anceu Spain</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/docs/2023/03/16/agenda-for-docs-team-bi-weekly-meeting-march-21-2023/">Agenda for Docs Team bi-weekly meeting March 21, 2023</a></li>



<li><a href="https://make.wordpress.org/docs/2023/03/15/call-for-volunteers-to-help-with-6-2-end-user-documentation/">Call for volunteers to help with 6.2 end user documentation</a></li>
</ul>
</div>



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



<ul>
<li><a href="https://make.wordpress.org/hosting/2023/03/21/hosting-team-meeting-agenda-2023-03-22/">Hosting Team meeting agenda 2023-03-22</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/marketing/2023/03/14/notes-global-marketing-team-meeting-7-march-2023/">Notes: Global Marketing Team meeting, 7 March 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/meta/2023/03/20/agenda-biweekly-matrix-chat-thu-march-23-2023-10am-utc/">Agenda: Biweekly Matrix Chat – Thu, March 23, 2023 (10AM UTC)</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/openverse/2023/03/20/last-week-openverse-2023-03-13-2023-03-20/">A week in Openverse: 2023-03-13 – 2023-03-20</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/21/performance-chat-summary-21-march-2023/">Performance Chat Summary: 21 March 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/plugins/2023/03/10/advance-notice-of-retirement/">Advance Notice of Retirement</a></li>
</ul>



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



<ul>
<li> <a href="https://make.wordpress.org/polyglots/2023/03/21/agenda-weekly-polyglots-chat-march-22-2023-1300-utc/">Agenda: Weekly Polyglots Chat – March 22, 2023 (07:00 UTC)</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/21/new-translation-project-wp20-wordpress-net/">New translation project: wp20.wordpress.net</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/plugins/2023/03/21/use-of-code-generators-must-remain-gpl-compatible/">Use of Code Generators Must Remain GPL Compatible</a></li>



<li><a href="https://make.wordpress.org/plugins/2023/03/10/advance-notice-of-retirement/">Advance Notice of Retirement</a></li>



<li><a href="https://make.wordpress.org/updates/2023/03/22/plugin-review-team-update-20-march-2023/">Plugin Review Team Update: 20 March 2023</a></li>
</ul>



<h2 id="h-project">Project</h2>



<ul>
<li><a href="https://make.wordpress.org/project/2023/02/06/proposal-creating-a-wordpress-contributor-mentorship-program/">Proposal: Creating a WordPress Contributor Mentorship Program</a></li>



<li><a href="https://make.wordpress.org/project/2023/01/27/discussion-ending-the-eternal-september/">Discussion: Ending the Eternal September</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/support/2023/03/agenda-for-march-23rd-support-meeting-2/">Agenda for March 23rd Support Meeting</a></li>



<li><a href="https://make.wordpress.org/support/2023/03/support-ticket-triage-session-march-29th-2023-at-1600-utc/">Support ticket triage session – March 29th 2023 at 16:00 UTC&nbsp;</a></li>



<li><a href="https://make.wordpress.org/updates/2023/03/16/support-team-meeting-updates-for-march-16th-2/">Support Team Meeting Updates for March 16th</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/test/2023/03/14/hallway-hangout-lets-chat-about-all-things-layout/">Hallway Hangout: Let’s chat about All Things Layout</a></li>



<li><a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/">Help Test WordPress 6.2</a></li>
</ul>



<h2 id="h-theme">Theme</h2>



<ul>
<li><a href="https://make.wordpress.org/themes/2023/03/03/hallway-hangout-community-themes-initiative/">Hallway Hangout: Community Themes Initiative</a></li>
</ul>



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



<ul>
<li> <a href="https://make.wordpress.org/training/2023/03/20/meeting-agenda-for-march-21-2023/">Meeting Agenda for March 21, 2023</a></li>



<li><a href="https://make.wordpress.org/training/2023/03/18/contributor-day-recap-wordcamp-asia-2023/">Contributor Day Recap – WordCamp Asia 2023</a></li>
</ul>



<h3 id="h-tutorials"><a href="https://learn.wordpress.org/tutorials">Tutorials</a></h3>



<ul>
<li><a href="https://learn.wordpress.org/tutorial/what-kind-of-wordpress-theme-do-i-have-classic-block-or-something-else/">What kind of WordPress theme do I have: classic, block, or something else?</a></li>



<li><a href="https://learn.wordpress.org/tutorial/wp-rest-api-custom-fields-authentication-and-testing/">WP REST API – custom fields, authentication, and testing</a></li>



<li><a href="https://learn.wordpress.org/tutorial/displaying-testimonials-on-your-website/">Displaying testimonials on your website</a></li>



<li><a href="https://learn.wordpress.org/tutorial/interacting-with-the-wordpress-rest-api/">Interacting with the WordPress REST API</a></li>
</ul>



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



<ul>
<li><a href="https://learn.wordpress.org/?meeting=exploring-some-of-the-new-6-2-wordpress-features">Exploring some of the new 6.2 WordPress features</a></li>



<li><a href="https://learn.wordpress.org/?meeting=how-to-create-a-website-on-mobile-part-2">How to create a website on mobile (Part 2)</a></li>



<li><a href="https://learn.wordpress.org/?meeting=how-to-join-the-training-teams-welcome-committee-2">How to join the Training Team’s Welcome Committee</a></li>



<li><a href="https://learn.wordpress.org/?meeting=how-to-join-the-training-teams-welcome-committee">How to join the Training Team’s Welcome Committee</a></li>



<li><a href="https://learn.wordpress.org/?meeting=block-themes-and-wordpress-exploring-wordpress-6-2">Block Themes and WordPress: Exploring WordPress 6.2</a></li>



<li><a href="https://learn.wordpress.org/?meeting=how-to-update-a-video-tutorial-for-learn-wordpress-org">How to update a video tutorial for Learn.WordPress.org</a></li>



<li><a href="https://learn.wordpress.org/?meeting=build-a-blog-with-wordpress-6-2-released-today">Build a blog with WordPress 6.2 (Released today!)</a></li>



<li><a href="https://learn.wordpress.org/?meeting=block-themes-and-wordpress-live-stream-11">Block Themes and WordPress: Live Stream</a></li>
</ul>



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



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



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



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



<ul>
<li><a href="https://www.php.net/archive/2023.php#2023-02-14-2">PHP 8.2.3 Released!</a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-02-14-3">PHP 8.1.16 Released!</a></li>



<li><a href="https://262.ecma-international.org/13.0/">TC39</a></li>



<li><a href="https://github.com/composer/composer/releases/tag/2.5.4">Composer 2.5.4</a></li>
</ul>



<p class="has-theme-palette-7-background-color has-background">Thanks for reading our WP dot .org roundup! Each week we are highlighting the news and discussions coming from the good folks making WordPress possible. If you or your company create products or services that use WordPress, you need to be engaged with them and their work. Be sure to share this resource with your product and project managers. <br /><br /><strong>Are you interested in giving back and contributing your time and skills to WordPress.org?</strong> <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://wordpress.org/support/article/contributing-to-wordpress/">Start Here ›</a><br /><br /><strong>Get our weekly WordPress community news digest</strong> — Post Status&#8217; <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — covering the WP/Woo news plus significant writing and podcasts. It&#8217;s also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>



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



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



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



<div class="wp-block-spacer"></div>
<p>This article was published at Post Status — the community for WordPress professionals.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Mar 2023 01:05: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:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:70:"WPTavern: #68 – Chris Reynolds on Why To Use Composer With 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=142848";s:7:"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:84:"https://wptavern.com/podcast/68-chris-reynolds-on-why-to-use-composer-with-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:52027:"Transcript<div>
<p>​[00:00:00] Nathan Wrigley: 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, why you might like to add Composer into your WordPress website workflow.</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 Chris Reynolds. Chris has been working with WordPress for over 15 years. He&#8217;s freelanced, worked with Event Espresso, WebDevStudios, Human Made, and is now at Pantheon as a CMS ecosystem engineer and WordPress technical lead.</p>



<p>He&#8217;s spoken at WordCamps and at OpenWest about all aspects of WordPress.</p>



<p>I suspect that many of the people listening to this podcast are not using Composer in their WordPress workflow, and to Chris this is something that you should think about implementing, and he&#8217;s here to explain why.</p>



<p>Chris starts off by talking about the kinds of projects that he&#8217;s worked on, and how we found WordPress.</p>



<p>We then get into the weeds of what Composer is and the benefits that it brings. It&#8217;s essentially a package management system, and makes it easy to set dependencies for your project and manage them within Composer.</p>



<p>Why would you want to do that though? If you&#8217;re just building brochure websites, then perhaps you&#8217;ve don&#8217;t. But if your project is more complex then this might save you a lot of time.</p>



<p>Chris describes scenarios in which she thinks Composer is a good fit; if you want to add in specific packages and how those packages are managed and updated.</p>



<p>He explains how you can install composer depending on the OS that you&#8217;re working with, and how it structures the files and directories that are created.</p>



<p>Towards the end of the podcast, we talk about how composer can be useful for teams, and Chris&#8217;s use of Composer to keep everyone clear on how the project is structured.</p>



<p>If you&#8217;ve thought about using a package management system, such as composer, 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 Chris Reynolds.</p>



<p>I am joined on the podcast today by Chris Reynolds. Hello, Chris.</p>



<p>[00:03:40] Chris Reynolds: Hi. How&#8217;s it going?</p>



<p>[00:03:41] Nathan Wrigley: Very well, thank you. Chris is on the podcast today to talk to us about something that I confess I know very little about. I&#8217;m going to guess that if you&#8217;re a typical WordPress user, you too may be learning a few new things today. It&#8217;s all going to be about Composer. Before we get into Composer, what it is, how it works, and all of that, wouldn&#8217;t mind Chris if you just orientate our listeners. Give us a little bit of insight into you and your WordPress journey. The companies that you&#8217;ve worked at. The things that you&#8217;ve been involved in and so on. So over to you, Chris, give us your intro.</p>



<p>[00:04:14] Chris Reynolds: Sure. I came across WordPress right around the time that my son was born, which was 2005. The internet was a very different place back then, wasn&#8217;t it? At the time I was looking for something to like share pictures with family and stuff, make a website.</p>



<p>Back then I had what was then referred to as a weblog. It was before that was shortened to blogs, and it was literally a log of things that I did on my website, update changes. And that was all hard coded html. So when I was trying to think of something to share pictures, didn&#8217;t want to do it hard coded. I did do that for a little while and then I decided this was not the thing I wanted to be doing.</p>



<p>So there used to be a website called Hot Scripts. There I found a blogging platform called S Blog, and I was using that for a really long time. But as happens in open source, and actually honestly, as part of what happened in the WordPress history, the original maintainer and author disappeared for a little bit, and it wasn&#8217;t getting updates and I think there were some security things at some point. And I started looking for something else. Had some friends that were talking about WordPress, so I was like, I&#8217;ll try this thing out, and basically haven&#8217;t looked back.</p>



<p>At a certain point after my son was born, I decided that I wanted to quit my regular job, which at the time was doing tech support for grocery stores, and become a freelance web designer. And I did that for a few years. Was familiar with all of those Elance and I don&#8217;t even remember all, like freelancer.net or something. Like all those really old sites to get freelance work. And I worked for a time for a company that&#8217;s actually local, as an outsource, freelance web designer.</p>



<p>There, I believe owner, ran off with all their money or something, and the company closed down. That was a fun story. And then I met the folks from Event Espresso, which is a event management plugin. I met them at WordCamp Salt Lake City because they&#8217;re local, and Salt Lake City is where I live.</p>



<p>And I started working with them initially just doing tech support for them, and then I got into a little bit of development and then I got into a little bit of project management and development. And then I was at a WordCamp, I was speaking. And Pluralsight, which is an online training platform saw me speak and asked me if I wanted to do that sort of thing for them as a, as an author of WordPress related training courses.</p>



<p>So I started doing that while I was working at Event Espresso, and then eventually I quit to focus on that. And did that for about a year or so. And then, I started getting into agency world. So I worked at WebDevStudios for a couple years. And then I went to Human Made. I was there for almost five years. And now I&#8217;m working at Pantheon as a software engineer focusing on WordPress ecosystem things.</p>



<p>So I&#8217;ve been involved in very small projects. I&#8217;ve been involved in very large projects. I&#8217;ve been involved in training. For a while I did some work with the docs team for WordPress documentation. I went to the community summit in San Francisco way back in the day. I&#8217;ve spoken at lots of local WordCamps and OpenWest which is also held locally. And yeah, I&#8217;ve been around for a little while.</p>



<p>[00:07:12] Nathan Wrigley: Yeah, you really have. That&#8217;s an amazingly long history, and going back with WordPress to 2005, you really were right at the forefront. It was just the very beginnings at that point.</p>



<p>[00:07:22] Chris Reynolds: It had been around for a while. If you look at the screenshots of the admin, I wasn&#8217;t the very first iteration, but I think I was maybe the second iteration.</p>



<p>[00:07:31] Nathan Wrigley: Who knew back in 2005 that it would become such an important part of the ecosystem of the web in general. We&#8217;re at the point now where 40 plus percent, I still never quite know what that number means, but it&#8217;s a big number and WordPress is an important part of it.</p>



<p>You say that you&#8217;re a Pantheon at the moment. Just give us a little bit of insight into Pantheon because I confess, I don&#8217;t know a great deal about it. But in my mind I&#8217;m thinking managed WordPress hosting and also managed CMS hosting possibly some other variants as well. Just tell us a little bit about what Pantheons skin in the game is with WordPress.</p>



<p>[00:08:09] Chris Reynolds: You&#8217;re not wrong. We like to call ourselves a web ops platform and we also have kind of coined that web ops phrase, which means that outside of, speaking about Pantheon, it almost doesn&#8217;t exist. What web ops is, it&#8217;s website operations, right? It&#8217;s the things that make your website go.</p>



<p>And what that means practically is that the way that the platform has been built is from the ground up to make sure that teams are able to develop on their websites in a way that is easy to deploy, that is safe, and that is secure. And there&#8217;s all sorts of platform centric things that are part of the workflow.</p>



<p>Pantheon was one of the first, when I was working at WebDev, was the first exposure that I really had to Pantheon. And it was the first platform that I had used that had integrated Git. So you didn&#8217;t have to like, put your stuff on GitHub and then figure out a way to point that deploys to a server somewhere.</p>



<p>It was already built in. And they had been doing that from the very beginning. It also had as part of that there is a dev test live workflow where there&#8217;s separate environments. And this isn&#8217;t uncommon today, but it was one of the first places where you could do that and had it built in.</p>



<p>And then the real sort key feature that I enjoyed as a developer and still enjoy as an employee honestly is the concept of multi devs. Where if you have a branch that you are doing work on and you want to see what that branch would look like. Typically in my agency days, the way that you would handle this is by merging that into dev, and dev becomes really messy, dirty because it&#8217;s got lots of basically untested code, or code that was maybe tested and then rolled back or whatever.</p>



<p>Dev is always nasty, a nasty place to be, and you never deploy from dev. That was always the rule when I was working in agency stuff. Multi devs solve that problem by spinning up an entirely new environment for a branch. So you can create a multi dev off of whatever branch, and then you can test it there, and then you can merge that into dev or whatever.</p>



<p>Your dev branch is clean because it&#8217;s not, you&#8217;re not getting all this test code, experimental code that&#8217;s getting merged in, and then maybe you&#8217;re making some changes or maybe you&#8217;re fixing some stuff, undo some stuff that was from an old merge.</p>



<p>That way you can keep your branches clean. And that&#8217;s a really cool thing that Pantheon does that I&#8217;ve often have wished for when I was working elsewhere, or working on sites that were not hosted on Pantheon. So that&#8217;s one of the things that Pantheon does.</p>



<p>We were talking before we started recording that Pantheon was built by four or five Drupal dudes. So it&#8217;s been a Drupal shop for a very long time. And then maybe about 10 or so years ago, when I became aware of them they started doing WordPress sites. Still built on the same infrastructure that they had built with all the same live workflows, multi dev, all that sort of stuff.</p>



<p>And now we&#8217;re getting into a point where we&#8217;re really trying to build out and optimize for WordPress and find where our gaps are in terms of how the platform has been built and what WordPress specifically needs. And that&#8217;s essentially what my team is involved in.</p>



<p>[00:11:10] Nathan Wrigley: Nice. Yeah, that&#8217;s a real interesting set of things that you talk about there. I didn&#8217;t actually know prior to our conversation we had before we hit record, I didn&#8217;t know that it had all begun on the Drupal side of things, but obviously as WordPress has been in the ascendancy for the last 10 years, it does feel like an important pivot for any company really to make, is to give an experience to WordPress users which is optimized for them.</p>



<p>So, yeah, I&#8217;ll make sure to link in the show notes to anything that we talk about. So if you&#8217;re listening to this, don&#8217;t worry too much, you can go to the WP Tavern website and search for this episode and find all the links there.</p>



<p>Now I&#8217;m going to include quite a few links to what we&#8217;re about to talk about. This is the main thrust of the podcast. It&#8217;s something called Composer. Now, when Chris reached out to me, he mentioned that he wanted to talk about Composer, and I&#8217;ll be really honest, it&#8217;s not something that I&#8217;m familiar with. Chris was very kind to gather a bunch of links, which I&#8217;ve now read, and I&#8217;ve tried to understand.</p>



<p>But I feel that Chris, you are going to school me today, so we&#8217;ll go right back to the basics. The first thing I think to mention is that I don&#8217;t think I know anybody else in the WordPress community who is using Composer with the sort of urgency that you feel it should be being adopted. Most of the people that I know are freelancers, possibly working in an agency and the typical workflow is, you know, if you&#8217;re working with a team, you&#8217;ve got a method of doing that.</p>



<p>But you may well be working on your own website. You may be working for client websites, and you&#8217;re just installing WordPress and a bunch of plugins and themes and so on and so forth. But you&#8217;ve got this bee in your bonnet about Composer and the virtues of it. So let&#8217;s go right back to the beginning. You&#8217;ve probably heard the word Composer before if you&#8217;re listening to this podcast, I imagine. But you may not know what it is. So let&#8217;s go there. What is Composer and why is it in any way important?</p>



<p>[00:12:59] Chris Reynolds: At its base Composer is a package management system. So if you&#8217;re at all familiar with npm which is primarily for JavaScript packages, maybe you&#8217;ve used that for Gutenberg stuff. Maybe you&#8217;ve used that for other JavaScript things. Composer is that thing for PHP packages.</p>



<p>In the past there were things like Pear and PECL, P E C L which did the same sort of thing. Composer does those same-ish things, but better. So at its core, it&#8217;s a package management system, which means it&#8217;s able to do like dependency management. And what that means is, if I have a package, and I have a certain version of a package.</p>



<p>Say I want php code sniffing, I can require that package with Composer. I can make sure that package is up to date. But I can also be specific about the versions of that package that I want to keep. Maybe I want to be on PHP code sniffing version eight or eight dot whatever, but I don&#8217;t want to upgrade to nine yet, or something like that.</p>



<p>I can be specific about my version dependencies, the versioning system that I&#8217;m choosing and be really, either really explicit. I can pin it to a specific release. I could do, I only want the security or patch releases. Or I could be really vague and say, just give me the latest version of whatever.</p>



<p>And Composer has, it&#8217;s based on the idea of semantic versioning. So as long as your packages and WordPress itself doesn&#8217;t use semantic versioning notably, and neither to do a couple other things like Yoast doesn&#8217;t do it, because they&#8217;re using sort of the version numbers don&#8217;t matter school of thought, which kind of breaks the whole thing a little bit.</p>



<p>But if you&#8217;re doing that sort of semantic versioning, which is common throughout just open source software in general, of major dot minor dot patch fr security then you can be really, you can update your things and feel fairly confident that an update is not going to break your thing, break your site. This is perhaps not a myth now as things in WordPress have improved. But the analogy that I like to think of and the reason why feel like Composer is, really important in a WordPress environment is the, I&#8217;ve got a million plugins, maybe not a million, maybe 20.</p>



<p>And I&#8217;ve got a couple themes and I go to my WordPress updates page, or maybe it&#8217;s got auto updates, right? And something happens and an update happens, and I wasn&#8217;t there. Either I bulk updated all of them or it happened in the background. Either way, I&#8217;m not looking at each individual update that I&#8217;m doing, and something breaks. My website white screens, and I have no idea what caused that problem.</p>



<p>I have to go back, I have to undo everything. I have to like, rename my plug-ins folder. I&#8217;m now in panic mode because my production site is white screening. It&#8217;s because of an update. It&#8217;s because something went through that I was either not paying enough attention to, or that happened automatically in the background that broke my site.</p>



<p>Composer, and the way that WordPress is built with allowing, essentially anybody who has access to the plugins page or the updates page to run those updates means that you&#8217;re putting the power and the control over administrating code that is deployed to your site, to whoever has access to those screens, right?</p>



<p>And Composer almost flips that and says, no, we&#8217;re going to give this power to people who actually touched the code. Who maybe are more aware of dependencies and change logs and what an update might mean to a site. And that&#8217;s, sort of where I, see the value of Composer just broadly.</p>



<p>[00:16:21] Nathan Wrigley: Okay. That was, yeah, a really interesting description of how it works. Could you give us the nuts and the bolts of that? In other words, could you unpack what&#8217;s going on? In other words, how is it, how is it installed? How do you get it to bind to the different variations? You mentioned, that you may want it to update to a certain version of such a thing. How do you actually do all of that?</p>



<p>[00:16:44] Chris Reynolds: Composer is software that runs on your computer. You can install basically anywhere. So if you&#8217;re on a Mac, you might use Homebrew to install it. You can run it on a Windows machine, it&#8217;s just a binary. You can run it on a Linux machine, there are packages for it. It&#8217;s essentially cross platforms, so you can use it or you can run it anywhere. Once you have it on your operating system. . Then, we&#8217;ll just use a WordPress, vanilla WordPress site, as an example, if I had a WordPress site maybe I do wget or download the zip file of WordPress and I unzip the package. Okay, that&#8217;s great.</p>



<p>And then I have Composer on my, on my, system so I can run at the command line Composer in it. And that&#8217;s going to start the process of building a Composer dot json file. And then once I have that Composer dot json file, I can start pulling in dependencies. I can say Composer require this thing, this package by this vendor.</p>



<p>And that&#8217;s going to, by default, install my dependencies into a vendor folder. Composer also has a built-in auto loading system. Which means that then in my project, if it&#8217;s a WordPress project, I can have a file. I could throw it into wp-content or a rather wp-config, or I can throw it into a mu plugin that loads the Composer auto loader file so that any packages that are being pulled in through Composer or libraries or whatever, are automatically pulled in because Composers does that, just does it for me.</p>



<p>If I&#8217;m doing WordPress specific things, what I would also need to put in my Composer file is a additional repository for W Packagist. So out of the box, Composer works with a platform, a website, a repository called Packagist, and that&#8217;s where all of the packages live.</p>



<p>If you go to packagist.org today, you can do a search and you can find all sorts of stuff. What you won&#8217;t find is a ton of WordPress related stuff. You&#8217;ll find some. There&#8217;s Human Made has a ton of stuff up there, which I know because I worked there. And I&#8217;ve put a bunch of Pantheon things up there.</p>



<p>There&#8217;s some other people who have been putting stuff on Packagist, just core like, Yoast notably has stuff up there. But it&#8217;s not a WordPress place, it&#8217;s just a general open source place, just like npm again. W Packagist is a bridge between the wordpress.org repository and Composer.</p>



<p>And it is just a mirror of the WordPress plugins and theme repositories for Composer based WordPress projects. So if you add W Packagist as a repository in your Composer json, now I can do Composer require and I can say W Packagist plugin slash WordPress SEO. And that&#8217;ll pull in the latest version of Yoast SEO into my Composer file.</p>



<p>Or I can say Composer require P Packagist theme 2010, and it&#8217;s going to pull in the 2010 theme, of most recent version. That&#8217;s sort of a little bit of the nuts and bolts. That&#8217;s how the Ccomposer json is built. You can also obviously edit this file manually. And then if you want to get into versioning, when you pull that stuff in, it&#8217;s going to give you a sort of its default. Which is typically the major dot minor with a little caret before it, which means that it&#8217;ll accept all minor versions, but it will pause if the version number, the latest version number changes for the major version, right?</p>



<p>if it was like 1.5, 1.6, 1.7, 1.7.2, .3, .5 point whatever, all of those things would get pulled in. But as soon as that 1.7 turns to 2.0, because maybe they made a major release, it&#8217;s not going to get 2.0. It&#8217;s only going to be one point, whatever. Until I change that in my Composer file.</p>



<p>That&#8217;s sort of the default setting. You can be more specific. You can go all the way out to the minor point release and just say, the only updates I ever want to get are these minor or patch releases. To make sure I&#8217;m getting all the security updates or whatever. And not getting minor version updates because maybe I&#8217;m afraid that one of those minor updates might do something bad, or I&#8217;m not, prepared for it yet. Or you can be very vague, and say, just star and give me everything. Or you could say just one, no points, just caret 10 or something. That means that anything above version 10 you&#8217;ll get, doesn&#8217;t matter what the point release is.</p>



<p>And that&#8217;s a way that you can solve for that white screen of death scenario that I talked about earlier. Because if I&#8217;m being specific and explicit about what versions I&#8217;m allowing in my updates then I&#8217;m not going to, I shouldn&#8217;t get to a point where something unexpected happens because of an update that happened that ran on my system.</p>



<p>And in addition to that the way that those updates happen at all is by me or an automation system running a Composer update command. And that&#8217;s the thing that says, go look for things that have changed and pull in any differences based on my defined versioning scheme.</p>



<p>[00:21:21] Nathan Wrigley: So you can get really granular with it. You can instruct it to do whatever you choose to do. I like the example there of pausing at the point release. So instead of going from 1.9 to two automatically it just pauses because it&#8217;s two. But 1.8 to 1.9 was okay to do. Yeah, it&#8217;s really interesting, you can get really granular. And then you run the command to run all of the updates and off it goes.</p>



<p>It sounds like, I could be wrong about this. It sounds like you could broadly break down your description for why to use Composer into three things. I&#8217;m thinking, first of all, security. It sounds like it provides, it&#8217;s not really providing security, but it&#8217;s providing security in the sense that it&#8217;s going to update plugins and themes and whatever else you may have coded yourself. It&#8217;s going to do that without your intervention. It&#8217;s going to run on a schedule and it&#8217;ll just get those things updated for you.</p>



<p>Which as we know in a lot of cases, a lot of WordPress websites, I don&#8217;t think the updates are happening for weeks, possibly months, who knows, maybe even years. So all of that gets taken care of. It also sounds like there&#8217;s a big time save here. If you can get this into your workflow, then you can step away from the dull task of updating things. This will just happen on the fly. You could have a setup in Composer that you reuse over and over again on a sort of typical website that you might set up.</p>



<p>And thereby you can just drag in all of the packages on day one of the project. And within moments you&#8217;re up and running with a typical install that you mentioned. Suck in a particular theme or suck in a particular SEO plugin or what have you. You just run the Composer and all of that is just dragged in and you&#8217;re off to the races. It&#8217;s a quick way to get started.</p>



<p>But also, you didn&#8217;t mention this, but it feels like this is a real win for teams. It feels like a team using this workflow, there may be benefits there. So broadly speaking, I&#8217;m talking about teams, times and security. Is there anything in that? Have I sort of got that about right?</p>



<p>[00:23:16] Chris Reynolds: Yeah, I think so. Obviously there needs to be an automated step somewhere in the process of actually running the Composer update. But beyond that, yes, absolutely. And interestingly one of the things that you touched on maybe accidentally even, the idea of sucking in all of these different packages. When I was at Human Made, I worked on Altis, and Altus is their digital experience platform.</p>



<p>And Altis is built almost entirely on Composer, and lots of cool Composer things happening. Altis itself is what&#8217;s known as a meta package. When you install Altis, the initial Composer file is just linking out to a whole bunch of other projects or packages that it brings in. And those themselves have their dependencies. So each, each of the modules, like the security module or the core module or whatever, each of those has its own set of dependencies that it pulls in. So it, really does just sort of like package a whole bunch of stuff that you get just for free when you initially set up a new site using that.</p>



<p>And that was one of the things that going from the idea of, oh, I&#8217;m just going to throw this Composer file in my WordPress site and call that good. That&#8217;s one of the things that really made me think, oh, actually there&#8217;s, there&#8217;s a lot more to it here. And one of the things that I first was exposed to when I was working at Human Made, and that I&#8217;m actively doing now with what I&#8217;m working on a Pantheon, is the concept of WordPress itself being just a dependency of your project.</p>



<p>And so like with the initial example, I&#8217;ve got a WordPress site. I unzip it. I throw my Composer, json in the root folder. That means that I&#8217;m using Composer probably to manage my plugins and themes, any other packages I might have. But I&#8217;m still using WordPress itself to update itself. Because WordPress is still part of that root directory, and it&#8217;s not part of the Composer structure.</p>



<p>There are projects, there&#8217;s a couple things out there in the world that&#8217;s already, that have been existed, but one, a big thing that&#8217;s been part of the WordPress ecosystem for a while is by the Roots team called Bedrock. And that&#8217;s what we use at Pantheon. And that, among other things, what Bedrock does is it pulls WordPress in so that it can be a dependency. So that can be just another thing in your Composer file that is being versioned.</p>



<p>So again, same rules apply, right? You can say I want everything past six. You can say I want 6.1 dot anything beyond that. Or you can say, I only want 6.1.1, and when the next version comes out, I&#8217;m going to manually make that change so that I can be explicit about my testing process to make sure that I&#8217;m not going to ship broken code.</p>



<p>[00:25:42] Nathan Wrigley: Yeah, that&#8217;s really interesting. The idea that WordPress itself is a package. Okay. I can imagine, given the audience of this podcast, it really does span the whole community, you know. There&#8217;s people in every part of the WordPress ecosystem listening to this. And I can imagine there&#8217;ll be a certain proportion of them who as soon as you start to say things like npm and packages and all of this, and you mentioned, you know, things to do in the command line and da, da, da.</p>



<p>They&#8217;re scratching their heads thinking I don&#8217;t know if this is for me. This all sounds a little bit complicated. So just address that. There&#8217;s a certain level of tech geeky here, I would imagine, But, is it difficult? Is the payback for a, let&#8217;s say a user who is just playing with five or six sites, they&#8217;ve got a few client sites and they can well manage to go in and update the plugins and the themes and all of the bits and pieces that they got set up.</p>



<p>Is there a use case here where, okay, if you&#8217;re sitting on that side of the fence, don&#8217;t even bother? This is probably not needed. Whereas if you&#8217;re on this side and you know you&#8217;ve got more sites than a certain number where it&#8217;s going to be of more use.</p>



<p>[00:26:47] Chris Reynolds: I mean, I definitely think that a lot of the freelancers that I know when I talk to are of the mind that, it&#8217;s just one more thing I need to worry about. And certainly if you are not going to on behalf of your clients go in and make updates, and you&#8217;re handing, once you&#8217;re done at your site, you&#8217;re handing that responsibility off to them.</p>



<p>It&#8217;s going to be too much work for your clients probably. I&#8217;m thinking like small business. I&#8217;m thinking like mom and pop shop. That sort of thing where it&#8217;s really just a user, one person or two people that are running the site. They&#8217;re probably not going to want to do stuff on the command line and you&#8217;re not going to want to train them and that&#8217;s fine.</p>



<p>But I think about when I was at WebDev and we were doing maintenance contracts with clients, and WordPress updates came around and we had basically a person dedicated to reading all of the change logs of every plugin on every site before making any updates. Just to make sure that nothing was going to happen that could potentially break.</p>



<p>And then if there was something that was maybe potentially breaking, they would have to like manually test that themselves on a dev environment, or a local environment or whatever. Just to make sure we&#8217;re not going to run an update and it&#8217;s going to break something. And I think that that process is very tedious and time consuming.</p>



<p>And that process is the process that you&#8217;re saving by using something where you can be more explicit like Composer. And you know that your updates are not going to break anything because the way that you&#8217;ve set up your versioning is the thing that you want it to be, and you feel confident about that structure so that when there are updates, you can go in and yeah, you still need to do testing, you still need to evaluate those things, but you know that you&#8217;re not going to accidentally push something out.</p>



<p>Or you can be at least fairly confident that you&#8217;re not going to accidentally push something out that&#8217;s going to break something. Because breaking things is not a good thing. It&#8217;s not a good feeling to have shipped something when you&#8217;re just doing a maintenance WordPress update release and your client is calling an hour later saying, why is my website white?</p>



<p>[00:28:42] Nathan Wrigley: Yeah, I guess in the case of some of the agencies where you&#8217;ve worked, so Human Made WebDevStudios and so on, it really is enterprise level stuff, and there is no scope for bringing a site down because of a careless update. So the notion that most WordPress users would go in and read the change log before clicking update.</p>



<p>I think that&#8217;s probably not the case. I would imagine most people are fairly cavalier because it&#8217;s their own site, or it&#8217;s a client site that they&#8217;ve got a backup of, and there&#8217;s some mitigation that they&#8217;re, doing all of that. But in the case that you&#8217;ve just outlined where, I don&#8217;t know, maybe these are international brands that we&#8217;ve heard of where the press damage alone in having a website go down for 50 minutes is just unconscionable. You&#8217;ve got to do the background research, and so having these systems in place is truly important.</p>



<p>[00:29:36] Chris Reynolds: Yeah, for sure.</p>



<p>[00:29:36] Nathan Wrigley: In terms of, we&#8217;ve been talking quite a lot about updates. I just wonder what your thoughts are on the, I mean, it&#8217;s not that recent, it&#8217;s several years ago now. The idea that in WordPress you can click a link in the, let&#8217;s say the plugin page. And you can say just go on, update. Whenever something new rolls out, just get on with it and update it. So you can, if you like, trust it. What are your thoughts on that?</p>



<p>[00:29:58] Chris Reynolds: I think it&#8217;s nice for the people that it&#8217;s good for. And I think it&#8217;s definitely helped with WordPress adoption. Because if all I was doing, if I wasn&#8217;t a WordPress developer and all I was doing was being a podcaster and I had a website that was just about my podcast. I&#8217;m not going to care about code. I&#8217;m never going to want to touch the code. I&#8217;m going to want to install WordPress and never look at FTP, or know my server configuration, or care about my database.</p>



<p>None of that. None of that is interesting to me. What I want is I want to plug it in, turn it on, and let it run. And be fairly confident that it is going to continue to run when I have my eyes closed and I&#8217;m not looking at it. So I think that it&#8217;s nice in the sense of creating an ecosystem in which things that you do in WordPress are relatively easy. And the counterpoint to that, I work at Pantheon. Pantheon&#8217;s been involved in the Drupal committee for a very long time.</p>



<p>Talking earlier too about how Drupal has, I think since version eight, integrated Composer into the core of how Drupal works. So sort of the antithesis of this idea of, I&#8217;m going to turn it on and set auto update and then walk away, is the idea of Composerizing everything. So that every change is a code level change.</p>



<p>And what I&#8217;ve found interesting, that I&#8217;ve learned over the last year of being at Pantheon in a difference between the sort of like Drupal ecosystem and WordPress ecosystem, is in WordPress, yeah, there are some people who make it their job to kind of do just general site administration for people.</p>



<p>But it&#8217;s not a huge thing. It&#8217;s like there&#8217;s a couple people that do that sort of thing or they don&#8217;t actually touch the code, but they will do your WordPress updates and that sort of thing for you. In Drupal, there&#8217;s entire agencies where all of what they&#8217;re doing is essentially that, just the maintenance stuff of having a website.</p>



<p>And part of that is because the Drupal admin is a lot more complicated to use, to create sites and pages and views and all sorts of things. It&#8217;s a lot more complicated than the WordPress admin, which I credit to how WordPress is built personally. But the other part of it is the understanding of like, when it&#8217;s okay to update this Drupal module to the next version or that sort of thing. To be aware of what&#8217;s happening on their other sites. And then what combinations work together and that sort of thing.</p>



<p>There&#8217;s a whole ecosystem that it&#8217;s really just essentially website management, which doesn&#8217;t exist in the same way in WordPress. And so that&#8217;s sort of what we&#8217;re talking about. The difference between having really hands-on updates. Making sure that things are safe to do. Or making it so that the people who actually do the content editing or other administration on the site, they don&#8217;t have to worry about the stuff that&#8217;s happening in the background because they know somebody&#8217;s taking care of it, versus having just the software take care of that for itself.</p>



<p>And so I think there&#8217;s a place for it. And I think that the reason why WordPress has grown so much over the last many years is because it&#8217;s embraced this, well, we&#8217;re going to just auto update things and not have people stress over that stuff. But, also like the reason why there&#8217;s so many people that are holding onto Drupal is because they want to make sure, they want to ensure that their site is stable and secure and all of those things. And that those things matter for really big companies. It is that divide, right of more casual users versus the enterprise level stuff.</p>



<p>[00:33:09] Nathan Wrigley: I guess because Composer is essentially nothing to do with WordPress. I mean, you know, you&#8217;ve described a scenario in which WordPress can combine with it, which is very helpful. Updating plugins, themes and so on and so forth. I guess this can reach beyond WordPress. So if you&#8217;ve got something bespoke, unique, you&#8217;ve got a package, which is nothing to do with WordPress. Composer can take care of that as well.</p>



<p>[00:33:34] Chris Reynolds: Yeah, and it&#8217;s really useful when you, so in both npm and Composer, there&#8217;s the concept of dev dependencies. And these are dependencies that will install when you do like a Composer install. But you can also say, you can omit the developer dependencies on your production installs, right?</p>



<p>And that means that you can run things like linting and unit testing and all that sort of stuff, which doesn&#8217;t matter if it&#8217;s on the prod site. But maybe if you&#8217;re going to push it to your dev site or you&#8217;re going to keep it on your local machine. And you can manage all those things really easily with Composer.</p>



<p>There&#8217;s definitely WordPress coding standards and there&#8217;s WordPress suites for unit testing. Those things all exist and you can manage those in WordPress. But essentially, like the core thing, like PHP Code Sniffer is not a WordPress thing. It&#8217;s just a, it&#8217;s just a package that exists in the world. And same thing as PHP unit. It&#8217;s just a thing that exists in the world that we have adopted and embraced and brought it into our ecosystem. So for sure, yeah, there&#8217;s definitely value of using Composer to manage sort of like external things.</p>



<p>[00:34:29] Nathan Wrigley: Okay, given that if you went down this route and you made Composer an integral part of your process. You then to some extent become dependent upon the functioning of Composer for your whole process to work. And so that brings me to the Composer ecosystem.</p>



<p>So we&#8217;re all always talking about how great the WordPress ecosystem is. There&#8217;s a forum for this. There&#8217;s a Slack channel for that. If you want to find something out there&#8217;s ways of learning. Is the same true of Composer? It&#8217;s an open source project. Does it have a thriving community? Does it receive the updates that one would hope? Does it progress in the same way that we hope WordPress does? Does it have that same feel? Are there resources for learning and so on?</p>



<p>[00:35:07] Chris Reynolds: Well, I will say that the website for Composer getcomposer.org, I believe, is really, the documentation&#8217;s really good. At its core, it&#8217;s a pretty simple idea. The documentation&#8217;s pretty self-explanatory. Where it gets hairy is the distinction between a caret versus a squiggly line, in terms of how you&#8217;re going to do your versioning stuff.</p>



<p>Because there&#8217;s a very subtle but specific difference there. And how to pull in different repositories or how to do more complex things. It gets a little bit hairy. But again, the documentation is all there and it&#8217;s all really good and I found it very useful.</p>



<p>And there&#8217;s enough people in the open source ecosystem generally that are using Composer, that it&#8217;s not terribly difficult to find answers to any questions about Composer. Most things you would encounter have probably been done by someone, and there&#8217;s probably some prior art that you can use to base it on.</p>



<p>So I think that it&#8217;s generally pretty good. And packagist is a great place to find stuff. What I will do when I&#8217;m looking for stuff is I&#8217;ll look on packages, even if I&#8217;m looking for a WordPress thing, just to see if, if that developer has pushed their thing to packages before even looking at wordpress.org, or pulling it in from the W Packagist mirror.</p>



<p>That means it&#8217;s getting a little bit, it&#8217;s like one step closer to the source, right? Because all Packagist does really, to submit a package on Packagist, here&#8217;s your pro tip. You have an account obviously, and then you just say, submit a package and you give it a GitHub repository url, and then it just looks at GitHub. And as long as the GitHub project uses releases, even if it doesn&#8217;t really need to, it just looks at the branches. But if it has releases, then you will have those versions. And if it doesn&#8217;t have releases you can still pull that stuff in using a dev prefix or whatever.</p>



<p>That stuff is all self-contained. It all exists. It&#8217;s all well-maintained, all that sort of stuff. That&#8217;s all good. Composer itself does occasionally get updates. The last big thing was sort of a transition from Composer one to Composer two. And that was a little bit of a, there&#8217;s definitely some growing pains in the transition process of going from one version to the next.</p>



<p>And then they threw a wrench recently, not super recently. But they threw a wrench into things a little bit where there is a new thing that goes into your Composer file called allowed plugins. So if it, if it&#8217;s a dependency is calling something else or whatever. You have basically have to give permission to other vendors to, install things on your behalf. So as long as you, if they&#8217;re in the allowed plugins list then those things will get updated, and if they&#8217;re not in the allowed plugins list, then it&#8217;s not going to update those things. And I believe that was for like, security type things.</p>



<p>That did cause a problem with you know, at Pantheon we have a lot of stuff that&#8217;s based on Composer and we don&#8217;t want to introduce merge conflicts. So if we have a Composer file, that is basically the thing that is used to build sites. And then suddenly that Composer file needs to have a new part of the Composer file, and we push that change. It&#8217;s going to cause a merge conflict with everybody&#8217;s repository that didn&#8217;t already have that.</p>



<p>So it&#8217;s a little bit of a headache for us, but for the user it&#8217;s obviously a net win. Those sorts of things give me pause a little bit, as somebody who is now at least partially responsible for, thousands of people running sites that use Composer. But in terms of like individual users and stuff, I think that Composer has a really good thing going and has a good ecosystem around it.</p>



<p>[00:38:16] Nathan Wrigley: Just to give us some insight into how you are using it. Your work at Pantheon and all the other companies that you&#8217;ve mentioned that you&#8217;ve worked at. Is this something that is just typical? This is just part of the process. Everything is built with Composer bolted in. Or is this something that you cherry pick? Okay, this one needs it, this one doesn&#8217;t. Is it basically everywhere, all the time?</p>



<p>[00:38:38] Chris Reynolds: When I was at WebDev, which admittedly is many years ago now, we didn&#8217;t use Composer. We could have benefited from using Composer. And I think they&#8217;re probably using Composer now. I don&#8217;t know that for sure, but based on the types of projects that they&#8217;re doing, and types of things that I see them working on, I think that&#8217;re probably doing it now.</p>



<p>When I was at Human Made, it was just there. Everything that we did had Composer as part of it. And it was a sort of a fundamental part of how projects were built. And obviously like Altis is Composer. It&#8217;s a Composer built thing. It&#8217;s entirely built on top of Composer. One of the things that gives it its stability, but also if you look at the documentation for Altis or things, it&#8217;s always lagging, and is always going to be lagging a little bit behind the latest WordPress release.</p>



<p>And for enterprise, that&#8217;s fine. Because they&#8217;re not concerned about the major or minor point releases. They&#8217;re concerned that their site is secure and it&#8217;s updated and it&#8217;s getting those patch releases. So with each new Altis version that typically aligns with a new WordPress version it sort of, when I was there anyway, the release cycle for Altis followed by a month or so, offset from the last WordPress release, so that they could make sure that the next WordPress version was part of the next Altis version.</p>



<p>[00:39:48] Nathan Wrigley: Okay, so should somebody have been interested in this, you know, their interest has been peaked by everything that you&#8217;ve been saying. Where&#8217;s some good resources? I&#8217;m looking at getcomposer.org and there&#8217;s a get started link right at the top. That seems like it might be a decent place to start. But maybe there&#8217;s more, how to describe it? Maybe there&#8217;s some things which would help a WordPresser as well.</p>



<p>[00:40:13] Chris Reynolds: I definitely would point towards the Roots Bedrock Project as being a really good place if you&#8217;re looking at wanting to have WordPress as built as dependency, I think they&#8217;ve got a really good framework. And at Human Made, we were doing that thing, but we weren&#8217;t using Bedrock. So it would be a little bit more difficult to come up with those ideas and that system and that framework independently. And that&#8217;s one of the things I think that you would get from the Roots ecosystem. So definitely yeah the, just the get Composer to learn about it and to look at the documentation, to dig into it.</p>



<p>And then from a WordPress standpoint specifically, I would definitely look into Bedrock to understand like how that works. And they&#8217;ve got a thriving community as well around that. And, a whole Patreon thing and Discord channel and whatnot, so that you can actually talk to human beings and get some amount of support.</p>



<p>[00:41:02] Nathan Wrigley: Yeah I&#8217;ll make sure to link to everything that you sent in my direction into the show notes. But, if anybody wants to check those out, you can see them on the WP Tavern website. Search for this episode, and you&#8217;ll be able to see all of those links there. If anybody wants to link to you Chris, if anybody&#8217;s been interested in, just think they&#8217;d like bit of a helping hand. They&#8217;d like to understand this a little bit more from, from the horse&#8217;s mouth if you like. Where do we find you?</p>



<p>[00:41:27] Chris Reynolds: Online I&#8217;m jazz sequence most places. Frequently jazz sequence with a three. So j a z z s 3 q u e n c e. That&#8217;s my Twitter handle and Instagram, various other things. I am at @jazzsequence@mstdn.social on Mastodon. And, my website is jazzsequence.com without the three, cause I like to, be confusing. And LinkedIn and places like that. But the Twitters and lately Mastodon, and those sorts of social places where you&#8217;ll probably get my attention.</p>



<p>I&#8217;m also, you know, on the WordPress Core Slack and like I said I live in Salt Lake City so, we haven&#8217;t had very many WordCamps in the last couple years. There&#8217;s some weird pandemic thing happening, but when those things do happen I often will try to visit the things that are, within driving range. I&#8217;m hoping to be at at US in National Harbor this year. So, maybe I&#8217;ll see folks there.</p>



<p>[00:42:16] Nathan Wrigley: Nice. Chris Reynolds, thank you for joining us on the podcast today. I appreciate it.</p>



<p>[00:42:20] Chris Reynolds: Yeah, no worries.</p>
</div>



<p>On the podcast today we have <a href="https://twitter.com/jazzs3quence">Chris Reynolds</a>.</p>



<p>Chris has been working with WordPress for over 15 years. He’s freelanced, worked with Event Espresso, WebDevStudios, Human Made and is now at Pantheon as a CMS Ecosystem engineer, and WordPress technical lead. He’s spoken at WordCamps and at OpenWest about all aspects of WordPress.</p>



<p>I suspect that many of the people listening to this podcast are not using Composer in their WordPress workflow, and to Chris, this is something that you should think about implementing, and he’s here to explain why.</p>



<p>Chris starts off by talking about the kind of projects that he’s worked on, and how he found WordPress.</p>



<p>We then get into the weeds of what Composer is, and the benefits that it brings. It’s essentially a package management system and makes it easy to set dependencies for your project and manage them within Composer.</p>



<p>Why would you want to do that though? If you’re just building brochure websites, then perhaps you don’t, but if your project is more complex, then this might save you a lot of time.</p>



<p>Chris describes scenarios in which he thinks Composer is a good fit; if you want to add in specific packages, and how those packages are managed and updated.</p>



<p>He explains how you can install Composer depending on the OS that you’re working with, and how it structures the files and directories that are created.</p>



<p>Towards the end of the podcast, we talk about how Composer can be useful for teams, and Chris’ use of Composer to keep everyone clear on how the project is structured.</p>



<p>If you’ve thought about using a package management system such as Composer, this episode is for you.</p>



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



<p><a href="https://www.hotscripts.com/">Hot Scripts</a></p>



<p><a href="https://eventespresso.com/">Event Espresso</a></p>



<p><a href="https://www.pluralsight.com/">Pluralsight</a></p>



<p><a href="https://webdevstudios.com/">WebDevStudios</a></p>



<p><a href="https://humanmade.com/">Human Made</a></p>



<p><a href="https://pantheon.io/">Pantheon</a></p>



<p><a href="https://www.npmjs.com/">npm</a></p>



<p><a href="https://brew.sh/">Homebrew</a></p>



<p><a href="https://wpackagist.org/">WordPress Packagist</a></p>



<p><a href="https://packagist.org/">Packagist</a></p>



<p><a href="https://roots.io/bedrock/">Bedrock by the Roots Team</a></p>



<p><a href="https://getcomposer.org/">Composer</a></p>



<p><a href="https://twitter.com/jazzs3quence">Chris&#8217; Twitter account</a></p>



<p><a href="https://mstdn.social/@jazzsequence">Chris&#8217; Mastodon account</a></p>



<p><a href="https://jazzsequence.com/">Chris&#8217; website</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, 22 Mar 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: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:60:"WordPress.org blog: Introducing the WordPress Developer Blog";s:7:"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=14649";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://wordpress.org/news/2023/03/introducing-the-wordpress-developer-blog/";s: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:4659:"<p>With much activity happening in the WordPress development space every day, keeping up-to-date with the latest updates can be challenging. The new <a href="https://developer.wordpress.org/news/">WordPress Developer Blog</a> is a developer-focused resource to help you stay on top of the latest software features, tutorials, and learning materials relevant to the open source project.</p>



<p>This blog is the culmination of a community effort that began last year. Formed by experienced WordPress community members and developers, the <a href="https://developer.wordpress.org/news/about/">editorial group</a> has since worked on a wide range of content already available—from theme and block development tutorials to tips and tricks for leveraging WordPress in the site editing era.</p>



<h2 class="wp-block-heading">A new home for developers</h2>



<p>As a complementary resource to the WordPress documentation, the Developer Blog aims to provide a shared space to stay informed of development-related updates, keep up with ongoing discussions and ideas, and explore cutting-edge use cases.</p>



<p>In other words, <strong>consider it as a central hub for developers and </strong><a href="https://make.wordpress.org/updates/2020/05/01/care-and-influence-a-theory-about-the-wordpress-community/"><strong>extenders</strong></a> of different backgrounds and skill levels to learn with quality content from reliable sources, share knowledge, and drive WordPress development forward.</p>



<p>True to the open source way, the blog will likely evolve. As its editors and readers learn and create more content, it will adapt in response to the needs of community members like you.</p>



<p>Everyone is welcome to chime in on-topic discussions, share ideas or contribute. <a href="https://developer.wordpress.org/news/how-to-contribute/">Learn more about how to get involved</a>.</p>



<h2 class="wp-block-heading">What about the content?</h2>



<p>Content on the WordPress Developer Blog covers many topics, including tutorials on <a href="https://developer.wordpress.org/news/category/themes/">theme development</a>, <a href="https://developer.wordpress.org/news/category/plugins/">plugins</a>, and <a href="https://developer.wordpress.org/news/category/block-development/">block development</a>. You can also expect posts on WordPress APIs, best practices for working with WordPress, updates on upcoming releases, and <a href="https://developer.wordpress.org/news/category/learning/">learning resources</a> for beginners and seasoned developers.</p>



<p>These articles offer a good hint at what&#8217;s already in store for you:</p>



<ul>
<li><a href="https://developer.wordpress.org/news/2022/11/17/demystifying-home-and-posts-templates-in-wordpress-theme-development/">Demystifying home and posts templates in WordPress theme development</a></li>



<li><a href="https://developer.wordpress.org/news/2022/11/creating-themes-from-a-pattern-first-mindset/">Creating themes from a pattern-first mindset</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><a href="https://developer.wordpress.org/news/2023/02/creating-custom-block-styles-in-wordpress-themes/">Creating custom block styles in WordPress themes</a></li>



<li><a href="https://developer.wordpress.org/news/2023/03/whats-new-for-developers-march-2023/">What’s new for developers? (March 2023)</a></li>
</ul>



<h2 class="wp-block-heading">Sounds interesting? </h2>



<p><a href="https://developer.wordpress.org/news/#subscribe">Subscribe to the Developer Blog</a> to keep up with the latest content in the WordPress development space.</p>



<p><em>Props for content and peer review <a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a> <a href="https://profiles.wordpress.org/rmartinezduque/" class="mention"><span class="mentions-prefix">@</span>rmartinezduque</a> <a href="https://profiles.wordpress.org/mburridge/" class="mention"><span class="mentions-prefix">@</span>mburridge</a> <a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a> <a href="https://profiles.wordpress.org/bph/" class="mention"><span class="mentions-prefix">@</span>bph</a>&nbsp;<a href="https://profiles.wordpress.org/greenshady/" class="mention"><span class="mentions-prefix">@</span>greenshady</a> <a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</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, 22 Mar 2023 13:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Chloe Bringmann";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:85:"WPTavern: The Mercantile Reopens with Limited Edition 20th Anniversary WordPress Swag";s:7:"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=142884";s:7:"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:96:"https://wptavern.com/the-mercantile-reopens-with-limited-edition-20th-anniversary-wordpress-swag";s: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:1527:"<img />



<p><a href="https://mercantile.wordpress.org/">The Mercantile</a>, WordPress&#8217; official swag store, was closed for updates but has relaunched with the highly anticipated limited edition <a href="https://mercantile.wordpress.org/product-category/wp20/">20th anniversary swag</a>. </p>



<p>In celebration of the milestone, the store has added an array of keepsakes, including sweatshirts, pennants, a &#8220;Code is Poetry&#8221; t-shirt, stainless steel tumbler, pet bandana, commemorative sticker sheets, and more. What WordPress swag collector can pass up the WP20 Wapuu keychain?</p>



<p>Unlike years past, where the swag store seemed like its own separate site, this relaunch makes the store a  more natural part of the WordPress project&#8217;s website. It runs on WooCommerce and shares the same <a href="https://wptavern.com/wordpress-news-gets-a-new-design">updated design</a> as the rest of WordPress.org with the vibrant blue that has made its way into the 20th anniversary logos. </p>



<p>The limited edition swag is available while supplies last. Unfortunately, international shipping rates are hefty, a complaint the store has received for years. It makes it cost-prohibitive to order a single t-shirt or sweatshirt outside the U.S. when the shipping costs twice as much or more than the product. Hopefully, this year&#8217;s docket of WordCamp events will provide other avenues for distributing 20th anniversary swag to WordPress&#8217; global community through well-stocked pop-up shops.</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, 22 Mar 2023 03:21: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: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:76:"WPTavern: Admin Menu Tree Page View 2.8 Now Supports All Public Post Types ";s:7:"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=142881";s:7:"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/admin-menu-tree-page-view-2-8-now-supports-all-public-post-types";s: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:2211:"<p>The <a href="https://wordpress.org/plugins/admin-menu-tree-page-view/">Admin Menu Tree Page View plugin</a>, which adds a tree-view layout of content in the WordPress admin, has been refactored to support more content types. The plugin is an admin utility similar to <a href="https://wordpress.org/plugins/hierarchy/">Hierarchy</a> or the commercial <a href="https://organizewp.com/">OrganizeWP</a> plugin that reworks the CMS to show content in one place, but it offers a simpler set of features for free with no ads or upsells.  These types of plugins are valuable tools on larger, CMS-heavy WordPress sites.</p>



<p>Previously, the Admin Menu Tree Page View plugin focused on pages, allowing users to better visualize the page hierarchy/tree structure, add pages directly after or inside another post, and easily reorder pages via drag and drop.</p>



<p><a href="https://getbutterfly.com/admin-menu-tree-page-view-2-8-refactoring-update/">Version 2.8</a> adds support for all public post types &#8211; posts, pages, and custom post types, which was a long requested feature. The plugin&#8217;s author, WordPress developer Ciprian Popescu, said adding more post types made the dashboard menu unmanageable and the backend slow, requiring him to update the plugin to us a top-level menu page.</p>



<p>&#8220;The solution here was to move the pages to a top level menu page,&#8221; Popescu said. &#8220;This increased the &#8216;one click away&#8217; feature to &#8216;two clicks away,&#8217; which is not a bad trade-off in my opinion, especially when all public post types are now available in a hierarchical tree layout. Having a separate page now removed the need for collapsing the child <code>&lt;ul></code> elements, as the purpose of this plugin is to quickly see all your pages in a bird’s eye view manner.&#8221;</p>



<img />



<p>Version 2.8 also removes some redundant features, cookies, and JavaScript resources, as the expand/collapse functionality is no longer necessary. Next on the roadmap for future releases Popescu is working on adding caching for post types, removing the jQuery and jQueryUI dependency, and improving dragging and dropping to work inside child elements. </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, 21 Mar 2023 23:10: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:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:53:"WordPress.org blog: WordPress 6.2 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=14685";s:7:"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/03/wordpress-6-2-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:4880:"<p>It’s the final countdown: the third (and last) scheduled <a href="https://make.wordpress.org/core/handbook/glossary/#release-candidate">release candidate</a> (RC3) for WordPress 6.2 is ready! </p>



<p>The WordPress 6.2 release is scheduled for March 28, 2023—just one week away! Now is your last opportunity to test it before the general release.&nbsp;</p>



<p>Just tuning in now? Catch up on the featured highlights, and dig into more 6.2 details in the <a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-1/">WordPress 6.2 RC1 release announcement</a>.</p>



<p>Thanks to all the Beta and RC testers who have assisted in this release. Since <a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-2/">RC2</a> was released on March 14, there have been about 21 issues resolved in <a href="https://core.trac.wordpress.org/query?status=accepted&status=closed&changetime=03%2F15%2F2023..03%2F21%2F2023&milestone=6.2&col=id&col=summary&col=milestone&col=owner&col=type&col=priority&order=id">Trac</a> and <a href="https://github.com/WordPress/gutenberg/commits/wp/6.2">GitHub</a>.</p>



<p>Your feedback and help in filing bug reports keep the WordPress experience stable, smooth, and delightful. It’s critical work and a great way to contribute to the project.&nbsp;</p>



<h2 class="wp-block-heading">How to install RC3 for testing</h2>



<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 is recommended that you test RC3 on a test server and site.&nbsp;</p>



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



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



<p><strong>Option 2</strong>: Direct download the <a href="https://wordpress.org/wordpress-6.2-RC3.zip">RC3 version (zip)</a>.</p>



<p><strong>Option 3</strong>: Use the following WP-CLI command:</p>



<p><code>wp core update --version=6.2-RC3</code></p>



<h2 class="wp-block-heading">A shout out to plugin and theme developers</h2>



<p>Your products are the reason WordPress does so many things for more people across the world. As you test your latest versions against RC3, make sure you update the “<em>Tested up to”</em> version in your plugin’s readme file to 6.2. If you find compatibility problems, please post detailed information to the <a href="https://wordpress.org/support/forum/alphabeta/">support forums</a>.</p>



<p>Check out the <a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</a> for more details about the major changes in this release.</p>



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



<p>Do you speak a language other than English? <a href="https://translate.wordpress.org/projects/wp/dev">Help translate WordPress into more than 100 languages.</a>&nbsp;</p>



<h2 class="wp-block-heading">Keep WordPress bug-free—help with testing</h2>



<p>Without your testing support, hitting important product milestones would be a much bigger challenge. It’s also a meaningful way to contribute to the project. If you’re new to testing, or it’s been a while, <a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/">this detailed guide</a> can help you get started.&nbsp;</p>



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



<h2 class="wp-block-heading">Release the haiku</h2>



<p>Wow, we’re oh so close<br />Test, test. Get it out the door.<br />Please no RC 4.</p>



<p class="has-text-align-right"><em>Thank you to the following contributors for collaborating on this post: <a href="https://profiles.wordpress.org/laurlittle/" class="mention"><span class="mentions-prefix">@</span>laurlittle</a> <a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a> <a href="https://profiles.wordpress.org/audrasjb/" class="mention"><span class="mentions-prefix">@</span>audrasjb</a> <a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a> <a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</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, 21 Mar 2023 17:43: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:16:"Jonathan Pantani";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:82:"Do The Woo Community: Building Community and Employee Engagement with James Giroux";s:7:"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=74641";s:7:"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:63:"https://dothewoo.io/building-community-and-employee-engagement/";s: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:421:"<p>James Giroux from TeamWP joins us to talk about life as a community manager and building employee engagement with TeamWP.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/building-community-and-employee-engagement/">Building Community and Employee Engagement with James Giroux</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 21 Mar 2023 10: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: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:69:"Akismet: Version 5.1 of the Akismet WordPress Plugin is Now Available";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"http://blog.akismet.com/?p=2453";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:97:"https://blog.akismet.com/2023/03/20/version-5-1-of-the-akismet-wordpress-plugin-is-now-available/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:724:"<p>Version 5.1 of <a href="http://wordpress.org/plugins/akismet/">the Akismet plugin for WordPress</a> is now available. This update contains the following improvements:</p>



<ul>
<li>We removed some unnecessary limit notices from /wp-admin/ pages.</li>



<li>We&#8217;re now using post taxonomies to improve spam detection.</li>



<li>In order to avoid inadvertent exposure, API keys are no longer used in the stats iframe URLs.</li>
</ul>



<p>To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in <a href="http://wordpress.org/plugins/akismet/">the WordPress plugins directory</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 20 Mar 2023 19:37:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Christopher Finke";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:164:"WPTavern: CloudFest Hackathon 2023 Kickstarts Innovative WordPress Projects: VS Code Extension for In-Browser Development, WapuuGotchi Gamification Plugin, and More";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=142851";s:7:"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:172:"https://wptavern.com/cloudfest-hackathon-2023-kickstarts-innovative-wordpress-projects-vs-code-extension-for-in-browser-development-wapuugotchi-gamification-plugin-and-more";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:9378:"<p>More than 6,000 people are attending <a href="https://www.cloudfest.com/">CloudFest</a> in Europa-Park, Germany, this week. A strong contingent of WordPress developers and contributors are among them. During the <a href="https://www.cloudfest.com/hackathon">Hackathon</a> portion of the event, web professionals gather for a friendly competition, tackling problems for existing not-for-profit, OSS projects, creating solutions with a concentrated effort at a quicker pace than remote collaboration usually allows.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">WordPress running in VS Code!!! <a href="https://twitter.com/hashtag/CFHack2023?src=hash&ref_src=twsrc%5Etfw">#CFHack2023</a> <a href="https://t.co/qKQeQBZClW">pic.twitter.com/qKQeQBZClW</a></p>&mdash; daniel (@dbchhbr) <a href="https://twitter.com/dbchhbr/status/1637491441453735937?ref_src=twsrc%5Etfw">March 19, 2023</a></blockquote>
</div>



<p>Several WordPress-related projects have been put into action at the Hackathon, including the following: </p>



<ul>
<li><a href="https://www.cloudfest.com/mariadb-health-checks-in-wordpress">MariaDB Health Checks in WordPress</a></li>



<li><a href="https://www.cloudfest.com/privacy-focused-web-analytics-plugin">Statify: Privacy-Focused Web Analytics Plugin</a></li>



<li><a href="https://www.cloudfest.com/a-search-engine-for-wordpress-developers">docs_dangit: A search engine for WordPress developers</a></li>



<li><a href="https://www.cloudfest.com/wapuugotchi">Wapuugotchi</a></li>



<li><a href="https://www.cloudfest.com/wappspector-cli-utility-to-scan-a-hosting-server-to-identify-used-cms-ecommerce-top-frameworks-used-in-the-websites">Wappspector</a></li>



<li><a href="https://www.cloudfest.com/eco-mode-reduce-outgoing-network-traffic-of-your-wordpress-server">Eco-mode – reduce outgoing network traffic of your WordPress server</a></li>



<li><a href="https://www.cloudfest.com/wordpress-runtime-vulnerability-analysis">WordPress Runtime Vulnerability Analysis</a></li>



<li><a href="https://www.cloudfest.com/in-browser-wordpress-development-environment">In-browser WordPress development environment</a></li>
</ul>



<p>Automattic engineer Daniel Bachhuber <a href="https://developer.wordpress.com/2023/03/20/cfhack2023-wordpress-in-vs-code/">published</a> a preview of the in-browser WordPress development environment enabled by an experimental VS Code extension that uses <a href="https://webassembly.org/">WebAssembly</a> to run WordPress entirely in the browser.</p>



<p>&#8220;Forget spending hours setting up a local development environment at your next Contributor Day,&#8221; Bachhuber said. &#8220;Simply install the <a href="https://marketplace.visualstudio.com/items?itemName=WordPressPlayground.wordpress-playground">WordPress Playground VS Code extension</a>, run &#8216;Launch WordPress Playground&#8217; from the command launcher, and you’ll have a <s>fully</s> mostly functional WordPress installation right inside your editor.&#8221;</p>



<p>Bachhuber emphasized that the extension was built for demonstration purposes but is <a href="https://github.com/danielbachhuber/wordpress-playground-vscode">available on GitHub</a> for anyone who wants to contribute or report bugs. A more in-depth tour of the extension is available on <a href="https://developer.wordpress.com/2023/03/20/cfhack2023-wordpress-in-vs-code/">Automattic&#8217;s developer blog</a>.</p>



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

</div>



<p>In addition to the VS code previewer for WordPress plugins, the Hackathon team working with WordPress Playground is also <a href="https://twitter.com/adamzielin/status/1637457845141512194">experimenting</a> with using the block editor in the browser and working with the Terminal and PHP, wp-cli, and PHPUnit &#8211; all in the browser. </p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Our <a href="https://twitter.com/hashtag/CFHack2023?src=hash&ref_src=twsrc%5Etfw">#CFHack2023</a> Project 1: WordPress code editor, cli, and preview in the browser — with offline mode! <a href="https://twitter.com/hashtag/CFHack?src=hash&ref_src=twsrc%5Etfw">#CFHack</a> <a href="https://t.co/KdFzwq9IaJ">https://t.co/KdFzwq9IaJ</a></p>&mdash; Adam Zieliński (@adamzielin) <a href="https://twitter.com/adamzielin/status/1637769196128858114?ref_src=twsrc%5Etfw">March 20, 2023</a></blockquote>
</div>



<p>The WapuuGotchi project, which aims to gamify WordPress with a customizable Wapuu, notifications, and rewards, has its own <a href="https://twitter.com/wapuugotchi">Twitter account</a> and <a href="https://wapuugotchi.com/">website</a> where those interested can follow along with their progress.</p>



<img />image credit: <a href="https://wapuugotchi.com/hackathon-wrap-up-unveiling-the-future-of-wordpress">WapuuGotchi Hackathon Wrap-Up</a>



<p>&#8220;The audience was captivated as we demonstrated the customizable Wapuu assistant, which can be tailored to suit individual preferences by selecting unique outfits and accessories,&#8221; WapuuGotchi design contributor Dennis Hipp said.</p>



<p>&#8220;We also highlighted WapuuGotchi’s backend interaction capabilities, showing how it can guide users through updates, provide helpful tips, and offer reminders for important tasks. The presentation concluded with an invitation for Plugin authors to collaborate with us and integrate their Plugins into the WapuuGotchi ecosystem.&#8221;</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f469-1f3fb-200d-1f4bb.png" alt="👩🏻‍💻" class="wp-smiley" /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2728.png" alt="✨" class="wp-smiley" /> Day 3, the last day and the final sprint! Everyone in the <a href="https://twitter.com/hashtag/WapuuGotchi?src=hash&ref_src=twsrc%5Etfw">#WapuuGotchi</a> team is working hand in hand to complete the final steps before the presentation.  We are looking forward to sharing our results with you! <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2728.png" alt="✨" class="wp-smiley" /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f468-1f3fc-200d-1f4bb.png" alt="👨🏼‍💻" class="wp-smiley" /> <a href="https://twitter.com/hashtag/CFHack2023?src=hash&ref_src=twsrc%5Etfw">#CFHack2023</a> <a href="https://twitter.com/aprox7?ref_src=twsrc%5Etfw">@aprox7</a> <a href="https://twitter.com/joomla?ref_src=twsrc%5Etfw">@Joomla</a> <a href="https://twitter.com/TinaTO?ref_src=twsrc%5Etfw">@TinaTO</a> <a href="https://twitter.com/mpmike?ref_src=twsrc%5Etfw">@mpmike</a> <a href="https://twitter.com/cloudfest?ref_src=twsrc%5Etfw">@cloudfest</a> <a href="https://t.co/9VZy1KSAKg">pic.twitter.com/9VZy1KSAKg</a></p>&mdash; WapuuGotchi (@wapuugotchi) <a href="https://twitter.com/wapuugotchi/status/1637748796938506240?ref_src=twsrc%5Etfw">March 20, 2023</a></blockquote>
</div>



<p>The Wappspector project, which aims to create a CLI utility to analyze the file structure of a web hosting server and identify the frameworks and CMS used in the websites hosted on it, made significant progress during the Hackathon. The app added seven more CMS identifiers and will soon be ready for testing on control panels. The app focuses on CMS and e-commerce applications but will also have an extendable mechanism allowing hosting providers to customize it to suit their needs.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Seven more CMS identifiers added to <a href="https://twitter.com/hashtag/WappSpector?src=hash&ref_src=twsrc%5Etfw">#WappSpector</a> <a href="https://twitter.com/cloudfest?ref_src=twsrc%5Etfw">@Cloudfest</a> <a href="https://twitter.com/hashtag/CFHACK?src=hash&ref_src=twsrc%5Etfw">#CFHACK</a> <a href="https://twitter.com/hashtag/CFHACK2023?src=hash&ref_src=twsrc%5Etfw">#CFHACK2023</a> &#8211; in addition to <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a>, <a href="https://twitter.com/hashtag/Joomla?src=hash&ref_src=twsrc%5Etfw">#Joomla</a>, <a href="https://twitter.com/hashtag/Drupal?src=hash&ref_src=twsrc%5Etfw">#Drupal</a>, <a href="https://twitter.com/hashtag/Prestashop?src=hash&ref_src=twsrc%5Etfw">#Prestashop</a> &amp; <a href="https://twitter.com/hashtag/TYPO3?src=hash&ref_src=twsrc%5Etfw">#TYPO3</a>, <a href="https://twitter.com/hashtag/Composer?src=hash&ref_src=twsrc%5Etfw">#Composer</a> and <a href="https://twitter.com/hashtag/Laravel?src=hash&ref_src=twsrc%5Etfw">#Laravel</a> are now identifiable. Our app will soon be ready for testing on control panels. <a href="https://t.co/f26qLFiEqV">pic.twitter.com/f26qLFiEqV</a></p>&mdash; cPanel (@cPanel) <a href="https://twitter.com/cPanel/status/1637399014873202688?ref_src=twsrc%5Etfw">March 19, 2023</a></blockquote>
</div>



<p>CloudFest 2023 added a new <a href="https://www.cloudfest.com/wordpress-day">WordPress Day</a>, dedicated to helping internet infrastructure professionals learn more about WordPress&#8217;s footprint and ecosystem, and hear from some of the top WordPress plugin developers and security experts. The event was held earlier today on March 20, and featured 12 sessions on WordPress.</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, 20 Mar 2023 18:59:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:105:"Gutenberg Times: OpenAI Block, WooCommerce 7.5, Patterns and Flexible Table Block —Weekend Edition #247";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=23605";s:7:"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:110:"https://gutenbergtimes.com/openai-block-woocommerce-7-5-patterns-and-flexible-table-block-weekend-edition-247/";s: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:17466:"<p>Howdy, </p>



<p>Containers are on my mind. In one of those, our household will be shipped next week. 🚚 We will be AirBnB-ing for a few weeks. Exciting times. </p>



<p>I need to sort through some paperwork and create the inventory for the insurance. Sorry for the short intro, today. </p>



<p>Wish me luck! </p>



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




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



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




<p><strong>Josepha Haden Chomphosy</strong> joined <strong>DocPop</strong> on the <em>Torque Social Hour</em>. They discussed WordPress 20-year Anniversary celebration, WordPress 6.2 &#8211; Phase 2 to Phase 3. <a href="https://www.youtube.com/watch?v=9T0LgQP7M4A"><strong>Torque Social Hour: Preparing for WP20 Celebrations</strong></a>. In this episode, Haden Chomphosy  told us about the upcoming plans for WordPress’s 20th Anniversary. They also talked about WP version 6.2, the recent acquisition of the ActivityPub plugin for WordPress, and Plugin Madness 2023.</p>



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



<p>It&#8217;s release candidate week in WordPress land: <a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-2/"><strong>WordPress 6.2 RC 2</strong></a> was released on March 14, 2023, and <a href="https://github.com/WordPress/gutenberg/releases/tag/v15.4.0-rc.1"><strong>Gutenberg 15.4 RC 1</strong></a> is also available for testing. </p>



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



<p>WordPress 6.2 comes with a browse mode of the Site Editor. This includes a black left menu bar that blends in and out depending on if you are editing a template or browsing the menu. Until RC 2, &#8220;Navigation&#8221; was one of the menu items on the left admin menu, it was, however, pulled before this week&#8217;s RC 2. <strong>Anne McCarthy</strong> summarized the discussion around this issue in their post: <a href="https://make.wordpress.org/core/2023/03/14/fyi-navigation-section-of-new-site-editor-experienced-removed-for-6-2-rc-2/"><strong>FYI: Navigation section of new Site Editor experienced removed for 6.2 RC 2</strong></a> and shared also the list of issues this feature has. Each one a minor item in the sum it wasn&#8217;t up to the quality contributors aimed for. </p>



<div class="wp-block-group has-light-background-background-color has-background is-layout-flow wp-block-group-is-layout-flow"><div class="wp-block-group__inner-container">
<p><strong>🎙️ </strong> New episode:  <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-80-wordpress-6-2-preview-gutenberg-15-2-and-15-3/">Gutenberg Changelog #80 – WordPress 6.2 Preview, Gutenberg 15.2 and 15.3</a> with Birgit Pauli-Haack and special guest Rich Tabor  </p>
</div></div>



<p>WPEngine&#8217;s one-day virtual developer conference DE{CODE} will take place next week <strong>March 21 through 23rd, 2023. DE{CODE} </strong>will be broadcast in three global time zones and anticipates over 5,000 attendees in its fourth year, launching in 2020. <strong>Matt Mullenweg</strong> and <strong>Matias Ventura</strong> will discuss the future of WordPress and the rapid innovations in the block editor relied upon by millions of WordPress developers worldwide. It&#8217;s also part of the 20-year anniversary celebration of WordPress . Have a look at the <a href="https://events.wpengine.com/event/b1c1e30f-2c73-4abb-a609-52afaed68717/websitePage:289e81f7-3e30-49de-9510-696ad303d192"><strong>schedule of all the great sessions at DE{CODE} 2023</strong></a></p>



<img />



<p><strong>Anne McCarthy</strong> was a guest of <strong>Rob Cairns</strong> for the latest episode. They talk All about 6.2 on <a href="https://stunningdigitalmarketing.com/episode-307-wordpress-6-2-with-anne-mccarthy/">Stunning Digital Marketing</a> podcast. Highlights of the show: </p>



<ul>
<li>What is coming in WordPress 6.2 .</li>



<li>&nbsp;The coolest features in WordPress 6.2</li>



<li>&nbsp;When are we going to update the WordPress Admin Dashboard?</li>



<li>&nbsp;When are we going to fix the Media Library?</li>
</ul>



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



<p><strong>Jamie Marsland</strong>, shows off the <a href="https://www.youtube.com/watch?v=ERIz3diT9Sk"><strong>Side Editor and Block Themes</strong></a> again via YouTube. He uses both to rebuild Austin Kleon&#8217;s website, using the newest WordPress version.  <br /><em>Austin Kleon is the New York Times bestselling author of a trilogy of illustrated books about creativity in the digital age: Steal Like An Artist, Show Your Work!, and Keep Going.</em></p>



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



<p><strong><a href="https://developer.woocommerce.com/2023/03/14/woocommerce-7-5-released/">WooCommerce 7.5</a></strong> has been released, and the post highlights that Woo Blocks are ready for the new feature of the StyleBook coming in WordPress 6.2, Blocks have been rewritten, so users can use the core design tools for changing the look and feel, the block can be easier styled by block themes, and new blocks to manage the store can now be found in the inserter of the block editor. </p>



<p><strong>Sarah Gooding</strong> of WPTavern has more details: <a href="https://wptavern.com/woocommerce-7-5-0-introduces-3-new-blocks-expands-support-for-global-styles"><strong>WooCommerce 7.5.0 Introduces 3 New Blocks, Expands Support for Global Styles</strong></a></p>



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



<p>Learn.WordPress Tutorial: <a href="https://learn.wordpress.org/tutorial/displaying-testimonials-on-your-website/"><strong>Displaying testimonials on your website</strong></a> with<strong> Wes Theron</strong>. This tutorial will look at adding a testimonial pattern and installing a new block from the Block Directory to your site.</p>



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



<p><strong><a href="https://twitter.com/tetsuaki_hamano">Aki Hamano</a></strong>, a Gutenberg contributor from Japan, released a new version of his <a href="https://wordpress.org/plugins/flexible-table-block/"><strong>Flexible Table Block plugin</strong></a>, with the main changes </p>



<ul>
<li>Tested on WordPress6.2</li>



<li>Redesigned global settings modal </li>



<li>apply stripe color to tbody only </li>



<li>Preserve rowspan/colspan when converting to/from core table blocks </li>
</ul>



<p></p>



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



<p><strong>Mike McAliste</strong>r acclaims: <a href="https://olliewp.com/patterns-are-gonna-be-a-game-changer-for-wordpress/"><strong>Patterns are gonna be a game changer for WordPress</strong></a>, and he tells you why, after a recap of the genesis of Block Patterns:  &#8221;&nbsp;instead of designing a page from scratch, WordPress creators can now lean on patterns to quickly prototype or design their full website in the new WordPress Site Editor with little or no code involved.&#8221; McAlister also has concrete vision on how patterns could be a bit more intelligent: </p>



<ul>
<li>Go global: change once, update to all places where patterns were added.</li>



<li>Pattern locking features</li>



<li>Light/dark version of the same pattern.</li>
</ul>



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



<p>If that topic interests you more, <strong>Justin Tadlock</strong> wrote a post on the Developer Blog, introducing <a href="https://developer.wordpress.org/news/2022/11/creating-themes-from-a-pattern-first-mindset/"><strong>Creating Themes from a Pattern-first mindset</strong></a></p>



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



<p><strong>Ganesh Dahal</strong>&nbsp;wrote on CSS Tricks on <a href="https://css-tricks.com/managing-fonts-in-wordpress-block-themes/"><strong>Managing Fonts in WordPress Block Themes</strong></a>. &#8220;Block themes can indeed use Google Fonts, but the process for registering them is way different from what you might have done before in classic themes.&#8221; he explained. </p>



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




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




<p>On the WordPress Developer Blog, <strong>Daisy Olse</strong>n takes you along when she shows you  <a href="https://developer.wordpress.org/news/2023/03/block-theme-templates-the-easy-way-to-build-an-elegant-grid-of-posts/"><strong>Block theme templates: the easy way to build an elegant grid of posts</strong></a>. <em>&#8220;WordPress block themes let you lay out your home page in countless ways, with endless flexibility. To get you started and show you just a few of the possibilities, this tutorial will help you build a magazine-style home page that shows several recent posts and then a traditional post list for inner pages.</em>&#8220;Olsen summarized. Olsen also live-streams regularly <a href="httpa://twitch.com/daisyonwp">on Twitch</a>: Next event: Friday, March 31, 2023 7:30 AM to 9:00 AM Topic: <a href="http://clicks.meetup.com/ls/click?upn=XbaZ37larFA-2FuV5MohrYpdrra25MtI4CzodbRR1Rd1lcKVfFkaiAkMoxUvY-2FRvTYasrl05OpUEx72RVyvunbnfpl8aYBoogyprZFTIpUpo22NL-2FoQHUOrtYIfxI6PjJVQFCmp-2B2S-2Fq4FTLYKBM-2BmtFcLYWugMTX9zP0bhY6zZ3DLzmpF0KtJjZgT2sqIJWMLmpmnqQgZd0lq2xEArTmYCpw3GjujFvusA8j5HeNyemAoWMY12BDWC9aKbhEdL43wbmWxsdhlCn-2BVgCcoZjW3jRMKI9i3RSODpkr-2BEywOkyA-3DTYl__J40Cm482JAfcu64pauD5epBU-2Bh0Rd-2FPWHzdxWXz1rewkAa1qNT6zJlNeHNYZFAj0LnD-2Bb1AhQQSz4XVimu5ikL4v4OY5PmVLKfMIPDvE6BMosM9bkdqfAXKOIvxARLwcEaswvLfrjbcOYXZ6C3kRPGZOIfCYy917Fg5QeBskFMUyf3q4tnOMOPPjOqOaBMCUzD1FgXVOIMNE3e3r-2BhQukqfMyS-2FyScFE4d0bJew1heuXhcM4totKIVcUclpyh59sJALeLnEd7rm1-2Fqjh48JlQHN5Mu3Av-2FsH9ygknQvsc5x0A0KIrnZTxG3h2GrtpO7CVUdQl4Bc6wM2zHjt9-2B787S0FNwx7tr-2BI0gnbVhh3msWhB3gwO8L9YvSr-2BK297Bd2xRLzyP5phQS6MLNc8DjP1QvXnZNFPgnkJBi01ij4rj1YPcsSY-2Fo0gaDXyr-2FQVIUGP-2FQRg-2BDysOhbjHIF9IWpTizgKY1H8lY112ok0qu4wmRXXbjeFAqRqDstHdKbn1To22RrqAWiHnuz8gFPcdlUc2AGP-2BiO7jlJY-2BMMFkuaCYYcqV97OLC4u05JDD2KYzbB3loEraPvrnPo83nKJ4w-2B4GQleteGxeO-2BNZkBi5jVzF93Gz-2FQ41-2FqSCjNgHh46QPbQonA1BfYS3KYXiaPoCQTtqTjxDRRvuZOgrx6MeiNm0WMa-2BvS3qV0FFYDI54etDZF01xqafJyfVV0kXDBt7dNp0zsnZNMsTYIVXwErz8HEozy6mQquv99qo2jE-2FsMC7WE" target="_blank" rel="noreferrer noopener">Block Themes and WordPress: Exploring WordPress 6.2</a></p>



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



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



<p>In his latest recording, <strong>Ryan Welcher</strong> wrapped up <a href="https://www.youtube.com/watch?v=88c6z1XEvG0"><strong>building an OpenAI block for WordPress</strong></a>. In a previous edition, Welcher built an OpenAI integrated block that can generate images for use in our content. In this show, he turned it into a plugin that is part of the editor interface and inserted image blocks automatically after uploading the selected image. </p>



<p>If you missed the earlier parts of this series, they are also available on YouTube</p>



<ul>
<li><a href="https://www.youtube.com/watch?v=bQS69SglWOg">Integrating OpenAI with a custom block. Part One</a></li>



<li><a href="https://www.youtube.com/watch?v=gIJwXEXt7xE">Integrating OpenAI with a custom block. Part Two</a></li>
</ul>



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



<p>Using the WordPress REST API is how block editor development interacts with data. <strong>Jonathan Bossenger</strong> created a series of Workshops on how to use the API.</p>



<ul>
<li><a href="https://wordpress.tv/2023/01/13/lets-code-using-the-wordpress-rest-api/"><strong>Using the WP REST API</strong></a>: Learn how to use the WP REST API to interact with existing WordPress data.</li>



<li><a href="https://wordpress.tv/2023/01/20/lets-code-interacting-with-the-wp-rest-api/"><strong>Interacting with the WP REST API</strong></a>: Learn how to interact add and delete data. The tutorial also looks at a useful developer tool for testing endpoints.</li>



<li><a href="https://wordpress.tv/2023/01/27/lets-code-wp-rest-api-updates-custom-fields-and-authentication/"><strong>WP REST API updates, custom fields, and authentication</strong></a>: Learn how to use the REST API and Backbone.js to make update requests, add/update custom fields, and authenticate requests when logged out.&nbsp;</li>



<li><strong><a href="https://wordpress.tv/2023/02/03/lets-code-wp-rest-api-modifying-responses/">WP REST API – modifying responses</a>:</strong> Learn one of the ways to extend the REST API by modifying responses.</li>



<li><a href="https://wordpress.tv/2023/02/10/lets-code-wp-rest-api-custom-routes-and-endpoints/">WP REST API – custom routes and endpoints</a>: Learn how to create custom routes and endpoints and test them with Postman.</li>
</ul>



<p>I also highly recommend watching <strong>K. Adam White</strong>&#8216;s talk at WordCamp Asia on&nbsp;<a href="https://asia.wordcamp.org/2023/session/getting-the-most-out-of-the-rest-api/"><strong>Getting the most out of the REST API</strong></a>. During the talk, White renamed it to&nbsp;<em>“Getting the most out of WordPress when you’re writing Block Editor code”.</em> (<a href="https://www.youtube.com/live/vrDwB7iuHL8?t=2299">Recording</a>)&nbsp;(<a href="https://docs.google.com/presentation/d/1PQVcTzcUP2xRbwjEjqo8VENxU7fiDBtz8U7R4cA0-IE/edit#slide=id.g1f27001dabd_0_8"><strong>Slidedeck</strong></a>)</p>



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




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



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




<p class="has-text-align-right has-small-font-size"><em>Questions? Suggestions? Ideas? Don&#8217;t hesitate to send <a href="mailto:pauli@gutenbergtimes.com">them via email</a> or send me a message on WordPress Slack or Twitter @bph</em>. </p>



<p class="has-text-align-right has-small-font-size">For questions to be answered on the <a href="http://gutenbergtimes.com/podcast">Gutenberg Changelog</a>, send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a></p>



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




<p>Featured Image: &#8220;Container&#8221; by Izabela Reimers is licensed under CC BY-NC-SA 2.0.</p>



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



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



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



<hr class="wp-block-separator has-css-opacity is-style-wide" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 18 Mar 2023 05:33:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Birgit Pauli-Haack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:91:"WPTavern: WordPress Launches Wapuu Coloring Giveaway to Celebrate Upcoming 20th Anniversary";s:7:"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=142834";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://wptavern.com/wordpress-launches-wapuu-coloring-giveaway-to-celebrate-upcoming-20th-anniversary";s: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:2364:"<p>Wapuu lovers who are looking for a relaxing weekend activity will want to check out WordPress&#8217; recently launched <a href="https://wp20.wordpress.net/wapuu-coloring-giveaway-style-your-own-party-wapuu/">Wapuu Coloring Giveaway</a>. The challenge is to style your own 20th anniversary party Wapuu using crayons, markers, colored pencils, pastels, or even digital drawing tools.</p>



<p>Three random entries will be selected (which is why it&#8217;s called a giveaway and not a contest) to receive limited edition swag:</p>



<blockquote class="wp-block-quote">
<p>You have a chance to win one of three WP20 Swag Kits, complete with a variety of unique anniversary goods. From lapel pins to stickers, and some surprise mystery items, they’ll be a memorable collection for this milestone moment in WordPress history. </p>
</blockquote>



<p>Participants will need to download the Wapuu coloring set, which comes in different file types (.pdf, .png, .svg, and .ai). Finished wapuu coloring creations can be shared on Twitter using the <a href="https://twitter.com/hashtag/WapuuWP20">#WapuuWP20</a> hashtag to enter the giveaway. So far there are just a handful of party wapuus that have been submitted via Twitter, but email is another option if you want to send it privately or don&#8217;t have a Twitter account.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Long way from the Himalayan kingdom Bhutan, the land of gross national happiness with a population of 700,000 plus, would like to congratulate WordPress Communities worldwide in advance for our upcoming huge celebration on making it to the 20TH WordPress Anniversary. <a href="https://twitter.com/hashtag/WapuuWP20?src=hash&ref_src=twsrc%5Etfw">#WapuuWP20</a> <a href="https://t.co/Ml1Wz7m8nx">pic.twitter.com/Ml1Wz7m8nx</a></p>&mdash; Ugyen Dorji Organizing #WCAsia (@ugyendzodorji) <a href="https://twitter.com/ugyendzodorji/status/1636280709890576385?ref_src=twsrc%5Etfw">March 16, 2023</a></blockquote>
</div>



<p>Entrants must be 18 years old to win, but the coloring page is fun for kids even if they won&#8217;t have the chance to win swag. WordPress will celebrate its 20th anniversary on May 27, but the deadline to submit wapuu creations is April 17, 2023, at 03:59 UTC. Winners will be contacted via Twitter or email.</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, 17 Mar 2023 21:54:51 +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:39:"WordCamp Central: WordCamp Buffalo 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:39:"https://central.wordcamp.org/?p=3163106";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:64:"https://central.wordcamp.org/news/2023/03/wordcamp-buffalo-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:1802:"<a href="https://profiles.wordpress.org/empireoflight/"><img /></a>WordCamp Buffalo 2023 logo. Design by Ben Dunkle.



<p>Buffalo again will host the region’s WordCamp for bloggers and web designers and developers of all skill levels. Novices are very welcome. WordCamp Buffalo will be held Saturday, May 6, 2023.</p>



<p>Registration opens at 8:00am. Sessions begin at 9 a.m. and continue through 5 p.m. This year’s WordCamp will be held at Ken-Ton Elmwood Commons, 3200 Elmwood Ave Suite 110, Kenmore, NY 14217. Tickets are required in advance.</p>



<p>The $25 ticket cost covers WordCamp Buffalo swag, morning coffee, lunch, and the evenings’s after-party food. Participants are strongly encouraged to bring their laptops or tablets. Ticket purchase and program details are available at <a href="https://buffalo.wordcamp.org/2023">buffalo.wordcamp.org/2023</a>. The capacity for this event is about 120 people, so getting tickets early is advised.</p>



<p>WordCamps are held worldwide, locally run and purposely at a low cost for accessibility to all. WordCamp Buffalo is dedicated to WordPress, blogging and web facility. WordCamps are sponsored by WordPress, the open-source, free, not-for-profit platform for individuals, groups and businesses to build their own blogs and websites. WordPress.org began in 2003. Its administrators call it the “largest self-hosted blogging tool in the world, used on millions of sites and seen by tens of millions of people every day.”</p>



<p>Similar to previous years, Buffalo’s 2023 WordCamp will divide its workshops along two tracks, with sessions for every ability and level of use.</p>



<p>Speakers will include WordPress users from Buffalo, Rochester, and beyond, with experience ranging from user/blogger to advanced developer.</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, 17 Mar 2023 14:30:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Michelle Frechette";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:57:"WordCamp Central: WordCamp Entebbe 2023: An Amazing Recap";s:7:"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=3163170";s:7:"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://central.wordcamp.org/news/2023/03/wordcamp-entebbe-2023-an-amazing-recap/";s: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:4374:"<p>WordCamp Entebbe, a two-day event that took place on the 10th and 11th of March, 2023, was a resounding success and was attended by over 200 people. The event, which was focused on the WordPress content management system, drew attendees from across Uganda and beyond. However, what made this event stand out was its commitment to gender diversity in the tech industry.</p>



<p>The organizers of WordCamp Entebbe made a concerted effort to ensure that women were well-represented at the event. The gender diversity program featured female speakers and student attendees. This program was designed to inspire more women to pursue careers in technology, and it proved to be a huge success.</p>



<img src="https://masterwp.com/wp-content/uploads/2023/03/image2-1024x683.jpg" alt="A person stands on a stage with a microphone." />



<img src="https://masterwp.com/wp-content/uploads/2023/03/image4-1024x683.jpg" alt="The group poses for a photo." width="670" height="446" />Students pose for a group photo with the lead organiser Arthur Kasirye 



<img src="https://masterwp.com/wp-content/uploads/2023/03/image6-1024x683.jpg" alt="The group poses for a photo." />Students arriving at the WordCamp



<p>Over the course of the two-day event, attendees had the opportunity to attend a wide range of sessions, workshops, and presentations. Many of these were led by female speakers who shared their experiences and expertise with the audience.&nbsp;</p>



<p>The topics covered ranged from beginner-level introductions to WordPress to more advanced topics such as website optimization, content creation, and web security.</p>



<p>One of the most inspiring sessions of the event was a panel discussion on women in tech. This session featured female leaders in the Ugandan tech industry who shared their experiences and insights with the audience. The panelists talked about the challenges they had faced as women in a male-dominated industry and offered advice on how to overcome those challenges.</p>



<img src="https://masterwp.com/wp-content/uploads/2023/03/image7-1024x684.jpg" alt="A group is sitting in chairs." />Women Panel at the Wordcamp



<img src="https://masterwp.com/wp-content/uploads/2023/03/image5-1024x880.jpg" alt="The group poses for a photo." />



<p>Another highlight of WordCamp Entebbe was the student program. This program provided an opportunity for students to attend the event and learn more about WordPress and the tech industry in general. The students were able to attend workshops and presentations, network with professionals in the industry, and gain valuable insights into the world of tech as well as introduced to the new study curriculum of the Directorate of Industrial Training (DIT) a Ugandan quality assurance directorate offering nationally, regionally and internationally recognized quality assurance services for the Business, Technical, Vocational Education and Training (BTVET) were students can use WordPress in their final year projects and graded on a national level.</p>



<img src="https://masterwp.com/wp-content/uploads/2023/03/image3-1024x683.jpg" alt="A group is observing a laptop." />Students learning to install WordPress website



<p>This year’s WordCamp was led by Kasirye Arthur the leader of the&nbsp;<a href="https://www.meetup.com/entebbe-wordpress-meetup/" target="_blank" rel="noreferrer noopener">WordPress Community in Entebbe</a>&nbsp;who is also a community lead for&nbsp;<a href="https://www.meetup.com/kampala-woocommerce-meetup-group/" target="_blank" rel="noreferrer noopener">Woocommerce</a>&nbsp;and&nbsp;<a href="https://www.meetup.com/elementor-uganda-meetup-group/" target="_blank" rel="noreferrer noopener">Elementor</a></p>



<p>Overall, WordCamp Entebbe was a hugely successful event that demonstrated the power of gender diversity in the tech industry.&nbsp;</p>



<p>By creating a program that was focused on empowering women in Tech, the organizers of this event helped to inspire a new generation of female technologists. It is our hope that more events like WordCamp Entebbe will be organized even in schools so that we can continue to build a more diverse and inclusive tech industry.&nbsp;</p>



<img src="https://masterwp.com/wp-content/uploads/2023/03/image8-1024x684.jpg" alt="The group poses for a photo." width="670" height="447" />WordCamp Entebbe organising Team";s: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, 17 Mar 2023 09:30:42 +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:"Kasirye Arthur";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:105:"WPTavern: Equalize Digital Raises Pre-Seed Funding for Expanding Accessibility Checker Plugin Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=142818";s:7:"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:116:"https://wptavern.com/equalize-digital-raises-pre-seed-funding-for-expanding-accessibility-checker-plugin-development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3689:"<p>Equalize Digital, a WordPress accessibility products and consulting company, has <a href="https://equalizedigital.com/equalize-digital-receives-investment-emilia-capital/">received an undisclosed amount of pre-seed funding</a> from Emilia Capital, the investment company owned by Joost de Valk and Marieke van de Rakt. The investment will be used to accelerate the growth of Equalize Digital&#8217;s <a href="https://equalizedigital.com/accessibility-checker/">Accessibility Checker plugin</a>, a tool for auditing websites for WCAG, ADA, and Section 508 accessibility errors.</p>



<p>Emilia Capital now owns part of the company, although its owners were not given seats on the board. Equalize Digital founder and CEO Amber Hinds said they will be serving as advisors and playing a role in strategic planning, especially around marketing and plugin development.</p>



<p>The Accessibility Checker plugin currently has approximately 2,000 active installs, according to <a href="https://wordpress.org/plugins/accessibility-checker/">WordPress.org stats</a>, and the commercial upgrades make up a small percentage of Equalize Digital&#8217;s current revenue.</p>



<p>&#8220;We built the initial MVP in 2020 with an SBA loan and since then the plugin has been bootstrapped by profits from the service side of our business,&#8221; Hinds said. &#8220;My partner Steve and I have been splitting our time between client work and working on the plugin.</p>



<p>&#8220;We decided to bring on an investor because our ultimate goal is for the product to make up a significant portion of our revenue. It&#8217;s challenging to rapidly grow a product that isn&#8217;t yet self-sustaining, hence seeking investors. The funds will allow us to have full-time team members building new features, and also further invest in marketing, education, and sales than was possible while we were bootstrapping.&#8221;</p>



<p>Hinds said the features her team is targeting are aimed at making the plugin a more competitive accessibility auditing tool when compared with other existing SaaS solutions. </p>



<p>&#8220;Our focus right now is making our reports easier to understand by less technical users,&#8221; Hinds said. &#8220;The next major release with be a feature that allows people to click a button and highlight elements on the front end of the website, which will make it easier to find the element flagging the issue without having to interpret a code snippet.</p>



<p>&#8220;Other features that we have on the road map include scanning and reporting on archive pages for posts and taxonomies, improved scanning of non-English sites, and the ability for accessibility testers to log issues found during manual accessibility audits.&#8221;</p>



<p>Hinds said she was encouraged by the findings in the recent <a href="https://theadminbar.com/2023-survey/">Admin Bar survey of WordPress professionals</a>, which showed that 76.9% report they are striving for best practices when it comes to website accessibility, a significant increase from the previous year. With the new investment, Equalize Digital will be able to do more marketing to increase awareness and adoption of its tools.</p>



<p>&#8220;Ultimately I would like to see accessibility being considered during website builds in the same way that SEO is, and we&#8217;re hoping that our plugin will central to that,&#8221; Hinds said. &#8220;It&#8217;s why the free version of our plugin is much more full-featured than similar plugins. Other accessibility tools are prohibitively expensive for small businesses and bloggers. We&#8217;re aiming to build a tool that makes accessibility testing available to everyone.&#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, 17 Mar 2023 03:33: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: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:63:"WPTavern: Local 6.7.0 Adds Long-Requested Site Grouping Feature";s:7:"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=142784";s:7:"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/local-6-7-0-adds-long-requested-site-grouping-feature";s: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:2533:"<p>WP Engine&#8217;s <a href="https://localwp.com/">Local</a> development app has released <a href="https://localwp.com/releases/6.7.0/">version 6.7.0</a> with Site Grouping, a highly requested feature that will greatly improve users&#8217; workflows. It allows users to create custom groups in the sidebar of the Local dashboard page for better organization of their sites.</p>



<p>Local users have been <a href="https://community.localwp.com/t/group-sites-in-folder-in-sidebar/454/25">asking for this feature</a> since 2017, as many are managing dozens of WordPress sites. In June 2022, the Local development team began designing and then building the feature a couple months later, incorporating feedback from user interviews and usability testing.</p>



<p> In the new Site Grouping feature, sites can be easily dragged between groups and groups can be reordered up or down, as illustrated in the release notes.</p>



<img /><a href="https://localwp.com/releases/6.7.0/">Local 6.7.0 release notes</a>



<p>Another handy feature released with Site Grouping is the ability to start, stop, restart, or delete all the sites in a group from the context menu (the three dots to the right of the group name). Sites can also be sorted by how recently they were used via the clock icon at the top of the groups sidebar. </p>



<p>To get users started, all their Starred sites have been placed in a new Starred group at the top of the sidebar. Full <a href="https://localwp.com/help-docs/local-features/site-grouping-feature/">documentation for using the new Site Grouping feature</a> is available in Local&#8217;s help resources.</p>



<p><a href="https://deliciousbrains.com/wp-migrate-db-pro/">WP Migrate</a>, formerly known as WP Migrate DB and recently <a href="https://wptavern.com/wp-engine-acquires-5-plugins-from-delicious-brains">acquired by WP Engine</a>, introduced <a href="https://wptavern.com/wp-migrate-2-6-introduces-full-site-exports-and-import-to-local">full-site exports and imports to Local</a> in January 2023. Local version 6.7.0 improves imports from WP Migrate so that they auto-select the PHP, web server, and database version closest to the production environment if Local offers the same major/minor version.</p>



<p>This release also includes several bug fixes with Local importing or pulling to an existing site, where the site&#8217;s existing settings or environment were not applied. If you experienced this bug, make sure to update to the latest 6.7.0 release before attempting more imports.</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, 16 Mar 2023 17:27: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: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:87:"Post Status: WordPress 6.2 RC2 • Plugin Review Team Retirement News • WP20 Giveaway";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=148272";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:41:"https://poststatus.com/wordpress-6-2-rc2/";s: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:22040:"<h2 id="h-this-week-at-wordpress-org-march-13-2023">This Week at WordPress.org (March 13, 2023)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">Discover WordPress 6.2&#8217;s new features, accessibility enhancements, and developer updates. Contribute to the community by joining the Contributor Working Group. Explore new block theme template. Engage in discussions on mentorship programs. Celebrate WP20 and participate in the Wapuu Coloring Giveaway. </p></div>


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



<div class="wp-block-kadence-infobox kt-info-box_94d1bd-77"><div class="kt-blocks-info-box-link-wrap kt-blocks-info-box-media-align-left kt-info-halign-left"><div class="kt-blocks-info-box-media-container"><div class="kt-blocks-info-box-media kt-info-media-animate-none"><div class="kadence-info-box-icon-container kt-info-icon-animate-none"><div class="kadence-info-box-icon-inner-container"><span class="kb-svg-icon-wrap kb-svg-icon-fas_hand-holding-heart kt-info-svg-icon"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title">WP 6.2 RC2 • Plugin Review Team Announces Mika&#8217;s Retirement • WP20 Giveaway</h2><p class="kt-blocks-info-box-text"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f9ea.png" alt="🧪" class="wp-smiley" /> <a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-2/">WordPress 6.2 Release Candidate 2</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f4fa.png" alt="📺" class="wp-smiley" /> <a href="https://wordpress.org/news/2023/03/your-wordpress-6-2-preview/">Your WordPress 6.2 Preview</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64b-1f3fe.png" alt="🙋🏾" class="wp-smiley" /> <a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/">Help Test WordPress 6.2</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f5fa.png" alt="🗺" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f44b-1f3fb.png" alt="👋🏻" class="wp-smiley" /> <a href="https://make.wordpress.org/plugins/2023/03/10/advance-notice-of-retirement/">Advance Notice of Mika&#8217;s Plugin Review Retirement</a></p></div></div></div>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_b57166-6e"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 id="h-news"><a href="https://wordpress.org/news">News</a></h2>



<ul>
<li><a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-2/">WordPress 6.2 Release Candidate 2</a></li>



<li><a href="https://wordpress.org/news/2023/03/episode-51-is-routine-a-rut/">WP Briefing: Episode 51: Is Routine a Rut?</a></li>



<li><a href="https://wordpress.org/news/2023/03/your-wordpress-6-2-preview/">Your WordPress 6.2 Preview</a></li>



<li><a href="https://wp20.wordpress.net/wapuu-coloring-giveaway-style-your-own-party-wapuu/">Wapuu Coloring Giveaway: Style Your Own Party Wapuu</a></li>



<li><a href="https://wp20.wordpress.net/celebrate-with-wordpress/">WP20 Celebrations – Join in the Party – Online &amp; In-Person</a></li>
</ul>



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



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



<ul>
<li><a href="https://make.wordpress.org/accessibility/2023/03/13/accessibility-team-meeting-agenda-march-17-2023/">Accessibility Team Meeting Agenda: March 17, 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/community/2023/03/13/combining-roles-to-create-a-new-contributor-ladder/">Combining Roles to Create a New Contributor Ladder</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/13/proposal-updates-to-the-mentor-program/">Proposal: Updates to the Mentor Program</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/10/launching-the-contributor-working-group-call-for-volunteers/">Launching the Contributor Working Group: Call for Volunteers</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/08/recap-of-the-diverse-speaker-training-group-wpdiversity-amer-emea-on-march-8-2023/">Recap of the Diverse Speaker Training group (#WPDiversity) AMER/EMEA on March 8, 2023</a></li>



<li><a href="https://make.wordpress.org/community/2023/03/08/announcing-new-handbook-pages-on/">Running Funds Outside of WPCS</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/13/a-week-in-core-march-13-2023/">A Week in Core – March 13, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/13/whats-new-in-gutenberg-15-3-13-march/">What’s new in Gutenberg 15.3? (13 March)</a> </li>
</ul>



<h3 id="h-wordpress-6-2">WordPress 6.2</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/14/fyi-navigation-section-of-new-site-editor-experienced-removed-for-6-2-rc-2/">FYI: Navigation section of new Site Editor experienced removed for 6.2 RC 2</a></li>



<li><a href="https://wordpress.org/news/2023/03/wordpress-6-2-release-candidate-1/">WordPress 6.2 Release Candidate 1</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/14/wordpress-6-2-translation-status-march-14-2023/">WordPress 6.2 Translation Status (March 14, 2023)</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/04/wordpress-6-2-ready-to-be-translated/">WordPress 6.2 ready to be translated</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">WordPress 6.2 Field Guide</a>
<ul>
<li><a href="https://make.wordpress.org/core/2023/03/08/requests-library-upgraded-to-2-0-5-in-wordpress-6-2/">Requests library upgraded to 2.0.5 in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/patterns-api-expanded-to-include-template_types-property/">Patterns API expanded to include template_types property</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introduction-of-block-inspector-tabs/">Introduction of Block Inspector Tabs</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/shadows-in-global-styles-with-wordpress-6-2/">Shadows in Global Styles with WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introducing-the-html-api-in-wordpress-6-2/">Introducing the HTML API in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/miscellaneous-editor-changes-in-wordpress-6-2/">Miscellaneous Editor changes in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/introducing-move_dir-in-wordpress-6-2/">Introducing move_dir() in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/sticky-position-block-support/">Sticky position block support</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/07/upgrading-to-react-18-and-common-pitfalls-of-concurrent-mode/">Upgrading to React 18 and common pitfalls of concurrent mode</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/add-new-prop-to-serversiderender-component/">Add new prop to ServerSideRender component</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/google-fonts-are-included-locally-in-bundled-themes/">Google Fonts are included locally in bundled themes</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/custom-css-for-global-styles-and-per-block/">Custom CSS for global styles and per block</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/06/minimum-height-dimensions-block-support/">Minimum height dimensions block support</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/03/editor-components-updates-in-wordpress-6-2/">Editor Components updates in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/03/i18n-improvements-in-6-2/">I18N Improvements in 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/28/custom-settings-wordpress-6-2/">Customize settings for any block in WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/19/style-book-preview-of-blocks-in-global-styles/">Style Book preview of blocks in global styles</a></li>



<li><a href="https://make.wordpress.org/core/2022/12/09/update-to-content-only-editing-filter-namespace/">Update to content only editing filter namespace</a></li>
</ul>
</li>



<li><a href="https://make.wordpress.org/core/2023/03/02/wordpress-6-2-accessibility-improvements/">WordPress 6.2 Accessibility Improvements</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/28/wordpress-6-2-beta-4-postponed/">WordPress 6.2 Beta 4 Postponed</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/21/wordpress-6-2-beta-3/">WordPress 6.2 Beta 3</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/21/6-2-live-product-demo/">6.2 Live Product Demo</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/04/phase-2-finale/">Phase 2, Finale</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/03/hallway-hangout-performance-improvements-for-wordpress-6-2/">Hallway Hangout: Performance Improvements for WordPress 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/02/06/roadmap-to-6-2/">Roadmap to 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/18/bug-scrub-schedule-for-6-2/">Bug Scrub Schedule for 6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/11/early-bug-scrub-schedule-for-wp-6-2/">Early bug scrub schedule for WP&nbsp;6.2</a></li>



<li><a href="https://make.wordpress.org/core/2023/01/17/wordpress-6-2-planning-roundup/">WordPress 6.2 Planning Roundup</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/14/dev-chat-agenda-wednesday-march-15-2023/">Dev Chat Agenda, Wednesday March 15, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/14/editor-chat-agenda-march-15-2023/">Editor Chat Agenda: March 15, 2023</a></li>
</ul>



<h3 id="h-developer-blog">Developer Blog</h3>



<ul>
<li><a href="https://developer.wordpress.org/news/2023/03/block-theme-templates-the-easy-way-to-build-an-elegant-grid-of-posts/">Block theme templates: the easy way to build an elegant grid of posts</a></li>



<li><a href="https://developer.wordpress.org/news/2023/03/whats-new-for-developers-march-2023/">What’s new for developers? (March 2023)</a></li>



<li><a href="https://developer.wordpress.org/news/2023/03/block-deprecation-a-tutorial/">Block deprecation – a tutorial</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/design/2023/03/13/design-share-feb-13-mar-10/">Design Share: Feb 13–Mar 10</a></li>
</ul>



<h2 id="h-do-action"><a href="https://doaction.org/">do_action</a></h2>



<ul>
<li><a href="https://doaction.org/event/ruralhackers/">Rural Hackers Do_Action 2023 in Anceu Spain</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/docs/2023/03/16/agenda-for-docs-team-bi-weekly-meeting-march-21-2023/">Agenda for Docs Team bi-weekly meeting March 21, 2023</a></li>



<li><a href="https://make.wordpress.org/docs/2023/03/16/summary-for-docs-team-meeting-march-7-2023/">Summary for Docs Team meeting, March 7, 2023</a></li>
</ul>
</div>



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



<ul>
<li><a href="https://make.wordpress.org/hosting/2023/03/14/hosting-team-meeting-agenda-2023-03-15/">Hosting Team meeting agenda 2023-03-15</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/marketing/2023/03/14/notes-global-marketing-team-meeting-5-march-2023/">Notes: Global Marketing Team meeting, 5 March 2023</a></li>



<li><a href="https://make.wordpress.org/marketing/2023/03/13/notes-global-marketing-team-meeting-28-february-2023/">Notes: Global Marketing Team meeting, 28 February 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/openverse/2023/03/15/community-meeting-recap-14-march-2023/">Community Meeting Recap (14 March 2023)</a></li>



<li><a href="https://make.wordpress.org/openverse/2023/03/14/last-week-openverse-2023-03-06-2023-03-13/">A week in Openverse: 2023-03-06 – 2023-03-13</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/14/performance-chat-summary-14-march-2023/">Performance Chat Summary: 14 March 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/plugins/2023/03/10/advance-notice-of-retirement/">Advance Notice of Retirement</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/polyglots/2023/03/15/polyglots-monthly-newsletter-march-2023/">Polyglots Monthly Newsletter: March 2023</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/14/wordpress-6-2-translation-status-march-14-2023/">WordPress 6.2 Translation Status (March 14, 2023)</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/03/14/agenda-weekly-polyglots-chat-march-15-2023-1300-utc/">Agenda: Weekly Polyglots Chat – March 15, 2023 (13:00 UTC)</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/plugins/2023/03/10/advance-notice-of-retirement/">Advance Notice of Retirement</a></li>
</ul>



<h2 id="h-project">Project</h2>



<ul>
<li><a href="https://make.wordpress.org/project/2023/02/06/proposal-creating-a-wordpress-contributor-mentorship-program/">Proposal: Creating a WordPress Contributor Mentorship Program</a></li>



<li><a href="https://make.wordpress.org/project/2023/01/27/discussion-ending-the-eternal-september/">Discussion: Ending the Eternal September</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/support/2023/03/agenda-for-march-16th-support-meeting-2/">Agenda for March 16th Support Meeting</a></li>



<li><a href="https://make.wordpress.org/support/2023/03/summary-for-march-9th-support-meeting/">Summary for March 9th Support Meeting</a></li>



<li><a href="https://make.wordpress.org/support/2023/03/support-ticket-triage-session-march-22th-2023-at-1600-utc/">Support ticket triage session – March 22th 2023 at 16:00 UTC</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/test/2023/03/14/hallway-hangout-lets-chat-about-all-things-layout/">Hallway Hangout: Let’s chat about All Things Layout</a></li>



<li><a href="https://make.wordpress.org/test/2023/03/14/test-chat-summary-14-march-2023/">Test Chat Summary: 14 March 2023</a></li>



<li><a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/">Help Test WordPress 6.2</a></li>
</ul>



<h2 id="h-theme">Theme</h2>



<ul>
<li><a href="https://make.wordpress.org/themes/2023/03/15/themes-team-meeting-notes-march-14-2023/">Themes Team Meeting Notes –&nbsp;March 14, 2023</a></li>



<li><a href="https://make.wordpress.org/themes/2023/03/03/hallway-hangout-community-themes-initiative/">Hallway Hangout: Community Themes Initiative</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/training/2023/03/13/meeting-agenda-for-march-14-2023/">Meeting Agenda for March 14, 2023</a></li>



<li><a href="https://make.wordpress.org/training/2023/03/10/dev-squad-update-triage-sessions-planning/">Dev-squad update: Triage sessions planning</a></li>



<li><a href="https://make.wordpress.org/training/2023/03/10/training-team-meeting-recap-for-march-7-2023/">Training Team Meeting Recap for March 7, 2023</a></li>



<li><a href="https://make.wordpress.org/training/2023/03/08/introduction-to-wordpress-development-a-proposed-learning-path/">Introduction to WordPress&nbsp;Development: A proposed learning path</a></li>
</ul>



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



<ul>
<li><a href="https://learn.wordpress.org/?meeting=lets-code-developing-user-roles-and-capabilities">Let’s code: developing user roles and capabilities</a></li>



<li><a href="https://learn.wordpress.org/?meeting=wp-dev-livestream-developing-wordpress-user-roles-and-capabilities-2">WP dev livestream: Developing WordPress user roles and capabilities</a></li>



<li><a href="https://learn.wordpress.org/?meeting=updating-a-blogs-design-informal-live-stream-part-3">Updating a blog’s design (Informal live stream) – Part 3</a></li>



<li><a href="https://learn.wordpress.org/?meeting=%E3%82%AF%E3%83%A9%E3%82%B7%E3%83%83%E3%82%AF%E3%82%A8%E3%83%87%E3%82%A3%E3%82%BF%E3%83%BC%E3%81%8B%E3%82%89%E3%83%96%E3%83%AD%E3%83%83%E3%82%AF%E3%82%A8%E3%83%87%E3%82%A3%E3%82%BF%E3%83%BC%E3%81%AB">クラシックエディターからブロックエディターに移行するノウハウ</a></li>
</ul>



<h3 id="h-lesson-plans">Lesson Plans</h3>



<ul>
<li><a href="https://learn.wordpress.org/lesson-plan/pagine-vs-articoli/">Pagine vs. articoli</a></li>



<li><a href="https://learn.wordpress.org/lesson-plan/cosa-fare-quando-non-ti-ricordi-la-password/">Cosa fare quando non ti ricordi la password</a></li>



<li><a href="https://learn.wordpress.org/lesson-plan/ta-dashboard-overview/">டாஷ்போர்டு மேலோட்டம்</a></li>
</ul>



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



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



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



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



<ul>
<li><a href="https://www.php.net/archive/2023.php#2023-02-14-2">PHP 8.2.3 Released!</a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-02-14-3">PHP 8.1.16 Released!</a></li>



<li><a href="https://262.ecma-international.org/13.0/">TC39</a></li>



<li><a href="https://github.com/composer/composer/releases/tag/2.5.4">Composer 2.5.4</a></li>
</ul>



<p class="has-theme-palette-7-background-color has-background">Thanks for reading our WP dot .org roundup! Each week we are highlighting the news and discussions coming from the good folks making WordPress possible. If you or your company create products or services that use WordPress, you need to be engaged with them and their work. Be sure to share this resource with your product and project managers. <br /><br /><strong>Are you interested in giving back and contributing your time and skills to WordPress.org?</strong> <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://wordpress.org/support/article/contributing-to-wordpress/">Start Here ›</a><br /><br /><strong>Get our weekly WordPress community news digest</strong> — Post Status&#8217; <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — covering the WP/Woo news plus significant writing and podcasts. It&#8217;s also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>



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



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



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



<div class="wp-block-spacer"></div>
<p>This article was published at Post Status — the community for WordPress professionals.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Mar 2023 17:01: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:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:80:"Post Status: Post Status Live – The Right Approach to WordPress Accessibility";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=148252";s:7:"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:86:"https://poststatus.com/post-status-live-the-right-approach-to-wordpress-accessibility/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:105788:"<div class="is-layout-flow wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">If you’re a leader, a developer, or a designer about to start a major website project, this webinar will help you navigate the important topic of accessibility. <a href="https://twitter.com/corymiller303">Cory Miller</a> is joined by the team at <a href="https://tri.be/">Modern Tribe</a> &#8211; <a href="https://twitter.com/ChrisMKindred">Chris Kindred</a>, Director of Backend Development, <a href="https://twitter.com/sarahgless">Sarah Gless</a>, Creative Director, and <a href="https://twitter.com/mjklanac">Mike Klanac</a>, Director of Business Development, to discuss why accessibility is imperative and how to integrate it into each aspect of development and implementation. </p></div>


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



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







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



<p class="wp-embed-aspect-16-9 wp-has-aspect-ratio">The talented team from <a href="https://tri.be/">Modern Tribe</a>  joined <a href="https://twitter.com/corymiller303">Cory Miller</a> for this critical discussion about accessibility in WordPress. They highlight accessibility as a non-negotiable aspect of web development and provide guidance for leaders, developers, and designers to ensure your websites are accessible to all people.</p>



<p class="wp-embed-aspect-16-9 wp-has-aspect-ratio"><strong>Top Takeaways:</strong></p>



<ul type="video" class="wp-embed-aspect-16-9 wp-has-aspect-ratio">
<li><strong>Why Value Accessibility? </strong>Accessibility ensures all people have access to the things we create. It can’t be an afterthought or something for the web dev team to figure out. It must drive the entire creative process and serve as an anchor to ground our teams and our work.</li>



<li><strong>Requirement vs. Challenge.</strong> Most creative projects work within a set of requirements. These don’t prohibit the creative process. Instead, they challenge us to enhance the things we build and make them better than we might have without thinking through and within these constraints.</li>



<li><strong>It’s All Around Us.</strong> We think of accessibility as a new idea, but in so many spaces, it’s the norm. We have curb cutouts and braille signage. We see this every day, so tech is catching up.</li>



<li>Improving Usability. Developing through the lens of accessibility means delivering experiences that solve people’s problems and help them with tasks.</li>



<li><strong>It Takes Tools.</strong> The creative and engineering are just rails. Utilizing tools to ensure accessibility when publishing and setting up processes and guidelines will equip you to flex as requirements change. It’s necessary for your organization to resource accessibility for it to be done effectively.</li>
</ul>



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

</div>



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



<ul>
<li><a href="https://tri.be/">Modern Tribe</a></li>



<li><a href="https://vimeo.com/148927676">Eric Meyer</a></li>



<li><a href="https://myspace.com/">MySpace</a></li>
</ul>



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



<ul class="eplus-wrapper">
<li><a href="https://twitter.com/brandondove"></a><a href="https://twitter.com/ChrisMKindred">Chris Kindred</a> (Director of Backend Development, <a href="https://twitter.com/pixel_jar"></a><a href="https://twitter.com/ModernTribeAgcy">Modern Tribe</a>)</li>



<li><a href="https://twitter.com/sarahgless">Sarah Gless</a> (Creative Director, <a href="https://twitter.com/pixel_jar"></a><a href="https://twitter.com/ModernTribeAgcy">Modern Tribe</a>)</li>



<li><a href="https://twitter.com/mjklanac">Mike Klanac</a> (Director of Business Development, <a href="https://twitter.com/pixel_jar"></a><a href="https://twitter.com/ModernTribeAgcy">Modern Tribe</a>)</li>



<li><a href="https://twitter.com/corymiller303">Cory Miller</a> (CEO, <a href="https://twitter.com/post_status">Post Status</a>)</li>



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



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



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



<p>Cory Miller: [00:00:00] Everybody welcome back to another Post Status Live. This is where we<br />do, uh, webinars and interviews with our awesome members at Post Status. And today we&#8217;ve<br />got a great talented team from Modern Tribe.<br />I&#8217;m gonna let them unpack a little bit more about what Modern Tribe does and what they do at<br />Modern Tribe. But today, our topic is gonna be the right approach to WordPress accessibility.<br />This kinda, this really came to the forefront for us and why I sought these experts out because<br />accessibility is a non-negotiable for the web.<br />Um, and they&#8217;re gonna talk more about their passion, their experiences, their expertise around<br />that. But I will just say this is a topic that we need to be talking about more, and we&#8217;re<br />specifically doing this webinar, and I&#8217;ve asked them to come on and share. Particular areas and<br />work inaccessibility with WordPress.<br />But if you&#8217;re a leader, you&#8217;re a developer, you&#8217;re a designer, um, starting to embark on a, on a<br />website project and want rightly so, to [00:01:00] make sure your website is accessible to all<br />people. This is, this is the extended webinar for you. We&#8217;re gonna talk, we&#8217;re gonna talk about a<br />lot. We&#8217;re gonna talk about how does a c-suite or leadership team properly resource and lead,<br />uh, in the accessibility projects for your organization, all the way down to the developers,<br />designers, the people that use the website every single day to make sure you&#8217;re doing your best<br />for those, trying to access your website.<br />So, I wanna introduce these te these, uh, this team today, but I&#8217;m gonna let you do that. So,<br />Mike, could you start us off and share, um, a little bit about what you do with, with, uh, uh, your<br />work at Modern Tribe and, uh, your interest in this whole topic of accessibility?<br />Mike Klanac: Yeah, thanks Corey. Um, my name is Mike Klan.<br />I am the Director of Business Development at Modern Tribe. Um, that&#8217;s essentially a sales role<br />here. [00:02:00] Um, and, uh, I&#8217;m really excited to talk more about accessibility. Um, I, you know,<br />to be transparent, I was actually a little nervous at first, uh, because of my role as essentially a<br />sales role. And, um, this is such an important topic and, and Corey in like preparing for this, you<br />said something that, that resonated with me, which is, , you know, if this is important, um, don&#8217;t<br />feel bad about being an advocate for it and talking about it.<br />Um, so, uh, that helped build my confidence. So I&#8217;m excited to be here to talk more especially<br />about, uh, accessibility as it relates to leadership and as it relates to a core value that stretches<br />across all components of your business. Uh, so, um, yeah, I think continue on with introductions<br />and maybe I could circle back and, and tell you a little bit more about, uh, tribe and how long<br />we&#8217;ve been around.<br />Cory Miller: Yeah. We&#8217;ll, we&#8217;ll come back to you, but I think you, you know, one compelling<br />reason you&#8217;re here too is because you do talk to people that are making decisions, [00:03:00]<br />but not necessarily always the people doing the work too. And it&#8217;s a collaborative approach. And<br />I know your heart, you&#8217;re super, super humble, but very experienced.<br />Mm-hmm. , um, professional. So I&#8217;m really glad to have you on here and you&#8217;re gonna talk first<br />as we, after we do introductions about the whole leadership angle for all of this. Um, Chris and<br />Sarah. Yeah,<br />Chris Kindred: thanks. Um, my name&#8217;s Chris Kendrick. I am, uh, director of backend, um,<br />engineering here at Modern Tribe. Um, I, accessibility&#8217;s always been a passion of mine, um, and<br />it&#8217;s been, uh, really great to come on board at somewhere like Modern Tribe, where they take<br />flexibility so seriously.<br />So, uh, that&#8217;s always been a, a great thing for, for me, um, moving forward. So,<br />yeah.<br />Sarah Gless: Hi, I&#8217;m Sarah Glass. Oh, sorry.<br />Cory Miller: Yeah, yeah. Sorry. Go ahead Sarah. Yeah, thanks Chris.<br />Sarah Gless: Yeah, thank you for having us. Um, I&#8217;m Sarah Glass. I&#8217;m the creative Director at<br />Modern [00:04:00] Tribe. Ultimately, that means I&#8217;m in service to both our clients, making sure<br />that we&#8217;re shipping incredibly beautiful and, and and engaging work, um, as well as our design</p>



<p>team, ensuring that, you know, they&#8217;re fulfilled in and the work that they&#8217;re doing, and we&#8217;re<br />continuously developing and pushing the work forward.<br />Um, I&#8217;m super passionate about accessibility too. You know, I think that, as you know, coming<br />from a design background, um, ultimately I wanna communicate effectively with, with, with<br />people. And, um, if, if you cut off people in those lanes of communication, um, how good is that<br />design? So I, I truly believe that good design is accessible design.<br />Um, super excited to, to be here and, and chat more about.<br />Cory Miller: I can&#8217;t wait to dig in with all three of you because what you just said, Sarah, is good<br />access, good accessibility is good design. And I think there&#8217;s probably a lot of designers out<br />there that just kind of like, oh, okay, we can do this. So I&#8217;m looking forward to talking more about<br />that, particularly, um, I&#8217;m gonna hype &#8217;em up,<br />[00:05:00] Yeah, absolutely. This can be, you know, that&#8217;s another message in all this, this can<br />be done. There is an approach, a good approach to it, and it is possible, and I think that&#8217;s a<br />really great message. Um, so Mike, before we kind of get into the actual topics, could you tell us<br />a little bit more about Modern Tribe as an agency?<br />Mike Klanac: Sure, sure. I&#8217;ll give you the short version. So, um, Modern Tribe, we like to call<br />ourselves a full service digital design and development agency. Um, we&#8217;ve been around for<br />about 15 years now, uh, and recently joined the liquid web family of brands. Um, I think like one<br />of the way, another way we describe ourselves is we say we connect to the touchpoints of your<br />digital ecosystem.<br />Um, and when I say that, I think what&#8217;s important to note is kind of that WordPress is often. the<br />center, it&#8217;s the hub, the WordPress TMS is the hub of that ecosystem. So we lean on, on<br />WordPress heavily. [00:06:00] Um, and our, our business, I mean, it sort of breaks down into<br />four key categories. There&#8217;s strategy, there&#8217;s content, there&#8217;s design, there&#8217;s engineering, um,<br />and that&#8217;s sort of who we are.<br />Um, accessibility of the topic at hand today, uh, as you&#8217;ll see it, it sort of permeates all of those<br />areas and it&#8217;s sort of core to who we are, um, as an organization. So, um, yeah, we&#8217;re, we&#8217;re<br />press agency.<br />Cory Miller: And I know you all work with some name brand organizations. Maybe you can&#8217;t all<br />talk about it, but I&#8217;m aware enough to know that you all have worked with some of the biggest<br />brands that are household names, helping them specifically, not just with their web, but also that<br />this important part, accessibility.<br />And some of these, uh, organizations, Mike, particularly I know from talking with you all<br />background about this, is if you take federal funding in any way, particularly in the United States,<br />it, it&#8217;s not even a conversation about is it, is [00:07:00] it a thing we should do? It&#8217;s like, no, you<br />do it. And I think that amps us up even more.<br />Um, thankfully, government non-profits have led the way with accessibility, but this is something<br />we&#8217;ll talk more about. Everybody should be doing this. Um, this is this, we&#8217;re in 2023 now today.<br />And it, this is just a part and I&#8217;m, that&#8217;s why, another reason I&#8217;m glad, but you all work with these<br />organizations where you&#8217;re like, there&#8217;s a lot of scrutiny on these organizations you work with.<br />That means that that&#8217;s a good thing in a way because they have to make sure, like Sarah was<br />saying, that this website is successful for anyone that wants to, to access it. So, uh, I think that&#8217;s<br />pretty critical and also demonstrates why I asked Modern Tribe and U three to come on to talk<br />about this today.<br />So, okay, here&#8217;s the layout. We&#8217;re gonna talk about leadership. Now for those of you watching<br />and listening, um, we&#8217;re gonna each, each of the experts, I&#8217;ve asked to talk about a specific area<br />related to their expertise, but you&#8217;re gonna hear from them. I&#8217;ve told them, I said, [00:08:00] I<br />don&#8217;t want you to stay silent.<br />Mike&#8217;s part part, I want you to contribute too, because. As we&#8217;ve talked and prepared for this, it&#8217;s<br />helped me understand this is a holistic process that everybody in the organization needs to<br />embrace. And so, again, I&#8217;ll, I&#8217;ll just say to y&#8217;all, please, if Mike&#8217;s talking, share something from<br />your perspective about this, uh, please do that.<br />Cause I think this is gonna help people. Our intention here is you&#8217;re trying to do right and good<br />by this for your website project. So I want you all to like, help them really understand these are<br />the things we work with clients about. These are the problems we see, these are the challenges<br />we see and here&#8217;s our thoughts.</p>



<p>Because you, you are experts in this and you see things that I think could make those trying to<br />cross this threshold, um, truly be prepared for and make really good decisions that helps<br />everybody involved, even if they don&#8217;t choose modern tribe as the agency. So again, I think<br />that&#8217;s right on important.<br />Okay, so let&#8217;s just start right here, because [00:09:00] oftentimes, as I understand this, both<br />leading my own organizations, listening to you all and other agency members that post status, I<br />go, um, this type of decision needs to start at the, you know, the top of the hierarchy here. If the<br />leaders aren&#8217;t on board or don&#8217;t fully understand it, this is gonna be a problem.<br />So, I hope those leaders listening, this is your time to take notes because Mike, I, I want you to<br />kind of, what do you think of when you&#8217;re saying, okay, I am, let&#8217;s say a c e O of an organization<br />or in the C-suite or leadership team. I need to start helping think through this, you know,<br />accessibility for what we do on the web.<br />What stands out to you when we talked about leadership and WordPress accessibility.<br />Mike Klanac: Yeah, I&#8217;m, I&#8217;m so glad we get to talk about it from this perspective, because so<br />often accessibility can get pretty dense and technical right away. Um, but in today&#8217;s modern<br />world, uh, it it&#8217;s more than that. And it&#8217;s something that permeates all aspects of your business if<br />you [00:10:00] want it to be successful.<br />And therefore, it often has to start with leadership, um, realizing why it&#8217;s, IM important. Um, it&#8217;s,<br />it&#8217;s gotta be built as a core consideration, um, to all of those various layers. Uh, and the best<br />organizations, the really effective organizations that care and are considerate of their users<br />make this a, a core value.<br />It&#8217;s, it literally becomes, um, part of the culture. Top to bottom. Um, so I think one of the ways to<br />build that understanding is to really think about like, why you&#8217;re doing this. And we hit on the<br />legal implications initially, and I think that&#8217;s where a lot of people first start thinking about this for<br />some reason.<br />But you kind of need to back up and really remember that one of the first reasons this is<br />important is, is just morally, it&#8217;s, it&#8217;s morally important. It&#8217;s a part of digital inclusivity. We are<br />creating tools that serve [00:11:00] users, that serve people, and therefore we need to care for<br />them. We need to think about how they use it.<br />And that applies to all of the users. It&#8217;s an increasingly competitive world. We don&#8217;t have the<br />luxury of, um, excluding people because it&#8217;s not convenient to, um, build tools that serve them<br />effectively. So I think like we really need to ground ourselves in the moral component of this first,<br />which is it&#8217;s the right thing to do.<br />It&#8217;s just the right thing to do, therefore needs to be a leadership initiative. It needs to be brought<br />in, carried through to all components, all layers of your business. Okay. So that&#8217;s like the first<br />thing that I would probably tell a leader in this space is that make it a part of all of your thinking.<br />Cory Miller: I mean, you know, I, we were talking about a client used to consult with before we<br />started recording and I was like, you could tell there the client one did the traditional thing, print<br />off your core values, put it on all the doors, and you&#8217;re like, cool. Yeah. But what are your real<br />core values? [00:12:00] And it seems to me, as you talk about one, there is a business reason<br />to do this, very legitimate that it&#8217;s gonna get a lot of people&#8217;s attention.<br />But I think what you were, you&#8217;re saying is like it should reflect a value that you might not have<br />on the door, but like we care. Yes, we care about the whole population and being able to get to<br />the things that we offer. And if we don&#8217;t, it it, I mean that rings really true when you say that<br />business, there&#8217;s a legitimate business reason and that should hopefully check most boxes.<br />But I think the other thing is that you should actually just care. Yeah. We&#8217;ve all probably been<br />touched in some way with someone that has, uh, uh, uh, something that doesn&#8217;t allow them to<br />see, read, hear, whatever that is, um, that we need to be thinking about that. Just because we<br />don&#8217;t have that particular issue doesn&#8217;t mean there&#8217;s a pretty significant one is a significant<br />enough to me.<br />But I mean this, we&#8217;re talking about in this accessibility [00:13:00] conversation quite a bit of the<br />population that most organizations have flatly not even thought about till today.<br />Mike Klanac: Exactly. Yeah, I think it just sends the right message. You know, when you&#8217;re the<br />type of organization that takes the time to be deliberate and considerate of all of your users,<br />there&#8217;s probably an understanding that that carries through to your product.</p>



<p>If you&#8217;re selling something, um, you, your service, your, your organization as a whole. So, um,<br />it&#8217;s just the right thing to do. And I think, I think we should just start there as it&#8217;s, it&#8217;s morally right.<br />And as you hit on, um, and to segue a little bit, there are legitimate business reasons. So, um,<br />making sure that your, your site is fully accessible, has this effect of improving the quality, the<br />experience for your users.<br />And that sort of in some ways overlays these other topics that we often talk about as like key<br />performance indicators for businesses. [00:14:00] Things like search engine optimization, um,<br />core web vitals. Um, these are adjacent to each other. So it it&#8217;s about creating an experience<br />that is a user experience that&#8217;s quality for everyone, and therefore your, your business will feel<br />that it&#8217;ll have an impact.<br />Um, so not only is it the right thing to do, morally a highly accessible site that&#8217;s gonna benefit<br />your, your clicks, your conversions, and all those things that we&#8217;ve spent so much time thinking<br />about, um, and that we&#8217;re starting to, to kind of like land a couple of really important reasons. It&#8217;s<br />like, you know, it&#8217;s what&#8217;s good as a person, it&#8217;s what&#8217;s good for business.<br />Um, it th those alone are, are enough reason, right, to really think long and hard about this. Um,<br />But there&#8217;s this final one too, which is the one we kind of backed into this from, which was,<br />there&#8217;s some legal requirements here. I I, I pulled a stat, and I think everyone&#8217;s aware of this,<br />but, [00:15:00] um, 2,800 accessibility lawsuits in 2021.<br />Um, that&#8217;s, that&#8217;s like, it&#8217;s a big deal. And those lawsuits, um, are meaningful and there&#8217;s a place<br />for them. Um, but more important than the litigation itself is you just have an opportunity to get<br />ahead of this if you do things right, and that can get confusing. Um, I, sorry, you&#8217;re gonna jump<br />in. I&#8217;ll take a beat.<br />Cory Miller: Yeah, no, I, I think, um, I&#8217;m curious to hear what Chris and Sarah think too,<br />because it&#8217;s like, you know, we&#8217;ve all been to those situations, uh, where you&#8217;re like, the<br />organization talks a really good talk. Yeah. You know, and we&#8217;ve got plenty of those in our<br />society globally today. But you know, the ones that talk.<br />And you know that ones that just act on that value. And I think this shines pretty clearly whether<br />you go to a website, you see the accessibility blue circle or whatever this is. And I think<br />[00:16:00] this is an opportunity. I&#8217;m curious what Chris and Sarah think too from just an<br />organization standpoint of like when you see someone taking it to this degree, not because they<br />necessarily have to, a lot of these have to, but, and there&#8217;s a probably legitimate reason why<br />there&#8217;s regulations and laws and different things in these lawsuits is because like, okay, if you&#8217;re<br />not gonna do the right thing, the, the world society will kind of push you in that regard.<br />But I think, I&#8217;m curious what you think Chris and Sarah is like, this is a way to get out front and<br />lead act on those values. You can&#8217;t just say you care, but if you care enough to make sure your<br />website is A to B, everybody can can access that and and consume the information and<br />whatever you&#8217;re trying to offer in the world, that&#8217;s an opportunity for leadership to me.<br />So Sarah, Chris, what do you think? . I, yeah,<br />Chris Kindred: I, uh, okay. Uh, I, I think there&#8217;s a huge opportunity there. One of the things we<br />tend to hear is, well, that&#8217;s not the kind of person we&#8217;re marketing to. And [00:17:00] you know,<br />there&#8217;s, there&#8217;s so much more than that going on with accessibility. It&#8217;s, you know, you may not<br />be marketing to &#8217;em right now, but who knows what&#8217;s going to happen in the future.<br />They, they, uh, or, or, um, friends that they have that, that kind of thing, they can help, um, push<br />along whatever product you&#8217;re pushing. And in those cases, so, you know, you&#8217;ve got, um,<br />you&#8217;ve got companies that come at it from that angle and, and there&#8217;s a little bit of education that<br />we have to do to help kind of get &#8217;em over that hump of this.<br />This is, this is a moral thing as well, . It&#8217;s, it&#8217;s not who you&#8217;re marketing to. It is that you are<br />marketing to everybody. Everyone&#8217;s going to see it, and it&#8217;s important that everybody be able to<br />see it.<br />Sarah Gless: Yeah, and I think that, like, going back to Mike&#8217;s original point, like it takes the<br />organization to do that.<br />It cannot be on the shoulders of like your web team. Um, yes, they are like [00:18:00] hands-on<br />producing and shipping that thing. Um, but that thing should be symbolic of like a much larger,<br />um, um, effort around accessibility. Um, and, and your kind of example around, you know,<br />posting your, your core values as a, as a company on the wall, um, and accessibility or<br />inclusivity being on that, um, kind of made me start to think like, what&#8217;s like a real example of, of<br />this.</p>



<p>Um, you know, like I, I. And transferring that responsibility, not transferring, but sharing that<br />responsibility across the organization means you have to figure out, like, how can each<br />department take part in that? Um, how can we better collaborate on that mission? Um, I think,<br />you know, I&#8217;ve spent a lot of times on and, and working with like brand and marketing teams,<br />great opportunity for, for, for people to get involved in accessibility that may not be, um, on the<br />line to like ship that, that website necessarily.<br />Um, for example, we mentioned, you know, calling out your brand [00:19:00] values. Maybe<br />you&#8217;ve got, you know, being inclusive as, as, as a brand value. Well back that up with like, you<br />know, shipping accessible designs on the marketing side. So like, if you&#8217;re working on a brand<br />book, um, A big part of that is establishing a color palette.<br />Um, and that color palette has implications across so much of your collateral across the<br />organization, including that website. Now, oftentimes what happens on like design, um, is that<br />we&#8217;re handed a brand book with colors we can&#8217;t use, and now we&#8217;re having to rework that<br />because accessibility was never consideration going into that.<br />Um, so that&#8217;s like a, a various, you know, tech like tactile example of, of how one little shift, you<br />know, like, and if your team doesn&#8217;t have the specialties to do that, that&#8217;s okay. Like lean on a<br />team of experts to help and collaborate on that. So bring in the web team into, you know, that<br />brand conversation and when you&#8217;re developing that color palette or, or whatever the thing is,<br />um, to get their [00:20:00] expertise and, and, and make sure that we&#8217;re living up to that kind of,<br />you know, core tenant of being inclusive and accessible.<br />And also, um, Beyond just being like the right thing to do. Like, you know, if you do work ahead,<br />the more you work ahead on accessibility, the more money you&#8217;ll save down the road, um,<br />because you don&#8217;t have to rework as much. So, um, definitely another, you know, kind of<br />business, um, opportunity.<br />Cory Miller: And I, I think, thanks for that.<br />Oh, Chris, go ahead.<br />Chris Kindred: Well, that, that just made me start thinking, um, one of the things is accessibility<br />doesn&#8217;t just stop with your digital things. Um, I, there&#8217;s, there&#8217;s a billboard I drive past or used to<br />drive past all the time, and I could barely read it because it was blue on blue and it just didn&#8217;t,<br />didn&#8217;t work well for, for me as I was driving a car 60 miles an hour past it.<br />I, I, if you&#8217;re going. Put that your, uh, that accessibility and, [00:21:00] and being inclusive as<br />part of your core values that trickles into your billboard, that trickles into the entryway to your<br />business, that that trickles into so many other things in order to prove it.<br />Sarah Gless: It&#8217;s a mind shift, isn&#8217;t it? Like when you, when you Yeah, when and, but it, but<br />once you start doing and getting the practice of that and resource for it, that&#8217;s a critical part of<br />this, right?<br />Um, you, it will become a habit. And, and that&#8217;s a good habit to have.<br />Cory Miller: And I keep shaping this mike in my mind as it&#8217;s a, it&#8217;s a problem, but if we can do it,<br />you just said Sarah and shift her mind, we go, this is an opportunity to show people we care. We<br />don&#8217;t have to put the word on there. If we do certain things like this, just like we&#8217;ve mentioned,<br />diversity, equity, inclusion, huge topic and rightly.<br />This is going, if we truly want to act on that, we need to think about that person who might be<br />blind and trying to ex, like you were talking about, you know, the color palettes and things. It&#8217;s to<br />that thought. [00:22:00] But Mike, it seems like too, I think Chris and Boer helped me today.<br />Like, let&#8217;s add another reason here.<br />This is a team Mork, Hey, we care. So we&#8217;re doing this accessibility project and, and other<br />initiatives in the business side of things that they can do to say, we&#8217;re not just gonna say it, we&#8217;re<br />gonna do it. I mean, this seems like when you go to your team, like Sarah was saying, and<br />you&#8217;re like, Hey, leadership has bought in on this and understands it.<br />Now we go to the team, we want, hey, we want everyone as best we can to do, to, to be able to<br />access things.<br />Mike Klanac: It&#8217;s a, it&#8217;s a foundational, um, shift in how you think about it. So a small example<br />would be we used to, um, ask, do you need your site to be accessible? And now we just<br />assume we&#8217;re gonna build accessible sites.<br />And we used to take a pass at estimating a project and then sort of like do some additional math<br />to calculate accessibility. Now we assume accessibility is a part of every estimate that [00:23:00]</p>



<p>you&#8217;re doing. Every line item of the feature level estimate incorporates accessibility thinking.<br />Um, and that&#8217;s, and that&#8217;s, that changes the approach.<br />It, it&#8217;s, it starts at the beginning. It carries through all the way to the end. And I, I think I would be<br />remiss not to mention one other topic on leadership that this conversation is sort of remind me<br />of, which is that these standards we&#8217;re talking accessibility is sort of this like, like just just this<br />open-ended term, but it, it means probably slightly different things.<br />And from a leadership standpoint, I think one other thing you need to really consider is what<br />standard are you, in some cases mandated to hit? And just understanding that is part of the<br />leadership obligation because you are the person that may often understand where you&#8217;re doing<br />business, what your jurisdictions are, um, what, what laws you&#8217;re bound to.<br />And if you&#8217;re as an international organization, we, we work with groups in Europe, we work with<br />groups [00:24:00] in California. We, we work with groups that have different sets of<br />requirements and different guidelines. So I think an important note for anyone who&#8217;s, who&#8217;s<br />gonna try to build this philosophy into their organization as they should, uh, is to, to like really<br />fundamentally set some clear guidelines to your team and say that based on where we do<br />business and where we&#8217;re approaching it, the way we&#8217;re approaching it, we&#8217;re gonna try to hit,<br />you know, stay tuned to section 5 0 8.<br />Um, And, and the, the outlines set in WIC AG two one, aa. Like we, there needs to be some<br />basis for what you&#8217;re aiming towards. Uh, it doesn&#8217;t, doesn&#8217;t mean that, um, you can&#8217;t go past<br />that. Um, but uh, you probably need to have that guiding light.<br />Cory Miller: Uh, and I think there&#8217;s a relief for me talking to you all on this too, because when I<br />know for instance, this is a value, right?<br />That we want to, that I love you, you said, uh, just it&#8217;s assumed. You know, [00:25:00] we&#8217;re in<br />2023 having this conversation. It doesn&#8217;t matter what&#8217;s been in the past today, this is just an<br />assumption that mind shift shift, um, but that it occurs to me, you know, as a leader and then<br />we&#8217;ve all kind of talked this and know this, we can&#8217;t know every single thing.<br />Like you&#8217;re talking about these specific legislation, policies, regulations out there. You can&#8217;t<br />possibly. So, but I wanna say there&#8217;s hope. That&#8217;s why we&#8217;re having this conversation. That&#8217;s<br />why there&#8217;s great experts in WordPress overall. Try being one of them that, um, can help<br />navigate some of those. Like it doesn&#8217;t need to be the, the thing that you keep up with at the<br />absolute.<br />That&#8217;s why you hire people like you all to even mention some of these things. Like I&#8217;ve been in<br />tech a long time and I learned something when I&#8217;m talking about when to you all about these<br />things that I hadn&#8217;t considered. And I think that&#8217;s a maybe a sense. Is like, there&#8217;s a little bit of<br />relief you can say like you want to do the right thing.<br />That&#8217;s why you go seek out experts that do. That&#8217;s why I&#8217;ve enjoyed preparation about this. I&#8217;ve<br />learned [00:26:00] a ton that I wouldn&#8217;t even considered . Like Sarah, you were talking about the<br />brand and I go more design Chris than tech sometimes, cuz I don&#8217;t know what I&#8217;m talking about<br />with tech all the time. But I go take this thought and go to your brand values.<br />We have oranges ours, but I have no idea how that expresses itself necessarily. Right. Uh, on<br />the web for someone that&#8217;s hurt and that&#8217;s a holistic thinking. We&#8217;re thinking like we, we&#8217;ve hit<br />this do do good and it&#8217;s got a pretty dang good benefit because it&#8217;s like absolutely. You can<br />actually reflect and show what you&#8217;re doing.<br />So.<br />Sarah Gless: Absolutely. Um, yeah. And you mentioned like. Kind of like leaning on on experts.<br />And that ki kind of got me thinking, like, I think there&#8217;s this expectation. Um, I know design<br />designers put this expectation on them to, to, um, sometimes to, to be able to like have<br />expertise in this. And like we absolutely have to have, you know, baseline knowledge and, and<br />skills that apply to [00:27:00] our work to meet accessibility.<br />But, um, you know, as an organization, if you&#8217;re in a marketing team, um, for example, and<br />you&#8217;re like, do I, do I need to know everything about accessibility? No. And there&#8217;s no, I mean,<br />accessibility is a, you know, a full team of effort. Um, yeah. Um, at Modern Tribe, we&#8217;ve got a full<br />dedicated QA team that is testing rigorously everything we design and build.<br />Um, so, so no. But can you get to a place where you&#8217;ve got like a good baseline knowledge of<br />accessibility and or also like resources that you know you can turn to, whether it be, um, your<br />own team internally that&#8217;s focused on accessibility, your leadership has resource for awesome.</p>
