


<h3 class="wp-block-heading"><strong>10. Link in Bio from Later</strong></h3>



<img width="1264" height="759" src="https://blog.gravatar.com/wp-content/uploads/2024/10/link-in-bio-by-later-homepage.png" alt="Link in Bio by Later homepage" class="wp-image-2321" />



<p><a href="https://later.com/link-in-bio/">Later&#8217;s Link in Bio</a> tool is part of a larger social media management platform, with a strong focus on Instagram and TikTok integration. This tool goes beyond simple link sharing to offer a more comprehensive social media solution.</p>



<p>Key features of Later&#8217;s Link in Bio include:</p>



<ul class="wp-block-list">
<li>Customizable link pages to showcase your content.</li>



<li>Shoppable Instagram feed for easy product promotion.</li>



<li>Featured Banner to highlight your top content.</li>



<li>Ability to personalize the title tag and meta description for SEO.</li>



<li>Detailed analytics for link and post-performance tracking.</li>
</ul>



<p>One of Later&#8217;s Link in Bio’s best additions is its easy integration with Later&#8217;s broader social media management features. This allows for a more cohesive approach to your social media strategy. The tool also offers <a href="https://mailchimp.com/">Mailchimp</a> integration, enabling easy email list building.</p>



<p>Later&#8217;s Link in Bio is particularly well-suited for Instagram-focused creators and businesses, as well as eCommerce brands leveraging social media for sales. Its shoppable Instagram feed feature can significantly improve the path from post to purchase.</p>



<p>Later offers a free plan that includes basic Link in Bio features. For those needing more comprehensive tools, paid plans are available, unlocking the full potential of <a href="https://later.com/pricing/">Later&#8217;s social media management platform</a>.</p>



<h2 class="wp-block-heading"><strong>Maximizing your digital identity: Why Gravatar stands out from the crowd</strong></h2>



<p>While all these alternatives offer unique features, Gravatar stands out as a comprehensive digital identity hub that allows you to create and manage a consistent, verified online presence across the entire web. It comes with a <a href="https://blog.gravatar.com/2024/06/26/link-your-gravatar-profile-with-a-free-custom-domain/">free custom domain</a> and many premium features that you usually have to pay extra for.&nbsp;</p>



<p>The &#8220;update once, sync everywhere&#8221; feature saves time and ensures consistency across the web. This means your avatar and profile information automatically appear on Gravatar-enabled sites, maintaining a unified digital identity.</p>



<p>The verified links feature serves as a simpler alternative to Linktree, offering similar functionality but within the Gravatar ecosystem. This verification builds trust with profile visitors, reducing the risk of phishing or misrepresentation.</p>



<p>For those already using Gravatar, adding and rearranging links within the same profile where their avatar is hosted is convenient and ensures consistency without needing another service. Plus, the ability to manage multiple identities linked to different email addresses offers flexibility for personal and professional use.</p>



<p>Gravatar empowers users to control their online presence across the entire web, not just on social media platforms. It&#8217;s the foundation of a decentralized digital identity, giving you more control over how you&#8217;re represented online.</p>



<h2 class="wp-block-heading"><strong>Beyond basic links: Set up your ideal Linktree alternative today</strong></h2>



<p>As we&#8217;ve seen, Linktree alternatives offer more than just link aggregation. They provide robust tools for managing your online presence across platforms. Whether you prioritize customization, analytics, or e-commerce integration, there&#8217;s an option tailored to your needs.</p>



<p>When choosing your ideal alternative, think about how it aligns with your long-term online strategy. Look for tools that suit your primary goal, platform, and budget, can grow with your needs, and offer flexibility in customization and integration.</p>



<p>One standout (and 100% free) solution is <a href="https://gravatar.com/">Gravatar</a>. It offers features like sharing your social media profiles, portfolio, website, and other relevant links easily, as well as multiple identity management and privacy controls, all while maintaining a consistent online presence.</p>



<p>Gravatar uniquely integrates with thousands of platforms like GitHub, Slack, and WordPress. This means your information and avatar are potentially pulled from your Gravatar profile into platforms you use every day, ensuring your identity is consistent across the web.</p>



<p>Ready to take control of your online presence? <a href="https://gravatar.com/profile">Create your Gravatar profile today</a>!</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 21 Oct 2024 15:01:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:34;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"Do The Woo Community: Future Investments from WooCommerce: What to Expect";s: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=86201";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://dothewoo.io/blog/future-investments-from-woocommerce-what-to-expect/";s: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:366:"As WooCommerce continues to grow as a leading platform for online commerce, here are several key areas that Beau Lebens mentioned in a recent podcast episode about where the company is focusing its future investments. These developments are aimed at enhancing both the merchant experience and the overall ecosystem for developers and businesses alike. Here [&#8230;]";s: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, 21 Oct 2024 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: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: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:94:"WPTavern: WP Fusion Lite Plugin Removed From WordPress.com Following a Cease and Desist Letter";s: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=175800";s: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:105:"https://wptavern.com/wp-fusion-lite-plugin-removed-from-wordpress-com-following-a-cease-and-desist-letter";s: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:4846:"<p>Automattic has agreed to <a href="https://wpfusion.com/business/regarding-our-cease-and-desist-letter-to-automattic/">remove the WP Fusion Lite Plugin</a> from WordPress.com following a Cease and Desist letter filed by the plugin&#8217;s creator Jack Arturo on October 12, 2024. The letter accused Automattic and WordPress.com of unauthorized trademark usage by displaying the plugin on WordPress.com.</p>



<p><a href="https://wordpress.org/plugins/wp-fusion-lite/">WP Fusion Lite</a> is a WordPress plugin that connects WordPress websites to popular CRM systems and marketing automation tools. It has over 5,000 Active Installs in the WordPress.org Repository.&nbsp;</p>



<p>Jack Arturo, founder of Very Good Plugins LLC and creator of WP Fusion plugin, <a href="https://x.com/verygoodplugins/status/1845246925886353795">filed the Cease and Desist letter</a> stating: “As the owner of the federally registered trademark WP FUSION (U.S. Registration No. 6,052,437), which was registered on May 12, 2020, and is associated with software services including website integration with customer relationship management (CRM) and marketing automation systems, I believe that your continued use and distribution of the plugin under the WP Fusion name is a clear infringement of my exclusive trademark rights under U.S. law.</p>



<p>The plugin you are hosting creates a likelihood of confusion, mistake, or deception regarding the source, sponsorship, or affiliation of the WP Fusion brand, which could damage the reputation and goodwill associated with my brand. Please be advised that I will vigorously defend my trademark rights to the fullest extent of the law.”</p>



<p>The letter included three key demands:</p>



<ul class="wp-block-list">
<li>Immediately remove the &#8220;WP Fusion Lite&#8221; plugin from WordPress.com.</li>



<li>Cease any use of trademarks, logos, or names confusingly similar to WP Fusion.</li>



<li>Provide written confirmation within ten business days that these actions have been taken.</li>
</ul>



<p>He also warned that if the above requests are not met, he would “pursue all available legal remedies, including but not limited to seeking injunctive relief, damages, and attorney&#8217;s fees for trademark infringement.”&nbsp;</p>



<h3 class="wp-block-heading">Automattic&#8217;s Response on October 18, 2024 </h3>



<p>Automattic responded, saying they “would like to resolve this matter swiftly and amicably, and to that end WP Fusion Lite is no longer listed on WordPress.com and we have disabled its landing page. It is no longer available to WordPress.com customers nor will it appear in search results. We trust this resolves your concerns.”</p>



<p>However, Automattic disagreed with the trademark infringement claim, stating: “Automattic disagrees with your assertions that it has infringed the intellectual property rights of Very Good Plugins, LLC. The listing uses the WPFUSION trademark solely and only to the extent necessary to identify the genuine WPFUSION plugin, which constitutes nominative fair use under applicable law.”</p>



<p>Since last year, WordPress.com has displayed all WP.org plugins in a private directory for its hosting customers, a practice that has raised <a href="https://wptavern.com/developers-raise-concerns-about-wordpress-com-plugin-listings-outranking-wordpress-org-on-google">concerns among developers</a>. They worry that WordPress.com plugin listings are outranking WordPress.org on Google, causing confusion for users. Many users, unaware of the distinction between WP.com and WP.org, click the WP.com link, which prompts them to create an account and sign up for premium hosting. Jack mentioned that this confusion was affecting his customers, who had already purchased the pro version of the plugin.</p>



<p>Automattic has maintained that featuring plugins on WP.com benefits authors by increasing exposure. They responded to Jack’s complaints on <a href="https://x.com/automattic/status/1845252369174364554">X</a>, asking, “So, to clarify, you&#8217;d like us to hide your plugin from the ~248M registered users on @wordpressdotcom?” Matt had also <a href="https://x.com/photomatt/status/1701973661110915205">tweeted</a> last year, “It&#8217;s providing distribution to the plugin authors, literally millions and millions of installs.”</p>



<p>Jack <a href="https://x.com/verygoodplugins/status/1845266438539382989">clarified</a> that he has no objection to others mirroring his plugins, except for Automattic. Also, WP Fusion Pro does not require the free version to function, and they have been delivering updates to pro customers via their own servers for many years.</p>



<p>The issue has been resolved, but it remains to be seen whether more plugin authors will choose to remove their plugins from WP.com.</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, 21 Oct 2024 03:19: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: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: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:26:"Matt: My Freedom of Speech";s: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=128329";s: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:38:"https://ma.tt/2024/10/first-amendment/";s: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:2208:"<p><a href="https://wpengine.com/">WP Engine</a> has <a href="https://www.theverge.com/2024/10/18/24273448/wp-engine-injunction-matt-mullenweg-wordpress-resources">filed hundreds pages of legal documents seeking an injunction against me and Automattic</a>. They say this is about community or some nonsense, but if you look at the core, what they&#8217;re trying to do is ask a judge to curtail my First Amendment rights.</p>



<p>The First Amendment is the basis of our democracy. It is <em>inconvenient</em> and <em>important</em>. It&#8217;s also short, so I&#8217;m going to quote the First Amendment in its entirety:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.</p>
</blockquote>



<p>This means that, <a href="https://en.wikipedia.org/wiki/United_States_free_speech_exceptions">with rare exceptions</a>, the government cannot tell you not to say something.</p>



<h2 class="wp-block-heading">Freedom of Speech is not Freedom of Reach</h2>



<p>The First Amendment says I should be able to state facts and my opinions about WP Engine. However, the <a href="https://www.nytimes.com/">New York Times</a> is not required or compelled to publish them in their newspaper and distribute them to their subscribers.</p>



<p>WP Engine is free to publish whatever <a href="https://en.wikipedia.org/wiki/GNU_General_Public_License">GPL code</a> they want to the world. <a href="https://wordpress.org/">WordPress.org</a> should not be compelled to distribute it or provide it free hosting.</p>



<h2 class="wp-block-heading">Quiet For A While</h2>



<p>After this post, I will refrain from personally commenting on the WP Engine case until a judge rules on the injunction. I will continue to exercise my First Amendment rights to promote others&#8217; speech. However, <strong>I hope others speak up on our battle with WP Engine, and I will boost their speech wherever I can</strong>.</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, 20 Oct 2024 21:53:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:24:"Matt: Cloudflare Stories";s: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=128322";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:41:"https://ma.tt/2024/10/cloudflare-stories/";s: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:1102:"<p>There are two great Cloudflare-related stories published this weekend.</p>



<p><a href="https://www.wired.com/story/plaintext-you-can-now-see-the-code-that-ended-apartheid/">The first is Steven Levy&#8217;s incredible story about Tim Jenkin</a>, who created a secure communication protocol for the African National Congress to overthrow the apartheid regime in South Africa. Cloudflare&#8217;s CTO, <a href="https://jgc.org/">John Graham-Cumming</a>, later helped break past the cryptography system&#8217;s lost password, which he <a href="https://blog.jgc.org/2024/09/cracking-old-zip-file-to-help-open.html">blogged about with some technical detail here</a>.</p>



<p>Second, my dear friend Om Malik <a href="https://crazystupidtech.com/archive/future-of-internet-in-the-age-of-ai/">published a great conversation with Cloudflare CEO Matthew Prince in his new newsletter Crazy Stupid Tech</a>. <a href="https://x.com/eastdakota">Matthew</a> and Om are influential thinkers to listen to, and their discussion contains a lot of interesting nuance about networks, censorship, and sovereignty. </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, 20 Oct 2024 04:57:37 +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: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:120:"Gutenberg Times: Source of Truth WordPress 6.7, Mastering Theme.json, Dev Notes Galore and more — Weekend Edition #308";s: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=30448";s: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/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/";s: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:17032:"<p>Hi there, </p>



<p>WordPress 6.7 RC1 is scheduled for October 22, 2024. That&#8217;s also the occasion to publish the Fieldguide listing the big and small changes coming with the new version. Below I listed the Devnotes that are already available. <strong>Anne McCarthy</strong> published the 6,450-words <a href="https://gutenbergtimes.com/6-7-source-of-truth/"><strong>Source of Truth</strong></a> on this site as well. </p>



<p>It&#8217;s going to be a busy three weeks until the final release on November 12, 2024. </p>



<p>Enjoy exploring the new features and update in WordPress and have a great weekend! </p>



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



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



<ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#0-word-press-release-information">Developing Gutenberg and WordPress</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#0-p">Plugins, Themes, and Tools for #nocode site builders and owners</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#2-word-press-6-0-1-and-6-1-scheduled">Theme Development for Full Site Editing and Blocks</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#3-building-themes-for-fse-and-word-press">Building Blocks and Tools for the Block editor</a></li></ol>
</div></div>



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



<p><a href="https://wordpress.org/news/2024/10/wordpress-6-7-beta-3/">WordPress 6.7 Beta 3</a> has been released and the first <strong>Dev Notes</strong> are being published: </p>



<ul class="wp-block-list">
<li><a href="https://make.wordpress.org/core/2024/10/15/subscribe-to-changes-in-the-interactivity-api-state-and-context-on-client-side-navigation-in-6-7/">Subscribe to changes in the Interactivity API state and context on client-side navigation in 6.7</a>  </li>



<li><a href="https://make.wordpress.org/core/2024/10/14/updates-to-script-modules-in-6-7/">Updates to Script Modules in 6.7</a> </li>



<li><a href="https://make.wordpress.org/core/2024/10/17/roster-of-design-tools-per-block-wordpress-6-6-edition-2/">Roster of design tools per block (WordPress 6.7 edition)</a></li>



<li><a href="https://make.wordpress.org/core/2024/10/17/updates-to-the-html-api-in-6-7/">Updates to the HTML API in 6.7</a></li>



<li> <a href="https://make.wordpress.org/core/2024/10/17/new-block-type-registration-apis-to-improve-performance-in-wordpress-6-7/">New block type registration APIs to improve performance in WordPress 6.7</a></li>



<li><a href="https://make.wordpress.org/core/2024/10/18/auto-sizes-for-lazy-loaded-images-in-wordpress-6-7/">Auto Sizes for Lazy Loaded Images in WordPress 6.7</a></li>



<li><a href="https://make.wordpress.org/core/2024/10/18/post-editor-iframing-with-meta-boxes-in-wordpress-6-7/">Post Editor iframing with meta boxes&nbsp;in WordPress 6.7</a></li>
</ul>



<img width="652" height="374" src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/376215782-1f8a8a02-f3fd-464d-a543-00f7a90dd1eb.png?resize=652%2C374&ssl=1" alt="Highlights Grid WordPress 6.7" class="wp-image-30498" />



<p><strong>Anne McCarthy</strong> found a <a href="https://nomad.blog/2024/10/18/new-location-for-the-6-7-source-of-truth/">new location for the 6.7 Source of&nbsp;Truth</a> on the Gutenberg Times.  The <strong><a href="https://gutenbergtimes.com/6-7-source-of-truth/">Source of Truth</a></strong> is a tool for others who educate WordPress users on the new updates. &#8220;It’s a foundational resource but, it’s so long and detailed, it needs to be repackaged to be useful in each space.&#8221; McCarthy wrote. </p>



<a href="https://gutenbergtimes.com/6-7-source-of-truth/"><img width="652" height="365" src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/6.7-Source-of-Truth-Featured-Image.png?resize=652%2C365&ssl=1" alt="White text on blue background with a paintbrush mark saying WordPress 6.7 Source of Truth" class="wp-image-30499" /></a>



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



<div class="wp-block-group has-light-background-background-color has-background"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained">
<p>🎙️ Latest episode: <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-110-gutenberg-19-5-wordpress-6-7-create-block-theme-plugin/">Gutenberg Changelog #110 – Gutenberg 19.5, WordPress 6.7, Create Block Theme Plugin and a Thousand Block Themes at the Repository</a> with Joni Halabi </p>



<img width="652" height="184" src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/Screenshot-2024-10-25-at-17.17.35.png?resize=652%2C184&ssl=1" alt="" class="wp-image-30608" />
</div></div>



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



<p><strong>Joen Asmussen</strong> shared a list of work done by the WordPress design team: <a href="https://make.wordpress.org/design/2024/10/18/design-share-66-oct-7-oct18/"><strong>Design Share #66 (Oct 7-Oct18)</strong></a>. He highlights: </p>



<ul class="wp-block-list">
<li>Admin bar evolution</li>



<li>Unseen icon update</li>



<li>Navigation: Provide fallback when menu was deleted</li>



<li>Admin themes</li>



<li>Update component: Combobox</li>



<li>Storybook: Color</li>



<li>WordPress Photo Directory</li>



<li>5FTF. Sponsorship</li>
</ul>



<a href="https://make.wordpress.org/design/2024/10/18/design-share-66-oct-7-oct18/"><img width="652" height="278" src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/5FTF-Sponsorship.webp?resize=652%2C278&ssl=1" alt="" class="wp-image-30490" /></a>



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



<p>In his video, <a href="https://www.youtube.com/watch?v=v5drhUktS_0"><strong>WordPress, How to build Complex Layouts in the Block Editor </strong></a><strong>Elliot Richmond</strong> showed how easy it is now to build websites with WordPress, even if the layout seems a bit more challenging. I liked how you get to hear about the reasoning of design choices and also how Richmond decides on the tools to use. In the methods of the Speed building challenge, Richmond takes you along as he rebuilds the Blookup.com website.</p>



<img width="652" height="326" src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/Screenshot-2024-10-16-at-15.56.32.png?resize=652%2C326&ssl=1" alt="Screenshot of site building video" class="wp-image-30483" />



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



<p><strong><a href="https://x.com/robinpietersen">Robin Pietersen</a> </strong>announced a few more blocks for FooEvents. In his post <a href="https://www.fooevents.com/introducing-the-new-fooevents-calendar-and-attendee-listing-blocks/?s=09"><strong>Introducing the New FooEvents Calendar and Attendee Listing Blocks</strong></a> you can take a look at the new FooEvents Calendar Block and FooEvents Attendee Listing Block, as well as updates to the FooEvents Express Check-ins plugin and FooEvents Ticket Importer.</p>



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



<p><a href="https://x.com/ronaldhuereca"><strong>Ronald Huereca</strong></a> t<a href="https://x.com/MediaRonLLC/status/1847527385823900064">weeted he</a> &#8220;quietly released Photo Block earlier this week.&#8221;  An official announcement post is forthcoming. If you want to check out the new Photo Block, it&#8217;s available from the WordPress repository.  The <a href="https://docs.dlxplugins.com/photo-block">documentation page</a> is already available, showing off the plugin&#8217;s features, that enhance the image core block: Cropping, Dimension support, Image Sizing and Object Fit, Add CSS Gram Effects, multiple caption variations and overlay support. It&#8217;s definitely worth exploring if you have a wider range of image needs. </p>



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



<p><strong>Save The date!</strong> WordPress 6.7 and the new Twenty Twenty-Five theme are just weeks away. Theme Dev Leads,<strong> <a href="https://x.com/carolinapoena">Carolina Nymark</a></strong> and <a href="https://x.com/juanfraa"><strong>Juan Aldasoro</strong></a> will join Developer Hours on <strong>Oct. 29 at 15:00 UTC </strong>for an in-depth look at the theme’s technical details and features. <a href="https://www.meetup.com/learn-wordpress-online-workshops/events/304044317/"><strong>Developer Hours: Exploring the Twenty Twenty-Five Theme</strong></a></p>



<a href="https://www.meetup.com/learn-wordpress-online-workshops/events/304044317/"><img width="600" height="338" src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/DH-October-29-Carolina-Nymark-Juanfra-Aldasoro.webp?resize=600%2C338&ssl=1" alt="" class="wp-image-30507" /></a>



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



<p>If you are starting out building a Block Theme, it can be a bit overwhelming with the number of details you might have to consider. In <a href="https://developer.wordpress.org/news/2024/10/17/mastering-theme-json-you-might-not-need-css/"><strong>Mastering theme.json: You might not need CSS</strong></a>, <strong>Justin Tadlock</strong> gives you a walkthrough of many tips, tricks, and techniques for using theme.json and style variations to their full extent.</p>



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



