


<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/05/episode-56-what-to-know-about-wordpress-playground/">WP Briefing: Episode 56: What to Know About WordPress Playground</a></li>



<li><a href="https://wordpress.org/news/2023/05/wordpress-6-2-2-security-release/">WordPress 6.2.2 Security Release</a></li>



<li><a href="https://wordpressfoundation.org/news/2023/kim-parsell-memorial-scholarship-for-wordcamp-us-2023/">Kim Parsell Memorial Scholarship for WordCamp US 2023</a></li>
</ul>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Look closely. Did you know this wizardry is currently possible in the Editor?!?<br /><br />Join us on Thursday for the next <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a> Hallway Hangout where we'll discuss curating the Editor and building block themes for clients. RSVP<img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f447.png" alt="👇" class="wp-smiley" /><a href="https://t.co/DPqrFHVXtT">https://t.co/DPqrFHVXtT</a> <a href="https://t.co/XbZBC97QDu">pic.twitter.com/XbZBC97QDu</a></p>&mdash; Nick Diego (@nickmdiego) <a href="https://twitter.com/nickmdiego/status/1660712789491548160?ref_src=twsrc%5Etfw">May 22, 2023</a></blockquote>
</div>



<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"><a href="https://make.wordpress.org/accessibility">Accessibility</a></h2>



<ul>
<li><a href="https://make.wordpress.org/accessibility/2023/05/22/accessibility-team-meeting-notes-may-19-2023/">Accessibility Team Meeting Notes: May 19, 2023</a></li>
</ul>



<h2 class="wp-block-heading"><a href="https://central.wordcamp.org">Central</a></h2>



<ul>
<li><a href="https://central.wordcamp.org/news/2023/05/siteground-joins-the-wordpress-global-community-sponsorship-program-in-2023/">SiteGround joins the WordPress global community sponsorship program in 2023</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/05/24/idea-generation-next-gen-wordcamps/">Idea generation: Next Gen WordCamps!</a></li>



<li><a href="https://make.wordpress.org/community/2023/05/20/wordpress-community-team-discussion-9-the-next-generation-of-wordcamps/">WordPress Community Team Discussion #9: The Next Generation of WordCamps</a></li>



<li><a href="https://make.wordpress.org/community/2023/05/20/recap-of-the-contributor-working-groups-mentorship-chat-on-may-18-2023/">Recap of the Contributor Working Group’s Mentorship Chat on May 18, 2023</a></li>



<li><a href="https://make.wordpress.org/community/2023/05/19/siteground-joins-the-2023-global-sponsorship-program/">SiteGround Joins the 2023 Global Sponsorship Program</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/05/18/wordpress-6-3-planning-roundup/">WordPress 6.3 Planning Roundup</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/18/roadmap-to-6-3/">Roadmap to 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/17/command-center-request-for-feedback/">Command Center: Request for feedback</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/16/proposal-retiring-older-default-themes/">Proposal: Retiring Older Default Themes</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/22/core-editor-improvement-smoother-site-editing/">Core Editor Improvement: Smoother Site Editing</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/20/whats-new-in-gutenberg-15-8-may-17/">What’s new in Gutenberg 15.8? (May 17)</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/24/a-week-in-core-may-22-2023/">A Week in Core – May 22, 2023</a></li>
</ul>



<h3 class="wp-block-heading" id="h-developer-blog"><a href="https://developer.wordpress.org/news/">Developer Blog</a></h3>



<ul>
<li><a href="https://developer.wordpress.org/news/2023/05/curating-the-editor-experience-with-client-side-filters/">Curating the Editor experience with client-side filters</a></li>



<li><a href="https://developer.wordpress.org/news/2023/05/useentityrecords-an-easier-way-to-fetch-wordpress-data/">useEntityRecords: an easier way to fetch WordPress data</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/core/2023/05/23/editor-chat-agenda-24-may-2023/">Editor Chat Agenda: 24 May 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/23/dev-chat-agenda-may-24-2023/">Dev Chat Agenda, May 24, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/19/wp-feature-notifications-meeting-notes-2023-05-17/">WP Feature Notifications Meeting Notes: 2023-05-17</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/design/2023/05/23/wordcamp-sylhet-2023-contributor-day-recap/">WordCamp Sylhet 2023: Contributor Day Recap</a></li>



<li><a href="https://make.wordpress.org/design/2023/05/22/design-share-may-8-may-19/">Design Share: May 8—May 19</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/05/22/online-monthly-docs-team-contributor-day-may-23-2023/">Online monthly Docs Team Contributor Day May 23, 2023</a></li>



<li><a href="https://make.wordpress.org/docs/2023/05/22/summary-for-docs-team-meeting-may-16-2023/">Summary for Docs Team meeting, May 16, 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/05/15/is-wordpress-compatible-with-php-8/">Is WordPress compatible with PHP 8?</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/05/24/day-17-wp20-from-blogs-to-blocks/">Day 17: #WP20 From Blogs to Blocks</a></li>



<li><a href="https://make.wordpress.org/marketing/2023/05/23/day-16-wp20-from-blogs-to-blocks/">Day 16: #WP20 From Blogs to Blocks</a></li>



<li><a href="https://make.wordpress.org/marketing/2023/05/22/day-15-wp20-from-blogs-to-blocks/">Day 15: #WP20 From Blogs to Blocks</a></li>



<li><a href="https://make.wordpress.org/marketing/2023/05/21/day-14-wp20-from-blogs-to-blocks/">Day 14: #WP20 From Blogs to Blocks</a></li>



<li><a href="https://make.wordpress.org/marketing/2023/05/20/day-13-wp20-from-blogs-to-blocks/">Day 13: #WP20 From Blogs to Blocks</a></li>



<li><a href="https://make.wordpress.org/marketing/2023/05/19/day-12-wp20-from-blogs-to-blocks/">Day 12: #WP20 From Blogs to Blocks</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/04/11/contribute-to-the-future-of-the-wordpress-app/">Contribute to the Future of the WordPress App</a></li>



<li><a href="https://make.wordpress.org/updates/2023/05/18/mobile-team-update-may-17th/">Mobile Team Update – May 17th</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/05/18/catalog-postgres-exploration-effort/">Catalog Postgres Exploration Effort</a></li>



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



<li><a href="https://make.wordpress.org/openverse/2023/05/23/openverse-monthly-priorities-meeting-2023-06-07/">Openverse Monthly Priorities Meeting 2023-06-07</a></li>



<li><a href="https://make.wordpress.org/openverse/2023/05/22/last-week-openverse-2023-05-15-2023-05-22/">A week in Openverse: 2023-05-15 – 2023-05-22</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/05/23/performance-chat-summary-23-may-2023/">Performance Chat Summary: 23 May 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/05/17/plugin-review-team-update/">Plugin Review Team Update</a></li>



<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/05/09/plugin-review-team-update-8-may-2023/">Plugin Review Team Update: 8 May 2023</a></li>



<li><a href="https://make.wordpress.org/updates/2023/05/15/plugin-review-team-15-may-2023/">Plugin Review Team: 15 May 2023</a></li>
</ul>
</div>



<div class="wp-block-column is-layout-flow">
<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/05/24/polyglots-table-contributor-day-at-wordcamp-sylhet-2023/">Polyglots Table: Contributor Day at WordCamp Sylhet 2023</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/05/23/agenda-weekly-polyglots-chat-may-24-2023-1300-utc/">Agenda: Weekly Polyglots Chat – May 24, 2023 (13:00 UTC)</a></li>
</ul>



<h2 class="wp-block-heading" id="h-project">Project</h2>



<ul>
<li><a href="https://make.wordpress.org/project/2023/05/17/wordpress-contributor-mentorship-program-pilot-program-proposal/">WordPress Contributor Mentorship Program: Pilot Program Proposal</a></li>



<li><a href="https://make.wordpress.org/project/2023/04/13/wordpress-at-20-in-print/">Building Blocks: The Evolution of WordPress 2013-2023</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/05/23/test-chat-summary-23-may-2023/">Test Chat Summary: 23 May 2023</a></li>



<li><a href="https://make.wordpress.org/test/2023/05/22/xpost-test-team-update-22-may-2023/">Test Team Update: 22 May 2023</a></li>



<li><a href="https://make.wordpress.org/test/2023/05/18/fse-program-testing-call-23-rapid-revamp/">FSE Program Testing Call #23: Rapid Revamp</a></li>



<li><a href="https://make.wordpress.org/updates/2023/05/22/test-team-update-22-may-2023/">Test Team Update: 22 May 2023</a></li>
</ul>



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



<ul>
<li><a href="https://make.wordpress.org/themes/2023/05/18/hallway-hangout-curating-the-editor-and-building-block-themes-for-clients/">Hallway Hangout: Curating the editor and building block themes for clients</a></li>



<li><a href="https://make.wordpress.org/themes/2023/05/17/theme-handbook-overhaul-phase-2-creating-content/">Theme Handbook Overhaul: Phase 2 (Creating Content)</a></li>



<li><a href="https://make.wordpress.org/updates/2023/05/16/themes-team-update-may-16-2023/">Themes team update May 16, 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/05/09/brainstorm-wordcamp-europe-2023-contributor-day/">Brainstorm – WordCamp Europe 2023 Contributor Day</a></li>



<li><a href="https://make.wordpress.org/training/2023/05/24/training-team-meeting-recap-for-may-23rd-2023/">Training Team Meeting Recap for May 23rd, 2023</a></li>



<li><a href="https://make.wordpress.org/training/2023/05/19/training-team-meeting-recap-for-may-16th-2023/">Training Team Meeting Recap for May 16th, 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/building-a-page-with-only-patterns/">Building a page with only patterns</a></li>



<li><a href="https://learn.wordpress.org/tutorial/how-to-add-a-blog-or-news-page-to-any-wordpress-website/">How to add a blog or news page to any WordPress website</a></li>



<li><a href="https://learn.wordpress.org/tutorial/introduction-to-wordpress-multisite-networks/">Introduction to WordPress Multisite Networks</a></li>



<li><a href="https://learn.wordpress.org/tutorial/wordpress-editor-modes-for-streamlining-content-creation/">WordPress editor modes for streamlining content creation</a></li>
</ul>



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



<ul>
<li><a href="https://learn.wordpress.org/?meeting=debugging-in-wordpress">Debugging in WordPress</a></li>



<li><a href="https://learn.wordpress.org/?meeting=wp-dev-livestream-sendig-block-theme-2">WP dev livestream: Sendig block theme</a></li>



<li><a href="https://learn.wordpress.org/?meeting=wp-dev-livestream-sendig-block-theme-3">WP dev livestream: Sendig block theme</a></li>



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



