</ul>



<p>Dynamic Yield integrates well with other tools to enhance personalization efforts, particularly <a href="https://segment.com/twilio/">Twilio Segment</a>, a customer data platform enabling real-time data collection and action.</p>



<p><strong>Use cases:</strong> Businesses can use Dynamic Yield to increase engagement and conversion rates, such as personalizing homepage experiences for returning visitors.</p>



<p><strong>Used by:</strong> <a href="https://www.mcdonalds.com/us/en-us.html">McDonald&#8217;s</a>, <a href="https://www.pacsun.com/?srsltid=AfmBOopO0JjIGm5h8VDxzygttVVXvTEK6hTqyyXzFsLeCnaxG9mugNBs">PacSun</a>, <a href="https://www.cotopaxi.com/?srsltid=AfmBOorz7QhfPrt0CHN8RFdUjv_7VPTjcywAtK4ykdXSoYwhBNXT6eh8">Cotopaxi</a>, among others.</p>



<p><strong>Price:</strong> Dynamic Yield offers a customized pricing model tailored to each client&#8217;s specific needs and scale. For detailed pricing information, you&#8217;ll need to <a href="https://www.dynamicyield.com/request-demo/">contact their sales team</a> directly.</p>



<h3 class="wp-block-heading"><strong>3. Optimizely</strong></h3>



<img width="660" height="406" src="https://blog.gravatar.com/wp-content/uploads/2024/10/optimizely-homepage.png?w=660" alt="Optimizley homepage" class="wp-image-2259" />



<p><a href="https://www.optimizely.com/">Optimizely</a> is a leading digital experience platform that empowers businesses to create, experiment, and personalize user experiences.</p>



<p><strong>Best features:</strong></p>



<ul class="wp-block-list">
<li><strong>A/B testing and multivariate testing: </strong>Allows testing of different page versions to identify the most effective elements. An e-commerce site could test different product page layouts to see which leads to more purchases.</li>



<li><strong>AI-driven optimization:</strong> Uses machine learning to automatically optimize experiences. This could involve automatically adjusting the placement of call-to-action buttons based on user interaction patterns.</li>



<li><strong>Personalized content delivery: </strong>Serves different content to different user segments based on their data. A software company might show different feature highlights to enterprise visitors versus small business owners.</li>



<li><strong>Integrations:</strong> Make the most out of Optimizely by combining it with tools like Twilio Segment, <a href="https://marketingplatform.google.com/intl/en_uk/about/analytics/">Google Analytics</a>, and <a href="https://business.adobe.com/">Adobe Experience Cloud</a>.</li>
</ul>



<p><strong>Use cases:</strong> Businesses can increase engagement and conversion rates by running A/B tests on different versions of their product pages to identify the most effective elements.</p>



<p><strong>Used by:</strong> <a href="https://www.ebay.com/">eBay</a>, <a href="https://www.americanexpress.com/">American Express</a>, <a href="https://www.dolby.com/">Dolby</a>, <a href="https://www.fjallraven.com/eu/en-gb/">Fjallraven</a>, among others.</p>



<p><strong>Price:</strong> Optimizely offers a customized pricing model tailored to each client&#8217;s specific needs and scale. <a href="https://www.optimizely.com/plans/">Contact their sales team directly</a> for detailed pricing information.</p>



<h3 class="wp-block-heading"><strong>4. HubSpot&nbsp;</strong></h3>



<img width="660" height="393" src="https://blog.gravatar.com/wp-content/uploads/2024/10/hubspot-homepage.png?w=660" alt="Hubspot homepage" class="wp-image-2260" />



<p><a href="https://www.hubspot.com/">HubSpot</a> is a popular all-in-one CRM platform offering many powerful tools for marketing, sales, and customer service, with a strong emphasis on website personalization.</p>



<p><strong>Best features:</strong></p>



<ul class="wp-block-list">
<li><strong>Smart Content: </strong>Dynamically adjusts website content based on user attributes and behavior. For example, a B2B site could show different case studies to visitors from different industries.</li>



<li><strong>Personalized CTAs:</strong> Displays different call-to-action buttons to different user segments. A SaaS company might show a &#8220;<em>Start Free Trial</em>&#8221; CTA to new visitors and an &#8220;<em>Upgrade Now</em>&#8221; CTA to existing customers.</li>



<li><strong>Automated workflows:</strong> Creates personalized user journeys based on user actions and characteristics. This could involve sending a series of targeted emails based on which resources a user has downloaded.</li>
</ul>



<p><strong>Use cases:</strong> Businesses can use HubSpot to increase engagement and conversion rates by delivering targeted CTAs to specific visitor groups.</p>



<p><strong>Used By:</strong> <a href="https://www.tripadvisor.com/">Tripadvisor</a>, <a href="https://www.eventbrite.com/">Eventbrite</a>, <a href="https://www.weightwatchers.com/us/">WeightWatchers</a>, and more.</p>



<p><strong>Price:</strong> HubSpot offers <a href="https://www.hubspot.com/pricing/marketing/enterprise?hubs_content=www.hubspot.com%2F&hubs_content-cta=nav-pricing&term=annual">tiered pricing plans</a> for their different products, which include marketing, sales, service, content, operations, and commerce. All of them start at $15/month per seat and can go up to $3,600/month, depending on what you need. They also have many free tools, so you can get a taste of the platform before you commit to subscribing.&nbsp;</p>



<h3 class="wp-block-heading"><strong>5. Hyperise</strong></h3>



<img width="660" height="407" src="https://blog.gravatar.com/wp-content/uploads/2024/10/hyperise-homepage.png?w=660" alt="Hyperise homepage" class="wp-image-2261" />



<p><a href="https://hyperise.com/">Hyperise</a> is a personalization platform that allows businesses to dynamically personalize images and content across various digital touchpoints.</p>



<p><strong>Best features:</strong></p>



<ul class="wp-block-list">
<li><strong>Dynamic image personalization: </strong>Customizes images based on user data. A real estate site could show property images with the visitor&#8217;s name on the &#8220;For Sale&#8221; sign.</li>



<li><strong>Personalized text overlays: </strong>Adds personalized text to images or videos. An online course platform could add the user&#8217;s name to certificate images in promotional materials.</li>



<li><strong>CRM integration:</strong> Pulls data from CRM systems to personalize content. This allows for using detailed customer information, like past purchases or support interactions, in personalizing the web experience.</li>
</ul>



<p><strong>Use cases:</strong> Businesses can use Hyperise to create personalized landing pages for different audience segments, enhancing relevance and engagement.</p>



<p><strong>Used by:</strong> <a href="https://www.g2.com/">G2</a>, <a href="http://placer.ai">Placer.ai</a>, <a href="https://www.salesloft.com/">SalesLoft</a>, and <a href="https://orca.security/">Orca Security</a>.&nbsp;</p>



<p><strong>Price:</strong> Hyperise offers various pricing plans, depending on what you want included. Their <em>Images </em>plan costs $69/month per seat and lets you create personalized images for your outreach. The other two tiers include adding a website and videos.&nbsp;</p>



<h3 class="wp-block-heading"><strong>6. Marketing Cloud Personalization by Salesforce</strong></h3>



<img width="660" height="360" src="https://blog.gravatar.com/wp-content/uploads/2024/10/salesforce-homepage.png?w=660" alt="Salesforce marketing personalization homepage" class="wp-image-2262" />



<p><a href="https://www.salesforce.com/eu/">Salesforce</a>, formerly known as Evergage, is a comprehensive customer data platform that now also includes a personalization engine as part of its marketing tools. Businesses can use their tools to create individualized experiences across multiple channels, including web, mobile, and email.</p>



<p><strong>Best features:</strong></p>



<ul class="wp-block-list">
<li><strong>Real-time segmentation:</strong> Groups users based on their current behavior and historical data. An airline website could segment users based on their typical flight patterns and current browsing behavior.</li>



<li><strong>Dynamic content personalization:</strong> Adapts content in real-time based on user segments and behavior. A media streaming service could adjust its homepage layout based on the user&#8217;s viewing history and current trends.</li>



<li><strong>Journey orchestration</strong>: Creates and manages personalized customer journeys across multiple touchpoints. A bank could create different communication sequences for customers based on their life events, like buying a house or starting a business.</li>
</ul>



