Skip toolbar
WordPress.org
Get WordPress
WordPress.org

Make WordPress

Make WordPress

Whether you’re a developer, a designer, or want to push the community forward, we’re always looking for people to join us in making WordPress even better.

From core development and design to support and documentation, every contributor team has a blog, with general news, upcoming events, and opportunities to get started.

Community members
Nicholas Garofalo Community ·

Flagship WordCamps on WP.org/news

One of the key drivers of unique visits to the WCUS 2026 event site was WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, its banners and News posts, which also generate email newsletters and are the basis for social amplification. While the individual event blogs and social accounts share frequent updates for prospective and registered attendees, WordPress.org/news reaches a much larger audience.

We’ve known this for a while, but the publication of event news has been inconsistent across flagship events. After observing how we were able to double traffic to us.WordCamp.org this year (vs 2025 or either of its sibling events), I’d like to provide a framework for when and how we share updates in the future.

Current state

The following is a breakdown of posts made to WordPress.org/news for 2026 flagship WordCamps. Bear in mind that these were published amidst release posts and other content and sometimes reactive rather than planned.

Future post schedule

Based on what we’ve seen work in terms of readership and event site visits, I’d like us to publish at the following cadence for 2027 events:

  1. 51 weeks before or ASAP: Call for organizers and sponsors – A general announcement highlighting the location, a call for organizers, and a sponsor packet. Be Part of WordCamp Asia 2026 was a good example.
  2. 26 weeks before: Announcing ticket sales – A hyped introduction to this year’s themes, photos from last year, and keynotes (if chosen). Something like Get Your WordCamp US 2026 Tickets works.
  3. 16 weeks before: Scholarship(s) – Share any available scholarships and highlight last year’s recipients. See Kim Parsell Memorial Scholarship Opens for WordCamp US 2026.
  4. 8 weeks before: Schedule – Share full schedule, highlight keynotes and a few talks. From AI to Open Source at WordCamp Asia 2026 did this well.
  5. Recap. In the aftermath, we always publish a comprehensive recap akin to what you see in What Happened at WordCamp Europe 2026.

The provided examples and our agent skill should make it easy for anyone to draft these posts. @bjmcsherry and I (@eidolonnight) are available to help get these over the line and published with respect other scheduled content.

In addition to the aforementioned posts, other suitable News posts will promote the proper event in their footers. For example: WordPress 7.1 launched at WCUS 2026, so the following event banner was added to betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. releases (example). I appreciate the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. release squad for their help in making this happen for WordPress 7.1 releases.

+make.wordpress.org/core/
+make.wordpress.org/marketing/

MD. Masjidul Islam

Would it be beneficial to include dedicated opportunities for first-time contributors in these promotional campaigns? Highlighting beginner-friendly activities, volunteering, and contribution pathways could help attract not only attendees but also future WordPress contributors.

Reply

MD. Masjidul Islam

Could WordPress.org also consider publishing localized event announcements in different languages? This could make flagship WordCamps more accessible to people from diverse regions and encourage greater participation from emerging WordPress communities worldwide.

Reply

Nicholas Garofalo Marketing ·

Updates to the WordPress Marketing Repository

Hi everyone! In case you haven’t been watching the marketing Slack, the marketing repo has been getting some love lately. As promised, a variety of AI marketing skills are now available. All of these are built on the WordPress Brand Writing Style Guide, an adaptation of our handbook guide specifically written for agents, and are the same skills used in a few automated workflows. They should be a boon for anyone writing in the WordPress voice.

  • wordpress-writer-news: A useful skill if you’re writing for WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//news, this will write in the WordPress voice by default and ensure formatting matches other content there.
  • wordpress-writer-news-event-recap: Similar to the News skill, this is specifically used for creating event recaps. In case you’ve ever wondered how our event recaps get published so quickly (usually while everyone is still at the after-party), this is it.
  • wordpress-writer-showcase: This is the skill used to draft WordPress Showcase entries based on submission material. Drafts are included in all submission issues that pass initial verification.
  • wordpress-writer-social: This is the same skill used in all the existing workflows that create social content. It covers all social platforms.

These skills have been in use and incrementally improved over the last couple of years. They represent continued learning based on content performance and the latest model changes. That said, if you utilize any of these for your own work, use these as a starting point and feel free to break the rules. I often combine these skills with my own voice files. If you learn anything particularly useful, PRs are welcome.

And speaking of PRs, the largely outdated marketing handbook now syncs from GitHub, While the team may be inactive, much of the documentation around WordPress on social platforms, the WPTV-to-YT sync, Showcase moderation, and more is still relevant. Now, anyone, including agents, can submit PRs for updates.

More to come:

  • As we migrate many workflows from Zapier to n8n, expect to see those show up here. I’m excited for this invisible infrastructure to be more visible and available for other projects to copy/steal.
  • @bjmcsherry and I have been using an agent to continually monitor comms for issues. Once we have a dashboard built and documented, I’ll also share it here. Like the shared skills, I hope this proves to be a useful tool for contributors across the project.
  • We’re cleaning up old issues. We currently have 60 open non-amplification, non-showcase issues. Many of these are years old and no longer relevant.

As always, the goal here is to make great software and support the people who use it in telling their own stories. WordPress is marketed by the millions of people who build with it, write about it, teach it, and gather around it at events. This work makes that ecosystem visible, removes friction from contribution, and ensures that the tools and systems for sharing WordPress’s story are available to everyone.

+make.wordpress.org/community/
+make.wordpress.org/tv/
+make.wordpress.org/ai/
+make.wordpress.org/core/
+make.wordpress.org/meta/

annezazu

Thanks so much for creating these and sharing for us all to benefit from. Writing on News can be really intense in particular so I’m excited to have some extra tools that make it easier. I don’t feel super strongly about this but I wanted to call out that it might be helpful to add these skills to https://github.com/WordPress/core-contributor-skills/ instead of having them separated out into the Marketing repo so there’s one unified spot.

Reply

Nicholas Garofalo

I considered the monorepo approach as well, but ultimately rolled things out here because:

– Intent: WordPress/core-contributor-skills/ is documented as “Agentic skills aimed at helping WordPress Core contributors”. I.e. This repo is communicated as something for the core team.
– Permissions: The people who can/should be updating coding skills are often not the same people who will be working with these marketing skills. As separate repos, we can manage access separately.
– Skill bloat: Loading too many skills can be a detriment to workflows, so if this gets packaged as a plugin, people may not want both sets.

Might be neat to eventually bundle everything via submodules or something, but I find that many agents already figure things out based on the repos available under the WordPress GitHub organization.

Reply

Nishat Shahriyar

Thank you for sharing this, Nicholas!

I have already made some skills based on these skills for my personal use. It’s nice to see how you are using this workflow to run WordPress marketing. Pls, do share more!

Reply

Jeffrey Paul Core AI ·

What's new in AI 1.5.0 (29 OCTOBER 2026)?

AI 1.5.0 has been released and is available for download! “What’s new in AI…” posts (labeled with the #ai-release tag) are posted following every AI pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. release, showcasing new features included in each release.

Text graphic titled 'What's New In AI 1.5.0?' on a light pink background.

We’re pleased to announce the release of AI 1.5.0, the latest update to the canonical plugin powering AI-powered features in WordPress. This release introduces six new Experiments, including Text to Speech, Content Verification, MCP Access, WebMCP, Revision Change Summary, and BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Container Label Generation. It also expands the Embeddings infrastructure, improves Content Translation and Markdown Feeds, introduces additional AI providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). connectors, and brings several Abilities into alignment with WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

What’s new in 1.5.0?

New Experiment: Text to Speech

The new Text to Speech experiment lets editors generate an audio version of a post, giving visitors the option to listen to content instead of reading it.

When enabled, editors can generate audio from a post’s title and content using a configured AI provider that supports speech generation. Audio processing runs in the background, allowing editors to continue working or return later while longer posts are processed.

Once generated, the audio file is saved to the Media Library and can be played directly in the editor. Editors can choose whether to display an audio player on the published post and regenerate the audio when needed. This provides another way for publishers to make their content accessible and available in different formats without requiring a separate audio production workflow.

New Experiment: Content Verification

The new Content Verification experiment introduces support for detecting C2PA Content Credentials in images uploaded to WordPress.

Content Credentials are a standard for attaching provenance information to digital media, helping publishers and audiences understand where content originated and how it may have been modified. When enabled, the experiment detects embedded C2PA data in uploaded JPEG, PNG, and WebP images and preserves the manifest information alongside the attachment. Credential status is displayed in the Media Library, including a new indicator in the grid view.

This initial implementation is read-only. It detects and preserves existing Content Credentials but does not yet perform cryptographic verification or generate new credentials for images. The experiment establishes a foundation for future content provenance features, including deeper verification and support for preserving credentials through WordPress image-processing workflows.

New Experiment: MCP Access

Dashboard view of the MCP Access interface in a web application, displaying various tools and their settings related to AI functionalities, with options for abilities like site information retrieval, image generation, and content analysis.

The new MCP Access experiment makes it easier to connect WordPress to external AI agents through the Model Context Protocol (MCP).

MCP provides a standardized way for AI applications and agents to discover and interact with tools and capabilities exposed by other systems. When enabled, the experiment installs and activates the MCP Adapter plugin when site permissions allow. It also adds a new Tools MCP Access administration screen where site owners can review registered WordPress Abilities and control which ones are exposed to AI agents.

