


<img />



<p>After registering the CPT, users can then add an existing or new field group for it or create a taxonomy, and move on from there. The advantage is that users don&#8217;t have to break their workflows and use a different plugin for this functionality. For those managing client websites, it is one fewer plugin required. </p>



<p>&#8220;We know there are a large number of ACF users registering custom post types (CPTs) and creating custom fields for them,&#8221; WP Engine Senior Product Manager Iain Poulson said. &#8220;But they have to register the CPTs either manually with code or using another plugin. The overarching workflow of modeling the data needed for a site build is fragmented between different plugins, UIs, and user experiences. We wanted to fix that!&#8221;</p>



<p>The ACF development team has also created a <a href="https://www.advancedcustomfields.com/resources/post-types-and-taxonomies/#disabling-cpts-taxonomies">dedicated import tool</a> for users who want to migrate post types and taxonomies from the <a href="https://wordpress.org/plugins/custom-post-type-ui/">Custom Post Type UI</a> (CPTUI) plugin to ACF in order to manage them all from one plugin.  ACF has also built in the ability to <a href="https://www.advancedcustomfields.com/resources/acf-settings-enable_post_types/">disable post types and taxonomies from the plugin admin</a> in case users do not require this feature in the update.</p>



<p>ACF reports more than 4.5 million users, so it will be interesting to see how having this built in will impact the CPTUI user base, which is active on more than a million websites. Some users simply need custom post types but won&#8217;t require all of ACF&#8217;s capabilities, but there is certainly a large overlap between the two plugins.</p>



<p>After expanding well beyond the creation of custom fields with this and previous updates, Poulson said they will be referring to the plugin as &#8220;ACF&#8221; more going forward. The plugin&#8217;s admin sidebar menu has been updated from &#8220;Custom Fields&#8221; to ACF.</p>



<p>Version 6.1 also includes the following highlights and important changes:</p>



<ul>
<li>New &#8216;browse fields&#8217; button opens a modal to search and showcase all field types</li>



<li>Post Object, Page Link and Relationship fields now support filtering by post status</li>



<li> Full compatibility with PHP versions 8.1 and 8.2</li>



<li>New option to filter field settings tabs so other plugins can add custom tabs and arrange their fields</li>



<li>Security fix backported to ACF 5.12.5 for a security issue where ACF might unserialize maliciously manipulated data which instantiates a class</li>
</ul>



<p>All of these new features are available in both the free version and ACF Pro. Check out the <a href="https://www.advancedcustomfields.com/changelog/">changelog</a> for the full rundown of everything included in version 6.1.</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, 05 Apr 2023 21:21:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:101:"Post Status: Build a Block Theme • Theme Performance Improvements * Interactivity API • Why Jazz?";s:7:"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=148717";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:101:"https://poststatus.com/build-a-block-theme-theme-performance-improvements-interactivity-api-why-jazz/";s: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:19892:"<h2 class="wp-block-heading" id="h-this-week-at-wordpress-org-april-3-2023">This Week at WordPress.org (April 3, 2023)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">Matt shares why WordPress releases are named after jazz musicians. The FSE block theme explores functionality gaps and gathers feedback on the Site Editor experience. WordPress 6.2 improves load times and server-side performance for block and classic themes. The Interactivity API proposal standardizes frontend interactivity for Gutenberg blocks. </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_paint-brush kt-info-svg-icon"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title">Build a Theme, Time to First Byte, Jazz, and Interactivity API</h2><p class="kt-blocks-info-box-text"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f9b8-1f3fb-200d-2640-fe0f.png" alt="🦸🏻‍♀️" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/04/07/preparing-for-the-next-women-nonbinary-release-squad/">Preparing for the Next Women &amp; Nonbinary Release Squad</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f477-1f3fe.png" alt="👷🏾" class="wp-smiley" /> <a href="https://make.wordpress.org/test/2023/03/29/fse-program-exploration-build-a-block-theme/">FSE Program Exploration: Build a block theme</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f680.png" alt="🚀" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/04/05/wordpress-6-2-performance-improvements-for-all-themes/">WordPress 6.2 Performance improvements for all themes</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f3b7.png" alt="🎷" class="wp-smiley" /> <a href="https://make.wordpress.org/design/2023/03/30/why-jazz/">Why Jazz?</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f7e6.png" alt="🟦" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/">Proposal: The Interactivity API – A better developer experience in building interactive blocks</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f469-1f3fb-200d-1f4bb.png" alt="👩🏻‍💻" class="wp-smiley" /> <a href="https://make.wordpress.org/cli/2023/04/05/wp-cli-v2-8-0-release-date/">WP-CLI v2.8.0 release date</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 class="wp-block-heading" id="h-news"><a href="https://wordpress.org/news">News</a></h2>



<ul>
<li><a href="https://wordpress.org/news/2023/04/the-month-in-wordpress-march-2023/">The Month in WordPress – March 2023</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="wp-block-columns is-layout-flex wp-container-8">
<div class="wp-block-column is-layout-flow">
<h2 class="wp-block-heading" id="h-accessibility"><a href="https://make.wordpress.org/accessibility">Accessibility</a></h2>



<ul>
<li><a href="https://make.wordpress.org/accessibility/2023/04/05/accessibility-team-meeting-agenda-april-7-2023/">Accessibility Team Meeting Agenda: April 7, 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-central"><a href="https://wordcamp.central.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>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/community/2023/04/07/its-time-to-plan-your-wp20-anniversary-celebration/">It’s Time to Plan Your WP20 Anniversary Celebration!!</a></li>



<li><a href="https://make.wordpress.org/community/2023/04/06/personalised-coupon-codes-for-wordcamps/">Personalised Coupon Codes for WordCamps</a></li>



<li><a href="https://make.wordpress.org/community/2023/04/03/community-team-training-7-community-team-roles-overview-discussion/">Community Team Training #7: Community Team Roles Overview &amp; Discussion</a></li>



<li><a href="https://make.wordpress.org/community/2023/04/01/wordcamp-mentors-april-check-in/">WordCamp Mentors’ April check-in!</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/04/07/preparing-for-the-next-women-nonbinary-release-squad/">Preparing for the Next Women &amp; Nonbinary Release Squad</a></li>



<li><a href="https://make.wordpress.org/core/2023/04/05/whats-new-in-gutenberg-15-5-05-april/">What’s new in Gutenberg 15.5? (05 April)</a></li>



<li><a href="https://make.wordpress.org/core/2023/04/05/wordpress-6-2-performance-improvements-for-all-themes/">WordPress 6.2 Performance improvements for all themes</a></li>



<li><a href="https://make.wordpress.org/core/2023/04/04/a-week-in-core-april-3-2023/">Two Weeks in Core – April 3, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/04/03/preferred-languages-help-test-the-latest-version/">Preferred Languages: Help test the latest version</a></li>



<li><a href="https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/">Proposal: The Interactivity API – A better developer experience in building interactive blocks</a></li>
</ul>



<h3 class="wp-block-heading" id="h-meetings">Meetings</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2023/04/04/editor-chat-agenda-april-5th-2023/">Editor Chat Agenda: April 5th, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/04/06/dev-chat-summary-april-5-2023/">Dev Chat Summary, April 5, 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/design/2023/03/30/why-jazz/">Why Jazz?</a></li>
</ul>



<h2 class="wp-block-heading" 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/updates/2023/04/03/documentation-team-update-april-3-2023/">Documentation Team Update – April 3, 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-hosting"><a href="https://make.wordpress.org/hosting">Hosting</a></h2>



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



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



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



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



<ul>
<li><a href="https://make.wordpress.org/meta/2023/04/06/matrix-chat-summary-april-6-2023/">Matrix chat Summary, April 6, 2023</a></li>



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



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



<ul>
<li><a href="https://make.wordpress.org/updates/2023/04/07/mobile-team-update-april-6th-2/">Mobile Team Update – April 6th</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/openverse/2023/04/05/community-meeting-recap-2023-04-04/">Community Meeting Recap (2023-04-04)</a></li>



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



<li><a href="https://make.wordpress.org/openverse/2023/03/30/community-meeting-recap-28-march-2023/">Community Meeting Recap (28 March 2023)</a></li>



<li><a href="https://make.wordpress.org/openverse/2023/03/29/openverse-monthly-priorities-meeting-2023-04-05/">Openverse Monthly Priorities Meeting 2023-04-05</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/04/05/performance-chat-summary-04-april-2023/">Performance Chat Summary: 4 April 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-plugins"><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/04/04/plugin-review-team-3-april-2023/">Plugin Review Team – 3 April 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/polyglots/2023/04/05/agenda-weekly-polyglots-chat-april-05-2023-0700-utc/">Agenda: Weekly Polyglots Chat – April 05, 2023 (07:00 UTC)</a></li>
</ul>
</div>



<div class="wp-block-column is-layout-flow">
<h2 class="wp-block-heading" 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 class="wp-block-heading" id="h-support"><a href="https://make.wordpress.org/support">Support</a></h2>



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



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



<ul>
<li><a href="https://make.wordpress.org/test/2023/04/04/hallway-hangout-lets-chat-about-moving-to-the-site-editor/">Hallway Hangout: Let’s chat about Moving to the Site Editor</a></li>



<li><a href="https://make.wordpress.org/test/2023/03/29/fse-program-exploration-build-a-block-theme/">FSE Program Exploration: Build a block theme</a></li>



<li><a href="https://make.wordpress.org/updates/2023/04/03/test-team-update-3-april-2023/">Test Team Update: 3 April 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-theme">Theme</h2>



<ul>
<li><a href="https://make.wordpress.org/themes/2023/04/04/theme-handbook-overhaul-proposal/">Theme Handbook Overhaul Proposal</a></li>



<li><a href="https://make.wordpress.org/updates/2023/04/04/themes-team-update-april-04-2023/">Themes team update April 04, 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/training/2023/04/07/next-steps-for-the-faculty-program/">Next Steps for the Faculty Program</a></li>



<li><a href="https://learn.wordpress.org/learn-wordpress-april-2023-newsletter/">Learn WordPress April 2023 Newsletter</a></li>



<li><a href="https://make.wordpress.org/training/2023/04/05/proposal-creating-learning-pathways-for-learn-wordpress/">Proposal: Creating Learning Pathways for Learn WordPress</a></li>



<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/04/03/meeting-agenda-for-april-04-2023/">Meeting agenda for April 04, 2023</a></li>



<li><a href="https://make.wordpress.org/updates/2023/04/01/whats-new-on-learn-wordpress-in-march-2023/">What’s new on Learn WordPress in March 2023</a></li>
</ul>



<h3 class="wp-block-heading" id="h-lesson-plans"><a href="https://learn.wordpress.org/lesson-plans">Lesson Plans</a></h3>



<ul>
<li><a href="https://learn.wordpress.org/lesson-plan/ar-dashboard-overview/">نبذة عن لوحة البيانات </a></li>
</ul>



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



<ul>
<li><a href="https://learn.wordpress.org/tutorial/using-block-patterns/">Using Block Patterns</a></li>



<li><a href="https://learn.wordpress.org/tutorial/add-media-and-openverse-images-to-your-content-directly-from-the-inserter/">Add media and Openverse images to your content directly from the Inserter</a></li>



<li><a href="https://learn.wordpress.org/tutorial/wordpress-rest-api-custom-routes-endpoints/">WordPress REST API – custom routes &amp; endpoints</a></li>



<li><a href="https://learn.wordpress.org/tutorial/intro-to-the-site-editor-and-template-editor/">Intro to the Site Editor and Template Editor</a></li>



<li><a href="https://learn.wordpress.org/tutorial/how-to-use-the-wordpress-stylebook-with-your-block-theme/">How to use the WordPress Stylebook with your block theme</a></li>
</ul>



<h3 class="wp-block-heading" id="h-online-workshops">Online Workshops</h3>



<ul>
<li><a href="https://learn.wordpress.org/?meeting=how-to-validate-content-feedback-for-the-wordpress-training-team">How to validate content feedback for the WordPress Training Team</a></li>



<li><a href="https://learn.wordpress.org/?meeting=33114">WordPress 6.2 のアップデート内容を見てみよう！</a></li>



<li><a href="https://learn.wordpress.org/?meeting=wordpress-6-2-%E3%81%AE%E3%82%A2%E3%83%83%E3%83%97%E3%83%87%E3%83%BC%E3%83%88%E5%86%85%E5%AE%B9%E3%82%92%E8%A6%8B%E3%81%A6%E3%81%BF%E3%82%88%E3%81%86%EF%BC%81">WordPress 6.2 のアップデート内容を見てみよう！</a></li>



<li><a href="https://learn.wordpress.org/?meeting=updating-a-blogs-design-informal-live-stream-part-4">Updating a blog’s design (Informal live stream) – Part 4</a></li>



<li><a href="https://learn.wordpress.org/?meeting=the-wordpress-request-lifecycle-2">WP dev livestream: WordPress request lifecycle</a></li>



<li><a href="https://learn.wordpress.org/?meeting=the-wordpress-request-lifecycle">The WordPress request lifecycle</a></li>



<li><a href="https://learn.wordpress.org/?meeting=a-guide-to-open-source-and-wordpress-timezone-2">A Guide to Open Source and WordPress (Timezone 2)</a></li>



<li><a href="https://learn.wordpress.org/?meeting=a-guide-to-open-source-and-wordpress">A Guide to Open Source and WordPress</a></li>
</ul>



<h3 class="wp-block-heading" id="h-courses"><a href="https://learn.wordpress.org/courses">Courses</a></h3>



<ul>
<li><a href="https://learn.wordpress.org/course/converting-a-shortcode-to-a-block/">Converting a Shortcode to a Block</a></li>
</ul>



<h2 class="wp-block-heading" id="h-wp-cli">WP-CLI</h2>



<ul>
<li><a href="https://make.wordpress.org/cli/2023/04/05/wp-cli-v2-8-0-release-date/">WP-CLI v2.8.0 release date</a></li>
</ul>



<h2 class="wp-block-heading" 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 class="wp-block-heading" 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://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, 05 Apr 2023 19:30:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:31;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"WPTavern: #70 – Steve Persch and Brian Perry on How Hosting Is Changing";s:7:"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=143278";s:7:"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/podcast/70-steve-persch-and-brian-perry-on-how-hosting-is-changing";s: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:53090:"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, the past and future of website hosting.</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 show, I&#8217;m keen to hear from you and hopefully get you all your idea on the podcast as soon as possible. Head over to WPTavern.com forward slash contact forward slash jukebox, and use the form there.</p>



<p>So on the podcast today, we have Steve Persch and Brian Perry. They&#8217;re both employed at Pantheon, an enterprise website operations platform. And they&#8217;re here to talk about the evolution of website hosting.</p>



<p>Back when the internet started, hosting was a fairly straightforward enterprise. You created HTML files and uploaded them to a server. That was it. An HTML file was a page.</p>



<p>Server-side technology such as PHP came along, and the picture became a little more complex. Web pages needed to be constructed on the fly. Databases were thrown into the mix, and the complexity increased. Add in the different languages that you could write your code in, and the server configurations. The CMS that you choose also plays into this mix. Now we&#8217;ve got CDNs, headless, React, Gatsby, Node.js and much more. Is it even possible for the non-technical to have any understanding of where their website is?</p>



<p>Steve and Brian talk about how they got into the hosting space, and what&#8217;s changed over the years. We address what Pantheon is doing with WordPress and Drupal.</p>



<p>We discuss how headless can be difficult for content teams, given that there&#8217;s a disconnect with hitting the publish button and that content going live on the site.</p>



<p>What&#8217;s certain is that there&#8217;s no end in sight in terms of the rate of innovation in the website hosting space. What&#8217;s popular today might not be several years from now. And so it&#8217;s a timely discussion of what Steve and Brian see as the best bets for the future.</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 Steve Persch and Brian Perry.</p>



<p>I am joined on the podcast today by Steve Persch and Brian Perry. Hello.</p>



<p>[00:03:37] Steve Persch: Hello, Steve Persh here. Happy to be here.</p>



<p>[00:03:39] Brian Perry: Yeah, Brian Perry also really excited to chat.</p>



<p>[00:03:42] Nathan Wrigley: Well, thank you for joining me on the podcast today. We&#8217;re going to talk about something, and I seem to have said this sentence much more often recently, about something that that really is a mystery to me. You are going to school me in all sorts of ways about something that I&#8217;m really not that familiar with, and that is all about how files get served up. Where are our website files being kept? Where are the computers? Where&#8217;s the infrastructure, and how much more complicated it has become over the last 10 or 15 years.</p>



<p>Before we begin that, I think we&#8217;ll take you in order. I&#8217;ll go Steve first, if that&#8217;s all right? I&#8217;m wondering if both of you can give us a little bit of orientation about who you are, who you work for. Your history with technology and possibly WordPress in particular. So yeah, we&#8217;ll launch that with Steve.</p>



<p>[00:04:28] Steve Persch: Sure, so Steve Persch here in Minneapolis, Minnesota. I&#8217;m the director of technical marketing at Pantheon. We&#8217;re a website operations platform for Drupal, WordPress and now front end frameworks, which is, much of what, thinking about that question of what computer makes the website.</p>



<p>I&#8217;ve been in the web space for a while now. I first started making websites, first semi-professionally, and then professionally in the early days of WordPress. I built some of my first professional websites in WordPress 2, back in 2006. Then for some of the sites that I wanted to make, that took me into the Drupal world. And now in Pantheon, we play in both of those worlds, in the lamp stack, and as Pantheon is aiming itself at running extraordinary websites, as we like to say, the best possible websites. We see that that requires us to step more fully into the JavaScript centric front end framework ecosystem.</p>



<p>[00:05:23] Nathan Wrigley: Well thank you Steve. That was great. We&#8217;ll hand it over to Brian to do a similar job.</p>



<p>[00:05:28] Brian Perry: I&#8217;m Brian Perry. I&#8217;m a staff software engineer at Pantheon. What I&#8217;m focusing on at Pantheon is leading a project we&#8217;re calling Decoupled Kit, which is a set of open source utilities and projects that aim to make this decoupled architecture or running headless WordPress and Drupal sites easier.</p>



<p>What brought me to that is, prior to Pantheon, a lot of my background was in the agency space. Specifically focusing on front end and front end develop. More and more I found myself interested in what was going on in the JavaScript ecosystem, and working on projects where using a CMS like WordPress or Drupal to feed data into the front end. But also found that there were a lot of solutions that were being invented over and over to solve those problems. So being able to focus on trying to make that easier for folks has been really exciting.</p>



<p>[00:06:24] Nathan Wrigley: Thank you very much indeed. So you&#8217;re both coming from Pantheon and you mentioned there that you have a very keen focus on, well you mentioned two CMSs, which is curious actually. Obviously this is a WordPress podcast, but we&#8217;re not here to destroy the opposition if you like. But Drupal and WordPress, I think I&#8217;m right in saying that you don&#8217;t find too many hosting companies that lay claim to both of those. Is that a relic of the past of Pantheon, how it all began back in the day?</p>



<p>[00:06:51] Steve Persch: It&#8217;s an intentional choice. We think that supporting both of those systems gives us more flexibility. It ends up fitting us better to our core audience. Pantheon started with digital agencies. Our four founders came from running web development agencies, that&#8217;s the background.</p>



<p>And for a lot of the agencies and in the ecosystems we came from, we knew that it was normal for those sorts of agencies to have a preference between Drupal, WordPress or, you know, Ruby and Rails or any other of system. But often, the given client you&#8217;re working for might have both, for any number of historical reasons.</p>



<p>So yes, the initiation of that was, uh, somewhat happenstance. Our customers figuring out like, this platform was first built for Drupal, I bet we could make it run WordPress. And then Pantheon as a company realizing like, yes, we should support WordPress. That&#8217;s something that I think was a bit inevitable.</p>



<p>It&#8217;s good for us technologically and business wise to support more than one. And at the same time it&#8217;s good for us to not open it up as wide as, well, anything PHP. Some of our competitors take the other extreme of, hey, if you can make it run then you&#8217;re good. We think of ourselves as, we prefer the term, a website operations platform.</p>