<p><strong>Use cases:</strong> Businesses can use Salesforce for personalized product recommendations and content tailored to individual shopping behaviors.</p>



<p><strong>Used by:</strong> <a href="https://www.generalmills.com/">General Mills</a>, <a href="https://www.formula1.com/">Formula 1</a>, <a href="https://www.accenture.com/us-en">Accenture</a>, among others.</p>



<p><strong>Price:</strong> This service comes in <a href="https://www.salesforce.com/marketing/pricing/">three tiers</a>: Marketing Cloud Engagement, Marketing Cloud Account Engagement, and Marketing Cloud Growth Edition. The first two tiers go for $1,250/month, while the third is $1,500/month per organization.</p>



<h3 class="wp-block-heading"><strong>7. Yieldify</strong></h3>



<img width="660" height="385" src="https://blog.gravatar.com/wp-content/uploads/2024/10/yieldify-homepage.png?w=660" alt="Yieldify homepage" class="wp-image-2263" />



<p><a href="https://www.yieldify.com/">Yieldify</a> is a platform designed to optimize customer journeys through personalized experiences and conversion rate optimization, focusing on e-commerce businesses.</p>



<p><strong>Best features:</strong></p>



<ul class="wp-block-list">
<li><strong>Personalized overlays and pop-ups: </strong>Creates targeted messages that appear based on user behavior. An e-commerce site could show a discount pop-up to users who are about to leave the site without purchasing.</li>



<li><strong>Behavioral targeting: </strong>Tailors experiences based on user actions and characteristics. A fashion retailer could show different promotional banners to users based on the categories they&#8217;ve been browsing.</li>



<li><strong>Data-driven insights:</strong> Provides analytics to help understand user behavior and optimize personalization strategies. This could help identify which personalization tactics are most effective for different user segments.</li>
</ul>



<p><strong>Use cases:</strong> Businesses can use Yieldify to reduce cart abandonment through exit-intent pop-ups and promote special offers based on user behavior.</p>



<p><strong>Used by:</strong> <a href="https://www.lacoste.com/">Lacoste</a>, <a href="https://www.kiehls.com/">Kiehls</a>, <a href="https://int.clarins.com/">Clarins</a>, <a href="https://www.thenorthface.com/">The North Face</a>, among others.</p>



<p><strong>Price:</strong> Yieldify offers customized pricing based on specific needs. <a href="https://www.yieldify.com/get-started/">Contact them directly</a> to get started and obtain pricing information.</p>



<h2 class="wp-block-heading"><strong>Selecting the ideal personalization tools for your website</strong></h2>



<p>Choosing the right personalization tools for your website is crucial for maximizing engagement and conversion rates. Here&#8217;s how to approach this important decision:</p>



<h3 class="wp-block-heading"><strong>Step 1: Understand your needs</strong></h3>



<p>Before selecting a tool, identify your specific goals and challenges. Are you looking to improve user engagement, increase conversion rates, or streamline user profile management? Assess your current marketing stack and identify integration needs to ensure quick and easy implementation.</p>



<h3 class="wp-block-heading"><strong>Step 2: Evaluate key features</strong></h3>



<p>Create a list of essential features you need in a personalization tool. Consider factors such as:</p>



<ul class="wp-block-list">
<li>Ease of use and integration</li>



<li>A/B testing capabilities</li>



<li>Real-time analytics</li>



<li>User-friendly interfaces to reduce the learning curve for your team</li>
</ul>



<p><strong>Don&#8217;t overlook the importance of data privacy and security.</strong> Tools like Gravatar emphasize user control over personal information, allowing users to edit their public profiles and share only what they&#8217;re comfortable with. Ensure the tool complies with regulations such as <a href="https://gdpr-info.eu/">GDPR</a> and <a href="https://oag.ca.gov/privacy/ccpa">CCPA</a> for legal data handling practices.</p>



<h3 class="wp-block-heading"><strong>Step 3: Analyze cost and ROI</strong></h3>



<p>Consider both short-term costs and long-term value when evaluating tools. Low-cost and free tools like Gravatar offer high value and low risk, making them excellent starting points for personalization efforts.</p>



<h3 class="wp-block-heading"><strong>Step 4: Success stories</strong></h3>



<p>Look at real-world examples of companies successfully using personalization tools to drive growth. For instance, a great example of successful personalization is the plant-based cosmetics brand <a href="https://int.clarins.com/">Clarins</a> which <a href="https://www.yieldify.com/success-stories/clarins/">increased conversions by 20% using Yieldify</a>. Some of the strategies they implemented include:&nbsp;</p>



<ul class="wp-block-list">
<li>Adding virtual consultations to help users find the best products.&nbsp;</li>



<li>Guiding users to book a complimentary phone consultation with a specialist on category pages.&nbsp;</li>



<li>Re-engaging shoppers who try to change tabs with special overlays that include basket reminders and introducing Clarins’ three complimentary products that they offer with each order.&nbsp;</li>
</ul>



<p>Looking at examples like this will show you the full potential of the specific platform and maybe even give you some ideas on how you can implement similar strategies in your own business.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Step 5: Make an informed decision</strong></h3>



<p>Finally, whenever you can, take advantage of demos to better understand each tool&#8217;s capabilities before making a decision. Weigh the risk versus reward, keeping in mind that tools like Gravatar offer easy integration and are free to use, making them a low-risk option to start with.</p>



<h2 class="wp-block-heading"><strong>Unlock the potential of your website with personalization tools&nbsp;</strong></h2>



<p>Website personalization tools are powerful assets in enhancing customer engagement and boosting conversion rates. By tailoring user experiences, these tools provide a significant competitive advantage. In fact, <a href="https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/the-value-of-getting-personalization-right-or-wrong-is-multiplying">companies excelling at personalization generate 40% more revenue than their counterparts</a>.</p>



<p>When choosing personalization tools, consider factors like powerful features, integration capabilities, and ROI measurement.&nbsp;</p>



<p>Gravatar stands out with its unique advantage of utilizing existing user data for personalization without extensive on-site data collection. Its Profile API allows developers to create more detailed and personalized user experiences by integrating additional user information into their websites.</p>



<p>As you explore the tools we&#8217;ve discussed, consider how they align with your business needs. Remember, <a href="https://gravatar.com/developers/new-application">Gravatar is an excellent starting point</a> – it&#8217;s both highly useful and free.&nbsp;</p>



<p>So what are you waiting for? Take the best out of website personalization and create experiences that your users will love!&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:"Thu, 07 Nov 2024 17:33:58 +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:"Ronnie Burt";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:102:"Do The Woo Community: Do the Woo is Trailbazing the Fediverse with Matthias Pfefferle and Derek Hanson";s:7:"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=86690";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:101:"https://dothewoo.io/do-the-woo-is-trailbazing-the-fediverse-with-matthias-pfefferle-and-derek-hanson/";s: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:87:"Do the Woo is on the Fediverse with multi-authors, audio distribution and more to come.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 Nov 2024 10:15:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:112:"Do The Woo Community: Press Release: Do the Woo 4.0 Official Launch, Elevating Voices in the WordPress Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:43:"https://dothewoo.io/?post_type=blog&p=86703";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:54:"https://dothewoo.io/blog/press-release-do-the-woo-4-0/";s: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:125:"Press Release: The official launch of the Do the Woo Podcast Channel 4.0 takes place during WordCamp Europe in Turino, Italy.";s: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, 06 Nov 2024 15: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: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: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:"WPTavern: #144 – Damon Cook &amp; Seth Rubenstein on the Transformational Interactivity API";s:7:"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=178900";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:101:"https://wptavern.com/podcast/144-damon-cook-seth-rubenstein-on-the-transformational-interactivity-api";s: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:41793:"Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast, which is dedicated to all things, WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how the Interactivity API will transform your WordPress websites.</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/feed/podcast. And you can copy that URL into most podcasts players.</p>



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



<p>So on the podcast today we have Damon Cook and Seth Rubenstein.</p>



<p>Damon Cook is a developer advocate with WP Engine, and previously worked as a front end developer at several WordPress focused agencies.</p>



