165. Mētis, WordPress’s flagship theme

·

Mētis is WordPress’s most advanced theme, and it will launch alongside Ipsum as the default theme for WordPress 7.2.

Remember that you can listen to this program from:

Program transcript

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from November 9 to 15, 2026.

Mētis, the most advanced theme the team was working on before Ipsum was chosen as the default theme for WordPress 7.2, returns as WordPress’s “flagship” theme.

The idea is to separate two roles: a default theme has to serve any site, while a flagship one can go further and showcase what the editor can do today.

It takes its name from a Greek word that means cunning intelligence, the kind Odysseus had, and it is designed for creators who work across several formats and find their way as their work changes. It was built from the Site Editor and with real content from the start. It includes six base sites, with their page templates and patterns: business, news, magazine, portfolio, writer, and personal, plus three post layouts, three headers, and five interchangeable footers.

It also ships fifty section patterns, grouped by category and named after their description, something designed for people and also for AI agents, and six style variations that change the typography and color of the entire site, one of them a dark version of the default design. Each palette adds day and night gradients that switch automatically when the device enters dark mode, and nine open-source font families are included.

WordPress 7.2 is entering its final stretch: Beta 5; the first release candidate is scheduled for November 17, with string freeze, and the final release arrives on December 8. This beta adds email notices when an application password is created, better keyboard navigation through the toolbar, accessibility refinements in the visual history, stricter permissions for Notes reactions, and fixes for MP3 uploads and for automatic updates on installs using a Git worktree, and Ipsum receives another round of improvements. In addition, all known compatibility issues with PHP 8.6, scheduled for November 19, have been resolved, although each site should check its plugins and themes before upgrading.

The main star is the Secrets API, which stores credentials such as API keys or OAuth secrets encrypted with libsodium, keeping a previous version so they can be rotated. It requires a WP_SECRETS_KEY constant in wp-config.php: new installs receive it from the installer, but existing sites don’t, and without it the API stays disabled, something hosting providers will have to handle in their provisioning scripts. A host can also change the storage or connect an external secrets manager, even read-only, through a secrets.php file. The Hosting team is asking for testing before November 17, not only of this API but of the two update paths, which leave different old files depending on whether you update from the dashboard or with WP-CLI, and of the new /random/ route, which requires regenerating the rewrite rules and purging the cache after updating, and whose cost grows with the number of posts.

There is more news for developers. Text shadow becomes a block support, enabled by default on Paragraph and Heading, with two presets, Light and Strong, which themes can extend in theme.json and users can manage in Global Styles. The editor components complete the migration from Emotion to SCSS modules, introduce a presentation property for color and gradient swatches, which replaces asButtons, and deprecate eight components, such as Animate, Divider, Surface, or Tip, with removal planned for 7.4. Separately, the Presence API, which shows who is connected and what they are editing and moves editing locks into its own table, is in testing as a step before proposing its merge into core; for now it is not a confirmed part of 7.2.

WordPress officially introduces Reprint, a free and open-source tool written in PHP that copies the files and database of a WordPress site, available as a plugin in the directory along with the command-line client that performs the copy. It is another piece of WordPress’s data liberation work started in 2024: exporting posts and pages was already possible, but moving a site also involves the theme, plugins, uploads, and settings. The uses it proposes are copying a site to a new host, checking on the copy that pages load, images appear, and forms work before sending visitors there, with a step-by-step guide for the final switch, or creating a test copy, on your computer or in the experimental version of Playground, to try a design, a plugin, or an update.

What sets it apart is how it copies. It sends files and database directly to the chosen machine or server, piece by piece, without going through an external service and without the source host having to reserve space for a compressed archive of the entire site. If the connection drops, it resumes from the last saved point; if a new address is specified, it updates the old links, relying on the WordPress importer’s method, including links stored in settings, blocks, shortcodes, and complex structures such as serialized data or custom fields, without corrupting tables. When copying repeatedly, it detects what changed since the last time and transfers only the necessary files.

Gutenberg 24.4 continues refining collaboration with Notes. You can now search comments, replies, and author names, and filter by open or resolved notes. The reaction picker is compacted into a horizontal row that leaves the conversation visible, and two new reactions arrive, thumbs up and more. Global Styles gets an “Overridden by” list for elements such as headings, links, or buttons, which shows which core blocks have styles that take precedence and links to their settings so you can fix it without searching the full block list. Content-only editing improves in more blocks, the experimental media editor, still in testing, shows PDF previews and file details, and when restoring a browser backup, the current content is saved first, a useful safeguard for drafts.

Matt Mullenweg opens a security discussion following a report from Joe Youngblood that surprised him: the conservative approach sanitize_username takes when cleaning usernames is not applied to registrations when the site is not multisite. His approach is to assume that every attempt to create, read, update, or delete data is hostile and to ask where else what WordPress accepts can be narrowed. For usernames he proposes stricter rules for new registrations without breaking compatibility with existing ones. And just as comments arrive moderated by default, he suggests reviewing every email WordPress sends so it is less interesting to spammers, for example by having comment notifications leave out the content and only link to the moderation screen.

The comments offer support and several extensions. It is pointed out that user registration on multisite is both less and more restrictive than on a normal site, with other cleanup functions and, for example, a four-character minimum that bothers anyone named “sam,” and there is a case for unifying the behavior; some even ask whether there should be a roadmap to make every site multisite. It is also noted that media attachment pages still have open comments on existing sites and there is no global option to close them, or the same caution is requested regarding user enumeration, which facilitates brute-force attacks, and regarding public display names by default and the activation of author pages. For now it is an open discussion, with no changes announced.

The AI team outlines how the work is divided for the upcoming WordPress 7.3.

Among other items, the discussion covers where Abilities will live: it is proposed that the core root be the source of truth once development reopens, syncing them with the MCP adapter so new capabilities can be delivered before they reach a WordPress version, and it was agreed that schemas that only serve models and agents can evolve more freely than core schemas, which must maintain compatibility. On OAuth, there is a first prototype with a minimal subset of the protocol, which will continue to be tested in a branch of the adapter, and the group supports bringing it into core regardless of whether the adapter is included. RAG, content retrieval for AI applications, was also discussed: embeddings are part of the 7.2 work, but there is no decision yet on whether RAG belongs in core or in plugins.

On what will ship with WordPress 7.2, the group asks for continued testing of the Secrets API, especially on multisite, preparing developer notes for the Abilities API before RC1, and more feedback on a change to Abilities permissions that, if it doesn’t receive support, could be reverted. It was approved to move the shared Abilities into their own Composer package within the WordPress organization on GitHub, so projects such as WooCommerce can use them without installing the entire AI plugin, avoiding the core prefix so they don’t clash with core’s own.

The AI 1.6.0 plugin, planned for the end of the month and the last major regular release before 7.2, will introduce a workspace with a chat agent inside WordPress, with connections already configured. The team also reviewed the dependencies of the AI PHP client, the publication of documentation, and a scanner that would save the Abilities plugins register as plugin metadata, so they can be discovered in the directory.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *