Training Team Highlights

Announcement

We’re considering issuing certificates specifically for course cohort students. Unlike automated course completion certificates—which can sometimes be misused—cohorts are different. In a cohort, students must actively participate in regular classes, complete assessments, and pass an exam before earning a certificate.

Recent Updates:

Current Focus Areas

Meetings in November

Meeting TypeDateFacilitator
Team MeetingNovember 3ndSumit Singh
Team MeetingNovember 10thMuhibul Haque
Team MeetingNovember 17thRade Jekić
Team MeetingNovember 24thMuhibul Haque
Continue reading →

Training Team Meeting Recap – 17th November 2026

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

Introductions and Welcome

There were 23 attendees: @sonaliprajapati, @ravigadhiyawp, @snehal5774, @rfluethi, @hamadraja550, @pravin1996, @fahimmurshed, @dilip2615, @rjekic, @jenish1234, @dhruvang21, @sumitsingh, @andrewssanya, @huzaifaalmesbah, @makanikaran, @nikola93n (async), @VasantRajput (async), @nitspatel (async), @harshjadav003 (async), @webgrrrl (async), @courane01 (async), @clk87 (async), @upekar99 (async),

Newcomers: @Puchoweb
Meeting hosted by: @Devmuhib
Note Taker: @Harshjadav003
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?
    • @courane01: Testing WP 7.2, and running an audit on LearnWP content for things to revise or create to bring it current with 7.2
  • Anything you’ve accomplished since the last meeting?
    • @courane01: Showing up for the first time in a long stretch.
  • Do you have any blockers?
  • Can other contributors or Training Team members help you in some way?

Open Discussions

  • Have you tried the new AI course created on the Learn platform?
    • AI-Powered WordPress
    • Have you tried to complete the course or just had a quick look at the content? What do you think about it?
    • If you already have experience working with AI in WordPress, can you help us with Feedback – Free AI APIs on AI Powered WordPress Course #3686?
    • We want to provide the best possible AI experience for everyone interested in working with AI in WordPress, including those who aren’t ready to pay for commercial models and agents.

News

Meeting Note Takers

Here is our current note taker roster:

  • 17th November – @Harshjadav003
  • 24th November – @Upekar99
  • 1st December – @Alkesh7
  • 8th December – Looking for Volunteer
  • 15th December – Looking for Volunteer

Important note: If anyone needs to know more about Note Taking and need guide in creating a Recap Note Post then you can DM to @vasantrajput. He will guide you for a Recap Note and he will review & publish your Recap Post.

Looking for feedback

  • We are proposing a community-driven review of the Learn WordPress Learning Pathways (User, Developer, and Designer) to identify outdated content and gather improvement suggestions from experienced WordPress users and contributors. Check out this post for details.

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.
  • 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.

Updates from last week’s Triage Squad session

  • No triage squad meetings last week

Other News

Come and Contribute

This week’s contribution focus area

  1. Content ready for review: 9 issues. See Guidelines for reviewing content.
  2. Feedback awaiting validation: 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

Project updates

Upcoming Online Workshops

  • No workshop scheduled for this week.

If you have topics you’d like discussed in the meeting, please leave them in the Open Discussion section.


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

Office Hours Meeting Recap, 28 October 2026

Related links:

Nine contributors joined this session. In this recap, Decisions are items the group agreed on in the meeting. Recommendations are proposals that still need the team’s confirmation. Please share feedback on the Recommendations as a comment on this issue or in the #training Slack channel.

Participants

NameWordPress.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/ ProfileLocation
Sumit Singh@sumitsinghAhmedabad, India
Rade Jekić@rjekicSerbia
Rico@rfluethiSwitzerland
Nitesh Patel@nitspatelAhmedabad, India
Vasantsinh Rajput@vasantrajputAhmedabad, India
Pravin Karmur@pravin1996Ahmedabad, India
Upeka@upekar99Sri Lanka; lives between Latvia and Italy
Mohammad Katerega@mohkatzJinja, Uganda
Dilip Modhavadiya@dilip2615Ahmedabad, India
All contributors joined this session live via Zoom.