<p>Seth Rubenstein began his WordPress journey in college, and is now the lead engineer at the Pew Research Center, where he works on interactive WordPress applications.</p>



<p>This is the last of the podcast recorded at WordCamp, us 2024, and our focus today is the interactivity API. You may not be familiar with what this is and why it matters, so Damon and Seth will break it down, and explain how it might transform your WordPress websites in the future.</p>



<p>Damon starts off by defining what an interactive website is, giving examples such as single page applications, and dynamic elements like tabs and accordions. Seth adds his perspective on how interactivity aids both the end user, and website editors. Making for a more compelling user experience and efficient content creation.</p>



<p>We get into why WordPress needed an interactivity API, even though the platform already supports libraries, like React. The interactivity API provides a standardized way to create dynamic content, which is essential for modern web expectations.</p>



<p>We also highlight real-world examples, including faceted searching and filtering, which have been successfully implemented using this API.</p>



<p>The conversation also touches on performance improvements brought by the API, emphasizing how it can offload server resources by only updating necessary content.</p>



<p>Towards the end we explore how the API is being used in Gutenberg blocks, and how it supports both developers and site builders.</p>



<p>Damon and Seth also discussed the project&#8217;s development, encouraging more contributions and feedback from the community.</p>



<p>If you&#8217;re intrigued by improving your websites&#8217; interactivity and performance, this episode is for you.</p>



<p>If you&#8217;d like to find out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you&#8217;ll find all the other episodes as well.</p>



<p>And so without further delay, I bring you Damon Cook and Seth Rubenstein.</p>



<p>I am joined on the podcast today by Damon Cook and Seth Rubenstein. Hello.</p>



<p>[00:03:40] <strong>Damon Cook:</strong> Hey, how&#8217;s it going?</p>



<p>[00:03:41] <strong>Nathan Wrigley:</strong> Yeah, really, really nice thank you. That&#8217;s Damon.</p>



<p>[00:03:44] <strong>Seth Rubenstein:</strong> Hello, I&#8217;m Seth.</p>



<p>[00:03:45] <strong>Nathan Wrigley:</strong> Thank you so much. We&#8217;re at WordCamp US, it&#8217;s happening in Oregon. It is the month of September 2024, and I&#8217;m being joined by Damon and Seth so that we can talk about the Interactivity API.</p>



<p>Before we get into that, I think it&#8217;s probably important to paint a picture of both of you, what your background is with WordPress technology, et cetera. So we&#8217;ll just keep this very brief. Let&#8217;s go for Damon first. Damon, just tell us a little bit about you, your potted bio, if you like.</p>



<p>[00:04:10] <strong>Damon Cook:</strong> Sure, yeah. Well, I started out as a WordPress front end developer at WordPress. There&#8217;s several different WordPress focused agencies, and now I&#8217;m a developer advocate with WP Engine.</p>



<p>[00:04:21] <strong>Nathan Wrigley:</strong> Thank you very much. And Seth?</p>



<p>[00:04:23] <strong>Seth Rubenstein:</strong> My first time using WordPress was in college. I converted all of our websites to WordPress multi-site, as like the assistant web developer. And from there I just kept going, and that was just my career track from then on, just WordPress all the time. And now I am the lead engineer at the Pew Research Center, where we have a WordPress platform that we&#8217;ve made ourselves, and we work on a lot of interactive WordPress applications.</p>



<p>[00:04:43] <strong>Nathan Wrigley:</strong> Just staying on your bios just for a moment, what does the Pew Research Center do? I&#8217;ve not heard of them before.</p>



<p>[00:04:49] <strong>Seth Rubenstein:</strong> We are a non-partisan, non advocacy social science research organisation. So we basically study the American public and where they are, what they think on certain issues. And we do a lot of public polling and things like that, and we report that back. So we&#8217;re kind of like a nonprofit news organisation.</p>



<p>[00:05:04] <strong>Nathan Wrigley:</strong> Gosh, okay thank you. That&#8217;s really interesting.</p>



<p>Okay, let&#8217;s open it up and talk about the subject at hand today. So we&#8217;ve got both of these gentlemen here to talk about the Interactivity API. I think probably we should first deal with the topic of, what is an interactive website?</p>



<p>Probably, dear listener, if you&#8217;re listening to this, you might know this already, but I have an intuition that some people won&#8217;t. So, what are the benefits of having an interactive website? And whoever wants to answer that, pick up the mic and go for it.</p>



<p>[00:05:30] <strong>Damon Cook:</strong> I think the classic example is that of a single page application. So the idea of being able to navigate from page to page, or section to section even, and just have things that seem seamless, so the page isn&#8217;t refreshing, that is a pretty common scenario. But there&#8217;s also lots of other interactive pieces like tabs, accordions, all that stuff gets really helpful when you reach for the Interactivity API in creating stuff like that.</p>



<p>[00:05:59] <strong>Seth Rubenstein:</strong> I don&#8217;t have anything to add to that. I guess what I would say is, on the other side of it besides the front end user, the kind of, your visitor, I think the interactivity part of a website kind of also can help out your editors, and how they&#8217;re building content, and making more engaging content.</p>



<p>I think this will be interesting because I think, you know, Damon might have a kind of perspective of the front end user, and I&#8217;m definitely coming from a perspective of, how can I scale up my editorial team&#8217;s ability to create interactive content? And not so much like what it looks like on the front end.</p>



<p>[00:06:27] <strong>Nathan Wrigley:</strong> So there&#8217;s an interesting distinction there. So, does the work that you are doing touch on both the front end and the back end? So it&#8217;s not just for the forward facing, user facing part of a WordPress website. This is things that you can do in the back end, the admin side of things too.</p>



<p>[00:06:40] <strong>Seth Rubenstein:</strong> Yeah, it&#8217;s how editors create interactive bits of content, and how those interactive bits of content might interact with each other. Because I think right now, without the Interactivity API, that kind of content is static and siloed on the page.</p>



<p>[00:06:52] <strong>Nathan Wrigley:</strong> We will link in the show notes to all of the different places, and no doubt one of the first links will be to the project itself, the Interactivity, API. But I guess I have to ask the question, why is this even a project in WordPress? Is it that WordPress historically wasn&#8217;t particularly adapted towards interactive content?</p>



<p>I mean, we know how to publish posts and pages, and once you&#8217;ve done that, that&#8217;s kind of it. You&#8217;ve done it, and there&#8217;s no interactivity there. Is this something that has been, I don&#8217;t know, more recently thought was necessary? Is this something that you think should be in Core? Let&#8217;s just take that. Has WordPress been bad at interactivity historically?</p>



<p>[00:07:28] <strong>Damon Cook:</strong> I don&#8217;t think that it&#8217;s been bad historically, I think that it&#8217;s more of kind of a, I guess a technology trend of leaning into libraries like React or Preact, which Interactivity is built upon. So I think it&#8217;s more of a trend, but also, yeah, a necessity in Core, because folks are trying to build these types of experiences, and we want to have a standardised way for them to be able to do that, and not have to pull in a bunch of different libraries. And although they still can, you know, there&#8217;s a standardised and backwards compatible way for them to do it. So that&#8217;s the idea.</p>



<p class="ticss-13c01dd4">[00:08:05] <strong>Nathan Wrigley:</strong> Thank you. Seth, anything to add?</p>



<p>[00:08:06] <strong>Seth Rubenstein:</strong> Yeah. I don&#8217;t think WordPress has done a bad job on interactivity in the past, you know, ships with jQuery, ships with React, that&#8217;s all available to you. I think the Interactivity API is kind of looking at how developers have been creating front end experience with React, and narrowing that down to be like the right tool set for blocks and for block developers specifically.</p>



<p>[00:08:26] <strong>Nathan Wrigley:</strong> So it&#8217;s about having the right tooling. Something standardised that everybody can get their teeth into, that every developer understands.</p>



<p>[00:08:32] <strong>Seth Rubenstein:</strong> Yeah, and something that fits the blocks kind of model I think, a little bit better than some of these other frameworks.</p>



<p>[00:08:38] <strong>Nathan Wrigley:</strong> Okay, that&#8217;s great. So give us some examples of good interactivity on the internet. So we could limit ourselves to WordPress, but let&#8217;s not do that. Let&#8217;s just go out there and try to pick good examples.</p>