The interface displays the site’s MCP endpoint and provides controls for exposing or hiding individual Abilities, along with the option to restore their default settings. This separates the underlying MCP infrastructure from the controls site owners need to manage agent access, making it easier to explore how external AI systems can interact with WordPress functionality.

New Experiment: WebMCP

AI 1.5.0 also introduces a WebMCP experiment, allowing compatible AI-powered browsers to interact directly with the WordPress Block Editor.

While MCP Access exposes server-side WordPress Abilities to external agents, WebMCP focuses on interactions within the browser itself. Using the experimental document.modelContext interface, an AI agentAI Agent An AI system that autonomously performs tasks and interacts with systems through available tools and resources. can interact with the editor through a collection of tools that support actions such as:

  • Reading the current post and updating its title.
  • Inserting, editing, moving, and duplicating blocks.
  • Modifying block attributes and content.
  • Saving and publishing posts.

These actions use the editor’s existing data stores, so changes appear directly in the editing interface as they happen. This provides an early look at how AI agents could work alongside editors within familiar WordPress interfaces rather than operating exclusively through external APIs.

New Experiment: Revision Change Summary

The new Revision Change Summary experiment helps editors understand what changed between two revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. of a post.

WordPress already provides detailed revision comparisons, but interpreting those changes can become time-consuming for longer or more complex content. With this experiment enabled, editors can generate a plain-language summary of the differences between revisions directly from the visual or classic revision comparison screens.

The summary highlights meaningful changes to post content and titles, helping editors, reviewers, and content teams understand how a post has evolved without reviewing every individual change. The experiment is read-only and does not modify either revision or the underlying post. Additional improvements also preserve more detailed comparisons for multiline content such as tables and quotes.

New Experiment: Block Container Label Generation

The new Block Container Label Generation experiment helps editors navigate complex block layouts by generating meaningful labels for container blocks.

As posts and pages grow in complexity, List View can become difficult to navigate when multiple Group, Columns, and other container blocks appear with generic names. This experiment uses AI to suggest concise, descriptive labels based on the content and purpose of a container. Generated labels are available in List View and the block Rename modal, helping editors identify sections without changing their visible content.

A follow-up enhancement also incorporates document-level context, including the post title, surrounding sections, and existing labels, to produce more useful suggestions.

For editors working with complex page layouts, reusable patterns, or long-form content, these labels can make document navigation and organization considerably easier.

Expanded embeddings infrastructure

AI 1.5.0 continues building on the Embeddings infrastructure introduced in previous releases.

The plugin now includes a background synchronization system for generating and maintaining embeddings for posts and taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. terms.

Using WordPress Cron, the system can process existing content in batches, detect when content changes, and update or remove stored embeddings as needed. It also supports resuming interrupted operations and avoids unnecessary requests when content has not changed.

Embedding generation is not automatically activated for every site. Features that need embeddings must register their requirements, allowing the infrastructure to run only when needed.

Like the earlier embedding storage and vector ranking additions, this is primarily developer infrastructure rather than a new end-user experiment. It provides additional building blocks for future semantic search, content recommendations, retrieval, and other AI-powered workflows.

Content Translation improvements

Content Translation now supports a broader range of WordPress blocks.

Previously, translation focused primarily on paragraphs and headings. AI 1.5.0 expands that behavior to blocks containing rich-text content, allowing more of a post’s content to be translated within the existing workflow. The release also improves translation behavior when working with the editor’s “Show template” mode and prevents translations from being applied to blocks that have been edited, removed, or replaced while a request was processing.

These changes make Content Translation more useful for complex posts and help protect editors’ work when content changes during a translation request.

Markdown Feeds improvements

The Markdown Feeds experiment, introduced in AI 1.4.0, receives several enhancements.

Individual posts requested with ?output_format=markdown now include their approved comments, providing AI agents and other Markdown consumers with additional context from the discussion surrounding published content. The release also improves site-wide comment feeds, fixes content negotiation so requests respect the preferred response format, and applies existing WordPress feed filters for greater compatibility with other plugins.

One behavior has changed: individual post URLs using /<post>/feed/markdown/ are no longer supported. Consumers should request the post’s Markdown document using ?output_format=markdown instead.

Improved AI settings and provider discovery

AI 1.5.0 makes it easier to understand how different AI capabilities operate before enabling them.

The AI settings interface now more clearly distinguishes between stable Features and experimental functionality. Experiments that run automatically are identified, and an information control provides details about when each experiment runs, what information is sent to the configured AI provider, and how many requests it makes.

These improvements are intended to give site owners better visibility into AI usage, especially for experiments that can trigger requests automatically.

The release also expands the available connectors featured on Settings Connectors, adding Mistral and Vercel AI Gateway alongside the existing Anthropic, Google, and OpenAI options. Featured connectors can be discovered, installed, activated, and configured from the same interface.

Additional links to the AI-Powered WordPress course make it easier for new users to find educational resources.

Updated Abilities Explorer

The Abilities Explorer has been rebuilt using WordPress DataViews, bringing its interface more closely into alignment with modern WordPress administration experiences. The updated Explorer makes it easier for developers and administrators to discover, inspect, and execute registered WordPress Abilities.

Three new REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/ endpoints support retrieving and running Abilities, replacing parts of the previous implementation that relied on older administration patterns. Developers can also extend the Explorer with additional read-only columns using the new ai.abilitiesExplorer.fields JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output..

Updated core Abilities and breaking changes

AI 1.5.0 includes important updates to three general-purpose WordPress Abilities:

These Abilities have been synchronized with their corresponding implementations coming in WordPress core with 7.2 this December, helping developers work with consistent interfaces as the Abilities APIAbilities API A core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system. evolves. The updates introduce changes to request and response structures, including new where, fields, and pagination inputs for content and user queries, consistent result structures, and updated field names.

These updates include breaking changes for existing integrations. The deprecated aliases introduced in earlier releases have now been removed:

  • core/read-content use core/content-query
  • core/read-users use core/users-query
  • core/read-settings use core/settings-get

Developers using these Abilities should review the updated schemas and adjust existing calls accordingly. Additional changes to date fields and user lookup behavior may also require updates.

Additional fixes and improvements

The release includes several fixes and smaller enhancements across existing experiments and administration interfaces:

  • Title Generation: A new Generate title button is available in the post Rename modal.
  • AI Request Logging: Successful requests from providers using custom transports are now recorded, and administrators can delete logs by age rather than only purging everything.
  • Suggest Reply: Reply suggestions are applied to the correct comment, and protected post titles and excerpts are no longer sent to AI providers.
  • Comment Moderation: Automatic analysis no longer processes pingbacks, trackbacks, or block editor Notes by default.
  • Content Classification: Improved handling of taxonomy terms containing special characters or non-ASCII text.
  • Key Encryption: Integration with the emerging WordPress Secrets APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. includes backward compatibility and migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. for existing encrypted keys.
  • Performance: Feature and experiment settings are loaded more efficiently, reducing repeated database queries on sites without persistent object caching.
  • AI Status: The dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. now summarizes enabled and disabled experiments in a more compact format.

Security improvements

AI 1.5.0 includes fixes for two reported security advisories, GHSA-7mwf-4ppp-cxmp and GHSA-g94j-h78j-rr2j.

The release also improves how private and password-protected post information is handled in AI-powered comment workflows and includes additional protections around stored connector credentials.

Sites using the AI plugin are encouraged to update promptly.

What’s next?

Work is already underway on additional Features, Experiments, Developer Tools, and Abilities planned for 1.6.0 and future releases, including:

These concepts are still exploratory, but they help test how AI could support real workflows across WordPress.

Thanks to contributors!

A big thank you to everyone who contributed to this release, including:

@dkotter, @jeffpaul, @dan2k3k4, @jason_the_adams, @justlevine, @philsola, @milindmore22, @laurisaarni, @fernandot, @mdraabiul, @whyisjake, @raftaar1191, @iamchitti, @originvault, @shubhambhar007, @mahbubwpwist, @ankitkumarshah, @colinmcdonough, @ekamran, @yogeshbhutkar, @urbankidro, @swissspidy, @fellyph, @jorgefilipecosta, @gziolo, @euthelup, @ugyensupport, @ovidiu-galatan, @drzraf, @zodiac1978, @dhrupo, @pranjal4804, @malaytiwari, @anubhav24, @gajendrasingh, @maheshbohara, @sohampate1, @riccardodicurti, @htperkins, @abcd95, @sainathpoojary, @hbhalodia, @noruzzaman, and others involved in review, testing, translating, and 81 commits across 395 files between 1.4.0 and 1.5.0. Your help and feedback are what make these Features and Experiments possible.

A similar thank you to translators assisting from the Chinese (Taiwan), Czech, Danish, German, German (Formal), Hindi, Japanese, Persian, Polish, and Turkish locales ensuring language packs are available for users. Translating the AI plugin is a great contribution and others contributing in this manner is very much welcome and appreciated!

Get involved

As always, we welcome feedback, testing, and contributions from the community. Whether you are interested in editor UXUX UX is an acronym for User Experience – the way the user uses the UI. Think ‘what they are doing’ and less about how they do it., APIs, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), performance, or AI ethics and policy, there are many ways to participate.