Context

The session was divided into two parts. The first part covered introductions and a review of 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 backlog. The second part was hands-on, focusing on fixing @upekar99‘s translation issue live and planning triage meetings.

@rjekic thanked @rfluethi and @vasantrajput for keeping the team running while the team reps were unavailable. He emphasised that the reps are “not leaders, same level as all of you.” He also explained that @devmuhib had WP Credits and Campus Connect obligations, that being available online from Serbia was difficult, and that Sumit had his own commitments.

@rjekic clarified that the team operates without specific leaders, with reps serving as a communication bridge to other teams. Decisions are made collectively, and nothing is set in stone.

Throughout both parts of the session, the main blocker was that most contributors could not change labels or project fields.

Topics

1. A backlog of 600+ issues, many outdated or AI-generated

  • The Learn WordPress GitHub repository has more than 600 open issues. Many were opened by contributors using AI tools to identify errors, so some no longer reflect the current website. Many translation-related issues were also created in the same way.
  • @sumitsingh and @vasantrajput shared the project board and walked the group through its labels: admin agenda, awaiting triage, issue type, priority, 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), content, and site improvement.
  • The group decided to review the backlog in smaller groups, starting with issues that have no type assigned, as these are the quickest to review. Issues that are no longer relevant will be closed, while the remaining issues will be labelled.
  • HelpScout tickets are also piling up. @rjekic is working through the tickets he can after being away for a month, and @vasantrajput can convert a ticket into a GitHub issue. Ownership of each group of issues has not yet been decided.

2. Label and project rights are the blocker

  • @rjekic showed how a correctly filed feedback issue gets its labels automatically. A reviewer then removes the “awaiting triage” label, assigns the project (for example, Learn WP Content Feedback), and changes the status to “awaiting validation.” Each issue needs two validations before anyone can start working on it.
  • @rjekic described validating an issue as the easiest way to make a first contribution, for example, for someone who has commented on an issue and wants to help.
  • If someone enters the type of feedback incorrectly, such as including an extra space, the automation does not run. In such cases, labels and project fields have to be set manually.
  • Labels are not required to validate an issue, but contributors often search for issues using labels (for example, “good first issue”). As a result, unlabeled issues are harder to find.
  • @upekar99 and @vasantrajput could not change labels or project fields. @rjekic and @sumitsingh were unsure whether they could grant these permissions themselves. Therefore, the group decided to ask @devmuhib and @psykro to grant label permissions to @rfluethi and @vasantrajput before announcing the triage meeting. @rjekic will contact @devmuhib.
  • Who else needs these permissions is still to be determined.

3. Translation courses: one issue per lesson, linked from one course issue

  • @upekar99 could not create sub-issues for the Sinhala Beginner WordPress User course. @rjekic explained that each lesson should have its own issue, while one main course issue should list all the individual lesson issues as links. GitHub then automatically converts them into sub-issues.
  • He used the Bengali course issue (created by @devmuhib) as an example and pointed out that there must be no space between # and the issue number.
  • During the call, he updated @upekar99‘s issue #3656 to “content translation,” assigned it to the Localisation Translation Progress project, and added Sinhala as the language.
  • @upekar99 has translated lesson 1 in a Google Doc and will create the individual lesson issues. @sumitsingh will link them to the main course issue and remove the “awaiting triage” label.
  • @rjekic also demonstrated how a completed translation moves to the next stage. It is added to the Learn WP Content Localisation project with the status set to “ready for review” and the language specified (Bengali in his example).
  • He suspected that the Bengali translation was AI-generated because the issue had been opened just a week earlier. He also mentioned that each translation needs two reviewers who follow the relevant local glossaries, such as the German and Dutch glossaries.