<p>Really, I guess we could be talking about Google Docs, we could be talking about websites, we could be talking about anything. Do you want to just rattle off a few things where you&#8217;ve seen and you&#8217;ve been impressed, and thought, ah okay, there&#8217;s a good example. The only reason I&#8217;m asking this really is so that the listener can just get an idea of what interactivity means.</p>



<p>[00:09:05] <strong>Damon Cook:</strong> Sure. And I&#8217;m actually going to set up Seth, because I think a lot of the things that his organisation is creating are representative of what folks kind of need. So I&#8217;ll set him up for that.</p>



<p>[00:09:17] <strong>Seth Rubenstein:</strong> And I&#8217;ll say the word that he&#8217;s probably thinking of, facets. Amazon, you&#8217;re browsing Amazon, you want to narrow down the content that you&#8217;re looking at. Those facets on the left hand side, filters, aggregations, whatever you want to call them. I think this has probably been our biggest success with the Interactivity API, is developing out facet blocks.</p>



<p>And with the Interactivity API what that would let you do is just server side hydrate data before it gets back to the client. And you can browse through all this content, and do it in a performant way that you just couldn&#8217;t do before. Or you could, but it would take a lot of work on your part to build out the framework and the technology to handle all that.</p>



<p>And so now that&#8217;s just in the box in WordPress free to use. So we can probably touch on facets a little bit more later, but I think that&#8217;s probably the best use case for the Interactivity API thus far.</p>



<p>[00:10:00] <strong>Nathan Wrigley:</strong> Let&#8217;s dig into that a little bit. So when you say facets, my head is immediately going to things like, I don&#8217;t know, the posts and pages, table layout, or something like that. And the fact that, if I want to get to post number 11, I might have to click a button, wait for a moment whilst the page refreshes, there&#8217;s obviously something going on there, page refresh, I&#8217;m contacting the server and what have you. Is the idea here that, a bit like, I don&#8217;t know, if I scroll on Google, I would be able to automatically upload more pages, more posts, that kind of thing? And then be able to, I don&#8217;t know, say filter them, show me only the ones that are authored by me, or ones with featured images, and that would all happen on the fly.</p>



<p>[00:10:35] <strong>Seth Rubenstein:</strong> Yeah. So, you know, you can filter by author, by taxonomies, category, custom taxonomies, whatever, date, et cetera. And those results just update in real time, without you having to refresh the page.</p>



<p>You can paginate through those results without having to refresh the page. That, of course, is great for the end user, but it&#8217;s also great on the backend because you&#8217;re saving server resources without having to re-render that entire page every single time. So you&#8217;re only rendering out what&#8217;s changed.</p>



<p>So in that way, great for the end user and great for you as a website operator, because the Interactivity API kind of offloads some of that performance overhead that way.</p>



<p>[00:11:07] <strong>Nathan Wrigley:</strong> Yeah, okay. I have children, and they have been born in a world where the mobile phone is completely ubiquitous. And the idea of anything refreshing to them just seems like an anathema, just a pointless thing. You know, you want to open an app, and from that moment just everything happens. You scroll, there&#8217;s more to see, you press back, it just immediately loads and what have you.</p>



<p>Is that kind of where we&#8217;re going with the internet? And what I mean by that is, sites where you&#8217;ve got to click a button to see another further piece of content, or for your shopping cart to be updated, or whatever it may be, that just seems like the 1990s almost.</p>



<p>Is it a bit of that? Is it just we&#8217;re kind of keeping up with the times? And the expectation from the next generation of users is going to be, well, if it isn&#8217;t interactive, I&#8217;m not sticking around. So if I&#8217;ve got a, I don&#8217;t know, a WooCommerce store or something like that, it&#8217;s going to be painful for a user to have to refresh, click a button to go to a cart, wait for it to load and all that. It&#8217;s just, like I said, the 1990s.</p>



<p>[00:12:05] <strong>Damon Cook:</strong> Yeah, I think a lot of it does touch on that and, yeah, just reaching out to that kind of experience. But, yeah, I think Seth touched on this, but the performance impact is pretty great about the Interactivity API because you&#8217;re only updating the sections, or components on the page that are really relevant to what the user is doing. So that has a performance impact. It makes things feel seamless, faster, and I think that&#8217;s a lot of probably what we&#8217;re all looking for at the end of the day.</p>



<p>[00:12:30] <strong>Nathan Wrigley:</strong> It feels like something more native to the device that you are on. So it feels like a Mac app, or a Windows app, or an Android, or an iPhone app. Does that kind of make sense? It just feels like we&#8217;re in the modern world, not in the old world where any kind of refresh just seems bizarre, frankly. Anything to add, Seth?</p>



<p>[00:12:46] <strong>Seth Rubenstein:</strong> You know, I think the coolest part about this is it basically lets you take a PHP application and turn it into a single page JavaScript app. I mean, that&#8217;s really what the Interactivity API as a whole is doing. And I think that&#8217;s what developers are looking for these days. Look at, you know, Next.js, and frameworks like that that are really grown and are really popular. And I think that this kind of API just is an answer to those for WordPress developers.</p>



<p>[00:13:06] <strong>Nathan Wrigley:</strong> So if I were a developer and I was, I don&#8217;t know, creating plugins, themes, blocks, whatever it may be, where do I go and find out about this? How do I get my teeth into the project? So you might want to drop a URL at this point, wherever you want to point us.</p>



<p>[00:13:20] <strong>Damon Cook:</strong> Sure. Well, I can tell you how I find it because I Google it. I Google it myself. Interactivity API Handbook, I&#8217;m pretty sure that&#8217;s where you&#8217;ll find it, and developer.wordpress.org. The documentation is very thorough, and up to date, and complete. And I think that&#8217;s what&#8217;s excites me about this API because it&#8217;s a very discreet project that kind of got pulled together and, yeah, the documentation is really up to date and great, so that&#8217;s where I&#8217;d go.</p>



<p>[00:13:47] <strong>Nathan Wrigley:</strong> Okay, I will link to that in the show notes. And probably a good idea, dear listener, to pause at this point, go and check that out and then come back and hit play.</p>



<p>So from the developer sort of point of view, how baked is it? How complete is it? Is there a lot that you have achieved already? Is there a big roadmap for things that you want to achieve?</p>



<p>I know that&#8217;s going to be difficult to encapsulate in a few sentences, but just tell us the state of the project now for developers listening to this, they might have some intuitions as, okay, that sounds like something I could use right now, as opposed to the roadmap features that are still going to come.</p>



<p>[00:14:17] <strong>Damon Cook:</strong> Sure. No, it is quite complete and ready to use, and the documentation can even step you through how to integrate it into an existing block. You can even spin up a new block with the Interactivity API already baked in.</p>



<p>Some of the future roadmap areas is, I know that we&#8217;re still working on like client side navigation, and then pulling in kind of different modules. Like I know one experiment that&#8217;s being explored is, there&#8217;s a package for accessibility. So just the general idea of speaking, screen reader, passing along. So these APIs have been in WordPress for a while, like some of the accessibility packages. So there&#8217;s explorations in kind of porting that over, and pulling it in, because the Interactivity APIs uses JavaScript modules for a lot of this. So it&#8217;s kind of re jigging, I guess, some of the code and pulling in some of these packages so that developers can use kind of those old, not old, but accessibility features, and have all that compatibility baked in.</p>



<p>So that&#8217;s some of the areas that are still getting integrated, and I&#8217;m excited for them. And I think that&#8217;s on the roadmap right now, and there&#8217;s folks contributing towards it.</p>



<p>[00:15:24] <strong>Seth Rubenstein:</strong> The modules area is probably, I think probably the area that it needs the most work, and hopefully the most amount of work is going into. I would say that&#8217;s probably one of the roughest parts of the Interactivity API right now is, if you need to use an external script, or kind of library, or framework, it&#8217;s a little difficult to get that in. So I think that&#8217;s probably where the most amount of work&#8217;s going to be going.</p>