<p><strong>Carlos Daniele</strong> created <a href="https://kinsta.com/blog/twenty-twenty-five-theme/"><strong>A developer’s overview of Twenty Twenty-Five, the next default WordPress theme</strong></a>. &#8220;Twenty Twenty-Five provides an excellent example of the philosophy of democratization of design, and this article will show you its structure in detail.&#8221; he wrote. Daniele looks at the code and explains some of the concepts that were incorporated into the new default theme, especially Section styles and Template patterns. </p>



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



<p>In <a href="https://kinsta.com/blog/wordpress-typography-theme-json/"><strong>Revolutionizing WordPress typography with full site editing and theme.json</strong></a> <strong>Jeremy Holcombe</strong> takes a comprehensive journey through the tools and features of the Site editor and block themes on working with typography on the web and how users can make their typography choices and add them to their site. </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 2024&#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. 2024 on. Updated by yours truly. The previous years are also available: <strong><strong><a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/">2020</a>&nbsp;|&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2021/">2021</a></strong>&nbsp;|&nbsp;<strong><a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2022/">2022</a></strong></strong>&nbsp;|&nbsp;<strong><a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/gutenberg-index-2023">2023</a></strong></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>For the first time, Developer Hours were streamed from YouTube directly, and it made a difference in the numbers of people reached. If you missed it, here is the recording: <a href="https://www.youtube.com/watch?v=6lBIkf3xNDw"><strong>How to Simplify Client Editing in WordPress</strong></a> with <strong>Nick Diego</strong>, <strong>Ryan Welcher</strong> and <strong>Jamie Marsland</strong>. </p>


<div width="100%" class="wp-block-newsletterglue-showhide ng-block">
<div class="wp-block-embed__wrapper">
<div class="toolbelt-video-wrapper"></div>
</div>
</div>


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



<p><a href="https://www.youtube.com/watch?v=JrOpsePAX3c">In his Live stream</a>,<strong> Ryan Welcher</strong>, explored if he could <strong>replace custom blocks with Block Bindings</strong>. It&#8217;s a continuation of the show from last week. <a href="https://www.youtube.com/watch?v=NIDS4PFUHBI"><strong>Looking at the Block Bindings API coming in WordPress 6.7</strong></a></p>



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



<p><a href="https://x.com/3LPU4S"><strong>Alfredo Navas-Fernandini</strong></a> found <a href="https://elpuas.com/blog/you-might-not-need-a-custom-block-the-block-variations-api/"><strong>You Might Not Need a Custom Block: The Block Variations API</strong></a> and teaches you how to create Block variations with a common examples, a Call-to-Action block, and a Team query block,  assembled from core blocks. In the same mind set, Navas posted earlier <a href="https://elpuas.com/blog/you-might-not-need-a-custom-block-the-block-styles-api/">You Might Not Need a Custom Block: The Block Styles API</a>, showing ways to create more buttons styles and a custom header block. </p>



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



<p>Now also available via <a href="https://playground.wordpress.net/?blueprint-url=https://gutenbergtimes.com/wp-content/uploads/2020/11/playnightly.json">WordPress Playground</a>. There is no need for a test site locally or on a server. Have you been using it? <a href="mailto:pauli@gutenbergtimes.com">Email me </a>with your experience</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-center has-small-font-size"><em>Questions? Suggestions? Ideas? </em><br /><em>Don&#8217;t hesitate to send <a href="mailto:pauli@gutenbergtimes.com">them via email</a> or</em><br /><em> send me a message on WordPress Slack or Twitter @bph</em>.</p>



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



<p class="has-text-align-center has-small-font-size">For questions to be answered on the <a href="http://gutenbergtimes.com/podcast">Gutenberg Changelog</a>, <br />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" />



<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 <br />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, 19 Oct 2024 08:30: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: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: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:82:"WordPress.org blog: Expanding Our Code of Conduct to Protect Private Conversations";s: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=17994";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wordpress.org/news/2024/10/protect-private-conversations/";s: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:2935:"<p>At the heart of our community is our shared pledge to create a space that is harassment-free, welcoming, and inclusive for all. Our <a href="https://make.wordpress.org/handbook/community-code-of-conduct/">Community Code of Conduct</a> already outlines a clear set of expectations, while also providing examples of unacceptable actions. Today, we are reinforcing our values by adding another element to our list of unacceptable behaviors: Publishing private messages without consent.</p>



<h2 class="wp-block-heading">Why This Addition Matters</h2>



<p>The relationships we build within our community often involve private discussions. These conversations may involve sensitive matters, personal experiences, or simply casual exchanges. Regardless of the content, every individual should feel confident that their private communications will remain private unless they grant explicit permission to share them.</p>



<p>Sharing private messages without consent is a breach of trust that can also lead to unintended harm, including emotional distress or misrepresentation. When members of our community feel they cannot trust others in their personal conversations, it undermines the collaborative spirit that is crucial to our collective success.</p>



<h2 class="wp-block-heading">How This Change Protects the Community</h2>



<p>By explicitly addressing the publication of private messages without consent, we are reinforcing an existing unacceptable behavior in our Community Code of Conduct: Other conduct which could reasonably be considered inappropriate in a professional setting. Sharing private communications without permission is a clear violation of professional integrity.</p>



<p>This new addition ensures that private messages receive the same level of protection as personal information and that sensitive communications shared in confidence will not be disclosed without prior consent. An important exception to this is when sharing private messages is necessary for reporting incidents or concerns to the <a href="https://make.wordpress.org/community/handbook/irt/">Incident Response Team</a>, as part of our commitment to maintaining a safe and respectful environment.</p>



<p>Ultimately, this change encourages honest, constructive engagement across all levels of participation.</p>



<h2 class="wp-block-heading">Moving Forward Together</h2>



<p>The strength of our community lies in the trust we place in one another. By clarifying and reinforcing our expectations, we are taking another step toward maintaining an inclusive, respectful, and safe environment for everyone.This new addition will take effect immediately, and violations will be handled in accordance with our existing <a href="https://make.wordpress.org/handbook/community-code-of-conduct/#enforcement">enforcement guidelines</a>. Together, we can ensure our community remains a place of collaboration, trust, and mutual respect.</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, 19 Oct 2024 00:51:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:47:"WordPress.org blog: WordPress Thanks Salesforce";s: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=18012";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2024/10/thank-you-salesforce/";s: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:2643:"<p>In the midst of our legal battles with Silver Lake and WP Engine, I wanted to take a moment to highlight something positive.</p>



<p>Because of my friendships with the co-founders of Slack, <a href="https://x.com/stewart">Stewart Butterfield</a> and <a href="https://x.com/iamcal">Cal Henderson</a>, WordPress.org has had a free version of the Pro version of Slack since they started in 2009. We switched from IRC to Slack, and it was like superpowers were unlocked for our team.</p>



<p>Over the past 10 years, <a href="https://slack.com/">Slack</a> has been our secret weapon of productivity compared to many other open source projects. Its amazing collaboration features have allowed us to scale WordPress from running just a few blogs to now powering around 43% of all websites in the world, almost 10 times the runner-up in the market.</p>



<p>As we have scaled from very small to very large, Slack has scaled right alongside us, seemingly effortlessly. WordPress.org currently has 49,286 users on its <a href="https://slack.com/pricing">Slack Business+ instance</a>, which would cost at least $8.8M/yr if we were paying. (And we may need to go to their enterprise grid, to support e-discovery in the lawsuit attacks from WP Engine, which would cost even more.) </p>



<p>This incredible generosity was continued by the enlightened leadership of Marc Benioff at Salesforce when they bought Slack in 2020. However, it has not been widely known or recognized on our <a href="https://wordpress.org/five-for-the-future/">Five for the Future page</a>, which only highlights self-reported contributor hours and doesn&#8217;t mention Salesforce at all.</p>



<p>This is a grave error, and we are correcting it today. Going forward:</p>



<ul class="wp-block-list">
<li>I would like every business in the world to see the amazing collaboration and productivity gains Slack has enabled for our community of tens of thousands of volunteers worldwide and <a href="https://slack.com/">consider adopting it for their own business</a>.</li>



<li>Salesforce will have a complimentary top sponsor slot at our flagship WordCamp events in the <a href="https://us.wordcamp.org/">United States</a>, <a href="https://europe.wordcamp.org/">Europe</a>, and <a href="https://asia.wordcamp.org/">Asia</a>, which attract thousands of people each.</li>



<li>We will update our <a href="https://wordpress.org/five-for-the-future/">Five for the Future program</a> to reflect contributions such as Salesforce&#8217;s going forward.</li>
</ul>



<p>We just want to repeat: Thank you. We hope to deepen our partnership with Salesforce in the future.</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, 18 Oct 2024 20:17: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:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:46:"Gutenberg Times: WordPress 6.7 Source of Truth";s: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=30495";s: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:47:"https://gutenbergtimes.com/6-7-source-of-truth/";s: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:81221:"<p>After quite a few rounds of sharing the <a href="https://nomad.blog/tag/source-of-truth/">Source of Truth on my personal site</a>, Birgit Pauli-Haack, the wonderful creator and curator of Gutenberg Times, offered up this space for me to share this resource. Going forward, we&#8217;re going to experiment with it continuing to be shared here in hopes of reaching more content creators, educators, and general WordPress enthusiasts who want to know every detail of the latest &amp; greatest of WordPress.</p>



<p>As always, I’d recommend staying up to date on the&nbsp;dev notes&nbsp;as those are rolling out along with&nbsp;reviewing the Field Guide when it comes out.</p>



<p><strong>As a reminder, this is not meant to replace dev notes or the release-specific field guides, which serve important roles and are separate efforts. </strong>I mainly see it as for folks close to the WordPress release itself and educating others than I see it as something broadly helpful for the average WordPress user. It’s a foundational resource but, it’s so long and detailed, it needs to be repackaged to be useful in each space. Feedback is welcomed for improvements for this version and for future versions as I consider how best to share this information.</p>



<p>Big thank you to everyone who helped in big and small ways.</p>



<img width="652" height="374" src="https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/376215782-1f8a8a02-f3fd-464d-a543-00f7a90dd1eb.png?resize=652%2C374&ssl=1" alt="" class="wp-image-30498" />



<ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#changelog">Changelog</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#important-note-guidelines">Important Note/Guidelines</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#overview">Overview </a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#important-links">Important links:</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#6-7-assets">6.7 assets: </a></li></ol></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#tags">Tags</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#priority-items-for-6-7">Priority Items for 6.7</a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#new-default-theme-twenty-twenty-five">New default theme: Twenty Twenty-Five</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#refining-data-views">Refining Data Views </a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#enhancements">Enhancements</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#expanded-extensibility">Expanded extensibility </a></li></ol></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#consolidating-and-expanding-block-supports">Consolidating and expanding block supports</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#block-bindings-improvements-including-ui-to-connect-blocks-and-custom-fields-developer-plugin-author-enterprise">Block Bindings improvements, including UI to connect blocks and custom fields [developer] [plugin author] [enterprise]</a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#ui-to-connect-blocks-and-custom-fields">UI to connect blocks and custom fields</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#new-apis-to-empower-extenders">New APIs to empower extenders</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#ux-improvements">UX improvements</a></li></ol></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#polishing-the-query-loop-block-with-a-focus-on-simplicity">Polishing the Query Loop block with a focus on simplicity</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#zoom-out-to-compose-with-patterns">Zoom out to compose with patterns</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#media-improvements">Media improvements</a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#support-for-heic-image-uploads">Support for HEIC image uploads</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#auto-sizes-for-lazy-loaded-images">Auto Sizes for Lazy-loaded Images</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#expanded-and-improved-background-image-support">Expanded and improved background image support</a></li></ol></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#view-meta-boxes-in-the-iframed-post-editor-plugin-author-enterprise">View meta boxes in the iframed Post Editor [plugin author] [enterprise]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#font-management-updates-end-user-theme-author">Font management updates [end user] [theme author]</a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#edit-and-apply-font-size-presets">Edit and apply font size presets </a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#consistent-interfaces">Consistent interfaces</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#font-library-enhancements">Font library enhancements</a></li></ol></li></ol></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#additional-items-for-6-7">Additional Items for 6.7</a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#template-registration-api-plugin-author-theme-author-developer">Template Registration API [plugin author] [theme author] [developer]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#preview-options-api-developer-plugin-author-enterprise">Preview Options API [developer] [plugin author] [enterprise]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#changes-to-heartbeat-api-to-lower-minimum-allowed-time-enterprise-plugin-author">Changes to Heartbeat API to lower minimum allowed time [enterprise] [plugin author] </a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#customize-heading-level-curation-developer">Customize heading level curation [developer]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#general-improvements">General improvements</a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#updated-order-of-editor-actions-for-a-clearer-sidebar">Updated order of editor actions for a clearer sidebar</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#opt-out-preference-for-choose-a-pattern-modal-when-adding-a-new-page">Opt out preference for &#8216;Choose a Pattern&#8217; modal when adding a new page</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#more-robust-saving">More robust saving</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#iterating-on-pattern-shuffling">Iterating on pattern shuffling</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#writing-flow-improvements">Writing flow improvements </a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#adding-block-examples-and-previews">Adding block examples and previews</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#site-editor-focused">Site Editor focused</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#other">Other</a></li></ol></li></ol></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#interactivity-api-iteration-bug-fixes-internal-refactor-and-new-apis-developer-plugin-author">Interactivity API iteration: bug fixes, internal refactor, and new APIs [developer] [plugin author]</a><ol><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#new-apis-getserver-state-getservercontext">New APIs: getServer State &amp; getServerContext</a></li></ol></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#updates-for-the-html-api-plugin-author-developer">Updates for the HTML API [plugin author] [developer] </a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#time-input-as-a-subcomponent-of-timepicker-developer-plugin-author">Time input as a subcomponent of TimePicker [developer] [plugin author]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#define-block-variations-via-a-php-file-developer-plugin-author">Define block variations via a PHP file [developer] [plugin author]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#override-styles-dynamically-plugin-author-developer">Override styles dynamically [plugin author] [developer]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#help-text-for-radiocontrol-options-developer-plugin-author">Help text for RadioControl options [developer] [plugin author]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#clearfix-for-the-post-content-block-theme-author-end-user">Clearfix for the Post Content block [theme author] [end user]</a></li><li><a class="wp-block-table-of-contents__entry" href="https://gutenbergtimes.com/6-7-source-of-truth/#continuing-to-improve-php-8-x-support">Continuing to improve PHP 8.x support</a></li></ol>



<h2 class="wp-block-heading" id="changelog"><strong>Changelog</strong></h2>



<p>Any changes will be catalogued here as the release goes on. </p>



<ul class="wp-block-list">
<li>Oct 21, 2024: added links to published Dev Notes</li>
</ul>



<h2 class="wp-block-heading" id="important-note-guidelines"><strong>Important Note/Guidelines</strong></h2>



<p><em>This is a public document so please be mindful of the fact that a wider audience than you might think can participate in what’s shared here 🙂&nbsp;</em></p>



<p><strong>Please do not copy and paste what is in this document </strong>since this will be shared with many people. This should be used to inspire your own content and to ensure that you have the best information about this release. If you do copy and paste, keep in mind that others might do the same, opening the door for some awkwardness around duplicated content out on the web.&nbsp;</p>



<ul class="wp-block-list">
<li>The document is shared publicly so be mindful of what you comment. The audience is large!</li>



<li>You will have Comment access but not edit access. This is intentional – please comment if you have any questions/concerns/feedback and I’ll follow up.&nbsp;</li>



<li>If there are drastic changes, this document will be updated and you will be alerted.</li>



<li>Each item has been tagged using best guesses with different high level labels so that you can more readily see at a glance who is likely to be most impacted.</li>



<li>Each item has a high-level description, visuals (if relevant), adoption strategy (if relevant), and key resources if you want to learn more.</li>
</ul>



<h2 class="wp-block-heading" id="overview"><strong>Overview&nbsp;</strong></h2>



<p>Along with a new default theme, there are new features, like the ability to zoom out to compose content with patterns, and new APIs, like the Template Registration API. More than anything though, this release brings refinement to how everything connects together to create a more seamless WordPress experience.</p>



<p>Of note, this release includes Gutenberg 18.6 &#8211; 19.3 and, for the first time, I used AI to help offer rewrites to different sections.&nbsp;</p>



<h3 class="wp-block-heading" id="important-links">Important links:</h3>



<ul class="wp-block-list">
<li><a href="https://make.wordpress.org/core/2024/09/03/roadmap-to-6-7/">Roadmap to 6.7</a>.</li>



<li><a href="https://make.wordpress.org/core/6-7/">6.7 Development Cycle information</a>.</li>



<li><a href="https://make.wordpress.org/core/2024/10/23/wordpress-6-7-field-guide/">6.7 Field Guide</a></li>



<li>What’s new for developers: <a href="https://developer.wordpress.org/news/2024/07/10/whats-new-for-developers-july-2024/">July</a>, <a href="https://developer.wordpress.org/news/2024/08/10/whats-new-for-developers-august-2024/">August</a>, <a href="https://developer.wordpress.org/news/2024/09/10/whats-new-for-developers-september-2024">September</a>, <a href="https://developer.wordpress.org/news/2024/10/10/whats-new-for-developers-october-2024/">October</a></li>
</ul>



<h3 class="wp-block-heading" id="6-7-assets">6.7 assets:&nbsp;</h3>



<p>To view all assets in this document, <a href="https://drive.google.com/drive/folders/1So-c8M-H45g_zyOZ8ACefZe-F-LD-8cq?usp=sharing">please review this drive folder</a>.&nbsp;</p>



<h2 class="wp-block-heading" id="tags"><strong>Tags</strong></h2>



<p>To make this document easier to navigate based on specific audiences, the following tags are used liberally:&nbsp;</p>



<p>[end user]: end user focus.&nbsp;</p>



<p>[theme author]: block or classic theme author.&nbsp;</p>



<p>[plugin author]: plugin author, whether block or otherwise.</p>



<p>[developer]: catch-all term for more technical folks.&nbsp;</p>



<p>[site admin]: this includes a “builder” type.&nbsp;</p>



<p>[enterprise]: specific items that would be of interest to or particularly impact enterprise-level folks</p>



<p><strong>If no tags are listed, it’s because the impact is broad enough to impact everyone equally.&nbsp;</strong></p>



<h2 class="wp-block-heading" id="priority-items-for-6-7"><strong>Priority Items for 6.7</strong></h2>



<h3 class="wp-block-heading" id="new-default-theme-twenty-twenty-five">New default theme: Twenty Twenty-Five</h3>



<p>6.7 marks the next edition of a default WordPress theme, designed to showcase the latest in WordPress and set a new standard for block themers. This year&#8217;s theme aims to cater to a wide range of bloggers. It’s designed for <strong>simple personal blogs</strong> like ma.tt, <strong>photo blogs</strong> focused on photography or portfolios, and more <strong>complex blogs</strong>, such as news sites that require a broader set of blocks and more complex content.&nbsp;</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1aZM2tL4Tt9IYMbULYJHEAUcp_CWwcb0V/view?usp=drive_link">demo</a> walking through the theme including style variations, template layouts, and page patterns.<br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> <em>Follow the </em><a href="https://github.com/WordPress/twentytwentyfive"><em>Twenty Twenty-Five GitHub repo</em></a><em> and </em><a href="https://make.wordpress.org/core/2024/08/15/introducing-twenty-twenty-five/"><em>read the announcement post</em></a><em> for more information.&nbsp;</em></p>



<h3 class="wp-block-heading" id="refining-data-views">Refining Data Views&nbsp;</h3>



<p>Following the launch of Data Views in 6.5 and advancements in 6.6, this release is focused on refining the experience with a few new features planned. The aim is to make these views more flexible for customization and more functional to use.&nbsp;</p>



<h4 class="wp-block-heading" id="enhancements">Enhancements</h4>



<ul class="wp-block-list">
<li><a href="https://github.com/WordPress/gutenberg/issues/60630">Ability to set the density of information in the grid layout</a>.</li>



<li><a href="https://href.li/?https://github.com/WordPress/gutenberg/pull/63203">Option to hide/show the filters in the user interface</a> to add more optionality and reduce clutter.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/63416">Ability to customize the column order in table views</a> with the <a href="https://github.com/WordPress/gutenberg/pull/64646">move left/right controls always available</a>, including in the <a href="https://github.com/WordPress/gutenberg/pull/64381">new view configuration UI to manage order across all columns</a>.&nbsp;</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/63487">Make the Grid layout aspect ratio user configurable</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/64175#top">Graduate data view options out of a menu to allow more design expression</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/63309">See author’s avatar next to publication status in Pages</a>.</li>



<li>Mobile responsiveness improvements, including fixes like <a href="https://github.com/WordPress/gutenberg/pull/63203">moving the filtering UI into a toggle-able panel to improve experience on narrow viewports/containers</a>, <a href="https://github.com/WordPress/gutenberg/pull/63118">make SiteHub available for Pages, Patterns, and Templates in mobile viewports</a>, and <a href="https://github.com/WordPress/gutenberg/pull/63002">ensure Patterns and Templates can be edited</a>.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/64209">De-emphasise bulk actions on Grid layout</a> after feedback that always being able to see the bulk select option proved to be confusing.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/64268">Move bulk actions menu to the Footer</a>, consolidate with the floating toolbar and total items display, to provide an easier to access pathway.&nbsp;</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/65223">Show item count for each item in the sidebar</a> for access to quick information.&nbsp;</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/65295">Improved UX of views for Pages</a> with filtered views, like Published and Drafts, that only shows additional filters and hides the “status” filter to prevent ending up in a confusing state.&nbsp;&nbsp;</li>
</ul>



<h4 class="wp-block-heading" id="expanded-extensibility">Expanded extensibility&nbsp;</h4>



<p>As part of enhancing Data Views extensibility and supporting the <a href="https://make.wordpress.org/core/2023/07/12/admin-design/">Admin Redesign</a> efforts, an API was introduced to register and unregister dataview actions. The existing post actions were also moved to globally registered actions and typed actions (see examples in <code>packages/editor/src/dataviews/actions</code>). This enables third-party developers to manage actions as needed. This includes a way to register and unregister core actions around <a href="https://github.com/WordPress/gutenberg/pull/64087">trashing</a>, <a href="https://github.com/WordPress/gutenberg/pull/64088">permanently deleting</a>, and <a href="https://github.com/WordPress/gutenberg/pull/64134">restoring</a> posts. In staying with the idea, users of the component can also unregister actions to duplicate <a href="https://github.com/WordPress/gutenberg/pull/64441">posts</a>, <a href="https://github.com/WordPress/gutenberg/pull/64373">patterns</a>, or <a href="https://github.com/WordPress/gutenberg/pull/64388">template parts</a>.&nbsp;</p>



<p>Developers can also remove the actions to view <a href="https://github.com/WordPress/gutenberg/pull/64467">posts</a> and <a href="https://github.com/WordPress/gutenberg/pull/64464">post revisions</a> or prevent users from <a href="https://github.com/WordPress/gutenberg/pull/64366">renaming a post</a> or <a href="https://github.com/WordPress/gutenberg/pull/64199">reordering pages.</a> These actions appear in both the Site Editor views and the sidebar in the Post or Site Editor.</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1q3_IyMrAtXe6s1gDc5kSr9qmt484GNNa/view?usp=drive_link">demo</a> changing grid density, <a href="https://drive.google.com/file/d/1B7DeTe6eXG6LCub2dKLLwPFE47TCmXck/view?usp=drive_link">image</a> of show/hide filters option.<br /><strong>Adoption approach:</strong> updated by default if using a block theme and opt in for extending with two guides to help <a href="https://developer.wordpress.org/news/2024/08/27/using-data-views-to-display-and-interact-with-data-in-plugins/">Using Data Views to display and interact with data in plugins</a> &amp; <a href="https://developer.wordpress.org/news/2024/09/23/actions-from-data-views-adding-images-to-the-media-library/">Actions from Data Views: Adding images to the Media Library</a><br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> <em>Follow </em><a href="https://github.com/WordPress/gutenberg/issues/63128"><em>this tracking issue</em></a><em> for more information.</em></p>



<h3 class="wp-block-heading" id="consolidating-and-expanding-block-supports">Consolidating and expanding block supports</h3>



<p>Several blocks now come with expanded support options, enabling even more design possibilities. Notably, the long-requested shadow support for Group blocks has been added, which is a big win for designers and theme developers:</p>



<ul class="wp-block-list">
<li>Buttons: Add border, color, and padding block supports. (<a href="https://github.com/WordPress/gutenberg/pull/63538">63538</a>)</li>



<li>Categories: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/63950">63950</a>)</li>



<li>Column: Enable border-radius support. (<a href="https://github.com/WordPress/gutenberg/pull/63924">63924</a>)</li>



<li>Comment Author Name: add border support (<a href="https://github.com/WordPress/gutenberg/pull/64550">64550</a>)</li>



<li>Comment Content: add border support (<a href="https://github.com/WordPress/gutenberg/pull/64230">64230</a>)</li>



<li>Comment Date: add border support (<a href="https://github.com/WordPress/gutenberg/pull/64210">64210</a>)</li>



<li>Comment Template: Add Border Block Support. (<a href="https://github.com/WordPress/gutenberg/pull/64238">64238</a>)</li>



<li>Comment Edit Link: Add Border Block Support. (<a href="https://github.com/WordPress/gutenberg/pull/64239">64239</a>)</li>



<li>Comment Reply Link: Add border support. (<a href="https://github.com/WordPress/gutenberg/pull/64271">64271</a>)</li>



<li>File: Add border block support (<a href="https://github.com/WordPress/gutenberg/pull/64509">64509</a>).</li>



<li>Gallery: Add border block support. (<a href="https://github.com/WordPress/gutenberg/pull/63428">63428</a>)</li>



<li>Group: Add block support for shadow. (<a href="https://github.com/WordPress/gutenberg/pull/63295">63295</a>)</li>



<li>Heading: Add border support. (<a href="https://github.com/WordPress/gutenberg/pull/63539">63539</a>)</li>



<li>Image: Adopt margin block support (<a href="https://github.com/WordPress/gutenberg/pull/63546">63546</a>)</li>



<li>Latest comments: Add color block support (<a href="https://github.com/WordPress/gutenberg/pull/63419">63419</a>)</li>



<li>List: add border support (<a href="https://github.com/WordPress/gutenberg/pull/63540">63540</a>)</li>



<li>List Item: Add color support (<a href="https://github.com/WordPress/gutenberg/pull/59892">59892</a>), add border support (<a href="https://github.com/WordPress/gutenberg/pull/63541">63541</a>).</li>



<li>Media &amp; Text: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/63542">63542</a>)</li>



<li>Paragraph: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/63543">63543</a>)</li>



<li>Post Author Biography: Add border support&nbsp; (<a href="https://github.com/WordPress/gutenberg/pull/64615">64615</a>)</li>



<li>Post Author Name: Add border support&nbsp; (<a href="https://github.com/WordPress/gutenberg/pull/64530">64530</a>)</li>



<li>Post Author: Add border support&nbsp; (<a href="https://github.com/WordPress/gutenberg/pull/64599">64599</a>)</li>



<li>Post Comments Form: Add Border Block Support. (<a href="https://github.com/WordPress/gutenberg/pull/64233">64233</a>)</li>



<li>Post Content: Add background image and padding support (<a href="https://github.com/WordPress/gutenberg/pull/62499">62499</a>)</li>



<li>Post Date: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/64023">64023</a>)</li>



<li>Post Excerpt: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/64022">64022</a>)</li>



<li>Post Terms: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/64246">64246</a>)</li>



<li>Post Title: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/64024">64024</a>)</li>



<li>Preformatted: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/64302">64302</a>)</li>



<li>Query Title: Add border support&nbsp; (<a href="https://github.com/WordPress/gutenberg/pull/64581">64581</a>)</li>



<li>Quote: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/63544">63544</a>), add spacing supports (<a href="https://github.com/WordPress/gutenberg/pull/63545">63545</a>), add background image and minimum height support (<a href="https://github.com/WordPress/gutenberg/pull/62497">62497</a>), add align support (<a href="https://github.com/WordPress/gutenberg/pull/64188">64188</a>).</li>



<li>Search: Add margin support. (<a href="https://github.com/WordPress/gutenberg/pull/63547">63547</a>)</li>



<li>Site Tagline: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/63778">63778</a>)</li>



<li>Site Title: Add border support (<a href="https://github.com/WordPress/gutenberg/pull/63631">63631</a>)</li>



<li>Social Links: Add border block support (<a href="https://github.com/WordPress/gutenberg/pull/63629">63629</a>)</li>



<li>Tag Cloud: Add border block support (<a href="https://github.com/WordPress/gutenberg/pull/63579">63579</a>)</li>



<li>Term Description: Add border block support (<a href="https://github.com/WordPress/gutenberg/pull/63630">63630</a>)</li>



<li>Verse block: Add background image and minimum height support (<a href="https://github.com/WordPress/gutenberg/pull/62498">62498</a>)</li>