4. Triage on Zoom first, then 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/

  • @rfluethi asked whether a session like this would be considered a triage meeting. @rjekic and @sumitsingh confirmed that it would. The group preferred using Zoom for the first few sessions so contributors could understand how triage works before moving to Slack once everyone is familiar with the process.
  • @rjekic prefers weekend sessions and offered to share his screen to explain the purpose of triage. He noted that triage previously focused mainly on pull requests and code, but the team now needs it for day-to-day issue management.
  • The group decided to hold the first triage meeting on a Saturday at 15:00 UTC, followed by weekly meetings at the same time. The announcement will be posted in the #training Slack channel once the label permissions are sorted out. Both @rfluethi and @sumitsingh offered to post the announcement. However, the date of the first Saturday is still to be confirmed.
  • Triage involves sorting issues into appropriate categories and labels and deciding which issues can be fixed without validation and which require validation.
  • After the first session, triage will become a recurring activity. However, the platform for future sessions (Slack, Google Meet, or Zoom) is still to be decided.
  • @rjekic suggested treating triage as one larger project, alongside the project group meetings proposed by @psykro and @mosescursor. He will also ask @psykro, or anyone else with the necessary access, to grant triage permissions to the contributors.

5. Outdated lesson content has to change in every language.

  • @rjekic is reviewing the Beginner WordPress User course. The first planned change is to replace Playground 5.1 with the latest version. Any changes made to the English lessons must also be communicated to all language teams; otherwise, the translations may become outdated or inconsistent with the original content.
  • Many images also need to be replaced, and this process is not automated. If the changes are extensive, @rjekic will create a separate validation issue. However, responsibility for replacing the images has not yet been decided.

6. Next Office Hours and who takes notes

  • The next Office Hours session will be held on a weekday at the same time. @sumitsingh suggested scheduling it on the last Wednesday of every month at a fixed time so it can be added to the team calendar.
  • The moderator and note-taker for the next session have not yet been decided. Participants also noted that while an AI-generated summary of the recording is helpful, it still takes time to turn it into a proper meeting recap post.

Decisions

#Decision
1Hold the first triage Zoom on a Saturday at 15:00 UTC, then weekly at the same time.
2Ask Muhibul Haque and Jonathan to give label rights to Rico and Vasantsinh before the triage meeting is announced.
3Start the backlog review with issues that have no type.
4Each lesson gets its own issue; one aggregate issue per course links them.
5The next Office Hours is on Wednesday, 25 November, at 15:00 UTC

Rationale: label rights come first because triage means sorting issues into categories and labeling them. A weekday suits most people for monthly Office Hours, and Zoom helps people learn triage by watching it.

Recommendations (for the team to confirm)

#RecommendationConsensus of attendees
1Use the last Wednesday of each month as the standing Office Hours slotYes, as a proposal
2Use two reviewers for each AI-generated translation, following local glossaries such as the German and Dutch ones.To confirm
3Give label and project rights to more contributors than just Rico and Vasantsinh, so triage does not depend on a few people.To confirm

Action Items

IssueTaskResponsible/ ParticipantStatus
—Ask @devmuhib and @psykro to grant label/triage rights to @rfluethi, @vasantrajput, and others who need them.@rjekic, @sumitsinghOpen
—Announce the first triage Zoom in the training Slack channel.@rfluethi / @sumitsinghOpen
—Run the first triage session (share screen, explain triage and labels).@rjekicOpen
#3656Create one issue per lesson for the Sinhala Beginner WordPress User course, starting with lesson 1.@upekar99Open
#3656Connect the lesson issues into the aggregate course issue; remove “awaiting triage.”@sumitsinghOpen
—Replace Playground 5.1 with the newest version in the English lessons; tell all language teams.@rjekicOpen
—Replace outdated images in lessons.@rjekic, @vasantrajput, language teamsOpen
—Validate feedback issues (two validations each).All contributorsOpen
—Review AI-generated translations (two reviewers, follow local glossaries).Language reviewersOpen
—Clear HelpScout tickets and create GitHub issues where needed.@rjekic, @vasantrajputOpen
—Add the next Office Hours to the training team calendar.@sumitsinghOpen
—Create and publish the meeting notes.@andrewssanyaDone
IssueTaskResponsible/ ParticipantStatus