<p>And I think there&#8217;s some work going on WordPress URL, bringing that in as well. And there&#8217;s a few more directives too, to the API, that are being added like wp-show which should be interesting, that should let you dynamically hydrate elements on the page in a different way. I won&#8217;t go to like all the technical details on that, but there are some additional features that are coming to the Interactivity API, beyond just the module stuff. So there are, in the Interactivity API parlance, there are new directives coming soon.</p>



<p>[00:16:05] <strong>Nathan Wrigley:</strong> I think for anybody who is a developer, you&#8217;re going to be fine looking at the documentation. But if I say any acronym on this podcast, I always get some pushback from people who are not developers, WordPress end users. So let&#8217;s address that.</p>



<p>Is there going to be functionality within the Interactivity API, although it&#8217;s there, and it is part of the Interactivity API, will be available to just builders of websites? People who have their own blog, or their own property, they&#8217;re not interested in WordPress from a technical point of view. Is there anything that they can do with it so that they can have this sort of dynamic content? Or is it mainly going to be through the work that developers do, through plugins, and blocks, and what have you?</p>



<p>[00:16:44] <strong>Seth Rubenstein:</strong> Right now. It&#8217;s live, already on your site if you&#8217;re running kind of the latest version of WordPress. The light box in the image block is using the Interactivity API. So site builders are already gaining that Core query, already has interactivity built in. So does the pagination block. So your publication pages can already be kind of a single page JavaScript app. So Core is adding that stuff in and, yeah, obviously plugin developers will also hopefully add interactivity to their plugins, but it&#8217;s already there for site builders.</p>



<p>[00:17:11] <strong>Nathan Wrigley:</strong> It feels like we&#8217;ve gone down the road in WordPress where everybody&#8217;s done their own thing with interactivity. The page builders have done, well, not just the page builders as one block, but each page builder has done a different thing. You&#8217;ve got these multitude of plugins that do the sort of facet searching and all of that kind of thing.</p>



<p>The idea that there&#8217;s just going to be this one thing, I suppose in a sense you kind of want the Interactivity API to not really be that well known about. The idea is for it to sort of fade into the background and nobody even realise that there&#8217;s a thing. Is that sort of doing down the project a little bit, or is that kind of the point? If nobody knows it exists, but it works, that&#8217;s kind of the ideal.</p>



<p>[00:17:45] <strong>Damon Cook:</strong> Yeah, I mean these APIs are in the background, yeah, for developers to explore, and use, and pull in, and integrate. But yeah, at the end of the day, the end user shouldn&#8217;t know about it, have to know about any of this, and just, have a great experience. So yeah, I think that&#8217;s the idea.</p>



<p>[00:18:00] <strong>Nathan Wrigley:</strong> Where do you learn what you should be working on? So the team of volunteers and seconded people that are working on the Interactivity API, who are you listening to? Where do you get your feedback from? And I know in the open source world, it&#8217;s hard to get that feedback. And you might be just listening to a dozen voices, interested people, or there may be, I don&#8217;t know, hundreds of people talking to you. But to drive it forward, who are you listening to? Where do you get your intuitions as to what should be on the roadmap?</p>



<p>[00:18:25] <strong>Damon Cook:</strong> There is a Make Slack Group, it&#8217;s Interactivity API I believe, or Core Interactivity API room. But there&#8217;s some great contributors in there, and I&#8217;m probably going to mess up all their names but there&#8217;s Jon Surrell, I believe, and Greg Ziółkowski. I apologise Greg, I tried. But they are very active contributors and I probably feel like the least contributor. But, yeah, they&#8217;ve been doing a great job.</p>



<p>I think what it comes down to historically, the Frontity team, I&#8217;m not sure if you&#8217;re familiar with that project, but back in the day they kind of got integrated. All these smart folks into Automattic as full-time contributors, and a lot of them have been driving this project daily and contributing towards it, and they&#8217;ve been doing an amazing job. Some other folks, I think from Google, also contribute a lot towards Interactivity API. So that&#8217;s what I follow, they&#8217;re all in that room a lot and very active.</p>



<p>[00:19:20] <strong>Seth Rubenstein:</strong> That&#8217;s almost everybody. I don&#8217;t know if you mentioned Luis, he&#8217;s kind of my main point of contact. I ping him with questions, or ideas or, hey, we&#8217;re going to try to do this, does this sound crazy to do with the Interactivity API? And he&#8217;s pretty receptive.</p>



<p>[00:19:32] <strong>Nathan Wrigley:</strong> Would it be fair to say that you could do with some more helpers though? I think in the open source world we could always use some more people flocking around any particular given project. Is that something that you&#8217;d be interested in? I don&#8217;t know, one of the intentions of a podcast like this is to make things like that happen but, yeah, is that a thing?</p>



<p>[00:19:47] <strong>Seth Rubenstein:</strong> I would like to see a lot more people using an API. You know, we&#8217;re trying to push the limits of the API, and I think it&#8217;s important that we all kind of try to push the limits and see where it needs additional work, or where we might need extra functionality. So I&#8217;d love to see a lot more people using it because I just don&#8217;t think it&#8217;s gotten kind of the critical mass yet.</p>



<p>[00:20:04] <strong>Nathan Wrigley:</strong> Can you give us some nice examples that I could link to in the show notes of situations where you&#8217;ve seen, specifically the Interactivity API. We mentioned earlier about, you know, general websites and what have you.</p>



<p>Are there any good examples where you&#8217;ve seen somebody using it, so that if there is a developer looking at this, they can go, oh okay, that&#8217;s the kind of thing we&#8217;re talking about.</p>



<p>[00:20:21] <strong>Damon Cook:</strong> I certainly can share some links. I have some repos on GitHub where I&#8217;ve built custom blocks and I&#8217;ve done, I believe there&#8217;s a YouTube, at least a recording of a presentation where I&#8217;ve gone step through building, some of these custom blocks and they&#8217;re all in my repo.</p>



<p>I was going to hand it off to Seth, I guess again, because I know one block that stood out to me that him and his team have created is like a, well, I think you have a poll, but also like a table filtering. I mean, I think those are pretty common experiences that we see on sites, and they&#8217;ve done a great job in creating that seamless experience of filtering.</p>



<p>[00:20:56] <strong>Seth Rubenstein:</strong> I can just gush for a moment. If you want a good example, www.pewresearch.org, almost everything that you&#8217;re going to see there is using the Interactivity API. Mega Menus, MailChimp newsletter signups, facets, pagination, table of contents. That updates as you scroll through the page, because the chapter blocks report using the Interactivity API to the table of contents block, which is separate, their position. Data tables, charts, quizzes, you name it, pretty much everything that we have on our website is using the Interactivity API at this point.</p>



<p>There&#8217;s a few plugins that we still have to convert, it&#8217;s actually only two. But almost everything that you see there is using the API, and almost all that code is available for free open source on github.com/pewresearch.</p>



<p>[00:21:39] <strong>Nathan Wrigley:</strong> Did you do that yourself because you are knee deep in the weeds of this, and so you could understand easily how to do that? Or would it be true to say that the developer documents that you&#8217;ve just mentioned would steer any, air quotes, competent developer to be able to achieve that? Or is it just that you know, you&#8217;ve got the Interactivity API, you also work for this organisation, so the two met.</p>



<p>[00:21:58] <strong>Seth Rubenstein:</strong> I think it&#8217;s because we wanted to provide learning resources, we wanted to provide a use case of, here&#8217;s what is possible. Obviously I&#8217;m talking about a lot of blocks that are interactive, but one of the things that I could really go into is our concept around the Interactivity API.</p>



<p>I think a lot of examples that people can point to, it&#8217;s a very specific use case. This block is a collapsible block, you click on it and it expands. We&#8217;ve taken a different approach, something that we call Atomic Interactive Blocks. And so we&#8217;ll make a block and it will have some interactivity instructions and functionality, but the point of that is to be dropped into another block, which has its own interactivity, and instructions, and functionality, and so on and so forth.</p>



<p>And so what we&#8217;ve really done is made a library of interactive blocks that kind of act like React components, and that you can drop them in other use cases and style them however you want, but what they do is defined maybe higher up.</p>



<p>Yeah, so I think to me that&#8217;s really the power of the Interactivity API, because what that allows us to do is, as developers, is just maintain a small library of blocks that are programmed to do a lot of things, and interact with a lot of other blocks, but then hand off styling, and content, and all that stuff to designers and other people.</p>



