Skip toolbar
WordPress.org

Make WordPress

Francisco Torres Team Updates ·

Plugins Team: 9 Nov 2026

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

  • Plugins requested : 1236
  • Plugins rejected : 57
  • Plugins closed : 75
  • Plugins approved : 960

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 6026
    • (older than 7 days ago)** : 4688
    • (2026-11-02 – 2026-11-08) : 955
    • (new; not processed or replied to yet)* : 719
    • (pending; replied to)* : 5307
    • (pending; waiting on author)* : 4517
    • (pending; waiting on reviewer)* : 535
    • (pending; waiting on reviewer, email not yet sent)* : 255

Help Scout Queue Stats

  • Total Conversations: 2593
  • New Conversations: 1601
  • Customers: 2283
  • Conversations per Day: 324
  • Busiest Day: Monday
  • Messages Received: 1717
  • Replies Sent: 4513
  • Emails Created: 1274

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

#plugins

Rade Jekić Training ·

Meeting Agenda for November 10th, 2026

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

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

1. Intro/Welcome

  • Welcome to all the new teammates who joined the Training Team this week!
  • Icebreaker – Do you have experience in creating content (video/audio/articles)?

2. Contributor Updates

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

3. Open Discussions

  • If you have topics you’d like discussed in the meeting, please leave them as a comment on this post.
    • Have you tried new AI course created on the Learn platform?

4. News

  1. Meeting Note Takers
  2. Looking for feedback
  3. Looking for volunteers
    • Translation Review Volunteers: We have a lot of lessons translated into many beautiful languages, but we need someone to review them and give us their opinion about the translation quality and possible improvements. Join us on 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/ by following this link: https://github.com/WordPress/Learn/issues?q=is%3Aissue+state%3Aopen+project%3AWordPress%2F104. Find the language you speak and know, and help us in the review phase. We do not want to leave all those translated lessons and courses in GitHub oblivion…
    • Content Review Volunteers: Volunteers are needed to review and identify content that should be updated or consolidated. Two groups are needed: one for the handbook and one for courses.
    • Lesson Thumbnails: Work has started on creating thumbnails for lessons that need them. Team members are welcome to contribute to the remaining thumbnails through GitHub Issue #3428.
    • Issue Cleanup: The team discussed organising the many open issues into smaller categories and reviewing them systematically.
      • Review Workflow: The proposed process is to review issues one by one, identify outdated or irrelevant items, suggest next steps, and add comments before closing or updating issues.
        • Good First Issues: Contributors can start with issues labeled Good First Issue, especially those related to content feedback, and follow the handbook guide for validating feedback.
        • Issue Categories: The team discussed starting with a specific categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., with Bug issues suggested as a priority. Other options include Needs Translation Reviewer, Unlabeled, Awaiting Triage, and Content Feedback.
        • Next Steps: Team members are encouraged to suggest which category should be reviewed first, after which the issues can be divided among contributors.
      • Goal: Work together to clean up and keep the repository organised.
  4. Updates from last week’s Triage Squad session
    • No triage squad meetings last week
  5. Other announcements and news

5. Come and Contribute

6. Contribution Acknowledgement

  • Badges awarded:
    • No badges awarded this week

7. Project updates

8. Upcoming Online Workshops

  • No workshop scheduled
tobifjellner (Tor-Bjorn “Tobi” Fjellner) Polyglots ·

List of Style Guides reworked November 2026

The list with links to glossaries and style guides per locale has been updated.

Previously, it used an 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. table, which made it unnecessary hard to maintain the document.

The newer format makes the list easier to update, especially if we want to add any specific extra information, for instance a link to “Style guide for agents”. A bonus point is that it’s now possible to link directly to the anchor for your 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/’s section, like this: https://make.wordpress.org/polyglots/handbook/translating/glossaries-and-style-guides-per-locale/#sv_se