You can explore the 1.5.0 release today, review open issues and pull requests, and help shape what comes next.

Props to @ekamran @laurisaarni @ for reviewing this post.

#ai-experiments, #ai-features, #ai-plugin, #ai-release, #canonical-plugins, #core-ai

Francisco Torres Team Updates ·

Plugins Team: 2 Nov 2026

PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Status Change Stats

  • Plugins requested : 1305
  • Plugins rejected : 246
  • Plugins closed : 77
  • Plugins approved : 995

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 5698
    • (older than 7 days ago)** : 4431
    • (2026-10-26 – 2026-11-01) : 901
    • (new; not processed or replied to yet)* : 316
    • (pending; replied to)* : 5382
    • (pending; waiting on author)* : 4515
    • (pending; waiting on reviewer)* : 610
    • (pending; waiting on reviewer, email not yet sent)* : 257

Help Scout Queue Stats

  • Total Conversations: 2709
  • New Conversations: 1724
  • Customers: 2368
  • Conversations per Day: 338
  • Busiest Day: Monday
  • Messages Received: 1834
  • Replies Sent: 4798
  • Emails Created: 1411

* : Stat reflects current size of queue and does not take into account ‘date’ or ‘day’ interval
** : Stat reflects activity only within the ‘recentdays’ from today

#plugins

George Mamadashvili Core ·

What's new in Gutenberg 24.3? (28 October)

“What’s new in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.

What’s new in
Gutenberg 24.3?

Gutenberg 24.3 is released and available for download!

This release lets you format text across several blocks at once, adds emoji reactions to notes, and redesigns the Media inserter on top of the DataViews grid. Save and autosave failures now tell you what went wrong. Developers get server-side CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. actions and fields, plus a few Interactivity APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. fixes. All of this thanks to a fantastic team of contributors, including ten first-timers.

Format text across blocks

Selections that span several blocks are no longer off-limits for formatting. Select the text, and the formatting controls now apply to all of it (#58913).

Working with multi-blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. selections got a few other upgrades, too. You can drag a selection by pressing anywhere inside it (#81602), move a dragged text selection (#81603), and keep your rich text selection when you Shift+click within the same block (#84579).

Emoji reactions for notes

Sometimes an emoji is all the reply a note needs. Notes now support reactions like ❤️, 🎉, 😄, 👀, and 🚀 (#76767).

Notes also got some polish. They highlight and connect to their content more clearly (#80578), and the text for an unsent note now gets a draft marker (#84125). The “Add note” toolbar button now only adds notes and no longer shows avatars (#84635).

A new look for the Media inserter

The Media inserter now shows your media in a DataViews grid, the same component behind the lists in the Site Editor (#82749).

Additionally, audio and other files that aren’t images or videos get proper previews (#84882).

Save failures that explain themselves

Nobody likes a failed save action. Save failure notices now have a copy option and a “Show/Hide details” button, so you can share what went wrong (#82496). Autosave failures with no server response are explained, too, and the HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. status is shown when available (#85157).

After a failed autosave, a countdown shows when the next attempt will run (#84656), and the notice goes away once a later save succeeds (#84649).

Security fixes from WordPress 7.1.4

Gutenberg 24.3 also includes the security fixes from WordPress 7.1.4, so updating is recommended.

Other notable highlights

  • Patterns: the inserter’s “My patterns” is now “Site patterns” and has an author filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., and synced patterns you can read but not edit are listed in the inserter and can be detached (#84680, #84661, #84641, #84681).
  • Design tools: the consistency work continues, with Search, Table, Tab List, Paragraph, and Icon gaining more support, fit text reaching Post Title, and writing mode reaching Quote and Pullquote (#83954, #83949, #83953, #83934, #83948, #83036, #83965, #83964). A new background clip control also lands in the block supports UIUI User interface (#77142). The changelog lists every block and support.
  • Non-breaking spaces: they are now marked with a red dot, and a button replaces them with regular spaces (#84737).
  • Navigation: links can be edited in a popover from the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. List View, and an empty Navigation MenuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. shows the inserter in the sidebar (#84005, #84003).
  • Gallery: the mobile lightbox gets animated swiping (#79114).
  • Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop: taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. terms are listed so they can be browsed, not recalled (#82583).
  • Table of Contents: headings are read from the post when the block is used in a block context (#85040).
  • Block toolbar: the parent selector plus only shows when no allowed block splits (#84645).
  • List View: nesting with top-level items is allowed (#84856).
  • Client-side media: animated image sub-sizes are generated by default, and EXIF metadata is preserved when converting HEIC to JPEG (#80385, #82040).
  • Icons: new asterisk and form-based icons (#85442, #84074), popular icons shipped to the core-adminadmin (and super admin) collection (#85072), and the Icon block shows the collection name in the “All” tab (#84055).
  • Reduced motion: uploaded Cover background videos and front-end Videos no longer autoplay when reduced motion is preferred (#83853, #84308).
  • Performance: the theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. data merged from all origins is cached, and the icon library renders faster (#81979, #84327).

Changelog

Features

  • Block Editor: Allow rich text formatting across blocks. (58913)
  • UI: Add AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. with initials, colored fallbacks, and an optional color ring. (84145, 84653, 84822, 84824)

Enhancements

  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org 19: Add new incompatible plugins. (84607)
  • Scripts: Run end-to-end tests against the configured wp-env test environment. (84654)
  • Standardize focus rings with the design system:
    • Components: Checkbox and radio, DataViews list items, Link, Snackbar, Tabs panels, and the UnitControl unit select. (85379, 85358, 84697, 85168, 84914, 85444)
    • Editor: Block Directory downloadable blocks, Edit as HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. textarea, LinkControl preview, MediaEdit, and the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Boxes panel toggle. (85307, 85266, 84695, 84940, 85355)

Block Library

  • Accordion Heading: Add background gradient support. (83938)
  • Comments Pagination Previous and Next: Add border and padding support. (64308, 64310)
  • Cover: Add link and button color support. (83972)
  • Cover: Add minimum width support. (83975)
  • File: Add typography support. (83969)
  • Gallery: Improve mobile lightbox with animated swiping. (79114)
  • Heading: Enable editableRoot for multi-selection on mobile. (84358)
  • Icon: Add background image, size, and gradient support. (83948)
  • Icon: Add minimum width and height support. (83971)
  • Icon: Add shadow support. (83921)
  • Icon: Show the collection name in the “All” tab of the icon library. (84055)
  • List: Add minimum width and height support. (83915)
  • Navigation Link: Check page create permission only when needed. (84663)
  • Navigation Overlay Close: Add margin support. (83970)
  • Navigation Overlay Close: Add minimum width and height support. (83907)
  • Paragraph: Add background image, size, and gradient support. (83934)
  • Paragraph: Add minimum width and height support. (83924)
  • Playlist: Add background image, size, and gradient support. (83928)
  • Playlist: Add minimum width and height support. (83909)
  • Post Navigation Link: Add background image, size, and gradient support. (83940)
  • Post Navigation Link: Add minimum width and height support. (83973)
  • Post Template: Add minimum width and height support. (83911)
  • Post Title: Add fit text support. (83036)
  • Pullquote: Add writing mode and text indent support. (83964)
  • Query Loop: List taxonomy terms so they can be browsed, not recalled. (82583)
  • Quote: Add writing mode support. (83965)
  • Search: Add background gradient support. (83954)
  • Search: Add border style support. (83960)
  • Search: Add minimum width and height support. (83977)
  • Search: Add shadow support. (83937)
  • Tab List: Add background image, size, and gradient support. (83953)
  • Tab List: Add line height, font weight, letter spacing, and text transform support. (83961)
  • Table of Contents: Read headings from the post in block context. (85040)
  • Table: Add background gradient support. (83949)
  • Table: Add link color support. (72229)
  • Table: Add text align support. (83966)
  • Term Count: Reuse term data from Term Template. (84119)
  • Term Template: Add heading and button color support. (83968)
  • Terms Query: Add padding, margin, and block gap support. (83959)
  • Video: Add minimum width and height support. (83974)

Components

  • Button: Use Spinner for loading indicators. (84321)
  • BorderBoxControl: Unpack multi-value shorthand width when unlinking border sides. (84826)
  • DataViews: Format footer counts. (84622)
  • DataViews: Improve bulk actions discoverability. (82730)
  • DataViews: Render table bulk actions outside the table. (85250)
  • DataViews: Support mixed-library overlays. (84305)
  • Dialog: Add an auto popup size that fits content width. (84559)
  • Migrate SelectControl consumers to wordpress/ui. (83035, 84345, 84546, 84584, 84936)
  • Modal: Add focus fallback for firstContentElement. (84344)
  • Notice: Match dismiss controls and titles to status colors. (84571)
  • Popover: Use design system tokens on the default surface. (84574)
  • RangeControl: Add size prop. (69844)
  • SearchableSelect, SelectControl: Add trigger slots for props and content. (84934, 84828)
  • Select, Combobox, Autocomplete: Align popup list spacing. (84393)
  • Snackbar: Keep snackbars with an action on screen longer. (84842)
  • Tabs: Align interaction backgrounds and focus states. (84572)
  • Theme: Enrich the design-tokens.js export with more token data. (76604)
  • Theme: Generate JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com design token fallbacks. (84569)
  • UI: Support button items in Breadcrumb. (84156)
  • UI: Use solid brand highlights for popup items. (84087)
  • UI: Use the compatibility overlay slot for AlertDialog, Dialog, and Drawer. (83878, 84379, 84380)

Block Editor

  • Block Breadcrumbs: Use the wordpress/ui Breadcrumb component. (84295)
  • Block Supports: Add background clip UI. (77142)
  • Block Toolbar: Only show the parent selector plus when no allowed block splits. (84645)
  • Drag a multi-selection by pressing anywhere inside it. (81602)
  • FontAppearanceControl, FontFamilyControl: Migrate to wordpress/ui. (84715, 84716)
  • LinkControl, PostURL: Use the wordpress/ui Link. (84819, 84820)
  • Mark non-breaking spaces with a red dot and add a button to replace them. (84737)
  • Media Inserter: Redesign using a DataViews grid. (82749)
    • Add a FilePreview component for audio and other non-image or video files. (84882)
    • Clear the grid and show a loading spinner when switching categories. (84667)
    • Change the page size with the window height when switching categories. (85053)
  • Move a dragged text selection. (81603)
  • Navigation: Edit links in a popover from the sidebar List View. (84005)
  • Navigation: Show the inserter for an empty Navigation Menu in the sidebar. (84003)

Post Editor

  • Core Data: Keep read-only taxonomy fields out of collaborative edits. (84838)
  • Editor: Stabilize the DataForm-based inspector. (85081)
  • Improve save and autosave failure handling:
    • Add a copy option and a “Show/Hide details” button to save failure notices. (82496)
    • Explain autosave failures with no response, and show the HTTP status. (85157)
    • Show a countdown to the next autosave after an autosave fails. (84656)
    • Remove the autosave failure notice once a later save succeeds. (84649)
    • Show the browser backup’s date and compare it before restoring. (84735)
    • Don’t promise a browser backup in save failure notices. (84948)

Notes

  • Add emoji reactions to notes ❤️ 🎉 😄 👀 🚀. (76767)
  • Improve how notes highlight and connect to content. (80578)
  • Make the “Add note” toolbar button add-only and drop the avatars. (84635)
  • Mark the text an unsent note is about with a draft marker. (84125)
  • Remove the divider between the canvas and floating notes. (84850)

Patterns

  • Rename the inserter’s “My patterns” to “Site patterns” and add an author filter. (84680)
  • Support synced patterns the user can read but not edit: list them in the inserter, load them without “Edit original”, and allow detaching them. (84661, 84641, 84681)

Global Styles

  • Add pseudo-selector support for text inputs and select elements. (71634, 81644)
  • Font Library: Mark installed font variants in font collections. (84023)
  • List elements alongside blocks. (81645)
  • Preview the selected state on element screens. (83787)
  • Remove the custom styles dot from the block list. (84657)
  • Style states: Add footer viewport and responsive styles status. (84146)
  • Style states: Enable state-specific custom CSSCSS Cascading Style Sheets.. (83539)

Extensibility

  • Actions and Fields APIs: Register the core entity actions and fields on the server. (84650, 84660, 84696, 84700)
  • Blocks: Accept a feature path array in getBlockSupport and hasBlockSupport. (84708)
  • Rename “fields” to “entity fields”. (84691)

Media

  • Client-side media: Upgrade wasm-vips to 0.0.19 and raise memory budgets. (84980)
  • Generate animated image sub-sizes by default. (80385)
  • Media editor: Add an edits slice to the session and reset the whole session in one step. (83899, 84591)

Icons

  • Add asterisk and form-based icons. (85442, 84074)
  • Experiment with proportional stroke scaling. (84081)
  • Mirror the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) icons to match the other angled icons. (84675)
  • Ship popular icons to the core-admin collection. (85072)

Bug Fixes

  • DOM: Fix getOffsetParent infinite loop on a non-element parent. (84374)
  • Experiments: Don’t invalidate saved option with a legacy key. (84619)
  • Icons: Restore the missing speech bubble in the postComments icon. (85275)

Components

  • BorderControl: Remove double focus outline. (85173)
  • CustomGradientPicker: Keep the color interpolation method when editing a gradient. (84383)
  • DataForm: Center the text control’s prefix and suffix. (84314)
  • DataViews: Fix the page title row jumping on hover when a page type badge is shown. (84368)
  • DropdownMenu: Keep a disabled toggle closed on ArrowDown. (84556)
  • DropdownMenu: Match initial focus to the opening interaction. (85486)
  • Grid: Fix bottomLeft alignment mapping to the bottom left corner. (82641)
  • InputControl: Ignore the drag gesture on touch devices. (81519)
  • Link: Keep the new-tab indicator with the link text. (84806)
  • SearchableChipSelect: Preserve selected chips on Escape. (84172)
  • SearchableSelectControl: Fix search icon orientation. (84690)
  • Select: Preserve scrolling when item alignment falls back. (84682)
  • SelectControl: Fix default options showing the Select placeholder. (85172)
  • Snackbar: Restore focus when used outside SnackbarList. (84342)
  • Tabs: Expand vertical interaction backgrounds and focus rings. (84821)
  • Tabs: Restore fit-content width for horizontal tab lists. (84626)
  • UI: Keep popups open for presses inside their iframes. (83870)
  • UI: Preserve explicit null portal containers. (84370)
  • UI: Show keyboard focus on disabled menu items. (85488)
  • UI: Synchronize popup hover and keyboard targets. (85487)
  • UnitControl: Use a neutral color for static unit labels. (85456)

Post Editor

  • Customize Widgets: Keep the block selected when using wordpress/ui overlays. (84628)
  • Editor: Fix long author name overflowing the Post sidebar panel. (84165)
  • Editor: Keep a preview canvas from adopting the entity’s selection. (84832)
  • Editor: Keep the block toolbar row on phones while no block is selected. (84461)
  • Editor: Validate parent container when converting blocks to template parts. (84155)
  • Ensure “Hide block tools” text isn’t wider than the button background. (85051)
  • Fields: Lock the status and slug fields for users who can’t publish. (84371)
  • Post Taxonomies: Restore shortcuts to create terms. (84601)
  • Post slug: Derive the slug preview from the current title instead of generated_slug. (84893)
  • PostURL: Remove double focus ring outline. (84694)
  • RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.: Save unsaved changes as a revision before restoring a revision. (84590)
  • Style Book: Fix crash when the Heading block is unregistered. (84359)
  • Template field: Show the default template instead of the Select placeholder. (85167)
  • URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: Make cleanForSlug match WordPress Core’s sanitize_title(). (84896)

Notes

  • Focus the new note form once it’s positioned. (84639)
  • Keep the avatar round when it fails to load. (85807)
  • Read note markers from the rich-text record, not its HTML. (84310)
  • Select the note under the caret. (84147)
  • Skip the reaction summary pre-fetch when Core already does it. (85047)

Block Library

  • Accordion Heading: Anchor inline notes to selected title text. (84497)
  • Cover: Decode the oEmbed iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. source before parsing its query string. (83770)
  • Custom HTML: Show a floating marker when the block renders nothing. (84150)
  • Gallery: Let columns override legacy responsive styles. (84360)
  • Icon: Fix display issues in the block manager. (84107)
  • Image: Measure the lightbox container, not the image’s parent. (82312)
  • Layout: Pair physical margins with the physical float on .alignleft and .alignright. (83520)
  • Login/out: Mark the block as content. (84849)
  • Media & Text: Restore content padding in classic themes with a CSS reset. (85200)
  • Navigation Link: Apply “Open in new tab” from the link popover. (83506)
  • Navigation: Fix error when inserting a block via “Browse all” in List View. (84665)
  • Navigation: Keep custom CSS, including from Global Styles, off inner list containers. (84881, 85366)
  • Navigation: Keep the flex layout on a block inserted into an overlay. (82232)
  • Navigation: List only the blocks the sidebar supports in its link search. (85122)
  • Pattern: Load the view record, and the edit record only once it’s loaded. (84799)
  • Search: Don’t clip the button focus outline when the field is collapsed. (84685)

Block Editor

  • Allow block toolbar to wrap when text labels are enabled. (84802)
  • Block Styles: Clamp variation labels to two lines and show the label in a tooltip. (85721)
  • Block Toolbar: Fix UI menus requiring two clicks to open. (84547)
  • Block Toolbar: Keep last item fills out of the placeholder toolbar. (84554)
  • Keep multiline paste inside empty Preformatted and Poetry blocks. (83552)
  • List View: Allow nesting with top level items. (84856)
  • List View: Show appender in contentOnly locked section. (84713)
  • Preserve rich text selection on Shift+click within the same block. (84579)
  • Rich Text: Derive active formats at the caret for input and paste. (84303)
  • Rich Text: Strip every object replacement character in getTextContent. (81526)

Global Styles

  • Add icons and tweak styling for element and block buttons. (85363)
  • Custom CSS: Generate styles for blocks rendered by their parent block. (82590)
  • Custom CSS: Use the correct selector for block style variations on the front end. (84530)
  • Fix inconsistent “Elements” tools panel heading level. (85247)
  • Font Library: Load all installed font families. (84684)

Media

  • Preserve EXIF metadata when converting HEIC to JPEG client-side. (82040)
  • Skip auto-attach on save when attachment pages are enabled. (84851)
  • For published posts, only auto-attach newly added images. (84890)

Interactivity API

  • Align directive name validation with WordPress Core. (81023)
  • Fix late data-wp-html values, throwing functions, and directive conflicts. (84652)
  • Keep server-rendered data-wp-html content for the server’s token representation. (84889)

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)

  • Block Toolbar: Give the phone placeholder button a name and icon when the default block is unregistered. (84533)
  • ColorPicker: Improve accessibility and discoverability of inputs. (70214)
  • Cover: Don’t autoplay an uploaded background video when reduced motion is preferred. (83853)
  • Modal: Keep an accessible name when the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. is hidden. (82645)
  • navigateRegions: Only outline focused Publish and Save regions. (84343)
  • Notes: Drop misleading aria-haspopup from the “Add note” menu item. (84818)
  • PaletteEdit: Name picker dialogs and add screen reader dismissal. (84333)
  • Revisions: Meet AA contrast for the inline deletion diff without an opacity filter. (82258)
  • ToolsPanel: Put setting names first in accessible action labels. (84341)
  • Video: Don’t autoplay on the front end when reduced motion is preferred. (84308)

Performance

  • Cache the theme.json data merged from all origins. (81979)
  • Connectors: Preload REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/ responses on the Connectors screen. (77353)
  • Icon: Speed up rendering of the icon library. (84327)
  • Icons: Skip sanitizing the core icons. (85083)
  • Interactivity API: Optimize toVdom walk. (81699)
  • Site Editor: Preload the entity actions of the screen. (85155)

Documentation

  • Badge: Clarify that badges should not be interactive. (84920)
  • BaseControl: Update prop documentation. (70064)
  • Breadcrumb: Fix usage guidelines sidebar structure. (84564)
  • Components: Update guidance after the Emotion migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.. (85020, 85023)
  • Framework: Improve AGENTS.md guidance around running package scripts. (84195)
  • Menu: Clarify icon, label, and description usage guidelines. (84020)
  • Note reduced-motion handling for autoplaying media. (84594)
  • Storybook: Add more visual pages for all tokens. (84373)
  • Storybook: Keep documentation first by sorting unlisted folders alphabetically. (84563)
  • Storybook: Present motion tokens as an MDX documentation page. (85080)
  • Tabs: Fix filled link icon in Storybook. (84618)
  • UI: Add missing popup width stories. (84320)

Code Quality

  • Custom CSS: Apply changes from the Core review. (84757)
  • Duotone: Sync unsupported attribute type guard from Core. (84801)
  • Global Styles: Ignore theme.json values and preset items of unexpected types to avoid fatal errors. (84523, 84529, 84534)
  • Remove the wordpress/lazy-import package. (84318)
  • Remove unused internal helpers, components, and dependencies. (84575, 85091, 85092, 85093, 85094, 85098)
  • Tests: Use strict assertions in PHPUnit tests. (84510, 84513, 84514, 84515, 84683, 84686, 84883, 84884, 84885, 84886, 84887, 84888)
  • Use the null coalescing assignment operator in singleton getters. (85174)
  • TypeScript:
    • Block Editor: Convert the store, hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., shared components, utilities, InspectorControls, LinkControl, URLInput, typography controls, and useBlockDropZone to TypeScript. (84615, 84616, 84625, 84629, 84655, 84677, 84720, 84725, 84730, 84844, 84848, 84946)
    • Rich Text: Convert to TypeScript. (84324, 84365, 84378, 84610)
    • Commands, Compose, Components, DOM, Preferences Persistence, Primitives, Workflow: Convert to TypeScript. (84315, 84377, 84382, 84611, 84317, 84312, 84375, 84309, 84311, 84361)
    • Convert tests to TypeScript in Data Controls, DataViews, Date, Format Library, Kebab Case, Private APIs, Undo Manager, Upload Media, URL, and Warning. (84852, 84836, 84830, 85032, 84825, 84901, 84895, 84930, 84916, 85085)
    • Blocks: Type the background clip, gradient, position, and repeat supports. (84709)
    • React 19 types: Migrate away from MutableRefObject. (84550)
    • Remove redundant checkJs: false from fully converted packages. (84366)

Components

  • Migrate Emotion styles to SCSS Modules: ColorPicker, CustomSelectControl, DatePicker, DateTimePicker, FocalPointPicker, InputControl, Menu, Navigator, NumberControl, PaletteEdit, RangeControl, SelectControl, Tabs, TimePicker, and UnitControl. (84128, 84131, 84724, 84129, 84736, 84728, 84706, 84565, 84330, 84130, 84562, 84732, 84332, 84331, 84561)
  • Remove Emotion: context system, StyleProvider cache, styling utilities, test and story fixtures, dependencies, and compiler tooling. (84925, 85019, 84929, 84926, 85022, 85021, 85038, 84707)
  • Actions API: Remove the unsupported single action context. (85186)
  • Dialog: Check story and test sizes against popup prop types. (84705)
  • Gradient parser: Switch to the official gradient-parser types. (84582)
  • Simplify RangeControl, Tabs, and BorderBoxControl styles. (85086)
  • Text: Simplify the internal highlighter. (85101)
  • Theme: Consolidate border mode overrides in the token resolver. (84108)
  • Tip: Migrate inserter usages to Notice and deprecate the component. (84197)
  • UI: Consolidate shared iframe dismissal tests. (84296)

Block Editor

  • Block Supports: Share the state text clip helpers with theme.json. (85057)
  • Include migration hint in useSetting deprecation warning. (85100)
  • Rich Text: Remove refs from event listener contexts. (84545)
  • Sorting: Rely on stable standard sort and use toSorted. (52213)

Block Library

  • A11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility): Move prefersReducedMotion into the block library’s shared utils. (84297)
  • Blocks: Clarify button background comment and template part error string. (85176)
  • Media & Text: Replace deprecated word-break with overflow-wrap: anywhere. (82580)
  • Remove compat function for unsupported unprefixed style states. (84531)
  • Rename inspector and toolbar style-states slots for consistency. (84598)

Extensibility

  • Actions API: Extract the core actions into the wordpress/core-actions script modules, and remove the fields that moved to wordpress/core-fields. (84643, 84897)
  • Core Actions, Core Fields: Translate the labels with the default text domain. (85139)
  • Fields API: Take over Core’s registry singleton like the Icons API. (84168)

Tools

  • Props Bot: Queue runs instead of cancelling superseded ones. (84176)

Testing

  • Add an iOSiOS The operating system used on iPhones and iPads. end-to-end test harness and test selecting text across two paragraphs. (84463, 84585, 84640, 84741, 84859)
  • Add end-to-end tests for the autosave failure notice. (84644)
  • Automated Testing: Add AI review guidance for lint suppressions. (84638)
  • Automated Testing: Fix Storybook manifest errors and validate in CI. (84198)
  • Changelog validation: Reject blank lines between Unreleased entries. (84804)
  • DuotonePicker: Add component tests. (69264)
  • Entity Actions: Fix the taxonomy collision test against Core trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running “trunk”, then you are on the latest revision.. (85146)
  • Flaky end-to-end tests: Open settings sidebar in constrained canvas test. (84606)
  • Icons: Add unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. coverage for WP_REST_Icon_Collections_Controller. (83168)
  • React 19 codemod: Apply defaultProps when rendering a memo component. (84568)
  • Tests: Fix HTML comparison tests. (84294)
  • Tests: Fix list item unsafe markup test on older WordPress versions. (84302)
  • Tests: Scope Classic block media checkbox locator. (84524)
  • Upgrade JSDOM to 30.1.2. (84367)

Build Tooling

  • babel-preset-default: Add polyfill list to generated bundle. (84835)
  • Build: Fix npm run dev failing on the patterns tsconfig comment. (84898)
  • Build: Guard SCRIPT_DEBUG with defined() in script and style registration. (83633)
  • Build: Keep absolute paths out of worker source maps. (84163)
  • Build: Update pr-baseline-action to v0.3.0. (84692)
  • CI: Run the required trunk changes cron every 4 hours. (84301)
  • CI: Set explicit retention periods for large artifacts. (84525)
  • Cherry-pick script: Add an optional dry-run parameter. (78878)
  • Packages: Stop publishing tsconfig files, TypeScript build info, tests, and Markdown files other than README.md. (84164, 84307)
  • PR meta: Add a Playground preview link. (84687)
  • PR meta: Log fallback bodies verbatim and keep query strings in run links. (85119)
  • PR meta: Write sections on stacked pull requests. (84703)
  • Project management automation: Convert to TypeScript and move to tools as an internal action. (71193, 85087)
  • Raise the minimum required Node.js to 22 with CJS/ESM interop. (84313)
  • Release Tooling: Publish wp/X.Y branches with their own npm configuration. (84160)
  • Remove some stale overrides. (84674)
  • Update Ariakit to 0.4.42, Base UI to 1.9.0, Terrazzo token tools to 2.9.0, Testing Library user-event to 14.6.8, and Vite to 8.3.4. (84539, 85066, 84542, 85067, 85068, 84544)
  • WP Build: Support importing SVG files as inlined data URIs. (85147)
  • Zed: Exclude node_modules from the file scan and turn off Tailwind CSS. (84604)

Linting

  • ESLint: Align UI caution components with Storybook status. (84319)
  • ESLint: Allow design tokens in component JavaScript. (84827)
  • ESLint: Make jsdoc/escape-inline-tags an error. (84701)
  • ESLint: Remove an unused comments-pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. dependency. (85102)
  • ESLint: Require TypeScript for new files. (84829)
  • ESLint: Require WCSpinner alias for legacy Spinner imports. (84390)
  • JSDoc: Escape WordPress package names in comments. (84369)
  • Stylelint: Consolidate lint rules for simplification. (71235)

Env

  • Update simple-git to v4. (84137)
  • Use the matching wordpress-develop branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a “branch”, such as “the 4.0 branch”. for pre-release PHPUnit tests. (84758)

First-time contributors

The following PRs were merged by first-time contributors:

  • @00kaku: Search: Don’t clip the button focus outline when the field is collapsed. (84685)
  • @anamwp: Revisions: Meet AA contrast for the inline del diff without an opacity filter. (82258)
  • @ariel-maidana: Media & Text: Restore content padding in classic themes with a CSS reset. (85200)
  • @awss1i: DropdownMenu: Keep a disabled toggle closed on ArrowDown. (84556)
  • @bitworks-io: Env: Update simple-git to v4. (84137)
  • @poligilad-auto: Icons: Mirror the tag icons to match the other angled icons. (84675)
  • @preetpatel713: Editor: Fix long author name overflowing the Post sidebar panel. (84165)
  • @rajpreetcodes: Block Editor: Preserve rich text selection on Shift+click within the same block. (84579)
  • @salvatorecorsi: Accordion Heading: Anchor inline notes to selected title text. (84497)
  • @yotatameguchi-boop: Duotone: Sync unsupported attribute type guard from Core. (84801)

Contributors

The following contributors merged PRs in this release:

@00kaku @aaronrobertshaw @adamsilverstein @aduth @amitraj2203 @anamwp @andrewserong @annezazu @ariel-maidana @awss1i @bhaskargurram-ai @bitworks-io @ciampo @CookieDarb @DAreRodz @desrosj @dhruvikpatel18 @dinhtungdu @ellatrix @fabiankaegy @faisalahammad @fushar @gigitux @himanshupathak95 @im3dabasia @jameskoster @jasmussen @jeryj @jorgefilipecosta @joshualip-plaudit @jsnajdr @Kgupta62 @kraftbj @lancewillett @luisherranz @MaggieCabrera @Mamaduka @manzoorwanijk @Mayank-Tripathi32 @mirka @nb @nickchomey @noruzzamans @ntsekouras @oandregal @obenland @poligilad-auto @prasadkarmalkar @preetpatel713 @R1shabh-Gupta @rajpreetcodes @ramonjd @SainathPoojary @salvatorecorsi @sanketio @scruffian @sgomes @shail-mehta @shimotmk @simison @sirreal @Soean @t-hamano @talldan @tellthemachines @vedant-ere @westonruter @yashjawale @yotatameguchi-boop @youknowriad

Kudos to all the contributors that helped with the release! 👏

#block-editor, #core-editor, #gutenberg, #gutenberg-new

Milana Cap Team Updates ·

Documentation Team Update – November 2, 2026

New schema for docs meetings:

Documentation Issue Tracker stats.

Current state

By status:

By version:

By project:

Past month

0 pull requests merged.

37 issues closed.

24 issues were created.

Current projects:

The Documentation team repositories:

#docs

Sumit Singh Training ·

Meeting Agenda for November 3rd, 2026

This week’s meeting will be held on Tuesday, November 3rd, 2026, at 07:00 UTC. The meeting will be held on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, in the #training channel. Anyone is welcome to contribute to the meeting by commenting in Slack threads during the meeting and throughout the following days. Meeting notes will be published by the following Tuesday to incorporate these asynchronous conversations as well.

This week’s meeting will be hosted by @sumitsingh.

1. Intro/Welcome

  • Welcome to all the new teammates who joined the Training Team this week!
  • Icebreaker – What’s one WordPress tip, tool, or trick you’ve discovered recently that you’d love to share with the community?

2. Contributor Updates

  • What have you been working on, and how has it been going?
  • Anything you’ve accomplished since the last meeting?
  • Do you have any blockers?
  • Can other contributors or Training Team members help you in some way?

3. Open Discussions

  • If you have topics you’d like discussed in the meeting, please leave them as a comment on this post.
    • Have you heard the exciting announcement about a NEW FLAGSHIP WORDCAMPWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.?
      • Just like WordCamp Europe, WordCamp US, and WordCamp Asia, the newest flagship event is WordCamp India 2027!
      • Which city will get the opportunity to host this prestigious event? Share your guesses in the comments!

4. News

  1. Meeting Note Takers
  2. Looking for feedback
    • Looking for a [Content] Needs Translation Reviewer. You can see all pending issues here: https://github.com/WordPress/Learn/issues?q=is%3Aissue+state%3Aopen+label%3A%22%5BContent%5D+Needs+Translation+Reviewer%22
    • We are proposing a community-driven review of the Learn WordPress Learning Pathways (User, Developer, and Designer) to identify outdated content and gather improvement suggestions from experienced WordPress users and contributors. Check out this post for details.
    • Team Homepage: @clk87 has shared A block-based prototype for the Training Team homepage to make team pages more engaging and newcomer-friendly. Feedback is welcome via GitHub Issue #3674.
    • Office Hours: The next Office Hours will be held on a weekday because a weekday was preferred, as per the last meeting. The proposed date is November 25, 2026.
    • Text-to-Speech: The team discussed exploring text-to-speech/read-aloud functionality for course lessons. @softglazee has created prototypes, and the team is encouraged to provide feedback before implementation discussions with MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team.
    • Training Team Handbook: The handbook is currently being updated, and team members are encouraged to share suggestions, improvements, and ideas in GitHub Issue #3447.
    • Intermediate PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Developer Course: @mebo has revived the Learning Pathway course and started working on modules and lessons. Team members are invited to review the new content and share feedback, including the “Rendering plugin data” lesson.
  3. Looking for volunteers
    • Help us review and improve the Learn WordPress Learning Pathways – https://make.wordpress.org/training/2026/10/27/help-us-review-and-improve-the-learn-wordpress-learning-pathways/
    • Content Review Volunteers: Volunteers are needed to review and identify content that should be updated or consolidated. Two groups are needed: one for the handbook and one for courses.
    • Lesson Thumbnails: Work has started on creating thumbnails for lessons that need them. Team members are welcome to contribute to the remaining thumbnails through GitHub Issue #3428.
    • Issue Cleanup: The team discussed organising the many open issues into smaller categories and reviewing them systematically.
      • Review Workflow: The proposed process is to review issues one by one, identify outdated or irrelevant items, suggest next steps, and add comments before closing or updating issues.
        • Good First Issues: Contributors can start with issues labeled Good First Issue, especially those related to content feedback, and follow the handbook guide for validating feedback.
        • Issue Categories: The team discussed starting with a specific categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., with Bug issues suggested as a priority. Other options include Needs Translation Reviewer, Unlabeled, Awaiting Triage, and Content Feedback.
        • Next Steps: Team members are encouraged to suggest which category should be reviewed first, after which the issues can be divided among contributors.
      • Goal: Work together to clean up and keep the repository organised.
  4. Updates from last week’s Triage Squad session
    • No triage squad meetings last week
  5. Other announcements and news

5. Come and Contribute

6. Contribution Acknowledgement

  • Badges awarded:
    • No badges awarded this week

7. Project updates

  • A new version of the 50-hour course, WordPress Credits: Intro to Contribution, has been launched. It is integrated with the new Education Platform, where mentors can track student progress through student report cards.

8. Upcoming Online Workshops

  • No workshop scheduled

Nur E Tasfiya

I think beginner-friendly contribution activities are a great way to welcome new contributors. It would be helpful to have more practical tasks and step-by-step guidelines so that beginners can participate with confidence.

Reply

Jeffrey Paul Core AI ·

AI Contributor Weekly Summary – 28 October 2026

This week’s meeting focused on the newly published strategy for making WordPress ready for the agentic web, including coordinated work on the MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts., coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. abilities, OAuth authentication, and user experience. Contributors also discussed a proposed shared abilities package, upcoming AI pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client releases, and the roadmap for delivering a stable MCP experience alongside WordPress 7.2 and preparing for WordPress 7.3.

WordPress for the Agentic Web: Strategy and User Experience

@jeffpaul highlighted the newly published WordPress for the Agentic Web proposal, outlining the team’s priorities across the remaining WordPress 7.2 cycle and into 7.3. The strategy identifies three technical workstreams, MCP Adapter, Abilities, and OAuth authentication, supported by a coordinated user experience (UXUX UX is an acronym for User Experience – the way the user uses the UI. Think ‘what they are doing’ and less about how they do it.) effort to ensure they work together seamlessly.

@karmatosed volunteered to help lead the UX effort, emphasizing asynchronous collaboration and the need to map the complete user journey across these capabilities. @jeffpaul suggested beginning with the experience described in the proposal and identifying how the individual workstreams contribute to each step.

@apeatling also highlighted that user experience will vary significantly depending on which AI client or agent someone uses, requiring ongoing testing and refinement rather than a single implementation.

Contributors are encouraged to review the proposal and volunteer to help lead or contribute to the workstreams.

Shared WordPress Abilities Package

@nikskyverge shared a prototype for a centralized WordPress Abilities package, designed to simplify how abilities are developed, distributed, and eventually incorporated into WordPress core.

Currently, abilities may need to be maintained separately across the AI plugin, MCP Adapter, and other integrations. The proposed package would provide a shared implementation that these projects could consume without duplicating development work. The approach could also benefit third-party developers who want to use specific abilities without depending on an entire plugin. @nikskyverge is additionally exploring tooling to streamline the process of promoting abilities into WordPress core.

The prototype remains experimental, with outstanding considerations around autoloading, version management, and compatibility. The immediate priority remains getting useful abilities into the AI plugin and MCP Adapter, with the shared package potentially simplifying that work going forward.

AI Plugin 1.5.0 and AbilityAbility A registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. Compatibility

@jeffpaul and @dkotter shared that AI plugin version 1.5.0 was targeted for release on October 29. The release includes continued work on custom abilities, incorporating changes aligned with implementations being developed for WordPress core.

@justlevine raised concerns about potential breaking changes to ability schemas between versions 1.4.0 and 1.5.0, including renamed abilities and changes to existing interfaces. The team clarified that most content abilities are new to 1.5.0, limiting compatibility concerns for existing installations. However, settings abilities and other previously available functionality may require additional review.

Because these abilities remain part of an experimental feature, compatibility guarantees differ from those of stable functionality. Nevertheless, contributors agreed that any identified breaking changes should be clearly documented in the release changelog.

@justlevine will review the changes, while @dkotter will ensure relevant compatibility information is included in the release notes.

Contributors with outstanding pull requests targeted for 1.5.0 were encouraged to address remaining review and testing feedback promptly.

PHP AI Client 1.5.1

The team also discussed an upcoming maintenance release of the PHP AI Client, version 1.5.1, targeted for October 28 or 29. This release includes fixes following the PHP AI Client 1.5.0 integration into WordPress 7.2 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.

The goal is to incorporate the updates into WordPress 7.2 Beta 3, or Beta 4 at the latest, ensuring the fixes receive additional testing before the final WordPress release.

MCP Adapter Roadmap and WordPress 7.3

@justlevine provided an MCP Adapter update, noting that work continues on open pull requests and potential improvements to the adapter’s internal implementation.

Contributors were encouraged to review MCP Adapter issue #402, which collects user stories, technical improvements, testing requirements, and related work needed to deliver a more complete MCP experience.

@jeffpaul proposed targeting a stable MCP Adapter 1.0 release around December 8, alongside WordPress 7.2. This would provide an opportunity to gather real-world feedback and iterate ahead of the WordPress 7.3 development cycle. The proposed timeline would require any planned core integration for WordPress 7.3 to be ready for review ahead of Beta 1, tentatively expected in the first quarter of 2027. The scope and timing of MCP Adapter 1.0 remain open for further discussion.

@apeatling emphasized that delivering useful abilities should be the highest priority, since connecting an agent to WordPress provides limited value unless it can perform meaningful site operations.

The team also discussed whether additional abilities should be considered for WordPress 7.2 after Beta 1. While there may be opportunities to include sufficiently mature functionality, contributors cautioned against introducing unnecessary release pressure when experimental plugins can already make those abilities available for testing.

@nikskyverge will coordinate with @ovidiu-galatan to determine whether the MCP Adapter should consume abilities through the proposed shared package or integrate them directly in the short term.

Next Steps

  • Agentic Web UX: @karmatosed will begin mapping the end-to-end user journey and coordinating UX considerations across the MCP Adapter, Abilities, and OAuth workstreams.
  • Shared abilities package: @nikskyverge will continue refining the prototype and coordinate with @ovidiu-galatan on MCP Adapter integration.
  • AI plugin 1.5.0: Contributors will address outstanding pull request feedback ahead of the targeted release.
  • Ability compatibility: @justlevine will investigate potential breaking schema changes, with @dkotter ensuring they are documented in the changelog.
  • PHP AI Client 1.5.1: Finalize the maintenance release and prepare its fixes for inclusion in WordPress 7.2 Beta 3 or Beta 4.
  • MCP Adapter roadmap: Continue reviewing issue #402, prioritize foundational abilities, and refine the proposed scope for a stable 1.0 release.
  • Meeting documentation: @justlevine will share the draft meeting handbook, and @nikskyverge will review it and provide feedback.

Upcoming Meetings

  • Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
  • AI Team Office Hours: Thursday, October 29, 2026 at 17:00 UTC.

Props to @gziolo for pre-publish review.

#core-ai, #summary

Jenish Kotiya Training ·

Training Team Meeting Recap – 27th October 2026

This meeting followed the meeting agenda in GitHub and P2 Post.
You can see conversations from the meeting in this Slack Log. (If you don’t have a SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ account, you can set one up.)

Introductions and Welcome

There were 23 attendees: @alkesh7, @clk87, @pravin1996, @mrinal013, @noruzzaman, @Dhruvang21, @rfluethi, @jenish1234, @mosescursor, @makanikaran, @praful2111, @dilip2615, @vasantrajput, @harshjadav003, @sonaliprajapati, @andrewssanya, @ravigadhiyawp, @sumitsingh, @gohelkunjan, @nitspatel (async), @upekar99 (async), @mohkatz (async), @valeriewandeler (async)

Newcomers: @daxinigaurav, @thenizampur, @atikurpub

Meeting hosted by: @devmuhib

Note Taker: @jenish1234

Note Reviewer: @vasantrajput

Welcome! Please post in the #training channel or reach out to a team member to help you with contributing. Resources to check out our onboarding program, and our Guide Program.

Contributor Updates

  • What have you been working on and how has it been going?
    • @mosescursor was working to get his way back to the team. And he has been a bit taken up by:
      1. Community Team activities and Campus Connect
      2. Working on a booking pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. for speakers and volunteers who can allocate slots on their personal sites
  • Anything you’ve accomplished since the last meeting?
  • Do you have any blockers?
  • Can other contributors or Training Team members help you in some way?
  • Something we did in the community team that I loved, I do not know if it is possible here
    • @mosescursor: Something we did in the community team that I loved, I do not know if it is possible here
      • Having a contribution specific Office hour..
        • In this hour, we choose one area and focus on it and do things as a team.
        • This helps new people learn but also old members remember
      • I would really love a group contribution session.
    • @devmuhib: Nice idea! We can definitely try. But finding a dedicated member to execute with responsibility is hard. @mosescursor, if you can manage time and try few weeks, this would be very helpful. or we can discuss in office hour about it.
    • @vasantrajput: Nice idea! @mosescursor we love to know more about this, so please share more details on tomorrow’s Office Hours meeting on Zoom Call.
    • @mosescursor: @devmuhib your so right. We need someone that’s experienced and we need to start with what they feel most comfortable about.
    • We have @sumitsingh, @rfluethi, @rjekic, @psykro among others. We can start with those.
    • @psykro: There are a number of ways to do this. Something that the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team does which I quite like (not sure if they still do) is they have a “new contributors” meeting once a week (usually on the same day as the main core meeting). So it’s the same as the regular weekly meeting, held via text in Slack, but someone is around to help new folks find things to work on, answer questions etc. Obviously the only downside to something like that is that it’s timezone dependant. Maybe it’s something we could plan for during each weekly meeting, and ask for facilitators (the same way as we ask for meeting notetakers) from a list of folks who’ve offered to facilitate? I probably can’t do every week, but I could say do one a month, sharing the load with 4 or 5 other contributors.
    • @rfluethi: Building on @mosescursor ‘s idea and @psykro ‘s point about sharing the load, here’s a proposal we could discuss at the next Office Hours:
      • Group contribution projects:
      • Small, time-boxed projects where new and experienced contributors work together. Newcomers learn on real work, experienced folks share what they know.
        1. Pick a topic: At the monthly Office Hours we discuss a topic and one person volunteers as coordinator.
        2. Open an issue: The coordinator opens a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ issue with the goal, expected challenges, what’s out of scope, when it counts as done, a target end date (4 to 6 weeks) and the skills needed.
        3. Find contributors: The coordinator presents the project at the Tuesday meeting and invites contributors, both new and experienced.
        4. Kick-off: A short kick-off where we break the project into tasks. Tasks suitable for newcomers are labeled and each gets an experienced buddy.
        5. Work: The coordinator assigns tasks, keeps in touch via Slack and GitHub, helps with blockers and connects the right people. Tasks without an update for two weeks go back to the pool.
        6. Status: At least once a month the coordinator shares a short update in the Tuesday meeting and invites more people to join. Bigger problems go back to Office Hours.
        7. Wrap-up: Once the goal is reached, we close the project in the Tuesday meeting with a short retro and props to everyone involved.
      • Since Office Hours is monthly, we’d have one or two projects running at a time at most, which keeps the load manageable. What do you think?
    • @mosescursor: This is a perfect buildup, @rfluethi, I’m with you

Open Discussions

  • If you have topics you’d like discussed in the meeting, please leave them as a comment on this post.
  • Have you heard the exciting announcement about a NEW FLAGSHIP WORDCAMPWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.?
    • Just like WordCamp Europe, WordCamp US, and WordCamp Asia, the newest flagship event is WordCamp India 2027!
    • Which city will get the opportunity to host this prestigious event? Share your guesses in the comments!
      • @vasantrajput: I think Ahmedabad will get the opportunity to host the newest flagship event, WordCamp India 2027!
        • What do you think? Could Ahmedabad be the next big destination for the WordPress community?
        • @sumitsingh: 100% it will become the next big destination for the WordPress community as a 4th flagship event.
        • @utsav72640: Absolutely! Ahmedabad has all the potential to become the next big destination for the WordPress community and host the 4th flagship event! With our passionate local community, collaboration, and growing enthusiasm, let’s make it happen together!
        • @sonaliprajapati: I truly believe Ahmedabad is ready to shine on the national WordPress stage! With the dedication of our community, a culture of inclusivity, and a shared vision for the future, we have a wonderful opportunity to bring WordCamp India 2027 to our city. Let’s turn this exciting possibility into a milestone for the WordPress ecosystem!
        • @dilip2615: That would be amazing. It would be great to see Ahmedabad host WordCamp India 2027.

News

Meeting Note Takers

Here is our current note-taker roster:

Important note: If anyone needs more information on note-taking or a guide to creating a Recap Note Post, they can DM Vasantsinh Rajput. He will guide you on a Recap Note, and he will review & publish your Recap Post.

Looking for feedback

Looking for volunteers

  • Content Review Volunteers: Volunteers are needed to review and identify content that should be updated or consolidated. Two groups are needed: one for the handbook and one for courses.
  • Lesson Thumbnails: Work has started on creating thumbnails for lessons that need them. Team members are welcome to contribute to the remaining thumbnails through GitHub Issue #3428.
  • Issue Cleanup: The team discussed organising the many open issues into smaller categories and reviewing them systematically.
    • Review Workflow: The proposed process is to review issues one by one, identify outdated or irrelevant items, suggest next steps, and add comments before closing or updating issues.
      • Good First Issues: Contributors can start with issues labeled Good First Issue, especially those related to content feedback, and follow the handbook guide for validating feedback.
      • Issue Categories: The team discussed starting with a specific categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., with Bug issues suggested as a priority. Other options include Needs Translation Reviewer, Unlabeled, Awaiting Triage, and Content Feedback.
      • Next Steps: Team members are encouraged to suggest which category should be reviewed first, after which the issues can be divided among contributors.

Update for last week’s triage squad

  • No triage squad meetings last week

Other news

Come and Contribute

This week’s contribution focus area

  1. Content ready for review: 9 issues. See Guidelines for reviewing content.
  2. Feedback awaiting validation: 17 issues. See Guidelines for Validating and Applying Content Feedback.
  3. Topics awaiting vetting: 2 issues. See Guidelines for Vetting Topic Ideas.
  4. Validated feedback awaiting fix: 26 issues. See Guidelines for Validating and Applying Content Feedback.

Contribution Acknowledgement

  • Badges awarded:
    • No badges awarded this week
  • GiveProps:

Project updates

  • A new version of the 50-hour course, WordPress Credits: Intro to Contribution, has been launched. It is integrated with the new Education Platform, where mentors can track student progress through student report cards.

Upcoming Online Workshops

There is no workshop scheduled for this week.

Wrap up

If you have topics you’d like discussed in the meeting, please leave them as a comment on this issue.

Thanks to all who participated in sync and to those who will in the future.

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.

#meeting-recap, #training, #training-team

dhruvkb Openverse ·

A week in Openverse: 2026-10-26 – 2026-11-02

openverse

Merged PRs

APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.

  • #5650: Bump certifi to 2026.10.19 to drop compromised emSign CA

Catalog

  • #5650: Bump certifi to 2026.10.19 to drop compromised emSign CA

Documentation

  • #5617: Fix typos in documentation
  • #5650: Bump certifi to 2026.10.19 to drop compromised emSign CA
  • #5661: Update to Nuxt 4, @nuxtjs/i18n 10 and Tailwind 4; disable Storybook

Frontend

  • #5660: Require Node 22.23.4 for Brotli decoder RCE (CVE-2026-111497)
  • #5661: Update to Nuxt 4, @nuxtjs/i18n 10 and Tailwind 4; disable Storybook
  • #5665: Stop writing the Sentry auth token into the frontend image
  • #5668: Update dependency nock to v14.0.17

Management

  • #5650: Bump certifi to 2026.10.19 to drop compromised emSign CA
  • #5660: Require Node 22.23.4 for Brotli decoder RCE (CVE-2026-111497)
  • #5661: Update to Nuxt 4, @nuxtjs/i18n 10 and Tailwind 4; disable Storybook

openverse-infrastructure

Merged PRs

Infra

  • #1169: Replace removed git-crypt pre-commit hook with a local one
  • #1170: Drop inbound TCP packets with IP options to mitigate CVE-2026-98432

Management

  • #1169: Replace removed git-crypt pre-commit hook with a local one
  • #1170: Drop inbound TCP packets with IP options to mitigate CVE-2026-98432

#openverse, #week-in-openverse

Teams

  • Core

    The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team makes WordPress. Whether you’re a seasoned PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php, HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites., JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com or CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. developer or are just learning to code, we’d love to have you on board. You can write code, fix bugs, debate decisions, and help with development.

  • Design

    The design group is focused on the designing and developing the user interface. It’s a home for designers and UXers alike. There are regular discussions about mockups, design, and user testing.

  • Mobile

    The mobile team builds the iOSiOS The operating system used on iPhones and iPads. and Android apps. Lend them your Kotlin, Swift, or ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org Native skills. The team also needs designers, UXUX UX is an acronym for User Experience – the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. experts, and testers to give users a smooth experience on every device.

  • Accessibility

    The a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) group provides accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) expertise across the project. They make sure that WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and all of WordPress’ resources are accessible.

  • Polyglots

    WordPress is used all over the world in many different languages. If you’re a polyglot, you can help by translating WordPress into your own language or contributing to the GlotPress project, making translations easier and more effective for everyone.

  • Support

    Answering questions in the support forums, IRC, or SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ is one of the easiest ways to start contributing. Everyone knows the answer to something! Since the forums run on bbPress, you can also contribute by helping make the software behind them even better.

  • Documentation

    Good documentation lets people help themselves when they get stuck. The docs team is responsible for creating documentation and is always on the look-out for writers. The blog has discussion around the team’s current projects.

  • Themes

    The Theme Review Team reviews and approves every Theme submitted to the WordPress Theme repository. Reviewing Themes sharpens your own Theme development skills. You can help out and join the discussion on the blog.

  • Plugins

    If you are a PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. developer, subscribe to the Plugin review team blog to keep up with the latest updates, find resources, and learn about any issues around Plugin development.

  • Community

    If you’re interested in organizing a meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. or a WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more., the community blog is a great place to get started. There are groups working to support events, to create outreach and training programs, and generally support the community.

  • Meta

    The MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team makes WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, provides support, and builds tools for use by all the contributor groups. If you want to help make WordPress.org better, sign up for updates from the Meta blog.

  • Training

    The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

    If you enjoy teaching people how to use and build stuff for WordPress, immediately stop what you’re doing and join our team!

  • Test

    The Test Team works to improve WordPress quality and usability by advancing the development process through manual and automated testing. Whether through a browser, app, terminal, or code, the team focuses on testing across the entire WordPress ecosystem, including CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, mobile apps and themes, and feature plugins and importers.

  • TV

    The TV team reviews and approves every video submitted to WordPress.tv. They also help WordCamps with video post-production and are responsible for the captioning and subtitling of published videos. Reviewing videos is a great way to learn about WordPress and help the community: experience is not required to get involved.

  • Marketing

    The Marketing team is currently archived to make room for an experimental shift in focus and processes. Check out the WordPress Media Corps to learn more. Amplification requests and Showcase activities are still running, and you can find out more about them on GitHub.

  • CLI

    WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ is the official command line tool for interacting with and managing your WordPress sites.

  • Hosting

    The Hosting team maintains distributed testing software that tests pre-release versions of WordPress on hosting systems, and infrastructure-focused documentation.

  • Tide

    Tide is a series of automated tests run against every pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and theme in the directory and then displays PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php compatibility and test errors/warnings in the directory.

  • Openverse

    Openverse is a search engine for openly-licensed media. The Openverse team implements new features and new media types; maintains the public APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and front-end search engine; and develops WordPress integrations to share Openverse with the entire WordPress community.

  • Photos

    The Photo Directory team moderates every photo submitted to the WordPress Photo Directory, maintains and improves the directory site itself, and provides resources and documentation to educate, encourage, and facilitate photo contributors.

  • Core Performance

    The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. performance team is dedicated to monitoring, enhancing, and promoting performance in WordPress core and its surrounding ecosystem.

  • Playground

    The Playground team works on WordPress Playground: the platform that lets you run WordPress instantly on any device without a host, most often in a browser.

  • Core AI

    The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI Team coordinates and accelerates AI efforts across the project, focusing on responsible innovation that aligns with WordPress values. We use a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.-first approach to explore AI-powered features, share a public roadmap, and collaborate with other teams.

  • Core Program

    The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Program team is focused on strengthening coordination across teams, improving efficiency and empowering contribution. It’s a home for those who span across product and project work.

All teams and their meetings

Not sure which team to contribute to?

Check out our contributor wizard and find how to get started.

Shape the future of WordPress

Become a Five for the Future participant.

WordPress.org

The WordPress® trademark is the intellectual property of the WordPress Foundation.

Code is Poetry