Next meeting

This Office Hours session has been scheduled on a weekday as a trial. The day and time were finalised through proposals and discussions in the #training channel.

  • Date: November 25, 2026
  • Time: 15:00 UTC
  • Issue: To be created
  • Moderator: TBD
  • Note-taker: TBD

Focus topic: To be decided. The moderator will announce it in the #training Slack channel.

Summary: Focus Topics

The team’s focus for the next few weeks is getting triage working so the backlog can be cleaned up.

  • Access first: @rjekic will ask @devmuhib to give label and project rights to @rfluethi and @vasantrajput. The triage sessions are waiting for this.
  • Triage sessions: The first Zoom is on a Saturday at 15:00 UTC, then weekly. It will be announced in #training once rights are set.
  • Backlog clean-up: More than 600 open issues, starting with issues that have no type. Close what no longer applies and label the rest.
  • Translations: One issue per lesson, linked from one course issue. @upekar99 creates the Sinhala lesson issues, and @sumitsingh links them. AI-generated translations get two reviewers.
  • Outdated content: @rjekic updates Playground in the English lessons first, then every language team follows. Images need replacing too.
  • Next Office Hours: Wednesday 25 November, 15:00 UTC. The moderator, note-taker and topics are still to be chosen.

#learn-wordpress, #meeting-recap, #training-team

Meeting Agenda for November 17th, 2026

This week’s meeting will be held on Tuesday, November 17th, 2026, at 07:00 UTC. The meeting will take place 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 throughout the following days.

We’ll publish the meeting notes by the following Tuesday to incorporate these asynchronous conversations as well.

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

1. Intro/Welcome

  • Welcome to all the new teammates who joined the Training Team this week!
  • Icebreaker: If you could teach one WordPress skill to 1,000 students, what would it be?

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 the new AI course created on the Learn platform?
    • AI-Powered WordPress
    • Have you tried to complete the course or just had a quick look at the content? What do you think about it?
    • If you already have experience working with AI in WordPress, can you help us with Feedback – Free AI APIs on AI Powered WordPress Course?
    • We want to provide the best possible AI experience for everyone interested in working with AI in WordPress, including those who aren’t ready to pay for commercial models and agents.

4. News

1. Meeting Note Takers

  • 17th November: @Harshjadav08
  • 24th November: @UpekaR
  • 1st December: @miyanialkesh7
  • 8th December: Looking for a volunteer
  • 15th December: Looking for a volunteer

2. Looking for Feedback

We are proposing a community-driven review of the Learn WordPress Learning Pathways (User, Developer, and Designer) to identify outdated content and gather improvement suggestions from experienced WordPress users and contributors.

Check out this post for details.

3. Looking for Volunteers

Translation Review Volunteers

We have many lessons translated into different languages, but we need volunteers to review them and share their feedback on translation quality and possible improvements.

Join us on GitHub, find a language you speak and understand, and help us with the review process.

We don’t want these translated lessons and courses to remain unnoticed 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/!

Content Review Volunteers

We need volunteers to review and identify content that should be updated or consolidated. We are looking for two groups: one for the handbook and another 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 is working toward organizing the many open issues into smaller categories and reviewing them systematically.

  • Review Workflow: 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. Please follow the handbook guide for validating feedback.
  • Issue Categories: Bug issues have been suggested as a priority. Other categories include Needs Translation Reviewer, Unlabeled, Awaiting Triage, and Content Feedback.
  • Next Steps: Team members are encouraged to suggest which categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. should be reviewed first. Issues can then be divided among contributors.