<li><a href="https://learn.wordpress.org/?meeting=a-brief-history-of-wordpress-3">A Brief History of 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/creating-a-4-page-business-website/">Creating a 4-page business website</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://nodejs.org/en/blog/release/v20.2.0">Node v20.2.0 released</a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-04-13-1"><a href="https://www.php.net/archive/2023.php#2023-05-11-1">PHP 8.2.6 Released!</a></a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-05-11-2">PHP 8.1.19 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, 24 May 2023 19:57:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:103:"WPTavern: #77 – Mario Santos and Luis Herranz on What the Interactivity API Is and How You Can Use It";s:7:"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=145358";s:7:"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:117:"https://wptavern.com/podcast/77-mario-santos-and-luis-herranz-on-what-the-interactivity-api-is-and-how-you-can-use-it";s: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:43138:"Transcript<div>
<p>[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.</p>



<p>Jukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes and in this case, how you can start to make your sites more interactive.</p>



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



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



<p>So on the podcast today, we have Mario Santos and Luis Herranz. They both work for Automattic but are sponsored to work full-time in WordPress.</p>



<p>The main focus of their work is the block developer experience, and they are part of the group of contributors that worked on the Interactivity API proposal.</p>



<p>The Interactivity API is the main focus of the podcast today, and if you&#8217;re working with blocks and dynamically displaying data, this is sure to be of interest to you.</p>



<p>We start out the podcast today with the usual introductions, and get to know Mario and Luis. And then we learn what the Interactivity API is and what it can do.</p>



<p>The conversation is framed around a blog post written by Mario entitled, The interactivity API, a better developer experience in building interactive blocks.</p>



<p>In this Mario shows examples of what website interactivity is. In short, it&#8217;s the ability for content to be amended on the fly without a page refresh. Of course, this is nothing new on the web. We&#8217;ve been seeing this for years in WordPress sites and elsewhere. But now you&#8217;re going to be able to create interactivity in a standard way across the different blocks on your site.</p>



<p>The project hopes to absorb complexity and make the creation of interactive objects fairly trivial. Mario and Luis talk about examples of where the API might be used, and how it can be implemented.</p>



<p>We also discussed the fact that in the past developers have gone their own way to make their sites interactive. It all works, but it means that no two implementations are the same. This causes issues if the project is taken over by another developer. But it&#8217;s also a drain on resources.</p>



<p>Mario and Luis make the point that having a standard way of creating interactivity will benefit everyone in the long run. We get into the weeds a little and talk about the approach the team took when building the API. They decided to use directives and we find out why this was, and what benefit it brings over other possible solutions.</p>



<p>The project is still experimental, and they&#8217;re looking for people to test and report back on what they find to move the interactivity API forwards.</p>



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



<p>And so without further delay, I bring you Mario Santos and Luis Herranz.</p>



<p>I am joined on the podcast today by Luis Herranz and Mario Santos. Hello.</p>



<p>[00:04:15] Luis Herranz: Hey, hello Nathan.</p>



<p>[00:04:16] Mario Santos: Thanks for inviting us.</p>



<p>[00:04:18] Nathan Wrigley: You&#8217;re so welcome. We had an introduction on Slack from Anne McCarthy, who listeners to the podcast may very well have heard of, and she wanted me to chat to these two about the Interactivity API, so we&#8217;re going to get onto that. It&#8217;s a brand new project. Could be very interesting if you&#8217;re a developer implementing it, but also if you&#8217;re an implementer of WordPress websites and not a developer, you&#8217;ll be interested in the outcomes of it.</p>



<p>Before we do that, the usual questions at the beginning. I&#8217;m going to go to Luis first, if that&#8217;s all right. Would you mind just giving us your backstory, how you&#8217;ve come to be on a WordPress podcast, how long you&#8217;ve been working with WordPress, who you work for as much or as little as you wish.</p>



<p>[00:04:57] Luis Herranz: Okay, thank you. I started creating websites with WordPress 2010, I think, maybe nine, I don&#8217;t know, a long time ago. And I wanted to start a company in 2013, with Pablo Postigo. And we thought, okay, we wanted to create native apps for different companies, like services and so on.</p>



<p>And we knew WordPress, so we basically started with what was later known as headless WordPress, but back in 2013. And since then we iterated, we created a team. We got some investment and we started doing things on top of WordPress. Mostly in headless. First with native applications. Then we moved to just web have applications, but still on headless. Very focused on React.</p>



<p>And in 2019 we launched a open source framework for headless WordPress, powered by React. So we were very focused on developer experience and performance.</p>



<p>And in 2021, that company, Frontity was acquired by Automattic, so we could become like full-time contributors and focus on, well, basically what the Interactivity API proposal is today. Bringing some of those user experiences, what are possible with other solutions, to WordPress itself, on top of full site editing, or block themes.</p>



<p>[00:06:31] Nathan Wrigley: Thank you so much. That&#8217;s really interesting. I appreciate your nice history there. Thank you. And we&#8217;ll ask the same question this time of Mario. So Mario, backstory please.</p>



<p>[00:06:41] Mario Santos: Thank you. Actually, my story is really similar to Luis. Well first, when I finished the degree, I studied industrial engineer, but I didn&#8217;t want to be an engineer. So I started trying different things, and while I got my first job, I created a store in WordPress with WooCommerce. And then, that is when I started to learn about WordPress and all those things.</p>



<p>And later, based on that, I joined Frontity. I don&#8217;t remember exactly the year, 2015 maybe. And from there I really learned what was WordPress because we started going to meetups to WordCamps, and we started to, well at least I started to learn from the community.</p>



<p>From there the story is mostly the same as Luis. We were working on headless mainly. We were working with WordPress. And at some point, we were acquired by Automattic, and now I&#8217;m a sponsored contributor, working full-time. And as Luis said, we are focused on the developer experience, and the Interactivity API that we are going to talk about is part of it.</p>



<p>[00:07:45] Nathan Wrigley: Thank you so much for that. So the Interactivity API, I&#8217;m going to link in the show notes to a post which you can find. Now the post you&#8217;re going to be looking at is on the make.wordpress.org website. It&#8217;s written by Mario. It was on the 30th of March, 2023 that came out, and it&#8217;s entitled, Proposal, The Interactivity API, A Better Developer Experience in Building Interactive Blocks.</p>



<p>Now, if at any point during this podcast you become a little bit confused or you wish to have some more background, I would recommend pausing and going and reading what is an incredibly lengthy and detailed post, with actually a boatload of interaction and comments as well. It&#8217;s really heartening to see so many people chipping in, and giving their thoughts on this Interactivity API.</p>



<p>But I guess the best place to kick this conversation off simply asking, what is it? What is the Interactivity API? What does it do? Why does WordPress need such a thing?</p>



<p>[00:08:47] Mario Santos: I can start with this one. So, the Interactivity API is what we are proposing. The group of contributors that are working on that. It&#8217;s basically a new standard system to easily add front end interactivity to your blocks. Until now, most of the Gutenberg APIs have been focused on the block editor side, and there was unintentional gap on the front end.</p>



<p>So block developers could choose whatever they want. They could choose any Javascript framework, or other solutions. And the Interactivity API aims to cover that gap. Creating this standard.</p>



<p>So imagine functionalities like, like this post or e-commerce functionalities like add to cart, or the checkout, the instant search, page transitions, the comments form, without a page reload. So those are the user experiences that the Interactivity API aims to cover.</p>



<p>In a way that is real easy to build them, and block developers don&#8217;t have to deal with complex scaffolding or external tools. And it&#8217;s important to note also that it&#8217;s completely familiar and compatible with PHP and the block ecosystem. So overall, that&#8217;s what the Interactivity API is. Basically a standard to easily create any interactive experience that your users want.</p>



<p>[00:10:06] Nathan Wrigley: Luis, anything to add?</p>



<p>[00:10:09] Luis Herranz: No, it&#8217;s really filling that gap, or even that opportunity of absorbing as much complexity from the developers. Standardizing everything in a single solution, and making sure that it&#8217;s performant, and so on.</p>



<p>So yeah, there&#8217;s some advancement in web development in other places, mostly in the Javascript ecosystem and WordPress has never been opinionated in the front end, so this is kind of the first time for WordPress.</p>



<p>But yeah, we think that it&#8217;s an opportunity as well to absorb a lot of complexity for the developers, and to enable some of the user experiences that were not possible with WordPress before.</p>



<p>[00:10:52] Nathan Wrigley: Now we have some show notes, and we&#8217;ve got a list of questions that we&#8217;re potentially going to run through, but I&#8217;m going to skip to the end, more or less of the list of our questions. Because one of the things I think to do at the beginning would be to provide listeners concrete examples of how this might be used.</p>



<p>So do you have any examples that you think would demonstrate clearly the kind of things that the Interactivity API is touching on? I&#8217;ll just mention one. Which is the very first thing you&#8217;re going to see more or less when you open up Mario&#8217;s article, and it&#8217;s a video. It&#8217;s pretty short, two minutes long. And it demonstrates something a little bit like Netflix, where you&#8217;ve got, a view of three or four different video thumbnails. There&#8217;s a bunch of different movies there.</p>



<p>And the intention is that you would like to preserve your favorites. And so there&#8217;s a little heart icon, which is lodged in the top left of the thumbnails for each video. And as you click on that thumbnail, the heart becomes colored in. It goes from gray to red. But also in a different part of the UI, in the right hand of the view, the menu, traditional place for the menu, there&#8217;s a little total which goes up from two to three to four, and if you remove the hearts, it goes back down to two and so on and so forth.</p>



<p>So that&#8217;s one example of how you might use this. It&#8217;s able to do things on the page without needing to do page refreshes. And the idea is that this will be a standard way of doing it in blocks. And I wonder if you could give us some other examples. You mentioned WooCommerce and things like that. But let&#8217;s go into that a little bit. Some examples of where this might be useful for developers and end users to know.</p>



<p>[00:12:35] Mario Santos: Yeah, so basically the use case is anything that is interactive and requires Javascript should be able to be done with the Interactivity API in an easy way. So imagine like a slide show or light boxes in the image. So when you click on it, it zooms, and when you click out or scroll, it goes out. Some models like search, subscription, quizzes, e-commerce integrations, like you just have mentioned.</p>



<p>And one of the features that is enabled by having a standard is the client site navigation that basically is navigating through different pages of your WordPress site without triggering a page reload.</p>



<p>It&#8217;s important to know that this is something that is going to be enabled by the Interactivity API, but it&#8217;s going to be completely optional. So if you don&#8217;t need it, you don&#8217;t have to use it. But it powers other features like you can see in the movie, that we are paginating between the different pages. We are in the query loop. You have the pagination block, and you can go through the page one to the page two without page reload.</p>



<p>And for example, well, in the movies demo, we are showing that you can play the trailer and you can keep navigating and the video doesn&#8217;t stop. So those kind of user experiences that, for example, in this podcast you could be listening to this podcast in WP Tavern, and you could navigate to the articles.</p>



<p>So, maybe you can be reading an article while you are listening to the podcast in the same way. And the podcast will keep playing. Those kind of user experiences are enabled by client side navigation. And you can also find in the movies the instant search that you start typing and the list of results is automatically updated.</p>



<p>Infinite scroll could also work. Client size submissions like the comments form right now, in typical WordPress sites, when you submit a new comment, it triggers a page load. So this could be done directly in the client. So those are the kind of user experiences that we are talking about. And yeah, I think it&#8217;s important that this is totally compatible with the current block templating system. So whatever you change in the editor is going to keep working.</p>



<p>[00:14:54] Nathan Wrigley: That&#8217;s great, yeah. Luis, anything to add?</p>



<p>[00:14:57] Luis Herranz: I would add that I really like that demo. Because it&#8217;s a demo that we didn&#8217;t come up with. It was a demo that existed before. There is a version of that demo created with all the major Javascript frameworks out there. So there is one for React using Next, Vue using Nuxt, Svelte, Quick, Astro and so on.</p>



<p>So, you can compare now the WordPress version with the other Javascript frameworks, out there. I&#8217;m super happy to say that it really, in terms of user experience now with Interactivity API, you can provide the same user experience than the others. And this demo was created to show these type of complex or great user experiences.</p>



<p>With WordPress, now with the Interactivity API, you&#8217;re able to create that type of user experience, but leveraging the server side and the block editor. So the other Javascript frameworks version is 100% code, where this movies demo version of WordPress is done with Gutenberg and everything is a block, and you can go and change wherever you want. Which we think it&#8217;s really powerful.</p>



<p>And there&#8217;s yet another thing there, in comparing with the other frameworks, and it&#8217;s that if you look at the performance is a top performer there. It&#8217;s only 13 kilobytes of Javascript. Only a new experimental mode of Solid is able to be as performant as that one. So yeah, I&#8217;m really happy about enabling those user experiences, but with full compatibility with the Block editor and block themes, and with such performance.</p>



<p>[00:16:44] Nathan Wrigley: It&#8217;s true to say, I guess, that if you go to that demo, you will not be seeing anything that you haven&#8217;t seen somewhere else online. You&#8217;ve seen the ability to like things, and you&#8217;ve seen infinite scroll before, and you&#8217;ve seen elsewhere online the ability to paginate without a full page refresh, and you&#8217;ve seen comments being added, again without having to submit a new page and so on and so forth.</p>



<p>But this is creating a standard inside of WordPress. Why did you feel it was important to do this? Why not just leave developers to do their own thing? Again, we&#8217;ve seen WordPress websites implementing this. You know, I&#8217;ve been to countless WordPress websites where I&#8217;ve seen these features.</p>



<p>Clearly somebody&#8217;s dealt with it before and implemented it in their own way. I guess you&#8217;re just trying to make it so that everybody can build on top of the work that you are doing, rather than everybody going off in their own way and implementing a completely different solution based upon, well, however they wish to do it?</p>



<p>[00:17:43] Luis Herranz: Yes. It&#8217;s about absorbing complexity. So, definitely anything you can imagine, it&#8217;s possible with WordPress. The thing is how easy is to do it. And with this kind of standard, our hope is that those user experiences are not only easy, but also working practically out of the box.</p>



<p>[00:18:05] Nathan Wrigley: I&#8217;m guessing that this standard is going to be something that you are aiming at developers. Presumably the developers will then make it fairly straightforward for end users to interact with blocks and what have you, to make this available to them. But how would the standard actually work? What is going on in the background? How are developers going to implement this?</p>



<p>[00:18:25] Mario Santos: If I can add one note to the why this standard, is I think it&#8217;s also important to note apart from what Luis says, is that it absorbs a lot of complexity. In an ecosystem like WordPress where there are a lot of plugins interacting with other plugins and those kind of experiences that we have.</p>



<p>It&#8217;s important that following a standard enables things like block communication. For example, we can see what we were talking about in the demo that you are liking a movie and it&#8217;s updating another block, in another place. So if different blocks, created by different block developers, in different plugins are not using the same approach, it&#8217;s really difficult to be able to communicate those blocks. And having a standard solves that. And yeah, that composability and compatibility to nest the structures of different interactive blocks is possible thanks to a standard.</p>



<p>[00:19:21] Nathan Wrigley: Right. Okay, so you&#8217;re really opening it up so that any block developer can implement this so that, I don&#8217;t know, a different block developer can hook into the exact same standards so that two completely separate blocks, created by completely separate individuals can have interaction via the Interactivity API, right?</p>



<p>[00:19:42] Mario Santos: Yeah, that&#8217;s it.</p>



<p>[00:19:43] Luis Herranz: And they also use this, the same code, the same framework. Because if each block developer starts choosing their own framework, maybe some developers like React, some developers like Vue, some developers like Svelte or whatever comes next. Then WordPress sites could end up loading a lot of unnecessary Javascript.</p>



<p>So yeah, it&#8217;s important. Now that sites are, are a mix of blocks from different developers, these blocks are like small units. Yeah, it&#8217;s important to agree on a single kind of solution.</p>



<p>[00:20:17] Nathan Wrigley: Yeah, good point. Okay, so how is it actually going to work then? You mentioned in the article, and I think one of you mentioned it just a moment ago, that you&#8217;re trying to make it so that people are familiar with PHP, don&#8217;t necessarily have to get into the whole space of learning React or what have you. I&#8217;m not entirely clear on what the position is there, but is the intention to make this as simple as possible for people who are steeped in WordPress&#8217;s PHP history.</p>



<p>[00:20:44] Mario Santos: Yes. We wanted to make it as easy as possible to everyone. So yeah, that&#8217;s included. And yes, we said this is compatible with PHP, and it has been designed to be block first and PHP friendly. So yeah, it&#8217;s should be easy.</p>



<p>And going back to the question, how this standard work. Basically a system based on directives. I&#8217;m not sure, for those who are not familiar with directives, they are a way to extend HTML. They are custom HTML attributes that tell the Interactivity API to attach a specified behavior to a DOM element, or even transform it. So for those familiar with Alpine. it&#8217;s really similar, but it has been designed to work with WordPress.</p>



<p>[00:21:32] Nathan Wrigley: I know it&#8217;s potentially a bit on the technical side, but you talked about the CSS nature of things there. I&#8217;m wondering if you can give an example of how that might be implemented. What would you actually be doing, declaring those directives?</p>



<p>[00:21:47] Mario Santos: Okay, in order to create an interactive block using Interactivity API, you have to add directives to your markup. So you have some HTML, so you add custom attributes that are directives, and they call an action that is defined in Javascript in the view.js file of your block.</p>



<p>[00:22:06] Nathan Wrigley: What is the benefit of doing it in that way? You mentioned that you want it to be available to everybody. Is this the kind of thing that, obviously experienced developers can probably pick this up in a heartbeat, but are you trying to get people, how do we describe this, who are less experienced say. Is this going to be something that you could pretty quickly learn even if your developer chops are not all that impressive?</p>



<p>[00:22:29] Luis Herranz: Yes. The initial goal for this proposal is more enabling user experiences for WordPress that were not possible before, or were very difficult to do before. We also have a focus on developer experience, but that&#8217;s something that we think we can also keep improving over time.</p>



<p>This doesn&#8217;t have to be like the final API of creating blocks. We can work, keep working on simplifying things over time. For example, right now none of these touches like the editor part. So if you are creating a block, the edit is just, is still done in the same way that it is done today using a React component. But maybe in the future we can explore how we can kind of extend these directives also to the editor and if it makes sense to unify and simplify the templating for both use cases. But is not the main goal of this proposal at this moment right now.</p>



<p>[00:23:32] Nathan Wrigley: When you were making decisions about this, and you decided to go with directives instead of things like using React or something. Was there quite a lot of toing and froing? Was there a lot of soul searching, what the best way to do it was? Or was it just fairly straightforward from the very beginning that using directives was the way you were going to do it? How long did the conversation take before you settled on this? is it fair to say that everybody&#8217;s on board with this? This seems to be the way to do it.</p>



<p>[00:23:58] Mario Santos: We believe so. I mean, we have researched a lot of alternatives. Actually, as we mentioned, we come from Frontity, that it was a React framework. React was like the first alternative we had in mind, but we defined as a list of requirements and we started researching different possibilities, and at the end we come up with the solution to be the only one that it was the only one fully compatible with WordPress.</p>



<p>Just to explain this a bit better. As directives are custom attributes that we have in the HTML, we are using the HTML as the templating system. And this comes with many benefits, for example, were not possible with React. As HTML is the templating system, the service rendering is supported by default, for example.</p>



<p>That is something really important in WordPress, or WordPress, APIs like WordPress hooks, that we are used to WordPress hooks in plugins, to extend some functionality, or translations. Those things, with directives using the HTML as the templating system work out of the box. And we can keep using those APIs to even extend the directives.</p>



<p>And I think this was one of the main blockers to not use React. This system, the service rendering is supported, and the WordPress API are supportive as well. That using other approaches can get tricky or even impossible, I would say.</p>



<p>[00:25:32] Luis Herranz: Yes. I think we spent like a year or so researching this. And at first we tried with Javascript, JSX, or even JS templates like Vue or Svelte, and so on. But yeah, I think that that direction, things start getting like super complex. And once we switched to using HTML as the templating language, it was like boom. Like everything works out of the box. Everything is like super simple. Everything is compatible. So yeah, it was like seeing the light a little bit.</p>



<p>[00:26:04] Nathan Wrigley: if I&#8217;m a current block developer, there&#8217;s obviously now going to be this conflict of, do I carry on with what I&#8217;ve been doing so far? I&#8217;ve got some kind of interactive component in my blocks. Do I carry on with what I&#8217;ve been doing up until this point? Or do I flip over and start using the Interactivity API?</p>



<p>You&#8217;ve obviously just mentioned some reasons why that could be the case. But I&#8217;m wondering if there is anything else buried in there. In other words, what&#8217;s the use case to switch? There&#8217;ll be a bit of retooling, you might have to rewrite a whole bunch of stuff that you&#8217;ve already rewritten.</p>



<p>Do you think the benefit&#8217;s going to be in there purely for people who are creating new things? Or do you think there&#8217;s going to be a benefit for people who already have existing things out there in the real world, to go and rewrite what they&#8217;re doing using the Interactivity API?</p>



<p>[00:26:54] Luis Herranz: Of course, as everything in WordPress, this is optional. Even though we want it to become a standard. It&#8217;s optional. But there&#8217;s going to be some kind of sitewide experiences that can only be enabled if all the blocks use this language, or this standard. So yeah, our hope is that there&#8217;s not going to be any reason for new blocks to not use this.</p>



<p>Because it absorbs a lot of complexity and it works out the box with all these things. But there&#8217;s also going to be some benefit on migrating existing blocks to this system if you want to make your blocks compatible with these new user experiences. And also, get rid of all the complexity that you have to deal with in terms of bundling and performance and things like that.</p>



<p>[00:27:42] Mario Santos: And actually it can also improve the user experiences, beause due to this complexity, we have seen many cases of blocks using React in the front end, but having issues with the server side rendering or not having server side rendering at all. So it could be a good approach to migrate to the Interactivity API, because it&#8217;s going to be easier to improve their blocks to support server side rendering, hooks, or other user experiences. There may be cases that they could benefit from that as well.</p>



<p>[00:28:13] Nathan Wrigley: Yeah, I guess the intention would be for a slow but steady migration over to using the Interactivity API, to the point where it just doesn&#8217;t make sense to use anything else. One of you, I can&#8217;t remember which one of you it was, mentioned performance implications there. I&#8217;m just wondering if you could dwell on that a little bit. Have you, in your testing so far, really noticed this? Has it speeded things up, made less use of resources and so on.</p>



<p>[00:28:39] Mario Santos: Yes. We&#8217;ve been testing and we want to test everything better and we will keep testing it in real sites. But it&#8217;s something that we had in mind from the beginning, that it has to be as performant as possible. And that&#8217;s why the runtime code is so small. It&#8217;s around 10 kilobytes. And yes, Luis before compared with other Javascript frameworks is performing pretty well.</p>



<p>I think we did mention this, but it&#8217;s using React under the system. So that&#8217;s why it is so small. And yeah, it is actually performant and we are looking for other ways of optimizing it. For example, we want to only send the directives that are needed by the blocks that are in the page. Or we want to send the scripts so they don&#8217;t block the page rendering.</p>



<p>Or for example, we are also exploring the possibility of the scripts, so they are only load when they are in the view port. So, yeah, overall I would say it&#8217;s performant. It&#8217;s been designed to be performant. The code is relatively small, and we are still looking for ways to optimize it even more.</p>



<p>[00:29:51] Luis Herranz: Yeah, I think that&#8217;s important. It&#8217;s not only performant today, but you have the guarantee that it&#8217;s going to be performant in the future, in the terms of you don&#8217;t have to, as a block developer, you don&#8217;t have to deal with performance in that sense anymore. Because that&#8217;s absorbed now by, well will be, hopefully absorbed by WordPress at some point.</p>



<p>And then if there&#8217;s something new in the web platform that can be leveraged to increase the performance and so on, it will be done in the WordPress side. So your block will just benefit from that, from just adopting this standard.</p>



<p>[00:30:29] Nathan Wrigley: In the article that you wrote, Mario, the first word is the word proposal. Which implies that this is a work in progress, shall we say. And I&#8217;m just wondering how far down the path of usability you would say you&#8217;ve got. In other words, can developers begin using this out of the box? Have you seen real world examples of people using this?</p>



<p>And have you had some interest from developers who perhaps haven&#8217;t implemented it, but certainly want to get on board? Because I&#8217;m guessing the more yes&#8217;s we can answer to that question, the more likely it is that other people will say, okay, yeah, let&#8217;s take a, let&#8217;s take a look at this. So, can you use it, and have people been using it?.</p>



<p>[00:31:08] Mario Santos: I would say, yes, you can use it, but we remind that this is still experimental, although we included the proposal word there. This is still experimental, very likely to change. So the APIs that we are using right now, that are used for example in the movies demo site, we are confident that they work, but maybe the syntax change.</p>



<p>So we haven&#8217;t promoted it yet to be used too much. There are people experimenting with it and giving feedback. For example, there&#8217;s an ongoing experiment in WooCommerce to replicate some of their blocks using directives. But there&#8217;s nothing in production yet because, as I said, this is still experimental.</p>



<p>There are some missing functionalities that may break your site, and it doesn&#8217;t have any documentation yet. So, I would say you can use it at your own risk because it&#8217;s experimental. We would love people to test it. To give feedback. We want to understand better if it&#8217;s easy to use the blockers that people may face.</p>



<p>Just to to clarify. In order to be able to use it, we are working on repository in GitHub. It&#8217;s a plugin that you can install, and from there you can create your own interactive blocks. Or if you prefer, there&#8217;s also the repository for the movies, with some examples that you can take a look and modify or whatever you want to do.</p>



<p>[00:32:34] Nathan Wrigley: Are those repositories linked from Mario&#8217;s article on make.wordpress.org?</p>



<p>[00:32:40] Mario Santos: Yes.</p>



<p>[00:32:41] Nathan Wrigley: Okay, so perfect. So if you want to find those, you can just go to the article, which is going to be in the show notes and you can find them all there. Now you&#8217;re both working at Automattic, and although it was only about 30 minutes ago that you gave me your bio, I wasn&#8217;t quite sure.</p>



<p>I know that you&#8217;re both sponsored full-time in WordPress. Is this project, the Interactivity API, is this a focus for both of you at the moment? In other words, are you being asked to implement this, full-time, part-time? Are you tasked with making this happen?</p>



<p>[00:33:12] Luis Herranz: Yes, we are. But we are not the only ones. It&#8217;s a large group of contributors. But yes. It was part of when we stopped developing Frontity the headless framework, and joined Automattic, it was precisely to focus on this. And we thought it made a lot of sense. Yeah, and thanks to Automattic for sponsoring us to be able to work on this for WordPress.</p>



<p>[00:33:40] Mario Santos: One note on this, as you said, there are more contributors working on this Interactivity API, and yeah, we are part of a bigger group that is working on the whole developer experience of Gutenberg. So this is just a project to improve the front end interactive parts of your blocks, but there are ongoing efforts to improve the whole developer experience.</p>



<p>[00:34:04] Luis Herranz: Yeah, and maybe it&#8217;s a good moment to say that if anyone is interested in this topic, just come to the repository and so on. And contact us and join us.</p>



<p>[00:34:15] Nathan Wrigley: Yeah, I was going to ask about exactly that. How open are you to contributions? Presumably any people that you can get interested in this, the more the merrier.</p>



<p>[00:34:24] Luis Herranz: A hundred percent open. We need people. We need people testing these. We need people using it. We need people giving feedback. Sharing different ideas. The most exposure, the better. How do you say that?</p>



<p>[00:34:37] Nathan Wrigley: Yeah, exactly that. So I guess really if this podcast serves to do anything, it would be exactly that. It would be to encourage people to go over. Read the post on make.wordpress.org, and if you&#8217;re interested and you think that you can help, then certainly it looks like your help would be most welcome. Testing, getting involved.</p>



<p>In terms of what&#8217;s coming, you mentioned that there are things which you desire to have. So I guess that&#8217;s a roadmap question. What is on the roadmap? What do you want to have in there that is not in there? Don&#8217;t worry about timeframes. It might be a year off, two years off, six months, doesn&#8217;t really matter. What are you hoping that it will do that it currently is unable to do?</p>



<p>[00:35:16] Mario Santos: Basically finish the Interactivity API, because it&#8217;s not finished. But, for example, our initial idea is to create the list of core directives that covers, I don&#8217;t know, 90% of the use cases, most of the use cases. Although then developers can create their custom directives.</p>



<p>So for example, that list is not finished yet. We still have to ensure that the APIs work for most of the use cases. We have to finish. And our idea for this is to, at some point, include it as experimental in Gutenberg. Start testing it in real core blocks, for example. Doing some experiments there.</p>



<p>Ensure that those user experiences are easy to create with the Interactivity API. Start receiving more feedback. So yeah, the idea is that. Keep experimenting. Keep developing the API. Receive feedback of users using it. And I think that&#8217;s it.</p>



<p>[00:36:16] Luis Herranz: It&#8217;s going to be important the moment when we add, we added as experimental API in Gutenberg. Because that&#8217;s going to increase the exposure by, I don&#8217;t know, ten fold.</p>



<p>tenfold.</p>



<p>[00:36:25] Nathan Wrigley: One of you mentioned before we click record that you are going to be giving a presentation at WordCamp Europe around the Interactivity API. By good coincidence, this podcast episode is going out just prior to that. So it may be that people listening to this are very soon going to be getting in the car train or a plane to head to Athens. Which one of you is giving that talk and what is it that you&#8217;re going to be covering exactly?</p>



<p>[00:36:51] Luis Herranz: That would be me, Luis. I hope Mario helps.</p>



<p>[00:36:55] Mario Santos: Yeah, I will help.</p>



<p>[00:36:57] Luis Herranz: It&#8217;s going to be a workshop. I don&#8217;t know if it&#8217;s a two hour workshop or two hour and a half workshop. It&#8217;s going to be hands-on. A step by step introduction to the Interactivity API and creating some interactive blocks and user experiences.</p>



<p>[00:37:12] Nathan Wrigley: So very much a hands-on experience. You are going to be teaching people and hopefully getting them to learn in real time. Do you know if any of that gets recorded and put on WordPress TV?</p>



<p>[00:37:22] Luis Herranz: I don&#8217;t know if workshops are recorded or not. Presentations are, yes. I don&#8217;t know.</p>



<p>[00:37:27] Nathan Wrigley: Yeah, okay. So you can very much be seen at WordCamp Europe, in Athens. Hopefully both Luis and Mario are going to be there. Head over to the workshop and say hi, and get involved. If people want to reach out to either of you, be that on social media or email or whatever works best. Maybe we can go to Luis first. Can you give us some details of where people could get in touch with you, specifically around this topic?</p>



<p>[00:37:53] Luis Herranz: Sure. I actually started like, I left Twitter for a while and I&#8217;m back from last week or so. I&#8217;m going to try to answer any question that people may have about the Interactivity API and to share the progress there at my personal account, which is @luisherranz, like my name and surname in Twitter.</p>



<p>[00:38:11] Nathan Wrigley: Thank you very much, and Mario, where can we reach you?</p>



<p>[00:38:14] Mario Santos: I would say Twitter as well. I&#8217;m not actively tweeting, but if someone writes to me, I will answer for sure. Handle is @santosguillamot. It&#8217;s a bit difficult, so maybe it&#8217;s better to include the link?</p>



<p>[00:38:28] Nathan Wrigley: I will link to it in the show notes because yeah, that might be the best way of doing it.</p>



<p>[00:38:33] Luis Herranz: And probably I would say come by the Block Interactivity Experiments repository. So in GitHub, WordPress slash block interactivity experiments. And then there&#8217;s, open a issue, open a discussion. Yeah.</p>



<p>[00:38:47] Mario Santos: And if people don&#8217;t use Twitter, I think they can reach both of us also in WordPress Slack, if they prefer to do so.</p>



<p>[00:38:55] Nathan Wrigley: I will link to both of those things as well. I will include both of your Twitter handles and both of your Slacks, plus all of the links to anything that we mentioned during the course of the podcast. So yeah, an interesting discussion about the Interactivity API. I know it&#8217;s not just the pair of you, but Luis and Mario, much appreciation for taking on this work, which hopefully in the near future will be improving, not only the performance, but the interactivity of our WordPress websites. Thanks very much for joining me today.</p>



<p>[00:39:21] Mario Santos: Thank you a lot for inviting.</p>



<p>[00:39:23] Luis Herranz: Thanks, Nathan.</p>
</div>



<p>On the podcast today we have <a href="https://twitter.com/santosguillamot">Mario Santos</a> and <a href="https://twitter.com/luisherranz">Luis Herranz</a>. They both work for Automattic, but are sponsored to work full-time in WordPress. The main focus of their work is the block developer experience, and they are part of the group of contributors that worked on the Interactivity API proposal.</p>



<p>The Interactivity API is the main focus of the podcast today, and if you&#8217;re working with blocks and dynamically displaying data, this is sure to be of interest to you.</p>



<p>We start out the podcast with the usual introductions and get to know Mario and Luis, and then we learn what the Interactivity API is, and what it can do.</p>



<p>The conversation is framed around a blog post written by Mario entitled The Interactivity API, a Better Developer Experience in Building Interactive Blocks. In this, Mario shows examples of what website interactivity is. In short, it’s the ability for content to be amended on-the-fly without a page refresh.</p>



<p>Of course, this is nothing new on the web, we’ve been seeing this for years in WordPress sites and elsewhere, but now you’re going to be able to create interactivity in a standard way across the different blocks on your site. The project hopes to absorb complexity and make the creation of interactive objects fairly trivial. Mario and Luis talk about examples of where the API might be used and how it can be implemented.</p>



<p>We also discuss the fact that in the past developers have gone their own way to make their sites interactive. It all works, but it means that no two implementations are the same. This causes issues if the project is taken over by another developer, but it’s also a drain on resources. Mario and Luis make the point that having a standard way of creating interactivity will benefit everyone in the long run.</p>



<p>We get into the weeds a little and talk about the approach the team took when building the API. They decided to use directives, and we find out why this was and what benefit it brings over other possible solutions.</p>



<p>The project is still experimental, and they’re looking for people to test and report back on what they find to move the Interactivity API forwards.</p>



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



<p>Frontity</p>



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



<p><a href="https://github.com/WordPress/block-interactivity-experiments">Interactivity API GitHib repo</a></p>



<p><a href="https://github.com/wordpress/wp-movies-demo">Repo for the movies demo</a></p>



<p><a href="https://europe.wordcamp.org/2023/session/building-interactive-blocks-a-step-by-step-workshop/">Luis&#8217; workshop at WordCamp Europe 2023</a></p>



<p><a href="https://twitter.com/luisherranz">Luis&#8217; Twitter</a></p>



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



<p><a href="https://github.com/WordPress/block-interactivity-experiments">Block Interactivity Experiments repo</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, 24 May 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: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:87:"HeroPress: About how WordPress saved my life. – Sobre como WordPress me salvo la vida";s:7:"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=5574";s:7:"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:140:"https://heropress.com/essays/about-how-wordpress-saved-my-life/#utm_source=rss&utm_medium=rss&utm_campaign=about-how-wordpress-saved-my-life";s: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:15217:"<img width="1024" height="512" src="https://heropress.com/wp-content/uploads/2023/05/052323-2-min.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: The opportunity that the Universe gave me is called WordPress. La oportunidad que me dio el Universo se llama WordPress." /><p><a href="https://heropress.com/feed/#espanol">Este ensayo también está disponible en español.</a></p>



<p>Hello, my name is Rita Robles Loaiza, I am a computer systems engineer and I live in Cartago, Costa Rica. Today I want to tell you a little bit about my story and how WordPress saved my life.&nbsp;</p>



<h2 class="wp-block-heading" id="h-about-the-beginnings"><strong>About the beginnings</strong></h2>



<p>I am the youngest of 4 siblings, and the one who for many reasons as we say here in Costa Rica &#8220;went out of the basket&#8221;. Since I was a child I had an affinity for technology, I will never forget the first time I used a computer and how my older sister taught me to use Windows 95 back in 1997 or the first time I was able to program a Lego controller in Robotics class at the age of 12. Even with that affinity at 17 years old I said I wanted to be a chef, and I refused the idea of being an engineer. When I left school and the bubble in which I was I could identify that I had a whole world ahead of me and that I had to follow one of the best&nbsp; pieces of advice my mom could have given me: &#8220;Try hard&#8221;.</p>



<h2 class="wp-block-heading"><strong>About My First Job and Entering the University.</strong></h2>



<p>In 2013 I had the opportunity to start with my first job, that experience opened my mind and was my school, pure and hard about survival and behavior. This job was as an assistant in a Laboratory of chemical and microbiological analysis, the biggest WOW of my life I lived here, in the middle of test tubes, beakers, Erlenmeyer’s I realized all the potential I had, and that creativity and enthusiasm would be my two great weapons, this without knowing that my main virtue is and will be resilience. In the middle of that job and against my wishes I started to study programming, I really did not feel fulfilled even though I liked technology, the Rita of now believes that in the midst of so many changes that rejection was my defense mechanism to everything that was happening around me.</p>



<h2 class="wp-block-heading"><strong>Leaving the Laboratory and the change of university</strong></h2>



<p>After 2 years I suffered an extremely unfair dismissal disguised as economic problems in the company, after many years I understood that they did me a favor and that this action gave me the wings I needed to join the world of technology, while that happened to me and in the middle of my search for the true taste for what I was studying, I changed University, what a decision, so far has been the best I have taken in terms of education, thanks to that change I found what I really liked and was a breeding ground to achieve complete engineering. Finally, after all this, I was incorporated in different organizations with various roles focused on technology.</p>



<h2 class="wp-block-heading"><strong>Rita turned to dust and ashes.</strong></h2>



<p>After a while and finishing my career, I decided to start my own business and entrepreneurship journey with 2 friends. Together we founded a boutique technology and innovation company, in the midst of our business empiricism we managed to meet many people and develop many projects, it was here where I had my first approach with WordPress in a meetup organized by the community of San Jose. At a certain point, my 2 friends abandoned the project and I decided to continue alone (big mistake), the company kept growing, I kept building many more projects, I incorporated more people until everything blew up in my face, it was absolutely unsustainable, and alone, without a job, and without any hope I became dust and ashes believing that I could not get up.</p>



<h2 class="wp-block-heading"><strong>Teaching as a weapon of defense</strong></h2>



<p>In 2018, the career director of the University where I studied contacted me to offer me the opportunity to be a Database teacher. I refused, believing that I did not have enough skills to assume that role, that thought was a product of everything that was happening with entrepreneurship, my director insisted, and I accepted, and that was how on May 19, 2018 I taught my first university class. From that moment until now, 5 years later, I can say that it was one of the smartest decisions I could make, teaching opened the doors to the possibility of rebirth, rebuilding myself and learning from my students. It was the university that in times of difficulties made me grow and get up from everything that was happening, it was here where I understood that resilience is and will be my greatest virtue.</p>



<h2 class="wp-block-heading"><strong>WordPress before my eyes</strong></h2>



<p>In 2019, in a meeting of a women&#8217;s collective, I met the person who pushed me the most in this world, my great friend Ericka, she invited me to go to meetups of the WordPress San Jose community, I knew I had to make an extra effort to just limit myself to go to Meetups, so thanks to her and everything she told me about WordPress I took the initiative to look for tutorials and start learning on my own. It was in this year where I developed my first project with WordPress and opened the doors to one of the career paths that have made me feel happy and fulfilled.</p>



<h2 class="wp-block-heading">WordPress saved my life</h2>



<p>Excited by that project, I continued studying and getting involved in the community, participating in meetups, and organizing WordCamps, to the point that this year 2023 I had the opportunity to be Lead Organizer of WordCamp San Jose 2023. In 2019 in the midst of so much uncertainty came to me a job ad in GreenGeeks web hosting in the role of WordPress Specialist, without any expectation I sent my resume until I got the pleasant surprise that I was hired in February 2020.</p>



<h2 class="wp-block-heading"><strong>WordPress and the COVID-19 pandemic</strong></h2>



<p>It was thanks to this opportunity that I fully potentiated my taste and career towards WordPress, managing to get many projects for Foundations and NGOs in which through WordPress we can reach many interested people. It was also in this instance in which I managed to participate for the first time as a speaker at a WordCamp, this nourished my love for WordPress and the desire to continue sharing with all the people who have the same passion.</p>



<p>WordPress changed my life, put it in order and gave me guidelines to grow personally and professionally, the opportunity that the Universe gave me is called WordPress and all my life I will be grateful for that.</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">Rita&#8217;s Work Environment</h2>



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


	<div class="hotspots-image-container">
		<img width="2560" height="1144" src="https://heropress.com/wp-content/uploads/2023/05/IMG_5886-scaled-1.jpg" alt="Rita" 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="espanol" class="kt-adv-heading_96d019-44 wp-block-kadence-advancedheading"><strong>Sobre como WordPress me salvo la vida</strong></h1>




Escucha el ensayo de Rita con su propia voz






<p>Hola, mi nombre es Rita Robles Loaiza, soy Ingeniera en sistemas de computación y vivo en Cartago, Costa Rica. Hoy quiero contarles un poco sobre mi historia y como WordPress me salvo la vida.&nbsp;</p>



<h2 class="wp-block-heading"><strong>Sobre los inicios</strong></h2>



<p>Soy la menor de 4 hermanos, y la que por muchas razones como decimos aquí en Costa Rica se “salió del canasto”. Desde que era niña tuve afinidad por la tecnología, jamás olvidare la primera vez que utilice una computadora y como mi hermana mayor me enseñó a utilizar Windows 95 allá por 1997 o la primera vez que pude programar un controlador de Lego en la clase de Robótica a los 12 años. Aun con esa afinidad a los 17 años decía que quería ser chef, y me negaba a la idea de ser Ingeniera. Cuando Sali del colegio y de la burbuja en la que me encontraba pude identificar que tenía todo un mundo por delante frente a mis ojos y que debía seguir uno de los mejores consejos que mi mamá me ha podido dar: “Esfuérzate”.&nbsp;</p>



<h2 class="wp-block-heading"><strong>Sobre Mi primer trabajo y el ingreso a la Universidad</strong></h2>



<p>En el 2013 tuve la oportunidad de iniciar con mi primer empleo, definitivamente esa experiencia abrió mi mente y fue mi escuela, pura y dura sobre la sobrevivencia y el comportamiento. Este empleo fue como asistente en un Laboratorio de análisis químicos y microbiológicos, el mayor WOW de mi vida lo viví aquí, en medio de tubos de ensayo, beakers, erlenmeyers me di cuenta de todo el potencial que tenía y que la creatividad y el entusiasmo serian mis dos grandes armas, esto sin saber que mi principal virtud es y será la resiliencia. En medio de ese empleo y contra mis deseos empecé a estudiar programación, en serio no me sentía plena a pesar de que me gustaba la tecnología, la Rita de ahora cree que en medio de tantos cambios ese rechazo era mi mecanismo de defensa ante todo lo que sucedía a mi alrededor.</p>



<h2 class="wp-block-heading"><strong>La Salida del Laboratorio y el cambio de Universidad</strong></h2>



<p>Después de 2 años sufrí un despido sumamente injusto disfrazado de problemas económicos en la empresa, después de muchos años entendí que me hicieron un favor y que esa acción me dio las alas que necesitaba para incorporarme laboralmente en el mundo de la tecnología, mientras me sucedía eso y en medio de mi búsqueda por el verdadero gusto hacia lo que estaba estudiando, me cambie de Universidad, vaya decisión, al momento ha sido la mejor que he tomado en temas de educación, gracias a ese cambio encontré lo que realmente me gustaba y fue caldo de cultivo para lograr completar la ingeniería. Finalmente, después de todo esto, me fui incorporando en distintas organizaciones con diversos roles enfocados en tecnología.</p>



<h2 class="wp-block-heading"><strong>Rita convertida en polvo y cenizas</strong></h2>



<p>Después de un tiempo y terminando mi carrera decidí iniciar el viaje al negocio propio y el emprendimiento con 2 amigos. Juntos fundamos una empresa boutique de tecnología e innovación, en medio de nuestro empirismo en negocios logramos conocer a muchas personas y desarrollar muchos proyectos, fue aquí donde tuve mi primer acercamiento con WordPress en un meetup organizado por la comunidad de San José. En un momento determinado, mis 2 amigos abandonaron el proyecto y yo decidí continuar sola (grave error), la empresa siguió creciendo, seguí construyendo muchos más proyectos, incorpore más personas hasta que todo exploto en mi cara, era absolutamente insostenible, y sola, sin empleo, y sin esperanza alguna me convertí en polvo y cenizas creyendo que no podía levantarme.</p>



<h2 class="wp-block-heading"><strong>La docencia como arma de defensa</strong></h2>



<p>En el 2018, el director de carrera de la Universidad en la cual estudie me contacto para ofrecerme la oportunidad de ser profesora de Bases de Datos. Yo me negué, creyendo que no tenía las habilidades suficientes para asumir ese rol, ese pensamiento era producto de todo lo que estaba sucediendo con el emprendimiento, mi director insistió y yo acepté, y así fue como el 19 de mayo del 2018 impartí mi primera clase universitaria. Desde ese momento hasta ahora, 5 años después, puedo decir que fue una de las decisiones más inteligentes que pude tomar, la docencia me abrió las puertas a la posibilidad de renacer, reconstruirme y aprender de mis estudiantes. Fue la universidad la que en tiempos de dificultades me hizo crecer y levantarme de todo lo que estaba sucediendo, fue aquí donde entendí que la resiliencia es y será mi mayor virtud</p>



<h2 class="wp-block-heading"><strong>WordPress ante mis ojos</strong></h2>



<p>En el 2019, en una reunión de un colectivo de mujeres, conocí a la persona que más me impulso en este mundo, mi gran amiga Ericka, ella me invito a ir a meetups de la comunidad de WordPress San José, yo sabía que debía hacer un esfuerzo adicional a solamente limitarme a ir a Meetups, así que gracias a ella y todo lo que me contaba sobre WordPress tome la iniciativa de buscar tutoriales y empezar a aprender por mi cuenta. Fue en este año donde desarrolle mi primer proyecto con WordPress y abrir las puertas a uno de los caminos laborales que más me han hecho sentir feliz y plena.</p>



<h2 class="wp-block-heading"><strong>WordPress salvo mi vida</strong></h2>



<p>Emocionada por ese proyecto, seguí estudiando e involucrándome en la comunidad, participando en meetups y organizando WordCamps, a tal punto que este año 2023 he tenido la oportunidad de ser Lead Organizer del WordCamp San José 2023. En el 2019 en medio de tanta incertidumbre llego a mi un anuncio de empleo en GreenGeeks web hosting en el rol de WordPress Specialist, sin expectativa alguna envié mi currículo hasta llevarme la grata sorpresa que me contrataron en febrero del 2020.</p>



<h2 class="wp-block-heading"><strong>WordPress y la pandemia del COVID-19</strong></h2>



<p>Fue gracias a esta oportunidad que potencialice completamente mi gusto y carrera hacia WordPress, logrando conseguir muchos proyectos para Fundaciones y ONG en los cuales por medio de WordPress podemos llegar a muchas personas interesadas. También fue en esta instancia en la cual logre participar por primera vez como speaker en un WordCamp, esto alimento mi cariño hacia WordPress y el deseo de poder seguir compartiendo con todas las personas que tenemos esta misma pasión.</p>



<p>WordPress cambio mi vida, la puso en orden y me dio pautas para crecer personal y profesionalmente, la oportunidad que me dio el Universo se llama WordPress y toda mi vida estaré agradecida por eso.</p>
<p>The post <a rel="nofollow" href="https://heropress.com/essays/about-how-wordpress-saved-my-life/">About how WordPress saved my life. &#8211; Sobre como WordPress me salvo la vida</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, 24 May 2023 12:30:01 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Rita Robles Loaiza";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:101:"WPTavern: Automattic Releases wp-now: A Local Development Environment Powered by WordPress Playground";s:7:"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=145373";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:111:"https://wptavern.com/automattic-releases-wp-now-a-local-development-environment-powered-by-wordpress-playground";s: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:2530:"<p>Automattic has published a new project called <a href="https://twitter.com/AutomatticEng/status/1660997741793927168">wp-now</a> that creates a local development environment in seconds. The tool is a NodeJS app that is powered by WordPress Playground, an experimental project that uses WebAssembly (WASM) to <a href="https://wptavern.com/new-prototype-runs-wordpress-in-the-browser-with-no-php-server">run WordPress in the browser</a>. </p>



<p>wp-now allows developers to quickly spin up a new WordPress site with their chosen theme and then open it in the browser automatically logged in as admin without having to enter any credentials. It uses the <a href="https://wordpress.org/plugins/sqlite-database-integration">SQLite Database Integration plugin</a> for its database and developers can quickly swap out versions of PHP and WordPress for testing.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Five minute install? wp-now launches your local environment in five seconds <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f680.png" alt="🚀" class="wp-smiley" /><a href="https://t.co/cKkUDN8uHE">https://t.co/cKkUDN8uHE</a> <a href="https://t.co/QdgZle5mgw">pic.twitter.com/QdgZle5mgw</a></p>&mdash; AutomatticEng (@AutomatticEng) <a href="https://twitter.com/AutomatticEng/status/1660997741793927168?ref_src=twsrc%5Etfw">May 23, 2023</a></blockquote>
</div>



<p>Automattic software engineer Antonio Sejas explained how it works: </p>



<blockquote class="wp-block-quote">
<p>When you use <code>wp-now</code> from a directory, we create a php-wasm instance, download the selected WordPress version and mount the necessary directories in a virtual file system (VFS). Then, we initiate a NodeJS express server that listens and proxies all requests to the php-wasm. As a result, <code>wp-now</code> can easily log you into WordPress automatically, activate plugins and themes, and automatically configure your WordPress site.</p>
</blockquote>



<p>wp-now can be <a href="https://www.npmjs.com/package/@wp-now/wp-now">installed directly from npm</a>. It works across all platforms (Mac, Linux, and Windows). Although it doesn&#8217;t support custom domains or SSL yet, Automattic has it on the roadmap. wp-now contributors are also looking at auto detecting when a file is modified and automatically refreshing the browser, importing a database from another WordPress site, and adding a deploy feature for SSH/SFTP hosting, among other features.</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, 24 May 2023 02:48:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:64:"Post Status: Launching a WordPress Product in Public: Session 14";s:7:"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=149350";s:7:"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://poststatus.com/launching-a-wordpress-product-in-public-session-14/";s: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:47211:"<p><a href="https://poststatus.com/planet/feed/#h-transcript">Transcript</a> ↓</p>



<p><a href="https://twitter.com/coreymaass">Corey Maass</a> and <a href="https://twitter.com/corymiller303">Cory Miller</a> continue the development of their new WordPress plugin, <a href="https://crop.express/">Crop.Express</a>. They delve into the world of image-generation tools for content marketing. In this insightful conversation, they explore creating customizable templates to generate visually appealing images for blog posts, social media, and other channels. Discover how these tools can help marketers enhance their content, highlight important quotes and summaries, and streamline sharing. Dive into the workflow and envision a future where content creators can effortlessly generate eye-catching images that elevate the presentation and value of their posts.</p>



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



<ul>
<li><strong>Continuous Learning:</strong> The WordPress ecosystem constantly evolves, so staying updated with the latest trends, technologies, and best practices is crucial. Engage in continuous learning through online resources, forums, and communities, and attend WordPress events and conferences.</li>



<li><strong>Security Measures:</strong> WordPress security should be a top priority. Implement robust security measures such as using strong passwords, keeping themes and plugins up to date, using reliable security plugins, regularly backing up your website, and staying vigilant against potential vulnerabilities.</li>



<li><strong>Performance Optimization: </strong>Website speed and performance are essential for user experience and search engine rankings. Optimize your WordPress site using lightweight themes and plugins, optimizing images, leveraging caching techniques, and minimizing HTTP requests. Regularly monitor and optimize your site&#8217;s performance to ensure a smooth and fast user experience.</li>
</ul>



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

</div>



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



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



<li><a href="https://www.instagram.com/">Instagram</a></li>



<li><a href="https://thevidabars.com/">Vida Bars</a></li>
</ul>



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



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



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



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



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



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



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



<p>[00:00:00] Dude. Hey.&nbsp;</p>



<p>[00:00:04] <strong>Cory Miller:</strong> All right. Session 14. I had to go on YouTube and look, but golly, that&#8217;s been. Three months, three and a half months. Been good stuff. Had fun on these, but we have some good things to talk about today. I think you were gonna show me some of that stuff and come up with a punch list of what you&#8217;ve been manically working on.</p>



<p>Yeah, I&#8217;m meager man. And I know the other part of the agenda is now baton is. Getting handed over to me to really drive marketing and the work of, that I can actually do with your class. Yep, exactly. Genius and insight and feedback. All right, you want to any thoughts or do you want to kick&nbsp;</p>



<p>[00:00:53] <strong>Corey Maass:</strong> it off and No, lemme share. Which 1:00 AM I sharing? [00:01:00] Share, update, plugin. Let&#8217;s make it smaller. Come on window.</p>



<p>You see that? Okay? Yep. And hold on just a second. Where is.</p>



<p>Real life needs and leads of a dog. Must be in the office with me at all times. Okay, go lay down. All right we have a blog WordPress install. I&#8217;ve been testing with Yost, but for the fun of it, we&#8217;ll leave that. Deactivated general settings. Oh, it&#8217;s interesting that didn&#8217;t reset. But anyway, the title of this blog tagline, so this is the description of this blog.</p>



<p>So I&#8217;m just like, some things I [00:02:00] want to sensible, sensible defaults basically And looking at these variables because they&#8217;ll show up later. If you go, so you have a WordPress install you&#8217;ve just downloaded O M G I M G we need Oh, you have that WorkFlowy document I think I shared with you.</p>



<p>Yeah. Did. So these are, I&#8217;ll take notes here. Plug in marketing. So it&#8217;s like, what do we call the damn thing? I plugged in. It&#8217;s O M G I M G and all capital letters we decided on, which I love. And then what do we call it? I&#8217;m, so a couple of neat things with this. We, I think we, we touched on it a little bit or I was thinking it earlier today, is we don&#8217;t need, because we&#8217;re not going in the plug-in repo, we don&#8217;t need a readme, we don&#8217;t need there&#8217;s a bunch of SEO [00:03:00] stuff that we don&#8217;t need to worry about, that we were messing around with Crop Express.</p>



<p>But I think we still want, we still need a description for here. We still need do we just call it O M G I M G? Do we want another word? Image builder, maker, candlestick maker, something in there. So yeah, what do we call it? What should be like, What we see on the plugins page,</p>



<p>Description name oops. All right. So anyway we activate it. It takes you to a welcome screen. Right now it says, welcome to O M G I M G. Let&#8217;s get you started creating your first image, an open graph image for your site. The first image is the image people see when they share your [00:04:00] sites on socials.</p>



<p>So we can review all this copy later, but Roger that we just need an icon I&#8217;ve been using, actually let&#8217;s do, if I go to post status, it&#8217;s gonna be the real lit litmus test, right?</p>



<p>Is there a high res version? Hey, look at that. Holy leash. Nikes. No, that&#8217;s good. It&#8217;s an svg. Okay which we don&#8217;t support currently. We&#8217;re gonna want to I can. I got it. Because we can just go SVG to p and g. It&#8217;s one of my favorite. These are my favorite sites. There&#8217;s this whole series of sites that look just like this.</p>



<p>It&#8217;s compress P and g. Yeah, compress jpeg, compress All these are my favorite sites. With the elephant. And I contacted this person once and I was like, can I give you money because I use your websites,[00:05:00] every day. And he is no, I make more from ads than you could ever give me.</p>



<p>Okay. It&#8217;s a good problem to have anyway, so let&#8217;s show.</p>



<p>Did it really make it that small?</p>



<p>Oh, no, it really does make it that small.</p>



<p>Okay. So yes, you should send me a version if you have it.</p>



<p>I should have asked you for this earlier,</p>



<p>SVG whole doc. Why not? It really is that small though.&nbsp;</p>



<p>What size do you need? I&#8217;ve got just as big as possible with the transparent background.</p>



<p>I&#8217;ve got three 20,&nbsp;</p>



<p>[00:05:41] <strong>Cory Miller:</strong> about three 20. Let&#8217;s see.</p>



<p>I had these made for Different social platforms. So they&#8217;re already scaled down.&nbsp;</p>



<p>Yep. Do you want an eps?&nbsp;</p>



<p>[00:05:54] <strong>Corey Maass:</strong> I think I&#8217;ve almost got it.</p>



<p>[00:05:55] <strong>Cory Miller:</strong> We&#8217;re illuminating some of the things that we&#8217;ve talked about,&nbsp;</p>



<p>[00:05:59] <strong>Corey Maass:</strong> right? [00:06:00] Yeah. Around tight.</p>



<p>Yep. Yep. This is compelling listening and watching for anybody out there. There we go. I got it. And I&#8217;m being a little pedantic because I want this to be a good demo for you. Oops. Export p and g thousand by a thousand giggles. Heat export. Having fun. Download save. All right, I got it.&nbsp;</p>



<p>[00:06:39] <strong>Cory Miller:</strong> Here we go.</p>



<p>LeBron Giggle in their heat map software is probably going, oh my God.&nbsp;</p>



<p>[00:06:44] <strong>Corey Maass:</strong> Tertiary dancing. All right, I&#8217;m gonna drag in the PS logo, see if this works. Hey, you get a little preview. So there&#8217;s a bug. Go bugs [00:07:00] dropping image shows preview, but placeholder doesn&#8217;t. Disappear.</p>



<p>Doesn&#8217;t matter though. So you create, so this is going to automatically generate the first one based on I think it&#8217;s the, oh, let&#8217;s find out. And there&#8217;s a fatal error because get options hasn&#8217;t been set site. There&#8217;s a little live coding for you.</p>



<p>Oh,</p>



<p>obviously I haven&#8217;t walked through this in a while.</p>



<p>Oh. Called up there. I see.&nbsp;</p>



<p>What did happen?</p>



<p>Oh, I know what I did. Yeah. So change this to until good options. [00:08:00] There we go. Let&#8217;s try that again. Refresh. Grab the PS logo, P and G</p>



<p>and nothing happens. Okay, skip. Anyway it should have created one, but we&#8217;ll create one. So this is the other workflow, basically the idea being that welcome screen, you drop in a logo and then it just spits one out. Yep. So that you&#8217;re not, so that you&#8217;re, on board you, and obviously we&#8217;ll tweak that.</p>



<p>But I wanted to get that we had talked about. The experience of it. Essentially you drop an image and it&#8217;s just done and then you&#8217;d click then option to set it as an OG image. But here we&#8217;ll say created open OG image. Right now we&#8217;ve got logo only and then side by side are mostly working.</p>



<p>Top bottom isn&#8217;t done and simple was the old version I need to clean up, but we&#8217;ll start with logo only. Let&#8217;s see if this works.[00:09:00] We&#8217;re close. Line app, line one 20. Oops. Of course I&#8217;ve been hacking away at this, so lots of errors. I get it. No issue here.</p>



<p>But anyway okay, so real simple, I just want this to go away. If set.</p>



<p>There we go. So real simple options here. You&#8217;ve got a background and you&#8217;ve got an image. And so that&#8217;s all the options that you&#8217;ve got here on the left. So you can set a background color. So if we go to Do you know what color the post status orange is? It&#8217;s the,</p>



<p>like the official&nbsp;</p>



<p>[00:09:51] <strong>Cory Miller:</strong> I don&#8217;t think it&#8217;s,&nbsp;</p>



<p>[00:09:53] <strong>Corey Maass:</strong> oops, I spelled you wrong. Post status.com. There we go. [00:10:00] Inspect.</p>



<p>It&#8217;s that one. Okay, so hypothetically you&#8217;d come in, you&#8217;d say, oh, and I&#8217;ve added global options. So there&#8217;s under settings, you can set a site name if you want it different than the WordPress name, site description, site url. There&#8217;s also going to be Default colors. So it&#8217;s if you create a new one, instead of you having to set the background color every time it&#8217;d import these.</p>



<p>I also think I showed you, I just added or showed a screenshot. I just added support for Google. Fonts a little clunky but is working, which is cool. Ah, okay. So this is what it was supposed to do, is it creates your first project With, here&#8217;s your channel, here&#8217;s your template. So logo only, open graph.</p>



<p>So anyway, back in the editor, so you changed the [00:11:00] background color to be the post status one, and of course it doesn&#8217;t paste FC 78 15.</p>



<p>FC 78 15. So there&#8217;s the post status low color. I added an overlay just by default, so if you wanted to add like, A gradient, something to make it a little more dynamic. I&#8217;m gonna add a little toggle for this so you can turn it off all, all together. You can also rotate it so you can make the gradient come from a different direction if you want.</p>



<p>I guess the hack right now is you would just go in here and make this the same as that orange. Okay.</p>



<p>Looks like it&#8217;s still adding a gradient, but anyway. But the idea is right now I&#8217;ve added, I&#8217;m basically flushing out. I&#8217;m trying to flush out like one of each option, like a color picker, a or slider, [00:12:00] a bunch of different things. And so we can keep adding these selectors basically. So you can, you&#8217;ll have options all day long.</p>



<p>You come over here and. So that&#8217;s how you could figure the background, right? And then for the image this should by default, say site logo, which is the thing we uploaded. But I&#8217;ve added support for the media library. So if you wanted to do let&#8217;s grab one of my testing document WordPress.</p>



<p>Nope. Testing. So I&#8217;ve been using this gear, so you could also select an image from the media library or the default site logo. You set the size, you could rotate it. Rotate it if you want to.</p>



<p>So dead simple. Save your changes. And it&#8217;s there every time, right? There&#8217;s an option to view it, [00:13:00] full screen. And then there&#8217;s the, you saved say download. I don&#8217;t know if you, I don&#8217;t think you can see that part, but it downloads right now. It&#8217;s a funny name, but we&#8217;ll give it a better name when you download it so you&#8217;ll know what it looks like in the download.</p>



<p>And then there&#8217;s also the option to save it as your open graph image. And so we don&#8217;t really have a way to demo that, but what it does is it will it&#8217;ll write headers to your, to, to the website so that anytime your website is shared this&#8217;ll be your OG image. Okay. And then also so I think, so it&#8217;s saving it as OG image.</p>



<p>Yeah. Puts it into your media library and then. And then that&#8217;s what gets shared out. So another bug here or an extra feature we want is to save. In addition, to save as to download, we wanna be able option to save to media Library. [00:14:00] So it&#8217;ll just show up in the media library. And saving is the OG image.</p>



<p>So when you go back to projects, there&#8217;s a little flag that says this is your OG image, cuz you can only have one obviously. And so it&#8217;s if you set a different one. So here&#8217;s that same menu you can download directly from here. Or save it as the OG image. And then, and this&#8217;ll replace whatever one is the OG image.</p>



<p>Let&#8217;s create another. Go ahead. Yeah, let&#8217;s create&nbsp;</p>



<p>[00:14:26] <strong>Cory Miller:</strong> another one. But how did you get the name Project five? Number&nbsp;</p>



<p>[00:14:29] <strong>Corey Maass:</strong> five. So it&#8217;s, these are just like posts. So if you create A post has an id. So project number five. So yeah, one of the Go&nbsp;</p>



<p>[00:14:39] <strong>Cory Miller:</strong> ahead default, or we just naming that by default or do they have the&nbsp;</p>



<p>[00:14:44] <strong>Corey Maass:</strong> What would we name it?</p>



<p>[00:14:47] <strong>Cory Miller:</strong> No, I was it. Do we, do they have the option to name it&nbsp;</p>



<p>[00:14:52] <strong>Corey Maass:</strong> something different? Oh, they don&#8217;t yet. So let&#8217;s add that to the list. Custom project [00:15:00] name</p>



<p>because, yeah, I thought about that too, like that once it gets up to 1,986,426, it&#8217;s like, what&#8217;s, which one are we talking about?&nbsp;</p>



<p>[00:15:12] <strong>Cory Miller:</strong> I&#8217;m just thinking too, for sorting, like we probably want to say it&#8217;s O N G I M G and then they name it like default homepage or something. And then when we get into the single post pages and stuff, maybe it&#8217;s post ID or post name and number or something like that.</p>



<p>Just so they, when they see this page, it&#8217;s gonna get pretty filled.&nbsp;</p>



<p>[00:15:37] <strong>Corey Maass:</strong> Yep. Yeah, the here it says SITEWIDE images. I don&#8217;t think this is working right now because I&#8217;ve made a bunch of changes to the site version. There is a menu option here for O M G I M G per post. Yeah, it&#8217;s totally broken right now.</p>



<p>But it&#8217;ll, when it&#8217;ll look similar, [00:16:00] but it, but up here it says, Name of post, today&#8217;s specials or whatever, and then it, and then has your images, so you do have context. But yeah under the project number name we&#8217;ll want to come up with some naming convention. The other thing that I, so let&#8217;s do that custom project name, but right off the bat, maybe a date or we could do the name of the template.</p>



<p>Default project name, using date or template or both because it would be like April 26th. OG image would at least give you some context.&nbsp;</p>



<p>[00:16:40] <strong>Cory Miller:</strong> Ni picky. But when you say CRI project, that button right there. Yep. C. Could that be create O n G? Im G.&nbsp;</p>



<p>[00:16:48] <strong>Corey Maass:</strong> Absolutely.</p>



<p>Not nitpicky. That&#8217;s the kind of stuff I please jump in. Okay. Especially cuz most, most of those changes are small. Yeah. Yeah. I&nbsp;</p>



<p>[00:16:58] <strong>Cory Miller:</strong> think coming back to the branding, like [00:17:00] that&#8217;s what we&#8217;re doing is M G I M G and that&#8217;s what they&#8217;re getting and I think&nbsp;</p>



<p>[00:17:04] <strong>Corey Maass:</strong> that&#8217;s good. Yep. Okay. Let&#8217;s do another open graph.</p>



<p>Actually let&#8217;s do an Instagram and again. So instead of logo only now we get into side by side, so it&#8217;s a bit more complicated.</p>



<p>So this is a logo on the left and text options on the right. So again, we do a background color. See there&#8217;s a little bug of. That border.&nbsp;</p>



<p>[00:17:35] <strong>Cory Miller:</strong> You&#8217;re a very daring dev. I always like doing this stuff though, but a lot of devs have worked with her, like they don&#8217;t want to see, they don&#8217;t want you to see some of this. I&#8217;m like,&nbsp;</p>



<p>[00:17:45] <strong>Corey Maass:</strong> Hey. Oh, I want you to see it as broken as possible. Cuz then it&#8217;s like one, one, it&#8217;s part of the journey and what we&#8217;re trying to illustrate with all of our, everything we, we&#8217;ve been doing in public Mo honestly, most of our conversations have been [00:18:00] public.</p>



<p>And that&#8217;s I also wanna show, this is as part of our journey. You have barely usable products, but it&#8217;s, then you clean it up. So same thing, overlay color, make it nice and ugly for you. So let&#8217;s just do white and green. With that angle. The image, again, you can choose, that&#8217;s supposed to be site</p>



<p>site, logo side.</p>



<p>Just clicking through to see that it all works, so it changes to this other thing. Or you jump back and it&#8217;s the site logo, make it bigger title. So this is the stuff that I&#8217;ve been really working on right now. I&#8217;m, I don&#8217;t have Google fonts enabled. I. But you still get the idea. So we&#8217;ve got some default font families basically.</p>



<p>So if you wanted handwritten I [00:19:00] don&#8217;t know if bold works. No, I was just doing that this morning. But you will have the option to ignore this input and you will have, but you will have the option to say bolder italics, cuz it&#8217;s I want you to be able to customize the text to your heart&#8217;s content.</p>



<p>Text color. So you might hear, you might match the orange type of thing, text size,</p>



<p>but you&#8217;d say, I want this tighter. There&#8217;s line height. If you wanna get, what&#8217;s that tweak to your heart&#8217;s content. Exactly. And again, these are not quite the, like you gave me some comps of the ultimate post status. Social image. And so based on that, I want to give us, give you all the options.</p>



<p>If you were a customer coming in, you&#8217;d say, okay, I&#8217;d upload my logo here. I might choose a a font that not looks like that. [00:20:00] Like that. I&#8217;d want it bold, I&#8217;d want it all caps. So we want all those options. And then, Be able to make it look good in the context of this template. There&#8217;s the title, then you go to the subtitle.</p>



<p>And so you&#8217;d have site url, site description. Remember I said, this is where we put in the description of the blog. But it&#8217;s like most likely you&#8217;d want the title of the blog and the url, so you&#8217;d do that, but it&#8217;s, and there&#8217;s a setting for let me save this. So there&#8217;s a setting again. So by default, if you&#8217;re like, our webs, our website is http and www, but we really just want it to be post status.com or if you had a short u r l, po.st or something like that, you could put that in here.</p>



<p>So let&#8217;s do post status.com. [00:21:00] Save. Go back to here. Oh. So you know, this is what your project screen looks like. So you&#8217;ll see all of your projects. And yeah, we&#8217;re gonna want ability to sort projects by name most recently updated, et cetera. So we&#8217;ll add that to that screen. Jumping back in here, Seesa.</p>



<p>Now, the, by default it brings in post status.com, but there&#8217;s also an option of custom text. So if you wanted to put in dot, something or post status.com, link to, something specific, a blog, something like that, right? Text color X size, but you get the idea.</p>



<p>[00:22:00] So yeah, that&#8217;s where we&#8217;re at.</p>



<p>No problem, dude.&nbsp;</p>



<p>[00:22:05] <strong>Cory Miller:</strong> So from the premise of the Sitewide OG image probably when I was doing that for, it was so good. Can I show you some stuff&nbsp;</p>



<p>[00:22:14] <strong>Corey Maass:</strong> real quick? Yeah, absolutely.</p>



<p>[00:22:16] <strong>Cory Miller:</strong> Okay. So I was playing, this is off topic, but I was playing with some of this, like more into the blog post stuff. So you can see some of these things. I was just like trying to be the client. This is not it. Okay. Where did that play with it?</p>



<p>It&#8217;s in our.</p>



<p>Oh, here we go.</p>



<p>But this side by side image, I think side by side thing is gonna be really great for the in, in just what we need for. Initial stuff. Yep. So I was running around with like logo on top here.&nbsp;</p>



<p>[00:22:52] <strong>Corey Maass:</strong> Yeah, your number 15 is what I was emulating and then. Once, once I&#8217;ve got all the kinks worked [00:23:00] out, it&#8217;s easy enough to duplicate it to, I called it top and bottom or something.</p>



<p>So logo above, and so that becomes your like 14 or 13 where it&#8217;s the same elements on the page. Just, up and down instead of left and right. Yeah, I really, as I was&nbsp;</p>



<p>[00:23:18] <strong>Cory Miller:</strong> doing this just for post, I was like, this is what, this is really what you need. You just need. Logo, brain thing, tagline. And so that was really good for me to go through that experience.</p>



<p>But yeah, I guess I&#8217;ve got four cards here. Put it on the right, put it on the left, but it above, but it below.&nbsp;</p>



<p>[00:23:40] <strong>Corey Maass:</strong> Yep. And I, and so actually I&#8217;m now thinking, so maybe I. Like I do the, just an image, cuz that was one of the ones we saw on that gallery. And then, and I think it&#8217;s a really good place to start.</p>



<p>Basically it&#8217;s the simplest. And then we will, [00:24:00] and then I will adjust the side by side to be, we&#8217;ll call it the, like the default business card. And I will put in little toggles that are like, Because again, it&#8217;s, I&#8217;m trying to flush out potential options, right? And so if there was an option that was like logo left top, right bottom, cuz it&#8217;s all essentially the same.</p>



<p>All of those cards from our perspective are the same, just reordering of things. But logo, title, U R L. And I just lock that shit down and then we&#8217;re ready to publish, essentially, like I, as you saw, like I wanna, I want to clean up the welcome screen a little bit more cuz I do think that onboarding&#8217;s gonna make a big difference rather than it just being a blank screen when you sign in and it&#8217;s done.</p>



<p>It was pretty simple to implement. Yeah, I really think, and then,&nbsp;</p>



<p>[00:24:58] <strong>Cory Miller:</strong> Go ahead. Just go to the experience [00:25:00] is like those five are all we need. Yep. Specifically for the homepage you saw here, just this is for next level step stuff. Yep. But I was like, when you told me I could have a screenshot, I was like, oh yeah.</p>



<p>[00:25:16] <strong>Corey Maass:</strong> Oh yeah. When once I add that, like that&#8217;s gonna be a lift. Because it&#8217;s, a screenshot within a screenshot kind of thing. But so I&#8217;ll circle back to that. But is, so is this your official, the official font of post status? Yes. And what font is it?</p>



<p>Go round A round. I believe&nbsp;</p>



<p>[00:25:40] <strong>Cory Miller:</strong> it&#8217;s a Google font.</p>



<p>Yes, it is.&nbsp;</p>



<p>[00:25:43] <strong>Corey Maass:</strong> Okay. And do you make it bold or is it just, is that how it comes? I&nbsp;</p>



<p>[00:25:49] <strong>Cory Miller:</strong> I did for this stuff. I don&#8217;t know the original, how this is all done, but I was trying to match it and Sure. That won&#8217;t work for me. It is bold.&nbsp;</p>



<p>[00:25:58] <strong>Corey Maass:</strong> Okay. [00:26:00] So by having Google fonts right now, so there are 1500, I think 1,508 Google fonts, and we, just so you know, right?</p>



<p>So that we are not, because a plug-in, can&#8217;t call, dial out without permission and you can&#8217;t get Google font information without an API key. We can&#8217;t expect our users to go through all those steps, so you have to enable Google fonts within the plugin. But I set it up so that now I&#8217;m just bragging, but I&#8217;m proud of myself.</p>



<p>I got us a Google a p i key Once a day we hit the Google Fonts API and get all the information. We store it on omg.co. I created a little API there, and so the plugin, anybody&#8217;s [00:27:00] plugin will hit omg img.co. That meaning our website to get all the font data, and then it&#8217;ll be, and then it&#8217;ll be cashed on in their own website too, but, so it was, The sort of clever way if I do say so myself, not, it&#8217;s not super tricky, but so we, so pretty quick, I was able to pretty quickly add Google font support the without the user having to do much, which is cool.</p>



<p>However, right now all it does is create a dropdown that has 1,508 names of fonts For you, for now that you can, you would just go, sorry, select Vare around from that dropdown. But we&#8217;re gonna have to add some way to preview all of those fonts, anyway, I wanna make sure that Varela round bold works for you.</p>



<p>You don&#8217;t do italics, you don&#8217;t rotate anything, but I had fun implementing that [00:28:00] stuff. And for you, it&#8217;s just a white background. Yeah. Oh, so I want to add, toggle the background overlay. So you can just disable it and just say, set a white background. And then that default. Color picker. I couldn&#8217;t, I had to type in the color.</p>



<p>I couldn&#8217;t paste it in, which was a pain in the ass doesn&#8217;t support pasty. So I think we want a better color picker so that somebody could go copy an eight. Most people are gonna have a hex code color and so they&#8217;re gonna want to paste it in. Yep. Okay. So gimme 20 minutes. Just sit there quietly for 20 minutes and I will have this ready for you.</p>



<p>Just kidding. Okay. I can&nbsp;</p>



<p>[00:28:50] <strong>Cory Miller:</strong> be quiet. So then I went a little further into thinking through how we want those, and I came back to this. [00:29:00] Yep. Featured image stuff and going and let you know, just try to present some what we probably want on things. I did show, I did see. Yep. There, I did it. Let&#8217;s see if I can, your&nbsp;</p>



<p>[00:29:15] <strong>Corey Maass:</strong> hair&#8217;s getting long.</p>



<p>Huh? Your hair is getting long. In that picture,</p>



<p>[00:29:21] <strong>Cory Miller:</strong> I showed you that thing. I just saw some from Twitter, but it was just a quote with a person&#8217;s picture on it. I was like, that&#8217;s cool. Cuz a lot of the podcast stuff we&#8217;re doing</p>



<p>Like something like this where you have the person you&#8217;re interviewing with their little quote. I&#8217;ll keep working on those. Thinking about those, cuz those outputs were really good. Like we do so much audio, video stuff. And really been working with content journey to break those down more and more where you get clips and stuff like that, that then go out on social that are more valuable content on there [00:30:00] than just listen to 45&nbsp;</p>



<p>[00:30:01] <strong>Corey Maass:</strong> minutes.</p>



<p>But what you just said more valuable, we were talking earlier about like taglines and concepts and stuff. More valuable images.</p>



<p>I really like that.</p>



<p>Okay. Because we were talking like. Making you look more professional, which I bucked at cuz it&#8217;s it implies you don&#8217;t look professional now or as opposed to like we are. And also going back a handful of conversations that we had where it&#8217;s like crop Express was solving a problem.</p>



<p>We were a wrench, you had a bolt. We could help tighten the bolt faster kind of thing. Whereas this, technically you can live without this, but we are making ev making your website better.&nbsp;</p>



<p>[00:30:52] <strong>Cory Miller:</strong> It&#8217;s the polish. Yeah. It&#8217;s like you said, the last mile of Polish, yep. Done work doing [00:31:00] the 45 minute thing, doing the thing.</p>



<p>And then this is that last mile that you said, I&#8217;d like that toughest mile of just polish. Yep. We&#8217;re making that really to display that. When I was thinking through the blog post stuff, I was like, that&#8217;s what I&#8217;d want is, when we shove out a podcast episode that&#8217;s not guy, oh, they did another thing.</p>



<p>But if we have that quote from somebody in there that really resonates, then it&#8217;s I should go and look more. And what we&#8217;re trying to do on the content side is break those up better and better with transcripts, show notes and stuff like that.&nbsp;</p>



<p>[00:31:36] <strong>Corey Maass:</strong> Yeah, initially, so I&#8217;ve added that. Basically it&#8217;s a content field, so it&#8217;s like you pull in the title of the website, you&#8217;d pull in whatever, right?</p>



<p>But that, that the last option was custom text. And the label on the left would say quote, and then you&#8217;d say custom text. And you&#8217;d put in a quote and you&#8217;d have [00:32:00] this saved as a default. So you&#8217;ve got post sta, a white background and the post status logo and U R L in the bottom right print that, that&#8217;s quote number one.</p>



<p>You&#8217;re now looking at that screen that has all of your projects and you&#8217;d say duplicate post or duplicate project. You change the name to quote number two. You&#8217;d go in paste in the second quote, and now you&#8217;ve got two of those images, same picture of the woman, but two different quotes. So you&#8217;d download one to post on socials on Tuesday and you&#8217;d download the second one to post on socials on Thursday.</p>



<p>Gosh.&nbsp;</p>



<p>[00:32:39] <strong>Cory Miller:</strong> So it&#8217;s been a bit a second on this blog post thing. So all those, I gather, you&#8217;re probably setting it up where it&#8217;s set in the front. When you do a post, there could be these options that you could fill in to create all those images. And right there I can do that. So I&#8217;m looking at [00:33:00] the post, oh, that quote there is the template plug and play.</p>



<p>Like if you saw on this one screen, I was</p>



<p>Why you get to Drift.</p>



<p>I think that&#8217;s where we&#8217;re gonna get in. The valuable part is something that looks nice enough and allows me to share those things out.&nbsp;</p>



<p>[00:33:25] <strong>Corey Maass:</strong> Yeah, and I think, like we&#8217;ve talked about, I. A number of those different templates of, or scenarios, an image that you generate that&#8217;s got a picture of a per, for your interview, you&#8217;ve got their picture on the left, and then you&#8217;ve got a quote and you can make five of those five different quotes, but it&#8217;s essentially the same image.</p>



<p>And initially, Today, tomorrow, this week, like I&#8217;ll set up that template next week. You&#8217;re using it and you&#8217;re plugging it. You know you&#8217;re gonna have to cr [00:34:00] recreate that template every time. But a week from now, I&#8217;m gonna give you the option to duplicate a template and or save a template. For reuse, essentially.</p>



<p>So then step two is gonna be okay. It&#8217;s I set it up once for each post and then and then I&#8217;ve gotta manually plug in those quotes and then step three, like basically to verify that, that we are using it this way and that these are loops that we want to close or processes that we wanna make faster.</p>



<p>It&#8217;s like I&#8217;m picturing a. A screen where essentially you can quick generate, if you&#8217;ve got a bunch of these templates that like, opens up in the sidebar, your, you go and you look at your blog post and you highlight something, and then you select from a dropdown like, plug this, whatever text I&#8217;ve highlighted into this template.</p>



<p>So it&#8217;s highlight a quote. Generate a quote, image [00:35:00] highlight, quote number two, generate quote, image, highlight bullet points you instead of the quote template, use a, use the bullet point template and you just go bang. Okay, all done. Go back to I M G O M G I M G project screen and there&#8217;s all of those different templates populated, already with your logo, but quote one, quote two, quote three, bullet 0.1, bullet 0.2, bullet 0.3.</p>



<p>So I think it&#8217;d be&nbsp;</p>



<p>[00:35:27] <strong>Cory Miller:</strong> okay, let me just make sure we&#8217;re on the same page. And I&#8217;m sorry if I missed this, but, so I was thinking post templates I&#8217;d want for most post ads content. I put down quote and summary slide. It&#8217;s probably the two big ones, just summary slide about what this content is about and then actionable cool quotes on that.</p>



<p>So I started plugging up MGM G. I could create a template for the post things that would show, then [00:36:00] set there for its to global, and then I&#8217;m in post writing, post and go ready for the OG images, click. Oh, I want to do, I gotta have a summary slide that&#8217;s already in my template over you on the post. And then same thing with quote, I&#8217;d have that option too.</p>



<p>Those templates would show up</p>



<p>because right there, from a workflow standpoint, I&#8217;m thought about, I&#8217;ve done the work of thinking about some of the key things that would drive value on the post content summary slide, which is our featured image thought. And then the quote Thing and I&#8217;ll, maybe the bullet point would be the third for me is like we, we talked about these three things, which could be a variation of the summary slide.</p>



<p>Sure. And if I did that, what that would do for me on my social channel is just talking this out as opposed to as, okay, I&#8217;ve already illuminated in a graphically appealing way what this long form post is about. Then I have those images for [00:37:00] those channels. LinkedIn, Twitter primarily for us at the appropriate sizes and stuff.</p>



<p>I think we&#8217;re cooking. Yeah.&nbsp;</p>



<p>[00:37:10] <strong>Corey Maass:</strong> Yep. Yeah, I like we&#8217;ve talked about the baseline is an OG image, ideally auto generated The moment you hit publish, you&#8217;ve based on a template being populated with the title of the post and then down the road with a screenshot of the post, and or the featured image.</p>



<p>But once you&#8217;ve done kind of what is considered the word press basics, you&#8217;ve added categories, you&#8217;ve added a featured image, you&#8217;ve written your blog post, you&#8217;ve hit publish. Already when you share it, it looks damn good. There&#8217;s maybe a little bit of setup, but if you haven&#8217;t set up an OG image template or an OG image template for a, for that post, [00:38:00] then at least when somebody shares it, they get the sitewide business card, like you&#8217;re describing it.</p>



<p>But with the next step. Every post that gets created automatically has a business card, but has the title of that post built in. And then step three, you could essentially recreate reuse that same one, let&#8217;s say make it a square for Instagram. And so again, you&#8217;re going, up and out with all these things and it&#8217;s just a matter of how you use it.</p>



<p>So like at post status, your. You&#8217;re going, okay. Baseline is an OG image, but we also then want and that&#8217;s gonna cover your LinkedIn and Facebook. But you&#8217;re like, but we need a square for Instagram. Copy. Change it to, I didn&#8217;t show you that part. So it&#8217;s like that we select that channel.</p>



<p>You saw that the second image I created was for Instagram. You can actually change that live. So you could take a rectangle image, you could replicate it, so [00:39:00] now you&#8217;ve got another one. But you could say, now make this square and it&#8217;ll just change. And things might move around on the screen.</p>



<p>So you might want to go tweak, tweak some of those sliders. But if you&#8217;ve already done the work once, copy change screen size.&nbsp;</p>



<p>[00:39:14] <strong>Cory Miller:</strong> Okay, let me talk this through. From a marketing customer Perspective. So what I&#8217;ve gathered, cuz I want us to capture this for the market, my marketing work, but I&#8217;m, I need to say that out loud to you.</p>



<p>So what this has done for me as the content marketer at Post status is it&#8217;s in my workflow. It&#8217;s creating I&#8217;ve said my templates, I&#8217;ve thought these things, o n g has helped me. Do those, think through those these are the basic things you can do to add value to your post.</p>



<p>So it&#8217;s in my workflow. It&#8217;s great cuz I&#8217;m going to my post. I&#8217;m adding new podcast, new blog posts, whatever. I&#8217;ve already done this initial workflow work to set my templates that are there for me when I need it. It looks nice, [00:40:00] like it doesn&#8217;t look like shit. It looks nice. And then the third is it, this is just direct speed.</p>



<p>It illuminates the value of the post better. I&#8217;m pulling out the things to showcase what the post actually is, so I&#8217;m enticing people to do that. The fourth I didn&#8217;t add down here though, is making it super easy to go off and share. So for marketing wise, right there, we talk to content marketers first.</p>



<p>They&#8217;re already doing this work. Yep. It&#8217;s in your workflow. It&#8217;s gonna look nice. It&#8217;s gonna share, showcase the value of the landing page better, and then it&#8217;s easy to share.&nbsp;</p>



<p>[00:40:43] <strong>Corey Maass:</strong> So that last mile talking about the last mile is the hardest mile. Is also an aspect that I think. Mar like marketers and marketing agencies, it&#8217;s going to make sense to [00:41:00] them that we don&#8217;t close the loop on actually publishing to your average person.</p>



<p>I th I anticipate this being a discussion. This we&#8217;re gonna have to have over and over again. Corey, with his little music blog. In a perfect world, We would generate images for each channel and then we&#8217;d click a button that would say, push these to these channels. Yep. But it&#8217;s, but that is so a big, messy step.</p>



<p>Yeah. And there are tools that already do it. And again, from a marketer or an agency is already going to be using a radar, a buffer, a hoot suite to queue up and publish this content.&nbsp;</p>



<p>[00:41:59] <strong>Cory Miller:</strong> Yeah.[00:42:00] So I was thinking though, like your Instagram, I go, huh, when am I gonna use that? But the Vida bars company, Lindsay has an investment in helps.</p>



<p>She&#8217;s got shampoo and conditioner bars. She primarily uses Instagram, right? So she&#8217;s creating a post, wants something that then she can download and just upload back to, that publishing option. They&#8217;re great services that do all that. To me, it&#8217;s yeah, we&#8217;ve handed it on the thing, now go use your tools, your workflows.</p>



<p>Yeah. You&#8217;re already in that workflow. But man I think that&#8217;s awesome. Okay. I&#8217;ve only, sorry, I&#8217;ve only got four more minutes, but here&#8217;s my question to you. What do you think needs to happen for it to be ready for&nbsp;</p>



<p>[00:42:39] <strong>Corey Maass:</strong> production on Postex? Like I said, I need to clean up some of these bugs and I am now going to, so I&#8217;ve already created options that, that post status based on the template you gave me, I think we&#8217;re [00:43:00] pretty much covered.</p>



<p>Like we&#8217;ve got Google font support. You can upload a logo, you can pull in a title, and I am going to clean it all up so that it works and you stop seeing errors when you first install it. But I&#8217;ll make sure that essentially the first template covers. The post status template and I need to replicate it.</p>



<p>Like I said I&#8217;ve been hacking away at the Sitewide version, and so I&#8217;ve done this a couple of times. I just need to copy all my updates over to the post version. And then you&#8217;ll have all the same features on for sitewide images or for post specific images. And then we&#8217;re, and then you can at least start messing around with it.</p>



<p>Okay.&nbsp;</p>



<p>[00:43:43] <strong>Cory Miller:</strong> Do I need to do a little bit more work for you, like sh on the post templates, take a podcast or whatever content we have and think through. I&#8217;d want to quote from here. I&#8217;d want the summary slide for here. Do you want me to do a little bit of that work? [00:44:00] Like with live action stuff and Google Slides?</p>



<p>[00:44:02] <strong>Corey Maass:</strong> Yes. Like the more work you do thinking through these templates, I don&#8217;t think we&#8217;re gonna I&#8217;m not gonna be able to deliver most of it tomorrow, but we can create one, yeah. Or we can create the one that&#8217;s similar to the Sitewide business card that just covers your basics. It&#8217;s got a logo, it&#8217;s got the title.</p>



<p>So it, and then you like, cuz I wanna get this to you so that you&#8217;re like, you are pub, you publish and you&#8217;re like, Hey Corey, I&#8217;m trying to publish this for tomorrow. I need X, Y, Z. I&#8217;m like, okay, now we have a real world scenario, let me go add that. Here&#8217;s&nbsp;</p>



<p>[00:44:41] <strong>Cory Miller:</strong> what I&#8217;m gonna do. Then I&#8217;m just gonna think about, I get one featured image template thing.</p>



<p>Yeah. And to just showcase the value of the post. And and work on a couple of thoughts with, I&#8217;ll take one post and start doing it. Maybe take another [00:45:00] one and start doing it, and then deliver that and go, Hey, I think these are the basics for that one thing. And that gets me huge way into showcasing the value post and everything else.</p>



<p>Like you said, it&#8217;s crazy. Yep. With that. So I&#8217;ll&nbsp;</p>



<p>[00:45:14] <strong>Corey Maass:</strong> do that. And then like I said, I mean we&#8217;ve I&#8217;ve set up the technical side of serving, of selling this thing using e D on the website. Yeah. So we need to start thinking about a homepage, cuz we&#8217;re not gonna be selling tomorrow.</p>



<p>But you and I both know that the first version is 10 versions, in a day, or, in, within a week before we actually let something stay online. Yeah. We wanted you sent over a design you like and then we&#8217;ll but we need some words to start putting on that page. So start thinking about that.</p>



<p>Okay. So&nbsp;</p>



<p>[00:45:58] <strong>Cory Miller:</strong> really for me it&#8217;s [00:46:00] homepage and the post template.</p>



<p>Okay. Can do. Awesome. Love it dude.&nbsp;</p>



<p>[00:46:08] <strong>Corey Maass:</strong> Thank you. We&#8217;re so close. We&#8217;re so close.&nbsp;</p>



<p>[00:46:12] <strong>Cory Miller:</strong> Yeah. Too, and I love the way we&#8217;re doing it. It&#8217;s like we have a live action thing that we&#8217;re making it better and I&#8217;m putting on the hat of actual users cuz I am Right. Helping formally, I think that&#8217;s such a good way to do product that sometimes has been a mismatch for me, but I&#8217;ve got the live action, thank you.&nbsp;</p>



<p>[00:46:31] <strong>Corey Maass:</strong> Great. 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:"Tue, 23 May 2023 20:14: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: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: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:67:"Do The Woo Community: A Product Deep Dive with Wilson Favre-Delerue";s:7:"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=75190";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"https://dothewoo.io/sendcloud-shipping-automation/";s: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:399:"<p>In this episode we take a deeper look at Sendcloud with Wilson and what shipping automation means to a developer or freelancer.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/sendcloud-shipping-automation/">A Product Deep Dive with Wilson Favre-Delerue</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, 23 May 2023 13:38:52 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:86:"WPTavern: Gutenberg 15.8 Adds Pages Menu to Site Editor, Revisions UI to Global Styles";s:7:"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=145332";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:96:"https://wptavern.com/gutenberg-15-8-adds-pages-menu-to-site-editor-revisions-ui-to-global-styles";s: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:2667:"<p><a href="https://make.wordpress.org/core/2023/05/20/whats-new-in-gutenberg-15-8-may-17/">Gutenberg 15.8</a> was released with some exciting features that were included in the tentative <a href="https://wptavern.com/wordpress-6-3-development-kicks-off-to-conclude-gutenberg-phase-2">WordPress 6.3 roadmap</a>. Users are getting closer to a more unified content editing experience with the addition of the Pages menu to the Site Editor. Clicking on Pages will load the ten most recently updated pages with a link to &#8220;Manage All Pages&#8221; at the bottom of the list. Users can quickly jump into editing content by selecting a page.</p>



<img />



<p>The interface also includes a little reminder about the nature of pages in WordPress: &#8220;<em>Pages are static and are not listed by date. Pages do not use tags or categories.</em>&#8221; It will be interesting to see how page editing in the Site Editor is received, whether it is too confusing for users to understand what they are editing, or whether the baseline expectation is that content can be edited anywhere. </p>



<p>Revisions for design changes have landed in 15.8 with <a href="https://github.com/WordPress/gutenberg/pull/50089">a basic UI inside the Global Styles panel</a>. It shows a timeline of saved changes along with who made the change, so users can easily revert back to previous design changes. This creates an extra cushion or safety net for those who are designing their own sites and should provide a greater level of user confidence when making design changes.</p>



<img />



<p>Version 15.8 also introduces <a href="https://github.com/WordPress/gutenberg/pull/50030">theme previews for block themes</a>, a feature that has been sorely missing for early adopters of block themes. This is made possible by a new <code>theme_preview</code> parameter, which allows the user to see what the site would like if a different theme was active.</p>



<p>A few other noticeable changes in this release include the following: </p>



<ul>
<li>Post Featured Image: New design for Replace and Remove buttons. (<a href="https://github.com/WordPress/gutenberg/pull/50269">50269</a>)</li>



<li>More intuitive Details block with summary and innerBlocks content. (<a href="https://github.com/WordPress/gutenberg/pull/49808">49808</a>)</li>



<li>List View: Allow dragging to all levels of the block hierarchy. (<a href="https://github.com/WordPress/gutenberg/pull/49742">49742</a>)</li>
</ul>



<p>Check out the full <a href="https://make.wordpress.org/core/2023/05/20/whats-new-in-gutenberg-15-8-may-17/">changelog</a> for all the details on enhancements and bug fixes in 15.8.</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, 23 May 2023 01:53:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:69:"WPTavern: Shufflehound Releases Free Lemmony Child Theme for Agencies";s:7:"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=145111";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:80:"https://wptavern.com/shufflehound-releases-free-lemmony-child-theme-for-agencies";s: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:3032:"<p><a href="https://shufflehound.com/">Shufflehound</a> made a big splash in March when it <a href="https://wptavern.com/lemmony-a-free-wordpress-block-theme-with-30-patterns">released Lemmony</a>, a free WordPress block theme with more than 30 patterns. This was the company&#8217;s first block theme on WordPress.org and it is already active on more than 1,000 websites. Building on the success of this theme, Shufflehound has created a child theme for agencies.</p>



<p>Lemmony Agency bears a strong resemblance to its parent theme but with more agency-specific patterns. This theme ships with 25 new custom block patterns, on top of the ones already included in Lemmony, for a total of more than 50 patterns.</p>



<img />



<p>The patterns unique to this theme suit agencies but would also work well for non-profits, advocacy, portfolios, or businesses of any kind. These include a hero with services, accordions for things like FAQ, counters, more pricing tables, services with icons or images, a blockified sidebar, testimonials, and more.</p>



<img />



<p>The theme&#8217;s creators have done an excellent job in organizing all the patterns available to users. Inside the pattern explorer/inserter, they have been separated into different panels for the patterns specific to the Lemmony Agency theme, the Lemmony patterns, and the Lemmony full-page patterns. This makes it easier to build pages, since users won&#8217;t have to hunt through all the patterns lumped together.</p>



<img />



<p>The Lemmony Companion plugin, recommended when users install the theme, adds a handful of custom blocks that some of the patterns rely on to work. It includes blocks for a counter, icon, post featured image caption, typing text, hero auto-slider, and accordion. </p>



<img />



<p>This might be the best way to ensure these features are styled exactly to match the theme and give users more creative control inside these particular blocks. Sometimes using third-party plugins to add sliders or icons can look like it&#8217;s bolted onto the design in an unsightly way. A companion plugin designated specifically for this theme makes sense in this instance.</p>



<p>Shufflehound made an interesting choice creating Lemmony Agency as a child theme of what is already a very flexible multi-purpose theme. This certainly could have been shipped as full-page pattern but it would have also greatly expanded the patterns packaged with the parent theme. In these early days of block theming, it&#8217;s not yet clear what users might consider &#8220;pattern bloat&#8221; or too many patterns, especially since they can easily be categorized under various panels inside the explorer. </p>



<p><a href="https://wordpress.org/themes/lemmony-agency/">Lemmony Agency</a> is a solid option for building websites that need to showcase their services, display pricing, or simply maintain an informational web presence. It&#8217;s available for free from WordPress.org and will auto-install the parent theme at the same time.</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, 22 May 2023 20:35: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: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:93:"WordCamp Central: SiteGround joins the WordPress global community sponsorship program in 2023";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:39:"https://central.wordcamp.org/?p=3165350";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:118:"https://central.wordcamp.org/news/2023/05/siteground-joins-the-wordpress-global-community-sponsorship-program-in-2023/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2491:"<p>Please join us in welcoming <a href="https://siteground.com/wordpress-hosting.htm">SiteGround</a> to the&nbsp;<a href="https://central.wordcamp.org/sponsor-multiple-wordcamps/">2023 WordPress global community sponsorship program</a>! SiteGround’s pledge to sponsor all official WordPress community events (WordCamps, Meetups, and more) all around the world provides support and stability to our hardworking crew of volunteer event organizers. Thanks for everything, SiteGround!</p>


<div class="wp-block-image">
<a href="https://central.wordcamp.org/files/2023/05/siteground-logo-black-transparent-400x81-2.png"><img /></a></div>


<p><a href="https://siteground.com/wordpress-hosting.htm">SiteGround</a>&#8216;s hosting services are crafted to make managing websites easy, whether you&#8217;re building a site for yourself, your small business, or your clients.</p>



<p>We host over 2.8 Million domain names on a powerful Google Cloud Platform infrastructure, optimized with an array of in-house tools for seamless, faster and more secure WordPress performance:</p>



<p></p>



<ul>
<li>Fast: Choose from multiple data centers across USA, Europe, Asia, and Australia, complemented by over 170 CDN edge network locations with our free CDN to improve website performance. Powerful built-in Caching, custom PHP setup, and SiteGround Optimizer plugin for WordPress to make your sites up to 5 times faster right out of the box.</li>



<li>Secure: Advanced security on server, website, and application level with a free SSL, advanced built-in Web Application Firewall, SiteGround Security plugin, in-house antispam protection and AI-powered anti-bot system to keep your websites safe.</li>



<li>Easy to manage: Build or transfer WordPress projects in a few clicks with our WordPress Starter and Automatic website and Email Migrators. Manage multiple sites in one place hassle-free, get automatic core and plugin updates, add team collaborators, ship sites to clients, manage white-label hosting, and many more handy features to keep all the control, but spare you the hassle of website management.</li>
</ul>



<p>Our long-term expertise in helping WordPress users succeed online extends into our award-winning <a href="https://www.siteground.com/wordpress-plugins/siteground-optimizer">SiteGround Optimizer</a> and <a href="https://www.siteground.com/wordpress-plugins/siteground-security">SiteGround Security</a>; plugins, free to download and install on any hosting platform.</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, 22 May 2023 16: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:6:"Isotta";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:84:"WordPress.org blog: WP Briefing: Episode 56: What to Know About WordPress Playground";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/news/?post_type=podcast&p=14968";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:86:"https://wordpress.org/news/2023/05/episode-56-what-to-know-about-wordpress-playground/";s: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:16989:"<p>Join guest host Rich Tabor and WordPress Playground innovator Adam Zielinski as they discuss the capabilities and promise of WP Playground in episode 56 of the WordPress Briefing. Stay tuned for your small list of big things coming up in the next two weeks.</p>



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



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



<p>Host: <a href="https://profiles.wordpress.org/chanthaboune/">Josepha Haden Chomphosy</a><br />Guests: <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a> and <a href="https://profiles.wordpress.org/zieladam/">Adam Zielinski</a><br />Editor:&nbsp;<a href="https://profiles.wordpress.org/dustinhartzler/">Dustin Hartzler</a><br />Logo:&nbsp;<a href="https://profiles.wordpress.org/javiarce/">Javier Arce</a><br />Production:&nbsp;<a href="https://profiles.wordpress.org/bjmcsherry/">Brett McSherry</a> and <a href="https://profiles.wordpress.org/eidolonnight/">Nicholas Garofalo</a><br />Song: Fearless First by Kevin MacLeod</p>



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



<ul>
<li><a href="https://developer.wordpress.org/playground/">WordPress Playground</a> and the <a href="https://github.com/WordPress/wordpress-playground">Playground Github repo</a></li>



<li><a href="https://gliwice.wordcamp.org/2023/">WordCamp Gliwice</a> </li>



<li><a href="https://europe.wordcamp.org/2023/">WordCamp Europe 2023</a>, <a href="https://europe.wordcamp.org/2023/contributor-day/">Contributor Day,</a> and <a href="https://europe.wordcamp.org/2023/presenting-wp-connect/">WP Connect</a></li>



<li><a href="https://wordpress.slack.com/archives/C04EWKGDJ0K">#meta-playground</a> in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack</a></li>



<li><a href="https://chat.openai.com/">ChatGPT</a></li>



<li><a href="https://woocommerce.com/">WooCommerce</a></li>



<li><a href="https://www.cloudfest.com/">CloudFest</a> and <a href="https://profiles.wordpress.org/danielbachhuber/">Daniel Bachhuber</a></li>



<li>The <a href="https://wordpress.org/news/feed/blank">Kim Parsell Memorial Scholarship</a> for travel to WordCamp US 2023</li>



<li>Find your closest location for a <a href="https://wp20.wordpress.net/">WordPress 20th Anniversary celebration</a></li>



<li><a href="https://us.wordcamp.org/2023/wordcamp-us-2023-programming-team-announcement/">Changes to the WCUS event for 2023</a></li>
</ul>



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



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



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



<p>(Intro music)</p>



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



<p>(Intro continues)</p>



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



<p>Today we&#8217;re gonna spend a little time talking about WP Playground. This is a project that debuted at State of the Word in December 2022, but it was demoed for me about a month prior in November.</p>



<p>I was, and remain, absolutely floored by the potential future applications, as well as the innovative thinking behind it. So I&#8217;ve invited a couple of excellent WordPress futurists to the show today so that we can listen in on their conversation.</p>



<p>Welcome guys.</p>



<p><strong>[Rich Tabor 00:01:07]</strong></p>



<p>Hey everyone, I&#8217;m Rich Tabor, and I&#8217;m here today with Adam Zielinski to talk about WordPress Playground. So for those of you who don&#8217;t know what WordPress Playground is, can you tell us a little bit more about it, Adam?</p>



<p><strong>[Adam Zielinski 00:01:18]</strong></p>



<p>Absolutely. WordPress Playground is WordPress that works in your browser like there&#8217;s no server with PHP or database like there&#8217;s just your browser and JavaScript, and you can run it in so many more places that we’ll all get to. For example, I just came back from WordCamp Gliwice, where on a Contributor Day, a couple of developers got set up with WordPress in just a couple of minutes, whereas normally, it can take hours to do that.</p>



<p><strong>[Rich Tabor 00:01:44]</strong></p>



<p>Yeah, that&#8217;s, that&#8217;s pretty impressive. Do you think that, particularly for WordCamps and other demo-type areas, this would be something that&#8217;s very useful? Or what do you think would be the other problems that could be solved with WordPress Playground?</p>



<p><strong>[Adam Zielinski 00:01:55]</strong></p>



<p>Playground solves one primary problem, and that is WordPress is pretty difficult to get started with. I&#8217;m not even talking about creating your website, but let&#8217;s say, someone told you there&#8217;s this WordPress thing that you should try. Well, you Google for it, and you find installation instructions, and there&#8217;s like three hours of work for you there.</p>



<p>So then maybe you&#8217;ll find a hosting company, and you have to pay some money. So with WordPress Playground, you can actually try it for free because there&#8217;s no cost to run it. It just runs on your device. If you&#8217;re a developer, and you want to start learning WordPress, normally you have to go through quite an extensive setup process, and there are some tools to make it easier, but maybe there&#8217;s still friction like you have to even own a computer, like a PC device or a Mac. Playground can run on your phone, and it can power interactive tutorials that you can use and just start learning there and there with zero setup.</p>



<p>Like if you work on a product team and someone asks you to test a code change, with Playground you can just click a link and test it with no infrastructure behind it. And if you&#8217;re a company creating a plugin, you can just show your plugin in a live demo to people. And this isn&#8217;t something many plugins are doing because it&#8217;s quite hard to get a live demo set up.</p>



<p><strong>[Rich Tabor 00:03:12]</strong></p>



<p>Ah, that&#8217;s pretty impressive. So, you know, amongst like tutorials, code changes for developer environments, the mobile application running, do you think that, since there&#8217;s such a wide brevity of ideas that WordPress Playground can kind of plug into, would this be more of a developer tool?</p>



<p>Is that right? Or is Playground more of a like a click and play-type application that can run anywhere and demo anything?</p>



<p><strong>[Adam Zielinski 00:03:36]</strong></p>



<p>I&#8217;d say it&#8217;s both, but it&#8217;s more transparent for the users. So there are a whole lot of things you can do with Playground as a developer, as I just mentioned. But who are you doing these things for? Well, some of them are for the users, as in live demos, or there&#8217;s a WordCamp Europe coming, and I know some people are doing workshops there. They are going to use Playground to get everyone set up. So now that&#8217;s, well, maybe a workshop that teaches you how to build a theme, for example, right? Now you can just get started without any setup process. So there&#8217;s both, it&#8217;s very useful for development teams, and it&#8217;s very useful for them to build stuff for the final users.</p>



<p><strong>[Rich Tabor 00:04:21]</strong></p>



<p>That&#8217;s great. I know you, and I have probably both been in the same scenario at WordCamps when you&#8217;re trying to get dev environments set up, and it takes, you know, the better half of the workshop to get to step one. So this is really gonna be interesting to see it, especially at WordCamp Europe, and to see it getting into action.</p>



<p>Are you planning on going to WordCamp Europe this year?</p>



<p><strong>[Adam Zielinski 00:04:39]</strong></p>



<p>Absolutely, I will have a table at Contributor Day, a WordPress Playground table. So yeah, everyone&#8217;s invited to come over. I&#8217;ll show you a lot of cool stuff. And then at WP Connect on Saturday at 10:00 AM, there will be a WordPress Playground session where you&#8217;ll be able to learn more and see some cool demos.</p>



<p>And this will be a conversational format, so we&#8217;ll just have a nice chat.</p>



<p><strong>[Rich Tabor 00:05:01]</strong></p>



<p>Super cool. So how else can people find out a little bit more info about Playground and perhaps even get involved and contribute to the project?</p>



<p><strong>[Adam Zielinski 00:05:08]</strong></p>



<p>There&#8217;s a developer.WordPress.org/playground website. There&#8217;s a link in a show notes where you&#8217;ll be able, like this is the perfect entry point to the entire rabbit hole of WordPress Playground.</p>



<p>There&#8217;s a quite a few projects under the WordPress Playground umbrella, and they all live in a single GitHub repository where you can just find any issue that interests if you want to contribute and just start contributing. Also, there&#8217;s a Slack channel in WordPress org space called #meta-playground, and I highly encourage everyone interested in coming over to say hi.</p>



<p>And probably one of the best places to ask questions and get acquainted with the community.</p>



<p><strong>[Rich Tabor 00:05:54]</strong></p>



<p>Oh, that&#8217;s great; I&#8217;m very intrigued about the project overall. I think that there&#8217;s an immense amount of potential, for WordPress Playground. Just last question here, like, where do you see the future of this project going? What is the most interesting application that hasn&#8217;t been done yet, or the things that are really gonna be the next level in unlocking Playground for everyone?</p>



<p><strong>[Adam Zielinski 00:06:12]</strong></p>



<p>There&#8217;s quite a few. Imagine being able to go to WordPress.org and have a WordPress demo right then and there without having to download anything. Then you customize it, and you have a button to host your website anywhere or just to download it.</p>



<p>Imagine having a live preview for all the themes and plugins in the directory and even in WordPress core, but these are sooner than later. Maybe like, let&#8217;s talk more grandiose, shall we? So there&#8217;s this term, 1 billion new users coming online in the next, like in the nearest future, and plenty of them doesn&#8217;t even own a desktop device. Maybe they have a mobile phone, maybe they have a tablet, maybe we&#8217;re talking about a young, prospective developer somewhere. And currently, if you don&#8217;t own a desktop device, you cannot contribute to the WordPress plugin ecosystem at all.</p>



<p>Like, we&#8217;re seeing more and more of creating themes with no code, which is really exciting. But you cannot build the plugin, really. Well, with WordPress Playground. Suddenly you can do development on a mobile device. So development tools and code editors and just the entire suite of things we use as the developers on our desktop of devices like this may come online and be available in your browser.</p>



<p>And if you&#8217;re on a train and you just have a phone with you, but you still want to learn, how to build a plugin, well, you&#8217;ll be able to do that. Furthermore, there&#8217;s a lot of exciting opportunities with ChatGPT, as in, well, here&#8217;s a WordPress running entirely on your device. So maybe if that&#8217;s connected to ChatGPT, you&#8217;ll be able to say, well, I like fish, or like, I want two columns and a photo of a racing car on top of it.</p>



<p>And because ChatGPT can output HTML, we connect the two, and suddenly, you can build a website entirely in your browser using natural language.</p>



<p><strong>[Rich Tabor 00:08:20]</strong></p>



<p>Man, that&#8217;s, that&#8217;s really interesting. It really does unlock the next, potentially the next like, wave of innovation in the WordPress experience, especially removing all the complications of getting set up and actually seeing what&#8217;s there. I think that it really could, be huge for users every day.</p>



<p><strong>[Adam Zielinski 00:08:38]</strong></p>



<p>Oh, here&#8217;s one more. So, edge computing is big lately, and it&#8217;s going to be bigger in the future. WordPress Playground runs on this new technology called Web Assembly, and it just happened so that a bunch of edge computing providers allows you to run web assembly on their gear. So imagine having WordPress running entirely in edge infrastructure with no centralized server.</p>



<p>Truly decentralized WordPress. It could be big for a well cost of operating, but also for speed, but also even further down in the future. Imagine downloading the actual, you know, even WordPress around time to your device and having the entire website on your phone. So then you know, you&#8217;re on a train, you enter a tunnel, but you can still browse that WooCommerce store and add things to your cart even though there is no range at all.</p>



<p><strong>[Rich Tabor 00:09:32]</strong></p>



<p>Wow, that&#8217;s, that&#8217;s pretty crazy. How far out there do you think something like that is?</p>



<p><strong>[Adam Zielinski 00:09:37]</strong></p>



<p>It&#8217;s hard to tell. I mean, technically, it is possible. There are a lot of challenges with regard to privacy, right? And data security for the edge computing case specifically. As for the development tools, there was a Cloud Fest hackathon earlier this year where I was with Daniel Bachhuber, also from Automattic, and we led this exciting project that brought the WordPress development environment into the browser using a couple of editors that are out there, and this is too much of an MVP for actual production use yet, but we got it working, and we build an actual plugin on a phone without internet access.</p>



<p><strong>[Rich Tabor 00:10:19]</strong></p>



<p>Wow. And that was just a hackathon, just hacking at it to see what you can get.</p>



<p><strong>[Adam Zielinski 00:10:23]</strong></p>



<p>Yeah, it was two and a half days.</p>



<p><strong>[Rich Tabor 00:10:25]</strong></p>



<p>Oh, that&#8217;s awesome. That&#8217;s really cool, man. Well, this has been quite a pleasure. Thanks, Adam, for chatting all about WordPress Playground. Folks, just be sure to check out developer.WordPress.org/playground to explore, experiment, and play with WordPress Playground.</p>



<p>This has been awesome, Adam.</p>



<p><strong>[Adam Zielinski 00:10:43]</strong></p>



<p>Thank you so much for having me, Rich.</p>



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



<p>What a remarkable new way of working with and experiencing WordPress. I would love to be able to find ways across the project and ecosystem to help folks see what they&#8217;re getting into before they get into it, but also, who knows what the future holds for that project. Keep an eye on it.</p>



<p>(Musical interlude)</p>



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



<p>That brings us to our small list of big things happening right now in the WordPress project. The first one is that the Kim Parel Memorial Scholarship for WordCamp US 2023 is open, and applications for it are the WordPress Foundation will once again be offering that scholarship for Travel to WordCamp US.</p>



<p>It is for specifically for women in technology, women in the WordPress space. I&#8217;ll include a link to that in the show notes.</p>



<p>The second thing is WordPress&#8217; 20th anniversary is still coming, as we heard in the last podcast.</p>



<p>So we have reached over 100 events that are scheduled on or around May 27th, which is WordPress’ launch date. There is still time to find your closest location and attend one of those events. And probably, there&#8217;s also time to pull together an event of your own. Head on over to wp20.WordPress.net if you would like to see events in your area.</p>



<p>And the third thing is WordCamp US 2023. I realize WordCamp Europe comes before that, but the programming team actually has a really interesting thing that they&#8217;re doing this year. They have some changes to the way that they are organizing the event and finding speakers for the event. But as always, they are working very hard to make sure it is an attendee-focused event.</p>



<p>I&#8217;m gonna include a link or two to some announcements that are really worthwhile there. Head on over to the podcast page to see those. And that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I&#8217;m your host, Josepha Haden Chomphosy. Thanks again to my guests, and I&#8217;ll see y&#8217;all in a couple of weeks.&nbsp;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 22 May 2023 12:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Nicholas Garofalo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:98:"Gutenberg Times: Gutenberg Changelog #83 – WordPress 6.2.1, Gutenberg 15.7, 15.8 and experiments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://gutenbergtimes.com/?post_type=podcast&p=24228";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:90:"https://gutenbergtimes.com/podcast/gutenberg-changelog-83-wordpress-gutenberg-experiments/";s: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:64666:"<p>Fabian Kägy and Birgit Pauli-Haack discuss the new enhancements in Gutenberg plugin releases 15.7 and 15.8 as well as the Experiments available in the plugin.</p>



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



<ul>
<li>Music:&nbsp;<a href="https://soundcloud.com/xirclebox">Homer Gaines</a></li>



<li>Editor:&nbsp;<a href="https://www.linkedin.com/in/sandy-reed/">Sandy Reed</a></li>



<li>Logo:&nbsp;<a href="https://markuraine.com/">Mark Uraine</a></li>



<li>Production:&nbsp;<a href="https://icodeforapurpose.com">Birgit Pauli-Haack</a></li>
</ul>



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



<h2 class="wp-block-heading">Special Guest: Fabian Kägy </h2>



<ul>
<li>Twitter: <a href="https://twitter.com/fabiankaegy">@fabianjaegy</a></li>



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



<li>Personal website: <a href="https://fabian-kaegy.com/">fabian-kaegy.com</a></li>



<li><a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-59-extensibility-of-the-block-editor/">Gutenberg Changelog #59 – Gutenberg 12.4, Developer Hours, Extensibility of the Block Editor and more</a></li>



<li><a href="https://gutenberg.10up.com/">10up Gutenberg Best Practices!</a></li>



<li><a href="https://www.npmjs.com/package/@10up/block-components">10up Block Components</a></li>
</ul>



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



<ul>
<li><a href="https://developer.wordpress.org/news/2023/05/whats-new-for-developers-may-2023/">What’s new for developers? (May 2023)</a></li>



<li><a href="https://developer.wordpress.org/news/2023/04/how-webpack-and-wordpress-packages-interact/">How webpack and WordPress packages interact</a></li>



<li><a href="https://developer.wordpress.org/news/2023/04/per-block-css-with-theme-json/">Per-block CSS with theme.json</a></li>



<li><a href="https://make.wordpress.org/test/2023/05/04/fse-program-build-a-block-theme-summary/">FSE Program Build a Block Theme Summary</a><a href="https://make.wordpress.org/test/2023/05/11/fse-program-front-page-fun-summary/">FSE Program Front Page Fun Summary</a></li>



<li><a href="https://wptavern.com/wordpress-themes-team-releases-stacks-a-community-theme-for-building-slide-decks">WordPress Themes Team Releases Stacks: A Community Theme for Building Slide Decks</a></li>
</ul>



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



<h3 class="wp-block-heading">WordPress 6.2.1 + 6.2.2</h3>



<ul>
<li><a href="https://wordpress.org/news/2023/05/wordpress-6-2-1-maintenance-security-release/">WordPress 6.2.1 Maintenance &amp; Security Release</a></li>



<li><a href="https://wordpress.org/news/2023/05/wordpress-6-2-2-security-release/">WordPress 6.2.2 Security Release</a></li>



<li><a href="https://wptavern.com/wordpress-6-2-2-restores-shortcode-support-in-block-templates-fixes-security-issue">WordPress 6.2.2 Restores Shortcode Support in Block Templates, Fixes Security Issue</a></li>
</ul>



<h3 class="wp-block-heading">Gutenberg 15.7</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2023/05/04/whats-new-in-gutenberg-15-7-03-may/">What’s new in Gutenberg 15.7? (03 May)</a></li>



<li><a href="https://wptavern.com/gutenberg-15-7-adds-site-logo-upload-to-inspector-controls">Gutenberg 15.7 Adds Site Logo Upload to Inspector Controls</a></li>
</ul>



<h3 class="wp-block-heading">Gutenberg 15.8</h3>



<p><a href="https://make.wordpress.org/core/2023/05/20/whats-new-in-gutenberg-15-8-may-17/">What’s new in Gutenberg 15.8? (May 17)</a></p>



<h2 class="wp-block-heading">Experiments in Gutenberg</h2>



<table><tbody><tr><th>Zoomed out view</th><td>&nbsp;Test a new zoomed out view on the site editor (Warning: The new feature is not ready. You may experience UX issues that are being addressed) (<a href="https://github.com/WordPress/gutenberg/pull/41156">#41156</a>)</td></tr><tr><th>Color randomizer</th><td>&nbsp;Test the Global Styles color randomizer; a utility that lets you mix the current color palette pseudo-randomly. (<a href="https://github.com/WordPress/gutenberg/pull/40988">#40988</a>)</td></tr><tr><th>Command center</th><td>Test the command center; Open it using cmd + k in the site or post editors. (<a href="https://github.com/WordPress/gutenberg/pull/50128">#50128</a>)</td></tr><tr><th>Grid variation for Group block</th><td>&nbsp;Test the Grid layout type as a new variation of Group block. (<a href="https://github.com/WordPress/gutenberg/pull/49018">#49018</a>)</td></tr><tr><th>Details block</th><td>&nbsp;Test the Details block (<a href="https://github.com/WordPress/gutenberg/pull/49808">#49808</a>)</td></tr><tr><th>Block Theme Previews</th><td>&nbsp;Enable Block Theme Previews (<a href="https://github.com/WordPress/gutenberg/pull/50030">#50030</a>)</td></tr><tr><th>Navigation block</th><td>&nbsp;Test the Navigation block using the Interactivity API (<a href="https://github.com/WordPress/gutenberg/pull/50041">#50041</a>)</td></tr></tbody></table>



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



<div class="wp-block-group is-layout-flow wp-block-group-is-layout-flow"><div class="wp-block-group__inner-container">
<ul>
<li>Did you like this episode? <a href="https://lovethepodcast.com/gutenbergchangelog"><strong>Please write us a review </strong></a></li>



<li>Ping us on Twitter or send DMs with questions. <a href="https://twitter.com/gutenbergtimes">@gutenbergtimes </a>and <a href="https://twitter.com/bph">@bph</a>.</li>



<li><em>If you have questions or suggestions, or news you want us to include, send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. </em></li>



<li><em>Please write us a review on iTunes! <a href="https://gutenbergtimes.com/itunes/">(Click here to learn how)</a></em></li>
</ul>
</div></div>



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



<p><em>Birgit Pauli-Haack</em>: Hello and welcome to our 83rd episode of the Gutenberg Changelog Podcast. In today&#8217;s episode, we will talk about WordPress Point Release, 6.2.1, Gutenberg 15.8, and of course the previous one, Gutenberg 15.7 as well, and some of the experiments featured hiding in the Gutenberg plugin. I&#8217;m your host, Birgit Pauli-Haack, curator of the Gutenberg Times and WordPress developer advocate, and a full-time core contributor for the WordPress Open Source project.&nbsp;</p>



<p>I&#8217;m so happy to have, again, Fabian Kägy back on the show. It&#8217;s been a while since we talked and so much happened. We just found out, it was the episode 59 and it was in February 2022, well, it&#8217;s a whole world happened in between. So for our new listeners, Fabian Kägy is the Associate Director of Editorial Engineering at 10up and a core contributor to the Gutenberg project since 2017, I think. So welcome back on the show, Fabian. How are you today?</p>



<p><em>Fabian Kägy</em>: Thank you so much for having me. I&#8217;m excited to be back on this.</p>



<p><em>Birgit Pauli-Haack</em>: I&#8217;m glad you&#8217;re here. So I have to ask, editorial engineering, what does that entail at the agency 10up?</p>



<p><em>Fabian Kägy</em>: So that is a special, in quotation marks, &#8220;made up role&#8221;, where I started down the path of a front end engineer and over time became more and more passionate about all things editorial experience. So that is now a special role where I get to focus part of my time on actually coming up with best practices and solutions for working with a block editor and helping the entire team level up and carved out my niche.</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s awesome, especially because in view of the next phase of Gutenberg where it is actually all about collaboration on an editorial team, so making that a smooth experience is definitely something we all will be working on for when 6.3 come out, I think. Your input will be invaluable for your clients, as well as for the team, I think.</p>



<p><em>Fabian Kägy</em>: Yes. I&#8217;m very, very excited about all the things that are lined up for all of us to work on and to explore, and it&#8217;ll be fun.</p>



<p><em>Birgit Pauli-Haack</em>: So with the developer blog, I&#8217;m part of the editorial team that does reviews and works with writers. Once in a while, we start out with Google Docs and have everybody comment on it. Some writers say, &#8220;Well, I&#8217;m waiting for that moment where I don&#8217;t have to use Google Docs anymore to collaborate with people on a post and not have to copy/paste it over.&#8221; So we are very much looking forward to that collaboration and we will be eating the Gutenberg dog food, so to speak, on the developer blog.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>



<h3 class="wp-block-heading"><strong>Announcements</strong></h3>



<p>Speaking of the developer blog, Justin Tadlock just published the What&#8217;s New for Developers in May 2023 on the developer blog, and that&#8217;s a series of roundup posts that were started in February, where we look at all the publications that come out throughout the month, what&#8217;s new in core, the Gutenberg plugin, the keeping up with Gutenberg index page, and so much more, and just pick those things that are relevant for developers not to teach them how to use them, but more like, &#8220;Watch out, this is coming,&#8221; and prepare them for an X release pretty much.&nbsp;</p>



<p>The main one has quite a few items in there that are highlighted there. One is the Block Selectors API, which has definitely the markup of a larger tutorial, but it got quite a few developers excited about CSS and their blocks and being more in control of it. Another one as we will also talk about it is the first community theme and all things. So it&#8217;s pretty much a roundup of a lot of things that are interesting for extenders like plugins, developers, theme developers, and also agency developers.</p>



<p>So we share the latest blog post link in the show notes, but if you haven&#8217;t looked at those yet, and if you&#8217;re a developer, subscribe to the feed of the developer blog or just for the roundup post so you get a heads up on many things.</p>



<p><em>Fabian Kägy</em>: I would highly encourage everybody to take a look at those because they&#8217;re super valuable, just quick shares of what&#8217;s going on, what are the things to look out for, and even if you&#8217;re not developing for the actual experimental Gutenberg plugin, it is something. It makes it so much easier when the next big WordPress update comes around to know what&#8217;s in the pipeline, what are the things that are being talked about and already have some grasp of just what&#8217;s coming.</p>



<p><em>Birgit Pauli-Haack</em>: Well, thank you so much. Justin does a great job in putting it all together and also shares some resources that are available on Learn WordPress. Then there were two new posts since we had the last show. There was one on how Webpack and WordPress packages interact by Ryan Welcher. That really gets you a little bit more theory around how WordPress and Webpack work together. For those that are not like me, I trust the things &#8230; I trust in God. I trust in things that if I put an NPM, run something, that it&#8217;s all going to work out, but some people want to really dive into Webpack some more and this gives them a great introduction to that. How are you doing with Webpack? Are you manipulating Webpack for your own development?</p>



<p><em>Fabian Kägy</em>: So I used to do it a lot, especially in the early days of the WordPress Scripts package. There were so many things that were not yet a part of it, and I was very actively adding hacky solutions to add post CSS and all of those SaaS things to WordPress Scripts. That was my introduction to actually working with Webpack. Now, WordPress Scripts takes care of most of our needs or for some of the things, we have a similar tool at 10up that is a helper so we don&#8217;t have to deal with custom Webpack configurations.</p>



<p>I read through that post from Ryan about how that interacts, and it&#8217;s a really solid deep dive. If you want to understand the areas, the inner workings of how some of these Webpack plugins interact, which you don&#8217;t need to, but if you want to, that is very, very useful.</p>



<p><em>Birgit Pauli-Haack</em>: Then the other blog post was the per-block CSS with theme.json. The per-block CSS came out out of feedback from the community that custom CSS were not available anymore to put in custom CMS for the block themes and for sites, and it was introduced with 6.2, but it also needs some additional handle. Justin wrote a blog post about it, how best to think about per-block CSS with theme.json without getting too deep into the weeds and how that&#8217;s offered to the user. So definitely read up about it.&nbsp;</p>



<p>For the FSE program, Anne published two summary posts and you make your part of coffee first because they&#8217;re both very long but also very detailed from the latest testing calls. One was Build Your Block Theme with the great block theme plugin and the other one was the testing call 21 for the FSE program for the front page fund summary. There will be a new testing call coming out of the FSE program.</p>



<p>So if you are into block themes and users use them and all that, it&#8217;s definitely a good overview on what are the pain points, what are the team working on because Anne is very, very thorough in adding to all pain points or discussion points, also the PRs or the issue that is on GitHub about that particular topic. So you can chime in with your opinions, with your experiences, and with your testing, and it would really help if you chime in and be encouraged to actually be part of the testing project. That&#8217;s it.&nbsp;</p>



<p>Of course, we share all the links in the show notes for this episode.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Community Contributions</strong></h3>



<p>Another great announcement and community contribution is the first theme coming out of the community theme project where community members and team members are working together on creating block themes and the first one is called Stacks. It&#8217;s a theme with which you can build slide decks. It&#8217;s a very interesting approach to a website that is more a slide deck rather than have navigation from page to page to page. It&#8217;s more like a guided tool that you can use it or you can use it for your next presentation, but you don&#8217;t have to use a third-party tool for that if you want to spin up a website and just use it for your presentation.&nbsp;</p>



<p>It&#8217;s quite interesting to see how that comes together. The code is certainly available on GitHub and we share both the announcement post, as well as the write up by Sarah Gooding on the WP Tavern for you.</p>



<p><em>Fabian Kägy</em>: These explorations and these themes and plugins that allow you to build your slide deck in the block editor, I&#8217;m always amazed when I see that. I think a couple of years ago, Ella was maybe one of the first ones who did talk at a React conference and blew my mind in the end when they revealed, &#8220;Hey, and all of this was created in the block editor and these slides are powered by it.&#8221; I think Nick Diego also did it at WordCamp US or at WordCamp and it&#8217;s always pretty cool to see.</p>



<p><em>Birgit Pauli-Haack</em>: You&#8217;re right. Nick Diego did it at WordCamp US for his talk, Build A Block in 15 minutes, and he built actually that slide back there as well. It&#8217;s very interesting how this can be used on your own website. Yes, Ella had a slide. It was actually a block that she added. I think it was the same for Nick Diego and now we have a theme for it. So it&#8217;s really cool.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>



<h3 class="wp-block-heading"><strong>What’s Released</strong></h3>



<p>All right. That brings us into what&#8217;s released and, of course, let&#8217;s start with the minor release for WordPress, the 6.2.1 Point Release that just came out this week and there were a few hiccups there. Do you want to talk about this and what&#8217;s happening there?</p>



<p><em>Fabian Kägy</em>: Sure. So 6.2.1 was released, I believe it was at some point early this week. One thing, there was a security issue that the security team took care of and made sure that that gets resolved as quickly as possible, but that security issue essentially resulted in short codes no longer working in block templates. So in a block-based theme, if you have a short code inside a block template, that will no longer actually get converted to the dynamic data. That has caused some issues for folks, especially around auto updates because it&#8217;s just a minor patch release, but it is breaking some existing sites, which as always, it is a very difficult choice to make and a very unfortunate thing when that has to happen because of security thing.&nbsp;</p>



<p>There is an open issue in track where a lot of this is getting discussed right now, and it was discussed in the core chat yesterday, where essentially, it is very unfortunate when something like that has to happen. From my perspective, I think the team, if there is a security issue, that is the only thing that can be done. The only thing that I think we as a community can try to be a little better at is communicating those types of things ahead so folks are more aware of that, &#8220;Hey, we needed to make a difficult decision here. Beware, you should make this update, but here are some things that you can do instead to help your site still be up there,&#8221; because the communication around the issue could have been a little better.</p>



<p><em>Birgit Pauli-Haack</em>: I don&#8217;t think there&#8217;s no maybe about it, but it was a little obscure in the change log and it wasn&#8217;t saying, &#8220;Okay. It&#8217;s going to break sites,&#8221; but I think it&#8217;s really hard to also suggest a solution right now. So Jean Baptist Audras was one of the release leads together with George Mamadoshvilli, and he wrote in the core dev chat on Wednesday night, &#8220;The release itself went pretty well. Thanks everyone for your patience. However, as you may know, one security fix led to the important issues with the short codes used in templates, but it was not templates per se, but block templates in block themes. So the issue is currently actively discussed in the security editor team and some hypotheses have been made to sort this out in a quick followup release. No schedule is available right now because the discussions haven&#8217;t been finished yet, but it will depend on the followup patch currently discussed by the editor team.&#8221;</p>



<p>So to just point out, and Paul Byron had actually &#8230; All the solutions on how to deal with it right now in the emergency situation when you see dozens or even hundreds of page breaks, one is to roll back to 6.2 with a core rollback plugin, use the short code, and put them in template parts. That seems to be working in the block themes that you put the short code in a template part and add that template part to the template or have &#8230; In the ticket that you mentioned, Fabian, there were also a code example on how to introduce making the shortcuts work again, but all three of them introduced the security issue again.&nbsp;</p>



<p>So I&#8217;m not sure quite how to advise people to work, but there are no good choices right now because you are caught between you want your client&#8217;s side to work, but you also don&#8217;t want their security issue to be out there too long. So the core editor team is definitely working on a solution to fix the security fix, but all, what I just said, is actually just introducing back the security issue into your sites.&nbsp;</p>



<p>So there are also opinions that short codes might be a legacy way of dealing with things. Maybe it&#8217;s a good call for converting the most important short codes to blocks and use them for the block editor instead of &#8230; but not everybody has the capacity for it, not everybody has the time for it or they&#8217;re just not there yet, but the plugins that they use are also not converting the shortcuts to blocks. So it&#8217;s the nature of the beast. I don&#8217;t think the shortcuts will ever go away, but there&#8217;s a better way to handle that.</p>



<p><em>Fabian Kägy</em>: Yeah, definitely. In regards to the various options that we have right now, rolling back and that plugin that exists and that code that you can add to your theme, those all add back the vulnerability, like you said. I wasn&#8217;t sure from my understanding whether putting the short code in the template part actually caused any issues. I thought that that was the best proposed solution even though it&#8217;s clunky to have to deal with template parts for those areas individually, but from my understanding, that was the best outcome where you&#8217;re not really introducing the security vulnerability, but also can retain your feature or the look of your site. So I think that is the best option right now, but yeah, it is a little opaque.</p>



<p><em>Birgit Pauli-Haack</em>: Good point. Thank you for pointing that out again. Okay. The rest of 6.2.1, quite a few bug fixes for core, as well as for the editor that were found during the release of 6.2 and didn&#8217;t make it into 6.2, but that&#8217;s why the followup release was really on the schedule relatively to the 6.2 release. We will also share the changelog for the release in the show notes, as well as the tickets for the discussion. Paul Byron also added that solution with the template parts to the ticket so you have it all in one place to look up for if you want to follow up on that.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>



<h3 class="wp-block-heading"><strong>Gutenberg 15.7</strong></h3>



<p>All right. Next one up was Gutenberg 15.7 and it had quite a few enhancements. One is that as group and media texts have now allowed blocks attributes that can be passed to the inner block props, so to speak, that means that you can control which blocks can be added to a certain group or a media text block if you wanted to.</p>



<p><em>Fabian Kägy</em>: That is a really useful thing for extenders or theme builders or if you create a pattern that is meant to be a certain thing, you&#8217;re now able to restrict which other blocks can be used within that area, which can be super useful when you build a call to action and have some styling around that and don&#8217;t want to support a table to be in that call to action, for example. This is so useful to be able to do that. So we don&#8217;t have to build the custom block for it, but instead we can create a pattern and have all those options and can curate that editorial experience to really, the level that we want to curate it to. With the template and template block, we were able to do some things, but now with the allowed blocks, we have most of the controls of an actual inner block area also exposed for these blocks that support inner blocks, which is very useful, I think.&nbsp;</p>



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



<p><em>Fabian Kägy</em>: Next up, we have the site logo added a replacement flow that allows you to change out the actual logo using the inspector control. That is just an addition, an alternative way that you can deal with the site logo essentially. You can still use the inline controls, but while you are in the sidebar tweaking your spacing or any other visual controls, you can also quickly swap out the media there, which I think is an interesting approach to this.</p>



<p>For this one in particular, I&#8217;m interested to see the feedback around it because for the most part, we&#8217;ve been very strict about there should be direct manipulation of content right in the editor canvas and not many controls should live in the inspector controls. It&#8217;s not removing it from the inline, but it&#8217;s also adding that secondary way of manipulating it to the inspector controls. I&#8217;m very curious to see how that will play out and how that may affect just how we use this.</p>



<p><em>Birgit Pauli-Haack</em>: So inspector controls is just another way to say sidebar, just make sure where those tools are when you first encounter them. I think it comes more like we want to be a parity with a customizer. That&#8217;s one more step. Then in the inspector in the sidebar, when you replace the media, you are going right directly to the media library and select that. So you don&#8217;t have to &#8230; It seems to be a slightly different workflow than it is from the toolbar.&nbsp;</p>



<p>So the next feature is actually a really cool addition or enhancement of the fluid typography. So when the fluid typography was introduced first in 6.1, it still had the problem that if you have very large fonts, they wouldn&#8217;t go small enough for the mobile version because the calculations would stop and it would still be too big. This feature introduces a logarithmic scale factor to calculate the minimum font size and now the font adopts to all screen sizes. Even if you have a 68 or 102 pixel font, it will scale down to a mobile version and not stop at 50 or something like that.&nbsp;</p>



<p><em>Fabian Kägy</em>: The next thing on the list here is the behavior of the top toolbar has been changed, and that is for a long time now you&#8217;ve been able to using that user settings menu in the upright corner change the behavior of the block toolbar to no longer be attached to the actual block, but instead always be fixed at the top of the editor. The behavior of that has been changed so that you can collapse that toolbar and still have it available there, but because the space in that top toolbar is quite sparse, that allows for just some more flexibility with how things are getting laid out there.&nbsp;</p>



<p>There are a couple more things that we&#8217;ll talk about later that were changed about the overall layout of that tool toolbar. Actually, I like it very much the way that it&#8217;s coming together and with some of the explorations happening there. I really like the direction where a lot of this is going right now.</p>



<p><em>Birgit Pauli-Haack</em>: It also fixed &#8230; One particular thing that was still missing is that you now have access to the parent block, which on the block toolbar you were always able to select the parent toolbar and then the sidebar changed and everything. When you had the toolbar fixed on the top, you wouldn&#8217;t have that particular icon available to click on to manipulate the parent block. That has changed too, and it came in with that particular feature there.&nbsp;</p>



<p>I was always 50/50. Some weeks I like having the block toolbar right on the block, especially when I&#8217;m further down on the block page, and sometimes I just want it on the top and I&#8217;m changing it all the time. I don&#8217;t know how you do it. So I have not tested this new toolbar fixed setting yet, but I definitely will. I read through the comments and there are some discussions. So please add your feedback and your experiences to it and what you think about it to make it the best it can be.</p>



<p>The next is that the image block now also displays &#8230; No, it&#8217;s not the image block, it&#8217;s when an image is in a block or in a template, it now also displays the borders on the placeholder. So if you have a template that gives you all the series of blocks and each block you want the feature image there, you will also see now in the placeholder the color of the borders, including the color of it. So it makes your choices of images maybe even smoother. It&#8217;s very subtle, but it&#8217;s definitely a live quality enhancement that I definitely like because sometimes you just need to have a picture that does not clash with your borders if you had a design option that image has borders.</p>



<p><em>Fabian Kägy</em>: It just makes your life a lot easier when you&#8217;re creating a template and you don&#8217;t &#8230; Before this when there was a placeholder where no actual image was selected for the post, it was just difficult to gauge, &#8220;Hey, how do these border controls actually affect this?&#8221; Having the placeholder resemble the actual image much closer and retain all of those border controls is just a very good thing.&nbsp;</p>



<p>Next up, we have a change in experiment for the actual pattern insertion modal, which I am really excited about. When you use the pattern instruction modal, you know that all of the various patterns are displayed in a grid, and that grid can look a little weird sometimes because it&#8217;s very staggered how these &#8230; Some patterns are very tall, and then the next one is very narrow, very short. There&#8217;s a lot of white space in that modal. This option here tries a masonry layout where they actually &#8230; If you&#8217;ve ever used Pinterest, it&#8217;s essentially that type of layout where it just fills all that white space and it&#8217;s showing all of those, I think, in a more elegant fashion and it just makes that look a little more refined. I&#8217;m very happy to see that.</p>



<p><em>Birgit Pauli-Haack</em>: It&#8217;s definitely a more natural look for the pattern modal. The next feature is that duotone block controls are now added to the sidebar. They were hidden before in the block toolbar and you had to know that they are there and the icon was a little bit obscure. Then the options when you do it in the block toolbar is it feels like you are in the wrong place to make those decisions, and now you can make them from the sidebar. I really like that. It&#8217;s a clear adoption to the interfaces that we saw from other design tools.</p>



<p><em>Fabian Kägy</em>: Next up, in the accessibility section, there are some refactors of how the ARIA attributes for the list view have been modified, which makes it much easier and much more accessible to navigate through the list view. It&#8217;s always good to see those enhancements over time.</p>



<p><em>Birgit Pauli-Haack</em>: Those ARIA levels, there were quite a few in the list view, so there was a major overhaul of the display of the list view. I think Alex Stein did some great work there to make it happen and put it over the finish line.</p>



<p>So I&#8217;m scrolling a little bit further down to the changelog and I have the feeling we are done with 15.7. It was a smaller release, but it had definitely some great features in there.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Gutenberg 15.8</strong></h3>



<p>We are now coming up with 15.8. Fabian, you were the release lead on that. Do you want to kind of kick it off and let us know what&#8217;s in there?</p>



<p><em>Fabian Kägy</em>: Sure. So there were a couple of major features which get their introduction here, which is always fun. One of them is the addition of a command center. There actually is &#8230; There was a post on the make blog from Riad that I&#8217;m sure will get added to the release note or to the podcast notes here that explains a little bit more in depth what this command center actually is. Right now, it is an experiment, but it essentially like spotlights on a Mac, for example, or some of these launchers. You have a quick keyboard command. In this case, it&#8217;s command K, to launch essentially, an open prompt field where you can put in your prompts and jump to different places of the editor or create new pages or just perform quick actions.&nbsp;</p>



<p>It&#8217;s also meant to be extendable and meant to be something that plugin developers can hook into and allow users to actually quickly navigate their site and perform actions. I&#8217;m really excited to see if this comes to life and explore how this ships out in the future. With this feature, I&#8217;m so here for it, I&#8217;m so excited about it. I cannot wait for the day where this gets expanded outside of the editor view and is just available in all of the screens of WordPress because right now, it is limited to the editor screens, but I think in the future, this will be available in all of the pages of the admin of WordPress. I&#8217;m so looking forward to that.</p>



<p><em>Birgit Pauli-Haack</em>: Riad&#8217;s post on the Make Core Blog &#8230; Blog and block, sometimes I get it mixed up, but I did it right this time. It&#8217;s the Make Core Blog. It&#8217;s called Command Center and Request for Feedback. So he explains what the prototype is. There&#8217;s also a small little video that quickly shows you how it works and then explains the API and the static commands and also what dynamic commands are, definitely, and the contextual commands. So there are three commands that you can have it use, but it&#8217;s also the extendability in mind for plugin developers.&nbsp;</p>



<p>I think it also triggered a few things. If you want to employ an AI to use within the block editor, having a standard interface that can call AI commands is certainly beneficial to the editor. So as Fabian said, I will share the post in the show notes so you can chime in and see what you think about it and how it works. It&#8217;s really hard to describe on a podcast, audio podcast, for that reason.</p>



<p><em>Fabian Kägy</em>: As somebody who has championed extensibility and plugability in the editor for such a long time, I&#8217;m so happy to see how this feature is getting rolled out and how it is built with that extendability and plugability from the very beginning. So I&#8217;m really excited about this.</p>



<p><em>Birgit Pauli-Haack</em>: If you want to try it, it&#8217;s still behind the experiment flag. You need to go to install the plugin 15.8 and then go to the Gutenberg menu on your WP admin and then there&#8217;s an experiments page and you need to check the mark for the command center to actually be able to test it.&nbsp;</p>



<p>The next item on the list is a new feature as well, and the first version of the revisions UI for the global styles, so all the talk about global styles and new features and new options to change things. Some people want to try just something out and then revert to the previous version and there was no revision available for the global styles. Now, there is, and it has actually some nice features. When you have the site editor style, the style site open and click on the revisions, it will show you a history of the revisions, and when you click on the items, it will show you a version of it on the canvas and you can also compare versions.&nbsp;</p>



<p>So I think it&#8217;s getting there. It definitely needs some more refinement in terms of what information will be there, how many revisions are we showing, and all that. So that&#8217;s a really interesting progression on this global styles editing.</p>



<p><em>Fabian Kägy</em>: If you&#8217;ve ever used revisions of a standard post or a page since the block editor was introduced, this is a great feature for global styles and I think it&#8217;s the right thing to roll it out for this first, but the live preview of a revision in a rich preview makes me so excited for a future where we can eventually get rid of the existing code view of revisions for standard post content stuff and actually show rich previews of that because, especially since the introduction of blocks, the revisions UI is just really, really difficult for non-technical people and even technical people to really manage because you just get a code view and are trying to figure out what changed.&nbsp;</p>



<p>This year is a visual preview of what revisions look like for global styles and it&#8217;s making me so excited about what&#8217;s to come for more other visuals or revisions in the future.</p>



<p><em>Birgit Pauli-Haack</em>: I totally agree that revisions for the posts and pages are on the board for the collaboration project, the phase three of Gutenberg and making revisions be aware is definitely something we are all looking forward to.&nbsp;</p>



<p><em>Fabian Kägy</em>: Next up, we have the inspector panel. So again we&#8217;re talking about that right-hand sidebar of the global styles panel is now getting or got a refactor to make it work and look more similar to how it works on the standard post. I think that for a long time had been an area of confusion for me where if you wanted to change the typography options or color options in the global styles, the interface was just structured completely differently to how it is structured when you just select a paragraph block, for example, in the standard editor. This is unifying those two experiences to be alike and that just lifts a whole bunch of cognitive load that you have to think about and just makes it work the same way in both of those areas.</p>



<p><em>Birgit Pauli-Haack</em>: Excellent. In the same way, there is now a details block. We talked about it on the show before. That is in experiments and it now has been enhanced to be able to use InnerBlocks in the details of the spoiler alert block. I call it spoiler alert because the detailed summary that&#8217;s as broad idea that some people don&#8217;t know what we&#8217;re talking about, but you have a sentence or just a headline, and then you get an arrow and then it reveals additional content. You can use it to talk about spoilers in your book review or in your film review or you can hide details that only a certain amount of readers will need about a technical thing or so. In the earlier versions, you only could add a paragraph to those details or only paragraph blocks and now you can add images, you can add quotes and all that. So this is definitely an enrichment of the details block. Also an experiment though.</p>



<p><em>Fabian Kägy</em>: That is really something &#8230; I know I have been involved with those conversations of the details block for way too long already, but I&#8217;m really looking forward to getting the community feedback of just what&#8217;s available there. It&#8217;s a very difficult thing because the detailed summary is essentially an accordion, but there are some accessibility issues that make it not the best use case for an accordion. So with these changes, just I&#8217;m interested in the feedback of the community of how they&#8217;re able to use all of the design tools to make it function the way they want to or whether there are struggles because this changes a little bit of what was there before and there were some more design options that you had with that earlier approach, but it also was a little less intuitive because it had more levels of nesting and the summary element was its own block and was just more complicated, and this is a much simpler implementation of that block. Also, it therefore removes some of the options that you have available. I&#8217;m really interested to see how that plays out and what people will think about it.</p>



<p><em>Birgit Pauli-Haack</em>: Many, many, almost all block collections that came out when the block editor first was released had an accordion block in there. A lot of people liked it for FAQs and for how-tos and all that, but it was interesting, I really didn&#8217;t really know why there wasn&#8217;t an accordion block in core until I read through the discussions about the details and summary. Some people will make it work as an accordion, but what the accordion does, it knows about the other block. So you have an accordion. The first is the tab on top and then you have details and then you have another tab and then the details and each accordion knows about the other one being open or not open. That&#8217;s very hard to replicate in a model way how the block editor works.&nbsp;</p>



<p>I tested the details in summary block that&#8217;s in the experiment right now with 15.8 and I didn&#8217;t find it particularly easy to navigate because it had some hiccups. I don&#8217;t know how to get out of it. Normally, if you have a list block, when you hit enter twice, you&#8217;re out of it and then you can add additional blocks to it. There are no visual cues when you are in the block writing or adding additional blocks. There are no visual cues, are you still in the details section or are you not? The summary, there is no way to get from the summary to the details block per keyboard. You need to change controls on it.&nbsp;</p>



<p>So there are a few things, but that&#8217;s why it&#8217;s behind the experimental flag and not yet completely released. So do as a favor and enable that test, that experiment so you can also test it. As Fabian said, community input is wanted and necessary.&nbsp;</p>



<p><em>Fabian Kägy</em>: Next up, there is another addition to the site editor and that is in the main sidebar of the site editor. There now is a new menu item called Pages that allows you to view the 10 most latest edited pages of your site and directly jump in and edit them. That is one step of actually making content editing in the site editor more possible. Again, that was one of the features that was there in earlier revisions of the site editor but then got taken out before it got released in I believe it was 6.1. These are explorations of slowly adding that content editability back into the site editor. It&#8217;s really interesting to see how that works. It is so difficult how to best communicate with the user when you&#8217;re editing parts of a template versus when you&#8217;re editing parts of the actual content of a page.&nbsp;</p>



<p>I think that that will still be the most difficult issue to solve for here, but this is slowly introducing that back into the site editor and it is really cool to see just having all of those things in there.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Look at the menu item on the left-hand side, as other people say the dark side of the site editor, but it&#8217;s there. So the next item or feature that got introduced makes Fabian really, really happy and it&#8217;s the introduction of the plugin template settings panel slot, which means on the sidebar, there is now a way for plugin developers to extend the feature set that&#8217;s displayed to the user. Have you tried it out yet? Have you looked at that feature?</p>



<p><em>Fabian Kägy</em>: I&#8217;ve not yet had a chance to play with it, but yeah, more slots and more places for extenders to add to the experience and showcase custom settings and those types of things always make me happy, especially when they&#8217;re done right, and this seems pretty cool.&nbsp;</p>



<p>Next up, we have an update that is very useful for extenders again. It consolidates and adds some more documentations to the storybook. If you&#8217;re not familiar with the storybook, that is actually something when you go to the GitHub repository of the Gutenberg plugin, in the right-hand sidebar there is, I think it&#8217;s called pages or deployments. You can actually jump to that storybook right from GitHub and view it. The storybook essentially is showcasing all of the various React components that were built as part of the Gutenberg plugin and are available in WordPress core and is showing live previews of them with some controls. You can tweak some of the settings right there visually and also have some of the documentation there. This consolidates and changes a little bit of just how that is structured and how that appears. Just in general, the storybook that has been there for a long time is a super valuable and great tool and it&#8217;s always nice to see additional enhancements for that.</p>



<p><em>Birgit Pauli-Haack</em>: I definitely want to point that out that at WordCamp Asia, I heard from a few people that were at the contributor day and working with the core editor table there, they were really surprised that many developers that came and wanted to work on things did not know about the storybook. I think we have not done a good job in explaining what it is and pointing people to it. I think it&#8217;s part of the documentation that is in the components, but it&#8217;s not referred to &#8230; Most of the time, it&#8217;s not referred to in the documentation on the developer site in the block editor handbook. We are going to change that a little bit and add more links to the storybook for the various components because it&#8217;s such a rich developer experience where you can change things and then you click on a button and it gives you the code for it for the changes that you made and you can immediately reuse it in your own code base. Definitely, I take any chance when I can talk about the storybook now.</p>



<p>The next part is a feature for the block editor that is talking about the dimension controls and it&#8217;s not always visible. So now, it&#8217;s an attempt to show all the dimensions control at the beginning and not hide them so much where you had to open them and then decide do you want to see the padding, do you want to see the margin. It&#8217;s now easily available so you don&#8217;t have to look for it, what padding and margins is, because we all talk about padding and margins, but we never talk about dimension controls. So when the words appear on the screen, you don&#8217;t as easily recognize that that&#8217;s what you&#8217;re talking about.</p>



<p><em>Fabian Kägy</em>: This, again, is also something where it is just difficult and interesting. The vertical space that we have available in the sidebar is very limited and it&#8217;s always an interesting balance to strike of how much do we show by default versus how much do we hide behind the setting so it&#8217;s not overwhelming for somebody that is new to the editor, but also makes it discoverable for somebody. So it is not changing any of the features that are available, but it is trying to show some more by default. I&#8217;m very interested to see how folks will react to that, whether it feels overwhelming or whether it makes it more approachable. The only real way to find that out is by actually testing that. So I&#8217;m glad to see those explorations happening in the plugin.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: It might go away again or will be tweaked later on. So your comments are certainly wanted and necessary. We share in the show notes the release post for 15.7, the release post for 15.8. By the time you listen to this, Fabian will have published it, and I&#8217;m sure also, Sarah Gooding will talk about both releases or already has on 15.7 and 15.8.&nbsp;</p>



<h3 class="wp-block-heading"><strong>What’s in Active Development or Discussed</strong></h3>



<p>or I just wanted to at the end of it &#8230; So those were all the releases and we are now talking about what&#8217;s in active development or discussed. We have right now the largest number of experiments in the block editor since the beginning. I think there are now seven experiments hiding on the experiments page for the plugin. So let&#8217;s talk about them. Some of them we already talked about. So it starts out with a zoomed out view and it&#8217;s test a new zoomed out view on the site editor. So I&#8217;m reading from the page now and it also has a warning attached to it, &#8220;The new feature is not ready. You may experience UX issues that are being addressed.&#8221; UX means user experience, just to clarify that. Did you test that before?</p>



<p><em>Fabian Kägy</em>: Yeah. So the zoomed out view essentially means that you can more quickly navigate through or get a more holistic view of your page and not appearing in the same size as you would always see it, but instead, it zooms out and shows you more of your entire page smaller in the canvas. That is very useful when you want to make changes to your global styles and just want to see how it affects your site more holistically or when you tweak those things. Especially when you switch between block theme variations, that is just useful to see how it will not just affect that very small area of the site that you see in your viewport, but instead see it more broadly for an entire page.&nbsp;</p>



<p>So I think this is a great thing to work on. Right now, as the warning says, there are some issues that are being worked on. Especially for working with global styles, having that more zoomed out view is very useful.</p>



<p><em>Birgit Pauli-Haack</em>: So if you tested it and you have an idea how to make it better, definitely air those on GitHub and filing an issue of that. So the second one, it says color randomizer, test the global styles color randomizer, a utility that lets you mix the current color palette pseudo- randomly. I think it&#8217;s one of those features where it said, &#8220;Okay. It&#8217;s cool to have and cool to test things out, but it&#8217;s not something that a lot of people would think they needed.&#8221; Do you have any thoughts on it?&nbsp;</p>



<p><em>Fabian Kägy</em>: It is one of those features where from my perspective as somebody who works a lot in the large agency space, that is not a feature I would&#8217;ve ever come up with, but I can see how, especially if you&#8217;re somebody who&#8217;s just playing around in the editor trying to build a new design, it can be a useful partner to give you some inspiration of maybe you&#8217;re not the best with color theory and coming up with an accessible color palette yourself, and that can be a great way to get some inspiration for just showing you different variations of what your site could look like with different colors and spark some of that imagination, but it is one of those features that I know for a client site that has a design guide with strict color I would want to disable that feature and would not want to expose certain clients to that feature. So it&#8217;s definitely one of those where I can see it being useful for some, but also rather distracting for others. So I&#8217;m interested to see how that will actually get rolled out.</p>



<p><em>Birgit Pauli-Haack</em>: It might also be part of the explorations, but the design team does in figuring out is there a way to include different palettes that are on third-party sites that can come in and you can choose from, but I think it&#8217;s not a high priority right now for the team. That&#8217;s why it&#8217;s all still in the experimental phase and it hasn&#8217;t gone that route yet. I heard Matt Mullenweg and one of his state of the word talking about making color palettes that are out in the universe interesting, available to site builders or site owners in some way or shape.&nbsp;</p>



<p>The third test item on the page is the command center, a test of command center, open it up using command K in the site of post editor. We talked about it. I don&#8217;t think we need to elaborate some more, but that&#8217;s where you find it.&nbsp;</p>



<p>The fourth one is the grid variation for a group block, test the grid layout type as a new variation for the group block. Right now, that only works on the site editor because it&#8217;s actually a template or site design approach to the grid. Grid, it&#8217;s actually a CSS feature. So this tries to explore how you can make templates that adhere to a certain grid layout, but I&#8217;m not as knowledgeable about design to be able to use that. I think I need a little pre-beginner&#8217;s tutorial for that.&nbsp;</p>



<p><em>Fabian Kägy</em>: It is. I am really happy to see this exploration being done right now. In the last couple of years, we got that row and stack variation of the group block, which essentially as a developer, that is my flex box. Flex box allows you to layout content in one direction, so either horizontally, the row, or vertically with the stack. The grid, you can achieve some of those grid layouts with the columns block, but the columns block, it is very difficult for it to wrap around. So if you wanted to, let&#8217;s say, have a three column grid that is not just one free column layout, but instead has two rows of those two columns, that is not really or is technically possible, but it is not ideal. That is where grid layouts come into play and are, I think, so much more powerful.</p>



<p>I think there also is an exploration that is not listed here of adding an actual grid layout or using CSS grid layout for the grid in the query block. We weren&#8217;t able to use grid when the editor first came out because it was too new of a CSS feature and we needed to support more older browsers, but that browser support has changed so much in the last couple of years that we&#8217;re now able to use grid in the editor. It just opens up so many new design possibilities and makes it so much easier.&nbsp;</p>



<p>I&#8217;ll say on the custom development side, grid block is one of the first things that we build on one or a grid block is one of the first things we build on many custom sites because it is just much more powerful than the columns block and also easier to use in a way. So I&#8217;m excited for these explorations.&nbsp;</p>



<p>I will say though, a couple of releases ago, the group block changed to show that variation picker when you first insert it where you have to pick between the variations. I&#8217;m not yet sure I&#8217;m in love with that approach of &#8230; I like the various variations of the group block, but when I add a new group, it always pauses me a little too much because I need to step back and, &#8220;Hey, I just want to start with a default grid or a default group and then continue with it.&#8221; So I&#8217;m happy for more of these variations of the group block and for more of those layout controls. I&#8217;m not quite sure we have found the best way to expose them.</p>



<p><em>Birgit Pauli-Haack</em>: I hear you. Making the decision to use a group block now becomes also a decision of what kind of flow you want and you are not there yet. When you get the group block, I understand that, but I&#8217;m also excited for the grid layout in terms of it is a feature that was requested quite a bit in the early days of the block editor layout site editing things, and it&#8217;s still missing. So now, certain plug-ins and block collections and theme collections have stepped in and allowed that already. So core is a little bit behind on that, but of course, core has a different outlook for the site editor than plugin developers have.&nbsp;</p>



<p>The fifth experiment in the experiments page is the details block with the detailed summary block. We talked about it. It&#8217;s there for you to test out.</p>



<p>The sixth one is the block theme previews, and it enables block theme previews. That&#8217;s not much of an explanation, but what it allows you is on your site &#8230; So the customizer had the live preview of themes that were already installed on your site so you can see how your site would need to change to when a theme would be activated. It&#8217;s more a decision making tool rather than a good design tool.&nbsp;</p>



<p>So with many, many block themes coming online, we are now beyond 300 in the directory. I think the largest number is 306. I think it helps with the decision if you want to change your theme out to have a better preview, and the customers that preview doesn&#8217;t work with it. This is the first iteration. I ran that through themes through the preview and it was a great experience, so much better than the original one to review certain parts of an existing site.</p>



<p>It also revealed that not all block themes are alike. There are significant differences, and having a tool to actually explore those differences or even notice them is invaluable, definitely. Not every theme behaves with this live preview feature in it, so if you are working on themes and either you have a starting theme in an agency or you use a collection of themes to build your sites to choose from, you might want to test them with this theme preview so you can turn on and off features and showcase a few things that are available in the preview.&nbsp;</p>



<p>Also, please, please comment on the issues or file issues on GitHub after your tests. I already found one that when I look for style variation and I want to see how a page changed the style variation, I don&#8217;t have a way to do this because the page that is linked, the link doesn&#8217;t go to the preview, it goes to the page in the template editor, and all of a sudden, I&#8217;m out of my mindset on a preview, but all of a sudden it gets me into the editor. So that&#8217;s common for things that are in testing, but it also needs to be pointed out that that&#8217;s a major stumbling point for someone who uses the feature for the first time.&nbsp;</p>



<p>The last one of the tests has just come in. It&#8217;s a navigation block that uses the still in Experiment interactivity API, and I have not used it. Did you look at that, Fabian?</p>



<p><em>Fabian Kägy</em>: I looked at it briefly, but the summary of it is if you&#8217;re using it and you notice a difference that worked before, there&#8217;s a bug because this essentially swaps out the engine, but you should notice it as an end user. It changes how the front end JavaScript of the site works to use that interactivity API, but instead of some custom JavaScript that was purposefully written for this, using that interactivity API to make it more declarative, but as an end user, toggling that setting should not change anything about it works. Yeah, it may produce the actual bundle size, therefore make your site a little bit faster, but usability wise, there should be no difference and there should be full-on feature parity with how the navigation works today before or after you switch that setting.</p>



<p><em>Birgit Pauli-Haack</em>: Good to know. So if you don&#8217;t notice anything, it&#8217;s okay. Excellent. So this brings us to the end of the show today. Well, I think we talked a lot about all the new things that come to block editor and to WordPress. Thank you so much for joining me today. Fabian, is there anything that you want our listeners to know about the block editor, about WordPress, about 10up? Now is the chance to talk about it and we&#8217;ll add links to the show notes. I just wanted to say about 10up, you have a wonderful educational site about the block editor with quite a few white papers and tutorials. How did that come about? Is it your work or…?</p>



<p><em>Fabian Kägy</em>: Yeah. The <a href="https://gutenberg.10up.com/">gutenberg.10up.com</a> website, our block editor best practice site has been my baby for the last year and a half or so, where I got to spend a lot of time actually writing down how we as an agency approach working with the block editor and setting up the best practices for how to do that in the agency setting for that special type of client. Whereas the main documentation of core is more geared to end users, which is the right thing, but because of that, we decided that there is space for an additional resource to focus on the things that are important for those very curated experience for big clients and so forth.&nbsp;</p>



<p>So that is one thing that I would mention, just taking a look at that <a href="https://gutenberg.10up.com/">gutenberg.10up.com</a> website, and if you have any feedback on that, feel free to reach out anywhere on the Make Slack or on Twitter or Masévon or Blue Sky or wherever you can find me pretty much always talking about block editor stuff.&nbsp;</p>



<p>Then the other thing that I will just mention is the 10up block components NPM package, which is my passion project and has been for the last three years or so, which essentially is a collection of React components that work like all of the WordPress packages, the WordPress components, WordPress block editor components. It is a collection of additional components that are adding sometimes very complex, sometimes easy functionality for you to build. If you build custom blocks, making that a whole lot easier so you have to write less code and know that it&#8217;s tested and is working with the way that it should, and doing that in a way that feels 100% like it is just core WordPress. I&#8217;m very happy and proud of that project. If you find it useful or if you have questions or feedback about that, always happy to chat.</p>



<p><em>Birgit Pauli-Haack</em>: Well, thank you so much. There&#8217;s some great resources. You mentioned custom blocks. There has been discussion around static block with this dynamic blocks. Where do you land?</p>



<p><em>Fabian Kägy</em>: The way I think about it, if I&#8217;m building a plugin that is meant for the official directory where I as a developer do not have access to the site where the code is running on, I would go with a static block unless I need to show dynamic data. If I as the developer can access and have maintenance over the site I built dynamic blocks, and that means in the agency context where we&#8217;re often changing designs, making quick iterations, we are, for the most part, only building dynamic blocks because of that because we cannot spend the time to deal with deprecations and all of those things.&nbsp;</p>



<p>It really comes down to that where if you have &#8230; The thing that you should ask yourself is, &#8220;What should happen when I need to change something about this block on a code level? Should all of the old instances that maybe were published three years ago, should they also get those updates automatically or should I not &#8230; Should that historical content stay untouched and just stay the way that it was?&#8221; If it should stay in touch, static blocks is your right answer. That is the way to go. If it should update in all instances or if you need to modify the block structure very often and have access to the maintenance there, dynamic blocks are much easier to deal with and are &#8230; So I&#8217;m coming down most of the time on the dynamic side.</p>



<p><em>Birgit Pauli-Haack</em>: Dynamic blocks side. All right. So well, thank you for answering these quick questions and having some insight in how you work as a longtime block editor adopter and in the agencies. It was a great pleasure talking to you, Fabian. We will share all the links that you mentioned, of course, in the show notes. Before we end the show, oh, what&#8217;s your Twitter handle, Fabian?</p>



<p><em>Fabian Kägy</em>: My full name spelled out, so F-A-B-I-A-N-K-A-E-G-Y, just all spelled together. You should be able to search for it and it should come up.</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s just for the people who don&#8217;t go through the show notes. We, of course, have all the links in the show notes. As always, the show notes will be published on gutenbergtimes.com/podcast. This is episode 83. If you have questions, suggestions, and news that you want us to include in the next show, please send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. That&#8217;s c<a href="mailto:hangelog@gutenbergtimes.com">hangelog@gutenbergtimes.com</a>. Thank you all for listening. Thank you for being here, Fabian. This is goodbye and I wish you a wonderful weekend.</p>



<p><em>Fabian Kägy</em>: Thank you so much for having me.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 21 May 2023 08:18:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:19:"Gutenberg Changelog";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:93:"WPTavern: WordPress 6.2.2 Restores Shortcode Support in Block Templates, Fixes Security Issue";s:7:"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=145264";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:103:"https://wptavern.com/wordpress-6-2-2-restores-shortcode-support-in-block-templates-fixes-security-issue";s: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:1594:"<p><a href="https://wordpress.org/news/2023/05/wordpress-6-2-2-security-release/">WordPress 6.2.2</a> was released early this morning as a rapid follow-up to 6.2.1, which introduced a bug that <a href="https://wptavern.com/wordpress-6-2-1-update-breaks-shortcode-support-in-block-templates">broke shortcode support in block templates</a>. Version 6.2.1 was also an important security release, but due to the catastrophic breakage for those using shortcodes in block templates, some users were implementing insecure workarounds or simply downgrading to 6.2 to keep critical functionality working on their websites.</p>



<p>WordPress contributors worked quickly over the weekend to ensure that users can now update to 6.2.2 with their shortcodes intact. The release post identified the removal of shortcode support in the previous release as &#8220;a regression&#8221; and a bug. This is an important recognition, as shortcodes are still a tool that users frequently rely on to insert functionality from plugins that haven&#8217;t made it available as a block, as well as a necessity for things that won&#8217;t work without inline shortcodes.  </p>



<p>Version 6.2.2 is also a security release, as core contributor Jonathan Desrosiers said that the issue patched in 6.2.1 &#8220;needed further hardening&#8221; in this update.</p>



<p>Users are advised to update immediately and automatic updates are rolling out. Many reported having turned automatic background updates off for core after 6.2.1 broke their websites. Users who did so will need to manually update as soon as possible. </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, 20 May 2023 21:38:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:118:"Gutenberg Times: WordPress 6.3 roadmap and release squad, WPCampus schedule, Wayfinder and more—Weekend Edition #254";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=24143";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:124:"https://gutenbergtimes.com/wordpress-6-3-roadmap-and-release-squad-wpcampus-schedule-wayfinder-and-more-weekend-edition-254/";s: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:24412:"<p>Howdy, </p>



<p>Hubby and I are almost settled in our new apartment, except we are still missing our furniture. They are scheduled to arrive on June 1, which would make it exactly 74 days, since they all got packed up in Sarasota. Yesterday we measured all the rooms, so we can decide where we can place the big items, and how to organize our offices. So, when I write &#8220;settled&#8221;, I mean getting accustomed to living in our neighborhood, organizing our infrastructure of daily life and using all the transportation choices, rather than being settled in the apartment. </p>



<p>WordCamp Europe is coming up fast. There are a ton of Gutenberg talks on the roster this year. <a href="https://gutenbergtimes.com/wordcamp-europe-2023-block-editor-talks-meet-greet-contributor-day-and-more/">I collected them all in a separate post.</a> And if you are going in person, make sure we connect and have a chat. You can <a href="https://twitter.com/bph">DM me on Twitter</a>, s<a href="mailto:pauli@gutenbergtimes.com">end an email </a>or just pick a <a href="https://calendly.com/pauli-haack/wordcamp-europe?month=2023-06">slot from the public calendar.</a> </p>



<p>I am excited about exploring the city a couple of days prior to Contributor Day. </p>



<p>This Weekend edition is again full of updates on the open-source projects, tutorials, and videos. Hope y&#8217;all enjoy it. </p>



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



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




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



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





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

	
	<div class="ngl-articles-wrap ngl-articles-webview">
	
						
			<div class="ngl-article-mobile">
				<table width="100%" border="0" cellpadding="0" cellspacing="0">
					<tr>
						<td valign="top">
							<div class="ngl-article-mob-wrap">
							<div class="ngl-article-featured"><a href="https://gutenbergtimes.com/wordcamp-europe-2023-block-editor-talks-meet-greet-contributor-day-and-more/" target="_self" rel=""><img src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2023/05/Guiseppe-Milo-Athens-Greece-web.jpg?w=652&ssl=1" /></a></div><div class="ngl-article-title"><a href="https://gutenbergtimes.com/wordcamp-europe-2023-block-editor-talks-meet-greet-contributor-day-and-more/" target="_self" rel=""><span>WordCamp Europe 2023 &#8211; Block editor talks, meet &#038; greet, Contributor Day and more</span></a></div><div class="ngl-article-excerpt">WordCamp Europe is less than four weeks away, the speakers and sessions have been announced, and the schedule is now available. Time to make plans. <a href="https://gutenbergtimes.com/wordcamp-europe-2023-block-editor-talks-meet-greet-contributor-day-and-more/" class="ngl-article-read-more" target="_self">Read more.</a></div>							</div>
						</td>
					</tr>
				</table>
			</div>
			
			
			

		
		
		</div>

</div>




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



<p><a href="https://make.wordpress.org/core/2023/05/18/roadmap-to-6-3/"><strong>The Roadmap for the WordPress 6.3 release</strong></a> has been published. Anne McCarthy identified three focus areas for this release: </p>



<ul>
<li>Polishing the Site Editor,</li>



<li>Iterating on blocks, </li>



<li>Expanding patterns</li>



<li>Stabilizing usability and prioritizing refinement,</li>



<li>Enhancing design tools,</li>



<li>Leveling up APIs,</li>



<li>Addressing&nbsp;PHP&nbsp;items (8.x compatibility), and </li>



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



<p>For each focus area, she described the scope and listed GitHub issues and PRs of the work in progress. </p>



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



<p>On the heals for the Roadmap, <strong>Hector Prieto</strong> published an update on the <a href="https://make.wordpress.org/core/2023/05/18/wordpress-6-3-planning-roundup/"><strong>WordPress 6.3 Planning Roundup</strong></a>, confirming the release scheduled as it was proposed earlier and announcing Matias Ventura as the release lead and all other members of the release squad. </p>



<ul>
<li>Beta 1 will be on June 27, 2023</li>



<li>Release Candidate 1 + Dev Notes are scheduled for July 18th, 2023</li>



<li>General release aimed for August 8th, 2023. </li>
</ul>



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



<p>During the latest Hallway Hangout, contributors discussed what is in the works for the Site Editor and what can be expected for WordPress 6.3. Anne McCarty posted a summary and shared the video recording in <strong> <a href="https://make.wordpress.org/test/2023/05/11/hallway-hangout-lets-chat-about-the-site-editor-6-3/">Hallway Hangout: Let’s chat about the Site Editor &amp; 6.3</a></strong>. </p>



<p><strong>The next Hallway Hangout is scheduled for May 25, 2023 &#8211; 17:00 UTC. Nick Diego and Justin Tadlock will be discussing <a href="https://make.wordpress.org/themes/2023/05/18/hallway-hangout-curating-the-editor-and-building-block-themes-for-clients/">Curating the editor and building block themes for clients</a>. </strong>Don&#8217;t miss it. <a href="https://www.meetup.com/learn-wordpress-online-workshops/events/293612715/">RSVP via Meetup.com</a></p>



<a href="https://www.meetup.com/learn-wordpress-online-workshops/events/293612715/"><img /></a>



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



<p>In his <a href="https://make.wordpress.org/design/2023/05/08/design-share-apr-24-may-5/"><strong>Design Share: Apr 24–May 5</strong></a>, Joen Asmussen shared what the WordPress design team has been working on the last two weeks. He lists quite a few avenues with their respective GitHub PR/Issue links, so you can follow along and chime in. </p>



<ul>
<li>Document title &#8211; as part of the re-introduction content editing to the site editor, a short video shows the switch in the UI for either editing the template or the single page, that is using the template</li>



<li>Revision History Management &#8211; explores a potential future side by side page comparison</li>



<li>Vertical Text as a new design tool introduced to certain blocks</li>



<li>Featured Image improvements &#8211; show a more compact and streamlined interface to handle feature images settings</li>
</ul>



<img />



<p><strong>Justin Tadlock</strong> published the monthly roundup <a href="https://developer.wordpress.org/news/2023/05/whats-new-for-developers-may-2023/"><strong>What’s new for developers? (May 2023)</strong></a> on the developer blog. It&#8217;s again full of focused notes about changes in the WordPress worlds relevant for extenders, plugin and theme builders and agency or freelance developers building sites for others.  </p>



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



<p><strong>Anne McCarthy </strong>published the next <strong><a href="https://make.wordpress.org/test/2023/05/18/fse-program-testing-call-23-rapid-revamp/">FSE Program Testing Call #23: Rapid Revamp</a>.</strong> &#8220;With the&nbsp;<a href="https://make.wordpress.org/core/2023/05/18/roadmap-to-6-3/">roadmap to 6.3 published</a>&nbsp;and another version of&nbsp;Gutenberg&nbsp;out in the wild, it’s time to test some of the upcoming features that are in the works to upgrade and polish the experience of using the Site Editor:&#8221; she wrote and listed all eight of them. </p>



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



<p>Led by <strong>Fabian Kägy</strong>, <strong>Gutenberg 15.8</strong> was released on May 18th, 2023. The number of PRs merged for this release was considerably higher than for 15.7 and it&#8217;s expected to rise with the urgency of the upcoming WordPress 6.3 release. There are only three Gutenberg plugins releases left until Beta 1 on June 27. </p>



<ul>
<li>15.9 scheduled for May 31</li>



<li>16.0 to be released on Jun 14 (after WordCamp Europe) </li>



<li>16.1 RC 1 to be release on June 21</li>
</ul>



<p>In his release post <a href="https://make.wordpress.org/core/2023/05/20/whats-new-in-gutenberg-15-8-may-17/">What’s new in Gutenberg 15.8? (May 17)</a>, Kägy highlight three new features that need testing from Gutenberg plugin users: </p>



<ul>
<li><a href="https://make.wordpress.org/core/2023/05/17/whats-new-in-gutenberg-15-8-may-17/#add-the-pages-menu-to-the-site-editor-50463">Add the pages menu to the site editor</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/17/whats-new-in-gutenberg-15-8-may-17/#add-revisions-ui-50089">Add revisions UI to the global styles interface</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/17/whats-new-in-gutenberg-15-8-may-17/#add-theme-previews-for-block-themes-50030">Add Theme Previews for block themes</a></li>



<li>One feature is now still listed in experiments. It will come out next Gutenberg plugin release: The Command Center AKA Wayfinder. (See Riad Benguella&#8217;s post. )</li>
</ul>



<p>It&#8217;s always a great pleasure to connect with <strong>Fabian Kägy</strong>. We had a great time geeking out over the blog editor while recording episode 83 of the Gutenberg Changelog. We discussed Gutenberg 15.7, 15.8 the feature available on the Experiments page and 6.2.1, Gutenberg Storybook and 10up tools. The episode  is at the editor now, and it will arrive in your favorite podcast app over the weekend. </p>



<img />



<div class="wp-block-group has-light-background-background-color has-background is-layout-flow wp-block-group-is-layout-flow"><div class="wp-block-group__inner-container">
<p><strong>🎙️ </strong> New episode:  <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-83-wordpress-gutenberg-experiments/">Gutenberg Changelog #83 – WordPress 6.2.1, Gutenberg 15.7, 15.8 and experiments</a> with special guest, Fabian Kägy and host Birgit Pauli-Haack</p>
</div></div>



<p><strong><a href="https://twitter.com/riadbenguella">Riad Benguella</a></strong> published the post <a href="https://make.wordpress.org/core/2023/05/17/command-center-request-for-feedback/"><strong>C</strong></a><strong><a href="https://make.wordpress.org/core/2023/05/17/command-center-request-for-feedback/">ommand Center: Request for feedback</a> </strong>asking for testing and review of a new feature that will come out of the experimental phase for Gutenberg 15.9, for now called the Command Center, and the Marketing team is probably recommending a new name: The<strong> Wayfinder. </strong></p>



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



<p><strong>Caroline Nymark</strong> published an <a href="https://fullsiteediting.com/site-creators/introduction-to-the-site-editor/"><strong>Introduction to the Site Editor for creators</strong>.</a> This tutorial is meant for Beginners and no-code creators and covers everything available since WordPress 6.2 and Gutenberg 15.7. Although it&#8217;s title Introduction, it is quite comprehensive and covers the Site Editor, Navigation, Styles, Templates and Template parts. Then she dives deeper into the Design Tools via the Styles menu item. You will be creating or modifying themes in no time! </p>



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



<p><a href="https://wordpress.org/plugins/maxi-blocks/"><strong>Maxi Blocks</strong></a> – a template library for site builders using  WordPress Block editor. It came recently out of beta and offers developers a whole range of design tools in an interface that has been built on top of Gutenberg, yet using custom components to offer additional design features. The plugin comes with hundreds of icons, patterns, templates and sixteen custom blocks. The Pro version is available at <a href="https://maxiblocks.com/">MaxiBlocks.com</a>. It&#8217;s meant for designers looking for all the tools, not so much for beginners or site owners. There will be a learning curve due to the additional UI components. </p>



<img />



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



<p><strong><a href="https://twitter.com/mahdiali_">MahdiAli Khanusiya</a> </strong>built the plugin<strong> </strong><a href="https://wordpress.org/plugins/patternswp/"><strong>PatternWP</strong></a> &#8211; a pattern block library for WordPress. The first version offers patterns on many categories. for the busy site owner. The plan is to be adding new patterns and templates on a consistent basis. </p>



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



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



<p>Lots of feedback has been provided during the Call for Exploration. <strong>Anne McCarthy </strong>published <a href="https://make.wordpress.org/test/2023/05/04/fse-program-build-a-block-theme-summary/"><strong>FSE Program Build a Block Theme Summary</strong></a>. The TL;DR: &#8220;Using the Site Editor alongside the Create Block Theme plugin supercharges the experience, mainly by filling in gaps around font management and offering more nuanced creating/exporting options. With these added features, the Site Editor is both left to shine as a theme building tool and the current known pain points impacting regular site building come to the surface, like needing more clarity around where layers of styles are coming from. In general, feedback fell into three categories: Create Block Theme plugin pain points, missing options in the Site Editor (font management, synced patterns, desire for more styling options with certain blocks), and UX considerations for the Site Editor that match the site building experience. &#8221; she wrote. The videos shared from the contributors are certainly eye-opening. </p>



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



<p><strong><a href="https://twitter.com/mikemcalister">Mike McAlister</a></strong> explains in his article how <a href="https://olliewp.com/a-native-and-iterative-approach-to-responsive-control-in-wordress/"><strong>a native and iterative approach to responsive control in WordPress</strong></a> could bridge the gap between the goals to rely on <a href="https://developer.wordpress.org/news/2023/02/intrinsic-design-theming-and-rethinking-how-to-design-with-wordpress/">i<em>ntrinsic design</em></a> and still be able to handle edge cases for viewpoint-driven responsiveness of a site. </p>



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



<p>In his video, <a href="https://www.youtube.com/watch?v=Zh0ANsYgoN0"><strong>WordPress Gutenberg Product Manager explains what&#8217;s next for Responsive Websites and Block Themes</strong></a>,  <strong>Jamie Marsland</strong> interviewed <strong>Rich Tabor</strong> on intrinsic design, what a theme product might look like for theme creators and what the next wave of block building inspiration might arrive at the WordPress shores. </p>



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



<p><strong><a href="https://twitter.com/jkoussertari">James Koussertari</a></strong> explained <a href="https://gutenbergmarket.com/news/using-layout-sizes-in-themejson"><strong>Using Layout Sizes in theme.json</strong></a>. &#8220;The layout setting in theme.json is great for developers, as they can set default container sizes for their design system, easily in one place. It also means that content editors do not have to think about which container sizes to set manually each time they add a block.&#8221; he wrote on the blog of the Gutenberg Market</p>



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



<p>The latest call for testing ended last week, too and <strong>Anne McCarthy</strong> recounts the feedback: <a href="https://make.wordpress.org/test/2023/05/11/fse-program-front-page-fun-summary/"><strong>FSE Program Front Page Fun Summary</strong></a>. The high-level feedback revealed: &#8220;In general, the call for testing was relatively tame bug wise, with only a few obvious ones found, mainly in the Navigation block. The usability feedback related to many ongoing projects in the Site Editor underscoring the impact of solving these consistent problems, in particular the clarification of the content &lt;> template relationship and confusion around the overall experience of managing pieces of navigation. &#8221; and &#8220;While the new Grid layout type was the primary focus of the testing call, feedback on it was limited to suggestions for consolidating the various options between the grid layout, Columns block, Gallery block, and Table block.&#8221; McCarthy wrote. </p>




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




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



<p><strong><a href="https://twitter.com/3LPU4S">Alfredo Navas</a></strong>, WebDevStudios was <a href="https://webdevstudios.com/2023/05/16/query-loop-block/"><strong>Having Fun with Query Loop Block</strong></a> and published a post to tell you all about it. He takes you along to explore the usefulness of the Query Loop block and learn how to extend its capabilities.</p>



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



<p>In his latest post for the Developer Blog, <strong>Michael Burridge</strong> created a tutorial on  <a href="https://developer.wordpress.org/news/2023/05/useentityrecords-an-easier-way-to-fetch-wordpress-data/"><strong>useEntityRecords: an easier way to fetch WordPress data</strong></a>. If you have simple data fetching requirements and don’t need additional customization or resolution checks, the <code>useEntityRecords</code> function can be a straightforward choice. Burridge shows  how it simplifies data handling in contrast to useSelect + getEntityRecords. </p>



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



<p>Don&#8217;t miss next week&#8217;s <strong>Developer Hours</strong> about the new WordPress tool called Playground. <strong>Adam Zieliński</strong> will introduce the app and demo some great use cases for it. There are two events, so all timezones get a chance to participate live. </p>



<ul>
<li><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/293196462/">May 23, 2023, at 17:00 UTC (11 am EDT)</a></li>



<li><a href="https://www.meetup.com/learn-wordpress-online-workshops/events/293196452/">May 24, 2023, at 8 am UTC </a></li>
</ul>



<img />



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



<p><strong>WPCampus </strong>will take place from July 12 to the 14th, 2023 in New Orleans. The organizing team released their <a href="https://2023.wpcampus.org/schedule/">schedule.</a> WPCampus 2023 is a hybrid event. <strong><a href="https://2023.wpcampus.org/tickets/">Join in-person or online</a>.</strong></p>



<p>I spotted Nick Diego on the roster with his 3-hour Workshop: <a href="https://2023.wpcampus.org/schedule/workshops/modern-wordpress-building-techniques-full-site-editing-in-higher-ed/"><strong>Modern WordPress Building Techniques: Full Site Editing in Higher Ed</strong></a>. </p>



<p>But there is more: </p>



<ul>
<li>Daniel Tyger and Tom O&#8217;Donnell from the University of Maine will share their Journey <a href="https://2023.wpcampus.org/schedule/from-classic-to-blocks-in-90-days/"><strong>From Classic to Blocks in 90 Days</strong></a>?</li>



<li>Joni Halabi will present on <a href="https://2023.wpcampus.org/schedule/make-it-your-own-integrating-twig-templates-with-your-wordpress-block-theme/"><strong>Make it your own: Integrating Twig templates with your WordPress block theme</strong></a></li>



<li><a href="https://2023.wpcampus.org/schedule/development-of-a-no-code-theme-for-teaching-full-site-editing-to-beginning-wordpress-students/"><strong>Development of a No-Code Theme for Teaching Full Site Editing to Beginning WordPress Students</strong></a> with Drake Gómez</li>



<li><a href="https://2023.wpcampus.org/schedule/destination-full-site-editing-all-the-steps-monmouth-university-took-to-prepare-the-future-of-wordpress/"><strong>Destination Full-Site Editing: All the Steps Monmouth University Took to Prepare the Future of WordPress</strong></a> with <strong>Steve Graboski</strong></li>



<li><a href="https://2023.wpcampus.org/schedule/55330/"><strong>Developing a design system within the block editor</strong></a> with <strong>Nick Novak</strong></li>



<li></li>
</ul>




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



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




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



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



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




<p>Featured Image: Colorful Duplo blocks by Maruska, <a href="https://wordpress.org/photos/photo/2206266bbc/">found on WordPress Photos site.</a></p>



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



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



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



<hr class="wp-block-separator has-css-opacity is-style-wide" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 20 May 2023 13:00:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Birgit Pauli-Haack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:52:"WordPress.org blog: WordPress 6.2.2 Security Release";s:7:"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=14974";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"https://wordpress.org/news/2023/05/wordpress-6-2-2-security-release/";s: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:5417:"<h2 class="wp-block-heading">WordPress 6.2.2 is now available!</h2>



<p>The 6.2.2 minor release addresses <a href="https://core.trac.wordpress.org/query?milestone=6.2.2&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority">1 bug</a> and 1 security issue. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 5.9 have also been updated.</p>



<p>WordPress 6.2.2 is a rapid response release to address a regression in 6.2.1 and further patch a vulnerability addressed in 6.2.1. The next major release will be<a href="https://make.wordpress.org/core/6-3/"> version 6.3</a> planned for August 2023.</p>



<p>The update process will begin automatically if you have sites that support automatic background updates.</p>



<p>You can <a href="https://wordpress.org/wordpress-6.2.2.zip">download WordPress 6.2.2 from WordPress.org</a> or visit your WordPress Dashboard, click “Updates,” and click “Update Now.”</p>



<p>For more information on this release, please <a href="https://wordpress.org/support/wordpress-version/version-6-2-2">visit the HelpHub site</a>.</p>



<h2 class="wp-block-heading"><strong>Security updates included in this release</strong></h2>



<p>The security team would like to thank the following people for responsibly reporting vulnerabilities and allowing them to be fixed in this release.&nbsp;</p>



<ul>
<li>Block themes parsing shortcodes in user-generated data; thanks to Liam Gladdy of<a href="https://wpengine.com/"> WP Engine</a> for reporting this issue.</li>
</ul>



<p>The issue above was originally patched in the 6.2.1 release, but needed further hardening here in 6.2.2. The Core team is thankful for the community in their response to 6.2.1 and collaboration on finding the best path forward for proper resolution in 6.2.2. The folks who worked on 6.2.2 are especially appreciative for everyone’s understanding while they worked asynchronously to get this out the door as quickly as possible.</p>



<h2 class="wp-block-heading">Thank you to these WordPress contributors</h2>



<p>This release was led by <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a>.</p>



<p>WordPress 6.2.2 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver security fixes into a stable release is a testament to the power and capability of the WordPress community.</p>



<p><a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/xknown/">Alex Concha</a>, <a href="https://profiles.wordpress.org/antpb/">Anthony Burchell</a>, <a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a>, <a href="https://profiles.wordpress.org/chriscct7/">chriscct7</a>, <a href="https://profiles.wordpress.org/talldanwp/">Daniel Richards</a>, <a href="https://profiles.wordpress.org/davidbaumwald/">David Baumwald</a>, <a href="https://profiles.wordpress.org/ehtis/">Ehtisham S.</a>, <a href="https://profiles.wordpress.org/gziolo/">Greg Ziółkowski</a>, <a href="https://profiles.wordpress.org/priethor/">Héctor Prieto</a>, <a href="https://profiles.wordpress.org/isabel_brison/">Isabel Brison</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a>, <a href="https://profiles.wordpress.org/jeffpaul/">Jeffrey Paul</a>, <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a>, <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/chanthaboune/">Josepha</a>, <a href="https://profiles.wordpress.org/Clorith/">Marius L. J.</a>, <a href="https://profiles.wordpress.org/matveb/">Matias Ventura</a>, <a href="https://profiles.wordpress.org/mikeschroder/">Mike Schroder</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a>, <a href="https://profiles.wordpress.org/noisysocks/">Robert Anderson</a>, <a href="https://profiles.wordpress.org/rmccue/">Ryan McCue</a>, <a href="https://profiles.wordpress.org/Otto42/">Samuel Wood (Otto)</a>, <a href="https://profiles.wordpress.org/coffee2code/">Scott Reilly</a>, and <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a></p>



<h2 class="wp-block-heading">How to contribute</h2>



<p>To get involved in WordPress core development, head over to Trac, <a href="https://core.trac.wordpress.org/report/6">pick a ticket</a>, and join the conversation in the <a href="https://wordpress.slack.com/archives/C02RQBWTW">#core</a> and <a href="https://wordpress.slack.com/archives/C051Z1SKBDZ">#6-3-release-leads</a> channels. Need help? Check out the <a href="https://make.wordpress.org/core/handbook/">Core Contributor Handbook</a>.</p>



<p><em>Thanks to <a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a>, <a href="https://profiles.wordpress.org/davidbaumwald/" class="mention"><span class="mentions-prefix">@</span>davidbaumwald</a>, <a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a>, <a href="https://profiles.wordpress.org/jeffpaul/" class="mention"><span class="mentions-prefix">@</span>jeffpaul</a> for proofreading.</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:"Sat, 20 May 2023 04:09:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:19:"Jonathan Desrosiers";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:75:"WPTavern: WordPress 6.3 Development Kicks Off to Conclude Gutenberg Phase 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=145206";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:86:"https://wptavern.com/wordpress-6-3-development-kicks-off-to-conclude-gutenberg-phase-2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3694:"<p>The WordPress 6.3 development cycle has begun and work is already underway  on an ambitious list of features that will debut in the upcoming major release. It will <a href="https://make.wordpress.org/core/2023/02/04/phase-2-finale/">cap off Phase 2</a> of the Gutenberg project, with an emphasis on polishing customization features and making them easier to use.</p>



<p>WordPress 6.3 Editor Triage co-lead Anne McCarthy published a <a href="https://make.wordpress.org/core/2023/05/18/roadmap-to-6-3/">roadmap to 6.3</a> this week, which summarizes what users can expect:</p>



<blockquote class="wp-block-quote">
<p>This release aims to make it easier for users to edit pages, manage navigation, and adjust styles all directly in the Site Editor. It also seeks to provide detailed, relevant information when exploring different parts of the site, such as showing the number of posts per page when viewing relevant blog templates. </p>
</blockquote>



<p>In addition to polishing and wrapping up phase 2, McCarthy&#8217;s post outlines the new features that are coming. Here are a few of the highlights: </p>



<ul>
<li><a href="https://github.com/WordPress/gutenberg/issues/44461">Introduce content editing</a>, including clarifying the relationship between templates and content.</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/50396">Add a Navigation section to the Site Editor</a>&nbsp;with nuanced options depending on the number of menus and complexity of each.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/50463">Add a Pages section to the Site Editor</a>.&nbsp;</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/49014">Add a Styles section to the Site Editor.</a>&nbsp;</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/49601">Expose revisions (styles, templates, and template parts)</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/48457">Add a command center tool</a> for easily accessing different parts of your site. <a href="https://make.wordpress.org/core/2023/05/17/command-center-request-for-feedback/">More information here</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/50030">Add Theme Previews for block themes</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/38990">Surface aspect ratio tooling</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/49175">Consider adding distraction free mode to Site Editor</a>.&nbsp;</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/25071">Keep custom templates and template parts across themes</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/45271">Add an interface for font management</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/issues/50397#top">Explore a path towards “library” management with reusable blocks and template parts</a>.</li>
</ul>



<p>This is a tentative glimpse at some of the user-facing features that may be coming in WordPress 6.3, but the <a href="https://make.wordpress.org/core/2023/05/18/roadmap-to-6-3/">roadmap</a> includes many more items, screenshots, and quick demos.</p>



<p>&#8220;As always, what’s shared here is being actively pursued, but doesn’t necessarily mean each will make it into the final release of WordPress 6.3,&#8221; McCarthy said.</p>



<p>Gutenberg Lead Architect Matías Ventura will be <a href="https://make.wordpress.org/core/2023/05/18/wordpress-6-3-planning-roundup/">leading WordPress 6.3</a>. Beta 1 is expected in a little more than a month on June 27, 2023, with RC 1 on July 18, and the general release scheduled for August 8.</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, 19 May 2023 22:13:07 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:73:"WPTavern: WCEU 2023 Publishes Schedule, Reaffirms Commitment to Diversity";s:7:"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=145217";s:7:"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/wceu-2023-publishes-schedule-reaffirms-commitment-to-diversity";s: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:3577:"<p><a href="https://europe.wordcamp.org/2023/">WordCamp Europe</a> 2023 is just under three weeks away from happening in Athens on June 8-10. More than 2,700 <a href="https://europe.wordcamp.org/2023/tickets/">tickets</a> have been purchased and 527 remain, along with 49 micro-sponsor tickets. </p>



<p>Speaker announcements have concluded and the official <a href="https://europe.wordcamp.org/2023/schedule/">schedule</a> was published today. WCEU will be running three tracks of presentations and two tracks for workshops. Organizers have also announced a <a href="https://europe.wordcamp.org/2023/welness-track-activities/">Wellness Track</a> that will feature different activities throughout the day, including a Yoga class, a Tai Chi class, and a group hike.</p>



<p>&#8220;The Wellness Track is an important addition to WordCamp Europe because we need to find a balance and be more focused on taking care of our minds and bodies, taking care of the whole community and in turn the one world we have to live in,&#8221; organizer Ohia Thompson said. </p>



<p>&#8220;This means seeing our interconnectedness and moving forward with a focus on wellbeing, diversity, and sustainability. The Wellness Track this year is just the beginning of a more intentional future for everyone connected to WordPress.”</p>



<p>Last year the team hosting the event in Porto was <a href="https://europe.wordcamp.org/2022/diversity-at-wceu/">called out for a lack of diversity on the organizing team</a>, which performs critical tasks like selecting speakers and managing a speaker support program. In what appears to be an echo back to that controversy, a public interaction on Twitter earlier this month caused community members to question the organizing team.</p>



<p>WCEU was once again forced to reaffirm its commitment to diversity after Sjoerd Blom, one of the Global organizers, accused StellarWP&#8217;s Director of Community Engagement, Michelle Frechette, of &#8220;being prejudiced&#8221; when she questioned the lack of diversity in the first few rounds of speaker announcements. </p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Please stop being prejudiced and wait until ALL speakers have been announced. Thanks.</p>&mdash; Sjoerd Blom (@sjblom) <a href="https://twitter.com/sjblom/status/1656015637641043968?ref_src=twsrc%5Etfw">May 9, 2023</a></blockquote>
</div>



<p>Blom has since publicly apologized for his response to the criticism this week, reiterating that diversity matters to the team, but only after WCEU received overwhelmingly negative feedback regarding the incident.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">In past weeks, <a href="https://twitter.com/michelleames?ref_src=twsrc%5Etfw">@michelleames</a> highlighted the lack of diversity in WCEU’s speaker line up. I’m truly sorry for the offense I caused, especially in using the word ‘prejudiced’. <a href="https://twitter.com/hashtag/WCEU?src=hash&ref_src=twsrc%5Etfw">#WCEU</a> and I know that diversity matters, and we will be sharing more about what happened in coming days.</p>&mdash; Sjoerd Blom (@sjblom) <a href="https://twitter.com/sjblom/status/1659236811456086016?ref_src=twsrc%5Etfw">May 18, 2023</a></blockquote>
</div>



<p>WordCamp Europe has not yet published anything to mitigate the effects of this public altercation but damage control measures are likely in the works, as Blom indicated a more official response will be coming from the team.</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, 19 May 2023 17:23: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:"";}}}}}}}}}}}}}}}}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:"Sun, 11 Jun 2023 12:05:41 GMT";s:12:"content-type";s:8:"text/xml";s:13:"last-modified";s:29:"Sun, 11 Jun 2023 11:45:31 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 1";}}s:5:"build";s:14:"20230322082821";}