<li>Text orientation controls have been added to more blocks (site-title, site-tagline, verse, and button block.) (<a href="https://github.com/WordPress/gutenberg/pull/62727">#62727</a>)</li>
</ul>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1Z3aZYjI7kmM2Q1Gzhvq9kiEouNWzdaMR/view?usp=drive_link">image</a> of shadow support in the Group block.</p>



<p>In <a href="https://make.wordpress.org/core/2024/10/17/roster-of-design-tools-per-block-wordpress-6-6-edition-2/">Roster of design tools per block (WordPress 6.7 edition</a>, you&#8217;ll find an overview table, updated with the most recent changes. </p>



<h3 class="wp-block-heading" id="block-bindings-improvements-including-ui-to-connect-blocks-and-custom-fields-developer-plugin-author-enterprise">Block Bindings improvements, including UI to connect blocks and custom fields [developer] [plugin author] [enterprise]</h3>



<p>The Block Bindings API launched in 6.5 and iterated upon in 6.6 allows you to bind dynamic data to block attributes, solving many use cases for custom blocks and powering other features, like overrides in synced patterns. The work for this release centered mainly on polishing and opening the underlying APIs that were deemed stable, improving the overall UX, and adding a user interface (UI) that allows users to connect attributes with custom fields to their binding sources, making it possible to create bindings through the UI instead of the Code Editor.</p>



<h4 class="wp-block-heading" id="ui-to-connect-blocks-and-custom-fields">UI to connect blocks and custom fields</h4>



<p><em>A quick note here, this is specific to post meta fields as the APIs to extend this UI weren’t considered stable yet. This means that other sources can’t use it yet.</em></p>



<p>This release comes with a new user interface (UI) that allows users to connect attributes with custom fields, making it possible to create bindings through the UI instead of the Code Editor. This UI is controlled by a new editor setting reading a <a href="https://github.com/WordPress/wordpress-develop/pull/7258"><code>new edit_block_binding</code> capability</a>, which is mapped to `edit_post` (if editing a post) or <code>edit_theme_options</code> (if editing a template). This means that by default admin and editor users can create and modify bindings, but this can be overridden with <code>block_editor_settings_all</code> or <code>map_meta_cap</code> filters.</p>



<h4 class="wp-block-heading" id="new-apis-to-empower-extenders">New APIs to empower extenders</h4>



<ul class="wp-block-list">
<li><a href="https://github.com/WordPress/gutenberg/pull/65713">APIs to register sources in the client</a>: Allow extenders to show their source value and provide mechanisms to update it if wanted.</li>



<li><a href="https://github.com/WordPress/gutenberg/pull/64102">Utils to update and remove bindings</a>: Open the door for plugin authors who might want to create their own UI.</li>



<li><a href="https://github.com/WordPress/wordpress-develop/pull/6839">PHP filter to customize the output of a block bindings source</a>: Provide flexibility for developers that just want to modify the output of a specific source.</li>
</ul>



<h4 class="wp-block-heading" id="ux-improvements">UX improvements</h4>



<p>In terms of UX improvements, this includes everything from warnings when a block is connected to an invalid attribute to changing the placeholder text when a block is bound. Additionally, a <a href="https://github.com/WordPress/wordpress-develop/pull/7298">new “label” property</a> has been added to register_meta to be able to consume a human-readable text, which highly improves the UX, especially for non-developer users. When combined, these all seek to improve the experience of editing and interacting with bound blocks.</p>



<p>For this release, the possibility of extending this UI hasn’t been opened because the API wasn’t considered stable, but there are plans to do so in the future.</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1V0OduoyRBnFNy2KUtjAvQiu7lUotfpfA/view?usp=drive_link">demo</a> of UI to connect blocks and custom fields.&nbsp;<br /><strong>Adoption approach: </strong>opt-in by using block bindings UI with the ability to override which users have access to the UI with the `block_editor_settings_all` filter. To disable, you can use the same `block_editor_settings_all` filter and set <code>$editor_settings['canUpdateBlockBindings']</code>as false.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>To read about every change in this release, review <a href="https://github.com/WordPress/gutenberg/issues/63018">this iteration issue</a><strong>.</strong></p>



<p>The Developer Note covers the details: <a href="https://make.wordpress.org/core/2024/10/21/block-bindings-improvements-to-the-editor-experience-in-6-7/">Block Bindings: Improvements to the Editor Experience in 6.7</a> </p>



<h3 class="wp-block-heading" id="polishing-the-query-loop-block-with-a-focus-on-simplicity">Polishing the Query Loop block with a focus on simplicity</h3>



<p>WordPress 6.7 introduces significant improvements to the Query Loop block, focusing on simplicity and clarity. One of the most notable changes is the default settings, where the block now automatically inherits the query from the template, eliminating the need for users to enable this option manually. This ensures that posts display immediately both in the editor and on the front end, streamlining the process for most users who just want to see their content without extra configuration. This also applies when adding a Query Loop block to a single post or page, where the settings will be automatically configured to work in that context.</p>



<p>The Post List variation has been removed from the Inserter due to its confusing settings, which often caused posts to not appear. This change improves the overall user experience.&nbsp;</p>



<p>In terms of customization, a new toggle allows users to easily switch between default and custom queries. If opting for a custom query, another toggle lets users choose between filtering for posts, pages, or custom post types. Additionally, commonly used settings like Posts Per Page, Offset, and Max Pages to Show have been moved from the toolbar to the sidebar settings panel, consolidating all key options into one central place for easier configuration.</p>



<p>The update also includes several refinements, such as a quick preview when selecting the Query Loop block in the Inserter and more intuitive help text, particularly for sticky posts, which are now clearly labeled to always appear first. Pagination controls have been enhanced and moved to the Advanced section for better organization. Another new feature is the introduction of a &#8220;format&#8221; parameter, which allows users to filter content by post format, offering more flexibility in creating tailored queries. Combined, these updates make the Query Loop block both easier to use for beginners and more powerful for advanced users.</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1OPLKlFAi3c9J0JNlQlOEuygVzD70pKrd/view?usp=drive_link">demo</a> of some of the query loop block changes, <a href="https://drive.google.com/file/d/13HAuc-2EdkQ8BYCg1NViA2NyIQmy-FA3/view?usp=drive_link">image</a> of post format support.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong><a href="https://make.wordpress.org/core/2024/09/23/core-editor-improvement-simplified-query-loop-block-with-smarter-defaults-intuitive-settings/">Core Editor Improvement: Simplified Query Loop block with smarter defaults &amp; intuitive settings</a>.</p>



<h3 class="wp-block-heading" id="zoom-out-to-compose-with-patterns">Zoom out to compose with patterns</h3>



<p>The Zoom Out view aims to simplify the process of composing content at the pattern level, rather than focusing on lower-level, individual blocks. This new feature, accessible as a toggle in the toolbar, introduces a high-level, streamlined approach to site building with several key benefits:</p>



<ul class="wp-block-list">
<li>High-Level Overview of Content Structure: The Zoom Out View allows users to insert and manipulate patterns across a page or template, offering a clearer sense of the content structure.&nbsp;</li>



<li>Efficient Pattern Manipulation: While zoomed out, users can easily move, delete, shuffle between, and edit patterns, powered by the usual block toolbar.</li>



<li>Toggle On/Off: This option can be turned on and off in various ways, including clicking the option in the toolbar and double-clicking to edit patterns. All of these options provide pathways in and out of zooming as you’d like.</li>



<li>Ability to style at a high level: As part of making zoom out more robust, you will still see options to style top level container blocks and any individual blocks that don’t exist within a container. This means you can stay zoomed out and still make quick changes, like changing the background color of a Group block.</li>



<li>Additional Enhancements: Other refinements include closing the inserter automatically when switching to block-level editing, showing top-level sections in List View, visual vertical displacement when dragging patterns, and an “Add pattern” prompt for the quick inserter.</li>
</ul>



<p>This feature gives users a simplified, high-level interface to make design changes, ensuring more cohesive layouts with less granular block management.</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1mQFeDmNun-U_PCedpoTqWlRTYKYB2O5U/view?usp=drive_link">demo</a> showing a template being built moving in and out of using zoom out.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Zoom out mode iteration issue for 6.7 for a full list of related changes (<a href="https://github.com/WordPress/gutenberg/issues/64197">64197</a>)&nbsp;</p>



<p><a href="https://make.wordpress.org/core/2024/10/21/developer-notes-for-zoom-out-in-wordpress-6-7/">Developer Notes for Zoom Out in WordPress 6.7</a></p>



<h3 class="wp-block-heading" id="media-improvements">Media improvements</h3>



<p>Adding and interacting with media is taking a big leap forward in this release with HEIC support, auto sizes for lazy loaded images, and more background image support at an individual block and global level:</p>



<h4 class="wp-block-heading" id="support-for-heic-image-uploads">Support for HEIC image uploads</h4>



<p>“In WordPress 6.7, <a href="https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format">HEIC</a> image uploads <a href="https://core.trac.wordpress.org/ticket/53645">will be automatically converted to JPEG on the server when possible</a>. This allows you to view HEIC images in WP Admin and use them in posts and pages regardless of whether a visitor’s browser supports HEIC. Automatic conversion of HEIC images to JPEG can be disabled using the <code>image_editor_output_format</code> filter.”</p>


<pre class="wp-block-code has-small-font-size"><span><code class="hljs language-php shcb-code-table shcb-line-numbers shcb-wrap-lines"><span class="shcb-loc"><span>add_filter( <span class="hljs-string">'image_editor_output_format'</span>, <span class="hljs-function"><span class="hljs-keyword">function</span><span class="hljs-params">( $output_format )</span> </span>{
</span></span><span class="shcb-loc"><span>
</span></span><span class="shcb-loc"><span>    <span class="hljs-keyword">unset</span>( $output_format&#91;<span class="hljs-string">'image/heic'</span>] );
</span></span><span class="shcb-loc"><span>
</span></span><span class="shcb-loc"><span>    <span class="hljs-keyword">return</span> $output_format;
</span></span><span class="shcb-loc"><span>
</span></span><span class="shcb-loc"><span>} );
</span></span></code></span></pre>


<p>From the <a href="https://make.wordpress.org/core/2024/08/15/automatic-conversion-of-heic-images-to-jpeg-in-wordpress-6-7/">Automatic conversion of HEIC images to JPEG in WordPress 6.7</a></p>



<h4 class="wp-block-heading" id="auto-sizes-for-lazy-loaded-images">Auto Sizes for Lazy-loaded Images</h4>



<p>“This implements the HTML spec for applying auto sizes to lazy-loaded images by prepending auto to the sizes attribute generated by WordPress if the image has a loading attribute set to lazy. For browsers that support this HTML spec, the image&#8217;s size value will be set to the concrete object size of the image. For browsers that don&#8217;t support the spec, the word &#8220;auto&#8221; will be ignored when parsing the sizesizes value.”</p>



<p>From the <a href="https://core.trac.wordpress.org/ticket/61847">trac ticket</a> that implemented this feature.</p>



<p>Developer Note: <a href="https://make.wordpress.org/core/2024/10/18/auto-sizes-for-lazy-loaded-images-in-wordpress-6-7/">Auto Sizes for Lazy Loaded Images in WordPress 6.7</a></p>



<h4 class="wp-block-heading" id="expanded-and-improved-background-image-support">Expanded and improved background image support</h4>



<p>Recent updates to background image support bring new customization options for content blocks like Quote, Verse, and Post Content. Previously, background image functionality was restricted to container blocks such as Cover and Group, but with expanded support across multiple blocks, users now have more flexibility in design. This enhancement eliminates the need for nesting blocks, making it easier to achieve the desired look by adding a background image to individual blocks.</p>



<p>Another key improvement is the ability to set background images globally via Styles for block themes for all blocks with background support. For example, this means you can apply a background image across all Quote or Pull Quote blocks within a site, ensuring consistency in design. Additionally, when setting a background image globally or for an individual block, you can enable a fixed background directly from the block settings in Styles. Alternatively, you can define this setting in <code>theme.json</code> using the `background.backgroundAttachment` style property. Finally, a new popover interface has been introduced for background image controls, keeping them neatly hidden when not in use.&nbsp;</p>



<p>In terms of technical updates, you can now use reference values for background images in <code>theme.json</code>, allowing for code reuse and avoiding potential bugs. For example, you can reference a background image defined via <code>styles.background.backGroundImage</code> by setting a value of <code>{ ref: 'styles.background.backgroundImage' }</code> for another background image. Overall, these enhancements greatly improve the flexibility and user experience of adding background images across a site.</p>



<p><strong>Visuals: </strong>images of <a href="https://drive.google.com/file/d/1mS1QUNCV4Qe13HHFE-5LWVcMhltgyUaa/view?usp=drive_link">Quote block</a> and <a href="https://drive.google.com/file/d/1FEfhr1-bxFiEHfOubyNb1uFr-TZcbjo3/view?usp=drive_link">Verse block</a> with background image support, <a href="https://drive.google.com/file/d/1nwVqced-a7U3QxnVsUKNVcOxOGjbvSIN/view?usp=drive_link">demo</a> of using background image tools in Styles.</p>



<p><strong>Adoption approach:&nbsp;</strong></p>



<p>Opt out for HEIC support via the <code>image_editor_output_format</code> hook.</p>


<pre class="wp-block-code"><span><code class="hljs language-php">add_filter( <span class="hljs-string">'image_editor_output_format'</span>, <span class="hljs-function"><span class="hljs-keyword">function</span><span class="hljs-params">( $output_format )</span> </span>{

    <span class="hljs-keyword">unset</span>( $output_format&#91;<span class="hljs-string">'image/heic'</span>] );

    <span class="hljs-keyword">return</span> $output_format;

} );</code></span></pre>


<p>See examples of adding reference values to `theme.json` <a href="https://github.com/WordPress/gutenberg/pull/64128">in the PR that implemented the feature</a>.&nbsp;</p>



<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>background image block support follow up tasks with a dedicated 6.7 section (<a href="https://github.com/WordPress/gutenberg/issues/54336">54336</a>)</p>



<h3 class="wp-block-heading" id="view-meta-boxes-in-the-iframed-post-editor-plugin-author-enterprise">View meta boxes in the iframed Post Editor [plugin author] [enterprise]</h3>



<p>Previously, after an effort to <a href="https://github.com/WordPress/gutenberg/issues/33346">iframe the post editor</a>, metaboxes prevented the editor content from loading in an iframe, causing a fair amount of disruption and workarounds. To resolve this and ensure that both metaboxes and canvas content is visible when working on content, a split view option has been added to allow you to access both while editing when the editor is iframed. This change will provide a consistent WYSIWYG experience between the Editor and frontend views.</p>



<ul class="wp-block-list">
<li>The editor running as an iframe will affect many plugin developers and may force you to modify your code (see <a href="https://github.com/WordPress/gutenberg/pull/64351#issuecomment-2326301103">this comment</a>). Expect a dev note on this topic. Ideally, if you are building a plugin that extends the editor with custom data input, you would transition to one of the available <a href="https://href.li/?https://developer.wordpress.org/block-editor/reference-guides/slotfills/">SlotFills</a> in the interface, creating a more integrated user experience.</li>



<li>This work makes the post editor canvas work as an iframe when there is a meta box.</li>



<li>The meta box area is resizable, and its height is saved as a user preference. If the browser height is low, the meta box switches to a toggleable details element.</li>
</ul>



<p>For enterprise folks who often use plugins that add metaboxes, this is also a change to be aware of and plan for.&nbsp;</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1Sfa0pPnlOJ8_7sxUhrctSnayHgLYfugh/view?usp=drive_link">demo</a> showing before and after this work with the Yoast plugin as an example.&nbsp;<br /><strong>Adoption approach: </strong>Plugin developers may have to alter their code. Expect a dev note on this topic. <a href="https://github.com/Yoast/wordpress-seo/issues/21602">Here’s an example</a> from Yoast around adjustments that had to be made.<br /><strong>Key Make Posts/GitHub/Trac Issue(s):&nbsp; </strong>Try split content view with open metaboxes (<a href="https://github.com/WordPress/gutenberg/pull/64351">64351</a>)</p>



<p>Developer Note: <a href="https://make.wordpress.org/core/2024/10/18/post-editor-iframing-with-meta-boxes-in-wordpress-6-7/">Post Editor iframing with meta boxes&nbsp;in WordPress 6.7</a></p>



<h3 class="wp-block-heading" id="font-management-updates-end-user-theme-author">Font management updates [end user] [theme author]</h3>



<h4 class="wp-block-heading" id="edit-and-apply-font-size-presets">Edit and apply font size presets&nbsp;</h4>



<p>An enhanced Styles interface allows for greater flexibility when creating, editing, removing, and applying font size presets. Users can now easily modify the presets provided by a theme or create their own custom options. A key feature is the ability to toggle fluid typography, which enables responsive font scaling, with the option to set custom fluid values for finer control over responsiveness. Of note, individual font sizes may opt out of fluid typography if it is turned on globally. Individual font size presets can opt in to fluid typography if it is not turned on globally, creating more possibilities.&nbsp;</p>



<h4 class="wp-block-heading" id="consistent-interfaces">Consistent interfaces</h4>



<p>In addition to these font-related enhancements, the Styles interface has been upgraded to offer more intuitive control over font size presets. These presets, along with color presets, are now available for selection from the Styles sidebar under the &#8220;Browse styles&#8221; option, aligning with the left sidebar Styles menu. This change creates a more streamlined and consistent user experience, making navigating and applying global styles across the site easier and making &nbsp; the fonts management modal dialog more discoverable. (<a href="https://github.com/WordPress/gutenberg/pull/62129">62129</a>)</p>



<h4 class="wp-block-heading" id="font-library-enhancements">Font library enhancements</h4>



<p>Fonts are now grouped by source (<a href="https://github.com/WordPress/gutenberg/pull/63211">63211</a>) helping users understand at a glance where each font comes from. A new “Select All” option (<a href="https://github.com/WordPress/gutenberg/pull/63531">63531</a>) allows for quick activation or deactivation of all fonts at once, streamlining font management. When no fonts are installed, a message now displays in the library tab (<a href="https://github.com/WordPress/gutenberg/pull/63740">63740</a>), improving user awareness. Additionally, enhancements have been made to the &#8220;No fonts installed&#8221; state (<a href="https://github.com/WordPress/gutenberg/pull/63533">63533</a>), clarifying situations when fonts are installed but not yet activated.</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1yOpfEc9fVustc7swG5CXTm6ivGeLBFl9/view?usp=drive_link">demo</a> showing editing font preset, creating a font preset, and font library improvements.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong><a href="https://make.wordpress.org/core/2024/10/08/core-editor-improvement-new-features-and-flows-for-font-management/">Core Editor Improvement post dedicated to these changes</a>, efforts done across a number of PRs including add font size presets UI (<a href="https://github.com/WordPress/gutenberg/pull/63057">63057</a>), Font Library: group fonts by source (<a href="https://github.com/WordPress/gutenberg/pull/63211#top">63211</a>), and fluid typography: allow individual preset overrides (<a href="https://github.com/WordPress/gutenberg/pull/64790">64790</a>).</p>



<p>Developer Notes excerpt: <a href="https://make.wordpress.org/core/2024/10/20/miscellaneous-block-editor-changes-in-wordpress-6-7/#new-font-size-presets-ui">New Font Size Presets UI</a></p>



<h2 class="wp-block-heading" id="additional-items-for-6-7"><strong>Additional Items for 6.7</strong></h2>



<h3 class="wp-block-heading" id="template-registration-api-plugin-author-theme-author-developer">Template Registration API [plugin author] [theme author] [developer]</h3>



<p>A new API streamlines the process of registering templates and template parts for plugins, making it easier for developers to integrate custom templates. Previously, plugins had to rely on multiple filters to accomplish this, which created a barrier to entry and limited adoption. With this new API, developers now have a much simpler path to building block templates and aligning with the expectations of WordPress users.</p>



<p>One key feature of the new API is that plugin-registered templates can be overridden by themes, with fallback options that automatically revert to the plugin&#8217;s registered title and description when necessary. The API also empowers theme builders by offering customization options for these templates. Additionally, developers can unregister existing templates or create custom category templates to suit their needs.</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1jXL79RTt3v7UN9UW_dQ5GT9myUU-juCE/view?usp=drive_link">image</a> of code showing how to register a template.&nbsp;<br /><strong>Adoption approach:</strong> Opt in. The tutorial, <a href="https://developer.wordpress.org/news/2024/08/29/registering-block-templates-via-plugins-in-wordpress-6-7/">Registering block templates via plugins in WordPress 6.7</a>, walks you through an example of how to use the new API to provide single, archive, and custom templates for a Book custom post type. Here’s an example for now:</p>


<pre class="wp-block-code"><span><code class="hljs language-xml">register_block_template( 'devblog-plugin-templates//example', &#91;

'title'       =&gt; __( 'Example', 'devblog-plugin-templates' ),

'description' =&gt; __( 'An example block template from a plugin.', 'devblog-plugin-templates' ),

'content'     =&gt; '

<span class="hljs-comment">&lt;!-- wp:template-part {"slug":"header","area":"header","tagName":"header"} /--&gt;</span>

<span class="hljs-comment">&lt;!-- wp:group {"tagName":"main"} --&gt;</span>

<span class="hljs-tag">&lt;<span class="hljs-name">main</span> <span class="hljs-attr">class</span>=<span class="hljs-string">"wp-block-group"</span>&gt;</span>

<span class="hljs-comment">&lt;!-- wp:group {"layout":{"type":"constrained"}} --&gt;</span>

<span class="hljs-tag">&lt;<span class="hljs-name">div</span> <span class="hljs-attr">class</span>=<span class="hljs-string">"wp-block-group"</span>&gt;</span>

<span class="hljs-comment">&lt;!-- wp:paragraph --&gt;</span>

<span class="hljs-tag">&lt;<span class="hljs-name">p</span>&gt;</span>This is a plugin-registered template.<span class="hljs-tag">&lt;/<span class="hljs-name">p</span>&gt;</span>

<span class="hljs-comment">&lt;!-- /wp:paragraph --&gt;</span>

<span class="hljs-tag">&lt;/<span class="hljs-name">div</span>&gt;</span>

<span class="hljs-comment">&lt;!-- /wp:group --&gt;</span>

<span class="hljs-tag">&lt;/<span class="hljs-name">main</span>&gt;</span>

<span class="hljs-comment">&lt;!-- /wp:group --&gt;</span>

<span class="hljs-comment">&lt;!-- wp:template-part {"slug":"footer","area":"footer","tagName":"footer"} /--&gt;</span>'

] );</code></span></pre>


<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong><a href="https://developer.wordpress.org/news/2024/08/29/registering-block-templates-via-plugins-in-wordpress-6-7/">Registering block templates via plugins in WordPress 6.7</a> developer blog post tutorial, Add plugin template registration API (<a href="https://github.com/WordPress/gutenberg/pull/61577">61577</a>).</p>



<p>Developer Note: <a href="https://make.wordpress.org/core/2024/10/20/new-plugin-template-registration-api-in-wordpress-6-7/">New Plugin Template Registration API in WordPress 6.7</a></p>



<h3 class="wp-block-heading" id="preview-options-api-developer-plugin-author-enterprise">Preview Options API [developer] [plugin author] [enterprise]</h3>



<p>The latest WordPress release enhances the Preview Options in the block editor, making it easier for developers to customize how content is previewed. A new API allows plugins and themes to add custom items to the preview dropdown menu, enabling users to see content in different formats or environments. This flexibility improves the editing experience while maintaining the existing structure of the Preview dropdown:</p>



<ul class="wp-block-list">
<li>Introduces <code>PreviewDropdownMenuItem</code> component for adding custom items to the Preview dropdown</li>



<li>Allows plugins to add menu items with custom titles and click handlers</li>



<li>Maintains the existing Preview dropdown structure while allowing for extensibility</li>
</ul>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1Axvxz-jnDHk0E341zRWF7cPelnRoLfXo/view?usp=drive_link">image</a> of an example of how a plugin could use this API.&nbsp;<br /><strong>Adoption approach:</strong> opt in.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Add extensibility to PreviewOptions v2 (<a href="https://github.com/WordPress/gutenberg/pull/64644#top">64644</a>)</p>



<p>Developer Note: <a href="https://make.wordpress.org/core/2024/10/18/extending-the-preview-dropdown-menu-in-wordpress-6-7/">Extending the Preview Dropdown Menu in WordPress 6.7</a></p>



<h3 class="wp-block-heading" id="changes-to-heartbeat-api-to-lower-minimum-allowed-time-enterprise-plugin-author">Changes to Heartbeat API to lower minimum allowed time [enterprise] [plugin author]&nbsp;</h3>



<p>The WordPress Heartbeat script (used to set post locks, show logged-out warnings in wp-admin, etc.) <a href="https://github.com/WordPress/wordpress-develop/pull/7301">has been updated</a> to <a href="https://public-api.wordpress.com/bar/?stat=groovemails-events&bin=wpcom_email_click&redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2023%2F10%2F23%2Fsummary-and-insights-of-phase-3-related-conversations%2F%23%3A%7E%3Atext%3DCollaborative%2520editing%2520%2526%2520asynchronous%2520collaboration&sr=1&signature=e67e40321ccefa55db4f6637890faf5e&user=64259130&_e=eyJlcnJvciI6bnVsbCwiYmxvZ19pZCI6MjAzNzcxODY0LCJibG9nX2xhbmciOiJlbiIsInNpdGVfaWRfbGFiZWwiOiJ3cGNvbSIsIl91aSI6NjQyNTkxMzAsImxvY2FsZSI6ImVuIiwiY3VycmVuY3kiOiJVU0QiLCJjb3VudHJ5X2NvZGVfc2lnbnVwIjoiVVMiLCJzaWdudXBfZmxvd19uYW1lIjoiIiwiZW1haWxfZG9tYWluIjpudWxsLCJwb3N0X2lkIjo3NDYwLCJ1c2VyX2VtYWlsIjoiIiwiZGF0ZV9zZW50IjoiMjAyNC0wOS0xNyIsImVtYWlsX2lkIjoiYjhkMDZiNjFhMWI0NTA2YjJhNjkyN2U1NWQ4YzFiOGYiLCJlbWFpbF9uYW1lIjoicG9zdCIsInRlbXBsYXRlIjoicG9zdCIsImFuY2hvcl90ZXh0IjoiaW1wcm92ZSB0aGUgY3Jvc3MtdXNlciBjb2xsYWJvcmF0aW9uIGV4cGVyaWVuY2UiLCJfZHIiOm51bGwsIl9kbCI6IlwvIiwiX3V0Ijoid3Bjb206dXNlcl9pZCIsIl91bCI6ImFubmV6YXp1IiwiX2VuIjoid3Bjb21fZW1haWxfY2xpY2siLCJfdHMiOjE3MjY1NTQ1NTU2NzMsImJyb3dzZXJfdHlwZSI6InBocC1hZ2VudCIsIl9hdWEiOiJ3cGNvbS10cmFja3MtY2xpZW50LXYwLjMiLCJibG9nX3R6IjowLCJ1c2VyX2xhbmciOiJlbiJ9&_z=z">improve the cross-user collaboration experience</a>. This update speeds up the &#8220;heartbeat&#8221; a bit, from 15 to 10 seconds, which means post locked notices (when somebody edits a post) will be set and cleared faster. It also allows extenders more flexibility in setting a precise heartbeat poll interval, rather than a fixed set of values, ranging from 1 to 3600 seconds (1 hour).</p>



<p><strong>Adoption approach: </strong>opt in by making changes to <code>wp.heartbeat.interval()</code> which has been modified to allow theme and plugin authors to set the heartbeat interval to any value between one second and one hour rather than limiting them to a fixed set of values.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Heartbeat API: consider changing the min allowed time (<a href="https://core.trac.wordpress.org/ticket/61960">61960</a>)</p>



<h3 class="wp-block-heading" id="customize-heading-level-curation-developer">Customize heading level curation [developer]</h3>



<p>The <code>levelOptions</code> block attribute allows you to limit the available heading levels directly through block markup in patterns and templates. Additionally, you can customize the attribute using a filter for both PHP and JavaScript so the applications are broad. This attribute is now available for Core blocks that use heading elements, including <a href="https://github.com/WordPress/gutenberg/pull/64106">Post Title</a>, <a href="https://github.com/WordPress/gutenberg/pull/64107">Query Title</a>, <a href="https://github.com/WordPress/gutenberg/pull/64113">Site Tagline</a>, <a href="https://github.com/WordPress/gutenberg/pull/64111">Site Title</a>, and <a href="https://github.com/WordPress/gutenberg/pull/64103">Comments Title</a>.</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1NChG_4ZAkyPKtkLSyPLlhD0Vm_X4OkZl/view?usp=drive_link">image</a> of before/after heading curation.<br /><strong>Adoption approach: </strong>Opt in via block markup or filters. For examples, <a href="https://github.com/WordPress/gutenberg/pull/63535">please review the PR</a> that added this option to see both markup and filter examples.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> Enable heading level curation. (<a href="https://github.com/WordPress/gutenberg/pull/63535">63535</a>)</p>



<p>Developer Note excerpt: <a href="https://make.wordpress.org/core/2024/10/20/miscellaneous-block-editor-changes-in-wordpress-6-7/#heading-level-curation">Heading level curation</a></p>



<h3 class="wp-block-heading" id="general-improvements">General improvements</h3>



<h4 class="wp-block-heading" id="updated-order-of-editor-actions-for-a-clearer-sidebar">Updated order of editor actions for a clearer sidebar</h4>



<p>The top toolbar in the editors is an important part of the publishing and saving flow, requiring careful consideration around the placement of each item. In this release, two enhancements come together to add clarity and streamline the experience of working across the editors:</p>



<ul class="wp-block-list">
<li>Reorder the top bar actions to move Save/Publish buttons to the right of the Settings and Global Styles (pinned items) buttons.&nbsp;</li>



<li>Swap the &#8220;Cancel&#8221; and &#8220;Publish&#8221; buttons in the pre-publish check panel, allowing users to publish without additional cursor movement.</li>
</ul>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1vLC8_X2APSpX_K1QmzFZHKLN5GMCcXY7/view?usp=drive_link">demo</a> of streamlined pre-publish flow, <a href="https://drive.google.com/file/d/1_UFOlzJ9cfVZ49UUZhU2nBmph8r2UF5l/view?usp=sharing">image</a> of before/after in the site editor of editor actions, <a href="https://drive.google.com/file/d/1plrWkmLLV7dx7jXiGQezXHsVcAx7ROAn/view?usp=drive_link">image</a> of before/after in the post editor of editor actions.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Editor topbar: Reorder the actions on the right (<a href="https://github.com/WordPress/gutenberg/pull/65163">65163</a>), Swap position of the Pre-publish checks buttons (<a href="https://github.com/WordPress/gutenberg/pull/65317#top">65317</a>).</p>



<h4 class="wp-block-heading" id="opt-out-preference-for-choose-a-pattern-modal-when-adding-a-new-page">Opt out preference for &#8216;Choose a Pattern&#8217; modal when adding a new page</h4>



<p>Based on feedback, a new preference was added to toggle on and off “Show starter patterns” to provide the ability to control whether starter patterns appear when creating a new page.&nbsp;</p>



<p><strong>Visuals: </strong><a href="https://drive.google.com/file/d/1VR5YRm9U4WbrLeknyjX5K5Wh0JihpnJ9/view?usp=drive_link">demo</a> showing turning off this option.<br /><strong>Adoption approach: </strong>Opt in by turning preference on.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Add opt out preference to the &#8216;Choose a Pattern&#8217; modal when adding a page. (<a href="https://github.com/WordPress/gutenberg/pull/65026">65026</a>)</p>



<h4 class="wp-block-heading" id="more-robust-saving">More robust saving</h4>



<p>Imagine a situation where you are adding an image to your post and, before it finishes loading, you navigate away from the editor, without ever getting a warning that your image hasn’t yet been saved. In WordPress 6.7, work was done to ensure that doesn’t happen anymore with the introduction of temporary block attributes that ensure in-progress media items are eventually saved and shown:</p>



<ul class="wp-block-list">
<li>Introduce “local” attributes and use it for the image block. (<a href="https://github.com/WordPress/gutenberg/pull/63076">63076</a>)</li>



<li>Video Block: Do not persist blob urls and fix undo. (<a href="https://github.com/WordPress/gutenberg/pull/63238">63238</a>)</li>



<li>Audio Block: Do not persist blob urls and fix undo. (<a href="https://github.com/WordPress/gutenberg/pull/63257">63257</a>)</li>



<li>File block: Do not persist blob urls and fix undo. (<a href="https://github.com/WordPress/gutenberg/pull/63282">63282</a>)</li>
</ul>



<h4 class="wp-block-heading" id="iterating-on-pattern-shuffling">Iterating on pattern shuffling</h4>



<p>To ensure that pattern shuffling behaves as expected and to minimize the risk of losing customizations made to patterns, several adjustments were made to limit its scope:</p>



<ul class="wp-block-list">
<li>Shuffling now applies only to patterns added by the theme or the user.</li>



<li>Shuffling is only available in the zoomed-out view, and the option has been removed from the block toolbar.</li>
</ul>



<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>&nbsp;Remove the Shuffle block toolbar button <a href="https://github.com/WordPress/gutenberg/pull/64571">(</a><a href="https://github.com/WordPress/gutenberg/pull/64954">64954</a>), limit pattern shuffling to theme and user patterns only (<a href="https://github.com/WordPress/gutenberg/pull/62677">62677</a>).</p>



<h4 class="wp-block-heading" id="writing-flow-improvements">Writing flow improvements&nbsp;</h4>



<ul class="wp-block-list">
<li>Allow dropping multiple images to the image block. (<a href="https://github.com/WordPress/gutenberg/pull/65030">65030</a>)</li>



<li>Drag and Drop: When dragging a mix of video, audio, and image blocks, create individual blocks as appropriate. (<a href="https://github.com/WordPress/gutenberg/pull/65144">65144</a>)</li>



<li>Inserter: When opening the block inserter, it will now stay open when interacting with the editor canvas. This makes it easier to move around the document while adding blocks. (<a href="https://github.com/WordPress/gutenberg/pull/63059">63059</a>)</li>



<li>LinkControl: Refined the display of the link preview title and URL when both are same. (<a href="https://github.com/WordPress/gutenberg/pull/61819">61819</a>)</li>



<li>Link Editing: Automatically add tel to phone number when linking URL. (<a href="https://github.com/WordPress/gutenberg/pull/64865">64865</a>)</li>



<li>Page editor: Double-click to edit template part. (<a href="https://github.com/WordPress/gutenberg/pull/65024">65024</a>)</li>



<li>Post Title: Fix pasting in Safari. (<a href="https://github.com/WordPress/gutenberg/pull/64671">64671</a>)</li>



<li>Post Title: Move selection at the end after pasting over the text. (<a href="https://github.com/WordPress/gutenberg/pull/64665">64665</a>)</li>



<li>Restore: Move to trash button in Document settings. (<a href="https://github.com/WordPress/gutenberg/pull/65087">65087</a>)</li>



<li>Slash Inserter: Restrict block list to allowed blocks only. (<a href="https://github.com/WordPress/gutenberg/pull/64413">64413</a>)</li>



<li>Writing flow: Split heading into default block. (<a href="https://github.com/WordPress/gutenberg/pull/61891">61891</a>)</li>
</ul>



<h4 class="wp-block-heading" id="adding-block-examples-and-previews">Adding block examples and previews</h4>



<p>The following adds previews and examples to blocks so that, when searching in the Inserter, you can quickly see how each might be used:</p>



<ul class="wp-block-list">
<li>Excerpt block: Add example of the block. (<a href="https://github.com/WordPress/gutenberg/pull/63010">63010</a>)</li>



<li>Login/out block: Add example of the block. (<a href="https://github.com/WordPress/gutenberg/pull/62937">62937</a>)</li>



<li>Post author blocks: Add example and preview. (<a href="https://github.com/WordPress/gutenberg/pull/62978">62978</a>)</li>



<li>Post content block: Add example of the block. (<a href="https://github.com/WordPress/gutenberg/pull/62968">62968</a>)</li>



<li>Post title: Add example of the block. (<a href="https://github.com/WordPress/gutenberg/pull/62955">62955</a>)</li>



<li>Post date block: Add a block example. (<a href="https://github.com/WordPress/gutenberg/pull/63368">63368</a>)</li>



<li>Post featured image: Add example of the block. (<a href="https://github.com/WordPress/gutenberg/pull/63011">63011</a>)</li>



<li>Post terms block: Add an example. (<a href="https://github.com/WordPress/gutenberg/pull/63369">63369</a>)</li>



<li>Query loop block and Posts list: add example (<a href="https://github.com/WordPress/gutenberg/pull/63286">63286</a>)</li>
</ul>



<h4 class="wp-block-heading" id="site-editor-focused">Site Editor focused</h4>



<ul class="wp-block-list">
<li>Add colors and typography to the browse styles section. (<a href="https://github.com/WordPress/gutenberg/pull/63173">63173</a>)</li>



<li>Allow editing of description only for custom templates. (<a href="https://github.com/WordPress/gutenberg/pull/63664">63664</a>)</li>



<li>Add a typesets section to Typography. (<a href="https://github.com/WordPress/gutenberg/pull/62539">62539</a>)</li>



<li>Apply same styles to block previews on inserter and Styles. (<a href="https://github.com/WordPress/gutenberg/pull/63177">63177</a>)</li>



<li>Document bar is now displayed when viewing the Style book and Style revisions (<a href="https://github.com/WordPress/gutenberg/pull/62669">#62669</a>)</li>



<li>Move font directory into uploads to match WP 6.5. (<a href="https://github.com/WordPress/gutenberg/pull/60354">60354</a>)</li>



<li>Polish create template part modal. (<a href="https://github.com/WordPress/gutenberg/pull/63617">63617</a>)</li>



<li>Template parts now show the content panel in the editor settings. (<a href="https://github.com/WordPress/gutenberg/pull/62034">#62034</a>)</li>



<li>Use four color palette colors instead of five for useStylesPreviewColors. (<a href="https://github.com/WordPress/gutenberg/pull/64700">64700</a>)</li>
</ul>



<h4 class="wp-block-heading" id="other">Other</h4>



<ul class="wp-block-list">
<li>Automatically select group variation if there is only one available. (<a href="https://github.com/WordPress/gutenberg/pull/61871">61871</a>)</li>



<li>Categories List block: Add dropdown for taxonomies. (<a href="https://github.com/WordPress/gutenberg/pull/65272">65272</a>)</li>



<li>Cover Block: Move Clear Media button from Inspector Controls to Block Controls. (<a href="https://github.com/WordPress/gutenberg/pull/64630">64630</a>)</li>



<li>Flex dimensions: Rename “Fill” to “Grow”. (<a href="https://github.com/WordPress/gutenberg/pull/62779">62779</a>)</li>



<li>Format Library: Add alt edit field to inline image (<a href="https://github.com/WordPress/gutenberg/pull/64124#top">64124</a>)</li>



<li>Image lightbox: Remove duplicate image when lightbox is opened. (<a href="https://github.com/WordPress/gutenberg/pull/63381">63381</a>)</li>



<li>Image: Adds the block controls for uploading image. (<a href="https://github.com/WordPress/gutenberg/pull/64320">64320</a>)</li>



<li>Improve Social Icons setup and appending. (<a href="https://github.com/WordPress/gutenberg/pull/64877">64877</a>)</li>



<li>Make SiteLogoReplaceFlow always available in the Site Logo block toolbar. (<a href="https://github.com/WordPress/gutenberg/pull/63499">63499</a>)</li>



<li>Move gallery link controls to the block toolbar. (<a href="https://github.com/WordPress/gutenberg/pull/62762">62762</a>)</li>



<li>Post Date &amp; Comment Date: Add relative date format. (<a href="https://github.com/WordPress/gutenberg/pull/62298">62298</a>) Both the Post Date and Comment Dates now let you <a href="https://github.com/WordPress/gutenberg/pull/62298">set a relative date format</a> (e.g., 00 hours ago).</li>



<li>Table Block: Add toolbar button to add a caption. (<a href="https://github.com/WordPress/gutenberg/pull/47984">47984</a>)</li>



<li>Toolbar justification controls for Group and Content blocks The justification controls for the Group and Content blocks are now exposed in the block toolbar. This makes it easier to quickly update these blocks to be left or right-aligned, using a similar interface to text and button blocks. (<a href="https://github.com/WordPress/gutenberg/pull/62924">62924</a>)</li>
</ul>



<h2 class="wp-block-heading" id="interactivity-api-iteration-bug-fixes-internal-refactor-and-new-apis-developer-plugin-author">Interactivity API iteration: bug fixes, internal refactor, and new APIs [developer] [plugin author]</h2>



<p>For WordPress 6.7, internal improvements and bug fixes were done to ensure that the Interactivity API&#8217;s code is as simple and stable as possible and to make the Interactivity API resilient when used asynchronously (e.g., adding directives or stores after initialization). This paves the way for future performance improvements such as directive code splitting or lazy loading of interactive blocks.&nbsp;</p>



<h3 class="wp-block-heading" id="new-apis-getserver-state-getservercontext">New APIs: getServer State &amp; getServerContext</h3>



<p>Alongside this, two new APIs are available with <code>getServerState</code> and <code>getServerContext</code>, available from the <code>@wordpress/interactivity</code> package. These functions are required for subscribing to changes in state/context when the HTML is updated using <code>navigate()</code>. These functions return an object that is analogous to the state/context returned by <code>store()</code>/<code>getContext()</code>, with a couple of differences:</p>



<ul class="wp-block-list">
<li>The object returned is read-only.</li>



<li>The object is updated after <code>navigate()</code> calls, using the values defined in the HTML.</li>



<li>Devs cannot directly use its properties in directives, but they can use callbacks to subscribe to changes in its properties and update the usual state/context.</li>
</ul>



<p><strong>Adoption approach: </strong>Opt in. For awareness, some new documentation is available for using the Interactivity API:</p>



<ul class="wp-block-list">
<li><a href="https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/core-concepts/the-reactive-and-declarative-mindset/">The Reactive and Declarative mindset</a></li>



<li><a href="https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state/">Understanding global state, local context and derived state</a></li>



<li><a href="https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/core-concepts/server-side-rendering/">Server-side rendering: Processing directives on the server</a></li>
</ul>



<p><strong>Key Make Posts/GitHub/Trac Issue(s):</strong><em>Follow </em><a href="https://github.com/WordPress/gutenberg/issues/63232"><em>this iteration issue</em></a><em> for more information.</em></p>



<p>Developer Note: <a href="https://make.wordpress.org/core/2024/10/15/subscribe-to-changes-in-the-interactivity-api-state-and-context-on-client-side-navigation-in-6-7/">Subscribe to changes in the Interactivity API state and context on client-side navigation in 6.7</a></p>



<h2 class="wp-block-heading" id="updates-for-the-html-api-plugin-author-developer">Updates for the HTML API [plugin author] [developer]&nbsp;</h2>



<p>The HTML Processor has a few upgrades and features:</p>



<ul class="wp-block-list">
<li>Full HTML Support: HTML Processor can handle any HTML and in only the rarest situations will the HTML Processor now give up, and in none of these cases is it because the processor doesn&#8217;t know how to handle a given tag.</li>



<li>Ability to modify most text in a document: The first of a new set of modification methods has been added to the HTML API: <code>set_modifiable_text()</code>.&nbsp;</li>



<li>Full parser mode: The <code>create_full_parser()</code> mode was introduced, which allows the HTML API to process entire HTML documents from start to finish, something that wasn&#8217;t possible before.</li>



<li>CSS behavior reviewed: The Tag Processor and fragment parser in the HTML Processor will assume a document is in standards mode (no-quirks mode) unless it determines otherwise. In response to this, all CSS-adjacent code has been audited and updated to ensure that the matching of things like class names behaves just as it would in a browser.</li>
</ul>



<p><strong>Adoption approach:</strong> opt in by using the HTML API<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>HTML API: Plans for 6.7 (<a href="https://github.com/WordPress/gutenberg/issues/60396">60396</a>)&nbsp;</p>



<p>Developer Note: <a href="https://make.wordpress.org/core/2024/10/17/updates-to-the-html-api-in-6-7/">Updates to the HTML API in 6.7</a></p>



<h2 class="wp-block-heading" id="time-input-as-a-subcomponent-of-timepicker-developer-plugin-author">Time input as a subcomponent of TimePicker [developer] [plugin author]</h2>



<p>Sometimes users only need a way to enter time separate from the <a href="https://github.com/WordPress/gutenberg/pull/63145">date for the TimePicker.component</a>. Developers can now offer <code>separateTimePicker.TimeInput</code> fields in their plugins and apps.&nbsp;</p>



<p><strong>Adoption approach: </strong><a href="https://wordpress.github.io/gutenberg/?path=/docs/components-timepicker--docs">Documentation is available</a> via Storybook.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>TimeInput: Expose as subcomponent of TimePicker (<a href="https://github.com/WordPress/gutenberg/pull/63145">63145</a>).&nbsp;</p>



<p>Developer Note excerpt: <a href="https://make.wordpress.org/core/2024/10/18/editor-components-updates-in-wordpress-6-7/#timepicker-time-input-can-be-used-in-isolation">TimePicker: Time input can be used in isolation</a></p>



<h2 class="wp-block-heading" id="define-block-variations-via-a-php-file-developer-plugin-author">Define block variations via a PHP file [developer] [plugin author]</h2>



<p>6.7 introduces <a href="https://github.com/WordPress/gutenberg/pull/62092">support for referencing a PHP file</a> in block.json for registering block variations. To do this, you must assign the file path as a value for the variations property:</p>


<pre class="wp-block-code"><span><code class="hljs language-json">{

<span class="hljs-attr">"variations"</span>: <span class="hljs-string">"file:./variations.php"</span>

}</code></span></pre>


<p>Previously, you could only define a variations JSON object, but this change lets you register the variations on the server-side. The PHP file must return an array of variations to register.</p>



<p><strong>Adoption approach: </strong>opt in.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>block.json: Allow passing filename as variations field (<a href="https://github.com/WordPress/gutenberg/pull/62092">62092</a>)&nbsp;</p>



<h2 class="wp-block-heading" id="override-styles-dynamically-plugin-author-developer">Override styles dynamically [plugin author] [developer]</h2>



<p>The <a href="https://github.com/WordPress/gutenberg/pull/63656">hook `useStyleOverride` is now available for plugin developers</a> so that styles can be added to the canvas by blocks. This can be especially useful when packaging a component library with custom styles rather than instructing developers to enqueue a separate stylesheet in all the correct locations.&nbsp;</p>



<p><strong>Adoption approach: </strong>opt in.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Make useStyleOverride public (<a href="https://github.com/WordPress/gutenberg/pull/63656">63656</a>)&nbsp;</p>



<h2 class="wp-block-heading" id="help-text-for-radiocontrol-options-developer-plugin-author">Help text for RadioControl options [developer] [plugin author]</h2>



<p>“Developers using the Radio Control component can now add help text for each of the listed options by adding an extra `<a href="https://github.com/WordPress/gutenberg/pull/63751">options[].description`</a> property. This becomes even more relevant when the component is used in the context of input forms for visitors and users via the new wp-admin.” &#8211; From <a href="https://developer.wordpress.org/news/2024/09/10/whats-new-for-developers-september-2024/">What’s new for developers? (September 2024)</a></p>



<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>RadioControl: add support for option help text (<a href="https://github.com/WordPress/gutenberg/pull/63751">63751</a>).</p>



<h2 class="wp-block-heading" id="clearfix-for-the-post-content-block-theme-author-end-user">Clearfix for the Post Content block [theme author] [end user]</h2>



<p>“<a href="https://github.com/WordPress/gutenberg/pull/63690">A “clearfix” solution</a> is now applied to the Post Content block. This is an old-school technique that ensures blocks after Post Content sit below the content itself, especially in cases where there is a right or left-aligned block at the end of the post. As this was an issue for quite a while, it’s expected that theme developers found other ways to solve this particular problem. Now that it’s solved for the core block, you might need to double-check your existing sites to make sure this doesn’t break any previous layouts. Content creators might have helped themselves by adding a spacer block after the aligned block in questions.” &#8211; From <a href="https://developer.wordpress.org/news/2024/09/10/whats-new-for-developers-september-2024/">What’s new for developers? (September 2024)</a></p>



<p><strong>Adoption approach:</strong> please double-check to ensure existing layouts continue to work.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> Post content: Add clearfix (<a href="https://github.com/WordPress/gutenberg/pull/63690">63690</a>)</p>



<h2 class="wp-block-heading" id="continuing-to-improve-php-8-x-support">Continuing to improve PHP 8.x support</h2>



<p>To continue improving support for PHP 8.x, code specific to prior PHP versions that are no longer supported have been removed.</p>



<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Remove PHP &lt; 7.2 code (<a href="https://core.trac.wordpress.org/ticket/61574">61574</a>)&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:"Fri, 18 Oct 2024 19:54:23 +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:"Anne McCarthy";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:63:"WordPress Foundation: 2024 WordPress Foundation Meeting Minutes";s: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=1193851";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpressfoundation.org/news/2024/meeting-minutes/";s: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:14353:"<h1 class="wp-block-heading">October 17, 2024 &#8211; Online</h1>



<p><strong>Present</strong>:&nbsp;</p>



<p>WordPress Foundation Directors: Mark Ghosh, Matt Mullenweg, and Chele Chiavacci Farley</p>



<p>Guests/Observers: Harmony Romo, Isotta Peira, and Sarah Glenn</p>



<p>Regrets: None</p>



<ol class="wp-block-list">
<li><strong>Call to Order</strong></li>



<li><strong>Financial discussion</strong>
<ul class="wp-block-list">
<li><strong>WordPress Foundation financial overview and discussion&nbsp;</strong></li>
</ul>
</li>
</ol>



<p>Harmony Romo spoke to the current financial position of the WordPress Foundation as of today October 17, 2024 and reported on the current cash position, which is up $44,560 compared to the prior year. She noted that after challenges with Wells Fargo earlier in the year that the foundation has switched to J.P. Morgan.</p>



<p><strong>WordPress Foundation Cash Position:</strong></p>



<table class="has-fixed-layout"><tbody><tr><td>J.P. Morgan Commercial Operating Account</td><td>$264,680</td></tr><tr><td>PayPal</td><td>$0</td></tr><tr><td>Stripe</td><td>$0</td></tr></tbody></table>



<p>She shared that, to date, in 2024 the foundation has received $41,417 in donations, up $12,952 compared to last year. It was noted that since WordCamp US in September 2024 there has been an increase in donations with 48 new recurring donations created and a total of $12,535 donated.&nbsp;<br /><br />Matt Mullenweg inquired about the sources of the increased donations to WPF. Harmony Romo shared that there are currently 174 active recurring donations, an increase of 40 over the prior year. Donations received were from a wide variety of foundation supporters, with no single donor contributing more than $5,000. This ensures that the foundation will meet the required 33.33% public support percentage.</p>



<p>The board, alongside a recommendation from Harmony Romo, identified that the foundation should maintain a balance of $150,000. There was further discussion as to how the current excess should be directed. It was suggested that donations could be made to non-profit organizations with similar missions (Foundation for Public Code, Black Girls Code, and Internet Archive) as has been done in the past. Matt Mullenweg requested that an agenda item be added to direct $100,000 to the Internet Archive as they are currently in need.</p>



<ul start="2" class="wp-block-list">
<li><strong>Motion by Matt Mullenweg to approve a $100,000 donation to the Internet Archive&nbsp;</strong>: Seconded by Chele Chiavacci Farley and Mark Ghosh and carried&nbsp;</li>
</ul>



<ul start="3" class="wp-block-list">
<li><strong>WordPress Community Support, PBC financial overview and discussion</strong></li>
</ul>



<p>Harmony Romo spoke to the current financial position of WordPress Community Support, PBC as of today October 17, 2024 and reported on the cash position which is up $667,076 compared to this time in 2023.</p>



<p><strong>WordPress Community Support Cash Position:<br /></strong></p>



<table class="has-fixed-layout"><tbody><tr><td>J.P. Morgan Commercial Operating Account</td><td> $2,181,836</td></tr><tr><td>J.P. Morgan Commercial Deposit-Only Account&nbsp; </td><td>$0</td></tr><tr><td>PayPal</td><td>$0</td></tr><tr><td>Stripe</td><td>$0</td></tr></tbody></table>



<p>Harmony Romo noted that ~$120,000 of our current balance does represent income received for 2025 events and that we still have significant expenses from WordCamp US, held in September 2024, that have yet to be reconciled.&nbsp;</p>



<p>Matt Mullenweg inquired as to why the cash position is so much higher this year than in the past, and Harmony shared that both WordCamp US and WordCamp Europe ended up with significant surpluses. He requested that the programming team look to address this and suggested that we invest in local marketing for WordCamp US next year, and that the programming team works to reduce ticket prices if possible.</p>



<ul start="4" class="wp-block-list">
<li><strong>Discussion of Meetup.com fees and bank strategy&nbsp;</strong></li>
</ul>



<p>Harmony Romo shared that the largest overhead expense is $221,529 for Meetup.com fees per year. She shared that there has been some progress and testing of GatherPress, which if successful could reduce overhead expenses by more than 50%.&nbsp;</p>



<p>Harmony Romo shared that the foundation moved their operating account to J.P. Morgan after challenges with Wells Fargo earlier in the year.</p>



<p>The board discussed whether or not the WordPress Foundation or WordPress Community Support, PBC should alter their banking strategy. It was decided that there is low financial risk with J.P. Morgan, and opening additional accounts with different banks is not necessary at this time. The board did identify that opening money market accounts would be beneficial for WordPress Community Support, PBC and potentially for the WordPress Foundation.<br /><br />Chele Chiavacci Farley noted that interest income returns on both accounts should be 4-5% on the balances. Mark Ghosh recommended that balances be transferred to money market accounts with an option to automatically fund the operating account as needed to cover expenses. Harmony Romo will discuss this with the J.P. Morgan representatives and follow up with options and details via email.</p>



<ul start="5" class="wp-block-list">
<li><strong>Discussion of tax returns</strong></li>
</ul>



<p>Harmony Romo shared that in the filing of the 2023 WordPress Foundations Form 990 the foundation highlighted do_action and learn.wordpress.org programs. The main difference in the 2023 filing, over 2022, was an increase in donation income from $23,744 to $36,388.&nbsp;</p>



<p>As for WordPress Community Support, PBC, the 2023 filing reflected a loss of ($159,983). The loss was due to a large increase in total WordCamps, 71 in 2023 compared to 26 in 2022, and rising inflation that heavily impacted venue as well as food and beverage costs. It was noted that the majority of 2023 losses were related to the flagship events (WordCamp Europe, WordCamp US).  Some of the income for WC Asia that was received in 2020 was reported as income for that year versus being carried forward to offset the 2023 expenses, which also contributed to the loss. This 2023 tax loss will roll forward to offset future years income.&nbsp;</p>



<p>Chele Chiavacci Farley requested that moving forward all financials shared with the board include the prior years financials, and that we ensure a board meeting is held prior to when taxes are due.&nbsp;</p>



<ol start="3" class="wp-block-list">
<li><strong>Programming discussion</strong></li>
</ol>



<p>Isotta Peira shared updates on the various WordPress Foundation and WordPress Community Support, PBC programs.&nbsp;</p>



<p><strong>do_action:</strong></p>



<p>By the end of 2024, the foundation will have supported 8 do_action charity hackathons that combined produced over 21 charity websites for deserving non-profits. The do_action events are close to revenue neutral and only $1,066 was paid in grants in 2024. Mark Ghosh inquired as to how this compares to last year, and it was shared that there were twice as many do_action events as in 2023, when the Foundation only supported 4. In an effort to promote do_actions, they are now displayed on events.WordPress.org alongside other events, like WordCamps.&nbsp;</p>



<p><strong>Open source education:</strong><br /><br />So far in 2024, the WordPress training team organized one online Intro to Open Source workshop called <a href="https://www.meetup.com/learn-wordpress-online-workshops/events/301830181/">“Shape the Future: Your Role in WordPress Open Source Contribution</a> that received 40 RSVPs. There were also 108 participants who completed the ‘<a href="https://learn.wordpress.org/course/open-source-basics-and-wordpress/">Open Source Basics and WordPress’</a> Learn WordPress asynchronous course, and six meetup groups that held open source-focused workshops with a combined total of 200 participants that RSVP’d. There were no direct costs associated with any of these programs as they used the Meetup.com infrastructure paid for by WordPress Community Support.</p>



<p><strong>Learn WordPress</strong><br /></p>



<p>Learn WordPress, launched in December 2020, continues to grow. There are currently 502 lessons and 24 courses with 38,000 people that have registered. So far, 8,600 learners have completed courses this year, which is an average course completion rate of 21%. There have also been 107 online workshops in 2024 with an average of 33 participants.<br /><br />Matt Mullenweg expressed some concern around the low number of learners (8,600) that completed courses, given that there are two full-time sponsored employees focusing on the program. He requested that the programming team work to increase the number of individuals that complete courses as that is much more valuable than the number of people that register.&nbsp;</p>



<p>It was also noted that Learning Pathways was launched in August 2024 as a new approach to educational content, and so far, the average learner satisfaction rate is 93%, and the video retention rate for Learning Pathway courses is 59% (this aligns with technology video benchmarks that see a 40-70% retention rate).&nbsp;</p>



<p><strong>Mentorship Program</strong></p>



<p>An update was shared on the new WordPress Contributor Working Group that aims to bring in new contributors to WordPress through active mentorship over a six-week period. In 2024 there were two cohorts, the first with 28 mentors supporting 52 mentees and the current cohort with 25 mentors supporting 100 mentees. Mentees in the Spring 2024 cohort had an 89% program satisfaction rate.&nbsp;</p>



<p>Matt Mullenweg shared that rtCamp has 10 developers prepared to contribute to core, but they need mentorship. He will create a WordPress.org Slack channel with a representative from rtCamp and Hari Shanker.</p>



<p><strong>Meetups<br /><br /></strong>It was shared that as of today, there are 633 WordPress chapter Meetups in 92 countries, with over 510,000 Meetup members globally, an increase of 10,000 members since last year.&nbsp;</p>



<p><strong>WordPress Events</strong><strong><br /></strong><strong><br /></strong>So far in 2024, there have been 56 WordCamps and WordPress Events held in 51 countries with 6 events held in the US, with another 22 events scheduled over the next two months for a total of 78 events in 2024 compared to 71 events in 2023. In total the events sold more than 18,500 tickets, which is an increase of 4,500 over the previous year.&nbsp;</p>



<p>The board discussed the progress here and Matt Mullenweg shared that he thinks we can do much better and would like to see a larger increase in ticket sales for next year.</p>



<p><strong>Kim Parsell Memorial Scholarship:</strong></p>



<p>In 2024 the Kim Parsell Memorial Scholarship recipient was Cynthia Norman of Ontario, Canada who was awarded $3,000. Cynthia was a member for the 2023 mentorship pilot and has since contributed to the WordPress Training Team, and created more than two dozen lessons for Learn WordPress. </p>



<p>The board was impressed with the impact the scholarship has had and decided to expand the program to offer scholarships for WordCamp Europe and WordCamp Asia in addition to WordCamp US.&nbsp;</p>



<p>Mark Ghosh suggested that the recipient receives approximately 5 minutes of stage-time to discuss how they became involved, and Matt Mullenweg suggested that this could be built into his keynote at flagship events. Matt Mullenweg also recommended that we write blog posts about recipients and try to encourage more people to apply.&nbsp;</p>



<ol start="4" class="wp-block-list">
<li><strong>Updates and new business</strong></li>
</ol>



<ul class="wp-block-list">
<li>New Executive Director</li>
</ul>



<p>It was noted that Mary Hubbard will be starting as the new Executive Director of WordPress.org next week. She will also oversee educational programs in 2025 with support from teams focused on community, education, and contribution.&nbsp;</p>



<ul start="2" class="wp-block-list">
<li><strong>New business</strong></li>
</ul>



<p>Mark Ghosh suggested that WordPress Community Supports look into offering developer badges or certification as a type of learning offering.&nbsp;</p>



<p>Mark Ghosh suggested that in order to move forward more quickly with GatherPress the foundation may want to consider a hackathon type event focused on building this plugin, as the rapid iteration available at a hackathon may help move this along quicker, since a new solution would directly reduce expenses.&nbsp;</p>



<ol start="5" class="wp-block-list">
<li><strong>Next Meeting</strong></li>
</ol>



<p>Matt Mullenweg suggested that the foundation move from one annual meeting to two meetings annually. Mark Ghosh, and Chele Chiavacci Farley agreed this would be beneficial as it would allow the new Executive Director to provide an update and opportunities to review financials prior to tax filings being due.&nbsp;</p>



<p>The board decided the next meeting will be in March, with the following one in August or September.</p>



<ol start="6" class="wp-block-list">
<li><strong>In-Camera Session</strong>
<ul class="wp-block-list">
<li>Matt Mullenweg called an in-camera session for the board at 9:35 AM PST, and the guests/observers departed.&nbsp;</li>
</ul>
</li>
</ol>



<p>The In-Camera session was adjourned at 9:55 AM PST.</p>



<ol start="7" class="wp-block-list">
<li><strong>Close</strong></li>
</ol>



<p>Matt Mullenweg called the meeting to close at 9:57 AM PST.&nbsp;</p>



<p><strong>ADDENDUM</strong></p>



<p>After the meeting was adjourned, it was discovered that some courses on Learn.WordPress.org were deprecated during the fiscal year reported on in the board meeting, and thus the total completed number of courses was understated by 4,087. Total completed courses was actually 12,687.</p>



<p>In addition, it was suggested there be an annual blog post announcing the winner of the Kim Parsell scholarship. This is, in fact, already being done.</p>



<p>WC Asia 2024 also ended with a surplus, which has increased the cash position of WPCS.</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, 18 Oct 2024 16:09: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:12:"Harmony Romo";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:115:"Do The Woo Community: WooCommerce Caching, Scaling, Plugin Optimization, Security, Headless, and AI with Andre Faca";s: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=86155";s: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:109:"https://dothewoo.io/woocommerce-caching-scaling-plugin-optimization-security-headless-and-ai-with-andre-faca/";s: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:176:"In this episode of Woo DevChat, Marcel and Mike discuss optimizing WooCommerce sites with guest Andre Faca, covering caching, performance, scaling, and security best practices.";s: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, 18 Oct 2024 08:25: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: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:79:"WordPress Foundation: WordPress Foundation Donates $100,000 to Internet Archive";s: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=1193835";s: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:72:"https://wordpressfoundation.org/news/2024/wordpress-foundation-donation/";s: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:768:"<p>On October 17th, 2024, the WordPress Foundation Board of Directors made the unanimous decision to make a contribution of $100,000 to the <a href="http://Archive.org">Internet Archive</a>. The WordPress Foundation has long supported the work of the Internet Archive. </p>



<p>The work this organization does to <a href="https://blog.archive.org/2016/10/23/defining-web-pages-web-sites-and-web-captures/">preserve the Internet</a>, ensures that students, researchers, journalists, librarians, and curious citizens around the globe have access to our digital cultural heritage for many years to come. </p>



<p>The Board of Directors is hopeful that this donation will make a significant impact, given the recent challenges faced by the organization.</p>



<p></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, 17 Oct 2024 19:54: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:12:"Harmony Romo";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:87:"WPTavern: Developers Remove Plugins From WordPress.org Repository After ACF Controversy";s: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=175491";s: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:98:"https://wptavern.com/developers-remove-plugins-from-wordpress-org-repository-after-acf-controversy";s: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:4525:"<p>Following the recent ban and <a href="https://wptavern.com/acf-plugin-forked-to-secure-custom-fields-plugin">ACF to Secure Custom Fields fork/takeover</a> incident, some plugin authors have announced their decision to remove their plugins from the WordPress.org repository.</p>



<h3 class="wp-block-heading">Gravity PDF Plugin</h3>



<p>The <a href="https://wordpress.org/plugins/gravity-forms-pdf-extended/">Gravity PDF plugin</a> with over 50k active installations and a 4.9 rating is leaving the plugin repository. Its founder Jake Jackson <a href="https://gravitypdf.com/news/installing-and-upgrading-to-the-canonical-version-of-gravity-pdf/">stated</a> that “WordPress co-founder Matt Mullenweg has weaponized WordPress.org and appropriated the popular Advanced Custom Fields plugin from its creators. This action sets a dangerous precedent, and violates the integrity and security of the platform. To minimize the risks to ourselves and our users, the canonical (primary) version of the free and open-source Gravity PDF plugin is now being distributed directly from GravityPDF.com.”</p>



<p>The team reassured users that all existing PDF settings, custom templates, and fonts will be preserved when transitioning to the new release. Future reviews will be hosted on <a href="https://www.g2.com/products/gravity-pdf/reviews">G2.com</a>. The canonical plugin will use “gravity-pdf” for the slug and text domain, replacing the “gravity-forms-pdf-extended” used on WordPress.org. Updates for the premium version and its extensions will continue directly from GravityPDF.com.</p>



<a href="https://x.com/takisbig/status/1846542405706649856"><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeBCgibxR6Q2OJ7hjcnbnSHUnt0mZul_fiN5UHGXRlnnrG9N_-wKG5tgAE1aTgOKwO7js8IsPnhs3ktfcY0GWU-aQYD8WPiC96FAkml9d58dhZIGWKz3xCQnKaW-hiC0bE_TOgtVV3WIgUg4uFongcFSfvb?key=sYM_dbehUUr6zg7NnQ_agg" alt="" /></a>



<a href="https://x.com/ajaydsouza/status/1846519982030483735"><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdy92EbP5Jkcj_u3OOrDU7vxQasl9fbRrqJSOLELKPkpSIjUAUe0UnYCP4Hh5mJEfLkN2hPS3KIVfr9DZnlgDJ2M9IEJ0315cClyqVOcZZpJSbZatAhkm9Y7I6rPDC9uzPUSSKDvQW0LlosKhaq0d9ugcKq?key=sYM_dbehUUr6zg7NnQ_agg" alt="" /></a>



<h3 class="wp-block-heading">BE Media from Production &amp; Display Posts Plugins&nbsp;</h3>



<p>Bill Erickson, author of <a href="https://en-gb.wordpress.org/plugins/be-media-from-production/">BE Media from Production</a> and <a href="https://wordpress.org/plugins/display-posts-shortcode/">Display Posts</a>, also expressed concerns, <a href="https://displayposts.com/install/">stating</a>, “I am no longer comfortable hosting my code on WordPress.org given recent actions by Matt Mullenweg.”</p>



<p><a href="https://en-gb.wordpress.org/plugins/be-media-from-production/">BE Media from Production</a> plugin has been closed and <a href="https://wordpress.org/support/topic/plugin-has-moved-to-github/">Future updates</a> to this plugin will only come from the official GitHub repo.</p>



<p>He also <a href="https://x.com/BillErickson/status/1845872464296808724">tweeted</a>: “If you use my plugin BE Media from Production, it&#8217;s now hosted only on GitHub.”</p>



<h3 class="wp-block-heading">Paid Memberships Pro Plugin</h3>



<p>The Paid Memberships Pro team released version 3.3 and their CEO Jason Coleman <a href="https://www.paidmembershipspro.com/pmpro-update-3-3/">explained</a>, “This is the first update of the core Paid Memberships Pro plugin that will be served off our own license server instead of the wordpress.org repository. We have been serving our premium plugins and several of our free plugins from our own license server for many years. We will now be serving downloads and updates of our core plugin ourselves.”</p>



<p>He continued, “We plan to follow suit for all of our plugins that are hosted at wordpress.org, excepting a few that are co-maintained with other folks there. The core plugin is still free and users will always be able to update it for free.”</p>



<p>Version 3.2.2 will be available in the repository for a day or so and then closed. Jason said on <a href="https://x.com/jason_coleman/status/1846957738624274560">X</a> that &#8220;We&#8217;ve had this planned for over a year. Recent events motivated us to expedite things.&#8221;</p>



<p>Given the current situation, it doesn&#8217;t seem like things will settle down anytime soon. It remains to be seen if other developers too will follow suit. </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, 17 Oct 2024 19:43:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:54:"WordPress.org blog: WP Engine Promotions &amp; Coupons";s: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=17996";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2024/10/wp-engine-promotions/";s: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:2256:"<p>Given the egregious legal attacks by WP Engine against WordPress co-founder Matt Mullenweg, a number of their customers have been looking for alternative hosting, and in return a number of hosts have created specials and promotions for WP Engine customers looking to migrate to a host that has great relations with WordPress.org. Here they are, in alphabetical order.</p>



<p>We&#8217;ll update this post if any new offers come online, get in touch and we&#8217;ll link it.</p>



<ul class="wp-block-list">
<li><a href="https://www.bluehost.com/migrate-wordpress-website?channelid=P61C46097236S625N0B2A151D0E0000V107">Bluehost will cover migration costs, and credit back your existing contract</a>. They offer 24/7 phone support, you can call them at 844-699-3907. Their wp.cloud-powered Cloud hosting starts at $29.99/mo.</li>



<li><a href="https://www.dreamhost.com/switch-to-dreamhost/">DreamHost is offering free migrations</a>, with plans starting at $16.95/mo.</li>



<li><a href="https://hostinger.com/migrate">Hostinger offers free migration for an unlimited number of websites with a 24/7 dedicated customer success team</a>. Their relevant cloud plans start at $7.99/mo. </li>



<li><a href="https://www.nexcess.net/wp-engine-vs-nexcess/">Nexcess has plans starting at $21/mo</a>.</li>



<li><a href="https://pressable.com/wpe-contract-buyout/">Pressable will credit back your current WP Engine contract and match their pricing</a>, so if you&#8217;re in the middle of a long contract with WP Engine, you don&#8217;t need to wait until your renewal time.</li>



<li><a href="https://siteground.com/free-wp-migration">SiteGround has a special with 83% off and unlimited automated WP migrations</a>, their plans start at $2.99/mo.</li>



<li><a href="https://wordpress.com/migrate-from-wp-engine/">WordPress.com will give you a free year of any plan they offer</a>, and donate 5% of your purchase price to the <a href="https://wordpressfoundation.org/">WordPress Foundation</a>. Their relevant plans start at $25/mo.</li>



<li>For large-scale enterprise customers, <a href="https://wpvip.com/wordpress-vip-vs-wp-engine/">WordPress VIP will cover the cost of migration</a>. Their plans generally start at $2k/mo.</li>
</ul>



<p></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, 17 Oct 2024 15:19:56 +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:"WordPress.org";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:27:"Gary: HOWTO: Fork WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:25:"https://pento.net/?p=5587";s: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://pento.net/2024/10/17/howto-fork-wordpress/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:9215:"<p>Congratulations on your decision to fork WordPress! You&#8217;ve taken on a mammoth task, I&#8217;m impressed with your willingness step up to the challenge of a lifetime. I&#8217;m here to give some advice on the things you might not have thought about yet, and what you&#8217;ll need to help the long term success of your fork.</p>



<p>Forking, I&#8217;m please to share, <a href="https://wordpress.org/news/2024/10/spoon/">is beautiful</a>. It continues to be an important feature of the Open Source ethos, even if it has become more involved as projects have matured. Forking is a valuable tool for Open Source communities to demonstrate that they believe a project should move in a different direction.</p>



<p>Before we get into the details, however, I do have to offer a few disclaimers. This post is <strong>not</strong>:</p>



<ul class="wp-block-list">
<li>An active call for people to fork WordPress. In the spirit of Open Source, I think it&#8217;s important that we publicly talk about what this process looks like, even if it can be an uncomfortable discussion.</li>



<li>An announcement that I&#8217;m forking WordPress. I don&#8217;t have the free time for that.</li>



<li>An offer to wrangle your fork of WordPress. I am happy to discuss your plans and offer advice, though.</li>
</ul>



<p>Disclaimers out of the way, let&#8217;s begin!</p>



<h2 class="wp-block-heading">Before you Announce</h2>



<p>First of all, let&#8217;s talk about that big old elephant in the room: the current level of instability in the WordPress world. I wouldn&#8217;t be surprised to learn that this the major factor in motivating your fork. Unfortunately, this approach won&#8217;t get you very far, so the first thing you need to do is take any feelings you have about it, and set them aside. You need to decide what you&#8217;re in favour of, instead. What are are the positive motivational factors that will make you jump out of bed, and push this project forward for the next decade or more? What will motivate others to join you for the long haul?</p>



<blockquote><p>Build a community, not an angry mob.</p></blockquote>



<p>Think carefully about what your fork is going to be named. I&#8217;m willing to bet that you first jumped to calling it <em>{Adjective}</em>Press, or perhaps something with &#8220;WP&#8221; in the name. That&#8217;s a great idea if you&#8217;re planning on your project being forever defined as a protest against WordPress, but you need to think beyond that. How will you define your brand to keep it relevant for decades to come?</p>



<p>Oh, and make sure you can get the domains and social media handles for your name. Having to try and get them later is just expensive and frustrating.</p>



<p>Talk to people. Not just your circle of friends and colleagues who agree with you, find people who can offer different perspectives, and decide how your fork is going to help them. Talk to WordPress core contributors (not just committers!), and learn their take on it. Can you present an argument that would convince long term contributors to switch to working on your fork?</p>



<p>Figure out funding, at least enough to bootstrap your project. As much as I&#8217;d love to be, most of us are not post-economic. You can only get so far as a volunteer project, you&#8217;re going to need at least some people to be paid to work on it. There are big, complex problems that crop up along the way, it&#8217;s hard to solve them if everyone has to context switch between their day job, and their volunteer work.</p>



<h2 class="wp-block-heading">The Meta Project</h2>



<p>If you&#8217;ve made it this far into starting your fork, give yourself a pat on the back. You&#8217;ve made it much further than many others do. Your next challenge is deciding the process of building it. You could stick with the <a href="https://en.wikipedia.org/wiki/Benevolent_dictator_for_life">BDFL</a> approach, which certainly has benefits, particularly when first starting out. It might be hard to sell what many folks see as a key weakness in WordPress, though. Perhaps you might like to explore a democratic governance model, or some sort of hybrid approach. Everything has a set of benefits and trade-offs, you&#8217;ll need to decide what works for you.</p>



<p>You&#8217;re going to have a bunch of technical dirty work to figure out. Where will the code be hosted? How will you track issues? Provide support? Discuss plans? Build community? Track data? Host themes, and plugins? What will you do about mobile apps?</p>



<p>At first glance, each of these are fairly straightforward to answer, but it&#8217;s very easy to get lost in the possibilities. My advice here is simple: pick something, use it until it stops being valuable. You can always switch to something different later. Switching governance models might be hard, but switching server-side tools is relatively easy.</p>



<blockquote><p>Do the dirty work, but don&#8217;t get stuck in the weeds.</p></blockquote>



<p>Start thinking about how you&#8217;ll build your in-person community. Meetups, conferences, hack days, helping people move to your project, there are countless opportunities here to build your community.</p>



<h2 class="wp-block-heading">The Moat</h2>



<p>WordPress has three substantial factors that have made it largely unassailable for many years.</p>



<p>First, there&#8217;s the massive community that&#8217;s built up around WordPress over the years. Regular meetups and conferences are an integral part of building a popular Open Source project. You can&#8217;t really piggy back off the work that WordPress has done over the years here, either. The only way forward is to put in the work to build and maintain a community that you&#8217;re proud to be a part of.</p>



<p>Second, there&#8217;s the vast selection of plugins and themes that are available to download for free. The quality between options vary wildly, of course, but that&#8217;s largely irrelevant. The fact that so many options exist means there really is something for everyone. You&#8217;re going to need to figure out how to either maintain long term compatibility with existing WordPress plugins and themes, or you&#8217;re going to find yourself reproducing them all.</p>



<p>Finally, you&#8217;ll need to deal with inertia. The vast majority of WordPress site owners have no need or motivation to change, so you need to make it easy (ideally, your fork would be a drop-in replacement), and beneficial. What will your fork do better to solve real problems?</p>



<h2 class="wp-block-heading">Tell Your Friends!</h2>



<p>It&#8217;s around about this point that you&#8217;re probably getting ready to talk about your fork publicly. Go ahead, you&#8217;ve earned it!</p>



<p>Launch day is inevitably a mix of strong emotions. Elation if you get a huge positive response from the public, maybe discouragement if the public response is a bit more muted. Relief at having made it this far. Optimism about the future. Maybe even some doubt could creep in that you&#8217;re the right person to be wrangling such a huge endeavour. Whatever you end up experiencing, try not to stress about it too much. It&#8217;s a big day, but what really defines your project is what you do with it tomorrow. Next week. Next year.</p>



<p>Go right back to the start, and remind yourself of the positive reasons that you&#8217;re choosing to build this project. Tell the world those positive reasons, and welcome anyone who wants to join you on the journey.</p>



<h2 class="wp-block-heading">The Long Haul</h2>



<p>Not every day is launch day, however. Most of your days will be&#8230; kinda boring, to be honest. That&#8217;s a good thing! Too much excitement will inevitably burn out you and your community. Sustainable effort, day after day, is how you build something to last.</p>



<blockquote><p>It&#8217;s a marathon, not a sprint.</p></blockquote>



<p>Of course, there&#8217;ll be ups and downs. It&#8217;s always okay to go back to the start, and reminder yourself (and your community!) of the positive reasons that you&#8217;re all working together on this.</p>



<p>Oh, and please try to remember that one day, you&#8217;re probably not going to be the right person to lead your project any more. This isn&#8217;t something to fear, or to look forward to, really: projects, communities, and individuals all grow and change. It&#8217;s probably going to be a weird time when you get to this point, but it doesn&#8217;t have to be a time of upheaval and uncertainty. If you&#8217;ve run the project well, you should hopefully have a deep pool of talented folks who can step in to continue what you began.</p>



<h2 class="wp-block-heading">Have Fun!</h2>



<p>Finally, it would be remiss of me not to remind you to have fun! It&#8217;s easy to get lost in conflict at times, but it&#8217;s important to remember that&#8230; it&#8217;s just a CMS. It&#8217;s not going to be the end of the world if you take time away from the project, it&#8217;s actively beneficial for you to have a life outside of the internet. Friends, family, pets, hobbies: make time for the things that matter in your life.</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, 17 Oct 2024 01:20:23 +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:"Gary";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:87:"WPTavern: #141 – Christy Nyiri and Mike Straw on Automattic’s Special Projects Team";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=175292";s: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:98:"https://wptavern.com/podcast/141-christy-nyiri-and-mike-straw-on-automattics-special-projects-team";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:46359:"Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.</p>



<p>Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, learning about the work of the Automattic Special Projects Team.</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 Christy Nyiri and Mike Straw.</p>



<p>Christy leads the design arm of Automattic&#8217;s Special Projects Team. She taught herself to design and code 17 years ago, and has since worked with a wide range of clients, many of whom you&#8217;ll hear about later.</p>



<p>Mike is an engineer with the Special Projects Team. He&#8217;s been writing code for over four decades and has been deeply into WordPress for the last seven years.</p>



<p>Today we&#8217;re pulling back the curtain on the work done at Automattic&#8217;s Special Projects Team, a somewhat mysterious entity within Automattic. Because of its low visibility and its detachment from regular product output, many have never heard of the team or what they produce, but that is about to change.</p>



<p>Mike and Christy, tell us all about the team, what they do and who they work with and for. They clarify the unique operational model of the team, which resembles an internal agency focusing exclusively on WordPress and open source projects. Their mission isn&#8217;t driven purely by profit. They often support nonprofits and contribute back to the WordPress community.</p>



<p>We get into the team&#8217;s philosophy of learning from mistakes while striving for excellence. From there work with prominent websites, to assisting household names to more philanthropic work, Mike and Christy illustrates how their work showcases the power and versatility of WordPress. In short, they strive to show the very best that WordPress can produce.</p>



<p>This episode highlights the technical and design prowess of the Special Projects Team, but also captures the passion and dedication of its members.</p>



<p>Whether you&#8217;re a WordPress developer, a web design, enthusiastic, or someone interested in the operational intricacies of high caliber web projects, 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 Christy Nyiri and Mike Straw.</p>



<p>I am joined on the podcast by Christy Nyiri and Mike Straw. Hello both.</p>



<p>[00:03:28] <strong>Christy Nyiri:</strong> Hello.</p>



<p>[00:03:29] <strong>Mike Straw:</strong> Hello.</p>



<p>[00:03:31] <strong>Nathan Wrigley:</strong> We&#8217;re going to have a conversation today from WordCamp US. We are in one of the meeting rooms in Portland, Oregon. Christy and Mike have joined me today because they work on a really interesting team, which I don&#8217;t know much about. So they&#8217;re going to school me in how this all hangs together, and how it works.</p>



<p>Before we begin that though, Christy first, and then Mike afterwards, would you mind just giving us a little potted bio about yourselves. Maybe a minute, or something like that.</p>



<p>[00:03:55] <strong>Christy Nyiri:</strong> Yeah. Hey, I&#8217;m Christy Nyiri. I&#8217;m Canadian, but I live in Brooklyn now. I&#8217;ve been with Automattic for a little over four years, and it&#8217;s the longest job I&#8217;ve ever held. So that says something about Automattic as a company.</p>



<p>[00:04:08] <strong>Nathan Wrigley:</strong> Thank you very much Christy. And Mike, give us your little potted bio.</p>



<p>[00:04:12] <strong>Mike Straw:</strong> I&#8217;m Mike. I&#8217;m currently from Ohio, but I&#8217;m from everywhere. I traveled around a lot as a kid, and then in my adult life. But I joined Automattic about seven years ago, and I just joined the Special Projects Team two years ago. I kind of can&#8217;t hold down a job, so I keep changing places I work. I did that my whole life, changing jobs between company, or between organisations. And then in Automattic, I&#8217;ve kind of bounced around a little bit, and I&#8217;ve settled on the special projects team and I am pretty happy here.</p>



<p>[00:04:42] <strong>Nathan Wrigley:</strong> Okay, so you&#8217;ve alluded to what we&#8217;re going to talk about today, Mike. You mentioned the Special Projects Team. It&#8217;s kind of an interesting name. It sort of feels a little bit shrouded in mystery. I don&#8217;t know, it almost feels like special forces in in the army, or something like that. You know, this is the team that we deploy when things get a little bit tricky, when things are complicated.</p>



<p>I don&#8217;t know if that&#8217;s the feeling that you guys get, but it does feel as if what you are working on is, let&#8217;s say, at a higher level than any of the websites I ever built. Put it that way.</p>



<p>So the first question, and either of you can tackle this. What is the Special Projects Team, and which kind of clients do you work with?</p>



<p>[00:05:18] <strong>Christy Nyiri:</strong> So the Automattic Special Projects Team, I&#8217;ll read our little mission statement. We just help interesting people, projects, and organisations have a great experience with WordPress.</p>



<p>[00:05:27] <strong>Nathan Wrigley:</strong> Okay, perfect. Can you name drop? Are you allowed to name drop any of the kind of projects that you&#8217;ve worked on before?</p>



<p>[00:05:32] <strong>Christy Nyiri:</strong> For sure. You can see a bunch of the projects on our website, which is specialprojects.automattic.com. The biggest one that I worked with personally was Print Magazine, which is like a publication that has been around since the 1940s, and it has a big history in the design community.</p>



<p>[00:05:48] <strong>Mike Straw:</strong> Some of the ones I really were proud of is End The Backlog. Which was about backlogs of sexual assault in the country, because they won a Webby for their work. The website won a Webby, and the work they&#8217;re doing has actually had real impact, like the numbers and the charts since they started has actually stopped this backlog that&#8217;s going on. So it was like a real social life impact. And I have some background in that field, so I&#8217;m really passionate about it. So seeing that happen was really cool.</p>



<p>Also, the site we talked about, one of the sites we talked about yesterday was Johan Ernst the explorer, his website, and just the amazing experience of the site itself. The work is pretty amazing.</p>



<p>Post Secret is another really cool one that we&#8217;ve worked on. There&#8217;s a list, we have, what is it, over 450 production sites running now that we&#8217;ve built over the years. And it&#8217;s actually a fun experience having only been here for two years to periodically go on a website and say, hey, wait a minute, that&#8217;s one of our websites. Because I still don&#8217;t know the list completely.</p>



<p>[00:06:51] <strong>Nathan Wrigley:</strong> Okay, thank you for that. That&#8217;s great. So we know that some of the websites that you&#8217;re building have impact. Sounds like some of them, especially meaningful to you in particular there, Mike. That&#8217;s really nice.</p>



<p>What&#8217;s the purpose of the team though? So, as an example, if I rocked up to the special projects team, and just said, I have a brochure website for a local veterinary practice in the town where I live. I&#8217;m guessing that, at some point, you&#8217;re going to filter me out, maybe I don&#8217;t qualify as special.</p>



<p>And I just wonder, is there a criteria? Is it, I don&#8217;t know, is there a criteria based upon the depth of your pockets, or the type of projects, or the industry you are in, or is it maybe just more, well, there&#8217;s a notorious company? Everybody&#8217;s heard of those, so they qualify as special. What is the criteria that gets you in?</p>



<p>[00:07:35] <strong>Christy Nyiri:</strong> Well, we&#8217;ve done projects for a huge range of people, like from very high profile projects to, honestly, there is, not a vet, but we have a site for an animal adoption agency that I think is actually just a girl. A young girl, a teenager, and we built her a website.</p>



<p>So the project has come to us through referrals from other partners that have already existed, and from other Automatticians as well. So if anyone at the company has a project they think would fit with our mission, we can work on that too.</p>



<p>[00:08:07] <strong>Nathan Wrigley:</strong> Okay. So yeah, there&#8217;s definitely some sort of criteria there. But it seems, I was probably missing the target a little bit. So it really isn&#8217;t necessarily to do with the depth of the pockets, or the fact that you are notorious, it really could be anything.</p>



<p>[00:08:17] <strong>Christy Nyiri:</strong> It really can, yeah.</p>



<p>[00:08:19] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;s fascinating. In the presentation blurb that went along with the presentation that you gave yesterday, one of the phrases that you used was, well, you said, connecting partners with the best that the WordPress community has to offer. And as soon as I hear the word WordPress community, I kind of imagine the crowd that we&#8217;re amongst here. Everybody shows up, everybody has their turn, you know, anybody can speak here, anybody can attend here.</p>



<p>But the sort of slightly exclusive nature of the word special, and the kind of projects that you deal with, how is that connection made? Do you feed back things to the WordPress community? So I&#8217;m just wondering if you could unpack that sentence for me.</p>



<p>[00:08:54] <strong>Mike Straw:</strong> There&#8217;s a lot there, because we really are, we&#8217;re part of the WordPress community. We are not primarily about making money, but the way I like to word it is, we are here to make WordPress look good.</p>



<p>We bring things to our partners, we give them the best experience, with the best website we can build for them, and give them the best experience we can for using WordPress.</p>



<p>So we choose tools, we&#8217;re really big on, like right now using block editor, and all that technology. We&#8217;ve been doing a lot of even no code builds, or low code builds, only building like specific functionality that has to be coded up, but using the block editor, and using the tools so that it&#8217;s just there. And then when they&#8217;re working on their website later, they just go in the editor, and click, and it&#8217;s done. So very simple. So it&#8217;s making the WordPress experience a good experience.</p>



<p>And then we also, on the other side of it, we try to give back to the community as much as we can. If we do use a plugin, as an example, I was recently on a project where I found a bug in a plugin that we had installed on a site that was a wordpress.org plugin. I went in, I was like, this is the problem, here&#8217;s the bug. And I fixed it inside, so we could get the site going. And then I went on to their forum and said, hey, we found a bug, here&#8217;s the bug, here&#8217;s how I fixed it. And then they&#8217;re like, cool, thank you, and the next release had the fix.</p>



<p>And we do that with community plugins. We do that with our own products. You know, we&#8217;ll obviously, we&#8217;ll promote Automattic products for them to use. And if there&#8217;s a problem with the product, we&#8217;ll go to the product team and say, we found this. The dog fooding experience, that we dog food pretty much everything that Automattic has to offer. And we find a problem, and we say, we&#8217;ll go to the product team and say, here&#8217;s the bug we found. And sometimes we&#8217;ll also say, here&#8217;s the PR to fix the code.</p>



<p>[00:10:43] <strong>Nathan Wrigley:</strong> So it&#8217;s kind of like a double pronged thing, in that you are creating things, but then contributing back, maybe improvements to existing things, but also perhaps creating your own functionality and allowing the WordPress repository to get a hold of that. But also, I suppose the community piece there is that you are creating exceptional websites, exceptional experiences, which then are a kind of advert, if you like, for WordPress as a tool, like a showcase almost. You know, the things that you produce, I&#8217;m guessing are of, without blowing your own trumpets, you would probably regard them as of high quality, and good examples of what WordPress itself can do.</p>



<p>And I do feel at this moment in time, we&#8217;re recording this in 2024, that we do have, not a credibility problem, but we are competing in a marketplace where the tools that are out there, which you can pay, I don&#8217;t know, $20 a month for, we know what we&#8217;re talking about, these SaaS-based tools. They are beginning to be popular. They&#8217;ve got television adverts, they have giant marketing budgets. So one of the ways that I guess WordPress can promote itself is with exceptional websites that people can look at. So, I don&#8217;t know if you&#8217;ve got anything you want to add to that.</p>



<p>[00:11:48] <strong>Mike Straw:</strong> Yeah. I think, internally, because you know we have our own internal team names. Our team is called Team 51, which sounds as mysterious and strange, and secretive as Special Projects. But really the 51 is for 51%. And that is, we want WordPress to have 51% of the internet. And we&#8217;re doing that by doing things like this because, and this is me personally editorialising a little of, before I came to WordPress, WordPress does kind of have a reputation issue sometimes, because the average external person hears of these suss hosting sites, or because anybody can extend it, anybody can write a plugin.</p>



<p>And you get a plugin in there that&#8217;s junk, and then the WordPress experience is junk, and then they&#8217;re saying WordPress is junk. And so we&#8217;re trying to highlight, no, WordPress itself is a solid tool, a solid platform, and if you develop well on it, you will have a solid site. And so we do a lot of that just to kind of build the reputation.</p>



<p>[00:12:46] <strong>Christy Nyiri:</strong> I&#8217;d like to add that, on the design side of things, someone came up to me after the talk yesterday and said, how does WordPress compete with the other platforms out there that are really design focused? And I think that is what we&#8217;re trying to do on our team, is show that you can build really well designed websites with WordPress, and using the block editor.</p>



<p>It is a more recent thing, I will admit, the block editor only really came to maturity maybe in the last year. And up until then, like I was even very anti-block theme. As a developer I&#8217;m like, I can build it better in PHP, like I know what I&#8217;m doing. But like now that you can adjust padding, and negative margins, and all those things, it&#8217;s an actual tool that you can use to build nice looking things.</p>



<p>There is some work that needs to be done, but it&#8217;s getting there. And we&#8217;re confident that the more that we show sites that we build, that are full, non headless builds, like straight block themes, that it&#8217;ll inspire other people to do the same.</p>



<p>[00:13:39] <strong>Mike Straw:</strong> One of the things I will often tell people is, I think I&#8217;m a pretty good engineer, I am a terrible designer. So you tell me what to make a website look like and do, and I will make it do it. If you look at my websites that I have put together, they are disgustingly ugly because a designer has not looked at them.</p>



<p>With the block editor, I&#8217;ve gotten better. I&#8217;m able to actually make it look pretty decent because it does a lot of that for me. But it&#8217;s that thing of, if you have something that&#8217;s only going to be built by engineers, it&#8217;s going to look like something an engineer built. If you build it like anybody would build a website on any other platform, where you have designers that design, and make the look, and the branding, and you get the marketing in there, whatever team you have, and then the engineers are building what they have said make it look like, you end up with something that&#8217;s nice and pretty.</p>



<p>And WordPress, I think, has always had that capability, although it required a lot more engineering work historically. But now, I think it&#8217;s amazing now that we now have project builds that, I think we&#8217;ve had some that just had no engineer involvement now.</p>



<p>[00:14:37] <strong>Nathan Wrigley:</strong> Oh wow. Because the blocks are good enough.</p>



<p>[00:14:39] <strong>Mike Straw:</strong> Our designers design it, our account managers build it in the block editor, and then they&#8217;re done.</p>



<p>[00:14:44] <strong>Nathan Wrigley:</strong> It feels a bit like Team 51 is a website building agency, buried within Automattic then. So again, just to let me understand it a little bit more, we&#8217;ve got designers, Christy&#8217;s a designer. We&#8217;ve got developers, Mike is a developer. And it sounded like you mentioned marketing as well. There&#8217;s marketing people as well? What I&#8217;m trying to get to with that question, is it almost like an agency buried inside of Automattic?</p>



<p>[00:15:09] <strong>Christy Nyiri:</strong> Yeah, you&#8217;re hitting the nail right on the head. Our team does operate on an agency model. There&#8217;s a couple of other teams at Automattic that do as well. One being VIP, and now the other one is lost on me. Oh, The Design Core, they&#8217;re kind of like do all our internal brand stuff.</p>



<p>So Team 51, we are composed of designers, engineers, and project managers, which we call TAMS, AKA Technical Account Managers. And we also have an operations team. All of us like work together to build sites, as any traditional agency would.</p>



<p>[00:15:40] <strong>Mike Straw:</strong> The marketing was an example of how a company would build a website. But yeah, for us internally, some of the partners we bring in have a marketing branch, and we will work with them to do the designing. But yeah, we don&#8217;t do marketing ourselves within the team.</p>



<p>[00:15:56] <strong>Nathan Wrigley:</strong> Okay. And I think I&#8217;m right in saying that the WP Tavern website, and if you are listening to this, there&#8217;s a high chance that either you&#8217;re on an RSS reader, and you&#8217;re listening to this on a podcast player, or you&#8217;re on the WP Tavern website. I think the Tavern website is one of your projects.</p>



<p>[00:16:10] <strong>Mike Straw:</strong> I believe so.</p>



<p>[00:16:10] <strong>Christy Nyiri:</strong> Yeah. Yeah, I remember working on that, or working with other people who were working on it. But yeah, we did that a few years ago, but it was before block themes. I think it&#8217;s actually probably due for a revamp to create a block theme version of it.</p>



<p>[00:16:24] <strong>Nathan Wrigley:</strong> I&#8217;m going to be in your inbox.</p>



<p>Okay, let&#8217;s go in this direction. If we&#8217;re going to categorise your team as special, which is obviously the name. What is special? What do you bring to the table that any other agency out there might not? I am not trying to put you up against, or make you give me a competitive analysis statement of how you&#8217;re different. But what are some of the things that you&#8217;ve noticed in your time there, which really does separate it out as a special thing?</p>



<p>[00:16:47] <strong>Christy Nyiri:</strong> Yeah, I think the biggest thing with our team is that we&#8217;re just like really WordPress focused, and involved in the community, and the open source nature of WordPress, which a lot of like other larger agencies, building larger sites, aren&#8217;t. They&#8217;re doing headless builds using whatever sort of build processes they are, and we&#8217;re like hardcore, a hundred percent block themes. So that&#8217;s one special thing about us.</p>



<p>[00:17:08] <strong>Mike Straw:</strong> And, while we use the agency model, we don&#8217;t directly operate like an agency. An agency is a company trying to make money by building websites. So they&#8217;re going to try to do the things that are going to help them bring in good income, and that&#8217;s kind of what they&#8217;re thinking about.</p>



<p>We are more, even though we operate on that model, that&#8217;s how we interact with partners that we&#8217;re working on with websites and things like that. The things we&#8217;re doing is not to extract funding from them. Again, it&#8217;s about us making a project that shines, and does good things, and makes a site that they will be proud of and brag to their friends about. And so we don&#8217;t operate in that.</p>



<p>And we&#8217;re also just, the entire team is people that are just really, really passionate about WordPress. We want to make it look good. We want to give the best that we have to our partners, to the community. It&#8217;s not unusual, when we discover a bug or a glitch, there&#8217;s somebody within minutes saying, okay, who do we need to talk to, to make sure this works right for everybody else that&#8217;s running into this.</p>



<p>[00:18:09] <strong>Nathan Wrigley:</strong> Do you end up doing sort of some philanthropic work as well? Because this is something buried within Automattic, and Automattic as we know, the three of us at least do, and dear listener, if you don&#8217;t, you can go and explore what Automattic do. They&#8217;ve got multiple revenue streams, and so a traditional agency, I&#8217;m imagining their revenue stream is client work. And the fact that Automattic has other revenue streams, does that make it possible for you to do website builds that aren&#8217;t necessarily going to be, air quotes, profitable? That perhaps you could describe as, I don&#8217;t know, philanthropic?</p>



<p>A good example may be The Tavern actually because, as far as I&#8217;m aware, it doesn&#8217;t, there&#8217;s no revenue stream coming out of The Tavern. The decision has been made to keep a news organisation for WordPress going, and it&#8217;s being kept alive by your team, but there&#8217;s no revenue stream there. So I&#8217;m wondering, do you have that? Is it possible for you to do things on a more philanthropic nature because of the funding system that you&#8217;ve got?</p>



<p>[00:19:03] <strong>Christy Nyiri:</strong> Yeah, I think exactly what you&#8217;re saying. We are not like a profits based team. We work on just trying to showcase the best of what WordPress can do. And so we definitely have done sites for partners that are nonprofits, and we help them build their web presence online.</p>



<p>[00:19:22] <strong>Mike Straw:</strong> I think End The Backlog is a great example of that. There&#8217;s a lot of ones that are just, they&#8217;re not profit making entities. They&#8217;re just groups that are trying to do better things in the world, and we&#8217;re providing some service to that. We&#8217;re not necessarily we&#8217;re not like, this is a good, although that comes into the equation, it&#8217;s not a, we&#8217;re doing this because it&#8217;s a good social justice thing or something, but it&#8217;s a good place we can work. But the outcome is definitely there of enabling these organisations to be able to do things that they might not otherwise be able to do because of financial considerations.</p>



<p>[00:19:55] <strong>Nathan Wrigley:</strong> But it does sound then as if the overall purpose of the special projects team then, and we did allude to this a little bit ago, but we probably could go a little bit further, is to act like a bit of a showcase for WordPress, and just to sort of exemplify the very best of what it can do.</p>



<p>And I don&#8217;t know if you&#8217;ve got like one place, one domain where we can go, and look at the work that you&#8217;ve done, or if it&#8217;s more of, no, you&#8217;ll have to be a bit inventive, and Google, and contact us, and we&#8217;ll tell you what we&#8217;ve built.</p>



<p>But it does feel like that&#8217;s the point. Here&#8217;s a big property. Here&#8217;s an important thing, whether it&#8217;s philanthropic or not, and we&#8217;re going to churn out the best that WordPress can do, and thereby, sort of vicariously let the community know, here&#8217;s WordPress. Here&#8217;s how credible it is. Here&#8217;s the kind of people with the stature that they&#8217;ve got who are using it.</p>



<p>[00:20:41] <strong>Mike Straw:</strong> As of this week, you can go to specialprojects.automattic.com, which has a list of websites, showcases. It actually has some of the tools we&#8217;ve built, and some of the blocks that we&#8217;ve got out there.</p>



<p>Going back to contributing to the WordPress community, there&#8217;s a pull request to put our Accordion Block into Gutenberg Core.</p>



<p>But actually, going back to that whole showcasing idea, the actual way back origins of this team go back to when Matt was working for CNET and building WordPress. And he would build WordPress sites for his friends and say, here&#8217;s a site I made in WordPress, isn&#8217;t WordPress cool? I&#8217;m not quoting him. I don&#8217;t know what he actually said exactly, but that&#8217;s the gist of what was happening.</p>



<p>But that was kind of how, when we were starting as a team back in the day, a lot of times it was a, we&#8217;d see a site hosted on, I don&#8217;t know if it was around back then, but a Wix or a Squarespace kind of environment, and we&#8217;d be like, we could make that in WordPress.</p>



<p>The team would build a WordPress site mirroring that site, and then go to that person and say, look, we made a WordPress site, this is probably going to be a lot easier for you to work with than wherever you are. And that&#8217;s kind of the origins of, literally, let&#8217;s make WordPress look good by building good WordPress sites.</p>



<p>[00:21:53] <strong>Nathan Wrigley:</strong> Forgive me for sort of making this assumption, but it seems like you&#8217;re both quite happy with the work that you are doing. It&#8217;s got value, there&#8217;s some credibility to the work that you&#8217;re doing. I mean, that kind of stuff going on a CV looks nice, right?</p>



<p>And I&#8217;m just wondering if somebody listening to this has the thought that, I think I&#8217;m doing good work, I think I have that caliber in me.</p>



<p>How did you end up dropping into this team? Was it that you were Automatticians already? You may have touched on this in your bio at the beginning, I can&#8217;t remember. Is there a way that you can find yourself into this team? Do you hire externally? There&#8217;s a lot in there, but just tell us what you can.</p>



<p>[00:22:27] <strong>Mike Straw:</strong> Can I say yes?</p>



<p>[00:22:28] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;ll do it.</p>



<p>[00:22:30] <strong>Mike Straw:</strong> Because I think we have very different experiences. You got hired into 51. So we&#8217;d had very different experiences on this, and I think from both ways of, I came in, I got hired by Automattic about seven years ago. Basically rediscovered WordPress, went to a conference, became a happiness engineer doing wordpress.com support.</p>



<p>And then, I think I said earlier, I kind of can&#8217;t hold down a job. I switched from wordpress.com support to doing WooCommerce support. And then I went through, we had an internal developer apprenticeship program that I went through, back to engineering, and worked as an engineer on the woocommerce.com website.</p>



<p>But back when I was a wordpress.com happiness engineer, one of the sites came in for support, who happens to be one of my favorite authors. So I saw her site, and actually it was a, she made a post on her blog of, I&#8217;m having a problem with my like button or something. I&#8217;m like, oh, well I have the access, I&#8217;m doing support, I can go check on it. And I went in, and I start reading, and it had this little flag on it saying, this is a Team 51 site.</p>



<p>So I went and looked. It&#8217;s like, you contact these people. I was like, okay, what is this Team 51? Are they alien secret people? I don&#8217;t know because I hadn&#8217;t, I was new enough, I didn&#8217;t know who they were. And so I messaged someone, I was like, here&#8217;s the thing. And then we got chatting, and he started talking about what they&#8217;re doing. I&#8217;m like, oh my gosh, I want to, this just sounds really cool.</p>



<p>And once an opportunity came in, after I was an engineer for a while, and then they just happened to have an internal thing saying, we&#8217;re looking for some engineers. And I was like, hello, please, yes, and contacted them and then got in. So we do some of that internal hiring kind of thing. But also, and I think Christy can talk more about getting from the outside.</p>



<p>[00:24:09] <strong>Nathan Wrigley:</strong> Okay. So there is internal, there&#8217;s mechanisms internally within Automattic to make your way toward the team. But Christy&#8217;s got a different story.</p>



<p>[00:24:15] <strong>Christy Nyiri:</strong> I guess I didn&#8217;t say this earlier, but I lead the design arm of Special Projects. When I got involved with Automattic I was, like I&#8217;ve been designing and developing websites, self-taught for like, I don&#8217;t know, 17, 18 years now. And I started with WordPress about 17 years ago, when it was so young.</p>



<p>And it was like February, 2020, and I was looking for a full-time role somewhere, and I had a friend who was on the Tumblr engineering team at the time. And he&#8217;s like, why don&#8217;t you just apply at Automattic? And I was like, oh, okay.</p>



<p>And then I applied, and went through the whole trial, and the interview. And the interview was for a product designer. And I don&#8217;t really do product design. I&#8217;m a web, UI person. But I went through the trial expecting eventually like, to get an offer, it would be as the product designer. And they were like, oh, actually we have this team for you, we think you&#8217;d be good on, it&#8217;s called Team 51. And like I had the same reaction as Mike, Team 51, what is that? It sounds mysterious.</p>



<p>And I kind of like looked on the website that they had, and looked at who was on the team, and Jeffrey Zeldman was on the team at the time. Oh my God, if I get to work with Jeffrey Zeldman, like, amazing. And so I was thrilled to get hired at that time.</p>



<p>But I was the first internal designer on the team at that point. They didn&#8217;t really have anyone else. They were working with some contractors who&#8217;s, a lot of them are still with us. We&#8217;ve now grown from just me, to like three other internal designers on our team. So the benefit for my design side of the team is that having internal designers means they can work on internal projects, and they&#8217;re more closely associated with the brand. So they can do like Automattic brand things as well. Because like, in addition to the websites, sometimes we do other projects. I am involved in kind of a rebrand for Automattic. There will be something coming hopefully in the next year or so in that end.</p>



<p>[00:25:58] <strong>Nathan Wrigley:</strong> Would it be fair to say then, if I find a website and the logo of Automattic is at the bottom of the footer, would that be something that is likely to have been done by your team?</p>



<p>[00:26:07] <strong>Christy Nyiri:</strong> Some of them, yeah. Not all of them. We do some internal builds, but there&#8217;s definitely ones we haven&#8217;t done.</p>



<p>[00:26:13] <strong>Nathan Wrigley:</strong> Okay. Yeah, so it&#8217;s not guaranteed, but it&#8217;s a probable. Do you find yourself involved in Automattic properties that have got nothing to do with WordPress as well? So, I don&#8217;t know, things like Pocket Casts and, dare I say it, Tumblr, things like that.</p>



<p>[00:26:25] <strong>Mike Straw:</strong> We&#8217;ve built Tumblr sites as part of it. We&#8217;ve had a couple people just kind of get directly involved on building Tumblr themes. One of the ones, the first time I heard that we were doing that was actually the Jonas Brothers were going on tour, and one of the leads I&#8217;ve had, it was actually built that theme.</p>



<p>And I think that might&#8217;ve been the, was that the first one we did? I know they came back. But we built the theme for the Jonas Brothers when they went on tour. And I think there were some others that we&#8217;ve built. We&#8217;ve built Tumblrs for partners, like along with the sites, or things like that. So yeah, we&#8217;ve worked with Tumblr. I don&#8217;t know that we&#8217;ve done anything with Pocket Casts. That&#8217;s what I listen to your podcast on.</p>



<p>[00:27:01] <strong>Nathan Wrigley:</strong> Okay, yeah. That&#8217;s my podcast player of choice as well.</p>



<p>[00:27:05] <strong>Mike Straw:</strong> Oh, we built, that&#8217;s right, we did. We built the Pocket Cast Blog. We just recently moved that over.</p>



<p>[00:27:09] <strong>Nathan Wrigley:</strong> Automattic seems like it&#8217;s on a clip of purchasing things. So in the more recent past, I can think of Beeper and Texts, and maybe they&#8217;re the kind of things that in the future will come under your purview as well. I don&#8217;t know.</p>



<p>[00:27:18] <strong>Mike Straw:</strong> If there&#8217;s a website, if it&#8217;s an Automattic branded site that belongs to it, we tend to be involved in building those sites, and getting them up and running, or doing a redesign and migration of the site into the Automattic platform.</p>



<p>I&#8217;ve worked, personally spent some time on akismet.com, jetpack.com, automattic.com, I think I&#8217;ve done a little bit of work there. So like those internal sites, we do work with those. And yeah, I had forgotten, we migrated the Pocket Cast Blog.</p>



<p>[00:27:45] <strong>Nathan Wrigley:</strong> Nice. Now, I&#8217;m guessing the fact that you&#8217;ve got, both of you, this incredible heritage, and you&#8217;re obviously surrounded by people of an equal caliber. I&#8217;m guessing that the kind of work that you put out means that it has to be of the highest quality. And if somebody was to be thinking, I&#8217;d like to work with that team, you have to have really high expectations here. Nothing can go out the door that isn&#8217;t as good as it possibly can be.</p>



<p>I don&#8217;t really have a question in there, but I&#8217;m just sort of asking, is that the case? Do you feel that you are doing the best work that you can do with everything that you put out? No corners cut, go the extra mile, do the extra work, that kind of thing. I&#8217;m getting some smiles.</p>



<p>[00:28:22] <strong>Mike Straw:</strong> That sounds really high stress.</p>



<p>[00:28:23] <strong>Nathan Wrigley:</strong> Yeah, and I wondered if it was.</p>



<p>[00:28:25] <strong>Mike Straw:</strong> So there&#8217;s a kind of a philosophy within Automattic of, you&#8217;re allowed to make mistakes. As a matter of fact, I said earlier, I went through an apprenticeship program to become an engineer again, because I&#8217;ve been doing some sort of coding for decades. But it was always smaller projects, and I knew when I came to Automattic, there was no way I could operate at the scale and the level that Automattic operates at.</p>



<p>So I came in as a support person, and then when they had the opportunity for me to go learn this, and when I started my apprenticeship, I actually, I was going to work on the woocommerce.com website. And as part of my apprenticeship, no pressure there, far as I know, the largest WooCommerce site on the internet, and I said something to my lead. Something about, as long as I don&#8217;t crash the site. And he says, oh no, it&#8217;s not a matter of if you&#8217;re going to crash the site, it&#8217;s when. And I fulfilled that. I only crashed it once, so that was good.</p>



<p>Yeah, and I&#8217;ve made mistakes on Team 51. I&#8217;ve made some that had some impact. I wish I hadn&#8217;t, but I did. And I learned from it, and will never do that again, and had learned things as I went. It&#8217;s definitely not a, we&#8217;re cavalier, work fast, break things, as some companies operate in. It&#8217;s, we are very careful, but we also acknowledge the fact that we are human beings that are going to make mistakes, especially because we&#8217;re operating at the cutting edge of things.</p>



<p>A new thing comes in WordPress, or is coming in WordPress, a lot of times we&#8217;ll start implementing it, and using it, and sometimes things don&#8217;t go perfectly. And we have an internal system to make sure that if something does go wrong, we&#8217;re quick to get it fixed, quick to get everything back to working well. But yeah, we do want to give the best. We do all absolutely always give the very best we have to what we&#8217;re doing. We don&#8217;t have an expectation of perfection in that. We have an expectation of, I would say an expectation of excellence, but not of perfection, if that makes sense.</p>



<p>[00:30:19] <strong>Christy Nyiri:</strong> Well, I have an expectation of perfection in design. I&#8217;d say it&#8217;s like really hard in design to get things to the level that I really want them to be. That mostly comes down to just like the really little, this finessing at the end of the build, the CSS details. That&#8217;s what I love. Like I&#8217;m a huge CSS nerd, and because I&#8217;ve built most sites, like up until working in Automattic, my background is that I would do it myself, and do those afterwards, and it&#8217;s hard for me to kind of like translate that to a developer a lot of the time.</p>



<p>But other people on my team that are younger, and have better, I guess like development handoff practices, are really good at like translating to a dev. Like, here&#8217;s the animation I want to see, here&#8217;s the details that I want on the site. And the site that Mike mentioned earlier, johanernst.com, so that&#8217;s. J-O-H-A-N-E-R-N-S-T, and I want everyone to see the site because it is, I think, the most perfect example of what we&#8217;ve built. It&#8217;s like a super high caliber, and all the little details on it. And they&#8217;re still even adding more. Like they&#8217;re going to add, on the site there&#8217;s this globe, and then we&#8217;re going to add a connector of the expeditions around the globe, so you can see the kind of like route that he&#8217;s taken. It&#8217;s such a good site, check it out.</p>



<p>[00:31:34] <strong>Mike Straw:</strong> Going back to the perfection idea, I&#8217;m going to amend a little bit, or with what Christy said, the perfection of the design, and the way the sites look, that is a thing. We try to give them the absolute best site. And I learned that on one website we worked on, that we got the initial site delivered, and then the QA went on for the design QA, and I was one of the people that worked on the couple of hundred issues that they found with the design.</p>



<p>A lot of it was, this is shaded a little different, this is just a couple of pixels out of alignment when you&#8217;re with this particular, like it was very, very detailed design. Making the site look perfect. Making things absolutely the best it can be. So there is that standard of the site we deliver. I was looking more from an engineering perspective of perfect code is not a thing, and sometimes there is a belief that you have to just do everything perfect, and if you make something go wrong, that&#8217;s just the end of everything. And we don&#8217;t have that mindset. We work very, very, very hard to make sure that doesn&#8217;t happen.</p>



<p>The presentation I gave yesterday about the safety net plugin we have, comes from that mindset of, we want to never risk doing something that&#8217;s going to impact our partners, or any of our websites in a negative way. WordPress is a very large code base, it&#8217;s not perfect. But our standards for what we deliver very much are very, very detailed.</p>



<p>[00:33:04] <strong>Nathan Wrigley:</strong> In preparation for this podcast, I actually asked a few Automatticians if they had any idea what your team does.</p>



<p>[00:33:10] <strong>Christy Nyiri:</strong> Nobody does.</p>



<p>[00:33:11] <strong>Nathan Wrigley:</strong> Yeah, and not only did they not know, many of them didn&#8217;t know that it was a thing, the Special Projects Team. So I think the cabal like nature of it, it is interesting. There is this perception that, okay, they live in a different warehouse over there, and they&#8217;ve got chemicals boiling in test tubes, and things like that. But it&#8217;s kind of interesting, this podcast, peeling it back a little bit, and just realising sort of more human nature of it.</p>



<p>[00:33:34] <strong>Mike Straw:</strong> It is kind of that way, but not by design. It just kind of happened that way, because we are so small, and we have such a small thing. So it&#8217;s just not really visible necessarily every day to things that are going on, because we&#8217;re not necessarily putting out product, and things like that.</p>



<p>So I could see where people, well, again, both of us kind of had that perception before we actually came to the team of this big, mysterious thing. And, no, it&#8217;s just really people that really love doing cool stuff.</p>



<p>[00:34:01] <strong>Nathan Wrigley:</strong> It sounds like the caliber of work that you&#8217;re doing is of great interest to you both. You seem to enjoy the space that you&#8217;re in. And obviously, the difficulty that comes with that is understood. I will into the show notes put any of the links that we mentioned today, including the, and I&#8217;m going to call it showcase, I don&#8217;t know if that was the right word, of the kind of sites that the team have been building.</p>



<p>But really fascinating just pulling back the curtain a little bit, and hopefully, off the back of this episode, some people will reach out to wherever they need to reach out to, to see how they can become involved. You never know, you might find some job applications coming through.</p>



<p>Thank you so much for talking to me today. Honestly, really interesting just pulling back the curtain a little bit on the team that you are involved in, and hopefully making it feel a bit less cabal like, in the process. So, Christy and Mike, thank you so much for chatting to me today. I really appreciate it.</p>



<p>[00:34:48] <strong>Mike Straw:</strong> Absolutely. Thank you, this has been fun.</p>



<p>[00:34:49] <strong>Christy Nyiri:</strong> Yeah, thanks so much.</p>
</div>



<p>On the podcast today we have <a href="https://profiles.wordpress.org/nyiriland/">Christy Nyiri</a> and <a href="https://profiles.wordpress.org/mikestraw/">Mike Straw</a>.</p>



<p>Christy leads the design arm of Automattic’s Special Projects Team. She taught herself to design and code 17 years ago and has since worked with a wide range of clients, many of whom you’ll hear about later.</p>



<p>Mike is an engineer with the Special Projects Team. He’s been writing code for over four decades, and has been deeply into WordPress for the last seven years.</p>



<p>Today, we&#8217;re pulling back the curtain on the work done at <a href="https://specialprojects.automattic.com/">Automattic’s Special Projects Team</a>, a somewhat mysterious entity within Automattic. Because of its low visibility and its detachment from regular product output, many have never heard of the team or what they produce, but that’s about to change.</p>



<p>Mike and Christy tell us all about the team. What they do, and who they work with and for. They clarify the unique operational model of the team, which resembles an internal agency, focusing exclusively on WordPress and open-source projects. Their mission isn&#8217;t driven purely by profit; they often support nonprofits and contribute back to the WordPress community.</p>



<p>We get into the team’s philosophy of learning from mistakes while striving for excellence. From their work with prominent websites, to assisting household names, to more philanthropic work, Mike and Christy illustrate how their work showcases the power and versatility of WordPress. In short, they strive to show the very best that WordPress can produce</p>



<p>This episode highlights the technical and design prowess of the Special Projects Team, but also captures the passion and dedication of its members.</p>



<p>Whether you&#8217;re a WordPress developer, a web design enthusiast, or someone interested in the operational intricacies of high-calibre web projects, this episode is for you.</p>



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



<p><a href="https://specialprojects.automattic.com/">Automattic Special Projects Team</a></p>



<p><a href="https://www.printmag.com/">PRINT magazine</a></p>



<p><a href="https://www.endthebacklog.org/">End The Backlog</a></p>



<p><a href="https://johanernst.com/">Johan Ernst</a></p>



<p><a href="https://postsecret.com/">Post Secret</a></p>



<p><a href="https://pocketcasts.com/">Pocket Casts</a></p>



<p><a href="https://blog.pocketcasts.com/">Pocket Casts Blog</a></p>



<p><a href="https://www.tumblr.com/">Tumblr</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, 16 Oct 2024 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: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:61:"Do The Woo Community: It’s WooSesh 2024 with Brian Richards";s: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=86126";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:57:"https://dothewoo.io/its-woosesh-2024-with-brian-richards/";s: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:160:"WooSesh 2024 is a free virtual conference on October 29-30, focusing on exceptional customer experience in WooCommerce, featuring keynotes and community awards.";s: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, 16 Oct 2024 12:39: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: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:"Fri, 01 Nov 2024 01:31:52 GMT";s:12:"content-type";s:8:"text/xml";s:13:"last-modified";s:29:"Fri, 01 Nov 2024 01:15:29 GMT";s:4:"vary";s:15:"Accept-Encoding";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:16:"content-encoding";s:4:"gzip";s:7:"alt-svc";s:19:"h3=":443"; ma=86400";s:4:"x-nc";s:9:"HIT ord 1";}}s:5:"build";s:14:"20211220193300";}