<p>And hosting is a feature of that. But don&#8217;t want to have a relationship with our customers that&#8217;s as simple as like, well, yeah, if you can make it run, that&#8217;s good. We&#8217;re only here to provide the server. We see ourselves as facilitating more growth of value of the websites, not just the question of can this run at all?</p>



<p>[00:08:21] Brian Perry: Yeah, I think that, that same sort of concept also extends to the front end and JavaScript frameworks in that, there&#8217;s definitely a lot of excitement around Next.js. But we are looking to build a platform where other future frameworks can run on it. But also, yeah, we&#8217;re not necessarily trying to be like, run whatever crazy JavaScript project you want. We want to have some guardrails there.</p>



<p>[00:08:44] Nathan Wrigley: I remember back in the day prior to stumbling across WordPress, which I did quite a long time ago now, I used to use Drupal exclusively actually, and I have a, have a memory of Pantheon cropping up, and at the time, really hadn&#8217;t heard of a hosting company that was binding itself to a CMS in that way.</p>



<p>It was curious to me that Pantheon had laid claim to, okay, if you&#8217;re using a CMS, we&#8217;re somebody that you should look at. Prior to that, it was always, we&#8217;re just a hosting company. You know, we&#8217;ll host anything.</p>



<p>[00:09:16] Steve Persch: I often go back to the first blog post that was done by, one of our co-founders, our four co-founders, when Pantheon started. I think the title of the blog post was Putting the Humans at the Top of the Stack. And it laid out, or at the time, but a decade plus ago, two common ways of running websites.</p>



<p>One was just that hosting mode of a host providing some baseline technological capabilities, but the team buying the hosting is responsible for assembling the parts and making it all work. And yes, that&#8217;s an appropriate choice for some teams, but it&#8217;s not a great recipe for success for what we see as the broad plurality of professional web teams.</p>



<p>The other extreme at the time, and it&#8217;s still present there, is the Squarespace, Wix, very templatized, cookie cutter way of building a site. Which again, is totally appropriate for certain people who need websites. But Pantheon, a decade ago and still now, wants to find a middle path that empowers the majority, or a plurality of professional web teams to make the best possible websites.</p>



<p>And we see that, fulfilling that mission does require us to build CMS specific capabilities, and now front end framework specific capabilities, while not putting ourselves as narrow as only WordPress, or only Next.js.</p>



<p>[00:10:35] Nathan Wrigley: Okay. That&#8217;s really interesting. Thank you for that. The subject at hand is really about how hosting has changed over the last decade, two decades, what have you. And it might be of interest to the listeners to the podcast if they pause for a moment and go and watch one of the videos. It was created by Steve, I believe, created the video.</p>



<p>It&#8217;s called Decoupled Architectures, What Computer Assembles the website, and it&#8217;s a great watch. It&#8217;s. 10 minutes long, and it&#8217;ll give you a real insight into the things that we&#8217;re going to talk about. What Steve brings to bear is lots of papers and drawing, which we can&#8217;t do on this podcast, but they really do help solidify the problem. He&#8217;s got lots of nice diagrams of how things are working.</p>



<p>But just to rewind the clock, let&#8217;s go back 20 years or so ago. It seems like an age almost at the birth of the internet almost. But if you had a website, whatever CMS it was. You would have to host it somewhere, and you would probably select a host and upload the files.</p>



<p>They were probably at that point, just static HTML. I imagine CSS probably hadn&#8217;t even emerged at that point. And you just uploaded them. And you had a great idea of where that computer was. You had a slice, a share of that computer. It was yours. You could point to where it was on the map and so on and so forth.</p>



<p>And that&#8217;s not how it&#8217;s done now. Or at least that&#8217;s not how everybody&#8217;s doing it. So I want us to run through a history of how that&#8217;s changed over time. Going right back from the beginnings when the internet began and you could build your own websites. Right up to how it&#8217;s done now. We can really be ponderous about this, we&#8217;ve got a whole episode ahead of us. So, whoever wants to begin that journey, you can flip flop and change, do tag team if you like, but that&#8217;s what I want to do. The history of how hosting has changed.</p>



<p>[00:12:19] Steve Persch: Brian, if you don&#8217;t mind, I&#8217;ll start from flat HTML files, and enter us into the era of PHP. And then you can talk about CMSs. So one of my first experiences getting paid to maintain a website, a thing, I wasn&#8217;t even pondering as a career path. I was a theater major, and then I found myself working in the marketing department of a theater company. And they had a flat HTML website that did the job, was good enough for the early two thousands. A few hundred pages of flat HTML files, mostly it&#8217;s like if you want to buy tickets, call this phone number. Here&#8217;s the production that we&#8217;re producing, here&#8217;s the calendar.</p>



<p>And one of the most annoying tasks, once I became the person getting paid to update the website was, add this menu link in the sidebar. And that sidebar appears on like a dozen pages. Okay, so I open up a dozen flat HTML files and then I notice, oh, this sub sidebar menu for the education department of the theater company. This menu isn&#8217;t even consistent on these 12 HTML files, because over however many years, copy paste errors happened. And that&#8217;s annoying, and creates a bad, confusing experience.</p>



<p>But, I know enough to realize that I could put in some PHP tags, and save myself some time. That&#8217;s how I first started transitioning that question of, what computer assembles the website? How does this website really come together? The first answer of, it&#8217;s all flat HTML that I&#8217;ve got to hand code on my own machine to, what if I put a little bit more, just a little bit more intelligence in the server and told it to like PHP include education sub sidebar dot PHP.</p>



<p>Then I don&#8217;t have to worry about copy pasting menu updates across 12 HTML files. That started to transition the question of what computer assembles the website, but the content management systems that were cropping up at the same time, WordPress, Drupal, others, provided a much more robust answer. But I can let Brian talk about that.</p>



<p>[00:14:25] Nathan Wrigley: I&#8217;ll just interject at that point because the pain that you&#8217;ve just described was my pain. I remember exactly that. I mean, it wasn&#8217;t the 200 page website, but I remember the exact same thing. And then stumbling across the, oh, you can include something with PHP can you? That will take that whole burden, maybe the header or the footer or wherever it may be on the website.</p>



<p>And I do remember finding that really quite startling, and thinking good grief. I&#8217;ve just saved myself literally hours of time, and it was fabulous. It was really, really an excellent moment. So, okay, so.</p>



<p>[00:15:00] Brian Perry: It&#8217;s also a, it&#8217;s a gateway to the danger of creating your own CMS, I don&#8217;t know if anybody on this has done that?</p>



<p>[00:15:07] Nathan Wrigley: Yes, that&#8217;s exactly what I did. We&#8217;ve laid the pathway then to, we&#8217;ve got PHP in there somehow now, and so now we&#8217;re moving towards CMSs. So I guess we&#8217;ll hand it to Brian to tell us what came next.</p>



<p>[00:15:19] Brian Perry: Yeah, and Steve, feel free to jump in as the overall tour guide with any color commentary. But yeah so, many of us have rolled our own CMSs. But then projects like WordPress and Drupal come along and provide a consistent user experience to being able to manage your data. Have an associated front end.</p>



<p>It&#8217;s the great situation where there&#8217;s a community of folks making that project better, rather than the CMS we built on our own. That is a situation where you have your CMS, that handles that data. But it is essentially a single lamp stack. And your CMS is responsible for assembling your website. So you can edit things in the admin. But at the end of the day, WordPress, for example, is what puts everything together, using its templates and providing the end page that the user interacts with.</p>



<p>[00:16:15] Steve Persch: Another way I think about this progression is through the lens of the three really broad groups of people who make a website like this possible. Especially in those early PHP days, to make something like this work there&#8217;s someone probably with an IT sort of job title who&#8217;s setting up the server. There&#8217;s someone with like a web developer type of job title who&#8217;s making the Drupal or WordPress part work, and they may be working with designers as well. And then there are people managing the content.</p>



<p>So in addition to what computer assembles the website, a more specific framing is where is the work of these three broad groups of people coming together? It&#8217;s coming together over and over and over and over again, to make a functioning website. And in the lamp stack era, it&#8217;s that PHP server, you know, be it shared hosting or a server in the closet. That is where the work of those three groups has to fit together.</p>



<p>And for the decade or so that the lamp stack was dominant, there became pretty solidified best practices on how those three groups need to work together in order to do their jobs most effectively.</p>



<p>[00:17:26] Nathan Wrigley: I feel that&#8217;s a really nice segregation of the different things that were going on. But also it makes the two bits that you are not involved with suddenly quite mysterious. If you&#8217;re the content editor, suddenly the IT bit, the hosting if you like, you&#8217;re no longer involved in that in any way. And, so that over time becomes a little bit more murky and what have you.</p>



<p>But the advent of the CMS suddenly opened up a whole range of possibilities for people who really don&#8217;t have any technical, they don&#8217;t desire to be technical. They want to be consumed with the content. They want to log into something, type away, upload images, what have you, and press publish, and for it to be done.</p>



<p>So I think that&#8217;s a really useful definition. Prior to that, you had to be fairly technical, at least technically enough to create the HTML and what have you, to then upload it to the server. And now we&#8217;ve got a kind of career path coming out of it, haven&#8217;t we? We&#8217;ve got the IT people, we&#8217;ve got the editor people, and various other different pieces of the puzzle.</p>



<p>It feels like maybe that is where quite a few people will still be with WordPress. That is to say they&#8217;ve got a WordPress website, they&#8217;re paying a monthly fee to a hosting company. That hosting company is literally holding the files of the CMS, in our case, WordPress. Holding them on a particular box somewhere. The DNS is pointed correctly. It all works. That set up is still doable, but I guess the journey doesn&#8217;t end there. I suppose we&#8217;ve got quite a long way to go in this journey.</p>



<p>[00:18:59] Steve Persch: Yeah, the journey does not end there. Actually it might, because it comes back around. There are other steps along the way. So, I see the next big event in this history as the release of the iPhone. Which for a while I wondered like, am I drawn to that as the key moment? Because that&#8217;s when I was coming into professional web development, around 2007. In the decade plus remove, I can see, no, that really was a big deal when we had to figure out how to make websites squish, and fit on different size devices. Phones, tablets, Android devices of every single size and resolution.</p>



<p>That was a huge change. And it came about at the same time these native application ecosystems sprung up, and really, really raised the bar for how good of an experience you could have on these devices. So not only is this just a new form factor to make work at all. The quality bar jumps up very, very high. In retrospect, I can see like, oh, that set off a bit of a panic in the web development community. And different people reacted in different ways and, you look at the 2010s and think, oh yeah, people ran in a bunch of different directions trying to handle or deal with the existential question of, how does the web stay relevant when literally billions of dollars are pushing technology towards native applications.</p>



<p>[00:20:33] Nathan Wrigley: I feel there&#8217;s some other pieces I might add into that as well, and that is, the invention of the iPhone, which then spawned so many other similar devices, some slightly larger, some competing operating systems. But the thing there was suddenly the internet went from something which was probably peripheral in your life.</p>



<p>You would interact with it, maybe with email or something at work. You&#8217;d have to turn on a computer and sit in a chair. And the internet would be on that screen and then you&#8217;d walk away from it and you&#8217;ve forgotten about the internet. Suddenly you&#8217;re at a point where the internet is with you 24 7, should you wish. It&#8217;s there all the time. So it marks a moment where not only is it technically possible to do it, but it increases the importance in everybody&#8217;s lives. So, almost everything now, what are we now about 15 years later or something?</p>



<p>Almost everything can have a web presence. You know, you were talking about buying tickets earlier. Well, what&#8217;s the best way to do that now? It&#8217;s the internet. How do you consume your radio? It&#8217;s the internet. Where does your entertainment come from? It&#8217;s the internet. There&#8217;s almost nothing, which the internet hasn&#8217;t touched, and I feel that that was the inflection point when it went in your back pocket and suddenly every company on earth had a window into everybody&#8217;s lives.</p>



<p>[00:21:50] Brian Perry: It&#8217;s a blessing and a curse.</p>



<p>[00:21:52] Nathan Wrigley: But also a convergence of the technology, you know. So cellular data was suddenly getting rolled out. Prior to that it was just mobile phones was as, as much as you could do. You could do voice chat and so on. But then mobile data came along and it all coincided at the same time. So I, yeah, Steve, I think that&#8217;s a really insight thing. The iPhone being this moment.</p>



<p>[00:22:09] Steve Persch: So the iPhone, when it comes out, it suddenly becomes the most powerful computer in the whole stack. If you&#8217;re thinking about what can we make a website or a native application? What can I do with this device? A lot of people consciously or unconsciously realized if we push more responsibility to this last computer in the chain. From the developer&#8217;s computers. There are still servers involved.</p>



<p>There are increasing number of computers in the cloud that are involved in getting the website to that iPhone. But the iPhone in many respects, the most powerful computer in the whole stack, and that leads to an architecture of, oh, let&#8217;s make that end device, be it a laptop, a high powered iPhone or a low powered budget Android phone. Let&#8217;s put all the responsibility there. Brian, I bet you could talk in greater detail about the upsides and the downsides of the single page application architecture that came about when a lot of the web development ecosystems said, oh, let&#8217;s put all the responsibility in the client, in the end device.</p>



<p>[00:23:16] Brian Perry: Yeah, there&#8217;s definitely like a huge trade off to that in that the end result that we&#8217;re doing there, especially thinking about modern JavaScript frameworks, were essentially pushing more responsibility, more code, more JavaScript to that end device. So there&#8217;s more places where things could potentially go wrong.</p>



<p>There&#8217;s more cases where rather than having just a HTML document that is passed from a device to device, it actually has responsible, responsibility for rendering the page and executing all of that code. And it&#8217;s even a situation where things as simple as being able to click the back button in your browser to go to the previous HTML document, that&#8217;s things that need to be handled within that client device.</p>



<p>So it really does increase the complexity there. And then also related to what we&#8217;ve been talking about and thinking about, the three audiences that we talked about before. One thing that jumped out to me is that as we&#8217;re finding all of these, you know, the internet everywhere, and all of these, different devices that can be used for these different purposes. I think some of also what brings us to the headless architectures that we&#8217;re going to get to down the line, is in some ways, I think driven by the content editor. In that they still want to have one place where they can go and manage content that is going to show up in all of these different places.</p>



<p>Whether it&#8217;s a client side page, a traditional website, things managed by PHP, and I think that also does start to lead us in the direction of how can we manage this content in one place and make that data available to all kinds of different consumers.</p>



<p>[00:25:01] Nathan Wrigley: So we have the, we have the iPhone, and prior to that we have just regular servers. I guess we&#8217;ve now got to take a bit of a leap and stray into an area where maybe many of us really don&#8217;t know what we&#8217;re talking about, and I&#8217;ve very much include myself in this. What are the evolution of things that have happened subsequently since the iPhone?</p>



<p>And what was the purpose of all of that? Were there things which were tried and failed? And I suppose we are slowly getting towards the present day, but if there&#8217;s been some interesting evolutions during that time which need to be mentioned to give context, please do.</p>



<p>[00:25:35] Steve Persch: Absolutely, I think one dynamic that played out in the 2010s was the splintering of all these different disciplines. I said in that lamp stack era, there are these three broad groups, of IT and content editors and developers. And I was even lumping in designers with the developers there.</p>



<p>There might be some designers who take offense to that, but you know, it&#8217;s a blurry line. I lump them together because at a very, a very zoom out level that that&#8217;s the group that&#8217;s responsible for controlling how the website looks. And the handoffs that happened between designer and developer have changed over the years.</p>



<p>But in the 2010s, there&#8217;s just an incredible splintering of the amount of detailed knowledge necessary to make websites look good across all these different devices was so large it was just unreasonable to think that you can hire one human being to know how to even implement a good design across all of these devices.</p>



<p>Who also knows how to, like, configure Advanced Custom Fields and WordPress. That&#8217;s not a terribly reasonable expectation, to think you can find one person who is excellent at both of those things. Some of those people do exist in the world, but for many team leaders putting together teams, they&#8217;re realizing, we&#8217;re going to be better off if we say like, Steve, you&#8217;re going to be the backend expert, and Brian, you&#8217;re going to be the front end expert. And, even though Brian has a whole lot of that backend expertise, for many teams, they just decided to make a hard divide in the people.</p>



<p>And then subsequently, or the order was sometimes flipped, a hard divide in the technology. So for, you know, a lot of websites built in this era, there is a very hard divide between the content management system is over here, be it WordPress or Drupal or a natively headless system like Contentful or Sanity. That&#8217;s going to be managed by one group, and then this group of front end specialists will handle the front end presentation.</p>



<p>That&#8217;s a hard cut to make. A question I&#8217;ve been asking for the last decade or so is, if we&#8217;re going to cut off WordPress&#8217;s head or Drupal&#8217;s head, where is the neck? That is an answer that is constantly moving. The next era, after single page applications, is static site generation. As people saw the, you know, that downside of single page applications, then it&#8217;s, oh, well what if we, what if we get some of the benefits of that old way of doing it where it was just flat files? Can we have flat files again, Brian.</p>



<p>[00:28:06] Nathan Wrigley: Full circle.</p>



<p>[00:28:07] Brian Perry: Exactly. That introduces a whole new set of challenges and trade offs. You know, it certainly does, things being completely static does provide a build asset that is immutable, and it&#8217;s easy to roll back. It&#8217;s something that can be cached on a CDN. But also it really changes, kind of going back to again, the editing experience. It really drastically changes that experience where someone who was used to editing a page in WordPress and clicking publish and then being able to see the page.</p>



<p>Now you have a workflow where you make a change in your CMS or whatever the source of the data is, and then a build has to run to be able to have the end website updated. And how do you preview what that looks like before the build runs? Do you need a separate environment? That trade off definitely brings a lot of additional complexity potentially to the content editing experience now.</p>



<p>[00:29:07] Nathan Wrigley: Yeah, I think it&#8217;s potentially very frustrating as well because although the technological benefits and probably things like SEO and all of those things. There probably are great benefits there. If you&#8217;re the content editor, there&#8217;s probably only annoyance that when you click publish nothing happens.</p>



<p>We&#8217;ve got to wait for some, like you say, some build process to carry on. You&#8217;re adding in a great deal of incredible technological innovation, which speed things up and pushes things to different parts of the world, and I&#8217;m sure it&#8217;s something we can get into. But also from the content editing point of view, we&#8217;ve had this evolution toward being able to edit everything right away, and click publish and seeing it, to then suddenly yanking that carpet out from underneath them, which is yeah, kind of frustrating I guess.</p>



<p>[00:29:55] Steve Persch: I called this the cliff of complexity. If you search on YouTube for that phrase, you can probably find a presentation that I did at Gatsby Conf. So Gatsby, as a front end framework, really became popular as that static site generator pattern was on the ascendance, because there are so many technological benefits to be had, but when you add in a handful of possibly extra requirements. Requirements like, well, the content editors really like to be able to press publish and see it immediately. That shoots you up this cliff where making that work in an architecture that is fundamentally static, is really cutting against the grain.</p>



<p>Like it can be made to work, but is massively complex. And we think for a lot of teams like that complexity is just now worth it. The fundamental mode that WordPress has done for 20 years of like, you press publish and then you see it immediately. That is something that should not be compromised on for most teams.</p>



<p>[00:30:56] Nathan Wrigley: We&#8217;re used to a trajectory where technology just gets better in every respect. So, not only does it get quicker, but the, you know, the UI is easier to use and there&#8217;s a complete expectation that if I could publish it yesterday, and click publish and it was published right away and I could examine and look for errors that I&#8217;d made.</p>



<p>Well, we&#8217;re a year on from that. Why have you taken that capability away from me? We&#8217;re going backwards? Well, we&#8217;re kind of going sideways. We&#8217;re not going back because we&#8217;re just changing things. I think that would be a bitter pill to swallow. Hard to understand if you&#8217;re not technical.</p>



<p>[00:31:30] Steve Persch: Yeah, absolutely. And I think that&#8217;s, that backwards moving or that sideways moving does happen in other places. That&#8217;s not something I think that&#8217;s unique to web development. I remember the first time I got a car that relied heavily on a touchscreen. I was like, no, I want a knob to turn up the volume on the radio. This is so much worse. But somebody thought, no touchscreens, that&#8217;s the future. No. A lot of cars are now backswinging. There&#8217;s some parts that we do need physical buttons and dials for. That is better.</p>



