A hackathon instead of a workshop, a sold-out WordCamp full of students, and a first contribution in an hour
Meetup Organizer Newsletter | October 2026
Hola, and hello. Welcome to your monthly roundup of practical ideas, community updates, and results from organizers around the WordPress community.
Worth celebrating

WordPress Youth Day Nicaragua. Kids and teenagers in Managua spent Saturday, October 10 building websites and online stores at the third WordPress Youth Day Nicaragua, in hands-on workshops split by age from 9 to 18.
The organizers’ recap counts 113 participants: 62 of them at their first official WordPress event, and 52 of them girls.
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. Guatemala. Organizers planned for 150 people on October 10 and welcomed 162, with 20 speakers across two tracks and about 30 organizers and volunteers.
WordCamp Costa Rica. The September 18 and 19 event sold out at 368 attendees, and at least 100 of them came from Campus Connect UCR Esparza and Campus Connect BeeNova. The second-place student from the UCR Esparza showcase featured in last month’s issue was one of the speakers, with a talk on reading the data your WordPress site already collects.
New groups. Limón, Costa Rica joined the meetupMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. chapter program on October 14, the same week as Gandia in Spain, Mostviertel in Austria, Cincinnati in the US, and Gwalior in India. Graz became Austria’s fourth meetup city in September, and Philadelphia held its first WordPress meetup in a very long time on September 24.
What happens when the workshop becomes a challenge

Campus Connect organizers in Dhaka noticed that students already line up for hackathons and programming contests, so they tried one at Stamford University Bangladesh: two days of online hackathon, then a day of seminar and workshop. Around 180 people registered, about 100 of them for the hackathon, across three tracks for beginners, designers, and developers. The result was 40 websites and 82 new 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/ profiles.
The write-up is honest about what did not work. About half of the registered students never took part in the hackathon, and some beginners stopped when they got stuck with nobody online to help. The organizers are now weighing a sequence of a Learn WordPress course, then a workshop, then the hackathon, and they are asking for ideas in the comments.
It lines up with new guidance for Campus Connect: build each event around something students actually do, such as creating a WordPress.org account, building a first site, or making a first contribution, rather than a day of talks. The Event Formats & Standards handbook page has been updated to match, so check it as you plan.
And when students build something, give them a stage. Making space for the next generation of WordPress builders describes students presenting their sites at WordCamp Europe 2026, and a sponsorship tier that brought WordPress Credits graduates to the event as volunteers and contributors.
Three formats to borrow this month
- A one-hour contribution session. WP LATAM ran its first online mini contribution session on September 30: 20 photos submitted to the Photo Directory, 10 strings translated, and one video subtitled, with 80% of attendees contributing in those areas for the first time. A draft guide for mini contributor sessions covers 30 and 60 minute versions, and its authors want organizers to try it and report back.
- Bring 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.. When storms cut transport links across Chiba Prefecture, the Chiba WordPress Meetup moved its September 27 meeting online and asked everyone to introduce one favorite plugin. Two people the organizer had met at other meetupsMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. gave lightning talks on plugins they are building, and several attendees showed plugins of their own. It works online or in a room, and it needs almost no preparation.
- A campus series with a name for each stop. Campus Connect Surat ran its sessions as a named journey across partner colleges, starting with Aarambh, “the beginning.” Across three colleges, more than 470 people registered and more than 300 students attended, and one college asked the team to run a similar session for its faculty.
Group of the Month: WordPress Ahmedabad, India

The September WordPress Ahmedabad Meetup drew more than 80 people, and one of its organizers spent the same month taking WordPress to three campuses. Campus Connect at OM Education Campus, Junagadh on September 7 and 8 was the first WordPress community event in Junagadh, and more than 90 students built their first website on day two. Adani University, Ahmedabad followed on September 19 with more than 80 students, then Gyanmanjari Innovative University, Bhavnagar on September 28 with more than 150 students, more than 15 faculty members, and coverage in the local newspaper. For an established group, the pattern is worth copying: lend the people and habits you already have to a nearby city that has never had a WordPress event.
Also worth knowing
Meetup groups are moving to events.wordpress.org
An update on community groups explains the move off Meetup.com for roughly 700 groups. Members will join the new groups themselves with a WordPress.org account, so start asking your members to create one now. Groups willing to run real events on the new platform as a pilot can say so in the comments, especially groups outside Europe and North America and groups that don’t meet in English.
Who can organize a meetup event?
A Tokyo co-organizer asked a fair question after three handbook pages seemed to disagree. The answer they got: any community member can run an event without being a co-organizer, but should coordinate with the group’s co-organizers, who confirm the person is trustworthy and following the Five Good Faith Rules. The post proposes writing that down in one place. Add your view in the comments.
Students are organizing their own Campus Connect
Campus Connect Universidad Fidélitas in San José on November 12 and 13 is the WordPress Credits contribution project of three students, one of them the lead organizer. The tickets include a “Conectá a alguien” option that helps cover materials for the students attending.
Keep your event website working after the event
Instead of leaving a dead countdown and a ticket button, turn it into a closing page: photos with credits, talks with slides and WordPress.tv links, recaps, and a clear invitation to join your local group. WordCamp Costa Rica 2026 is doing it now, so you can watch theirs change.
Organizing in the US or Canada?
Events in the US and Canada: the plan through 2027 lays out three stages, starting with getting meetups back on track, and offers a menu of event types rather than a mandate. It is worth reading in full if you organize there.
A profile marker for Campus Connect participants?
A proposal suggests marking Campus Connect and WordPress Credits participants on their WordPress.org profiles, along with their mentorEvent Supporter Event Supporter (formerly Mentor) is someone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues. or facilitator, so experienced contributors know who to welcome and support. Comments are open.
By the numbers
368
attendees filled a sold-out WordCamp Costa Rica, at least 100 of them from Campus Connect.
162
people came to WordCamp Guatemala, against a plan for 150.
82
new WordPress.org profiles came out of the Campus Connect hackathon at Stamford University Bangladesh.
80%
of attendees at WP LATAM’s first contribution session were contributing in those areas for the first time.
Meetups of the Month





