Our goal is to work together to clean up and keep the repository organized.

4. Updates from Last Week’s Triage Squad Session

  • No Triage Squad meetings last week.

5. Other Announcements and News

5. Come and Contribute

Content ready for review

See the Guidelines for reviewing content when reviewing content.

  • We have 9 issues ready for review.

Feedback awaiting validation

See Validating and Applying Content Feedback for step-by-step guidance on validating feedback.

  • We have 37 issues that require validation.

Topics awaiting vetting

See Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.

  • We have 2 issues that require vetting.

Validated feedback awaiting fix

Contributors, see Validating and Applying Content Feedback for guidance on applying feedback that has been validated.

  • We have 27 issues awaiting a fix.

6. Contribution Acknowledgement

Badges awarded:

Congratulations, and thank you for your contributions!

7. Project Updates

  • Training Team Blog Homepage: @chekle has redesigned the homepage of our Training Team blog! Congratulations to him on the great work. We’d love to hear your thoughts and feedback. Please share them in GitHub Issue #3674.
  • WordPress Credits Milestone: WordPress Credits has reached over 50 institutions worldwide in just one year! A big shoutout to all the organizers, mentors, and students who made this possible. Read more about this milestone.

8. Upcoming Online Workshops

  • No workshop scheduled.

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, come walk through our onboarding program to learn more about the team and how we work.

If you have any questions, feel free to reach out in the #training Slack channel at any time.

Training Team Meeting Recap – 10th November 2026


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

Introductions and Welcome

There were 14 attendees: @dilip2615, @rjekic, @atik0130961, @mrinal013, @VasantRajput, @andrewssanya, @gohelkunjan, @sumitsingh, @pravin1996, @makanikaran, @sibokul, @mebo (async), @upekar99 (async), @jenish1234 (async), @jagirbahesh (async)

Newcomers: @jarmada, @rarcemunoz, @jbarquero90228

Meeting hosted by: @rjekic

Note Taker: @gohelkunjan @VasantRajput

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 other contributors or Training Team members help you in some way?
    • @snehal5774: I recently completed the Advanced WordPress User course and noticed that the “Continue to next lesson” option is available even before completing the quiz. This can be a little misleading, as in other courses, the option becomes available only after the quiz has been completed.
      It would be helpful if the course followed the same flow to ensure learners complete the quiz before moving on to the next lesson.
    • @rjekic: Thank you for pointing this out! Yes, I also find this a bit odd, but it is the default behaviour – that is, by design. We do not force users to finish the content or pass the course with the predefined percentage (for instance, 70%), but maybe it is time to consider the course design.

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?
      • This is one of the new AI-related courses created on our Learn platform: https://learn.wordpress.org/course/ai-powered-wordpress/
      • Have you tried to finish the course or just get a quick glimpse of the content? What do you think about it?
        • @atik0130961: I’ve recently started the AI-Powered WordPress course on Learn WordPress. I haven’t completed it yet, but I’ve started exploring the lessons.
          • @rjekic: Great! What do you think about the course? Is it easy to follow for someone without previous AI experience?
          • @atik0130961: So far, the course seems easy to follow. I hope the upcoming lessons will be just as easy to understand.
      • If you already have experience working with AI in WordPress, can you help us with this issue: Feedback – free AI APIs on AI Powered WordPress course #3686. We would like to give the best possible AI experience for all the people eager to work with AI in WordPress, but still not ready to pay for the commercial models and agents.

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…
      • This is the area where we need help the most. Everyday we are getting more and more translations that need to be reviewed and approved before going live.
    • 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

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

Project updates

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

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

X-post: Training Team Update – November 7th, 2026

X-post from +make.wordpress.org/updates: Training Team Update – November 7th, 2026

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

Meeting Agenda for November 3rd, 2026

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

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

1. Intro/Welcome

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