<p>[00:32:01] Brian Perry: I was going to say, it&#8217;s funny that you bring up the car example because, my car actually has both, which is somewhat infuriating. There is a touchscreen that could do everything. And then on the console, all the knobs and buttons, they can do the exact same things. I feel like the JavaScript frameworks in trying to address the shift aggressively in the direction of static sites has had a period of time where it was the equivalent of my car that had both.</p>



<p>So things started shifting back over to server side rendering. But a lot of the frameworks had, and still have, concepts of both at one time. So there are ways that you can say, I want to either build things statically by default, and after some period of time they&#8217;re invalidated and re rendered on the server. Or say that it&#8217;s this subset of pages that are pre-rendered statically. Maybe it&#8217;s my homepage, and my 100 most popular pages.</p>



<p>And then other things are handled server side. That also does increase the complexity now. You have to know what things are static, what things are not. It&#8217;s kind of two different approaches. But yeah, it does feel a lot like my car that has essentially two completely redundant ways to interface with it.</p>



<p>[00:33:19] Nathan Wrigley: I&#8217;m waiting for somebody to invent the car which has levers in it. So that you&#8217;ve got screens, dials, and levers. Then we&#8217;ll, we&#8217;ll truly have the car from across the entire century. So is that where we&#8217;re at now then? If we chart our history we spoke about HTML files, and then PHP coming along and then flattening things. Is that this history lesson ends, or is there more to say?</p>



<p>[00:33:42] Steve Persch: The way I think about it, a phrase I often like to repeat to myself that came from a customer of ours, is that Pantheon needs to aim for state of the art, not bleeding edge. We see the state of the art for many web teams right now is one where you use a totally stable content management system like WordPress or Dupal for the content management systems.</p>



<p>And because so many front end developers simply expect to be working in JavaScript centric tools for teams in that, in that pool. Yes, you should have the front end then controlled through JavaScript centric tools. But do so with server side rendering because the content editors expect to press publish and then immediately see the change. And that works well with server side rendering.</p>



<p>So that&#8217;s, that&#8217;s a mode that we support in our front end sites product, the front end sites product does also support that static mode. Which is beneficial for a subset of teams out there. Like Pantheon&#8217;s own documentation site has been a totally static site for nearly a decade. I think as long as we&#8217;ve had a standalone docs site, it&#8217;s been static. And that works for that team where everything is all just in a Git repo. An edit to code can happen at the same time as an edit to the content markdown files. That works for that mode.</p>



<p>But we see that, you know, the state of the art for some web teams, as that mix of a contact management system, and a server side rendered Node.js framework. I should also say, because we&#8217;re on a WordPress centric podcast here, if you are totally comfortable with WordPress, as is, you don&#8217;t need to jump on a new React framework or a new JavaScript framework, just because there are a lot of people on Twitter saying it&#8217;s great. If you can do your job without taking on the extra complexity, stick with what works.</p>



<p>[00:35:28] Nathan Wrigley: Yeah, it&#8217;s a really good point. You mentioned there, now, I can&#8217;t remember the exact phrasing that you used, but you made a differentiation between bleeding edge and something else. Is that an approach that you take? Do you keep a watchful eye on what is happening at the extremes of technology.</p>



<p>[00:35:44] Steve Persch: Oh absolutely, yes.</p>



<p>[00:35:46] Nathan Wrigley: PhD thesis which are describing what the future might look like. But holding back just a little bit until it&#8217;s embedded and we figured out what all of this stuff is. That&#8217;s the approach?</p>



<p>[00:35:56] Steve Persch: Absolutely. So it is not a coincidence that Pantheon as a company started a decade after Drupal came into being. It was starting as a Drupal centric company, and then adding WordPress a few years later. That&#8217;s not a coincidence. There needed to be a decade or so of figuring out, how do we make websites like this before Pantheon or any company like Pantheon could do what we did. Which is put guardrails around what our founders considered to be a best practice mode of developing and maintaining and improving a lamp stack site.</p>



<p>Trying to impose those guardrails the same year that a system like WordPress or Drupal comes out, that wouldn&#8217;t make sense. Similarly, we didn&#8217;t really enter this front end framework ecosystem until about a decade in. I think almost exactly a decade after React, was released publicly is when we entered this space fully.</p>



<p>We&#8217;ve been keeping an eye on it for a very long time. I&#8217;ve been at Pantheon for seven years and that was one of my very first questions, my first week, like, when are we going to get into the Node.js space? And the answer then was not yet. And then for a while, it was soon. And then the answer was like, okay, now.</p>



<p>And now we can see, okay, the edge and one of the reasons I like to use that term bleeding edge is because that&#8217;s also the term for where the bleeding edge is now. The edge, as a synonym for the content delivery network. So companies like Cloudflare or Fastly that cache your website all over the world, have been adding more and more advanced capabilities beyond the simple caching that makes the website faster. That is very clearly where the bleeding edge or the cutting edge is now. We have a CDN baked in. We have ways of exploring that. However, put it all on the edge is not an acceptable answer yet for the broad plurality of professional web teams.</p>



<p>[00:37:50] Nathan Wrigley: Why is that? What&#8217;s the thing which makes that untenable?</p>



<p>[00:37:53] Steve Persch: The very short answer is because your database is still in one place. Even though the cloud abstracts so much like. There is a MySQL database or an abstraction thereof that lives physically in one place. Because we run on Google Cloud, that place for most sites on Pantheon is in Council Bluffs, Iowa.</p>



<p>For a WordPress site that you know, may be making in some cases hundreds of MySQL queries to generate an HTML page, hopefully fewer than, than a few hundred, but in many cases, hundreds of queries. It&#8217;s best if the PHP process that&#8217;s making those queries is right next to, physically right next to that database.</p>



<p>There are new companies popping up spreading your database all over the world at the edge. Okay, that sounds cool, but before, before we take some of the biggest websites in the world and say, oh yeah, your database will be everywhere. We need to see how that plays out with those who, who want to jump on the edge earlier. Because for the sites we serve and cater to they need to be planning in very long terms.</p>



<p>We&#8217;re highly adopted in the edu space, and I, I&#8217;ve put together timelines on yardsticks to represent like the multi hundred year history of these universities that we&#8217;re working with. And asking like, on a multi a hundred year scale or a scale of decades, it doesn&#8217;t matter that much if you switch to the new thing, whatever the new thing is, this semester or next semester, or this year or next year? Let&#8217;s wait till we know that that next thing is solid before we jump on it.</p>



<p>[00:39:23] Brian Perry: As the JavaScript guy, I got to say I want it now. But, aside from that, one thing that&#8217;s interesting from the front end perspective as well, thinking about running things on the edge. One of the challenges there is that right now, all of the different solutions for edge functions tend to use different variations of JavaScript runtime. So there&#8217;s really no consistency there. And I think that&#8217;s another thing that&#8217;s going to have to change before that gets real wide adoption, when there can be one consistent JavaScript runtime that is typically used for that solution.</p>



<p>[00:39:54] Nathan Wrigley: You mentioned Steve, but Brian maybe can answer this as well, I don&#8217;t know. You mentioned that there are people who are endeavoring to break up the database and put it in all sorts of different parts of the world and what have you. So that&#8217;s one innovation which people are trying to achieve. I&#8217;m just curious about what the next 10 years will look like. What kind of fun, interesting projects have you guys been keeping your eye on, which the listeners may be interested in? Just to give some insight into what hosting a WordPress website might look like Well, in 2025, 2026, whatever it may be.</p>



<p>[00:40:29] Brian Perry: My kind of, it&#8217;s partially my hope, but also where I&#8217;d like to think that things are going. With all of the constant changes in the JavaScript framework landscape, I think that more and more of the things that people like about that sort of developer experience is going to find its way just more generally into the platform and into browser standards.</p>



<p>Again, like looking back in the rear view, jQuery is a good example of that, in that jQuery brought so many wonderful niceties for how you can interact with the DOM. And then over time, most of the things that jQuery can do are just in JavaScript now. So they&#8217;re part of the platform.</p>



<p>So my hope is that the things that people like about React and Vue and et cetera, start to find their way into the general platform. Web components are one potential technology that might help there. A component based approach that can be used regardless of the framework.</p>



<p>My hope is that in the next 10 years, a lot of the things that people turn to React or Vue or different frameworks for, are just a part of the platform, rather than having to find your cool JavaScript framework that was released three months ago,</p>



<p>[00:41:47] Nathan Wrigley: Yeah. Nice. Thank you, Brian. Steve, anything to add to that?</p>



<p>[00:41:51] Steve Persch: I&#8217;ll give a quick tech answer, then a longer, uh, philosophical sort of answer. So the quick tech answer is web assembly. I&#8217;ll be quick because I can&#8217;t speak to many of the details of web assembly, maybe Brian can? I see it as a layer that can abstract away many of the differences between the different computer languages that we&#8217;re all writing in. PHP, JavaScript, TypeScript, Rust. If web assembly is a common target that can be used to leverage software. You write in these different modes. Run it in the same place, be it at the edge, or I saw a demo recently that I think involved web assembly getting WordPress to fully run in your browser, like the WordPress running in web assembly in your browser. Okay, that, that looks cool.</p>



<p>The thing I&#8217;m, I&#8217;m probably most excited about right now for where the overall web zeitgeist is going is, is that the web development ecosystem seems to be coming back to what WordPress has been saying for a long time, of decisions, not options as that philosophical pillar for the WordPress community.</p>



<p>I find it very reassuring that these front end framework projects that for a decade or so, provided so many options and put so many decisions on the plate of individual web teams and said like, you figure out whether or not you want Redux or this other thing to pair with your React project, and good luck sorting out the hundreds or thousands of NPM dependencies that get installed.</p>



<p>The frameworks that seem to be, that just are ascendant, right now, are the ones that are consolidating a lot of those options. Turning them into decisions that are made at the framework level, be it Next.js or Astro or Remix. The leaders of those projects seem to understand that there&#8217;s a desire in the community for, for those framework maintainers as experts to make a good quality decision that works for the broad majority of users of those frameworks. Be it Next or Astro or anything else. The users of Next.js are comfortable with an increasing number of decisions being first made in a centralized framework. WordPress has been doing that again for 20 years. Again, it&#8217;s fashionable.</p>



<p>[00:44:11] Nathan Wrigley: Yeah, history I think in many respects is fairly cyclical. What goes around does seem to come around. Yeah, good observation. I&#8217;m curious at this point, we&#8217;ve reached the 50 minute mark, and I want to wrap it up. I know you&#8217;ve got things to do with your day. But is there anything that you had wished that we had talked about that we failed to?</p>



<p>[00:44:31] Steve Persch: Brian, do you want to touch on Decoupled Kit?</p>



<p>[00:44:34] Brian Perry: Yeah, I&#8217;d love to talk about that a little bit. The Decoupled Kit project is essentially what we&#8217;re thinking of as a kit, is essentially a backend starter project and a front end starter kit that are intended to work together as close to out of the box with as little configuration as possible. To try to simplify the process of setting up the headless or decoupled architecture sites.</p>



<p>And also provide some common examples of types of integrations and common problems that need to be solved there. And the thing that I think is most interesting about some of what we&#8217;re doing there. Again, thinking about this being an open source project sponsored by Pantheon, is we&#8217;re trying to solve some of these problems in cases where it makes sense in a framework agnostic way.</p>



<p>So, obviously starter projects for both Drupal and WordPress. And then within that we have a starter kit, we have multiple starter kits that are based on React. So we have a starter kit for Gatsby and WordPress, and a starter kit for Next.js and WordPress. So we&#8217;re trying to find cases where there are things that we can abstract out, which are just essentially like general utilities for sourcing data from WordPress. And not things that are really strictly tied to any one framework.</p>



<p>So that if there is, you know, another framework in the future that we need to support, or gains popularity, it&#8217;s easy to make adjustments there and adapt to that. And I think in the headless CMS community, both in the Drupal world and the WordPress world. I think there&#8217;s a lot of opportunity for tools that are a little bit more framework agnostic, that can still serve popular projects like Next.js. But hopefully are things that the community can use as the JavaScript world evolves.</p>



<p>I&#8217;ll just also throw out there that, would love to, as we continue to build things, any feedback on the project. The main repo is decoupled dash kit dash js, under the Pantheon Systems GitHub. Would love to hear what people run into, any features that they&#8217;d love to see us support in the future. Any feedback is welcome.</p>



<p>[00:46:45] Nathan Wrigley: I will make sure to link to all of the bits and pieces that we&#8217;ve talked about in the show notes. So if you are listening to this and you want to follow up on what the guys have been mentioning, then head over to wptavern.com, search for the episode, and all of the links will be in the show notes. Just before I let you go and get on with your busy days. If somebody wants to reach out to you personally and connect, what are the best ways, what are the methods that you are willing to share publicly? Let&#8217;s go with Brian first.</p>



<p>[00:47:16] Brian Perry: Sure. Yeah, I&#8217;m in a number of CMS and Pantheon community Slacks, usually as Brian Perry. That, that&#8217;s one decent way to get at me. And then also I am still on Twitter. That is my main connection to the web development social media world, currently. Bri Comedy, b r i comedy on Twitter.</p>



<p>[00:47:38] Nathan Wrigley: Brian, thank you very much. And Steve.</p>



<p>[00:47:40] Steve Persch: I am spending less time on Twitter these days, although I&#8217;m still there as at stevector. And LinkedIn is the social network that I&#8217;m opening most often these days, and I&#8217;m easy to find just by searching for Steve Persch.</p>



<p>[00:47:55] Nathan Wrigley: Thank you very much. Brian Perry and Steve Persch really appreciate you coming onto the podcast today. Thank you very much indeed.</p>



<p>[00:48:02] Steve Persch: Thank you, Nathan.</p>



<p>[00:48:03] Brian Perry: Thank you.</p>
</div>



<p>On the podcast today we have <a href="https://pantheon.io/team/steve-persch">Steve Persch</a> and <a href="https://pantheon.io/team/brian-perry">Brian Perry</a>. They’re both employed at <a href="https://pantheon.io/">Pantheon</a>, an enterprise website operations platform, and they’re here to talk about the evolution of website hosting.</p>



<p>Back when the internet started, hosting was a fairly straightforward enterprise. You created HTML files and uploaded them to a server. That was it. An HTML file was a page.</p>



<p>Server-side technologies such as PHP came along and the picture became a little more complex. Web pages needed to be constructed on-the-fly. Databases were thrown into the mix and the complexity increased.</p>



<p>Add in the different languages that you could write your code in, and the server configurations. The CMS that you choose also plays into this mix.</p>



<p>Now we’ve got CDNs, headless, React, Gatsby, Node.js and much more. Is it even possible for the non-technical to have any understanding of where their website is?</p>



<p>Steve and Brian talk about how they got into the hosting space and what’s changed over the years. We address what Pantheon is doing with WordPress and Drupal.</p>



<p>We discuss how headless can be difficult for content teams, given that there’s a disconnect with hitting the publish button, and that content going live on the site.</p>



<p>What’s certain is that there’s no end in sight in terms of the rate of innovation in the website hosting space. What’s popular today might not be several years from now, and so it’s a timely discussion of what Steve and Brain see as the best bets for the future.</p>



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



<p><a href="https://pantheon.io/blog/decoupled-kit">Brian&#8217;s blog post about Decoupled Kit</a></p>



<p><a href="https://www.youtube.com/watch?v=dF39cXW3IqY">Steve&#8217;s video &#8220;Decoupled Architectures: What Computer Assembles the website&#8221;</a></p>



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



<p><a href="https://www.sanity.io/">Sanity</a></p>



<p><a href="https://gatsbyconf.com/">GatsbyConf</a></p>



<p><a href="https://docs.pantheon.io/overview/support">Pantheon&#8217;s documentation site</a></p>



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



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



<p><a href="https://webassembly.org/">WebAssembly</a></p>



<p><a href="https://nextjs.org/">Next.js</a></p>



<p><a href="https://astro.build/">Astro</a></p>



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



<p><a href="https://twitter.com/bricomedy">Brian&#8217;s Twitter</a></p>



<p><a href="https://twitter.com/stevector/">Steve&#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, 05 Apr 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:32;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:192:"HeroPress: Empowering Women within the WordPress Community: Embracing Contributions and Overcoming Fear – Empowerment von Frauen in der WordPress-Community: Mitmachen und Ängste überwinden";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=5438";s:7:"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:256:"https://heropress.com/essays/empowering-women-within-the-wordpress-community-embracing-contributions-and-overcoming-fear/#utm_source=rss&utm_medium=rss&utm_campaign=empowering-women-within-the-wordpress-community-embracing-contributions-and-overcoming-fear";s: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:15453:"<img width="1024" height="512" src="https://heropress.com/wp-content/uploads/2023/04/040323-min.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: Women, your talents, ideas, and passion are needed, and together we can continue to shape the future of WordPress." /><p><a href="https://heropress.com/feed/#deutsch">Dieses Essay ist auch auf Deutsch verfügbar.</a></p>




Here is Birgit reading her own story aloud.






<p>The world of technology and open-source projects can often feel intimidating, especially for women, who may experience feelings of inadequacy or fear of rejection. In my own journey within the WordPress community, I have faced challenges and insecurities while navigating an environment where my work and accomplishments sometimes go unrecognized. However, I have also discovered the incredible impact that women&#8217;s contributions can have on the community and the importance of overcoming fear to make a meaningful difference. Today, I will share my experience and mission to empower women to contribute to the WordPress project, regardless of the obstacles they might face.</p>



<h3 id="h-my-experience-in-the-wordpress-community">My Experience in the WordPress Community:</h3>



<p>Even though I’ve used WordPress from its first release, I began my journey in the WordPress community back in 2010 by visiting my first WordCamp in Berlin, Germany. This WordCamp was my leap into deep waters, I couldn’t imagine. There I made valuable contacts which led me joining one of the biggest WordPress agencies in Germany. After joining the Inpsyde Agency, whose founder also initiated the German-speaking WordPress community and ran the community forums, I was soon made responsible for overseeing the translations and compiling the software packages for the WordPress releases in German.&nbsp;</p>



<p>Since then, I have contributed in various ways, from organizing meetups and writing support documentation to translating the software and providing training materials. Like many others, I was not always vocal about my contributions, and due to the lack of visible logs, I could not easily measure the impact of my work. This lack of recognition sometimes left me feeling discouraged and questioning my value within the community.</p>



<p>Nonetheless, I persisted – with some mental health related sabbaticals – in contributing to the project, driven by my passion for WordPress and a desire to help others. Over time, I began to recognize the importance of the work I was doing, regardless of whether it was acknowledged by others. I saw firsthand how my efforts, along with those of countless other women in the community, helped to shape the WordPress ecosystem, making it more inclusive, accessible, and user-friendly.</p>



<h3 id="h-the-importance-of-embracing-contributions-and-overcoming-fear">The Importance of Embracing Contributions and Overcoming Fear:</h3>



<p>Despite the challenges we may face, it is crucial for women to embrace their contributions and overcome their fears in the WordPress community. By stepping up and sharing our skills, talents, and insights, we can help shape the future of the project and make a lasting impact. There are several reasons why this is essential:</p>



<ol>
<li>Diversity in perspectives: Women bring unique perspectives and experiences to the table, which can lead to innovative solutions and a more well-rounded community. By contributing, we help ensure that the WordPress project remains diverse and inclusive.</li>



<li>Empowerment and personal growth: Taking on challenges and pushing ourselves beyond our comfort zones can be an incredibly empowering experience. Contributing to the WordPress community not only allows us to grow professionally, but also boosts our self-confidence and sense of accomplishment.</li>



<li>Inspiring others: When we step up and contribute despite our fears, we become role models for other women who may be hesitant to get involved. By sharing our stories and experiences, we can inspire and encourage others to join the community and make their own impact.</li>



<li>Building a supportive network: By actively participating in the WordPress community, we can form connections and relationships with like-minded individuals who can offer support, mentorship, and encouragement. This network can be invaluable in overcoming challenges and fostering a sense of belonging within the community.</li>
</ol>



<h3 id="h-my-mission-to-empower-women-in-the-wordpress-community">My Mission to Empower Women in the WordPress Community</h3>