<p>For me, that&#8217;s been the coolest part about the Interactivity API, is this abstraction out of a block of what it does. We can go into it more, but the interactive stores can communicate with one another, and so you can have block A do a very specific thing, you click on it and it opens. And maybe you put that inside of block B, and block B is aware, well, when block A is set to be open, when its state is set to be open, I need to do this. And so, you know, you can imagine, you can make a button block, and use that in infinite applications.</p>



<p>The way that we approach it though, that block can dynamically target an interactive store rather than statically being set to just do this one thing in this one interactive store. So all of those GitHub repos will provide examples of how that kind of system works, and how you might approach the same thing for your organisation or website.</p>



<p>[00:23:48] <strong>Damon Cook:</strong> I think what Seth touched upon is interesting because I think it says a lot kind of to how the API has been built to abstract some of these ideas, and just shared state between components. So like you touched on, a button can be shared, and so many are used in so many contexts, but to be able to abstract that and share state, and the interactivity between these components is, it shows a lot of, the API has been built smartly so that it can be explored and experimented with, which is neat.</p>



<p>[00:24:19] <strong>Nathan Wrigley:</strong> I think one thing about this topic is that it is possible, probably, to go a bit overboard with being interactive. I&#8217;ve got the API, I know how to use it now, I&#8217;m going to make everything interactive. And I guess there&#8217;s a point where you&#8217;ve got to tell yourself, slow down, not everything needs to be interactive. So let&#8217;s just go into that. Are there any uses which you would say, yeah, you could do that interactively but we probably shouldn&#8217;t? Are there any times where you think, let&#8217;s put the brakes on?</p>



<p>[00:24:45] <strong>Damon Cook:</strong> I mean, I think any developer will kind of realise when they&#8217;ve maybe over-engineered something. There&#8217;s always going too far and making everything, yeah. You&#8217;ll know I think if you&#8217;re trying to make everything interactive, every paragraph or, you know, it&#8217;s just kind of pointless. But the exciting part is that you can experiment and explore, interact with these APIs and see what you can do. And find the edges of what you can do, and what you should do, or shouldn&#8217;t do, that&#8217;s the fun part.</p>



<p>[00:25:10] <strong>Seth Rubenstein:</strong> Yeah, I will say that, is it possible that you can do too much? For sure. Technically speaking though, is it possible that you can do too much? I don&#8217;t think so. Like I said, we have a lot of interactivity blocks on a page, and the performance has been great. So I don&#8217;t think there should be a concern of like, oh, I&#8217;m overdoing it with using the Interactivity API in terms of performance. I think the more things you make with the Interactivity API, the better performance you&#8217;re going to get.</p>



<p>[00:25:33] <strong>Nathan Wrigley:</strong> Let&#8217;s just speak to the performance side of things because you mentioned technically how it&#8217;s achieved a little bit, but could we just develop that a little bit? And you&#8217;ve definitely said performance isn&#8217;t affected, or performance is really great a number of times. What does that actually mean? So if I&#8217;m using this, is it a more performant website because it&#8217;s, I don&#8217;t know, it&#8217;s loading content asynchronously or what have you?</p>



<p>Has there been any situations where you&#8217;ve had to, I don&#8217;t know, refactor things because the performance took a dip. Performance at the moment is everybody&#8217;s big worry, isn&#8217;t it? Because, you know, Google takes those metrics and ranks you accordingly. So we kind of want to know that if we make this thing interactive, it&#8217;s not going to suddenly impact our score. And I know that Google does take note of these kind of things.</p>



<p>[00:26:11] <strong>Seth Rubenstein:</strong> Yeah, I think on the performance bit, I mean, to get a little technical, what makes it so performant is kind of that idea of server side hydration, right? You click on something and that element changes, and that can happen client side, but if it needs a new data, that in the past has meant refreshing the page or doing something really kind of complex and technical.</p>



<p>Now when the data changes and when that element needs to change, that one element re renders on the server, and then it&#8217;s returned back to the client, not the whole page. So that right there is an immediate performance savings because you&#8217;re not having to render a whole page out again, just to get this one little bit of changed information on a page.</p>



<p>[00:26:45] <strong>Nathan Wrigley:</strong> Let&#8217;s get into probably the final thing for today, and that is the accessibility perspective of things. It&#8217;s become the watch word I think of 2023, 2024, and probably it&#8217;ll carry on, rightly so.</p>



<p>Has there been any accessibility concerns? Because obviously if you&#8217;re updating content live on the page, is there anything that we need to be concerned about if we&#8217;re developing with the Interactivity API in terms of the accessibility, I don&#8217;t know, screen readers or other assistive technologies.</p>



<p>[00:27:12] <strong>Damon Cook:</strong> Sure, yeah. I think it&#8217;s always a challenge in building your components, and making sure they&#8217;re interactive. So I think that it&#8217;s really kind of just abstracting things, trying to figure out what your HTML is, what your CSS is, and then layering on the Interactivity API. I know that some of the extensions of pulling in like strings of information that are being updated on the page, like some of the older packages, like the accessibility, or a11y, for the acronym. Some of these packages that have been in Core for a while, they&#8217;re being ported over into the Interactivity API.</p>



<p>That&#8217;s something that&#8217;s kind of on the roadmap and being explored right now, so that we can have some of these screen reader updates for components, and on the page be integrated with the Interactivity API. So that&#8217;s, yeah, definitely something that&#8217;s being explored.</p>



<p>But also, yeah, a lot of it is more of just the approach because just the markup and the CSS alone, having the knowledge of how to make that accessible is always a practice, an art form, and something that is always, can be improved.</p>



<p>[00:28:17] <strong>Nathan Wrigley:</strong> Okay, thank you. Anything, Seth?</p>



<p>[00:28:19] <strong>Seth Rubenstein:</strong> I think that there&#8217;s actually probably better accessibility that you&#8217;re going to get out of the Interactivity API. You know, I know that screen readers and assistive technologies have come a long way, but if a lot of your website relied on React, and other JavaScript frameworks that render after the page has been rendered, that could pose a problem for accessibility technologies. Here, all that stuff is pre-hydrated and pre-rendered before the page even loads. So your markup&#8217;s ready to go as soon as the page loads, which is actually great.</p>



<p>[00:28:46] <strong>Nathan Wrigley:</strong> I think probably time has caught up with us. But before we go, we did mention the URLs and where you can find the project. Let&#8217;s just, firstly, go through where we can find you individually. So that might be an email, a Twitter handle, or whatever it might be. So let&#8217;s go to Damon first. Where can people find you if they&#8217;re interested in catching up?</p>



<p>[00:29:03] <strong>Damon Cook:</strong> I think probably the easiest is X, I still call it Twitter. I am dcook. I&#8217;m always open. Yeah, reach out. I think 99% of my Twitter timeline is sharing WordPress ideas, outreach links. So yeah, you&#8217;ll find me for any WordPress stuff there.</p>



<p>[00:29:21] <strong>Nathan Wrigley:</strong> Thank you so much. And, Seth?</p>



<p>[00:29:22] <strong>Seth Rubenstein:</strong> You can also find me on Twitter, which I refuse to call X. Twitter.com/sethrubenstein. And I also share a bunch of Interactivity API and WordPress stuff.</p>



<p>[00:29:29] <strong>Nathan Wrigley:</strong> Thank you. So this is the bit where I ask, is there anything that we missed? Is there something that you desperately wanted to get across that I failed to ask?</p>



<p>[00:29:36] <strong>Damon Cook:</strong> To go back just a little bit, he was touching on performance. So one thing actually I wanted to speak to was the idea of the Interactivity API is a standard means for developers to pull in these kind of libraries and do interactivity experiences. And so using this API, you&#8217;re relying on, you know, a simple small bit of source code that is going to be integrated on every page. So that performance impact of not having to pull in an entire library, so it makes it a smaller source code that&#8217;s being pulled in, so that has a huge performance impact as well.</p>
</div>



<p>On the podcast today we have <a href="https://us.wordcamp.org/2024/speaker/damon-cook/">Damon Cook</a> and <a href="https://us.wordcamp.org/2024/speaker/seth-rubenstein/">Seth Rubenstein</a>.</p>