Things to do:

  • Check if your locale is included and if its links are the right ones.
  • If you’ve got documents that may be hard to reach or use (Google documents, WordPress CodexWordPress Codex Living online manual to WordPress.org https://codex.wordpress.org/, for instance) — consider moving them to a better place, like your locale’s /team subsite. Contact me (@tobifjellner) if you don’t have any such subsite or if you need access, and, obviously, if you need to add or update any information for your locale in the list

Kamran Abdul Aziz

Thanks, the new format is much easier to read and link to. I checked hi_IN: it only lists the glossary, and most of its 60 terms were added between 2015 and 2017, with only a handful since. There is no style guide yet. I’d be happy to help draft a glossary refresh, along with a Hindi style guide for human translators and one for agents, if the Hindi team would find that useful. What would be the best place to share the drafts so the team can review them first?

Reply

Deepak Kumar Test ·

Call for Testing: Presence API

The Presence 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. feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins team is preparing for a proposal to merge into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as the foundation for real-time awareness and modernized post locking.

We invite the community and the Make/Test team to test the admin interfaces and real-time interactions across typical admin workflows. Feedback is open through November 23, 2026.

What is Being Tested?

  • Real-Time Awareness: Live presence indicators across the admin toolbar, posts list, and user screens.
  • Modernized Post Locks: Post locks look and behave identically to standard WordPress core post locking, but their storage has moved off the _edit_lock post field and into the dedicated wp_presence table (#548).
  • Build Version: The Playground blueprints test the latest preview-main build (built from the main branch).

How to Test

You can test directly in your browser using WordPress Playground without any local environment setup:

Option A: Interactive Testing with Simulated Collaborators (Recommended)

This instance runs the companion presence-scenes tool, which simulates real-time virtual users editing posts and navigating the admin:

👉 Launch Playground with Simulated Collaborators

(The scene lasts under a minute. To replay it, open /wp-admin/edit.php?presence_scene=editing-together.)

Option B: Playground with Demo Data

This instance comes pre-seeded with 100 demo users and a few demo posts, along with a Demo bar to simulate saves from other users:

👉 Launch Playground with Demo Data

(Note: Because Playground stores site state locally in your browser storage, opening two separate browser windows or an incognito tab creates independent Playground sites. To test multi-user actions, please use the simulated collaborators in Option A or the Demo bar in Option B. Additionally, seeded demo users time out after ~2.5 minutes of inactivity; if this happens, simply relaunch the blueprint link to reseed).

Guided Test Tasks

Task 1: Admin Bar Real-Time Presence

Use Option A (Simulated Collaborators).

  1. Open wp-admin and find the faces and “N online” count next to Howdy in the toolbar.
  2. Observe the counter updating as simulated collaborators move across screens.
  3. Hover or use keyboard navigation (Tab) to open the presence menu.
  4. What to verify:
    • The faces and menu show other people (not you), and the “N online” count includes you.
    • User avatars and names are legible, tooltips render correctly, and keyboard focus works properly.
Desktop admin bar presence menu
Admin bar presence menu on desktop showing active collaborators.

Task 2: Posts List & “Editors” Column

Use Option A with the “Editing together” scene (/wp-admin/edit.php?presence_scene=editing-together).

  1. A few seconds after the scene starts, reload Posts > All Posts.
  2. Find Launch checklist, the post the collaborators are editing.
  3. What to verify:
    • The Editors column shows an 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. stack indicating active editors.
    • Hovering or navigating into the row with a keyboard reveals collaborator names.
    • On smaller screens (or responsive mobile view), avatars adjust without causing horizontal overflow.
Editors column with collaborator avatar stack
Editors column showing active collaborator avatar stack in the Posts list.

(Note: The simulated scene runs for under a minute. When the scene completes, it automatically cleans up its simulated users and deletes the “Launch checklist” post. Testers should act within this window, or replay the scene at any time by revisiting /wp-admin/edit.php?presence_scene=editing-together.)

Task 3: Post Locking and Takeover

Use Option A with the “Editing together” scene.

  1. In Posts > All Posts, click to edit a post that another collaborator is currently editing.
  2. Observe the post lock dialog.
  3. Click Take over.
  4. What to verify:
    • The lock dialog indicates that another user is currently editing the post.
    • Taking over closes the dialog and lets you edit the post.

(Note: If the scene finishes before you take over, the post will be deleted. Simply refresh /wp-admin/edit.php?presence_scene=editing-together to replay).

Task 4: Stale Screen Notification

Use Option B (Demo Data).

  1. Navigate to Settings > General.
  2. In the Demo bar at the top, click a Save as {name} button.
  3. What to verify:
    • A yellow stale-screen notification appears indicating that someone else has saved changes to this screen.
    • When dismissing the notice, keyboard focus smoothly moves to the screen heading.

(Note: The stale-screen notice is designed for individual edit screens and settings pages, not the main Posts list).

What to Check

  • 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): Can you navigate and operate all presence indicators using only a keyboard?
  • Responsiveness: Do views on phones or tablets display cleanly without broken layouts? (See #830 for reference phone layouts).
  • Usability: Are presence indicators informative without being distracting?
Phone admin bar compact user icon and online count
Phone admin bar: compact user icon and online count (<600px).

Phone touch menu listing active collaborator names
Phone touch menu: expands on tap to display collaborator names.

Known Issues

How to Report Feedback

Please share your testing report following the Make/Test reporting format:

  1. Environment: Device, OS, Browser & version.
  2. Tasks Tested: Which scenarios you walked through.
  3. Findings: Any bugs, unexpected behaviors, layout glitches, or design friction.
  4. Screenshots/Console: Attach screenshots or any browser console errors encountered.

You can post feedback:

Props to @devmuhib for drafting this Call for Testing, and to @joefusco and @huzaifaalmesbah for pre-publish review.

#call-for-testing, #feature-plugin

dhruvkb Openverse ·

A week in Openverse: 2026-11-02 – 2026-11-09

openverse

Merged PRs

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

  • #5674: Size the API’s DB connection pool for request concurrency and shorten ES timeouts
  • #5677: Stop the ES client from queueing without a deadline and make the health check’s DB check opt-in
  • #5685: Stop the shared aiohttp session from keeping a cookie jar
  • #5686: Answer Elasticsearch timeouts and outages with 504/503 instead of 500
  • #5687: Publish changelog for api-2026.11.05.12.27.17
  • #5688: Trim the API’s heap periodically to stop its residual memory growth

Documentation

  • #5664: Upgrade @sentry/nuxt to v11
  • #5670: Document kernel updates and AMI migrations for Elasticsearch nodes
  • #5677: Stop the ES client from queueing without a deadline and make the health check’s DB check opt-in
  • #5687: Publish changelog for api-2026.11.05.12.27.17

Frontend

openverse-infrastructure

Merged PRs

Infra

  • #1139: Update Terraform cloudflare to ~> 4.52.0
  • #1141: Update Terraform grafana to ~> 3.25.0
  • #1147: Update Terraform 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/ to v6.13.0
  • #1166: Update Terraform aws to ~> 5.100.0
  • #1172: Move staging Elasticsearch nodes to Amazon Linux 2023
  • #1173: Add a playbook to update the kernel and reboot hosts one at a time
  • #1174: Group the production ingestion server and drop the retired Airflow host
  • #1175: Update packages in the golden image and keep launch templates on it
  • #1176: Wait for shard moves and pause rebalancing in the kernel update
  • #1177: Tune glibc malloc for the API task and raise its health check grace period
  • #1178: Move production Elasticsearch nodes to Amazon Linux 2023

#openverse, #week-in-openverse

Matt Mullenweg Core ·

Conservative in What We Accept

Joe Youngblood’s report surprised me because I didn’t realize our conservative sanitize_username approach doesn’t apply to registrations when you’re not in multi-site mode.

https://x.com/YoungbloodJoe/status/2118795342875431305

We should assume every CRUDCRUD Create, read, update and delete, the four basic functions of storing data. (More on Wikipedia.) attempt is hostile. Where else can we tighten up the range of what we accept? For usernames we could make new registrations have stricter rules than before without breaking backwards compatibility.

Just like we ship with moderated comments on by default, I think it’s a good opportunity to look at every instance where we send an email and look at how we can become less interesting to spammers. Should comment notification emails not include the content by default, and instead just link you to the moderation page?

Peter Westwood

Just like we ship with moderated comments on by default, I think it’s a good opportunity to look at every instance where we send an email and look at how we can become less interesting to spammers.

<3

Reply

Ryan McCue

There’s a few annoying inconsistencies with this in multisite, where user signup is simultaneously less restrictive and more restrictive; I think primarily due to the legacy of MU’s username:subdomain, there’s a different set of sanitizing functions. (For example, multisite has a minimum length of 4 chars for the username, which is annoying if your name is eg sam.)

Unifying the behaviour would be great, and improve security.

Reply

Torsten Landsiedel

I think it’s a good opportunity to look at every instance where we send an email and look at how we can become less interesting to spammers.

In the past every media has an attachment page with open comments out-of-the-box by default. For existing sites #57913 hasn’t changed this behavior, only for new sites. And I doubt that a redirect to the media prevents sending a POST request if comments are open for this media ID. And there is no option for this or a bulk edit for media items to turn this off globally or for each media.
See: https://core.trac.wordpress.org/ticket/58375

Reply

Rade Jekić Team Updates ·

Training Team Update – November 7th, 2026

Hello from the Training Team!
Here’s our monthly roundup of updates, highlights, and ways to get involved. Let’s celebrate the work accomplished last month and look ahead together!

📌 Highlights

Here are some important updates from the Training Team!

  • 🧳 The Training Team is working on a big project: finding outdated content in the Training Team handbook and updating it. Feel free to learn more about it and join us. You can find us in the #training channel 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/.
  • 📚 Also, we are actively working on reviewing and improving the Learn WordPress Learning Pathways. Feel free to join the discussion and help us: https://make.wordpress.org/training/2026/10/27/help-us-review-and-improve-the-learn-wordpress-learning-pathways/
  • 🏫 We are actively working on multi-language 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. testing – we decided to reorganize all the translated content and make the Learn website easier to use for everyone. We will update you shortly.

⚒️ Overview of the Training Team Activities in October

  • We held 4 Training Team meetings. Team reps continued to facilitate weekly meetings, but we will change this going forward. We decided to give this role to all new admins in the Training Team who are willing to facilitate the meetings.
  • We held our sixth Training Team Office Hours meeting on October 28th and scheduled the next for November (we will inform you once the date is set and confirmed).

You can read the weekly meeting recap notes on the  Training Team blog.

📋 Project Status

ProjectNumber of Active Tickets
🔍 Content ready for review9
🐛 Feedback awaiting validation37
🧪 Topics awaiting vetting4
✅ Validated feedback awaiting fix27
👀 Translations ready to review22

📋 Project Update

Task TypeCompleted
🧯 Closed feedback tasks24
📖 Translated content22
🖊️ Translation in progress20
🪚 Workshops completed0

Huge thanks to all contributors – whether you took notes on a meeting, facilitated a meeting, translated or reviewed content, created content, hosted or co-hosted a workshop, or helped us wrangle the tasks and issues in 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/. Your efforts power the Training Team forward. 🙌

+make.wordpress.org/training/

#training

SAndrew Training ·

Training Team Meeting Recap – 3rd November 2026


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

Introductions and Welcome

There were 18 attendees: @sonaliprajapati, @jenish1234, @pravin1996, @ravigadhiyawp, @dilip2615, @rfluethi, @vishitshah, @sumitsingh, @makanikaran, @andrewssanya, @gohelkunjan (async), @harshjadav003 (async), @nitspatel (async), @aqdesk (async), @upekar99 (async), @valeriewandeler (async), @clk87 (async), @VasantRajput (async)

Newcomers: @hamadraja550, @w3techy

Meeting hosted by: @sumitsingh

Note Taker: @andrewssanya

Note Reviewer: @VasantRajput

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

Contributor Updates

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

Open Discussions

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

  • Have you heard the exciting announcement about a NEW FLAGSHIP WORDCAMPWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.?
    • Just like WordCamp Europe, WordCamp US, and WordCamp Asia, the newest flagship event is WordCamp India 2027!
    • Ahmedabad, Gujarat, has been officially confirmed as the host city for our 4th Flagship Event! Looking forward to an amazing event and great community participation!  Who’s excited about Ahmedabad

News

Meeting Note Takers

Here is our current note taker roster:

Thank you for taking this week’s notes, @andrewssanya!

Important note: If anyone needs to know more about note-taking and needs guidance in creating a Recap Note Post, they can DM @VasantRajput. He will guide you for a Recap Note and he will review & publish your Recap Post.

Looking for feedback

  • Translation reviewers: We are looking for a [Content] Needs Translation Reviewer. You can see all pending issues on GitHub.
  • Learning Pathways review: We are proposing a community-driven review of the Learn WordPress Learning Pathways (User, Developer, and Designer) to identify outdated content and gather improvement suggestions from experienced WordPress users and contributors. See the post for details: Help us review and improve the Learn WordPress Learning Pathways
  • Team homepage: @clk87 shared a 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.-based prototype for the Training Team homepage, aimed at making team pages more engaging and newcomer-friendly. Feedback is welcome on GitHub issue #3674.
  • Office Hours: The next Office Hours session will be held on a weekday, as preferred at the last meeting. The proposed date is November 25, 2026.
  • Text-to-speech: The team is exploring text-to-speech (read-aloud) functionality for course lessons. @softglaze has created prototypes, and we encourage everyone to share feedback before implementation discussions with the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team.
  • Training Team handbook: We’re actively updating the handbooks, and there’s still time to contribute. Please share suggestions, improvements, and ideas on GitHub issue #3447.
  • Intermediate PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Developer Course: @mebo revived the Learning Pathway course and has started working on modules and lessons. Please review the new content and share your feedback, including on the “Rendering plugin data” lesson.

Looking for volunteers

  • Help us review and improve the Learn WordPress Learning Pathways.
  • Content review: We need volunteers to find content that should be updated or consolidated. We would love to have two groups: one for the handbook and one for the courses. Please state your interest and we will help you get started.
  • Lesson thumbnails: Work has started on thumbnails for all lessons that need them. You’re welcome to help with the remaining ones through GitHub issue #3428.
  • Issue cleanup: We have many open issues, and it would be most effective to sort them into smaller categories and work through them one at a time.
    • Proposed workflow: Review Workflow: The proposed process is to review issues one by one, identify outdated or irrelevant items, suggest next steps, and add comments before closing or updating issues.
      • Good First Issues: Contributors can start with issues labeled Good First Issue, especially those related to content feedback, and follow the handbook guide for validating feedback.
      • Issue Categories: The team discussed starting with a specific categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., with Bug issues suggested as a priority. Other options include Needs Translation Reviewer, Unlabeled, Awaiting Triage, and Content Feedback.
      • Next Steps: Team members are encouraged to suggest which category should be reviewed first, after which the issues can be divided among contributors.
    • Let’s work together to clean up and keep the repository well organised.

Updates from last week’s Triage Squad session

  • N/A

Other News

Come and Contribute

This week’s contribution focus area

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

Contribution Acknowledgement

  • Badges awarded:
    • N/A
  • Give Props:
    • N/A

Project updates

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

Upcoming Online Workshops

  • N/A

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

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

Nur E Tasfiya

Thank you for sharing this detailed recap. I really appreciate the effort of the Training Team. I believe regular updates and beginner-friendly resources can encourage more people to contribute to WordPress.

Reply

Nilo Velez Community ·

Call for testing: Badge Designer, a simpler way to make WordCamp badges

Every 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. needs badges, and making them is still one of the most technical jobs on an organizer’s list. The two methods in the handbook were introduced in April 2016, ten years ago: writing CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. and printing from the browser, or exporting the attendees, running a script and laying everything out in Adobe InDesign. Many teams end up with spreadsheets, paid design tools or the one volunteer who knows how to do it.

At the same time, Matt’s post on Elevating individuals asked for badges that show the 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/ username, hometown and website, with the company below. Part of that already reached the 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. badges, but the way badges are made did not change.

This proposal is to fix that with Badge Designer, which is ready to try today. Please share your feedback by Friday, November 20, 2026.

What it is

A visual editor in wp-admin, under Tickets, where organizers:

  1. Upload their own badge artwork, made with any design tool.
  2. Place the attendee’s name, WordPress.org username, 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, a QR code to their WordPress.org profile, and the answer to any ticket question (hometown, website, company, job title…).
  3. Check every attendee’s badge on screen, with warnings for text that does not fit.
  4. Get one print-ready PDF, with bleed and crop marks, to send to the print shop.

No CSS, no scripts, and no proprietary third-party tools like Canva Pro or Adobe InDesign. The PDF is made in the organizer’s own browser, so it adds no load to WordCamp.org, however big the event is.

Try it now

How it gets to every WordCamp

The badge tools on WordCamp.org have barely changed since 2016, and the ticket to automate badge making stayed open for more than ten years, until it was closed this week alongside this proposal. This time the hard part is already done.

Badge Designer is a standalone pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. for now, so it can be tested without touching WordCamp.org. Once it has been tested, the plan is to integrate it into CampTix Badge Generator, the badge tool every WordCamp site already has, as the recommended way to make badges, with HTML/CSS and InDesign kept as alternatives. The user guide would then replace the badge pages of the Organizer Handbook.

The integration is small: one more option in an existing plugin, built with the same tools WordCamp.org already uses, and nothing changes in CampTix itself. It could easily be available before the end of the year, so the WordCamps of 2027 can start using it.

Where to give feedback

Please leave your feedback on the 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: WordPress/wordcamp.org#2286, so everything stays in one place next to the code. The most useful test is to recreate a real badge: upload the artwork of a past or upcoming WordCamp and see whether its design can be made with the editor.

A special thank you to @bor0 for all his support and help, and for reviewing every change so carefully and generously. Thanks also to @annezazu and @desrosj for their input along the way.

MD Mahabub- A Elahi Rahat

This looks like a very helpful improvement for WordCamp organizers. A visual badge editor can save a lot of time, especially for teams without dedicated designers. I think it would be useful to test different badge sizes, long attendee names, QR code readability, and PDF printing quality. Great initiative!

Reply

Huzaifa Al Mesbah Test ·

Month in Test: November 06, 2026

Hello and welcome to another edition of Month in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Table of Contents

  1. Calls for Testing 📣
  2. Test Handbook📘
    1. Merging of Test Handbook in Github
  3. Weekly Testing Roundup 🤠
    1. 1. WordPress Core Testing
      1. a. Patch Testing 🩹
      2. b. Bug Reproduction
      3. c. Test Team Issues
    2. 2. Gutenberg Testing
      1. a. Gutenberg Bug Reproduction Testing
      2. b. Gutenberg Patch Testing
  4. Profile Badge Awards 🎉
  5. Read/Watch/Listen 🔗
  6. Upcoming Meetings 🗓

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Test Handbook 📘

Merging of Test Handbook in 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/

For the last few months, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skills? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets (11) have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets (117) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

2. 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/ Testing

👋Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (7) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets (1) have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
@abcd95, @adamsilverstein, @alexodiy, @dhrupo, @fushar, @hbhalodia, @iamchitti, @jadavsanjay, @jamesbregenzer, @khokansardar, @marzanhusain, @madhavishah01, @mirmpro, @muneebashraf, @phpbits, @ravichudasama01, @ravipatel, @rejaulalomkhan, @sanayasir, @sonaliprajapati, @syedjakir91, @tusharbharti and @yusufmudagal

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Second and Fourth Thursday of the Month at 15:00 UTC
    • Weekly Test Chat: Third Thursday of the Month at 15:00 UTC
    • Monthly Voice Test Chat: First Thursday of each month at 15:00 UTC
  3. Call for Testing

Upcoming Meetings 🗓

🚨There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

Current 2026 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

props to @r1k0 for peer reviewing this post

#core-test, #fse-outreach-program, #gutenberg, #make-wordpress-orgupdates

Teams

  • Core

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

  • Design

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

  • Mobile

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

  • Accessibility

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

  • Polyglots

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

  • Support

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

  • Documentation

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

  • Themes

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

  • Plugins

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

  • Community

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

  • Meta

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

  • Training

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

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

  • Test

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

  • TV

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

  • Marketing

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

  • CLI

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

  • Hosting

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

  • Tide

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

  • Openverse

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

  • Photos

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

  • Core Performance

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

  • Playground

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

  • Core AI

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

  • Core Program

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

All teams and their meetings

Not sure which team to contribute to?

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