<p>As someone who has experienced the challenges and rewards of contributing to the WordPress project, I am dedicated to empowering other women to do the same. My mission is to create a supportive environment where women feel encouraged to share their talents, ideas, and expertise, regardless of any fears or obstacles they may face.</p>



<p>To achieve this goal, I am committed to:</p>



<ul>
<li>Raising awareness about the importance of women&#8217;s contributions in the WordPress community</li>



<li>Actively recognizing and celebrating the achievements of women who have made a significant impact within the project</li>



<li>Encouraging mentorship programs that support and guide women in their journey as contributors</li>



<li>Sharing my own experiences and lessons learned to inspire and empower others</li>



<li>Fostering a sense of camaraderie and support among women in the community, promoting collaboration and understanding</li>
</ul>



<p>Fear can be a powerful deterrent that prevents us from realizing our full potential and making meaningful contributions to the projects and communities we care about. However, it is crucial for women to recognize the value of their skills and insights and to overcome their fears in order to make a lasting impact within the WordPress community.</p>



<p>By embracing our contributions, seeking support, and empowering one another, we can help create a more inclusive, diverse, and vibrant WordPress ecosystem that benefits everyone. So, to all the women who have thought about contributing to the WordPress project but have held back due to fear or uncertainty, I encourage you to take that first step. Your talents, ideas, and passion are needed, and together we can continue to shape the future of WordPress.</p>



<p>Disclaimer: While the content of this essay primarily addresses women, I wholeheartedly acknowledge and embrace the diversity of gender and sexual orientation, including those who identify as female, non-binary, or belong to underrepresented groups.</p>



<div class="kb-row-layout-wrap kb-row-layout-id_ade563-ae alignnone kt-row-has-bg wp-block-kadence-rowlayout"><div class="kt-row-column-wrap kt-has-1-columns kt-row-layout-equal kt-tab-layout-inherit kt-mobile-layout-row kt-row-valign-top">

<div class="wp-block-kadence-column kadence-column_d879cf-9a"><div class="kt-inside-inner-col">
<h2 id="work-environment" class="kt-adv-heading_1e8c32-97 wp-block-kadence-advancedheading">Birgit&#8217;s Work Environment</h2>



<p>We asked Birgit for a view into her development life and this is what she sent! </p>


	<div class="hotspots-image-container">
		<img width="2560" height="1920" src="https://heropress.com/wp-content/uploads/2023/03/birgit-olzems-desk-scaled-1.jpeg" alt="Birgit Olzem" class="hotspots-image skip-lazy" />
	</div>




<p class="kt-adv-heading_b61d45-c4 wp-block-kadence-advancedheading has-theme-palette-9-background-color has-background">HeroPress would like to thank <a href="https://wpdrawattention.com/">Draw Attention</a> for their donation of the plugin to make this interactive image!</p>
</div></div>

</div></div>





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



<h1 id="deutsch" class="kt-adv-heading_ca583d-16 wp-block-kadence-advancedheading">Empowerment von Frauen in der WordPress-Community: Mitmachen und Ängste überwinden</h1>



<p>Die Welt der Technologie und der Open-Source-Projekte kann oft einschüchternd wirken, insbesondere für Frauen, die sich unzulänglich fühlen oder Angst vor Ablehnung haben. Auf meinem eigenen Weg in der WordPress-Community war ich mit Herausforderungen und Unsicherheiten konfrontiert, in denen meine Arbeit und meine Leistungen manchmal nicht anerkannt wurden. Aber ich habe auch entdeckt, welch unglaublichen Einfluss die Beiträge von Frauen auf die Community haben können und wie wichtig es ist, Ängste zu überwinden, um etwas zu bewegen. Heute werde ich meine Erfahrungen und meine Mission teilen, Frauen zu befähigen, einen Beitrag zum WordPress-Projekt zu leisten, unabhängig von den Hindernissen, auf die sie stoßen könnten.</p>



<h3>Meine Erfahrungen mit der WordPress-Community:</h3>



<p>Obwohl ich WordPress seit seiner ersten Veröffentlichung benutze, begann meine Reise in die WordPress-Community im Jahr 2010 mit der Teilnahme an meinem ersten WordCamp in Berlin, Deutschland. Dieses WordCamp war mein Sprung in tiefere Gewässer, als ich es mir je hätte träumen lassen. Dort habe ich wertvolle Kontakte geknüpft, die mich zu einer der größten WordPress-Agenturen in Deutschland geführt haben. Bei der Agentur Inpsyde, deren Gründer auch die deutschsprachige WordPress-Community initiierte und die Community-Foren leitete, war ich bald für die Betreuung der Übersetzungen und die Erstellung der Softwarepakete für die deutschsprachigen WordPress-Versionen zuständig.&nbsp;</p>



<p>Seitdem habe ich mich auf verschiedene Weise eingebracht, von der Organisation von Meetups und dem Schreiben von Support-Dokumentation bis hin zur Übersetzung von Software und der Bereitstellung von Schulungsmaterialien. Wie viele andere habe ich meine Beiträge nicht immer laut ausgesprochen, und da es oft keine sichtbaren Aufzeichnungen gab, war es für mich nicht leicht, die Auswirkungen meiner Arbeit zu messen. Dieser Mangel an Anerkennung führte manchmal dazu, dass ich mich entmutigt fühlte und meinen Wert innerhalb der Community infrage stellte.</p>



<p>Nichtsdestotrotz arbeitete ich &#8211; mit einigen gesundheitsbedingten Unterbrechungen &#8211; weiter an dem Projekt, angetrieben von meiner Leidenschaft für WordPress und dem Wunsch, anderen zu helfen. Mit der Zeit wurde mir klar, wie wichtig die Arbeit war, die ich leistete, unabhängig davon, ob sie von anderen anerkannt wurde. Ich konnte aus erster Hand sehen, wie meine Bemühungen und die unzähliger anderer Frauen in der Community dazu beitrugen, das WordPress-Ökosystem inklusiver, zugänglicher und benutzerfreundlicher zu machen.</p>



<h3>Die Bedeutung von Beteiligung und die Überwindung von Ängsten:</h3>



<p>Trotz der Herausforderungen, mit denen wir konfrontiert sind, ist es für Frauen von entscheidender Bedeutung, ihren Beitrag zu leisten und ihre Ängste in der WordPress-Community zu überwinden. Indem wir unsere Fähigkeiten, Talente und Einsichten mit anderen teilen, können wir die Zukunft des Projekts mitgestalten und einen nachhaltigen Einfluss ausüben. Dies ist aus mehreren Gründen wichtig:</p>



<ol>
<li>Vielfalt der Perspektiven: Frauen bringen einzigartige Perspektiven und Erfahrungen ein, die zu innovativen Lösungen und einer vielfältigeren Gemeinschaft führen können. Durch unseren Beitrag tragen wir dazu bei, dass das WordPress-Projekt vielfältig und inklusiv bleibt.</li>



<li>Empowerment und persönliches Wachstum: Sich Herausforderungen zu stellen und die eigene Komfortzone zu verlassen, kann eine unglaublich befähigende Erfahrung sein. Die Beteiligung an der WordPress-Community lässt uns nicht nur beruflich wachsen, sondern stärkt auch unser Selbstvertrauen und das Gefühl, etwas erreicht zu haben.</li>



<li>Andere inspirieren: Wenn wir trotz unserer Ängste einen Beitrag leisten, werden wir zu Vorbildern für andere Frauen, die vielleicht noch zögern, sich zu engagieren. Indem wir unsere Geschichten und Erfahrungen teilen, können wir andere inspirieren und ermutigen, sich der Gemeinschaft anzuschließen und selbst etwas zu bewegen.</li>



<li>Aufbau eines unterstützenden Netzwerks: Durch die aktive Teilnahme an der WordPress-Community können wir Verbindungen und Beziehungen zu Gleichgesinnten aufbauen, die uns unterstützen, beraten und ermutigen können. Dieses Netzwerk kann von unschätzbarem Wert sein, wenn es darum geht, Herausforderungen zu meistern und das Zusammengehörigkeitsgefühl innerhalb der Community zu stärken.</li>
</ol>



<h3>Meine Mission: Frauen in der WordPress-Community stärken</h3>



<p>Als jemand, der die Herausforderungen und Vorteile der Teilnahme am WordPress-Projekt selbst erfahren hat, möchte ich andere Frauen ermutigen, dasselbe zu tun. Meine Mission ist es, ein unterstützendes Umfeld zu schaffen, in dem Frauen sich ermutigt fühlen, ihre Talente, Ideen und ihr Fachwissen mit anderen zu teilen, unabhängig von Ängsten oder Hindernissen, denen sie begegnen könnten.</p>



<p>Um dieses Ziel zu erreichen, verpflichte ich mich, die folgenden Maßnahmen zu ergreifen:</p>



<ul>
<li>Sensibilisierung für die Bedeutung der Beiträge von Frauen in der WordPress-Community</li>



<li>Aktive Anerkennung und Würdigung der Leistungen von Frauen, die einen wichtigen Beitrag zum Projekt geleistet haben.</li>



<li>Förderung von Mentoring-Programmen, die Frauen auf ihrem Weg als Mitwirkende unterstützen und begleiten</li>



<li>Eigene Erfahrungen und Erkenntnisse weitergeben, um andere zu inspirieren und zu stärken</li>



<li>Förderung von Teamgeist und Unterstützung unter den Frauen in der Gemeinschaft, Förderung von Zusammenarbeit und Verständnis.</li>
</ul>



<p>Angst kann ein mächtiges Hindernis sein, das uns davon abhält, unser volles Potenzial auszuschöpfen und einen sinnvollen Beitrag zu den Projekten und Gemeinschaften zu leisten, die uns am Herzen liegen. Es ist jedoch von entscheidender Bedeutung, dass Frauen den Wert ihrer Fähigkeiten und Einsichten erkennen und ihre Ängste überwinden, um eine nachhaltige Wirkung in der WordPress-Gemeinschaft zu erzielen.</p>



<p>Indem wir unsere Inputs annehmen, Unterstützung suchen und uns gegenseitig stärken, können wir dazu beitragen, ein inklusiveres, vielfältigeres und lebendigeres WordPress-Ökosystem zu schaffen, von dem alle profitieren. Daher möchte ich alle Frauen, die darüber nachgedacht haben, einen Beitrag zum WordPress-Projekt zu leisten, sich aber aus Angst oder Unsicherheit zurückgehalten haben, ermutigen, den ersten Schritt zu tun. Ihre Talente, Ideen und Leidenschaft werden gebraucht und gemeinsam können wir die Zukunft von WordPress gestalten.</p>



<p>Disclaimer: Obwohl sich der Inhalt dieses Essays in erster Linie an Frauen richtet, erkenne ich die Vielfalt des Geschlechts und der sexuellen Orientierung von ganzem Herzen an und begrüße sie, einschließlich derer, die sich als weiblich oder nicht-binär identifizieren oder anderen unterrepräsentierten Gruppen angehören.</p>
<p>The post <a rel="nofollow" href="https://heropress.com/essays/empowering-women-within-the-wordpress-community-embracing-contributions-and-overcoming-fear/">Empowering Women within the WordPress Community: Embracing Contributions and Overcoming Fear &#8211; Empowerment von Frauen in der WordPress-Community: Mitmachen und Ängste überwinden</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 05 Apr 2023 12:34:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Birgit Olzem";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:37:"WPTavern: iThemes Rebrands to SolidWP";s:7:"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=143283";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/ithemes-rebrands-to-solidwp";s: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:2861:"<img />



<p>iThemes, one of the oldest brands in WordPress that originally <a href="https://ithemes.com/blog/the-ithemes-story/">launched around theme products</a> nearly 15 years ago, is <a href="https://solidwp.com/blog/press-release-ithemes-is-becoming-solidwp/">rebranding to SolidWP</a>. Over the years, the company&#8217;s products became increasingly centered on plugins, yet the old brand had so much name recognition that its leadership was not quick to change it.</p>



<p>&#8220;iThemes is known today for security, backups, and site maintenance – none of which are well-represented in the name &#8216;iThemes,'&#8221; StellarWP Senior Director of Ops and Marketing Matt Cromwell said. &#8220;Additionally, the brand evokes the early 2000’s Apple era of technology, and we want to look toward the future.&#8221;</p>



<p>This week the company kicked off a &#8220;rebrand in public&#8221; approach to updating its identity to be more aligned with promoting iThemes&#8217; key offerings &#8211; its security, backup, syncing, and educational products. They will all be rebranded to the following: </p>



<ul>
<li>Solid Security</li>



<li>Solid Backups</li>



<li>Solid Central</li>



<li>Solid Academy</li>
</ul>



<p>&#8220;This shift in branding signifies our renewed focus on providing a solid foundation for every WordPress website,&#8221; Cromwell said. &#8220;Our whole team, as well as our products, will pivot to focus on security, backups, site maintenance, and training as we enhance and improve our solutions for all of our users.&#8221;</p>



<p>The rebranding is a massive undertaking, as the company&#8217;s products have millions of users and years worth of articles, webinars, eBooks, and tutorials. SolidWP will present reworked pricing and retire some legacy products in the process.</p>



<p>&#8220;Currently on ithemes.com you’ll find a lot of products that are either part of a bundle, or sold on other websites in a variety of ways,&#8221; Cromwell said in the FAQ section of the announcement. &#8220;Some products will continue to thrive on their own, and others will be retired. We plan on reviewing publicly the complete inventory of our current products and bundles and working with the community to shape what the future plan is for each.&#8221;</p>



<p>The company is not planning to increase prices on its products at this time but Cromwell said they reserve the right to adjust pricing as needed. iThemes will also be consulting its community regarding products that are slated to be retired.</p>



<p>&#8220;We will continue to support any and all who land in our support queue with our best efforts and service,&#8221; Cromwell said. &#8220;The official end-of-life for the products being sunset will be discussed with the community and decided on before the full launch of our new brand.&#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, 04 Apr 2023 22:33:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:34;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:99:"WPTavern: Twitter Suspends WordPress.com’s Access to Twitter API, Breaking Jetpack Social Sharing";s:7:"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=143281";s:7:"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:106:"https://wptavern.com/twitter-suspends-wordpress-coms-access-to-twitter-api-breaking-jetpack-social-sharing";s: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:3042:"<p>Twitter <a href="https://jetpack.com/blog/an-update-on-jetpack-social-and-twitter/">suspended WordPress.com&#8217;s access to the Twitter API</a> without notice yesterday. Representatives at WordPress.com do not know why their access is currently blocked but are working to regain it.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Our access to the Twitter API is currently blocked. As a result, Jetpack Social is temporarily unable to automatically share your posts directly from <a href="https://t.co/eRvNKWaolr">https://t.co/eRvNKWaolr</a> to Twitter.  We have reached out to Twitter for more information on how to get unblocked.</p>&mdash; WordPress.com (@wordpressdotcom) <a href="https://twitter.com/wordpressdotcom/status/1643240046621802497?ref_src=twsrc%5Etfw">April 4, 2023</a></blockquote>
</div>



<p>The API enables features like Jetpack Social&#8217;s Twitter connection. Users who rely on this Jetpack module to auto-tweet their published posts will see errors in the dashboard until this issue is resolved. </p>



<img />



<p>WordPress.com <a href="https://wordpress.com/blog/2023/04/04/why-twitter-isnt-working-with-your-blog-right-now/">advised</a> that reconnecting will not work at this time, nor will trying to establish a new connection. Connections to other social networks are still operational.</p>



<p>On large publishing sites some authors may not be aware that the auto-tweet functionality is broken. For the time being, the solution is to manually tweet published posts. </p>



<p>Jetpack users <a href="https://wordpress.org/support/topic/twitter-connections-from-wordpress-com-are-currently-experiencing-failures/">reported</a> the issue in the plugin&#8217;s support forums 10 hours ago, as some of them are Jetpack Social paid subscribers. In October 2022, Jetpack <a href="https://wptavern.com/jetpack-social-plugin-adds-paid-plan-free-users-now-limited-to-30-shares-per-month">announced</a> a paid plan for its Social plugin and limited the free version to 30 social shares per month, a controversial monetization decision that left many users in search of alternatives.</p>



<p>Several users asked if refunds will be coming their way if the fix for the issue is not forthcoming, as auto-sharing to Facebook and Twitter is one of the main reasons customers subscribe to the service.</p>



<p>&#8220;We are aware of issue and are looking into it with Twitter, but at this stage we don’t know when it will be fixed,&#8221; a Jetpack support representative responded to customers. &#8220;We’re working with Twitter to find the best solution possible.&#8221;</p>



<p>Twitter <a href="https://twitter.com/TwitterDev/status/1641222789901484034">launched</a> its new API access tiers on March 29, 2023. Access to the Enterprise tier requires an application process. Over the next 30 days Twitter is deprecating its previous access tiers and is encouraging developers to migrate to the new tiers as soon as possible to avoid disruption.</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, 04 Apr 2023 19:51:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:35;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:90:"Do The Woo Community: Woo DevChat on WordPress Blocks with Nyasha Greene and Kathy Darling";s:7:"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=74694";s:7:"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:52:"https://dothewoo.io/developer-chat-wordpress-blocks/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:429:"<p>Nyasha Greene and Kathy Darling have a conversation on what they are building lately, and the experiences they have had with blocks.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/developer-chat-wordpress-blocks/">Woo DevChat on WordPress Blocks with Nyasha Greene and Kathy Darling</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, 04 Apr 2023 09:35:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:91:"WPTavern: Anders Norén Releases Abisko, a New Free WordPress Theme with 30+ Block Patterns";s:7:"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=143241";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:99:"https://wptavern.com/anders-noren-releases-abisko-a-new-free-wordpress-theme-with-30-block-patterns";s: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:3292:"<p>Designer and developer Anders Norén has released a new free block theme called <a href="https://wordpress.org/themes/abisko/">Abisko</a>, created to fully support the new design features available in the latest <a href="https://wptavern.com/wordpress-6-2-dolphy-introduces-a-revamped-site-editor-distraction-free-writing-mode-and-updated-block-inserter">WordPress 6.2</a> release. The theme was named for one of Norén&#8217;s favorite stomping grounds, <a href="https://en.wikipedia.org/wiki/Abisko_National_Park">Abisko national park</a>, where he hikes every summer.</p>



<img />



<p>Abisko places a strong emphasis on both images and typography, featuring the geometric &#8220;Plus Jakarta Sans&#8221; font for both headings and paragraph text. Plus Jakarta Sans was designed by Gumpita Rahayu from Tokotype in 2020. It seems to be gaining popularity and was mostly recently featured in the <a href="https://wptavern.com/lemmony-a-free-wordpress-block-theme-with-30-patterns">free Lemmony theme</a> we reviewed last month. Plus Jakarta Sans is available as a free variable font and also on Google Fonts.</p>



<p>At a font weight of 800, Abisko&#8217;s H1 and H2 headings make a major statement in the design across the various templates and patterns. Norén contrasts this with liberal use of whitespace so it doesn&#8217;t end up feeling overbearing.</p>



<img />



<p>Abisko includes five different style variations, with unique color palettes that will change the entire look and feel of the site. These are found under Appearance &gt; Editor and can be accessed through the Styles panel and applied globally when editing any template.</p>







<p>Abisko packages more than 30 patterns for users to mix and match in creating pages. These include a grid with logo types, various artfully designed gallery layouts, contact section, various calls-to-action, hero patterns with images and background colors, testimonials grid, FAQ section, features list, a pricing table, large numbered lists, a wide separator with vertical margins, and more. </p>



<p>The theme also has five full-page layouts available as patterns: About Us, Contact Us, FAQ, Front Page, and a Linktree style page.</p>



<img />



<p>The evolution of WordPress themes, becoming fully editable and packaged with style variations and dozens of patterns, means there is no single screenshot that can fully represent what a theme might look like. Check out the <a href="https://andersnoren.se/themes/abisko/">live demo</a> to see what is possible and the page that previews all the <a href="https://andersnoren.se/themes/abisko/patterns/">block patterns</a>.</p>