Coming up
| Date | Event | Where |
|---|---|---|
| Oct 24, 2026 | WordPress Day for AI Faro 2026 | Faro, Portugal |
| Oct 24, 2026 – Oct 25, 2026 | WordCamp Islamabad 2026 | Islamabad, Pakistan |
| Oct 24, 2026 – Oct 25, 2026 | WordCamp Sofia 2026 | Sofia, Bulgaria |
| Oct 25, 2026 | WordPress Campus Connect Trasa CoWorking Space, Tegal | Tegal, Indonesia |
| Oct 30, 2026 | WordCamp Johannesburg 2026 | Johannesburg, South Africa |
| Oct 30, 2026 – Oct 31, 2026 | WordCamp Brasil 2026 | Belo Horizonte, Brazil |
| Oct 31, 2026 – Nov 1, 2026 | WordCamp Valencia 2026 | Valencia, Spain |
| Nov 5, 2026 – Nov 6, 2026 | WordCamp Canada 2026 | Vancouver, Canada |
| Nov 6, 2026 | WordCamp Manchester 2026 | Manchester, UK |
| Nov 12, 2026 – Nov 13, 2026 | WordCamp Netherlands 2026 | Netherlands |
| Nov 12, 2026 – Nov 13, 2026 | WordPress Campus Connect Universidad Fidélitas, San José | San José, Costa Rica |
| Nov 13, 2026 – Nov 14, 2026 | WordCamp Pisa 2026 | Pisa, Italy |
| Nov 14, 2026 | WordPress Campus Connect Manila, Philippines | Metro Manila, Philippines |
Local meetups run in far more places than this. Everything, everywhere, is on events.wordpress.org.
Open calls for speakers:
Worth passing to your group. Someone who has never spoken before is usually one nudge away from it, and a first talk at a nearby WordCamp is how a lot of organizers started.
- WordCamp Delhi closes Sunday, October 25.
- WordCamp Asia 2027 closes November 8.
- WordCamp Bandung opens October 19 and closes November 8.
- WordCamp Nepal 2027 closes November 15, and welcomes first-time speakers with 10-minute lightning talks.
- WordCamp Mumbai 2027 closes November 30.
Over to you
Have you tried a contribution activity at your meetup, even a small one? Tell us what people finished and what got in the way, so the next organizer can plan around it.
Reply in the comments below, in #community-events, or by email to support@wordcamp.org, whichever you already use.
This newsletter is built from what you share!
Send your recaps and photos and your group goes in Meetups of the Month. Every group that shares one is included, so ask your group’s permission and send it. Group of the Month is for a story another organizer can learn from, and you can put any group forward including your own.
Did we miss your event? Possibly, and we would rather know. Send your recap in #community-events or #campusconnect for the next issue, which publishes Friday, November 13.
Tell us what you want to read here too. If there is a section missing, a format you want explained, or a question you wish someone would answer, say so and we will build it into the next issue.
Need support or guidance?
The Community Team is here to help. Email support@wordcamp.org or join us in #community-events on the Making WordPress 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/.
Each issue opens with a greeting from a language spoken where one of the featured groups is based. This month it is Spanish, for the organizers in Nicaragua, Guatemala, and Costa Rica featured above. If you would like your language to open an issue, tell us.
Thanks for everything you do to grow and support the WordPress community.
WP Feature Notifications weekly update: 2026-10-16
This is the first in a series of weekly status update posts from the WP Feature Notifications work.
Security PRS
There are 30+ open Dependabot PRs that will resolve various dependency security alerts across the repository. It would be really helpful if any contributors have time to help review these PRs, or fix any merge conflicts (using the @dependabot rebase comment).
0.3.0 release tracking issue
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 #302 has been updated to include any open (and newly created) issues that will make the 0.3.0 (aka MVPMinimum Viable Product “A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development.” – WikiPedia) release possible. This tracking issue now lists the 16 open items required for the 0.3.0 release.
All development work toward releasing 0.3.0 will focus on these 16 open issues, and contributors are invited to focus their efforts on them.
Office hours
I will be restarting weekly office hours, during which time anyone can ask for help, support, or questions about the project. These will take place every Thursday starting on Thursday, October 22, 2026 at 11:00 am UTC in the #feature-notifications channel in Slack.
Thanks for getting this rolling again!
Call for Code Review Help: Repairing Gutenberg GitHub Actions Workflows for wp/x.y Branches
While the only actively supported version of WordPress is the most recent one, security updates are backported to older branches as a courtesy. All versions >=4.7 are in a security-only support state, receiving select security patches as a courtesy to users of WordPress.
The code maintained in the Gutenberg repository is just as critical to all WordPress versions >=5.0.
The code in the 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/ repository that corresponds to each release of WordPress is organized using wp/X.Y branches. These branches are frozen in time snapshots of the code that was used by wordpress-develop to build the final software that is released to the world. However, because the testing infrastructure in these branches has not been well maintained so automated checks and test suites are currently broken. Some fail consistently while others don’t run at all due to poorly scoped 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”. filters, event targeting, and other issues.
It’s imperative that these 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/ Actions workflows and the underlying testing infrastructure is restored to a working state to ensure that all relevant security patches that affect Gutenberg can be properly validated and confirmed before being shipped to end users in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
That’s where you come in!
Enter: Operation Tall Stack 🥞
Over the last few weeks I have worked with AI to create a pull request stack for each and every wp/x.y branch on the gutenberg repository that:
- Gets CI passing again, so changes to these branches are properly tested before they ship in a WordPress release.
- Modernizes and hardens the workflows by removing jobs that serve no purpose on a release branch, updating and pinning actions and runner images, and adding safeguards like job timeouts and workflow linting.
- Makes each branch’s test environment predictable by pinning it to the software versions that match its WordPress release, and testing the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher and Node.js versions that release actually supports.
- Repairs the local development tooling (
wp-env, Composer and PHPUnit), which broke as the outside services and packages it relies on changed over time. - Stabilizes the test suites by fixing or backporting fixes for flaky and broken tests.
Some details about the approach:
- One fix per PR. Each stack has between 18 and 32 pull requests, and each one addresses a single, specific problem. Reviews come in small, targeted pieces instead of one large diff.
- Stacked PRs. Each PR is based on the one below it, so the stack reads from the bottom up. The Files changed tab on each PR shows only that PR’s change, and CI on the top PR tests the whole stack together.
- Same fix, same shape on every branch. A fix that applies to several branches has the same branch name (
fix-actions-X.Y/<fix-name>) and a matching title on each of them. It also sits in roughly the same position in every stack. That makes it possible to review one fix across all branches at once, rather than reading through one branch’s entire stack. - Only the branches that need it. Each fix was checked against each branch’s actual code, and a fix only appears where the problem exists. Where a branch differs, the PR adapts the fix to that branch.
- Following 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. where possible. Many fixes are backports or adaptations of changes already made on trunk, and those PRs link to the original PR or commit.
- No new package releases: Changes that would publish new versions of the repository’s npm packages are forbidden. The only exception is
wp-env, a development-only tool that is not part of the WordPress code shipped to users, that a good portion of the testing infrastructure depends on to be operable. - Documented and traceable. Every PR description explains what changed, why, and how, and cites the failing CI runs or error output it addresses. Each PR also links to a tracking issue for its branch.
- Human review: Any pull request related to this effort in draft state should be considered AI-produced and unverified by a human. I have staged each branch’s stack in my fork for testing and verification before pushing to
WordPress/gutenberg. Each PR is then marked ready for review after a final confirmation.
Review Strategy
Before this work can be merged, this needs to be reviewed and approved. With roughly 500 total pull requests across 20+ branches, your help is needed.
After discussing with a few contributors, it’s become clear that the best way to review each branch’s stack of pull requests properly is to divide them up by fix, not by individual stacks. This allows someone to review all of the PRs related to a specific fix as it relates to the code within each wp/X.Y branch without having to context switch through each and every problem in a stack.
While there is an overarching ticketticket Created for both bug reports and feature development on the bug tracker. for this project (GB-82780) and a sub-issue for each wp/X.Y branch, there are no issues for the individual fixes. To help divide and track the review efforts without overlap, I’ve created an issue for claiming and tracking the review efforts (GB-84853).
You’ll find a table on that issue that assigns each fix an alphabetical identifier and links to the corresponding pull request for each version branch. The first comment lists the branch name, a 1-2 sentence description, and any PRs that applied the same changes to trunk for each fix (if any).
Please use the following procedure if you’re able and interested to help in reviewing these pull requests:
- Comment on GB-84853 to claim a given fix.
- If you’re able, edit the table in the issue’s description to add yourself as the reviewer for that fix.
- When you claim a given fix, you are pledging that you will explicitly submit a review with an approval or a request for change on every PR in that row. An approving review is required for every PR in a given stack, otherwise the stack cannot be merged.
- Claim one row at a time. You can always claim another after you complete the first.
- If you are reviewing the PRs in a row and are unable to finish within 24 hours, please comment on the issue and (if able) and note in the Reviewer column of the table the branches that you reviewed. Example: “Needed: 6.0-5.7. (@desrosj reviewed 7.1-6.1)”
Anyone is welcome to help review these PRs. However, the rulesets configured on the gutenberg repository require at least one approving review from a member of the WordPress GitHub organization granted write access to the repository.
Currently only the wp/7.1 through wp/5.7 branches are ready and pushed to the gutenberg repository, but the rest will be added in the coming days. When new stacks are pushed and ready, a comment will be left on the issue to notify everyone who has helped out.
Phase 2
Restoring these workflows to a functional state is phase 1 of the necessary efforts to make these more maintainable long term. Once the workflows are functional in each wp/X.Y branch, a second effort will begin to adopt the reusable workflow pattern matching the strategy in wordpress-develop (see TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. #61213), which makes maintenance of these workflow files significantly easier because the functional logic being performed lives in trunk and is shared amongst all branches that perform a given type of testing or automation.
Thank you to everyone in advance for your help contributing to this effort!
Props @johnbillion, @jorbin, @lancewillett for pre-publish review.
Thanks for putting together Operation Tall Stack and organizing this massive effort so cleanly, @desrosj!
Dividing the reviews by fix across branches on GB-84853 makes handling a stack of this scale much more manageable. Solidifying the test infrastructure across all wp/x.y branches is critical for reliable security backports.
I’ll be heading over to the tracking issue to claim a fix row and help get these reviews rolling.
Team Chat Agenda: 15th October, 2026
Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 15 October 2026, 03:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!
Agenda
- Attendance
- Attendance check in with the wp.org username
- Note-taker and facilitator selection for the next meeting
We encourage all members to contribute to the team chat, and we now welcome Note Takers and Facilitators. This is a great time to get involved in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. test team. Have you recently joined, and you don’t know where to go? Start here (No Skills Required)- This week’s facilitator and note-taker is – @huzaifaalmesbah
- Next week’s facilitator note-taker is – Looking for a volunteer ( PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” us #core-test to volunteer )
- Test Team Discussions
- Open Floor
- Got a topic? Add in comments below, or bring it up live during the chat.
- WordPress Ecosystem Announcements
- What’s new in Gutenberg 24.2? (14 October)
- Presence API: What’s new
- Real-time Collaboration: A Guide to Sync Engines
- Call for feedback: the W and the site name in the Toolbar
- Feature Notifications: status update and plan for 0.3.0
- The MCP Adapter Plugin is Now Available on WordPress.Org
- What’s new in AI 1.4.0 (5 OCTOBER 2026)?
- Roadmap to 7.2
- Introducing Ipsum, the new default theme
- WordPress Contributor Toolkit 1.2: One app for your first Core or Gutenberg contribution
- Test Team Announcements
- Call for Testing
- Call for testing: DataForm editor inspector
- We have Patch Testing issues for the WordPress 7.2 milestone that need testing.
- We also have a couple of Gutenberg Issues that need testing.
Leave a Comment
- Do you have something to propose for the agenda?
- Can’t make the meeting, but have a question for the Test Team?
If any of the above apply, please leave a comment below.
Polyglots GTE brainstorming session, recap
On October 3 a group of GTEs met on Zoom for the brainstorming session @tobifjellner called a month earlier. The topic: the flood of AI-generated translations and the PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. request workload it created. This is the recap of the pain points, the ideas on the table and the follow-ups. Nothing was decided; the goal was to collect options before moving to decision mode.
Attendees: Tor-Björn Fjellner @tobifjellner (sv_SE, host), Peter Smits @psmits1567 (nl_NL), Akira Tachibana @atachibana (ja), Gary Jones @garyj (en_GB), Jamie Dąbrowiecki @jdab (en_GB), Pedro Mendonça @pedromendonca (pt_PT), Luis Rull @luisrull (es_ES), Emre Erkan @emre (tr_TR).
One thing came up more than once: AI output quality has improved a lot over the past year, es_ES and pt_PT both said so. The problem is volume and the wrong 10%, not quality across the board.
PAIN POINTS
Volume. 300 to 5,000 submissions per day in es_ES. In one day nl_NL received five or six projects with about 500 unusable stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. each. (Luis, Peter)
PTE requests. Free-form blog posts that clog the P2p2 “p2” is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something “on the p2” by a member of the Polyglots team, that usually means you’re asked to post on the team blog https://make.wordpress.org/polyglots/.. One requester asking for many localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ at once. Developers requesting PTE only to get their own AI output approved fast. Teams cannot promise a 2-day turnaround. (Akira, Luis, Toby)
Bulk reject. Works one page at a time; 600+ strings from one user means several pages. (Toby)
Translation memory. GTEs cannot edit or delete entries. Wrong TM suggestions keep ranking above the corrected ones. TM is translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. (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.) code, not GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.. (Emre, Toby, Pedro)
GlotPress data model. Translations cannot be deleted, only marked obsolete. Rejected spam accumulates and the database is already slow. The consistency tool returns only the first 500 matches. (Pedro, Peter)
Discoverability. The per-localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ glossary and style guide list in the handbook is manual and incomplete, and someone applying for PTE will not go looking for it. Even the ja style guide is unknown to most ja contributors. (Gary, Toby, Akira)
Off-platform work. Translators work in Crowdin, Poedit or their own LLM and import the result. Imports get no glossary or style checks. (Emre, Luis)
Glossary matching. Plain stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. matching fails for compounding and agglutinative languages (sv, fi): valid translations get flagged. (Toby)
Locale rules. Formal vs informal Spanish is the single largest source of noise in es_ES. (Luis)
LLM tooling. Every provider handles prompts differently; prompts need constant tuning. (Peter)
IDEAS
PTE request process
Structured PTE requests. Replace blog-post requests with a form backed by a database. Checkboxes for: native speaker, read the style guide, applied the glossary. Trigger it inside GlotPress after someone submits strings, with a direct link to their pending strings. GTEs get a per-locale queue; the Polyglots leads can see which requests are stalled. (Akira, Peter, Toby)
Locale cap. Limit how many locales one person can request at once. (Akira)
Probation import. Limit a new contributor’s first import to about 100 strings and unlock the rest after review. (Peter) Pushback: for some locales 100 strings is too few to catch the once-in-40 errors, and level tracking adds administration. (Toby)
Flood control and cleanup
Bulk reject per user. One action to reject every unapproved string from user X in project Y, regardless of count or paging. (Toby) Caveat: rejected rows stay in the database, so this needs a retention policy, for example rejected and older than 2 years is deleted, spam is deleted after 30 days. (Peter, Pedro) History is worth keeping for real discussions, not for spam. (Pedro)
A role for developers shipping machine translations. Next to CLPTECross-locale Project Translation Editor A Cross-Locale Project Translation Editor is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localize their product. The cross-locale project translation editor can import/validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors.: their upload builds a language pack, never enters the translation memory, and cannot override a community translation. Gate it behind a 20-minute training. If they want to ruin their own 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.’s 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., that is their call. (@elbogen via Toby)
TM maintenance. Give GTEs a way to prune and edit the translation memory. Open question for the Meta team.
AI-assisted review
AI first pass in GlotPress. Modeled on how the Plugin Review Team automated checks with Plugin Check. GTEs write a per-locale skill; the pass flags approve/reject with reasons; a human confirms. (Pedro, Peter)
Machine-readable guidelines. Publish glossaries and style guides in an MCP-reachable form so agents can use them. Per-locale skills as plain text files linked from GlotPress. A central best-practice page for contributors who do not speak the target language. (Toby, Emre, Pedro)
Glossary check at import time. With the compounding-language caveat above. (Emre)
Prompt findings from tr_TR. 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. the glossary down to the terms that occur in the file and embed that in the prompt instead of calling tools. Fully embedded, the largest glossary (Malagasy) is about 53k tokens; filtered, it is small. Low reasoning effort translates better than high. Review time dropped from hours to minutes. (Emre)
A WordPress-specific translation model. Trained on translate.wordpress.org data, pre-populating new projects so reviewers only pick out the wrong ones. (Peter) Context: automatic propagation on 100% source matches was tried in the early days and dropped because short strings change meaning by context. (Toby)
Where to build it
Build as translate.wordpress.org plugins first and upstream to GlotPress later, since GlotPress changes can break other users. (Toby) Counterpoint: this belongs in GlotPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.; it is an old fight. (Pedro)
Community
Recurring Polyglots video calls at alternating hours so both East Asia and Latin America can join. Virtual coffee breaks ran 4 or 5 years ago and faded out. (Toby, Luis)
DEMO: The Polyglots Tool
At the closing of the meeting @emre did a demo of the review tool he has been building. The tr_TR waiting queue of themes went from about 22,000 strings to about 4,000 with it.
It runs as a CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. and a TUI. It can translate, review a submitted PO file, fetch one or more projects from translate.wordpress.org, split large projects (6,000 to 8,000 strings) and produce statistics. A review produces a repaired PO with a comment per changed string (glossary term, meaning or fluency, locale-specific rules such as Turkish title case) and a ready-to-paste reply for the PTE request thread. It uses your local translation memory, syncs the locale glossary from translate.wordpress.org and calls the consistency tool when a term is ambiguous. Providers are pluggable via 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. keys (DeepL, OpenAI, Antigravity and others); batch size 100 with a flash-class model on low reasoning effort gave the best results. Several projects can be reviewed in parallel, with 1.5 s delays between requests so it does not hammer translate.wordpress.org.
A configuration layer lets other locales define their own rules. Anyone who wants to try it on their locale can reach @emre 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/ or check it here.
ACTIONS AND NEXT STEPS
- Toby: compile the ideas; everyone keeps adding comments under the invitation post linked above. Revisit in about a month, then move to decision mode.
- Toby: talk to plugin developers to get their side; none were at this session.
- Toby: ask the Meta team (@ocean90, @timse201) about editing and pruning the translation memory.
- Akira: add a “read the style guide” checkbox to the ja PTE requirements.
- Emre: post the glossary token-size analysis: here it is.
- Emre: set up the Polyglots tool for interested locales; es_ES (Luis, Fernando) is first.
- Emre, Peter: a masterclass on using LLMs in Polyglots work: review automation, prompts, tooling. Date to be announced.
- All: try recurring Polyglots video calls at alternating hours.
@emre
Thanks a lot for this!
Related links:
– Call to brainstorming: https://make.wordpress.org/polyglots/2026/09/09/october-3-polyglots-brainstorming-session/
– “Discussion article”: https://make.wordpress.org/polyglots/2026/10/14/the-largest-problems-in-wordpress-ui-localization-in-2026/
GOOD READ!
Great recap @emre! The distinction between “blind AI dumping” and “native-speaker AI-assisted translation” is really important here, especially for smaller locales (like `yor`) where off-platform `.po` work with a well-tuned LLM prompt is one of the only realistic ways a small team can make a dent in thousands of strings.
Big +1 to publishing **plain-text, machine-readable per-locale skills** and to @emre’s point on smaller batches with low reasoning effort (high-reasoning models definitely over-interpret short UI strings).
One practical suggestion for discoverability: if we create these plain-text locale skills, let’s link them directly on the **GlotPress translation table and `.po` Import area** (“Using an LLM or Poedit? Download this locale’s prompt rules first”). Meeting off-platform contributors right where they export/import files would prevent a lot of the “wrong 10%” before it ever hits the waiting queue.
Thank you so much @tobifjellner for the initiative and @emre for the recap and tools!
One quick follow-up thought on the 100-string probation import limit: while that makes total sense for high-volume locales like `es_ES` or `nl_NL` dealing with spam floods, it could accidentally bottleneck smaller or under-resourced locales.
In locales where only 1 or 2 active contributors are working through thousands of core/plugin strings, and where GTE review turnaround might take weeks, capping imports at 100 strings would stall genuine progress. If a probation cap is built, making it an opt-in toggle per locale (or bypassing it when an import passes an automated locale-skill/placeholder check) would protect big teams without slowing down smaller ones.
What’s new in Gutenberg 24.2? (14 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.2?
Gutenberg 24.2 has been released and is available for download!
This release comes with a new place for notes: they now float in a margin next to the content, so collaborating no longer means closing the Settings 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.. Adding a categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., a 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.), or a post to a 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. now takes a single search, and the Gallery 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. can sort its images and tint all of them with one duotone.
The design tools consistency work started in 24.1 continues with about 80 more PRs, and the release also includes more than 60 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes plus some 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) and performance improvements. For developers, 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 is now enabled by default, and feedback on it is welcome and needed.
Notes move into a canvas margin beside the content
Until now, floating notes and the Settings sidebar couldn’t be open at the same time, and the notes column took space away from the content. In Gutenberg 24.2, notes live in a margin the editor reserves next to the canvas, so they stay visible while you change blocks or post settings (#83786).
When the canvas gets narrower, each thread shrinks to its author’s 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., and clicking the avatar expands the thread again. A new Notes submenu in the Options menu expands, minimizes, or hides the notes, and the editor remembers your choice (#83768).
Other changes make working with notes safer: deleting a note now shows an Undo action (#83988), a note or reply you haven’t sent is kept when you select another block (#84110), and the notes scroll together with the canvas (#83852).
One search for every link in a navigation menu
Adding anything other than a page to a navigation menu used to mean knowing the right block first, like Category Link or Tag Link, and then searching inside it. Now the link search of the Navigation block looks through every type of content at once and shows the type beside each result, so pages, posts, categories, and tags are one search away (#83408). Switching an existing link to another type, for example from a category to a page, also no longer means deleting it and adding it again.
The same search lists the blocks a navigation menu accepts, so typing “Home” finds the Home Link block (#83652). Results are now ranked by type too, with posts and pages before categories, tags, and media, and nothing is discarded when several types are searched together. That ranking applies to every link search in the editor, so on large sites, tags and attachments no longer push the post you’re looking for out of the results (#83407).
Sort any gallery and tint all of its images
The Order by control of the Gallery block now works for galleries of hand-picked images too. Choosing Newest to oldest, Oldest to newest, A Z, or Z A sorts the images once, and you can still drag them into any other order afterwards. Random moved into the same control and shuffles the images on the front end each time the page loads (#83438).
Galleries also gain duotone support. One 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. now tints every image in a gallery, either from the block settings or, for every gallery on the site, from Global Styles. A duotone set on a single image keeps priority over the one set on the gallery (#83978).
Design tools reach even more blocks

The design tools consistency work continues with about 80 more PRs. Some highlights:
- Minimum width and height controls, previously available on five blocks, now reach 40, including Buttons, Columns, Heading, Media & Text, and Post Title.
- Shadows reach ten more blocks, including Paragraph, List, Buttons, Social Icons, and Gallery.
- Duotone reaches Gallery, Media & Text, and Video, so a video can now match the tint of the images around it (#83979, #83981).
- Background images and gradients reach Button, List, List Item, and Media & Text.
- Line indent reaches Heading, Post Author Biography, and Poetry, which also gains text columns and fit text.
Every block and support is listed in the changelog.

React 19 is now on by default and some 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. enhancements
Gutenberg 24.2 turns the React 19 experiment on by default (#83784). Sites now load React 19 for the react and react-dom scripts, unless a theme or 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. known to have compatibility issues is active, so folks using one of those keep React 18. That list started from the issues observed on WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ and was extended for this release (#84607).
If you maintain a plugin or theme that uses React, please test it with Gutenberg 24.2 and report any issue you find. If something breaks on a site, turn React 19 off under Gutenberg > Experiments. To set the inert attribute in a way that works with both React 18 and React 19, use the new @wordpress/react-inert-value package (#83987).
The Interactivity API also gets two additions. The new data-wp-html directive renders HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. from the store, the same way data-wp-text renders text, and it only accepts values marked as trusted with asDangerousHTML() (#83092):
import { asDangerousHTML, store } from '@wordpress/interactivity';
store( 'myPlugin', {
state: {
get description() {
return asDangerousHTML(
'<p>A <strong>formatted</strong> description.</p>'
);
},
},
} );
<div data-wp-interactive="myPlugin">
<article data-wp-html="state.description">
<p>Loading description.</p>
</article>
</div>
The router now exposes state.navigating and state.initiator, so a block knows when a client-side navigation is in progress and which block started it (#83280).
Other notable highlights
- Restore original image: after cropping an image, the Image editor offers Restore original image in its More options menu, so going back to the uncropped image no longer needs a trip to the Media Library (#81805).
- Button links: the link popover of the Button block opens only when you click Link or press the keyboard shortcut, instead of every time you select a linked button (#30166).
- Columns: the column count slider is gone. Add a column with the plus button next to the Columns button in the block toolbar, and remove one like any other block (#83262).
- Options menu: the View group now has Appearance, Notes, and Panels submenus. Sidebars added by plugins moved into Panels, and their pinned toolbar buttons stay where they were (#82976).
- Post author: the author field is always searchable, and it searches users on the server, so the right person shows up on sites with many users (#83323).
- Navigation Link states: Global Styles can style the hover, focus, focus-visible, and active states of navigation links, starting with typography (#83451).
- Icon search: the icon library also matches keywords, so “hamburger” finds the Menu icon and “gear” finds Settings (#82367).
- Reduced motion: the Video and Cover blocks don’t autoplay in the editor when reduced motion is preferred, and Cover background embeds don’t autoplay on the front end either (#83337, #83452).
- Inserter performance: opening the inserter blocks the main thread for less time, and selecting another block while it’s open no longer re-renders every item in it (#83437, #83284).
- New post slugs: a new post could be published with the
auto-draftslug after clicking into the Slug field. That no longer happens (#83518).
Changelog
Features
Components
- UIUI User interface: Add Meter. (83855)
- UI: Add Progress with custom color support. (83781)
- UI: Add SearchableSelectControl. (80979)
Interactivity API
- Add a data-wp-html directive. (83092)
- Interactivity API Router: Add reactive navigation lifecycle and initiator API. (83280)
Enhancements
- Dashboard Widgets: Let a mounted 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. declare actions at runtime. (83877)
- React 19: Add new incompatible plugins. (84607)
Block Library
- Accordion Heading: Add line height support. (83958)
- Archives: Add minimum height support. (83573)
- Avatar: Add shadow support. (83929)
- Avatar: Explain that avatars use the GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. https://gravatar.com service. (83567)
- Button: Add background image, size, and gradient support. (83950)
- Button: Only open the link popover on explicit user action. (30166)
- Buttons: Add minimum width and height support. (83894)
- Buttons: Add shadow support. (83916)
- Code: Add minimum width and height support. (83574)
- Columns: Add minimum width and height support. (83895)
- Columns: Remove the column count slider. (83262)
- Comments Pagination: Add border support. (83746)
- Comments Pagination: Add padding, margin, and block gap support. (83744)
- Details: Add minimum width support. (83576)
- Embed: Add minimum width and height support. (83903)
- Embed: Add padding support. (83963)
- File: Add minimum width and height support. (83896)
- File: Add shadow support. (83918)
- Footnotes: Add minimum width and height support. (83579)
- Gallery Lightbox: Prevent image click from closing the dialog when navigation is enabled. (78898)
- Gallery: Add duotone support. (83978)
- Gallery: Add minimum width and height support. (83897)
- Gallery: Add Order By controls for static gallery, consolidate controls in settings sidebar. (83438)
- Gallery: Add shadow support. (83919)
- Heading: Add minimum width and height support. (83580)
- Heading: Add text indent support. (83615)
- Home Link: Add minimum width and height support. (83582)
- Home Link: Add padding and margin support. (83607)
- Icon: Add block bindings support to the
iconattribute. (80730) - Latest Comments: Add border support. (84148)
- Latest Comments: Add minimum width and height support. (83904)
- Latest Posts: Add minimum width and height support. (83905)
- List Item: Add background image, size, and gradient support. (83936)
- List Item: Add shadow support. (83925)
- List Item: Enable editableRoot for multi-selection on mobile. (82816)
- List: Add background image, size, and gradient support. (83935)
- List: Add shadow support. (83923)
- Login/out: Add minimum width and height support. (83583)
- Math: Add minimum width and height support. (83585)
- Media & Text: Add background image, size, and gradient support. (83927)
- Media & Text: Add duotone support. (83981)
- Media & Text: Add minimum width and height support. (83906)
- Media & Text: Add shadow support. (83976)
- Media & Text: Lower the specificity of the content padding. (83563)
- Navigation: List allowed blocks in the link UI search results. (83652)
- Navigation: Search every entity type from the link UI. (83408)
- No Results: Add minimum width and height support. (83584)
- Page List: Add minimum width and height support. (83908)
- Pagination: Add border support. (83745)
- Pagination: Add padding, margin, and block gap support. (83743)
- Paragraph: Add shadow support. (83926)
- Poetry: Add fit text support. (83980)
- Post Author Biography: Add text indent support. (83614)
- Post Comments Form: Add font family support. (83967)
- Post Comments Form: Add minimum width and height support. (83910)
- Post Content: Add minimum width support. (83575)
- Post ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.: Add minimum width and height support. (83578)
- Post Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts.: Add border style support. (83956)
- Post Terms: Add minimum width and height support. (83586)
- Post Time to Read: Add minimum width and height support. (83598)
- Post Title: Add minimum width and height support. (83600)
- Preformatted: Add minimum width and height support. (83587)
- Pullquote: Add minimum width support. (83588)
- Query Total: Add minimum width and height support. (83590)
- Quote: Add button colour support. (83983)
- Quote: Add minimum width support. (83592)
- Read More: Add border style support. (83735)
- Read More: Add minimum width and height support. (83912)
- RSS: Add minimum width and height support. (83913)
- Search: Add padding support. (83984)
- Site Tagline: Add minimum width and height support. (83589)
- Site Title: Add minimum width and height support. (83593)
- Social Icons: Add shadow support. (83920)
- Tab List: Add shadow support. (83922)
- Tab Panels: Add minimum height support. (83594)
- Tabs: Add minimum width support. (83595)
- Term Count: Add margin support. (83608)
- Term Count: Add minimum width and height support. (83596)
- Term Description: Add minimum width and height support. (83597)
- Term Name: Add margin support. (83606)
- Term Name: Add minimum width and height support. (83599)
- Term Template: Add minimum width and height support. (83914)
- Verse: Add minimum width support. (83609)
- Verse: Add text columns and indent support. (83962)
- Video: Add duotone support. (83979)
Components
- Card: Migrate from Emotion to SCSS modules. (82577)
- CheckboxControl: Keep the legacy control visually consistent across viewports. (83612)
- ColorPalette: Show design system focus ring on custom color button. (83841)
- ContentEditableControl: Keep a disabled field focusable. (84083)
- CustomGradientPicker: Extend control point targets to the bar height. (84124)
- CustomGradientPicker: Migrate control wrappers to an SCSS module. (82576)
- Deprecate Badge. (82379)
- FontSizePicker: Migrate Emotion styles to SCSS Modules. (84126)
- FormToggle: Match Switch colors across states. (83773)
- Icons: Experiment with proportional stroke scaling. (84081)
- InputControl: Darken the field border on hover. (83306)
- ItemGroup: Use design system focus ring. (83764)
- Menu: Align group labels and separators with indented item labels. (83993)
- Menu: Align submenu labels and highlight open parents. (84031)
- Menu: Guard against nesting Group and RadioGroup. (83792)
- Menu: Tighten spacing, use 16px prefix icons, and cap width at 320px. (84028)
- Progress: Migrate remaining ProgressBar usages and recommend UI Progress. (84021)
- ProgressBar: Use WPDS color tokens. (83779)
- RadioControl: Align colors with UI Radio. (83270)
- Text: Migrate Emotion styles to an SCSS Module. (82573)
- Theme: Generate complete border token modes for Figma testing. (84035)
- UI: Add item labels and descriptions to remaining popups. (83493)
- UI: Add separators to item popup components. (83776)
- UI: Align component names with their semantics. (83789)
- UI: Keep InputLayout chrome at md on small viewports. (82764)
- UI: Recommend the Checkbox, Radio, and Switch component families and the Notice component. (82685, 83771, 83872, 84097)
- UI: Remove automatic Notice announcements. (82737)
- UI: Update Spinner appearance and add a color prop. (83775)
- VisuallyHidden: Move hiding styles outside CSSCSS Cascading Style Sheets. cascade layers. (84114)
Block Editor
- Block Supports: Add background-clip block support infrastructure. (77141)
- Block Supports: Ensure position type is a string. (83500)
- Block Switcher: Show design system focus ring on pattern previews. (83933)
- Fit text: Size each block instance in a 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 independently. (83985)
- Fix translator comments for block count announcements. (83555)
- Honour background skip serialization in the editor. (83943)
- Inserter: Use design system focus ring for previews. (83126)
- Migrate state-control badges to UI Badge. (82608)
- States: Scope per-instance rules to the block’s root element. (83986)
Icons
- Add keywords to icon manifest. (83884)
- Make the “B” icon bolder. (83321)
- Polish the typography and “block-default” icons. (84073)
- Support keyword-based search in the icons registry. (82367)
- Update and add justify icons. (83519)
- Update heading level icons for optical balance. (83268)
Post Editor
- Base Styles: Default the adminadmin (and super admin) theme color to Blueberry. (83749)
- Document Outline: Show the design system focus ring instead of legacy box-shadow. (83755)
- Editor: Gather the View group of the Options menu into submenus. (82976)
- Editor: Remove icon for ‘Export’ more menu item. (83901)
- Editor: Use SearchableSelect for the post author field. (83323)
- Editor: Use UI Menu for template options. (82964)
Media
- Media Editor: Add a session boundary above the cropper. (83550)
- Media Editor: Restore original image in modal. (81805)
- Media Editor: Show an error when saving attachment details fails. (83560)
- Media Editor: Use UI Menu for crop aspect ratio. (82968)
- Track the original attachment ID for edited images. (81803)
Site Editor
- Canvas loader: Use Progress from wordpress/ui. (83860)
- Font Library: Use UI Menu for collection actions. (82965)
- Global Styles: Add pseudo-state controls for Navigation Link. (83451)
- Global Styles: Update the Styles > Blocks description. (83515)
- Style book: Add link to example text. (83448)
DataViews
- Fields API: Add the server-side registry and REST route. (84078)
- List hideable fields alphabetically in the view configuration. (83947)
- MediaEdit: Use design system focus ring. (83854)
- Truncate filter chips instead of wrapping them. (83879)
Collaboration
- Notes: Add show and hide options for floating notes. (83768)
- Notes: Add Undo to deleted note snackbar. (83988)
- Notes: Move floating notes into a canvas margin. (83786)
Bug Fixes
- Connectors: Keep a stored API key read-only when it can’t be verified. (83889)
- Date: Drop a trailing backslash instead of formatting it as “undefined”. (81528)
- Experiments: Don’t invalidate saved option with a legacy key. (84619)
- useServerSideRender: Parse messages from caught errors. (83365)
Components
- BorderControl: Remove
%from the border width units. (83492) - Checkbox: Prevent rounded themes from making checkboxes circular. (83526)
- CollapsibleCard: Scope 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. focus ring to its own trigger. (81314)
- Fix polymorphism typings leaking
asprop. (82704) - FocalPointPicker: End a drag released over the editor canvas. (83348)
- Menu: Disable triggers instead of roots in consumers. (83791)
- PaletteEdit: Stop changing the slug when renaming a preset. (83750)
- Popover: Close non-modal popovers on 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. interaction. (83509)
- Popover: Drop the will-change hint once the popover stops moving. (77359)
- RadioControl: Keep a 16px visual with a larger hit target. (83840)
- SandBox: Fix embed previews that require a referrer in Safari. (84014)
- TextControl: Use design system colors when disabled. (83307)
- Theme: Fix virtual modules, root styles, and seed validation. (83355)
- Theme: Improve accessibility, API documentation, and compatibility checks. (83358)
- Theme: Make 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 token fallback transforms syntax-aware. (83356)
- Theme: Preserve global token references in Lightning CSS. (83359)
- UI: Align selection popup checkmarks with the first label line. (82942)
- UI: Preserve Autocomplete item type inference. (84095)
- UI: Preserve Combobox source item generics. (84094)
Block Editor
- Columns: Allow dropping a column at the outer edges. (83274)
- Fix ‘Manage allowed blocks’ not shown when it’s the only ‘Advanced’ control. (84067)
- Fix style / nested attribute overwrite during multi-selection. (80070)
- Paste: Give each pasted data-URI image unique filename to avoid upload collisions. (79480)
- Paste: Replace non-breaking spaces at the edges of text with regular spaces. (83464)
- Rich text: Fix iOSiOS The operating system used on iPhones and iPads. double tap selection, preventing focus capture under editable host. (81042)
- Show whitespace changes in the Resolve Block diff. (82397)
- Style states: Fix exception when there’s no selected block. (84140)
- Typography: List only the weights inside a variable font’s range. (83128)
Block Library
- Group, Cover: Track drop zone element in state. (83756)
- Image: Fix invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. CSS url() value in circle-mask style. (82333)
- Image: Fix lightbox using thumbnail aspect ratio instead of original image ratio. (79058)
- Image: Fix the lightbox overlay becoming unusable (can’t close) when it isn’t a direct child of
<body>. (83480) - Image: Improve specificity of the lightbox button selector. (70800)
- Math: Store cell alignment in the MathML and polyfill alignment and overlines in Chromium. (83164)
- Post Featured Image: Fix crash when isLink is enabled. (81584)
- Tag Cloud: Update styles and add
!important. (70224) - Template Part: Fall back to rendering a template part from the theme file if the db version is unavailable. (83809)
Collaboration
- Notes: Delete permanently when the trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. is disabled. (84102)
- Notes: Draw the canvas divider from body so it uses the theme text color. (84158)
- Notes: Keep anchor writes out of undo history. (84079)
- Notes: Preserve unsent note and reply drafts. (84110)
- Notes: Reset paragraph top margin in floating notes. (84101)
- Notes: Restore child notes trashed along with their parent note. (84100)
- Notes: Restrict menu actions for resolution notes and resolved threads. (73243)
- Notes: Scroll floating notes with the canvas. (83852)
Media
- Media Editor: Fix pan drag flooding undo history after wheel zoom. (83558)
- Media Editor: Stop the crop pixel snap from recording undo history. (83571)
- MediaEdit: Show a checkerboard background behind image previews. (83846)
- MediaUpload: Fix console error when reopening Gallery media library. (76749)
- MediaUpload: Fix the
galleryprop ignoringallowedTypes. (78257)
Data Layer
- CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Data: Rank link suggestions by type, and stop discarding merged results. (83407)
- RTC: Fix undo breaking for non-synced entities. (83888)
DataViews
- Fields: Fix AuthorView for users who can’t edit users. (83498)
- Measure the container as the data view mounts to avoid a single column flash. (83752)
Post Editor
- Editor: Fix new posts being published with the
auto-draftslug. (83518) - 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/: Add action-trash link to posts and comments. (84045)
Site Editor
- ExtensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. Site Editor: Pass custom block categories to the blocks store. (83762)
- Global Styles: Fix popover position in Styles screen. (84048)
Accessibility
- Editor: Merge adjacent revision inline diffs. (80579)
- UI: Announce selected chips in SearchableChipSelect. (82863)
Block Library
- Cover: Don’t autoplay embedded background videos when reduced motion is preferred. (83452)
- Video, Cover: Don’t autoplay in the editor when reduced motion is preferred. (83337)
Performance
Block Editor
- Check the inserter’s fallback containers unmemoized. (83446)
- Inserter: Manage roving tab index to skip re-rendering every item. (83437)
- Inserter: Stop re-rendering the block list on block selection change. (83284)
Experiments
- Admin design tokens: Consolidate wp-admin container radiuses onto the design system scale. (82427)
- Admin design tokens: Restyle classic wp-admin controls from design system tokens. (82425)
- Experiments: Turn the React 19 experiment on by default, except when an incompatible theme or plugin is detected. (83784)
- RTC: Add an EntitySyncManager interface in core-data. (83410)
Documentation
- Block Parser: Correctly document the
blockNameproperty as nullable. (70900) - Block Parser: Document
\WP_Block_Parser::$stackas a list. (82695) - Combobox: Label popup dialogs in stories. (83476)
- DataViews: Fix README to describe sort() as receiving field values, not items. (83483)
- Design System: Clarify tooltip labeling and UI review guidance. (83898)
- Docs: Clarify wordpress/ui icon color requirements. (83564)
- Docs: Describe isolated dependencies for agents. (84141)
- Docs: Fix published Vitest migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.-guide links. (83449)
- Docs: Note that block attributes and global styles values are untrusted at render time. (83473)
- Docs: Recommend UI Tabs for switching views. (83516)
- Docs: Refine design system agent guidance. (84007)
- Docs: Remove CheckboxControl heading from InspectorControls example. (83844)
- Docs: Update deprecation testing guidance for shared reset. (83989)
- Env: Change the core 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”. from 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. to master in the documentation. (83566)
- Fix broken links in documentation. (83545)
- Navigation Link: Update readme title to match block name. (83999)
- Storybook: Add new contributing page. (83345)
- Storybook: Place Notice announcements under Components. (83617)
- Storybook: Show prop descriptions in Canvas controls. (83581)
- UI: Add change actions to form primitive stories. (83591)
Code Quality
- Packages: Declare missing peer dependencies and check them in CI. (83765)
- wp-build: Remove unused optional peer dependencies. (83601)
React 19
- Add inertValue helper and use it for setting inert attribute. (83871)
- Add new react-inert-value package with inertValue helper. (83987)
- Breadcrumb: Fix getMeasurementRender for React 19. (84069)
- DataViews: Use inertValue in CompositeGrid. (84072)
- react-inert-value: Add missing
@types/reactpeer dependency. (84024) - Remove use-memo-one usage (missing React 19 compat). (83952)
- Upgrade code and types to React 19. (83941)
Block Editor
- Bump
@react-spring/webfrom 9.4.5 to 10.1.2. (83796) - Format Library: Unify FormatEditProps to one type, move private types. (83487)
- Position controls: Fix useSelect warning for selected state viewports. (83570)
- RichText: Refactor useMarkPersistent, fix StrictMode mount mark. (83463)
- RichText: Remove dead exports and consolidate deprecations. (83461)
- RichText: Rename utils.jsx to utils.js. (83758)
Collaboration
- Notes: Extract note selection sync into useNoteSelection hook. (83528)
- Notes: Extract NoteReply and lift AddNote gating. (84106)
- Notes: Refactor floating board measurement. (83485)
- Sync: Remove exposed wp.sync package. (81999)
Media
- Media Editor: Remove initial state seeding from the session. (83893)
- Media Utils: Add
MediaEditas a private API. (84046) - Return 0 from the edit root lookup when there is no edit root. (84096)
Block Library
- Breadcrumbs: Fix typo in aria label translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. context. (84112)
- Playlist: Replace the waveform player patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. with its no-autoinit entry. (83132)
Components
CSS & Styling
- Style: Update color to use CSS variable in edit-site. (79002)
- Table: Replace deprecated
word-breakwithoverflow-wrap: anywhere. (82480)
Interactivity API
Themes
- Global Styles: Ignore 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. values of unexpected types. (84523)
Tools
- PR 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.: Move the props list into the shared comment. (82302)
- Props Bot: Skip bare reviews that duplicate their review comment runs. (84076)
Testing
- Block editor: Isolate mutable test fixtures. (83098)
- Block editor: Wait for final keyboard link suggestions. (83489)
- Block library: Isolate order-sensitive test interactions. (83101)
- Blocks: Isolate registration state in tests. (83099)
- Components: Isolate order-sensitive UI tests. (83103)
- Core data: Finish deferred selection updates in RTC test. (83366)
- Data: Assert and silence resolution error in useSuspenseSelect test. (83491)
- E2E: Mock Openverse in image drag-and-drop inserter test. (83842)
- E2E: Pin the site title in the router specs; raise the end-to-end Storybook build heap. (83474)
- ESLint: Allow non-module stylesheet imports in unit tests. (84019)
- Icons: Use assertEqualHTML() in icons registry tests. (83544)
- Include end-to-end Storybook sources in docgen. (83634)
- Notes: Fix flaky thread scroll end-to-end test. (84118)
- React 19 codemod: Apply defaultProps when rendering a memo component. (84568)
- Tests: Add browser coverage for Menu scroll lock and LinkControl protocols. (83991)
- Tests: Add floating notes end-to-end coverage. (83477)
- Tests: Add Vitest Browser Mode failure artifacts. (83093)
- Tests: Cover translation setup in override script tests. (83886)
- Tests: Enforce per-call Vitest console expectations. (83095)
- Tests: Enforce Vitest assertion coverage. (83572)
- Tests: Enforce Vitest callback, promise, and title rules. (83620)
- Tests: Fix order-dependent wp-env schema test. (84139)
- Tests: Fix PostCSS browser-externalized warnings in Vitest. (83091)
- Tests: Isolate deprecation warning state. (83107)
- Tests: Isolate mutable configuration fixtures. (83104)
- Tests: Lint JavaScript Vitest mock imports. (83783)
- Tests: Migrate internal linting to Vitest and remove unused Jest dependencies. (83502)
- Tests: Reset deprecation history in shared Vitest setup. (83849)
- Tests: Resolve Browser Mode commands against the live iframe. (83495)
- Tests: Run Vitest type graph validation in process. (83851)
- Tests: Shuffle test cases in CI. (83111)
- Tests: Use strict assertions in layout, template registry, and theme.json tests. (83619)
- Tests: Use strict assertions in override script tests. (83782)
- Tests: Verify localized data retention in override script test. (83845)
- Theme: Add integration test coverage for seed colors in artifacts. (81161)
- Tooltip: Stabilize the hover delay cancellation test. (84113)
- UI: Add end-to-end Storybook popup item layout fixtures. (83488)
- Unit tests: Detect the database client in the debug step. (84089)
- Use a mock plugin slug within tests that no WordPress build ships. (84133)
Dependencies
- Add prettier, eslint and stylelint to the root package.json. (84017)
- Build: Remove patch-package. (83982)
- Build: Update Vite to 8.3.1 and simplify Storybook tooling. (83569)
- Build: Update Vite to 8.3.2 and remove the PostCSS browser resolver. (83992)
- CI: Cover the AI development lockfile with Dependabot instead of npm audit. (83997)
- Fix peer dependency conflicts left in the lockfile. (83754)
- Framework: Declare React types in the workspaces that use them. (84013)
- Framework: Move @typescript/native from the root to the workspaces that use it. (84027)
- Framework: Switch from hoisted to isolated dependencies. (83847)
- npm: Switch from legacy-peer-deps to strict-peer-deps. (81029)
- Repair invalid peer dependencies in the lockfile. (84062)
- Tests: Bump ibm-cloud-sdk-core in the AI development test lockfile. (83887)
- Tests: Bump undici in the AI development test lockfile. (83799)
- Tests: Patch basic-ftp in AI development dependencies. (84000)
- Tests: Update AI development package versions after npm audit. (83830)
- Tests: Update Vitest to 5.0.3 and Storybook to 10.6.1. (83996)
- Upgrade typescript-eslint to v8.70.1. (83760)
Build Tooling
- Build Tools: Fix flaky ESM package types test timeout. (84068)
- Changelog validator: Ignore Markdown, Storybook, and configuration files. (83618)
- CI: Check CHANGELOG presence for published tooling and configuration packages. (83577)
- Coding standards: Skip anonymous class methods in block library function name sniffsniff A module for PHP Code Sniffer that analyzes code for a specific problem. Multiple stiffs are combined to create a PHPCS standard. The term is named because it detects code smells, similar to how a dog would “sniff” out food.. (83900)
- Developer tools: Simplify editor setup and add Zed settings. (84143)
- Fix check type declarations errors when running
npm run dev. (84070) - Ignore composer vendor files from top-level gitignore. (22283)
- Link upstream fixes for Storybook and Vitest warnings. (83632)
- Read npm v12 pack –json output. (84011)
- Release Tooling: Read the npm v12 JSON output shapes. (84075)
- Release: Rewrite SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. publication scripts in Node.js. (84034)
- Use Node.js v24.20 in
.nvmrc. (84061, 84138) - VS Code: Add managed workspace configuration. (84025)
- Widget Primitives: Avoid Vite warnings for runtime widget modules. (83602)
Storybook
- Avoid duplicate block-editor store registration in Storybook. (83636)
- Fix missing block styles in BlockCanvas playground stories. (81070)
- Give CI job a distinct name. (83869)
- Read icon keywords from the manifest. (84127)
- Register playground core blocks once in Storybook. (83637)
- Reuse PostCSS browser resolver in Storybook smoke tests. (83635)
- Update BlockPopover Storybook fixture to API version 3. (83642)
- Update manifest snapshot for Spinner color prop. (83856)
WP Scripts
- Scripts: Refactor Stylelint configuration detection in lint-style.js. (79280)
- Scripts: Resolve default configs without hoisted dependencies. (83902)
- Scripts: Treat files passed after –fix as file arguments. (83521)
Env
- Add an option to choose the MariaDB version. (83751)
- Pass
-Ttodocker composecommands when stdin is not a TTY. (78374)
ESLint plugin
- ESLint: Add allowUseWithCaution option to use-recommended-components. (83536)
- ESLint: Allow generated test titles. (83995)
Security
- Env, E2E: Update dependencies that ran native install scripts. (84012)
- Opt in to the npm v12 supply-chain defaults. (82689)
First-time contributors
The following PRs were merged by first-time contributors:
- @adamwoodnz: Base Styles: Default the admin theme color to Blueberry. (83749)
- @haritpanchal: Tests: Use strict assertions in layout, template registry, and theme.json tests. (83619)
- @Intenzi: Block Editor: Fix style / nested attribute overwrite during multi-selection. (80070)
- @jshawl: Env: Pass
-Ttodocker composecommands when stdin is not a TTY. (78374) - @karthick-320: Icons: Add keywords to icon manifest. (83884)
- @Kgupta62: Popover: Drop the will-change hint once the popover stops moving. (77359)
- @tbradsha: Bump
@react-spring/webfrom 9.4.5 to 10.1.2. (83796)
Contributors
The following contributors merged PRs in this release:
@aaronrobertshaw @adamsilverstein @adamwood @aduth @alecgeatches @Aljullu @amitraj2203 @andrewserong @ciampo @desrosj @ellatrix @haritpanchal @hbhalodia @Hug0-Drelon @i-am-chitti @im3dabasia @Infinite-Null @Intenzi @jameskoster @jasmussen @jeryj @Jiwoon-Kim @johnbillion @jorgefilipecosta @jshawl @jsnajdr @karthick-320 @karthick-murugan @Kgupta62 @lancewillett @luisherranz @Mamaduka @manzoorwanijk @mcsf @mecskyverse @mikachan @mirka @mukeshpanchal27 @Mustafabharmal @n8finch @noruzzamans @ntsekouras @oandregal @peterwilsoncc @R1shabh-Gupta @ramonjd @retrofox @SainathPoojary @shail-mehta @simison @stokesman @t-hamano @talldan @tbradsha @tellthemachines @theaminulai @USERSATOSHI @whyisjake @yashjawale
**Translation Review Request for “WP…
Translation Review Request for “WP Credits Presentation” #ja
Hello Japanese Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/!
I’m looking for a Japanese translator or editor who could help review the Japanese translation of the WP Credits Presentation.
I’ve prepared the presentation in Japanese and would really appreciate it if a Japanese-speaking community member could review it and suggest any necessary corrections to ensure the translation is accurate and natural for Japanese readers.
Presentation: https://docs.google.com/document/d/1AI82O_4o1BnogodgW81pgldBLuy5IfbSDYnsy-Q4TYw/edit?tab=t.0
Thank you very much for your support!
I requested access to that document.
Thanks Junko! I’ve added you as editor, please comment on the Github once you finish the proofreading.
https://github.com/WordPress/WPCredits/issues/42
@devmuhib @nukaga
I’ve removed the to-do status of this post. You may still continue talking here or on Slack.
Thanks Tobi!
The largest problems in WordPress UI localization in 2026
This is a “cross-post” of discussion piece in TobiFjellner’s personal blog.
Fighting for good translations of WordPress UIUI UI is an acronym for User Interface – the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. (coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., plugins, themes, etc.) is more painful in 2026 than ever before.
The reason is AI.
But I need to be much more specific.
Machine translation is a type of AI-tooling that has been around for at least some 20 years to speed up human translation. These tools have improved immensely over the years, and today, with a good TM (Translation Memory), and a well-tuned MT (Machine Translator) you can often get almost perfect results.
The new trend now, though, is that a lot of developers instead of specialized MT tools, have started using commercial LLMs (like ChatGPT, Claude, and other) to bulk translate their plugins/themes into a lot of languages they personally don’t speak.
The main problem is that after spending a few minutes (and a large number of tokens), they expect the unpaid volunteer contributors of the Polyglots’ team to validate/fix/improve their translations, a task that takes substantially more effort, more than the Polyglots’ volunteers can handle. For most localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ teams the backlog of pending stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. grow with thousands of new strings every week. (Ref: https://translate.wordpress.org/stats/ )
Only a few locale teams manage to regularly clear their backlog. In most cases, the only way to achieve this is by spot-checking and then approve or reject the whole submission in bulk.
By the way “approving or rejecting in bulk” is one of the things we need to make much easier. Our current “bulk” commands only deal with one screenful of strings at a time.
Another problem is that the developers, obviously, want to make their shiny new machine translations available to the users and apply for the PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. role (Project Translator Editor – a bit like “translation committer”). The number of PTE requests has exploded. Today we get at least 10 times more PTE requests over a week than we used previously. In addition, they request PTE not for the one-two languages they speak, but for 10-20 localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/.
Since the PTE role is supposed to be a quality assurance step, most locale teams want to make sure that the requester knows the target language well; and we get stuck.
So what are we doing?
The Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/ has started discussions around what can be done to improve the situation. Here are a few directions.
Help LLM users make better translations
Many locale teams have published style guides. We can adapt these for LLM ingestion:
- Write the style guide itself in English
- Use markdown syntax
- Optimize the instructions for use with LLM
- Make it easier to find these style guides
Creating a new machine translator role
This type machine translations isn’t going to disappear. Instead, we need to make room for it in our systems. We may create a new role, where a contributor is able to distribute translations, but they can’t approve/reject/edit already approved translations from other users.
Also, unverified machine translations should not be added to the translation memory, which allows easy reuse of previous translations from anywhere in the project.
To some extent, we already have similar functionality for a different role, CL-PTE (cross-locale project translation editorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the “Project Translation Editor” role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor – a role used when a developer submits translations that have been checked by professional translators).
The role of WordPress Polyglots’ also changes
We’ve been building and coaching volunteer translators to make better translations.
Now we need to coach developers about using machine translations in a smart way and guide them more about internationalization (preparing their code in ways that allow for better translations).
Next steps
We’ve just started talking about these things. Last weekend we had a video meeting with Polyglots contributors from all between Japan and all over Europe.
That discussion continues.
I also intend to talk to 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./theme developers, to get their view on these things.
am missing the proposal to alter the PTE request handling. Now it is one individual that keeps track of them. We should make it much easier to request PTE.
Proposal:
1. Create on online database for requests
2. Create an entry form, with the fields necessary to handle the request. Eg. user name, project name, locale, check boxes for acknowlegment
3. Create a new role ‘PTE request handler’
4. Attach a cron task to this table, which sends emails to defined GTE persons per locale.
5. Attach a cron task to notify a person, that requests are overdue
Adding a link to the style guide next to the glossary link.
If we have a database table for PTE requests, add the limiter into the request. This limiter should be released as the GTE grands PTE rol. Until then the author cannot import more then a default amount of records.
“Creating a new machine translator role”
This seems like a great idea to me. We can’t fight windmills (quote) when it comes to machine translation, but we can steer and guide the process so that it yields acceptable results—or better yet, excellent ones. Let’s create the path—the route—that artificial intelligence can follow, with the right guidelines and local requirements. But we must always keep in mind the need to provide accurate information in the right place to everyone who decides to use a translation tool.
To put it another way, the only effective place to put a STOP sign on the road is where it needs to be obeyed. It’s pointless to put it on page 51 of the vehicle’s owner’s manual.
Thank you for writing this up. The style guide direction feels like the most practical first step, since it helps volunteers and anyone using MT tools alike.
A few thoughts on what makes a style guide useful for both people and LLMs:
– Order of authority: glossary first, then the handbook, then the style guide.
– Words that stay in English: brand names, product names, code and the technical terms the locale keeps as is.
– Tone and address: formal or informal, and how the user is addressed.
– Script and punctuation: language specific rules, for Hindi the danda (।), nukta and anusvara.
– What must never change: placeholders, HTML tags, URLs and code.
– Code vs readme strings: UI strings and plugin descriptions often need slightly different rules.
– A short checklist per string: with good and bad examples.
Some locales, Hindi among them, have only a glossary listed today, so a shared template with sections like these could make it easier for those teams to start. Linking the style guide right next to the glossary in the translation editor would also help, both for translators and for anyone giving context to an MT tool.
Agenda: Weekly Polyglots Chat – October 14, 2026 (7:00 UTC)
This meeting will be held by text chat at Wednesday, October 14, 2026, 07:00 GMT in the #polyglots channel in the Making WordPress 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/.
- Welcome
- Weekly LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ Stats
- Release
- WordPress 7.1.3 Maintenance and Security Release — 7 security fixes and 4 bug fixes
- WordPress 7.2 schedule — 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 starts October 20, final release December 8
- Help & Feedback Wanted
- Name order in WordPress: input needed from family-name-first locales — still gathering input
- Call for Polyglots Meeting Facilitators – Join Us in Leading the Conversation! – The next Europe slot is October 21, 13:00 UTC.
- Open floor / Achievement
If you have any additions to the agenda, please share them in the comments.
#meeting-agenda, #polyglots, #polyglots-meeting, #weekly-meetings
Hosting Team Meeting Agenda 2026-10-14
Next Meeting
The next meetings will be in the #hosting 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/ channel on Wednesday, October 14, 2026 at 0900 UTC and Wednesday, October 14, 2026 at 1800 UTC. Hope to see you there!
Agenda
- WP 7.2 BetaBeta Beta is the software development phase following alpha. A Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, speed or performance issues, and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. 1 scheduled for release next week on Oct 20th
- Progress Report: wp_kses() has been replaced with new implementation
- NO_BACKSLASH_ESCAPES SQL mode now off by default in WP 7.2
- Real-time Collaboration: A Guide to Sync Engines
- Tickets/PRs
Anything else? Please leave a comment with any additions or suggestions for the meeting.
Props to @kirasong for the pre-publish review!
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.
-
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.
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.

Muhibul Haque
Happy to be part of this excellent initiative! It’s inspiring to see WordPress Campus Connect creating opportunities for students to learn, connect, and explore the WordPress ecosystem.
Reply
ATIKUR RAHMAN
Thanks a lot, Sir Muhibul Haque
Reply