<p>This is the last of the podcasts recorded at WordCamp US 2024, and our focus today is the Interactivity API. You may not be familiar with what this is and why it matters, so Damon and Seth will break it down, and explain how it might transform your WordPress websites in the future.</p>



<p>Damon starts off by defining what an interactive website is, giving examples such as single-page applications and dynamic elements like tabs and accordions. Seth adds his perspective on how interactivity aids both the end-user and website editors, making for a more compelling user experience and efficient content creation.</p>



<p>We get into why WordPress needed an Interactivity API, even though the platform already supports libraries like React. The Interactivity API provides a standardised way to create dynamic content, which is essential for modern web expectations.</p>



<p>We also highlight real-world examples, including faceted searching and filtering, which have been successfully implemented using this API. The conversation also touches on performance improvements brought by the API, emphasising how it can offload server resources by only updating necessary content.</p>



<p>Towards the end, we explore how the API is already being used in Gutenberg blocks and how it supports both developers and site builders. Damon and Seth also discuss the project&#8217;s development, encouraging more contributions and feedback from the community.</p>



<p>If you&#8217;re intrigued by improving your WordPress site’s interactivity and performance, this episode is for you.</p>



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



<p><a href="https://www.pewresearch.org">Pew Research Center</a></p>



<p><a href="https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/">Interactivity API Handbook</a></p>



<p><a href="https://developer.wordpress.org">WordPress Developer Resources</a></p>



<p><a href="https://frontity.org">Frontity</a></p>



<p><a href="https://github.com/pewresearch">Pew Research Center on GitHub</a></p>



<p><a href="https://x.com/dcook/">Damon&#8217;s X</a></p>



<p><a href="https://x.com/dcook/">Seth&#8217;s X</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, 06 Nov 2024 15:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nathan Wrigley";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:117:"Do The Woo Community: The Future of Distributed Social Media on WordPress with Robert Windisch and Matthias Pfefferle";s:7:"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=86671";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:116:"https://dothewoo.io/the-future-of-distributed-social-media-on-wordpress-with-robert-windisch-and-matthias-pfefferle/";s: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:178:"In this episode, Abha discusses WordPress's potential evolution into a distributed social media platform with Matthias and Robert, emphasizing community engagement and new tools.";s: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, 06 Nov 2024 10:23:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:93:"WPTavern: WordCamp Asia and WordCamp Europe Added to Kim Parsell Memorial Scholarship Program";s:7:"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=178985";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:104:"https://wptavern.com/wordcamp-asia-and-wordcamp-europe-added-to-kim-parsell-memorial-scholarship-program";s: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:2901:"<p>As announced at the <a href="https://wordpressfoundation.org/news/2024/meeting-minutes/">2024 WordPress Foundation Meeting</a>, the  <a href="https://wordpressfoundation.org/projects/kim-parsell-memorial-scholarship/">Kim Parsell Memorial Scholarship</a> has been expanded to include WordCamp Europe and WordCamp Asia. Traditionally supporting a woman WordPress contributor to attend WordCamp US, the scholarship now assists women facing financial challenges in attending these three flagship WordCamp events.</p>



<p>The scholarship honors <a href="https://wordpress.org/news/2019/11/people-of-wordpress-kim-parsell/">Kim Parsell</a>, a cherished member of the WordPress community and regarded as one of the first “women of WordPress”. Known fondly as #wpmom, Kim was a dedicated volunteer who devoted countless hours to the WordPress project and was a strong advocate for women entering the tech industry.</p>



<p>In 2014, Kim received a travel stipend from the WordPress Foundation, allowing her to attend the WordPress Community Summit held alongside WordCamp San Francisco—a transformative experience she cherished.The WordPress Foundation now offers this scholarship in her memory.</p>



<p>The<a href="https://wordpressfoundation.org/news/2024/kim-parsell-memorial-scholarship-expands-to-wordcamp-asia-and-wordcamp-europe/"> announcement post</a> states: “ This expansion honors Kim’s legacy and her dedication to inclusivity and diversity within the WordPress community, making it possible for more community members to attend these inspiring events.”</p>



<p>To qualify, applicants must:</p>



<ul class="wp-block-list">
<li>Identify as a woman</li>



<li>Actively contribute to the WordPress project</li>



<li>Have never attended WordCamp Asia or WordCamp Europe before</li>



<li>Require financial assistance to attend WordCamp Asia or WordCamp Europe 2025</li>
</ul>



<p><strong>Applications are open until November 30, 2024, for both <a href="https://wordcampcentral.survey.fm/wcasia-2025-kim-parsell-scholarship-application">WordCamp Asia</a> and <a href="https://wordcampcentral.survey.fm/wceu-2025-kim-parsell-scholarship-application">WordCamp Europe</a>, with notifications sent by December 21, 2024. </strong> Applications for WordCamp US will open in the coming months. The scholarship covers travel to the host city, hotel accommodation for the event duration, and a WordCamp ticket. It does not include airport transfers, meals, or other incidental expenses.</p>



<p>The scholarship’s inaugural recipient in 2015 was <a href="https://profiles.wordpress.org/anyssa/">Anyssa Ferreira</a>, a Brazilian designer, feminist, and WordPress community activist. Last year, it was awarded to <a href="https://profiles.wordpress.org/cnormandigital/">Cynthia Norman</a>, a WordPress developer and Web designer, with a background in training and education.</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, 06 Nov 2024 04:48:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Jyolsna";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:14:"Matt: I Voted!";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:23:"https://ma.tt/?p=129655";s:7:"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:30:"https://ma.tt/2024/11/i-voted/";s: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:485:"<p>It was a huge pain in the butt, because my mail-in ballot didn&#8217;t register properly, but I found a last-minute flight to Houston and this morning walked over to <a href="https://www.emanuelhouston.org/">Congregation Emanu El</a> and voted. It is our most sacred duty as a citizen. I encourage every American to vote.</p>



<img width="604" height="483" src="https://i0.wp.com/ma.tt/files/2024/11/IMG_9886-1024x819.jpeg?resize=604%2C483&ssl=1" alt="" class="wp-image-129656" />";s: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, 05 Nov 2024 23:04:55 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:53:"WordPress.org blog: WordPress 6.7 Release Candidate 3";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=18056";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wordpress.org/news/2024/11/wordpress-6-7-release-candidate-3/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8986:"<p>The third release candidate (RC3) for WordPress 6.7 is ready for download and testing!</p>



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



<p>Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.7 is the best it can be.</p>



<p>You can test WordPress 6.7 RC3 in four ways:</p>