<p>&#8220;Same as most block themes, Abisko is really lightweight and fast,&#8221; Norén said in a <a href="https://andersnoren.se/introducing-abisko/">post</a> introducing his theme. &#8220;It has a small CSS file, includes no JavaScript at all, and uses locally hosted variable fonts to keep external requests and page size at a minimum.&#8221;</p>



<p><a href="https://wordpress.org/themes/abisko/">Abisko</a> is available for free on WordPress.org. Although Norén said he designed it with travel blogs in mind, it&#8217;s flexible for many different use cases, including agencies, portfolios, businesses, and personal websites.</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, 04 Apr 2023 03:06:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"WordPress.org blog: The Month in WordPress – March 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:35:"https://wordpress.org/news/?p=14780";s:7:"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/04/the-month-in-wordpress-march-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:13171:"<p>March saw the arrival of the first major release of 2023, WordPress 6.2 “Dolphy.” Planning for the project&#8217;s 20th anniversary continues with new celebratory updates and commemorative swag. Read on for the latest happenings in the WordPress space.</p>



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



<h2 class="wp-block-heading">Meet WordPress 6.2 “Dolphy”</h2>



<p><strong><a href="https://wordpress.org/news/2023/03/dolphy/">WordPress 6.2</a> “Dolphy” was released on March 29, 2023</strong>. Named after the acclaimed jazz multi-instrumentalist and composer<strong> </strong>Eric Allan Dolphy Jr., the latest version of WordPress further enhances the site editing experience with significant updates.</p>



<p>Highlights include a reimagined Site Editor interface, a more intuitive way to manage menus, and a distraction-free writing mode. A new Block Inserter design adds integration with <a href="https://openverse.org/">Openverse</a>, allowing you to easily browse and insert free, openly-licensed images and audio files into your content.</p>



<img width="1024" height="581" src="https://i0.wp.com/wordpress.org/news/files/2023/04/WordPress-6.2-highlight-grid.png?resize=1024%2C581&ssl=1" alt="Feature highlights in WordPress 6.2: Reimagined Site Editor, more ways to manage menus, a more powerful inserter, faster access to media—yours and Openverse's, the new Style Book, distraction-free writing, and more." class="wp-image-14782" />



<p>Whether you&#8217;re a content creator, designer, or developer, WordPress 6.2 has something for you. <a href="https://wordpress.org/news/2023/03/dolphy/"><strong>Check out the full announcement post</strong></a> for an overview of what&#8217;s new and the <a href="https://make.wordpress.org/core/2023/03/09/wordpress-6-2-field-guide/">Field Guide</a> for detailed developer notes.</p>



<p>WordPress 6.2 is one of the last major releases planned for Phase 2 of the <a href="https://wordpress.org/about/roadmap/">project’s development roadmap</a> and was made possible thanks to more than 600 contributors.</p>



<blockquote class="wp-block-quote has-extra-large-font-size">
<p><a href="https://make.wordpress.org/test/2023/02/07/help-test-wordpress-6-2/"></a><a href="https://wordpress.org/download/">Download WordPress 6.2 “Dolphy.”</a></p>
</blockquote>



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



<h2 class="wp-block-heading">WP20 swag is here</h2>



<p>Show your WordPress excitement with <strong>limited edition 20th anniversary merchandise</strong>—now available at the official <a href="https://mercantile.wordpress.org/product-category/wp20/"><strong>WordPress Mercantile store</strong></a>. If you prefer to create your own swag, you can use these <a href="https://wp20.wordpress.net/download-the-wp20-commemorative-logos/">WP20 downloadable assets</a>.</p>



<img width="1024" height="576" src="https://i0.wp.com/wordpress.org/news/files/2023/04/digital-banner-1.png?resize=1024%2C576&ssl=1" alt="Blue background with confetti and WordPress 20th anniversary commemorative logo." class="wp-image-14785" />



<p>The 20th anniversary website <a href="https://wp20.wordpress.net/wp20-celebrations/">lists celebrations</a> as organizers announce and schedule them. Check back regularly to see if there’s an event in your area to join or <a href="https://wordpress.org/news/2023/03/lets-party-organize-your-wp20-celebration/">help organize one</a> to celebrate this milestone with your local community.</p>



<blockquote class="wp-block-quote has-extra-large-font-size">
<p><a href="https://wp20.wordpress.net/wapuu-coloring-giveaway-style-your-own-party-wapuu/">Enter the Wapuu Coloring Giveaway</a> by April 17, 2023, for a chance to win some commemorative WP20 swag!</p>
</blockquote>



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



<h2 class="wp-block-heading">New in the Gutenberg plugin</h2>



<p>Two new versions of the Gutenberg plugin have shipped in the last month:</p>



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/13/whats-new-in-gutenberg-15-3-13-march/"><strong>Gutenberg 15.3</strong></a><strong> </strong>was released on March 13, 2023. This version polishes the Site Editor experience, includes a new “Time to Read” block for displaying estimated read time to posts, and enhances the Duotone design tool.</li>



<li><a href="https://make.wordpress.org/core/2023/03/22/whats-new-in-gutenberg-15-4-22-march/"><strong>Gutenberg 15.4</strong></a> is available for download as of March 22, 2023, and focuses primarily on bug fixes and testing improvements. Other additions include color and layout support for the Cover block, improved descriptions to help you understand the purpose of each template in the Site Editor, and the ability to turn paragraph blocks into columns.</li>
</ul>



<blockquote class="wp-block-quote has-extra-large-font-size">
<p><a href="https://make.wordpress.org/core/2023/02/01/core-editor-improvement-strengthening-style-options/"></a>Follow the “<a href="https://make.wordpress.org/core/tag/gutenberg-new/">What’s new in Gutenberg</a>” posts to stay on top of the latest enhancements.</p>
</blockquote>



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



<h2 class="wp-block-heading">Team updates: Phase 3 planning, WordPress Developer Blog launch, and more</h2>



<ul>
<li>Gutenberg Lead Architect Matías Ventura <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">outlined the focus areas</a> for Phase 3 of the WordPress development roadmap, known as <strong>Collaboration</strong> or <strong>Collaborative Editing</strong>.</li>