2. Contributor Updates

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

3. Open Discussions

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

4. News

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

5. Come and Contribute

6. Contribution Acknowledgement

  • Badges awarded:
    • No badges awarded this week

7. Project updates

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

8. Upcoming Online Workshops

  • No workshop scheduled

Training Team Meeting Recap – 27th October 2026

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

Introductions and Welcome

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

Newcomers: @daxinigaurav, @thenizampur, @atikurpub

Meeting hosted by: @devmuhib

Note Taker: @jenish1234

Note Reviewer: @vasantrajput

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

Contributor Updates

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

Open Discussions

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

News

Meeting Note Takers

Here is our current note-taker roster:

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

Looking for feedback

Looking for volunteers

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

Update for last week’s triage squad

  • No triage squad meetings last week

Other news

Come and Contribute

This week’s contribution focus area

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

Contribution Acknowledgement

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

Project updates

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

Upcoming Online Workshops

There is no workshop scheduled for this week.

Wrap up

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

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


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

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

Help Us Review and Improve the Learn WordPress Learning Pathways

The Learn WordPress Learning Pathways help people build their WordPress skills, whether they are getting started as users, developing websites, or exploring web design.

As WordPress continues to evolve, it’s important to make sure our learning materials remain accurate, relevant, and useful for learners. We’d like to invite experienced WordPress users, contributors, developers, designers, educators, and community members to help us review the existing Learning Pathways and identify opportunities for improvement.

What Are We Reviewing?

We’re looking for feedback on the three existing Learning Pathways:

We want to understand which lessons continue to work well, which may need updating, and whether there are gaps in the learning experience.

What Should You Look For?

As you explore the pathways, consider sharing feedback about the following:

  • Outdated instructions: Are any steps, screenshots, or explanations no longer accurate?
  • WordPress and software versions: Do lessons refer to older versions of WordPress, plugins, themes, or other tools where the content may need updating?
  • Tools and workflows: Have the recommended tools, interfaces, or workflows changed?
  • Missing information: Are there important concepts or skills that learners need but the lessons don’t currently cover?
  • Learning experience: Is the content easy to follow, well structured, and appropriate for its intended audience?
  • Opportunities for improvement: Could a lesson benefit from a clearer explanation, a practical exercise, a video, a better example, or a different teaching approach?

You don’t need to review an entire pathway. Feedback on even one lesson can be valuable.

How to Share Your Feedback

When submitting a suggestion, please include as much of the following information as possible:

  1. Learning Pathway: User, Developer, or Designer.
  2. Lesson title and URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: Which lesson are you referring to?
  3. What needs attention: Describe the outdated information, issue, or missing content.
  4. Suggested improvement: What would you change, and why?
  5. Supporting references: If available, share relevant documentation, current examples, or other resources that can help verify your suggestion.

Please be as specific as possible. For example, rather than saying that a lesson looks outdated, point out the particular instruction, interface, software version, or workflow that may need to be checked.

What Happens Next?

Our goal is to make this a collaborative and practical review process.

We’ll collect the feedback, group similar suggestions, and prepare a draft of the proposed improvements. Relevant Subject Matter Experts (SMEs) will then be invited to review the recommendations, verify their technical accuracy, and help determine which changes should be prioritized.

Not every suggestion will necessarily require a change. Some lessons may still be accurate and useful, while others may benefit from revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., additional examples, or updated resources.

Once the recommendations have been reviewed, we can work toward implementing the approved changes and establishing a process for keeping the Learning Pathways relevant over time.

Join Us in Improving Learn WordPress

If you have experience with WordPress, teaching, web development, design, or creating learning resources, we’d love to hear from you.

Your perspective can help us identify issues that might otherwise go unnoticed and make the learning experience better for people discovering and working with WordPress.

Which lessons do you think need attention, and what improvements would you suggest?

Let’s work together to make Learn WordPress an even more useful resource for the community.