<table><tbody><tr><th>Plugin</th><td>Install and activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).</td></tr><tr><th>Direct Download</th><td>Download the <a href="https://wordpress.org/wordpress-6.7-RC3.zip">RC3 version (zip)</a> and install it on a WordPress website.</td></tr><tr><th>Command Line</th><td>Use the following <a href="https://make.wordpress.org/cli/">WP-CLI</a> command:<br /><code>wp core update --version=6.7-RC3</code></td></tr><tr><th>WordPress Playground</th><td>Use the <a href="https://playground.wordpress.net/#%7B%20%22preferredVersions%22:%20%7B%20%22php%22:%20%228.0%22,%20%22wp%22:%20%22beta%22%20%7D,%20%22features%22:%20%7B%20%22networking%22:%20true%20%7D,%20%22steps%22:%20%5B%20%7B%20%22step%22:%20%22login%22,%20%22username%22:%20%22admin%22,%20%22password%22:%20%22password%22%20%7D,%20%7B%20%22step%22:%20%22importFile%22,%20%22file%22:%20%7B%20%22resource%22:%20%22url%22,%20%22url%22:%20%22https://raw.githubusercontent.com/wpaccessibility/a11y-theme-unit-test/master/a11y-theme-unit-test-data.xml%22%20%7D%20%7D,%20%7B%20%22step%22:%20%22importFile%22,%20%22file%22:%20%7B%20%22resource%22:%20%22url%22,%20%22url%22:%20%22https://raw.githubusercontent.com/WordPress/theme-test-data/master/themeunittestdata.wordpress.xml%22%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22query-monitor%22%20%7D,%20%22options%22:%20%7B%20%22activate%22:%20false%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22create-block-theme%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22debug-bar%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22health-check%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22test-reports%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22user-switching%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D%20%5D%20%7D">6.7 RC3 WordPress Playground instance</a> (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.</td></tr></tbody></table>You can test the RC3 version in four ways.



<p>The current target for the WordPress 6.7 release is <strong>November 12, 2024</strong>. Get an overview of the <a href="https://make.wordpress.org/core/6-7/">6.7 release cycle</a>, and check the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/6-7/">6.7-related posts</a> in the coming weeks for further details.</p>



<h2 class="wp-block-heading">What&#8217;s in WordPress 6.7 RC3?</h2>



<p>Get a recap of WordPress 6.7’s highlighted features in the <a href="https://wordpress.org/news/2024/10/wordpress-6-7-beta-1/">Beta 1 announcement</a>. For more technical information related to issues addressed since RC2, you can browse the following links:</p>



<ul class="wp-block-list">
<li><a href="https://github.com/WordPress/gutenberg/commits/wp/6.7?since=2024-10-29&until=2024-11-05">GitHub commits for 6.7</a> since October 29</li>



<li><a href="https://core.trac.wordpress.org/query?status=closed&changetime=10%2F29%2F2024..11%2F05%2F2024&milestone=6.7&col=id&col=summary&col=milestone&col=owner&col=type&col=priority&order=id">Closed Trac tickets</a> since October 29</li>
</ul>



<h2 class="wp-block-heading">How you can contribute</h2>



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



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



<p>Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. <a href="https://make.wordpress.org/test/2024/10/01/help-test-wordpress-6-7/">This detailed guide</a> will walk you through testing features in WordPress 6.7. For those new to testing, follow <a href="https://make.wordpress.org/test/2024/02/15/help-test-wordpress-6-5-beta-1">this general testing guide</a> for more details on getting set up.</p>



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



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



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



<p>From now until the final release of WordPress 6.7 (scheduled for November 12, 2024), the <a href="https://make.wordpress.org/security/2024/02/12/welcoming-2024-with-wordpress-6-5-beta-1/">monetary reward for reporting new, unreleased security vulnerabilities</a> is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the <a href="https://hackerone.com/wordpress">HackerOne page</a> and in the <a href="https://wordpress.org/about/security/">security white paper</a>.</p>



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



<p>For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.&nbsp;</p>



<p>Thanks for continuing to test your themes and plugins with the WordPress 6.7 beta releases. With RC3, you’ll want to conclude your testing and update the <em>“Tested up to”</em> version in your <a href="https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/">plugin’s readme file</a> to 6.7.</p>



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



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



<p>Do you speak a language other than English? <span lang="es">¿Español?</span> <span lang="fr">Français?</span> <span lang="ru">Русский?</span> <span lang="ja">日本?</span> <span lang="hi">हिन्दी?</span> <span lang="bn">বাংলা?</span> You can <a href="https://translate.wordpress.org/projects/wp/dev/">help translate WordPress into more than 100 languages</a>.</p>



<h2 class="wp-block-heading">Release the haiku</h2>



<p><em>RC3 arrives,<br />Final polish, last bugs fall,<br />Six point seven calls.</em></p>



<p><em>Thank you to the following contributors for collaborating on this post:</em> <em><a href="https://profiles.wordpress.org/peterwilsoncc/" class="mention"><span class="mentions-prefix">@</span>peterwilsoncc</a>, <a href="https://profiles.wordpress.org/joedolson/" class="mention"><span class="mentions-prefix">@</span>joedolson</a></em>, <a href="https://profiles.wordpress.org/sabernhardt/" class="mention"><span class="mentions-prefix">@</span>sabernhardt</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, 05 Nov 2024 17:02:15 +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:"David Baumwald";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:84:"Do The Woo Community: Do the Woo WooSesh Recap, Day 2, with Robbie, Marcus and Brian";s:7:"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=86634";s:7:"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://dothewoo.io/do-the-woo-woosesh-recap-day-2-with-robbie-marcus-and-brian/";s: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:228:"The episode covers insights from WooSesh on motion design, e-commerce localization, accessibility, payment security, customer success, and lifetime licenses in plugin development, emphasizing enhancing user experience and trust.";s: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, 05 Nov 2024 10:20:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:100:"WordPress Foundation: Kim Parsell Memorial Scholarship Expands to WordCamp Asia and WordCamp Europe!";s:7:"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:42:"https://wordpressfoundation.org/?p=1194089";s:7:"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:120:"https://wordpressfoundation.org/news/2024/kim-parsell-memorial-scholarship-expands-to-wordcamp-asia-and-wordcamp-europe/";s: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:2835:"<p>We are thrilled to announce that following the latest WordPress Foundation Board meeting, the Kim Parsell Memorial Scholarship will now be available for WordCamp Asia and WordCamp Europe, in addition to WordCamp US. This expansion honors Kim’s legacy and her dedication to inclusivity and diversity within the WordPress community, making it possible for more community members to attend these inspiring events.</p>



<p>The scholarship is designed to support those who are passionate about contributing to WordPress, especially individuals who might otherwise face financial barriers to attending. By extending the scholarship to WordCamp Asia and WordCamp Europe, we aim to further empower community members around the globe to engage with and grow the WordPress community.</p>



<h3 class="wp-block-heading"><strong>Scholarship Requirements and Application</strong></h3>



<p>The requirements for applying and the application forms for WordCamp Asia and WordCamp Europe are available below.</p>



<p><strong>Eligibility Information</strong></p>



<p>There is one scholarship position available to each flagship event (WordCamp Asia, Europe and WordCamp US). To be considered, applicants must meet the following criteria:&nbsp;</p>



<ul class="wp-block-list">
<li>Is a woman</li>



<li>Is an active contributor to the WordPress project</li>



<li>Has never attended WordCamp Asia/Europe before</li>



<li>Requires financial assistance to attend WordCamp Asia/Europe 2025</li>
</ul>



<p>If you meet the above requirements and would like to be considered, please apply as soon as possible. Applications will be accepted until the closing date of 30 November 2024 for both WordCamp Asia and WordCamp Europe.&nbsp;</p>



<p>All applicants will receive notification by December 21, 2024.</p>



<p>For more information, please visit the WordPress Foundation’s page <a href="https://wordpressfoundation.org/projects/kim-parsell-memorial-scholarship/">about the Kim Parsell Memorial Scholarship</a>.</p>



<div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://wordcampcentral.survey.fm/wcasia-2025-kim-parsell-scholarship-application">Kim Parsell Memorial Scholarship: WcAsia Application</a></div>



<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://wordcampcentral.survey.fm/wceu-2025-kim-parsell-scholarship-application">Kim Parsell Memorial Scholarship: WcEU Application</a></div>
</div>



<p></p>



<p>Stay tuned, as applications for the Kim Parsell Memorial Scholarship for WordCamp US will open in the coming months!</p>



<p>We look forward to welcoming more of you to these incredible WordPress events and celebrating Kim’s legacy together.</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, 04 Nov 2024 16:43:16 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Isotta Peira";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:88:"Do The Woo Community: Do the Woo WooSesh Recap, Day 1, with Courtney, Jonathan and Brian";s:7:"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=86621";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"https://dothewoo.io/do-the-woo-woosesh-recap-day-1-with-courtney-jonathan-and-brian/";s: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:150:"In this episode, hosts recap WooSesh day one, focusing on WooCommerce's rebranding, UI enhancements, community engagement, and enterprise scalability.";s: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, 04 Nov 2024 13:40:50 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:48:"WpOrg\Requests\Utility\CaseInsensitiveDictionary":1:{s:7:"*data";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 27 Nov 2024 04:49:19 GMT";s:12:"content-type";s:8:"text/xml";s:13:"last-modified";s:29:"Wed, 27 Nov 2024 04:30:29 GMT";s:4:"vary";s:15:"Accept-Encoding";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:16:"content-encoding";s:2:"br";s:7:"alt-svc";s:19:"h3=":443"; ma=86400";s:4:"x-nc";s:9:"HIT ord 2";}}s:5:"build";i:1732621161;s:21:"cache_expiration_time";i:1732726159;s:23:"__cache_expiration_time";i:1732726159;}