<li>Last month, the <a href="https://wordpress.org/news/2023/03/introducing-the-wordpress-developer-blog/">WordPress Developer Blog</a> officially launched (removing the &#8220;beta&#8221; label). <a href="https://developer.wordpress.org/news/#subscribe">Subscribe</a> to keep up with the latest features, tutorials, and learning resources in the WordPress development space.</li>



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



<li>Are you looking to broaden your knowledge and improve your WordPress skills? See <a href="https://make.wordpress.org/updates/2023/04/01/whats-new-on-learn-wordpress-in-march-2023/">what’s new on Learn WordPress in March 2023</a>, including the latest course on <a href="https://learn.wordpress.org/course/converting-a-shortcode-to-a-block/">Converting a Shortcode to a Block</a>.</li>



<li>A new <a href="https://make.wordpress.org/themes/2023/03/03/hallway-hangout-community-themes-initiative/">Community Themes initiative</a> aims to bring together a group of contributors to collaborate and build block themes.</li>



<li>The Training Team is looking for assistance in creating content to complete <a href="https://make.wordpress.org/training/2023/03/29/introduction-to-wordpress-development-syllabus/">this WordPress Development syllabus</a>.</li>



<li>The newly formed Contributor Working Group <a href="https://make.wordpress.org/community/2023/03/23/recap-of-contributor-working-group-inaugural-mentorship-chat-on-march-20-2023/">hosted an inaugural chat</a> to kick off work on the <a href="https://make.wordpress.org/project/2023/02/06/proposal-creating-a-wordpress-contributor-mentorship-program/">WordPress Mentorship Program</a>.</li>



<li>The Polyglots Team is <a href="https://make.wordpress.org/polyglots/2023/03/29/adding-chatgpt-and-deepl-in-the-translation-memory/">testing AI systems</a> to help with translation work.</li>



<li>The WordPress.org redesign project has a new dedicated Making WordPress Slack channel to coordinate work: <a href="https://wordpress.slack.com/archives/C04U953K77A">#website-redesign</a>.</li>



<li>The March 2023 editions of the <a href="https://make.wordpress.org/polyglots/2023/03/15/polyglots-monthly-newsletter-march-2023/">Polyglots monthly newsletter</a> and the <a href="https://make.wordpress.org/community/2023/03/21/meetup-organizer-newsletter-march-2023/">Meetup Organizer newsletter</a> are available for reading.</li>



<li>The Mobile Team announced a <a href="https://make.wordpress.org/mobile/2023/03/28/new-mobile-support-forum/">new support forum</a> for the WordPress mobile app.</li>
</ul>



<blockquote class="wp-block-quote has-extra-large-font-size">
<p>Tune in to <a href="https://wordpress.org/news/2023/03/episode-52-phase-three-with-hector-prieto/">Episode 52 of WP Briefing</a> to learn more about the visioning behind Phase 3, Collaboration.</p>
</blockquote>



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



<h2 class="wp-block-heading">Feedback &amp; testing requests</h2>



<ul>
<li>A new Full Site Editing (FSE) Program exploration looks into the Site Editor as a design tool in light of the recent WordPress 6.2 release. Participants are asked to create a block theme without coding using the current editor tools. <a href="https://make.wordpress.org/test/2023/03/29/fse-program-exploration-build-a-block-theme/">Share your experience</a> by April 26, 2023.</li>



<li>A group of Core contributors is working on a new <a href="https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/">Interactivity API proposal</a> to provide a better developer experience for building interactive blocks.</li>



<li><a href="https://make.wordpress.org/updates/2023/03/25/mobile-team-update-march-25th/">Version 22.0</a> of the WordPress mobile app for iOS and Android is ready for testing.</li>
</ul>



<blockquote class="wp-block-quote has-extra-large-font-size">
<p>Members of the Core Team are looking for user experience (UX) feedback on the <a href="https://make.wordpress.org/core/2023/03/28/call-for-testing-plugin-dependencies-ux/">Plugin Dependencies feature plugin</a>.</p>
</blockquote>



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



<h2 class="wp-block-heading">WordPress events updates</h2>



<ul>
<li>WordCamp Asia 2024 is <a href="https://asia.wordcamp.org/2024/">calling for organizers</a>. Apply by April 15, 2023.</li>



<li>Registration for the <a href="https://europe.wordcamp.org/2023/contributor-day-registration-is-now-open/">WordCamp Europe 2023 Contributor Day</a> is now open.</li>



<li>Want to create diverse and inclusive WordPress events? Mark your calendars for the upcoming <a href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/diversity-speaker-training-workshop/#upcoming-wpdiversity-workshops">#WPDiversity workshops</a>.</li>



<li>Four WordCamps are taking place this month:
<ul>
<li><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ee-1f1f9.png" alt="🇮🇹" class="wp-smiley" /> <a href="https://torino.wordcamp.org/2023/">WordCamp Torino</a>, Italy, on April 14-15, 2023</li>



<li><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1e6-1f1f9.png" alt="🇦🇹" class="wp-smiley" /> <a href="https://vienna.wordcamp.org/2023/">Wordcamp Vienna</a>, Austria, on April 15-16, 2023</li>



<li><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1eb-1f1f7.png" alt="🇫🇷" class="wp-smiley" /> <a href="https://paris.wordcamp.org/2023/">WordCamp Paris</a>, France, on April 21, 2023</li>



<li><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1e7-1f1ec.png" alt="🇧🇬" class="wp-smiley" /> <a href="https://sofia.wordcamp.org/2023/">WordCamp Sofia</a>, Bulgaria, on April 22-23, 2023</li>
</ul>
</li>
</ul>



<blockquote class="wp-block-quote has-extra-large-font-size">
<p>Join WordPress Executive Director Josepha Haden Chomphosy as she discusses <a href="https://wordpress.org/news/2023/03/episode-51-is-routine-a-rut/">the benefits of routine and what role it plays in the WordPress project</a>.</p>
</blockquote>



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



<hr class="wp-block-separator has-text-color has-light-grey-color has-alpha-channel-opacity has-light-grey-background-color has-background" />



<p><strong><em><strong><em><strong><em>Have a story we should include in the next issue of The Month in WordPress? <strong><em>Fill out </em></strong><a href="https://make.wordpress.org/community/month-in-wordpress-submissions/"><strong><em>this quick form</em></strong></a><strong><em> to let us know.</em></strong></em></strong></em></strong></em></strong></p>



<p><em><em>The following folks contributed to this Month in WordPress: <a href="https://profiles.wordpress.org/bsanevans/" class="mention"><span class="mentions-prefix">@</span>bsanevans</a>, <a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a>, <a href="https://profiles.wordpress.org/eidolonnight/" class="mention"><span class="mentions-prefix">@</span>eidolonnight</a>, <a href="https://profiles.wordpress.org/rmartinezduque/" class="mention"><span class="mentions-prefix">@</span>rmartinezduque</a>, <a href="https://profiles.wordpress.org/sereedmedia/" class="mention"><span class="mentions-prefix">@</span>sereedmedia</a>.</em></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:"Mon, 03 Apr 2023 10:30:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"rmartinezduque";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:58:"Do The Woo Community: BobWP is Speaking at WordCamp Lisboa";s:7:"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=74701";s:7:"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://dothewoo.io/bobwp-wordcamp-lisboa/";s: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:318:"<p>BobWP will be speaking about community at WordCamp Lisboa 2023.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/bobwp-wordcamp-lisboa/">BobWP is Speaking at WordCamp Lisboa</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</a>	.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 03 Apr 2023 10:22:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:39;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:68:"WPTavern: WooCommerce to Host Virtual Contributor Day April 19, 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:30:"https://wptavern.com/?p=143218";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:78:"https://wptavern.com/woocommerce-to-host-virtual-contributor-day-april-19-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:2157:"<p>WooCommerce has announced a 24-hour virtual contributor day that will happen on April 19, 2023. Contributors will be working on the <a href="https://github.com/woocommerce/woocommerce">WooCommerce Core</a> and <a href="https://github.com/woocommerce/woocommerce-blocks">WooCommerce Blocks</a> repositories. To give better coverage over time zones, organizers will have two kickoff times (0 UTC and 12 UTC).</p>



<p>WooCommerce hasn&#8217;t had a WooConf in-person conference since 2017, opting instead for virtual events like WooSesh where people can attend and watch presentations for free. The open source project has focused more on virtual communication channels to help contributors stay connected, such as the new <a href="https://wptavern.com/woocommerce-to-launch-wc-blocks-extensibility-monthly-chat">monthly chat focused on WooCommerce block extensibility</a>. This virtual contribution day will be the first of its kind for WooCommerce. </p>



<p>&#8220;We are asking for a minimum of 4 hours of your time to dedicate to a curated list of issues,&#8221; WooCommerce developer advocate Stephanie Pi said. &#8220;These issues have been selected based on the effort needed to solve them –we’re only including issues that we believe can be solved within the day.</p>



<p>&#8220;Any issues picked up and worked on during contributor day will be merged before the next release.<strong> </strong>We are committed to making sure this happens because we want to honor the time our community is dedicating to this event.&#8221;</p>



<p>The virtual event will be a more intense, focused time than what one might experience at a WordCamp contributor day, with key WooCommerce decision makers present to help keep things moving.</p>



<p>Organizers will be creating new channels in the <a href="https://woocommercecommunity.slack.com/">WooCommerce Community Slack</a>, that will be dedicated to the different issues they plan to work on during the 24-hour event. This includes a channel for helping contributors get set up with a development environment. Those interested to attend can watch for updates in the #announcements channel.</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, 01 Apr 2023 01:02:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:82:"WPTavern: WordPress Contributors Propose New Interactivity API for Frontend Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=143152";s:7:"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:93:"https://wptavern.com/wordpress-contributors-propose-new-interactivity-api-for-frontend-blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6558:"<p>Over the past year a group of WordPress contributors have been <a href="https://make.wordpress.org/core/2022/04/27/exploration-to-enable-better-developer-and-visitor-experiences-with-blocks/">working</a> on making it easier for developers to build interactive blocks. These are the kinds of experiences that allow visitors to submit a form and get feedback without reloading the page, load paginated content without refreshing, and improve e-commerce stores with more dynamic responses based on visitor interaction. </p>



<p>A new <a href="https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/">proposal for an Interactivity API</a> aims to provide a standard way for developers to add interactivity to the frontend, making it faster to build these experiences without reinventing the wheel every time. </p>



<p>Automattic-sponsored core contributor Mario Santos cast the vision for what the new API will deliver: </p>



<blockquote class="wp-block-quote">
<p>What if effortlessly creating performant, fluid, and idiomatic frontend interactivity on block-based WordPress sites was possible? Imagine plugins providing interactions like “heart this post” or “add to cart” without page reloads. Picture instant search, commenting, and native full-page transitions as best-in-class built-ins without complex scaffolding or external tools. Envision achieving this in any block theme by default without sacrificing PHP server rendering and the plugin ecosystem for a JS runtime. Visualize block developers easily declaring and extending such behaviors in a way that is immediately familiar and compatible with the block ecosystem.</p>
</blockquote>



<p>Santos published a demo video accompanied by a <a href="https://wpmovies.dev/">live interactive demo</a> where visitors can favorite movies and have the favorite count instantly updated in the block in the header. Pagination and search update the content without refreshing the page. The code for the demo is <a href="https://github.com/WordPress/wp-movies-demo">available on GitHub</a>.</p>







<p>The Interactivity API is being created for use on the frontend of block-based websites but contributors may also explore the possibility of reusing some of its directives inside the editor. They are taking a similar approach to <a href="https://alpinejs.dev/">Alpine.js</a> with &#8220;directives&#8221; that extend HTML with special attributes, except designed specifically for WordPress and backwards compatible with its APIs. </p>



<p>&#8220;The API is designed for the world of blocks and takes WordPress history of being closely attached to web standards to heart,&#8221; Santos said.</p>



<p>&#8220;As directives are added to the HTML, they work great with dynamic blocks and PHP.&#8221;</p>



<p>Having a standard in place means that WordPress developers don&#8217;t have to roll their own solutions for things like tooling, inter-block communication, and frontend performance. They would be primarily responsible for the block logic, making creating interactive blocks easier and more approachable for less experienced developers.</p>



<p>Contributors on the project have selected <a href="https://preactjs.com/">Preact</a> to build the directives system due to its HTML-friendliness, small size, performance, extensibility, and compatibility with React.</p>



<p>The Interactivity API is currently in the stage of gathering feedback to incorporate in development as well as expanding technical documentation. </p>



<p>&#8220;Although it is now distributed as a plugin, it aims to be added as an experimental feature to Gutenberg,&#8221; Santos said. &#8220;The goal is to include it in Core once enough feedback has been gathered, and it’s clear that it’s the right direction.&#8221;</p>



<p>Initial reactions to the proposed API have been mostly positive, as developers have previously had to build their own solutions for interactivity in the absence of a standard.</p>



<p>&#8220;The Interactivity API is one of the most interesting proposals for WordPress frontend UX &amp; DX that I&#8217;ve seen in awhile,&#8221; WordPress Core contributor Weston Ruter <a href="https://twitter.com/westonruter/status/1641521738805809152">said</a>.</p>



<p>&#8220;As someone who has been experimenting a lot with using AlpineJS, HTMX, Unpoly, StimulusJS, etc. for interactivity on the frontend, having a blessed solution in WP core would be most welcome,&#8221; another developer (@r1ckd33zy) <a href="https://twitter.com/r1ckd33zy/status/1641573350701948928">commented</a>.</p>



<p>WordPress developer and WPGraphQL contributor David Levine seemed less enthused about the approach outlined in the proposal. &#8220;Great idea but shortsighted execution,&#8221; Levine said. &#8220;We need an actual block data layer, not to further pollute our markup for our scripts to parse. This just exacerbates the same problems that got us into this mess.&#8221;</p>



<p>A few others in the comments of the post have been critical of the approach and  others have questions about long term challenges of maintaining this approach.</p>



<p>&#8220;This is a pretty out-there which is quite a different approach to anything I’ve seen before,&#8221; WordPress core contributor Joe Hoyle said. &#8220;That does give me caution, as it’s very wp specific / centric. I think with the block editor there’s opportunity to align more with industry innovation around front-end tooling. I think it’s really great work and very creative; but again I’m not yet sure it’s the right direction. It could be that there’s no long term solution to bring an &#8216;nextjs&#8217;-ification to WordPress, but I’m not sure I’m looking at it.&#8221;</p>



<p>The proposal includes examples of how to create interactive blocks using the API and developers have opened a lively discussion on the approach. Contributors on the Interactivity API are planning to host two sessions on April 17, 2023 (<a href="https://www.meetup.com/learn-wordpress-online-workshops/events/292575913/">one at 08:00UTC</a> and <a href="https://www.meetup.com/learn-wordpress-online-workshops/events/292575942/">another at 17:00UTC</a>) that will include a live product demo followed by a Q&amp;A. Check out the proposal for more details and the <a href="https://github.com/WordPress/block-interactivity-experiments">Interactivity API GitHub repo</a> to see some experiments the team has been working on so far.</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, 31 Mar 2023 14:48:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:63:"Post Status: Launching a WordPress Product in Public: Session 7";s:7:"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=148593";s:7:"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-7/";s: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:63823:"<div class="wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background is-layout-flow"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">In this episode, <a href="https://twitter.com/coreymaass">Corey Maass</a>, a freelance web developer, joins <a href="https://twitter.com/corymiller303">Cory Miller</a> to discuss the intricacies of creating an impactful, user-appreciated product that makes a positive impact on customers and stands apart in a saturated industry. </p></div>


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


<span class="span-reading-time rt-reading-time"><span class="rt-label rt-prefix">Estimated Reading Time:</span> <span class="rt-time"> 33</span> <span class="rt-label rt-postfix">minutes</span></span>
</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>, the go-to on WordPress product design topics, and <a href="https://twitter.com/corymiller303">Cory Miller</a>, a master on the business of WordPress. They discuss finding the balance in the small and big pictures of product development, highlighting the process of trial and error.</p>



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



<ul>
<li><strong>Courage Under Fire.</strong> After what feels like a miserable failure, it’s vital to keep trudging forward. Great product design takes time to build and grow in the space you are putting it into. Keeping your passion alive and remaining consistent in your efforts will eventually lead you to success.&nbsp;</li>



<li><strong>The Impact of Thoughtful Design.</strong> Developing a product is, of course, based on meeting some kind of user need, but it’s important to consider if you are going to make that user’s life easier with your product. When the end user is your top priority, your product will shine, and you’ll be proud of your direct impact on someone’s everyday life. </li>



<li><strong>Finding the Spark in Your Product.</strong> Focusing on the overall product journey is key for great product development, but zooming in on the minor details is equally important. Brainstorming and finding the spark is not easy, but setting your product apart from the rest is crucial. </li>



<li><strong>Using Your Audience to Improve Development</strong>. Put your ideas and questions out there for your audience to speak to. If you are wondering how people will perceive a certain product aspect or want more information on their exact pain points, it’s good to ask directly. Getting information straight from your customers or peers can help you make well-informed decisions in product development.</li>
</ul>



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

</div>



<h3 class="eplus-wrapper wp-block-heading" 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://www.google.com/aclk?sa=l&ai=DChcSEwiIyKyw6PL9AhVlyZQJHT6EAcYYABAKGgJ5bQ&ei=bawcZJe0G8epqtsPivSAqA8&sig=AOD64_0_PN97hzZ3jYMLTv3M0suhf9h2Ag&q&sqi=2&adurl&ved=2ahUKEwjXnqSw6PL9AhXHlGoFHQo6APUQ0Qx6BAgKEAE">StickerMule</a></li>
</ul>



<h3 class="eplus-wrapper wp-block-heading" 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 wp-block-heading" id="h-transcript">Transcript</h2>



<h2 class="wp-block-heading">Session 7 Corey &amp; Cory Launch a WordPress Product Live</h2>



<p>Corey Maass: [00:00:00] So now I&#8217;m following along. I&#8217;ve gotten in the habit of. I opened the<br />YouTube, which is, well, it&#8217;s live, which is really disorienting cuz of course I&#8217;m talking, uh, 10<br />seconds ago or 10 seconds in the future. And then grab the chat and then close it as fast as I<br />can,<br />because it seems that people do ask us questions, but mostly on YouTube, not on, uh, the<br />webinar, the Zoom webinar.<br />Cory Miller: Um, sorry, I was just trying to get all that going. Um, yeah, speaking of what we&#8217;re<br />talking about today in the marketing channel with post status, there&#8217;s some good conversations<br />about product. Hmm. I was like, you know, there&#8217;s enough of this going around that we, um,<br />should we have more conversations about product and marketing.<br />And [00:01:00] channels.<br />Corey Maass: Um, I have to go find, I&#8217;ve got, um, I&#8217;m in product owner and I&#8217;m in a couple of<br />others, but I&#8217;m not in marketing. Oh, okay. You&#8217;re already in here. Yeah. Product leaders I&#8217;m in.<br />Cory Miller: Yeah. Um, I really want that product leaders channel to. This type of, you know,<br />conversation, whatever it has to do with product, you know?<br />Right.<br />Corey Maass: So, yeah, and it&#8217;s, I mean, it&#8217;s a popular topic. Like I, I was on Twitter five<br />minutes ago and somebody was asking like, who is marketing WordPress plugins? Well these<br />days? And of course was scrolling the answers to see who to follow or what examples to look at,<br />or, you know, there&#8217;s, I mean, a few known quantities.<br />Um, and articles and, and references and stuff, but well, you know, [00:02:00] year to year and,<br />and new products that will cause blips and, and whatnot. Yeah. Um, you know, because it&#8217;s<br />definitely still not a. You know, not a known thing. I mean, marketing anything is not, is never<br />necessarily reliable. But, uh, marketing a WordPress plugin.<br />There are people who are very successful with WordPress plugins, but I don&#8217;t know that the<br />marketing is, it&#8217;s not a solved problem. You know,<br />Cory Miller: I think we said this a lot, but I really love product. Um, but it feels like. Almost like<br />gambling, you know? Um, like this one, I continue to see there&#8217;s something here and we say<br />this, we don&#8217;t know what it is and we&#8217;re trying to kinda keep stepping into it.<br />But gosh, I&#8217;ve tried a bunch of products between I themes and today, you know, bunch of<br />different things. And they weren&#8217;t like [00:03:00] pure software products of course. Um, but.<br />Every time I talk about product, I realize how much I have to learn .<br />Corey Maass: Um, so there&#8217;s, um, they&#8217;re the people who I, I&#8217;m not gonna even try to mention<br />names, but it&#8217;s like, there are, there are people who are famous for breaking the land speed<br />record, you know, or the like, uh, What was his name?<br />Hopkins was in the, a movie called The Indian, and it was his, about his motorcycle or you know,<br />there&#8217;s nascar, like there&#8217;s the people who win over year, over year. And, and then there&#8217;s,<br />there&#8217;s gotta be the people who were fascinating, you know, they, they worked a, a regular job<br />and they spent every night and weekend working on, you know, Build, trying to build the fastest<br />[00:04:00] race car or the fastest motorcycle and, and have absolutely died in obscurity, , you<br />know, like, they just never, they d take a, take a motorcycle out to the flats, crash it, start over<br />again, you know, and, and have done it.<br />Or did it, you know, for 30 years or whatever, and, and we&#8217;re never gonna hear about any of<br />those people, you know, or they consistently came in third and we&#8217;re never gonna hear about<br />any of those people. Yeah. And it&#8217;s like, I&#8217;m a while ago, I had to th there was a time in my life<br />where I was absolutely convinced that I was going to be a rockstar dj, where I was going to be<br />the gazillion.<br />Uh, entrepreneur or, and I still would love to be all those things. Well, I don&#8217;t know if I have the<br />energy anymore, but Me too. Um, you know, um, but it, they were, they were tied into my<br />identity and they were like constant. You know, a need and would keep me up at night. And now<br />I&#8217;m like, I [00:05:00] have, I think part of middle age is accepting your mediocrity.</p>



<p>Um, and, and just going, you know, okay, if, if I&#8217;m, if I&#8217;m successful, if I&#8217;m having some fun and<br />I&#8217;m successful enough that I&#8217;m not, Uh, starving, you know, then, then that&#8217;s then and, and then<br />it&#8217;s fun to keep trying, you know, and, and on my deathbed, it, it&#8217;s still probably gonna hurt that I<br />didn&#8217;t, you know, uh, headline, uh, you know, some huge music festival or something, but, uh,<br />but at least I tried, I suppose<br />Cory Miller: I, I love that. Thank you for sharing that. Um, you know, because I, I totally. , um, in<br />so many ways. I feel like I had my time. Mm-hmm. , you know, I got my opportunity and I made,<br />I made the most of it. I&#8217;m, I&#8217;m proud of it, you know, uh, and that, that was a [00:06:00] very<br />magical period for me. You know? But when you&#8217;re talking, have you seen the Netflix?<br />It made me think of the Netflix special full swing. It&#8217;s about golf. So, I know you golf. I don&#8217;t, I put<br />putt golf, you know, but, um, even though we have a son named Callaway, everybody thinks we<br />named it after a golf club. And I&#8217;m like, no, sorry, , um, him out after a golf club. But, okay, so this<br />last episode, there&#8217;s a guy, and you may name, you may know his name, and I&#8217;m like, I, if, if<br />there were jerseys in golf, I&#8217;m not a.<br />I would go buy his jersey today. He&#8217;s like the 70th best. Mm-hmm. golfer in the world. His name<br />is Joel Drum. I can&#8217;t remember. I&#8217;ll f I&#8217;ll find his name. So the first episode, have you seen this?<br />Mm-hmm. . Okay. You, I think you&#8217;d be interested. I&#8217;m like you said. Full swing. Full swing. It&#8217;s a<br />documentary about the [00:07:00] PGA.<br />I&#8217;m morbidly curious about sports because I think it has so many parallels. Anyway, so the first<br />two were like, the brand names Justin Thomas, uh, Jordan Sp, and now I know those names<br />well, but I was familiar with their names. Sure. And like they&#8217;re at the top pinnacle of the sport.<br />Then the third episode is, is is Joel, and he&#8217;s basically like, I&#8217;m okay being seven.<br />like he&#8217;s got immense talent. Um, his caddy, everybody&#8217;s like, no, he&#8217;s a top 30 golfer. And he&#8217;s<br />just kinda like, you know, he&#8217;s, he could be like, he won, he&#8217;s won, but like, he could be even<br />better. But he&#8217;s just like, k he feels like almost resigned contend of being like 70th. And I. Maybe<br />I&#8217;m okay being like 500th best or five thousandths best at being an entrepreneur, being a<br />product person, right?<br />Um, [00:08:00] I am morbidly attracted to entrepreneurship and product. Like I think you and I<br />resonate with this. Like every time I hear you talk, man, I would go. Rather from another mother,<br />like he, you know,<br />Corey Maass: I could have said those words or have had or have said those words. Yeah,<br />exactly.<br />Cory Miller: But I think there&#8217;s something resonating here, Corey.<br />It&#8217;s the esteem that I, I&#8217;m gonna talk by myself. The esteem I might talk about, like iconic,<br />everybody says it, Steve, let me invoke his name. Steve Jobs right now, first time around, I<br />think. Right time, right place, and of course genius, you know, but right time, right place, right.<br />Critical thing got kicked out of Apple, comes back and doing it again, and we always talk about<br />him.<br />Right. You know, maybe, maybe Elon Musk in my mind before he started doing, just, I don&#8217;t<br />know. Um, he, I think he went too far. He overreach. But anyway, but I go, God, [00:09:00] I&#8217;d<br />love to have that kind of genius for product for. and, but selling down in Maine, like you were<br />saying about middle, middle age and Meoc, just going, Hey, I think I got some talent , you know,<br />but mainly I just work my ass off.<br />Mm-hmm.<br />Corey Maass: I&#8217;m one of those, try things and try things.<br />Cory Miller: I feel like one of those sports players, like if we use that metaphor analogy,<br />whatever it is, and I. Never gonna be number one. Mm-hmm. never gonna be top 50. But for my<br />brand of those, I&#8217;m really content with who I am. You know? Right. Even though I&#8217;m just like,<br />God, it feels like with product it&#8217;s miserable Failure.<br />Miserable failure. Miserable failure. Miserable failure. When 2008, man, I felt like I&#8217;m gonna mix<br />all these sports things, get up to the plate, ball&#8217;s coming, [00:10:00] and I hit it. And I get into the<br />field<br />Corey Maass: and you scored a touchdown<br />Cory Miller: and . Yes. And a hole in one and you know, let me find another sport so I can do it.<br />But you don&#8217;t end up in the gutter.<br />I think the reality is, yeah, , I need bumpers for my bowling entrepreneur, bowling, and there you<br />go. Product person. I need some bumpers. I feel like sometimes, and I&#8217;m glad I. I couldn&#8217;t laugh</p>



<p>about this a couple years ago at all. Hmm. I&#8217;d be like, what? I have magic. I&#8217;m supposed to be<br />magic. I&#8217;m supposed to come.<br />Right. You know, and then you&#8217;re like, maybe not . It&#8217;s the humbling effect of that. Yep. And I<br />think when you come down to it, you go, I think the reason why I&#8217;m so interested in product is<br />like it&#8217;s a gift. It should be like this cool gift that you&#8217;re trying to help someone. Make somebody&#8217;s<br />life better and in the process be [00:11:00] able to do it vocationally and get paid for it.<br />Yeah. And man, I love that about work, you know, and products specifically is like tie to this little<br />bow, here&#8217;s your present and I&#8217;m trying to get better about this is I&#8217;m trying to offer a gift that you<br />pay for. Of course. You know, like those win-win things. But I digress.<br />Corey Maass: Yeah, it&#8217;s, I love solving a problem.<br />I love the, like, this is gonna sound weird, but I love the angles of it. Like the, uh, moving through<br />a problem, uh, like screens and inner, like, I, I want to feel clever for having built it, like build a<br />better mouse trap. But I also want, that&#8217;s a bad analogy cuz a mouse, mouse uses a mouse<br />trap. But it&#8217;s like, I, I wanna build, you know, the, the better.<br />Thing that other people then get pleasure out of using to, again, to [00:12:00] solve a problem.<br />Um, and so then I feel smart. And they feel smart. And, and it&#8217;s like, to me it&#8217;s, it&#8217;s one of the<br />epitome of the human condition is, is solving problems, is manipulating the space around us.<br />And, um, and so yeah, product just absolutely.<br />Resonated with me early on. Which is funny because I think I, and a lot of, a lot of developers<br />and a lot of product people also are passionate about music in one way or another, which is the<br />opposite. It&#8217;s so abstract. It can mean anything to anybody. It&#8217;s totally subjective, uh, as opposed<br />to like, In the world we live in, like there&#8217;s a little bit of subjectivity.<br />Like there&#8217;s, you know, there&#8217;s a reason why there&#8217;s a million to-do list apps because everybody<br />solves it slightly differently or wants it to feel slightly different. But it&#8217;s still, uh, you know, there&#8217;s<br />still ones that objectively don&#8217;t [00:13:00] work. , uh, uh, But anyway. Yeah, it&#8217;s, it&#8217;s, it&#8217;s fun. It&#8217;s<br />interesting.<br />It&#8217;s, I&#8217;m glad that it&#8217;s now a hobby rather than, uh, something that I, that I&#8217;m relying on. Cuz I<br />remember building, I think I&#8217;ve talked about this before, like, I remember building things because<br />I was like, I&#8217;m not gonna make rent if this doesn&#8217;t succeed. And of course it didn&#8217;t come close to<br />succeeding. I don&#8217;t even think I was able to finish it cuz it was like, I can&#8217;t make a logical<br />decision.<br />From a position of desperation, like some people can mm-hmm. , but I just, I can&#8217;t, I have to like<br />sit in it and splash around. Which is also why, because I think maybe it was another Twitter<br />conversation I was having, but, um, I, I often. Will. Oh, so yeah, somebody, somebody asked<br />like, do you, do you do any planning or do you jump right in?<br />I&#8217;m like, I a hundred percent jump right in, just like you, you keep saying like, there&#8217;s something<br />here. I often jump right in when I just, my gut [00:14:00] tells me that there&#8217;s something here<br />and, uh, Because I&#8217;m finding, and this is, I was noticing this again over the weekend. Um, the<br />setting screen that I wanna show you is like, I had to start building the setting screen in order for<br />me to go, oh, no, this setting isn&#8217;t right, or, we don&#8217;t need this, or This is better organized a<br />different way.<br />But I had to like, and I suppose I could put pen to paper and come to the sum of the same<br />conclusions, but for me, pen to paper is usually writing. You know, some, some aspect of code<br />to, so that I&#8217;m clicking on a button or I&#8217;m, I&#8217;m starting to fill in a screen or I&#8217;m even at this point, I<br />can just look at a screen and be like, no, this isn&#8217;t what we need, or this isn&#8217;t intuitive, or, um, no.<br />With that said, what I&#8217;ve designed is quite ugly. Um, I was futzing around. Information<br />architecture, and I don&#8217;t know why I was bothering, it was Sunday. I was having fun. Um, but<br />anyway, yeah, it&#8217;s, uh, there&#8217;s, [00:15:00] there&#8217;s definitely a difference of, of, for me anyway, like<br />getting in and actually clicking on things.<br />Cory Miller: It&#8217;s uh, when you say, when you said hobby, it reset me back to me going, is this,<br />should this really be a hobby for me? You know? Hmm. Um, cuz. I gotta tell you, I&#8217;ve, I<br />presented my business group about a week or two ago, and I was like, yeah, I don&#8217;t know. I<br />don&#8217;t know if I keep going. You know, back to middle age mediocrity, whatever it is, it&#8217;s like, I,<br />you know, we&#8217;re trying to do some things with post status and it&#8217;s been one frustration after the<br />other hitting walls.</p>



<p>I think that&#8217;s starting to loosen up, maybe with my own growth, you know? Okay. But like, just<br />trying to make progress on stuff where I had a team previously and now we&#8217;re trying, you know,<br />put stuff together. But that&#8217;s the bigger business. But down product too is like, you know, I think<br />there was a hope in me that you launch it and everybody&#8217;s like, hell yes.[00:16:00]<br />You know? Yeah. There&#8217;s more to it, you know? I just wanted people to instantly love it.<br />Corey Maass: Well, and starting from scratch is freaking hard. I mean, you were, you were on<br />a, a winning team. You were, you know, you were on a, a bus with a group of people. You&#8217;d built<br />the bus. You got the bus moving, and then you were hurling down the highway successfully.<br />And it&#8217;s real easy to forget that, like, oh, right. When we were building the bus, nobody cared.<br />And when the bus, the wheels first started moving, nobody cared. Now they do. And so yeah, if<br />you are, you know, leveraging something, if you&#8217;re building a trailer onto a bus that&#8217;s already<br />moving, that&#8217;s different than getting off the bus, chilling for a couple of years and then starting to<br />build another bus, you know?<br />Weird, weird analogy, but ,<br />Cory Miller: no, no, no. I like the bus thing cuz that&#8217;s how it was. I was like, I. I don&#8217;t, I get credit,<br />but I try not to ever take it and [00:17:00] be sure to point it in other ways. Like it was very much<br />a band back to music. I like, this is like, we&#8217;re a band that makes great music together. You<br />know, somehow it&#8217;s working, you know?<br />Yeah. And I can&#8217;t really take credit for a lot of that. I was, don&#8217;t get me wrong, I contributed, I<br />impacted it, but it was a magic of. Yeah, things flying together with it. And I think I&#8217;ve been trying<br />to ree that magic, you know, particularly with product. Um, but the word that comes up for me,<br />and I&#8217;m curious what your thoughts about this are, like de detachment, detachment from my<br />brilliant ideas, Corey, like, man, I&#8217;m very attached to my brilliant ideas, you know, and like here I<br />go.<br />How to detach from that pride aspect and then go just kinda lean into like passion and interest,<br />which is what your pace and how you [00:18:00] approach This has been really healthy for me<br />because you&#8217;re kinda like, I&#8217;m having fun doing it today. I&#8217;m having it and then tomorrow having<br />fun doing it and it. It&#8217;s, it&#8217;s taking some box for you.<br />And I&#8217;m like, I need to be just okay with like, it&#8217;s taking a box for me. Now when I am working<br />with a developer partner, , I&#8217;m like, I wanna talk to you about filters. I wanna talk to you about all<br />these things. Cuz like I had, like all the stuff that we could do with images. I&#8217;ve been planning<br />around with stuff and wanting, been wanting to go like, you know, Instagram revolutionized<br />photos, for instance.<br />I think it, it took the iPhone or the smartphone, whatever it is, and made most anybody a pretty<br />decent photographer, right? Like, you know, Photoshop, you could do the Gazi blur and you can<br />kind of filter and like make things a little like correct stuff with Instagram. I did that and I&#8217;m like, I,<br />I love that.<br />I love taking photos. I&#8217;ve been taken. [00:19:00] So this is a weird sidebar onto the product by.<br />But I&#8217;ve been, um, you know, there&#8217;s those cartoon apps that&#8217;ll take a photo and make a cartoon<br />of it. Yep. I&#8217;m a freaking geek about cartoon illustration, all that stuff. So what I&#8217;ve been doing,<br />this is gonna lead back to product, by the way, an actual question on our product future.<br />And you can say, Hey, can we pause that? Can we hold that later? But, so I&#8217;ve been taking, I<br />love taking pictures of sunsets, you know, and I. So I&#8217;ve been taking my sunset pictures and<br />putting &#8217;em into my cartoon app. . Mm-hmm. nice. Yeah. And making these really things. But the<br />premise here was, you know, back to our philosophical conversations about images and the<br />web and on a website, and I go, you know, with ai, there&#8217;s a, that mix in there too, but I go, that&#8217;s<br />interesting to me.<br />Like for, for, for our product perspective is like, there&#8217;s cool things going on. I think we could be<br />creative and innovate downstream a bit in this [00:20:00] market. While I&#8217;m kinda like really<br />impatient, but trying to be patient about getting to the stage of like, I want somebody to pay for<br />it. I want somebody to give some validation to go, okay, should we put a little bit more time and<br />effort and money into this?<br />You know? Right. But anyway, the filtered conversation was where I&#8217;ve been going as we&#8217;ve<br />been talking, going man, You would know, but like are there libraries and stuff that we can do<br />filters or something different to make things just a little nicer in the pro side? Yeah, that I just<br />freaking love, like I&#8217;m such a geek Corey about that.</p>



<p>But I take my picture and then I share it over to whatever the tune app is and I really like, I don&#8217;t<br />know, it&#8217;s kind of fun. There&#8217;s gotta be . I can&#8217;t help, this is my idealism. There&#8217;s gotta be<br />something. On this other side when we start being able to get to the pro side. Okay.<br />Corey Maass: Looking for the other, the other app, there&#8217;s one that, um, I got really into a<br />[00:21:00] couple years ago.<br />That&#8217;s, um, it&#8217;ll, it&#8217;ll take any photo and basically make it a painting Yes. In a bunch of different<br />styles. Yes. Because there was a, a woman at the la in the, uh, woman who posted on<br />Facebook this like really cute watercolor painting of a farmhouse. And then I noticed at the<br />bottom that there was a watermark of the app that she&#8217;d used.<br />And I was like, oh crap. She just took a picture of a farmhouse and ran it through this little, you<br />know, 99 cent app and then had. Like a watercolor that I would&#8217;ve put on the wall, you know?<br />Um,<br />Cory Miller: see that, that, that&#8217;s like the heart of publishing for me is expression, and I&#8217;m very<br />much an amateur photographer that flunk photography twice, by the way, in college. But I go,<br />Corey Maass: you forgot to do that. No, the, the cover, the lens cover off . Yes, yes.<br />Cory Miller: I know what depth to field is, but I&#8217;m like, The manual. Mm-hmm. cameras I had to<br />use suck. But all that to say [00:22:00] like this is interesting and that&#8217;s a hobby of mine and so I<br />would say it&#8217;s a hobby of mine. It&#8217;s taking these photos.<br />I even had my son do it while I was driving. I was like, could you take a picture of that sentence?<br />Yeah,<br />Corey Maass: yeah, I do. It&#8217;s one more thing. We have the same of, you need to look at my<br />Instagram. It&#8217;s literally just sky pictures. That&#8217;s<br />Cory Miller: so, okay. This is called Tune. But yeah, let&#8217;s see<br />Corey Maass: here. Oh, it does it live? It Does it live?<br />Oh, that&#8217;s cool. I assumed it was like, it had to be a photo, but it, it actually applies the filter while<br />you&#8217;re moving the photo.<br />Cory Miller: Yeah. So I was like, that&#8217;s wild. And then they&#8217;ve got impressionism, they&#8217;ve got all<br />these filters and I go, right, you know, there&#8217;s something about Instagram having, yeah, I, I don&#8217;t<br />know, 10, 15 filters.<br />I always use like the first six. Sure. You know, but it&#8217;s like there&#8217;s something about that taking<br />something, making it, just dressing it up a little bit and being able to put it out there. Like I&#8217;ve<br />been playing with the tune stuff on the colors cuz it really pulls [00:23:00] out some of the sunset<br />photos and stuff and I go, I hope there&#8217;s something there on this pro.<br />I want it. You know what I mean? Like I want something that just<br />Corey Maass: I conceptually, I think. You&#8217;re onto something. I mean, again, go, what&#8217;s our<br />mantra? You know, making creative tasks simpler, easier, fun. And so we&#8217;re starting with what<br />we&#8217;re hoping is the widest base. Everybody needs to crop an image and get it into WordPress.<br />Um, and then. So I, my Instagram, again, I&#8217;m fascinated, I&#8217;m captivated by mostly cloud shapes<br />and especially sunlight coming through the clouds. But I didn&#8217;t want to, I, I was never. Really<br />impressed with filters. Like they&#8217;re neat for doing different things, but I didn&#8217;t, they didn&#8217;t do what<br />I wanted. And so what I [00:24:00] actually do is, um, because I noticed that the, whatever it is,<br />the polarization from my sunglasses, Make things more distinct.<br />So I usually take my sunglasses off and then take a picture through the lens, and that&#8217;s my real<br />world filter, so to speak. Right. But it&#8217;s like, it&#8217;s, it&#8217;s my style. Nobody knows I&#8217;m doing it, but<br />that&#8217;s stylistically. Right. And so I imagine that, uh, a lot of people like. They, they have their feed<br />and so they have their favorite one or two filters and they think of it in part as their branding.<br />Um, and maybe it&#8217;s the same with blogs where it&#8217;s like, oh, if I&#8217;m, I&#8217;m blogging week over week,<br />whatever photo, I&#8217;m gonna give it the same treatment. Um, you know, even if that means, it&#8217;s not<br />necessarily some manipulation of the photo, but I put. My own watermark, or I put the title of the<br />blog post in a certain font with a certain background.<br />You know, [00:25:00] there&#8217;s a treatment so that you know when it&#8217;s shared. It&#8217;s the same with<br />the OG images, which is why I&#8217;m so fascinated by those. Um, and that&#8217;s the other plugin that I<br />keep messing around with as generating social images. But it&#8217;s the idea of being, again, that<br />same sort of the concept of set it and forget it, but so, Um, so the, another, another word that we<br />should somehow incorporate into one or another of our sort of overarching rules here is<br />consistency, which we&#8217;ve talked about.</p>



<p>It&#8217;s like, but, but taking that, like all of your images should be 16, nine, but taking it much further<br />so that it&#8217;s all of your images should be watermarked the same way, or they should have some.<br />You know, coherent look and feel so that I land on any page on your blog and, and I know where<br />I am or if I see an image on, in, you know, I&#8217;m scrolling Twitter and I&#8217;m like, oh, there&#8217;s another<br />one of Corey&#8217;s photos.<br />Because it&#8217;s, it&#8217;s [00:26:00] a, it&#8217;s a sunset, but it&#8217;s got the, the comic book treatment, you know,<br />so whatever, whatever it is, like, um, I, I think you are, you&#8217;re, what I take away from what you&#8217;re<br />describing is, An example of still kind of what we, our long-term goal, like whatever the handling<br />of images, but allowing people to handle images consistently.<br />And if it&#8217;s, if it&#8217;s unrecognizable, if it&#8217;s just a task, if it, if we just make uploading images easier<br />than great, like, and we&#8217;re, and everybody has that problem, but if down the road, like, yeah, we<br />hear from people that they all want watermarks or they all want. Uh, you know, an image filter<br />and we can figure out how to do that.<br />It&#8217;s, it still, to me, falls in the same, the same ballpark. Yep.<br />Cory Miller: Now we need a business case, like, you know, take some of this [00:27:00]<br />abstract, creative thought and go, okay, how can we, back to what you kind of grounding us in<br />as like consistent, I heard the word consistent, consistent. unique to the brand Yeah. That<br />they&#8217;re trying to portray.<br />That&#8217;s really interesting thought cuz I, I love templates. I mean, obviously mm-hmm. , that&#8217;s the<br />it that&#8217;s High Themes came from Template. Template Monster. You know, I was a, I had used<br />Template Monster 2004 or five for a website, um, that wasn&#8217;t in WordPress. I don&#8217;t even know<br />what it was in. Um, and I.<br />Offering somebody some flavors to have a head start to, to create something creative. Like for,<br />for, for me, I can&#8217;t draw, you know, I doodle, but some kind of headstart to help somebody do the<br />things. Yep. Consistent you need to your brand, um, you, your [00:28:00] own kinda style that<br />you could develop. Um, kinda like paint by numbers, so.<br />Okay. Thanks for letting me die. Tribe on. Wonder and fascination about all this. Um, you<br />wanted to talk about settings?<br />Corey Maass: Yeah. So I just shared, uh, something with you. Um, you see my screen? Yeah, I<br />can. So starting a settings page. Um, so we&#8217;ve got, I don&#8217;t know if it&#8217;s working in this version yet,<br />so featured images, um, Oh yeah, I, I have a fix for this.<br />So you see the three, four is not actually three four. Um, so that I&#8217;ve, that&#8217;ll, that&#8217;ll be fixed in the<br />next version. A little thing that&#8217;s been bugging me. Um, but the, you know, we&#8217;ve, we&#8217;ve got the<br />actual cropper in a couple of places. Media ad new, no, it&#8217;s not in here. [00:29:00] Again, this is<br />just a non, a little local demo thing.<br />Um, but I started adding what we&#8217;d talked about previously. Uh, uh, the next thing we need, or<br />one of the next things we need is a settings page where we can define the, essentially the<br />defaults like we&#8217;re talking about. Um, So starting with one of the use cases or the, the place, the<br />implement, one of the implementations we&#8217;ve done, um, being featured images.<br />The idea being that right you, when you first install a plugin, we&#8217;ll walk you through these<br />essentially where, you know, okay, for featured images, what is, you know, you always want<br />your photo to be, or the resulting photo to be at least, you know, 500 wide, uh, you know, but not<br />more than 2000 wide. And then same with.<br />You know, something like this, right? So that you don&#8217;t, [00:30:00] you don&#8217;t end up with images<br />that are too small, but you don&#8217;t also don&#8217;t end up with images that are too large. Um, and then,<br />uh, presets,<br />Cory Miller: oh, you can remove. That&#8217;s cool.<br />Corey Maass: So, yeah, because it&#8217;s like, uh, the, the example of the featured image, right? It&#8217;s<br />like we have given you these six square circle, 16, 9 43.<br />but it&#8217;s like, you don&#8217;t, you don&#8217;t want to give you, you, you know, if, if your featured image<br />should always be a circle, then, then why do you have to select circle every time? Right. And so<br />in settings, yeah, you can go in and remove, um, you know, everything but the circle. Um, and<br />then save it. And then that&#8217;s the idea being that, you know, you hit save here and then the next<br />time you come into here where you&#8217;re setting your featured image circle would be the only thing<br />available.<br />Um, and obviously if there&#8217;s, if there&#8217;s only one, then it&#8217;ll be pre-selected and so then [00:31:00]<br />it saves you a step. Um, and then, and then there&#8217;s also the option of, um, so this isn&#8217;t quite</p>



<p>functioning, but, um, Choose a preset. So it&#8217;s, if you, if you know, I&#8217;ve now deleted all of the, the<br />default preset 16 nine, you can re-add it here, or there&#8217;s this, you know, I, this just, this is my<br />preset, but it&#8217;s like you can, you can name it the query, uh, Miller preset with an aspect ratio of,<br />you know, whatever, whatever.<br />Um, I think this works. Yeah. There&#8217;s the Corey Miller preset. Um, awesome. So, so this is, this<br />is what I started with, um, again, with the idea that what you set is what&#8217;s gonna get translated<br />to here. So the presets are choose your shape, you then have those to choose from. Um, and<br />then when you cropped an [00:32:00] image, the output would match whatever your Minn Max<br />is.<br />Um, I haven&#8217;t quite, I&#8217;m not sure what. Parallel is yet, is it, is it always you? It should be the<br />minimum, but should it go up to the max? You know, we&#8217;ll figure that out. But, um, is, is this kind<br />of what you had in mind? Does this resonate with you? Anything missing?<br />Cory Miller: Um, now that the preset thing is really awesome, like being able to set that here, I<br />think that&#8217;s very forward thinking.<br />Work. You know, I continue to think through work, through flow, come in here, configure it<br />yourself, save it, make it easier on the client, and it becomes a pretty easy thing to, for the<br />problem of getting right sized images per the theme design. So I think that&#8217;s cool. Would you<br />scroll up a little bit? So this puts it, [00:33:00] this men stuff puts it where, Any image that goes<br />through it and scrub by it will not be bigger.<br />So that then whatever we&#8217;ve listed here.<br />Corey Maass: Okay. Yeah, the, you know, it&#8217;s like if you thinking about pr, you know, protecting<br />people from themselves. So if they upload a 10 pixel by 10 pixel emoji and they, but they want to<br />use that as a high res, uh, featured image, then it. Upscale it and look terrible, but that&#8217;s better<br />than them, than a 10 by 10 pixel image getting stuck in there.<br />And then same with like, what we keep talking about is uploading from your photo where, or<br />uploading from your phone where a photo is six megs. No, bring it down, you know, and, and,<br />and 4,000 pixels. It&#8217;s like, no, bring it down to the web. Really doesn&#8217;t need more than 2000<br />pixels. [00:34:00]<br />Cory Miller: So, okay, so the experience is come in here, set it here, put some guardrails.<br />Um, bumpers. Bumpers. Keep talking about bowling, bowling. Bowling bumpers. Okay. Then<br />when they go to do it from like, this is the basic settings. Start, you know, start hearing, get a<br />little bumpers, but then the workflow, if they&#8217;re going into the image and all that kind of stuff. Is<br />there a plan for. Letting them customize that in the featured image and the other, you know,<br />tools in the post.<br />That&#8217;s a good question because here&#8217;s what I&#8217;m thinking. Like web designer developer would<br />go, there&#8217;s your guardrails. Cool. You know? Yeah. And then they get into the live, and I think<br />maybe they, like we were doing the ratios to be simple. Click boom, there you go. But if<br />someone goes. You know, I don&#8217;t know.<br />I want [00:35:00] the cropped image, like I think we were talking about, there&#8217;s a featured image<br />section, then there&#8217;s another section which is in lieu of the block. Yeah. It&#8217;s like upload an image<br />and, and my question would be like, I think we should consider in that, that screen over there,<br />letting them do the custom dimensions there potentially.<br />Corey Maass: Mm. Yeah, so I, I think if I understand you, like we&#8217;ve got a, we&#8217;ve got a bypass,<br />which lets them upload. Straight from their hard drive. And then I also think, if I&#8217;m hearing you<br />correctly, we need a bypass, essentially, these settings. So it&#8217;s like you can still use the cropper,<br />but you can essentially make bad choices if you want to.<br />Uh, and I, and I think maybe that, like there&#8217;s a, I also envision a toggle in here that enables<br />that. And so there&#8217;d be like, here are the [00:36:00] guardrails, you know, a and maybe this<br />screen, so at least, at least for my use case, right? I am, I am an ad I, I have the WordPress<br />admin role. I have the WordPress role of administrator, and then all of my clients have a<br />contributor role, or I&#8217;ve made up another, um, another role called site admin.<br />And so they still think that they&#8217;re admins, but I&#8217;ve actually disabled a bunch of things so that<br />again, they can&#8217;t, they can&#8217;t go in and update a plugin that they shouldn&#8217;t or delete a plugin or<br />change themes. Have had clients go in and just be like, what does this do? And totally break a<br />site. . And so I think in, in, in here, there&#8217;s a, there&#8217;d be a, like an advanced toggle that says, lock<br />this shit down.</p>



<p>Yeah. Or these are the recommended. Let them make bad choices if they want to. And so like<br />for my clients, for [00:37:00] featured images, hard, hard, hard rule, it&#8217;s 16 nine. Full stop, no<br />exceptions. And so I would switch that toggle to be like, do not let them make any other choices.<br />But you know, the o our other implementation, so this screen would essentially be repeated for<br />media library.<br />I haven&#8217;t reported it over yet, but in media library I might allow more presets. I also might toggle<br />it the other way and say, you know, let them. Upload something because frankly, like we also<br />use the media library for, um, you know, hosting an image to send to the press. And so we then<br />we want a high res image and we&#8217;re just basically using our WordPress install as file storage.<br />And so they would, they would hit a little button that says, just let me upload, you know, leave<br />me alone and let me upload the, the image or let me crop it, but leave it at 7,000 pixels or, or<br />whatever. So, yeah. [00:38:00] That&#8217;s another necessary.<br />Cory Miller: I think this is the work, this is the workflow for an organization or the developer<br />here in this screen.<br />Yeah. What I&#8217;m thinking is I go, okay, because we, the crux of the problem we started with<br />months ago was it&#8217;s a pain in the butt to like crop an image to make it reasonable for the web<br />and look good. And I, if I&#8217;m just Corey Blogger, Corey website thing, I go, okay, I&#8217;m writing a<br />post. I go, okay, I need an image.<br />I want an image for it in here and want it. Obviously I you won&#8217;t believe how many times I&#8217;ve like<br />gotten. A screenshot tool or something to go How many pixels wide is my Yeah. Post column<br />with, you know, and I, we&#8217;ve talked a lot about this, but I go, maybe I [00:39:00] want it really tall<br />in the, in the place or something like that doesn&#8217;t fit a preset mm-hmm.<br />you know, like, here&#8217;s the quick presets we&#8217;ve done. Just go here and you can kind of keep it<br />standard that checks that consistent box, but, Utility of the crop to make it whatever it needs to<br />be for that page design. Yeah, that&#8217;s the workflow I&#8217;m thinking about because I think this is<br />where we need to be for the, I&#8217;m handing this project over to you and I&#8217;m trying to keep you right<br />in the bumpers and I think that big time checks the agency box and some point I wanna share<br />that with our agency owner channel and just get some feedback and.<br />Understand the problems they actually face, but the other side is to make this ubiquitous and<br />easy to use. How do we make it really practical and easy for what they&#8217;re trying to do? And I&#8217;m<br />just talking that out, going, I wonder, you know, they find the image, [00:40:00] they upload it,<br />but they want it, you know, you know how it goes.<br />Sometimes the image doesn&#8217;t fit right. A, a ratio.<br />Corey Maass: So, yeah. Well, and yeah, and I think, you know, we. What we don&#8217;t want to do is<br />limit people&#8217;s creativity and so, you know, and what&#8217;s WordPress? Uh, The mantra, but I think it,<br />I think it&#8217;s actually backwards. They say decisions, not options or something like that.<br />But anyway, in, in our case, we actually want at least, at least sensible options. Um, you know,<br />or, or we don&#8217;t, we can&#8217;t speak for everybody, at least not yet . Um, and, and so yeah, letting<br />people. Bypass the, all these things. Um, I think if nothing else, you know, I mean more of the<br />spirit of WordPress and, and more, you know, the freedom to, to do what you want.<br />I mean, they can always disable the plugin. I&#8217;ve even done that with, there&#8217;s a plugin by short<br />[00:41:00] pixel that. It&#8217;s called something like resize after Upload. And so it, I installed that early<br />on so that client&#8217;s uploading it just lets you, uh, ju similar to some of this, right? It lets you set a<br />sensible limit, so it&#8217;s like resize anything over 2,500 pixels, down to 2,500 pixels.<br />And that&#8217;s all it does, but it&#8217;s it per it, it has saved us so much disk space. They will make a<br />mistake and upload something that&#8217;s, you know, two megs and 7,000 pixels or whatever. So,<br />um, but I&#8217;ve had to. Like, there were times when we wanted, uh, like we had a blog post that<br />was a web comic, and so we needed it 7,000 tall.<br />So I went in disabled, the plugin, and this is the process I had to do right as I went in. Had to go<br />in, disable the plugin, upload the full, full version, and then go back in and reenable the plugin.<br />So yeah, if there was a like click here to bypass just this one time, [00:42:00] uh, you know, then<br />it would&#8217;ve saved me.<br />Six clicks and a, and a bunch of load time. Um, so yeah, to, to make sure that we ac we<br />accommodate that or offer the option to accommodate that , uh, options to offer options always<br />gets a little meta, but I do think that that&#8217;s crucial as much because like we keep talking about,<br />we don&#8217;t, we just don&#8217;t know yet.</p>



<p>We don&#8217;t know who&#8217;s really gonna use this. We don&#8217;t really know. And that&#8217;s, that&#8217;s why like, I<br />like the thinking. We did at the beginning of this phone call about using, talking about filters. But<br />to me, filters is an example or of, of that, which we don&#8217;t know yet, but are the kind of features<br />that we can offer.<br />Not fi filters specifically, but some sort of photo manipulation, assuming that that&#8217;s what people<br />want. But I also, I think I&#8217;ve, I mean, I&#8217;m having fun looking at discovering. How robust<br />JavaScript is [00:43:00] now and, and what it can do, including photo manipulation. But to me,<br />cropping a circle was a no-brainer for this, you know, for v1.<br />But adding photo filters is, is down the road at some point because it&#8217;s, it could be a lot of noise<br />within the product and if nobody wants it, then we don&#8217;t wanna add that much noise.<br />Cory Miller: I feel like too, a lot of this just kind of pulling up for the overall product journey we&#8217;re<br />on. Mm-hmm. is trying to find that spark.<br />Yeah. Like we&#8217;re talking through things that we think are good ideas, thought like really<br />thoughtfully trying to embody the experience and I feel like we&#8217;re trying to find a little spark of<br />something when we, when we talk about feedback and like, Someone goes, yeah, that what you<br />just said there, but like a lot of the process of product like this is trying to get just lucky and, and<br />find that little spark of, [00:44:00] hey, here it, here it goes.<br />You know? So it&#8217;s good for me to kind of reset and go, yeah, doesn&#8217;t feel good to see fewer than<br />10, you know? But like we&#8217;re trying to get it out there enough and we&#8217;re doing this obviously, so<br />we find a spark somewhere in there and they go, Hey, that&#8217;s what I. To, I don&#8217;t know, let&#8217;s, let me<br />throw in another sport.<br />Fishing,<br />We&#8217;re trying to fish and go like, yeah, we think this is good. So I&#8217;m trying not to make too many,<br />um, minute feedback things about the thing. I go. We, we, we decided a couple weeks ago, we<br />kept talking about like the custom dimensions. So you&#8217;ve done the settings page and now this<br />seems to be the other side.<br />And just kind of getting it out there and going, like, does this, does this work? Part of it, I think<br />for me is I&#8217;m not actively blogging as much at all, and I haven&#8217;t for a long time, but I need to get<br />back in the [00:45:00] process and start documenting, you know, when I&#8217;m Yeah. Trying to<br />express a. Feeling, emotion, whatever those things are.<br />Um, and then going through the press of like, what, you know, for me, I&#8217;m trying to commit to<br />this, this going, okay, let me find an image for this. That kind of hits at what I&#8217;m trying to get at,<br />you know? Yep. Um, back to Instagram, that&#8217;s what I loved about Instagram and those little<br />apps, you remember those apps that take like a second a day and it&#8217;d kind of be a journal and.<br />It started with an image and then it became, you know, people tried to blow up the content<br />underneath. Um, I needed to play around that with, in my head a little bit and practice it of like,<br />what if I started with an image and wrote and just put, get back doing my click and publish<br />again, and then note all my pain points with finding [00:46:00] images that are appropriate.<br />Corey Maass: And I&#8217;m going to, um, to me we&#8217;re, I like your fishing analogy. We&#8217;re fishing with<br />a, with a all lure. We&#8217;re still building. You know, we, we&#8217;ve got the hook and we&#8217;ve got the eyes,<br />but we need the little wiggly bit that the fish will actually be attracted to or whatever. Um, but I&#8217;m<br />not, I guess I&#8217;m, to me, I&#8217;m not yet casting with the intent of actually catching fish like I&#8217;m casting<br />to just kind of make sure that it, it all still holds together when it hits the water.<br />Um, I think with a, with some basic settings, uh, with a block at that point. Like I wanna start<br />promoting it a lot more, putting it on, you know, actually put it in some places. Um, I think at that,<br />that&#8217;s when, you know, we actually are version complete and we can start sending it to some<br />blogs. Um, You know, you, you do a, a Google search for word [00:47:00] plug, you know,<br />WordPress plugin, photo cropping or photo manipulation, and then go find all those listicles and<br />add some comments and, and basically just do kind of the, the, the bare minimum, uh, s e o and<br />spreading of the word.<br />I think the other thing is, um, I don&#8217;t remember who it was, um, Kathy. Or somebody. Yeah,<br />Kathy, um, typed in crop, uh, in the plug-in directory and. Um, and it was like, I think just crop,<br />we&#8217;re not even on the first page. If you do crop.express, we come right up, but crop space<br />express doesn&#8217;t come up. So we, you know, we need to start tweaking some of, you know,<br />looking at, cuz at that point, like the, the README that&#8217;s in there now is, is almost, is already<br />almost not.</p>



<p>Accurate in that we&#8217;ve added more features. And so revisiting that, revisiting the wording,<br />starting to play with the [00:48:00] wording, but it&#8217;s like at that point we are at least a fully<br />functional product. And so then, then I feel much better about talking about it. I also look forward<br />to like, I will make my clients use this whether they like it or not, and I will toggle it so that they<br />are locked down.<br />Um, and then I will hear their complaints, you know, good, or, or I guess you don&#8217;t have good<br />complaints, but I will hear their feedback, good or bad. Um, but it&#8217;s, um, you know, to me a very<br />real world use case. So, um, we&#8217;re. I guess I&#8217;m trying to get us there, right? Like basic settings,<br />basic implementation. Um, and then I, I, and then frankly, like at that point, at we, we, we.<br />It&#8217;s fun to keep talking every week, but I almost feel like at least what I&#8217;ve done in the past is at<br />that point we, like, we let a couple of months go by and maybe we&#8217;re working on, we&#8217;re still<br />working on it [00:49:00] or we&#8217;re working on a companion or we&#8217;re, you know, something else is<br />cooking. But, um, The, you know, one of the best things that happened to me was, you know,<br />my social link pages plug in.<br />I built it and then, uh, had to stop working on it cuz of a job I was doing. And the year went by<br />and I stopped doing that job and I came back and was like, oh, it has a thousand active installs.<br />And it was like letting it grow organically. Mm. You know, letting time happen naturally. Like I<br />probably could have made that ramp happen a little bit faster, but not a lot, you know, at least at<br />the level I&#8217;m at.<br />Like we, like we talked about, if you&#8217;re starting from zero, you&#8217;ve only got so many favors you<br />can call in. You&#8217;ve only got so many eyes on you. You&#8217;ve only got, um, you know, I think we&#8217;ve,<br />we&#8217;ve both got a little bit of an, I, you&#8217;ve got a much bigger audience than I do. We both are<br />involved with communities, but you know, we are not, [00:50:00] Uh, who&#8217;s a successful<br />blogger?<br />Tim Ferris or, you know, Paul Jarvis or, um, Joel s Spolsky, or, you know, whoever, like big, big<br />names that have attention on them. And so we&#8217;ve, we&#8217;ve, there will be, there will come a day<br />when we&#8217;ve, we&#8217;ve basically tapped every lead that we can think of, and then it&#8217;s like, okay, so<br />let&#8217;s let a week go by and let some, you know, let the internet do its job and, and spreading the<br />word.<br />Cory Miller: That&#8217;s good grounding.<br />Corey Maass: It&#8217;s hard. It&#8217;s hard,<br />Cory Miller: like even if I want to, I, I&#8217;m always so impatient and want to accelerate and get to<br />the things, but I, that&#8217;s really good grounding.<br />Corey Maass: It&#8217;s like, well, if we, if we had a gajillion dollars, if, if we had investment, I&#8217;m not,<br />obviously, I&#8217;m not advocating that, but it&#8217;s like, If we were in that kind of situation or we were able<br />to, you know, sit down in an office day after day and say like, this is our job.<br />[00:51:00] Very different trajectory. Yeah, but I don&#8217;t, but we&#8217;re not in that position.<br />Cory Miller: Yeah, it&#8217;s true.<br />Okay. Well anyway, so go ahead.<br />Corey Maass: Oh, I was just gonna say like, we&#8217;ve got five minutes and I actually need to wrap<br />up on time today, so, okay. Um, just wanted to check in with you, see, see if there&#8217;s anything<br />else to talk about or what else you wanted to talk about. Put you on the spot here. I<br />Cory Miller: think that&#8217;s it. I want to keep kind of pushing in and trying to find, um, I think my<br />part in this is sniffing the problem that we go there.<br />It, you know, there it is. That could potentially illuminate it to bring in money for sales, whatever it<br />might be. But, um, and going like, I think we got a pretty cool thing here. It seems to me for the<br />future, it&#8217;s like [00:52:00] image creation in that cate, something in this category is the potential<br />for the pro. And I&#8217;m keen to just go, like, personally finding the angles in there that would go right<br />here.<br />This could be a little, this could be a V1 into the paid, you know, finding that, that little mix. But<br />thanks for keeping us on track with this. I, I think where we&#8217;re going with this setting is great. It&#8217;s<br />all there. It&#8217;s functional or it will be, and, uh, try to get a little bit more stepped in the, into the.<br />Finding our people<br />Corey Maass: Yeah. For this. Yeah. And I&#8217;m, I&#8217;m, you know, I don&#8217;t think I need to say it, but I&#8217;ll<br />say it anyway. Don&#8217;t get me wrong. Like, I&#8217;m also anxious and excited. Unfortunately, this week,<br />once again, life happens. And so I&#8217;ve, on Monday, a tight deadline Okay. With a day job. Um, but<br />I&#8217;m, but I&#8217;m, there&#8217;s something is going to shift [00:53:00] and I, I almost want to, uh, I wanna</p>



<p>make sure we don&#8217;t keep having the same conversation week over week, , uh, both for the<br />people listening in, but of course for ourselves.<br />Cuz that that&#8217;s also when we&#8217;re like, okay, yeah, last week we said we were gonna do this, it&#8217;s<br />still not done. So I guess another week goes by, you know, and then, and then we get frustrated.<br />So, um, trying to chip away at it and. But I think, cuz I think something will shift once we<br />honestly look at our, what, at our initial offering crop express the plugin and say, okay, that&#8217;s in<br />the repo as as a complete fishing lure, , or whatever.<br />Um, you know, and, and, and people are using it. And we are using it cuz it actually like does<br />solve the problems that we&#8217;re talking about.<br />Cory Miller: Yeah. Yeah. I wrote down here too, when you said block earlier, uh, I&#8217;ll follow back</p>



<p>up with Robbie [00:54:00] Umhmm. That&#8217;s right. We had the whole thing come back. Yeah. Mm-<br />hmm. . But it seems like I knew Block had some complexity, uh, you know, that we talked about,</p>



<p>but I know you&#8217;re heavily embedded into the Beaver Builder community and used it prolifically.<br />And we got that contact with Robbie, so I&#8217;ll follow back up with him. Kathy was the other one.<br />And then I still need to ping the Elementor team. Um, cuz that could be a, you know, it feels like<br />we need that. Somebody going Yeah. But mm-hmm. this or, you know, reactions like, what, what<br />we need. So, um, let me do that with the Robbie, Kathy, aunt Cadence and then, um, ping, ping<br />the team over at on Mentor.<br />Corey Maass: Yeah, and honestly like think about, so I, I think one of the things that you could<br />be doing. Is, or, or what you are doing, but [00:55:00] do more of, is this kind of, essentially, it&#8217;s<br />not really a custom inter customer interview, but kind of, sort of, yeah, yeah. Um, so like, you<br />know, put it on your Twitter or look for a way to, to elevate that question in post status or, and I,<br />I&#8217;m not sure what the question is, but I, I kind of want to put that, put that on your plate.<br />Let me keep focusing on the development of, of the first version of the plugin. Um, but if you can<br />be having starting, or, I mean, and, and usually, you know, tweet into the void and maybe<br />nobody comes back, but it&#8217;s the, like, you know, how, how do you, how do you find images or<br />like, that&#8217;s not the problem we&#8217;re solving yet, so I don&#8217;t wanna really ask that question yet.<br />But, you know, how, what problem, how painful do you, yeah. You know, is it, do you, do you,<br />you know, either define the problem, you know, do you have, do you wish that there was a<br />better crop in WordPress? Or what apps [00:56:00] do you use to manipulate a photo before<br />you upload it to your blog post? Or, um, you know, I think there&#8217;s, I think there&#8217;s, you asked a<br />couple of questions to help figure out the right question to ask and then start asking that in more<br />places.<br />Um, okay. Cuz that, that&#8217;ll. I think it&#8217;s, you know, you pinging the specific people is huge. Um,<br />especially tapping into if, if they are a, a essentially a gateway into, uh, a community or a, a<br />team that is facing a problem over and over again. But I would, I&#8217;d love to hear some, like,<br />answers in the wild too of like throw it on Twitter and see if, if people.<br />Have a response, you know? Um, yeah, because like you said, there&#8217;s, I, I do feel like we are<br />looking for a spark. Like I have this other, um, app, you know, a p i service that I built a while<br />ago that I want to talk to you some other time [00:57:00] about offline. Um, But it&#8217;s like I, and, uh,<br />well, I&#8217;ve mentioned a couple times.<br />I, I built it 99% of the way and then stopped and have not opened it up because I&#8217;m like, I&#8217;m just<br />missing that spark. Like the, and, and then just today somebody, it, it pertains to screenshots.<br />And so somebody today was like, oh, is there a WordPress plugin that takes this kind of<br />screenshot? And I was like, oh my God, I never even thought of that.<br />And I don&#8217;t, I don&#8217;t, still don&#8217;t know if it&#8217;s the spark, but I&#8217;m, you know, I&#8217;m pulling at that thread. I<br />messaged the guy and then we&#8217;re. We&#8217;re chatting via email, like I might bang together a quick<br />use case for &#8217;em to like see if that&#8217;s part of the spark. You know what I mean? So<br />Cory Miller: I, I would love to talk about that.<br />Cause you&#8217;ve mentioned it in our other discussions. I&#8217;d love to talk about that more because, I<br />mean, I think there&#8217;s one thing that I&#8217;m really interested in. It&#8217;s like images and they mentioned<br />Yeah, exactly. No, being able to do that and like, I love the, I think it was a screen. Tool<br />potentially you were talking about?<br />Um, yeah. [00:58:00] Or in that realm. And Yeah. And it makes me put, like, higher on my list is<br />the OMG IMG site as our base for Yeah. Being able to explore this. Here&#8217;s your free plug into<br />crop, you know, like that sticker mill thing. Like here&#8217;s your total mm-hmm. ,<br />Corey Maass: which by, by the way, Sticker Mule, they have, um, specials once in a while.</p>



<p>So I ordered us, um, 10 crop express stickers for a dollar. So we have our first swag, so as it, it<br />has shipped. So I need your, I need your address. Yep. And, uh, uh, I&#8217;ll send you five. And then<br />we each have five crop express plugin or, um, plugin stickers for, for the fun of it. .<br />Cory Miller: I, I want an OMG IMG Hoodie<br />Corey Maass: oh yes. . Yes.<br />And that, that logo, we&#8217;re gonna need to spend a little more time on roughly. So, yeah,<br />[00:59:00] I want, I want rainbows and unicorns or something. I don&#8217;t know yet. Ice cream<br />cones, but hey brother, I could keep<br />Cory Miller: talking, but I know you need to jet.<br />Corey Maass: Yeah, I gotta bounce.<br />Cory Miller: All right. Uh, I&#8217;m pumped. Thanks, man.<br />Corey Maass: Yeah, we&#8217;ll talk soon.</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, 30 Mar 2023 13:34:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:42;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s: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:4550:"<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>.&nbsp;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 that are imported 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 million 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>&nbsp;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:43;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s: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:21940:"<h2 class="wp-block-heading" 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 /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f7e6.png" alt="🟦" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/">Proposal: The Interactivity API – A better developer experience in building interactive blocks</a><br /><br />3&#x20e3; <a href="https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/">Phase 3: Collaboration</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f3b7.png" alt="🎷" class="wp-smiley" /> <a href="https://make.wordpress.org/design/2023/03/30/why-jazz/">Why Jazz?</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 class="wp-block-heading" 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="wp-block-columns is-layout-flex wp-container-12">
<div class="wp-block-column is-layout-flow">
<h2 class="wp-block-heading" id="h-community"><a href="https://make.wordpress.org/community">Community</a></h2>



<ul>
<li><a href="https://make.wordpress.org/community/2023/03/30/community-team-goals-for-2023-2nd-chat-session/">Community Team Goals for 2023 : 2nd Chat session</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/">Proposal: The Interactivity API – A better developer experience in building interactive blocks</a></li>



<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 class="wp-block-heading" 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 class="wp-block-heading" id="h-meetings">Meetings</h3>



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



<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 class="wp-block-heading" 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 class="wp-block-heading" id="h-design"><a href="https://make.wordpress.org/design">Design</a></h2>



<ul>
<li><a href="https://make.wordpress.org/design/2023/03/30/why-jazz/">Why Jazz?</a></li>



<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 class="wp-block-heading" 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="wp-block-column is-layout-flow">
<h2 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" id="h-support"><a href="https://make.wordpress.org/support">Support</a></h2>



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



<h2 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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 class="wp-block-heading" 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://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:44;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:56896:"<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>



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



<p>“Dolphy” includes several impressive performance improvements. You’ll note overall faster load times for block themes of 14 to 18%, and for classic themes, speed increases of 2 to 5%. Server-side performance is also significantly boosted, with an increase of 17 to 23% for block themes and 3 to 5% for classic themes, 3 to 5%. The performance team is dedicated to these kinds of improvements. You can learn more about their work by following the Making WordPress blog using the <a href="https://make.wordpress.org/core/tag/performance/">#performance hashtag</a>.</p>



<blockquote class="wp-block-quote"></blockquote>



<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/">Bjorn Holine</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/ironprogrammer/">Brian Alexander</a> · <a href="https://profiles.wordpress.org/bgardner/">Brian Gardner</a> · <a href="https://profiles.wordpress.org/bronsonquick/">Bronson Quick</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/">Devanshi Joshi</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/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/mmaattiiaass/">Matias Benedetto</a> · <a href="https://profiles.wordpress.org/matveb/">Matias Ventura</a> · <a href="https://profiles.wordpress.org/mattkeys/">Matt Keys</a> · <a href="https://profiles.wordpress.org/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/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/pypwalters/">Stephanie Walters</a> · <a href="https://profiles.wordpress.org/sabernhardt/">Stephen Bernhardt</a> · <a href="https://profiles.wordpress.org/netweb/">Stephen Edgar</a> · <a href="https://profiles.wordpress.org/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/">Tahmina Rahman</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:45;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:46;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:47;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:48;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:49;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:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:48:"WpOrg\Requests\Utility\CaseInsensitiveDictionary":1:{s:7:"*data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 19 Apr 2023 15:45:28 GMT";s:12:"content-type";s:8:"text/xml";s:13:"last-modified";s:29:"Wed, 19 Apr 2023 15:30:30 GMT";s:4:"vary";s:15:"Accept-Encoding";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:16:"content-encoding";s:2:"br";s:4:"x-nc";s:9:"HIT ord 2";}}s:5:"build";s:14:"20211221090300";}