Title: Make WordPress Training – WordPress Training Team, providing synchronous and asynchronous WordPress learning --- [ ](https://profiles.wordpress.org/devmuhib/) [Muhibul Haque](https://profiles.wordpress.org/devmuhib/) 1:08 am _on_ March 3, 2026   # 󠀁[Training Team Highlights](https://make.wordpress.org/training/2026/03/03/training-team-highlights/)󠁿 ## Recent Updates and Achievements ## 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: * [Monthly Office Hour Meeting for Make WordPress Training](https://make.wordpress.org/training/2026/02/03/proposal-monthly-office-hour-meeting-for-make-wordpress-training/) * [Announcing the Training Team Cohort: “Block Theme Development in WordPress”](https://make.wordpress.org/training/2026/03/30/announcing-the-training-team-cohort-block-theme-development-in-wordpress/) * [Welcoming New Mentors to the Training Team Guide Program](https://make.wordpress.org/training/2025/06/30/welcoming-new-mentors-to-the-training-team-guide-program/) * [Announcing Our Second Deputy in WordPress Training Team](https://make.wordpress.org/training/2025/06/10/announcing-our-second-deputy-in-wordpress-training-team-deputy-representative-program/) * [Training Team Goals for 2025](https://make.wordpress.org/training/2025/01/27/training-team-goals-for-2025/) * [WordCamp Europe 2026 Contributor Day](https://make.wordpress.org/training/2026/06/22/wordcamp-europe-2026-contributor-day-recap/) ## Current Focus Areas * [Drawing new learners to the new Learn.WordPress.org](https://make.wordpress.org/training/2024/08/28/drawing-new-learners-to-the-new-learn-wordpress-org/) * [Video Thumbnail Generator Project](https://make.wordpress.org/design/handbook/resources/figma-thumbnail-generator/) * [Training Team Guide Program](https://make.wordpress.org/training/handbook/guide-program/guide-program-handbook/) * [Hosting an Online Workshop](https://make.wordpress.org/training/handbook/online-workshops/) ## Meetings in October | **Meeting Type** | **Date** | **Facilitator** | | Team Meeting | October 6th | [](https://profiles.wordpress.org/devmuhib/)[Rade Jekić](https://profiles.wordpress.org/rjekic) | | Team Meeting | October 13th | [](https://profiles.wordpress.org/rjekic)[Muhibul Haque](https://profiles.wordpress.org/devmuhib/) | | Team Meeting | October 20th | [Sumit Singh](https://profiles.wordpress.org/sumitsingh) | | Team Meeting | October 27th | [](https://profiles.wordpress.org/devmuhib/)[Rade Jekić](https://profiles.wordpress.org/rjekic) | [Continue reading →](https://make.wordpress.org/training/2026/03/03/training-team-highlights/#more-121530) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F03%2F03%2Ftraining-team-highlights%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/devmuhib/) [Muhibul Haque](https://profiles.wordpress.org/devmuhib/) 3:47 pm _on_ October 12, 2026 Tags: [training ( 367 )](https://make.wordpress.org/training/tag/training/) # 󠀁[Meeting Agenda for October 13th, 2026](https://make.wordpress.org/training/2026/10/12/meeting-agenda-for-october-13th-2026/)󠁿 This week’s meeting will be held on Tuesday, October 13th, 2026, at [07:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?hour=07&min=00&sec=0). The meeting will be held on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), in the [#training](https://make.wordpress.org/training/tag/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 [@devmuhib](https://profiles.wordpress.org/devmuhib/). ## 1. Intro/Welcome Welcome to all the new teammates who joined the Training Team this week! ## 2. News 1. [Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/) 2. * Oct 13th – [@miyanialkesh7](https://github.com/miyanialkesh7)[](https://profiles.wordpress.org/alkesh7) * Oct 20th – [@softglazee](https://github.com/softglazee)[](https://profiles.wordpress.org/softglaze) * Oct 27th – [@Kotiyajenish](https://github.com/Kotiyajenish)[](https://profiles.wordpress.org/jenish1234) * Nov 3rd – [@SAndrrew](https://github.com/SAndrrew)[](https://profiles.wordpress.org/andrewssanya) * Nov 10th – [@gohelkunjan](https://github.com/gohelkunjan)[](https://profiles.wordpress.org/gohelkunjan) 3. **Looking for feedback** 4. * **WordPress Hackathon:** Recently we tried a WordPress Hackathon at Stamford University, Bangladesh alongside WordPress Campus Connect event. We have created a [community blog post](https://make.wordpress.org/community/2026/10/12/our-first-wordpress-campus-connect-hackathon-what-worked-what-didnt-and-whats-next/) where you can share your feedback. * **Team Homepage:** [@clk87](https://profiles.wordpress.org/clk87/) has shared [A block-based prototype for the Training Team homepage](https://playground.wordpress.net/?import-site=https://raw.githubusercontent.com/chekle/Make-Homepage/main/wordpress-playground-training.zip) to make team pages more engaging and newcomer-friendly. Feedback is welcome via [GitHub Issue #3674](https://github.com/WordPress/Learn/issues/3674). * **Office Hours**: The next Office Hours will be held on a weekday, avoiding Monday and Friday. The proposed dates are October 27, 28, or 29, 2026, you will be informed when the date is set and confirmed. * **Text-to-Speech:** The team discussed [exploring text-to-speech/read-aloud functionality](https://github.com/WordPress/Learn/issues/3649) for course lessons. [@softglazee](https://github.com/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](https://github.com/WordPress/Learn/issues/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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Developer Course:** [@mebo](https://profiles.wordpress.org/mebo/) has revived the [Learning Pathway course](https://github.com/WordPress/Learn/issues/2044) 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](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201). 5. **Looking for volunteers** 6. * **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](https://github.com/WordPress/Learn/issues/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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), especially those related to content feedback, and follow the [handbook guide for validating feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues). * **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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) suggested as a priority. Other options include [Needs Translation Reviewer](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22), [Unlabeled](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel), [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22), and [Content Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22). * **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. 7. Updates from last week’s Triage Squad session 8. * No triage squad meetings last week 9. Other announcements and news 10. * **Office Hours Recap:** The September 26, 2026 Office Hours session was successfully hosted, moderated by [@vasantrajput](https://profiles.wordpress.org/vasantrajput/), and the [recap post has been published](https://make.wordpress.org/training/2026/09/29/office-hours-meeting-recap-september-26-2026/). Thanks to [@rfluethi](https://profiles.wordpress.org/rfluethi/) for preparing the draft. * **Monthly Update:** The [Training Team’s September 2026 monthly update](https://make.wordpress.org/updates/2026/10/04/training-team-update-october-4th-2026/) has been published. * **Community & Slack:** The team shared the guide on [how to bring your community to Make WordPress Slack](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/). ## 2. Come and Contribute * [Content ready for review](https://github.com/orgs/WordPress/projects/33/views/17) - See [Guidelines for reviewing content](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) when reviewing content. * We have 9 issues ready for review * [[[Feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3) - See [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on validating feedback. * We have 39 issues that require validation * [Topics awaiting vetting](https://github.com/orgs/WordPress/projects/105/views/1) - See [Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/) for step-by-step guidance on vetting topic ideas. * We have 2 issues that require vetting * [Validated feedback awaiting fix](https://github.com/orgs/WordPress/projects/78/views/4) - Contributors, see [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on applying feedback that has been validated. * We have 26 issues awaiting a fix ## 3. Contribution Acknowledgement * Badges awarded: - No badges awarded this week ## 4. 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. ## 5. Upcoming Online Workshops * No workshop scheduled ## 6. 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? ## 7. Open Discussions If you have topics you’d like discussed in the meeting, please leave them as a comment on this post. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F10%2F12%2Fmeeting-agenda-for-october-13th-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/makanikaran/) [Karan Makani](https://profiles.wordpress.org/makanikaran/) 5:15 am _on_ October 12, 2026   # 󠀁[Training Team Meeting Recap – 6th October 2026](https://make.wordpress.org/training/2026/10/12/training-team-meeting-recap-6th-october-2026/)󠁿 This meeting followed this meeting agenda in [GitHub](https://github.com/WordPress/Learn/issues/3685) and [P2 Post](https://make.wordpress.org/training/2026/10/04/meeting-agenda-for-october-6th-2026/). You can see conversations from the meeting in this [Slack Log](https://wordpress.slack.com/archives/C02RW657Q/p1791270046225529).( If you don’t have a SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) account, you can [set one up](https://make.wordpress.org/chat/).) ## **Introductions and Welcome** **There were 27 attendees:** [@pravin1996](https://profiles.wordpress.org/pravin1996/), [@rjekic](https://profiles.wordpress.org/rjekic/), [@dilip2615](https://profiles.wordpress.org/dilip2615/), [@lidarroy](https://profiles.wordpress.org/lidarroy/), [@alkesh7](https://profiles.wordpress.org/alkesh7/), [@rfluethi](https://profiles.wordpress.org/rfluethi/), [@jenish1234](https://profiles.wordpress.org/jenish1234/), [@mosescursor](https://profiles.wordpress.org/mosescursor/), [@ishahinakhter](https://profiles.wordpress.org/ishahinakhter/), [@vishitshah](https://profiles.wordpress.org/vishitshah/), [@freewebmentor](https://profiles.wordpress.org/freewebmentor/), [@makanikaran](https://profiles.wordpress.org/makanikaran/), [@dhruvang21](https://profiles.wordpress.org/dhruvang21/), [@vasantrajput](https://profiles.wordpress.org/vasantrajput/), [@sumitsingh](https://profiles.wordpress.org/sumitsingh/), [@harshjadav003](https://profiles.wordpress.org/harshjadav003/), [@sonaliprajapati](https://profiles.wordpress.org/sonaliprajapati/)( async), [@ravigadhiyawp](https://profiles.wordpress.org/ravigadhiyawp/) (async), [@webgrrrl](https://profiles.wordpress.org/webgrrrl/) (async), [@rithika3](https://profiles.wordpress.org/rithika3/)( async), [@sibokul](https://profiles.wordpress.org/sibokul/) (async), [@andrewssanya](https://profiles.wordpress.org/andrewssanya/)( async), [@nitspatel](https://profiles.wordpress.org/nitspatel/) (async), [@upekar99](https://profiles.wordpress.org/upekar99/)( async), [@valeriewandeler](https://profiles.wordpress.org/valeriewandeler/) (async), [@ursha](https://profiles.wordpress.org/ursha/) (async), [@mohkatz](https://profiles.wordpress.org/mohkatz/)( async) **Newcomers:** [@fgcalderon](https://profiles.wordpress.org/fgcalderon/), [@owaisobject](https://profiles.wordpress.org/owaisobject/), [@riyad176255](https://profiles.wordpress.org/riyad176255/), [@forhadkhan](https://profiles.wordpress.org/forhadkhan/), [@purvadesai21](https://profiles.wordpress.org/purvadesai21/), [@noushin955](https://profiles.wordpress.org/noushin955/), [@msarvas](https://profiles.wordpress.org/msarvas/) **Meeting hosted by:**[@rjekic](https://profiles.wordpress.org/rjekic/) **Note Taker:**[@makanikaran](https://profiles.wordpress.org/makanikaran/) **Note Reviewer:** [@vasantrajput](https://profiles.wordpress.org/vasantrajput/) Welcome! Please post in the [#training](https://wordpress.slack.com/archives/C02RW657Q) channel or reach out to a team member to help you with contributing. Resources to check out [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/), and our [Guide Program](https://make.wordpress.org/training/handbook/guide-program/). ## News ### 󠀁[Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/)󠁿 Here is our current note taker roster: * 6th October – [@makanikaran](https://profiles.wordpress.org/makanikaran/) * 13th October – [@alkesh7](https://profiles.wordpress.org/alkesh7/) * 20th October – [@softglaze](https://profiles.wordpress.org/softglaze/) **Important note**: If anyone needs more information on note-taking or a guide to creating a Recap Note Post, they can DM [Vasantsinh Rajput](https://wordpress.slack.com/team/U0818LF4W4X). He will guide you on a Recap Note, and he will review & publish your Recap Post. ### Looking for feedback * **Team Homepage:** [@clk87](https://profiles.wordpress.org/clk87/) has shared [A block-based prototype for the Training Team homepage](https://playground.wordpress.net/?import-site=https://raw.githubusercontent.com/chekle/Make-Homepage/main/wordpress-playground-training.zip) to make team pages more engaging and newcomer-friendly. Feedback is welcome via [GitHub Issue #3674](https://github.com/WordPress/Learn/issues/3674). * **Text-to-Speech:** The team discussed [exploring text-to-speech/read-aloud functionality](https://github.com/WordPress/Learn/issues/3649) for course lessons. [@softglaze](https://profiles.wordpress.org/softglaze/) has created prototypes, and the team is encouraged to provide 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:** The handbook is currently being updated, and team members are encouraged to share suggestions, improvements, and ideas in [GitHub Issue #3447](https://github.com/WordPress/Learn/issues/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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Developer Course:** [@mebo](https://profiles.wordpress.org/mebo/) has revived the [Learning Pathway course](https://github.com/WordPress/Learn/issues/2044) 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](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201). ### 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](https://github.com/WordPress/Learn/issues/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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), especially those related to content feedback, and follow the [handbook guide for validating feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues). * **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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) suggested as a priority. Other options include [Needs Translation Reviewer](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22), [Unlabeled](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel), [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22), and [Content Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22). * **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 * N/A ### Updates for the Office Hours session * **Last Office Hours Recap:** The September 26, 2026 Office Hours session was successfully hosted, moderated by [@vasantrajput](https://profiles.wordpress.org/vasantrajput/), and the [recap post has been published](https://make.wordpress.org/training/2026/09/29/office-hours-meeting-recap-september-26-2026/). Thanks to [@rfluethi](https://profiles.wordpress.org/rfluethi/) for preparing the draft. * **Looking for feedback for Next Office Hours:** The next Office Hours will be held on a weekday, avoiding Monday and Friday. The proposed dates are October 27, 28, or 29, 2026. [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) will be informed when the date is set and confirmed. ### Other News * **Monthly Update:** The [Training Team’s September 2026 monthly update](https://make.wordpress.org/updates/2026/10/04/training-team-update-october-4th-2026/) has been published. * **Community & Slack:** The team shared the guide on [how to bring your community to Make WordPress Slack](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/). ## Come and Contribute ### This week’s contribution focus area 1. [Content ready for review](https://github.com/orgs/WordPress/projects/33/views/17) 2. * See [Guidelines for reviewing content](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) when reviewing content. * We have 9 issues ready for review 3. [Feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3) 4. * See [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on validating feedback. * We have 39 issues that require validation 5. [Topics awaiting vetting](https://github.com/orgs/WordPress/projects/105/views/1) 6. * See [Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/) for step-by-step guidance on vetting topic ideas. * We have 2 issues that require vetting 7. [Validated feedback awaiting fix](https://github.com/orgs/WordPress/projects/78/views/4) 8. * Contributors, see [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on applying feedback that has been validated. * We have 26 issues awaiting a fix ## Contribution Acknowledgement * **Badges awarded**: - No badges awarded this week * **GiveProps**: - No give props this week ## Project updates * Thanks to our colleague [@Destiny](https://profiles.wordpress.org/destiny/), the course [_AI Literacy through WordPress_](https://learn.wordpress.org/course/ai-literacy-through-wordpress/) is now live on Learn WordPress! * Building on the momentum of our last learning cohort (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. Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem. ## Upcoming Online Workshops * N/A ## Contributor Updates * N/A ## Open Discussions * If you have topics you’d like discussed in the meeting, please leave them as a comment on this issue. - [@vasantrajput](https://profiles.wordpress.org/vasantrajput/): [@sumitsingh](https://profiles.wordpress.org/sumitsingh/), [@rjekic](https://profiles.wordpress.org/rjekic/) 1) Have we finalised the** Training Team Office Hours** next meeting **Date/Time** and the **Topic** suggestion? 2) Also, any news for the **TT Admin meeting** schedule? Thanks to everyone who participated in the sync and async, and to those who will contribute in future sessions. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F10%2F12%2Ftraining-team-meeting-recap-6th-october-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/rjekic/) [Rade Jekić](https://profiles.wordpress.org/rjekic/) 6:56 pm _on_ October 4, 2026 Tags: [training ( 367 )](https://make.wordpress.org/training/tag/training/) # 󠀁[Meeting Agenda for October 6th, 2026](https://make.wordpress.org/training/2026/10/04/meeting-agenda-for-october-6th-2026/)󠁿 This week’s meeting will be held on Tuesday, September 15th, 2026, at [07:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?hour=07&min=00&sec=0). The meeting will be held on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), in the [#training](https://make.wordpress.org/training/tag/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 [@rjekic](https://profiles.wordpress.org/rjekic/). ## 1. Intro/Welcome Welcome to all the new teammates who joined the Training Team this week! ## 2. News 1. [Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/) 2. * Oct 6th – [@makanikaran](https://profiles.wordpress.org/makanikaran/) * Oct 13th – [@alkesh7](https://profiles.wordpress.org/alkesh7/) * Oct 20th – [@softglaze](https://profiles.wordpress.org/softglaze/) 3. **Looking for feedback** 4. * **Team Homepage:** [@clk87](https://profiles.wordpress.org/clk87/) has shared [A block-based prototype for the Training Team homepage](https://playground.wordpress.net/?import-site=https://raw.githubusercontent.com/chekle/Make-Homepage/main/wordpress-playground-training.zip) to make team pages more engaging and newcomer-friendly. Feedback is welcome via [GitHub Issue #3674](https://github.com/WordPress/Learn/issues/3674). * **Office Hours**: The next Office Hours will be held on a weekday, avoiding Monday and Friday. The proposed dates are October 27, 28, or 29, 2026, you will be informed when the date is set and confirmed. * **Text-to-Speech:** The team discussed [exploring text-to-speech/read-aloud functionality](https://github.com/WordPress/Learn/issues/3649) for course lessons. [@softglazee](https://github.com/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](https://github.com/WordPress/Learn/issues/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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Developer Course:** [@mebo](https://profiles.wordpress.org/mebo/) has revived the [Learning Pathway course](https://github.com/WordPress/Learn/issues/2044) 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](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201). 5. **Looking for volunteers** 6. * **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](https://github.com/WordPress/Learn/issues/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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), especially those related to content feedback, and follow the [handbook guide for validating feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues). * **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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) suggested as a priority. Other options include [Needs Translation Reviewer](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22), [Unlabeled](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel), [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22), and [Content Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22). * **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. 7. Updates from last week’s Triage Squad session 8. * No triage squad meetings last week 9. Other announcements and news 10. * **Office Hours Recap:** The September 26, 2026 Office Hours session was successfully hosted, moderated by [@vasantrajput](https://profiles.wordpress.org/vasantrajput/), and the [recap post has been published](https://make.wordpress.org/training/2026/09/29/office-hours-meeting-recap-september-26-2026/). Thanks to [@rfluethi](https://profiles.wordpress.org/rfluethi/) for preparing the draft. * **Monthly Update:** The [Training Team’s September 2026 monthly update](https://make.wordpress.org/updates/2026/10/04/training-team-update-october-4th-2026/) has been published. * **Community & Slack:** The team shared the guide on [how to bring your community to Make WordPress Slack](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/). ## 2. Come and Contribute * [Content ready for review](https://github.com/orgs/WordPress/projects/33/views/17) - See [Guidelines for reviewing content](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) when reviewing content. * We have 9 issues ready for review * [[[Feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3) - See [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on validating feedback. * We have 39 issues that require validation * [Topics awaiting vetting](https://github.com/orgs/WordPress/projects/105/views/1) - See [Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/) for step-by-step guidance on vetting topic ideas. * We have 2 issues that require vetting * [Validated feedback awaiting fix](https://github.com/orgs/WordPress/projects/78/views/4) - Contributors, see [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on applying feedback that has been validated. * We have 26 issues awaiting a fix ## 3. Contribution Acknowledgement * Badges awarded: - No badges awarded this week ## 4. Project updates * Thanks to our colleague [@piyopiyofox](https://profiles.wordpress.org/piyopiyofox/), the course **_[AI Literacy through WordPress](https://learn.wordpress.org/course/ai-literacy-through-wordpress/)_** is now live on Learn WordPress! * Building on the momentum of our last learning cohort (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. Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem. ## 5. Upcoming Online Workshops * No workshop scheduled ## 6. 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? ## 7. Open Discussions If you have topics you’d like discussed in the meeting, please leave them as a comment on this post. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F10%2F04%2Fmeeting-agenda-for-october-6th-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/rjekic/) [Rade Jekić](https://profiles.wordpress.org/rjekic/) 6:15 pm _on_ October 4, 2026 Tags: [make.wordpress.org/updates ( 46 )](https://make.wordpress.org/training/tag/make-wordpress-orgupdates/), [p2-xpost ( 147 )](https://make.wordpress.org/training/tag/p2-xpost/)    # 󠀁[X-post: Training Team Update – October 4th, 2026](https://make.wordpress.org/training/2026/10/04/xpost-training-team-update-october-4th-2026/)󠁿 X-post from [+make.wordpress.org/updates](https://make.wordpress.org/updates/): [Training Team Update – October 4th, 2026](https://make.wordpress.org/updates/2026/10/04/training-team-update-october-4th-2026/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F10%2F04%2Fxpost-training-team-update-october-4th-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/pravin1996/) [Pravin Karmur](https://profiles.wordpress.org/pravin1996/) 4:06 pm _on_ October 3, 2026 Tags: [meeting recap ( 187 )](https://make.wordpress.org/training/tag/meeting-recap/), [training ( 367 )](https://make.wordpress.org/training/tag/training/), [Training-team ( 252 )](https://make.wordpress.org/training/tag/training-team/) # 󠀁[Training Team Meeting Recap – 29th September 2026](https://make.wordpress.org/training/2026/10/03/training-team-meeting-recap-29th-september-2026/)󠁿 This meeting followed this meeting agenda in [GitHub](https://github.com/WordPress/Learn/issues/3681) and [P2 Post](https://make.wordpress.org/training/2026/09/29/meeting-agenda-for-september-29th-2026/). You can see conversations from the meeting in this [Slack Log](https://wordpress.slack.com/archives/C02RW657Q/p1790665278591529).( If you don’t have a SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) account, you can [set one up](https://make.wordpress.org/chat/).) ## **Introductions and Welcome** **There were 29 attendees:** [@pravin1996](https://profiles.wordpress.org/pravin1996/), [@sonaliprajapati](https://profiles.wordpress.org/sonaliprajapati/), [@jenish1234](https://profiles.wordpress.org/jenish1234/), [@ishahinakhter](https://profiles.wordpress.org/ishahinakhter/), [@sumitsingh](https://profiles.wordpress.org/sumitsingh/), [@mrinal013](https://profiles.wordpress.org/mrinal013/), [@alkesh7](https://profiles.wordpress.org/alkesh7/), [@Dhruvang21](https://profiles.wordpress.org/dhruvang21/), [@rjekic](https://profiles.wordpress.org/rjekic/), [@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/), [@makanikaran](https://profiles.wordpress.org/makanikaran/), [@rfluethi](https://profiles.wordpress.org/rfluethi/), [@mehuldabgar](https://profiles.wordpress.org/mehuldabgar/), [@sumitjavia](https://profiles.wordpress.org/sumitjavia/), [@praful2111](https://profiles.wordpress.org/praful2111/), [@dilip2615](https://profiles.wordpress.org/dilip2615/), [@vasantrajput](https://profiles.wordpress.org/vasantrajput/), [@jadavsanjay](https://profiles.wordpress.org/jadavsanjay/), [@vishitshah](https://profiles.wordpress.org/vishitshah/), [@nitspatel](https://profiles.wordpress.org/nitspatel/), [@freewebmentor](https://profiles.wordpress.org/freewebmentor/), [@gohelkunjan](https://profiles.wordpress.org/gohelkunjan/) (async), [@harshjadav003](https://profiles.wordpress.org/harshjadav003/)( async), [@sibokul](https://profiles.wordpress.org/sibokul/) (async), [@ursha](https://profiles.wordpress.org/ursha/)( async), [@andrewssanya](https://profiles.wordpress.org/andrewssanya/) (async), [@rithika3](https://profiles.wordpress.org/rithika3/)( async), [@valeriewandeler](https://profiles.wordpress.org/valeriewandeler/) (async), [@jagirbahesh](https://profiles.wordpress.org/jagirbahesh/) (async) **Newcomers:** [@silviamaringiraldo](https://profiles.wordpress.org/silviamaringiraldo/), [@nitspatel](https://profiles.wordpress.org/nitspatel/), [@mehuldabgar](https://profiles.wordpress.org/mehuldabgar/) **Meeting hosted by:** [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) **Note Taker:** [@pravin1996](https://profiles.wordpress.org/pravin1996/) **Note Reviewer:** [@vasantrajput](https://profiles.wordpress.org/vasantrajput/) Welcome! Please post in the [#training](https://wordpress.slack.com/archives/C02RW657Q) channel or reach out to a team member to help you with contributing. Resources to check out [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/), and our [Guide Program](https://make.wordpress.org/training/handbook/guide-program/). ## News ### 󠀁[Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/)󠁿 Here is our current note taker roster: * 29th September – [@pravin1996](https://profiles.wordpress.org/pravin1996/) * 6th October – [@makanikaran](https://profiles.wordpress.org/makanikaran/) * 13th October – [@alkesh7](https://profiles.wordpress.org/alkesh7/) * 20th October – [@softglaze](https://profiles.wordpress.org/softglaze/) **Important note**: If anyone needs more information on note-taking or a guide to creating a Recap Note Post, they can DM [Vasantsinh Rajput](https://wordpress.slack.com/team/U0818LF4W4X). He will guide you on a Recap Note, and he will review & publish your Recap Post. ### Looking for feedback * **Team Homepage**: [@clk87](https://profiles.wordpress.org/clk87/) has shared [A block-based prototype for the Training Team homepage](https://playground.wordpress.net/?import-site=https://raw.githubusercontent.com/chekle/Make-Homepage/main/wordpress-playground-training.zip) to make team pages more engaging and newcomer-friendly. Feedback is welcome via [GitHub Issue #3674](https://github.com/WordPress/Learn/issues/3674). * **Office Hours**: The next Office Hours will be held on a weekday, avoiding Monday and Friday. The proposed dates are **October 27, 28, or 29, 2026,** with [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) to confirm the date and time after Tuesday’s meeting. * **Text-to-Speech**: The team discussed [exploring text-to-speech/read-aloud functionality](https://github.com/WordPress/Learn/issues/3649) for course lessons. [@softglaze](https://profiles.wordpress.org/softglaze/) 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.. * **Training Team Handbook**: The handbook is currently being updated, and team members are encouraged to share suggestions, improvements, and ideas in [GitHub Issue #3447](https://github.com/WordPress/Learn/issues/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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Developer Course**: [@mebo](https://profiles.wordpress.org/mebo/) has revived the [Learning Pathway course](https://github.com/WordPress/Learn/issues/2044) 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](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201). ### Looking for volunteers * Schedule the next Office Hours: weekday trial, date, moderator, and note-taker– [View on GitHub #3679](https://github.com/WordPress/Learn/issues/3679) * Open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source** must be** delivered via a licensing model, see GPL. basics and WordPress; Quiz question answers for “What benefits can lead to a conflict of interest – [View on GitHub #3675](https://github.com/WordPress/Learn/issues/3675) * Needs Translation Reviewer for Lesson – [View on GitHub](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22) * **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](https://github.com/WordPress/Learn/issues/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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), especially those related to content feedback, and follow the [handbook guide for validating feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues). * **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](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) suggested as a priority. Other options include **[Needs Translation Reviewer](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22), [Unlabeled](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel), [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22),** and **[Content Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22)**. * **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 * N/A ### Other News * **Office Hours Format:** A short description of the Office Hours format will be publish by [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) ([@rfluethi](https://profiles.wordpress.org/rfluethi/) will preparing the initial draft), and reviewed by the team. * **Office Hours Recap:** The September 26, 2026 Office Hours session was successfully hosted, moderated by [@vasantrajput](https://profiles.wordpress.org/vasantrajput/), and the [recap post has been published](https://make.wordpress.org/training/2026/09/29/office-hours-meeting-recap-september-26-2026/). Thanks to [@rfluethi](https://profiles.wordpress.org/rfluethi/) for preparing the draft. * **Monthly Update:** The [Training Team’s August 2026 monthly update](https://make.wordpress.org/updates/2026/08/02/training-team-update-august-2nd-2026/) has been published. * **Community & Slack:** The team shared the guide on [how to bring your community to Make WordPress Slack](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/). ## Come and Contribute ### This week’s contribution focus area 1. **Content Ready for Review:** 9 issues are ready for review. Please follow the ** Guidelines for Reviewing Content** handbook when reviewing the content. 2. * 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/](https://github.com/): [https://github.com/orgs/WordPress/projects/33/views/17](https://github.com/orgs/WordPress/projects/33/views/17) * Handbook: [https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) 3. **Feedback Awaiting Validation:** 39 issues need validation. Please follow the ** Validating and Applying Content Feedback** handbook for step-by-step guidance. 4. * GitHub: [https://github.com/orgs/WordPress/projects/78/views/3](https://github.com/orgs/WordPress/projects/78/views/3) * Handbook: [https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) 5. **Topics Awaiting Vetting:** 2 issues are waiting for topic vetting. Please refer to the handbook for guidance on reviewing and vetting topic ideas. 6. * GitHub: [https://github.com/orgs/WordPress/projects/105/views/1](https://github.com/orgs/WordPress/projects/105/views/1) * Handbook: [https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) 7. **Validated Feedback Awaiting Fix:** 26 issues are awaiting fixes. Contributors can use the **Validating and Applying Content Feedback** handbook for guidance on applying validated feedback. 8. * GitHub: [https://github.com/orgs/WordPress/projects/78/views/4](https://github.com/orgs/WordPress/projects/78/views/4) * Handbook: [https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) ## Contribution Acknowledgement * **Badges awarded**: - No badges awarded this week * **GiveProps**: - [@sumitsingh](https://profiles.wordpress.org/sumitsingh/): Props to [@vasantrajput](https://profiles.wordpress.org/vasantrajput/) for hosting the first office hours and [@rfluethi](https://profiles.wordpress.org/rfluethi/) for always helping us - [@vasantrajput](https://profiles.wordpress.org/vasantrajput/): Props to [@rfluethi](https://profiles.wordpress.org/rfluethi/) for the perfect recap! You’ve covered everything that was explained and discussed during the Office Hours meeting. Really helpful and well summarised! - [@vasantrajput](https://profiles.wordpress.org/vasantrajput/): Props to [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) for the great idea of trying the next Office Hours on a weekday! And Also, kick-start TT-Admin as a monthly meeting to support and encourage admin contributions. ## Project updates * Thanks to our colleague [](https://github.com/Piyopiyo-Kitsune)[@Destiny](https://profiles.wordpress.org/destiny/), the course [_AI Literacy through WordPress_](https://learn.wordpress.org/course/ai-literacy-through-wordpress/) is now live on Learn WordPress! * Building on the momentum of our last learning cohort (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. Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem. ## Upcoming Online Workshops * N/A ## Contributor Updates * N/A ## Open Discussions * N/A * No new topics were raised. Team members are welcome to add any topics they would like to discuss in the comments. Thanks to everyone who participated in the sync and async, and to those who will contribute in future sessions. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. [#meeting-recap](https://make.wordpress.org/training/tag/meeting-recap/), [#training](https://make.wordpress.org/training/tag/training/), [#training-team](https://make.wordpress.org/training/tag/training-team/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F10%2F03%2Ftraining-team-meeting-recap-29th-september-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/sumitsingh/) [Sumit Singh](https://profiles.wordpress.org/sumitsingh/) 5:33 am _on_ September 29, 2026 Tags: [training ( 367 )](https://make.wordpress.org/training/tag/training/) # 󠀁[Meeting Agenda for September 29th, 2026](https://make.wordpress.org/training/2026/09/29/meeting-agenda-for-september-29th-2026/)󠁿 This week’s meeting will be held on Tuesday, September 29th, 2026, at [07:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?hour=07&min=00&sec=0). The meeting will be held on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), in the [#training](https://make.wordpress.org/training/tag/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](https://profiles.wordpress.org/sumitsingh/). ## 1. Intro/Welcome Welcome to all the new teammates who joined the Training Team this week! ## 2. News 1. [Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/) 2. * Sep 29th – [@pravin1996](https://profiles.wordpress.org/pravin1996/) * Oct 6th – [@makanikaran](https://profiles.wordpress.org/makanikaran/) * Oct 13th – [@alkesh7](https://profiles.wordpress.org/alkesh7/) * Oct 20th – [@softglaze](https://profiles.wordpress.org/softglaze/) 3. Looking for feedback 4. * Making team homepages could be more visually engaging and make it easier for newcomers to contribute, so I created 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: [https://playground.wordpress.net/?import-site=https://raw.githubusercontent.com/chekle/Make-Homepage/main/wordpress-playground-training.zip](https://playground.wordpress.net/?import-site=https://raw.githubusercontent.com/chekle/Make-Homepage/main/wordpress-playground-training.zip), We’d love your feedback on the overall ide. Thank you so much for sharing this new things@clk87. Here is 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/](https://github.com/) for share feedback – [https://github.com/WordPress/Learn/issues/3674](https://github.com/WordPress/Learn/issues/3674) * The next Office Hours will take place on a weekday as a trial; we will avoid Monday and Friday. The session will take place on a weekday as a trial, avoiding Monday and Friday. it will take place in the last week of October: Tuesday, October 27, Wednesday, October 28, or Thursday, October 29, 2026. [@sumit](https://github.com/sumit) will set the date and time after the proposal at the Tuesday meeting * We had a great conversation around exploring text-to-speech / read-aloud for course lesson content, and [@softglaze](https://profiles.wordpress.org/softglaze/) [has built some prototypes for us](https://github.com/WordPress/Learn/issues/3649). It would be great to get more feedback from Training Team members before we move to working 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 for implementation * We’re actively updating the Training Team handbooks, and there’s still time to contribute. If you have any suggestions, improvements, or ideas, please share them – we’d greatly appreciate your input:  [Update Handbook : “Handbook” #3447](https://github.com/WordPress/Learn/issues/3447). * Our colleague, [@mebo](https://profiles.wordpress.org/mebo/), revived the ** Learning Pathway Course: 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Developer** **Course** – [https://github.com/WordPress/Learn/issues/2044](https://github.com/WordPress/Learn/issues/2044). She started working on course modules and lessons, and we are waiting for your suggestions and opinions on the proposal she created – [Rendering plugin data #2182 (comment)](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201). Remember, GitHub activity is one of the easiest and most convenient ways to contribute. 5. Looking for volunteers 6. * Schedule the next Office Hours: weekday trial, date, moderator, and note-taker– https://github.com/WordPress/Learn/issues/3679 * Open source basics and WordPress; Quiz question answers for “What benefits can lead to a conflict of interest – https://github.com/WordPress/Learn/issues/ 3675 * We need your help in finding all the content that could be updated and consolidated. We would love to have two groups of volunteers – one that will go through all the handbook content, and one that will check the courses. Please state your interest, and we will help you organize and start working on these important issues. * Also, we started working on creating thumbnails for all lessons that need them. You’re very welcome to join us and contribute to this important and creative project. Here’s the issue with details on how to work on the remaining thumbnails: [https://github.com/WordPress/Learn/issues/3428](https://github.com/WordPress/Learn/issues/3428) * We currently have 586 open issues. It would be most effective to divide them into smaller categories and work through them one by one. - We can start with a label that is suitable for everyone to review. We suggest this simple workflow: * Going through issues one by one * Identifying outdated or irrelevant issues * Suggesting fixes or next steps * Adding comments where needed (before closing or updating) * We labeled some of the issues as **Good First Issues** – if you want to start contributing, this is your starting point. Just go and find issues labeled as [Good First Issue](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), particularly those that have Feedback in the issue title – help us verify them, and you will earn the Training Team Contributor badge in no time. Just follow this handbook article –[https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues) - For the upcoming sessions, we should divide the open issues into smaller groups and work through one categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. at a time. This should make the process more organised and easier for everyone to participate in. * We could begin with: **[Content] Needs Translation Reviewer** – [https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22)– Based on feedback from our last meeting, [@rfluethi](https://profiles.wordpress.org/rfluethi/) suggested starting with issues in the **Bug** category, as these are both the highest priority and likely the easiest to address. Please review the open tickets and share any feedback or suggestions you may have. - However, we would appreciate your suggestions on which category would be the easiest and most useful for everyone to start with. Other available categories include: * [Issues without a label](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel) * [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22) * [[Content] Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22) * [[Type] Bug](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) - Please share which category you think we should review first. Once selected, we can divide the issues and work through them together, one by one. - Let’s work together to clean up and keep the repository well-organized 7. Updates from last week’s Triage Squad session 8. * No triage squad meetings last week * We are planning to start, so if you are interested, comment here or join the [#Training team channel on WordPress Slack](https://wordpress.slack.com/archives/C02RW657Q) 9. Other announcements and news 10. * Writing a short description of the Office Hours format, review it together, and publish it – @sumitsinghwp (draft: [@rfluethi](https://profiles.wordpress.org/rfluethi/)) * We successfully hosted our Office Hours session on September 26, 2026 published– https://make.wordpress.org/training/2026/09/29/office-hours-meeting-recap-september- 26-2026/ – Thank you so much for the draft post, [@rfluethi](https://profiles.wordpress.org/rfluethi/) * Training Team Monthly update for August is published – [Training Team Update – September 7th, 2026](https://make.wordpress.org/updates/2026/09/07/training-team-update-september-7th-2026/) * How to Bring Your Community to Make WordPress Slack? [https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/) * Call for testing: WordPress community groups on events.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/](https://wordpress.org/) – [https://make.wordpress.org/meta/2026/08/28/call-for-testing-wordpress-community-groups-on-events-wordpress-org/](https://make.wordpress.org/meta/2026/08/28/call-for-testing-wordpress-community-groups-on-events-wordpress-org/) ## 2. Come and Contribute * [Content ready for review](https://github.com/orgs/WordPress/projects/33/views/17) - See [Guidelines for reviewing content](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) when reviewing content. * We have 9 issues ready for review * [[[Feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3) - See [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on validating feedback. * We have 39 issues that require validation * [Topics awaiting vetting](https://github.com/orgs/WordPress/projects/105/views/1) - See [Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/) for step-by-step guidance on vetting topic ideas. * We have 2 issues that require vetting * [Validated feedback awaiting fix](https://github.com/orgs/WordPress/projects/78/views/4) - Contributors, see [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on applying feedback that has been validated. * We have 26 issues awaiting a fix ## 3. Contribution Acknowledgement * Badges awarded: - No badges awarded this week ## 4. Project updates * Thanks to our colleague [@piyopiyofox](https://profiles.wordpress.org/piyopiyofox/), the course **_[AI Literacy through WordPress](https://learn.wordpress.org/course/ai-literacy-through-wordpress/)_** is now live on Learn WordPress! * Building on the momentum of our last learning cohort (Block Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem. ## 5. Upcoming Online Workshops * No workshop scheduled ## 6. 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? ## 7. Open Discussions If you have topics you’d like discussed in the meeting, please leave them as a comment on this post. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F09%2F29%2Fmeeting-agenda-for-september-29th-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/rfluethi/) [Rico F. Lüthi](https://profiles.wordpress.org/rfluethi/) 3:20 am _on_ September 29, 2026 Tags: [meeting recap ( 187 )](https://make.wordpress.org/training/tag/meeting-recap/), [training ( 367 )](https://make.wordpress.org/training/tag/training/)    # 󠀁[Office Hours Meeting Recap, September 26, 2026](https://make.wordpress.org/training/2026/09/29/office-hours-meeting-recap-september-26-2026/)󠁿 * **Date:** September 26, 2026 * **Time:** 14:00 UTC ([local time](https://www.timeanddate.com/worldclock/fixedtime.html?hour=14&min=00&sec=0)) * **Platform:** Zoom * **Issue:** [#3641](https://github.com/WordPress/Learn/issues/3641) * **Moderator:** Vasant ([@vasantrajput](https://profiles.wordpress.org/vasantrajput/)) * **Note-taker:** Rico ([@rfluethi](https://profiles.wordpress.org/rfluethi/)) **Related links:** * [Previous meeting (August 22, 2026)](https://make.wordpress.org/training/2026/08/24/office-hours-meeting-recap-august-22-2026/) * [Proposal: Monthly Office Hour Meeting](https://make.wordpress.org/training/2026/02/03/proposal-monthly-office-hour-meeting-for-make-wordpress-training/) * [Office Hours GitHub repository with detailed information](https://github.com/rfluethi/wpt-office-hours) * [Issue for the focus topic: formats, roles and responsibilities (#3644)](https://github.com/WordPress/Learn/issues/3644) * [Open issues from Office Hours](https://github.com/WordPress/Learn/issues?q=is%3Aissue+state%3Aopen+label%3A%22Office+Hours%22) Four contributors joined this session. Vasant moderated it for the first time, as decided on August 22. What worked and what will help the next sessions is described under **Lessons from the first run**. The items under **Decisions** were agreed in the meeting. The items under **Recommendations** were accepted by the attendees and go to the team reps for implementation. Items marked “as a proposal” still need the team’s confirmation. Please share feedback by the next weekly Tuesday meeting, as a comment on this post or in the [#training Slack channel](https://wordpress.slack.com/messages/training/). ## Participants | Name | 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/](https://wordpress.org/) profile | Location | | Pravin | [@pravin1996](https://profiles.wordpress.org/pravin1996/) | Ahmedabad, Gujarat, India | | Rico | [@rfluethi](https://profiles.wordpress.org/rfluethi/) | Switzerland | | Sumit | [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) | India | | Vasant | [@vasantrajput](https://profiles.wordpress.org/vasantrajput/) | Ahmedabad, India | Sumit had been largely unavailable in recent weeks because of a serious illness in his family and joined during the session. ## Context The focus topic was the purpose of each meeting format and how each one can create participation rather than mere attendance. The basis was a document by Vasant with seven proposals for the weekly Tuesday meeting, written from the observation that around 30 people regularly attend and only a few of them speak up. The attendees accepted the proposals. The second 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. covered the TT-Admins meeting, which has been announced for a long time and has not taken place. This is where the most concrete commitment of the session was made: a first monthly meeting, with invitations going out in the coming week. ## Lessons from the first run This was the first session run under the process agreed in August: moderator and note-taker had been assigned at the preceding meeting. Both held up, and two lessons from the session will help the next ones. Announcing the topic needs lead time. The topic was set, but the preparation only came together shortly before the session. People who know the topic early can plan time for it. The Monday reminder before each Office Hour, agreed in this session, addresses exactly this. Rotating the note-taker role needs a backup. The assigned person was unable to attend at short notice, and the notes were taken over during the session. To make this work without improvising, it helps to name a second person who can step in, and to ask for a short message when someone cannot make it. ## Topics ### Order and scope of the Tuesday meeting sections The sections where contributors actually write, Contributor Updates and Open Discussion, currently come last. Many people register their attendance and are no longer active by the end. Current order: 1. Intro and Welcome 2. News 3. Come and Contribute 4. Contribution Acknowledgement 5. Project Updates 6. Upcoming Online Workshops 7. Contributor Updates 8. Open Discussions Proposed order: 1. Intro and Welcome 2. Contributor Updates 3. Contribution Acknowledgement 4. Come and Contribute 5. Project Updates 6. News 7. Upcoming Online Workshops 8. Open Discussions In addition, sections with nothing to report in a given week should be left out, so the meeting gets shorter. ### Pair new contributors with an existing one New team members from the past week are welcomed by name, and an existing member is tagged to accompany them, for example with a request to find a first issue together. The goal is a first completed task in the first week. This does not replace the mentorship program; it comes before it. Based on the team’s experience, it takes one to two months from signing up for mentorship to being matched with a mentor. The accompanying person can later point the newcomer to the mentorship program. ### Shorten the News section Links should not be repeated for more than two to three weeks, and when there is no news, a short version is enough. The section is currently the longest one, with items that stay unchanged for four to six weeks. People who read the same item several times stop reading from that point on. ### Address issues and questions to named people In “Come and Contribute”, the moderator picks two to three issues and addresses each one to a specific person, with one issue left open to anyone. In Contributor Updates, two to three people who were active that week are asked directly about their progress and any blockers. A question to a named person gets answered; an open question to 30 people does not. One concern from the discussion affects implementation: for many issues it is not clear what needs to be done, and the rights to do it are often missing. The TT-Admins or the team reps resolve such obstacles. Anyone who takes on a task in the Tuesday meeting should therefore turn to the TT-Admins with questions. ### Contributor Spotlight and props The Contributor Updates section should be renamed “Contributor Spotlight”, so that visible work comes across as recognition. This is linked to an existing problem: props given in the Tuesday meeting do not automatically appear in the props channel, and only props from that channel show up on the WordPress.org profile. Anyone who wants the recognition on their profile currently has to ask for it. As a result, props get given twice, and the team’s own props lose their value. ### Open the Open Discussion with a real question Instead of the same questions every week, the section starts with a current decision the team needs input on. In most weeks, the section currently stays empty. A clarification from the discussion: the question is thought through in advance, including by the moderator, and then handed to another person who asks it. The moderator takes part in the discussion. This makes the format clearer, and everyone sees that anyone can ask questions or start a discussion. ### Publish the recap by Friday The guidance in the meeting script should change from “before the next meeting” to “by Friday”. Two reasons: news and workshops happening on the weekend are out of date once the recap appears on Sunday or Monday, and pushing the work to the weekend is the most common cause of delays. The effort does not stand in the way. For the Tuesday meeting, the text already exists in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), and there is a prepared template in the draft ticket where only the marked parts need to be replaced. With that, the recap takes about an hour and can be done on a weekday. ### TT-Admins meeting: tasks, format and access Three questions were on the table: Which recurring admin tasks exist, which of them have a clear process, and which can be handed over? Which format? How does someone become a TT-Admin? The recurring tasks are named: reviewing new issues 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/](https://github.com/) and setting their status, going through Help Scout feedback on existing content, creating issues from it and closing the tickets, and the meeting itself. On ownership, there was a clarification that goes beyond organization. The questions should be answered not by the team reps, but by the group that does the work. The team reps explain and support; if a process turns out not to work after six months, the group reorganizes itself. The group’s first goal is to reduce the number of open issues. On format: start monthly rather than every two weeks, and on Zoom rather than only in Slack, because commitment is higher. A format like this takes three to five months to become established and should run regularly even with few attendees. It was also suggested to hold a short admin meeting right before the weekly meeting to decide which five or so tickets to present there. A point about commitment belongs here too: anyone who takes on a task reports either that it is done or why it is not. Illness, lack of time and lack of knowledge are valid reasons; silence is not. If no update comes, the task goes to someone else. ### The Triage meeting The Triage meeting has been mentioned in the Tuesday meeting every week for years and does not take place; the last time it actually happened was many months ago. In substance, it is the same as the TT-Admins meeting. Either it takes place, or it should no longer be mentioned. ### Scoping the formats As long as it is unclear what the Tuesday meeting, the Office Hours, the TT-Admins meeting and the Coffee Hour are each for, low participation is understandable. The proposed split: the Office Hours are for the big, cross-cutting questions and the issues that come out of them. Following up on those issues and checking their progress belongs to the TT-Admins. The Coffee Hour is meant for newcomers with questions and is currently absorbed into the Office Hours. The sessions as well as the subgroups, such as the TT-Admins or the local Training Teams, need to be clearly defined in the handbook. This includes their tasks and goals, who belongs to them and who the contact person is. This has to happen soon: without a clear definition, the people behind these formats lose motivation and stop. In practice, a short description of the Office Hours is missing that can be shared with newcomers: what the format is, who can take part, that questions can also be asked about one’s own language, what happens when nobody in the room can help, who can moderate and how to get Zoom access. The full concept is in the [proposal](https://make.wordpress.org/training/2026/02/03/proposal-monthly-office-hour-meeting-for-make-wordpress-training/), and the detailed information is in the [Office Hours GitHub repository](https://github.com/rfluethi/wpt-office-hours); what is needed is a short version. A draft is now available in the [repository README](https://github.com/rfluethi/wpt-office-hours#what-are-the-office-hours) and will be reviewed together with Sumit. ### Announcing and scheduling the next Office Hours A short reminder in the [#training](https://make.wordpress.org/training/tag/training/) channel on the Monday before the session has been agreed, with date, time, Zoom link, moderator and topic. Before that comes the process already agreed in August: put three topics up for selection, fix the topic, add the guiding questions and remind people once more. New is a trial: the last weekend sessions had low attendance, so the next Office Hours will take place on a weekday as a trial. Monday and Friday will be avoided, because those are the busiest workdays. The known objection remains: during the day on weekdays most people are at work, and in the evening the time clashes with meetups. That is exactly why Saturday was chosen in the first place. Sumit will present the trial as a proposal at the next Tuesday meeting and then set the date and time, as well as the moderator and note-taker. October 21 or 22 and October 28 or 29 were mentioned. After the session, Sumit suggested the last week of October because of Navratri and Dussehra in India (October 11 to 20). This leaves Tuesday, October 27, Wednesday, October 28, and Thursday, October 29. ### Thumbnails as a starter task There is a list of around 120 to 130 lessons with a missing or outdated thumbnail, compiled from about 45 pages of the lesson overview. A first contributor is working through the list after watching the [Contributor Day tutorial on WordPress.tv](https://wordpress.tv/2026/06/12/training-team-wordcamp-europe-2026-contributor-day-online-how-to-generate-lessons-thumbnails/). The task is well suited for getting started: easy to explain, doable without prior knowledge and with a visible result. It will also be needed at the Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/) of 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](https://central.wordcamp.org/about/). Switzerland. Whether the Activity Kits also need thumbnails is still open. ### Multilingual support, lesson order and up-to-date lessons Work on multilingual support for the Learn website is ongoing. A related problem needs to be solved first: the order of the lessons is not right today, and the beginner course is missing Playground. As soon as lessons are inserted, the language versions drift apart in their order and the language connection no longer works. On top of that comes the known gap in keeping content current: most beginner lessons predate WordPress 6.9. In a test with beginners, almost every lesson required explaining four to five differences between the description and the actual interface. Beginners conclude that they did something wrong themselves. ### Keeping decisions visible A point that affects every format: decisions are recorded in the recap, and the recap reaches too few people. The decision to move away from long videos is the example; it has been settled for two sessions and has had no effect. There is no place where decisions are recorded and followed up. No proposal for this was made yet. ## Decisions | # | Decision | | 1 | The proposals for the Tuesday meeting from Vasant’s document are accepted. They go to the team reps with the request to implement them as soon as possible | | 2 | Sumit will invite all team reps and TT-Admins by email in the coming week to a monthly TT-Admins meeting; starting monthly, not every two weeks, on Zoom | | 3 | The next Office Hours will take place on a weekday as a trial; Monday and Friday will be avoided. The time is still open | | 4 | Sumit will present the trial as a proposal at the next Tuesday meeting and then set the date and time | | 5 | Sumit will assign the moderator and note-taker for the next session once the date is set. If nobody volunteers, he takes it on himself; if he is unavailable, Rico steps in | | 6 | Rico will provide a draft for a short description of the Office Hours format; Sumit will review it together with Rico and publish it, ideally before the next Tuesday meeting | | 7 | Before each Office Hours, a short reminder is posted in the [#training](https://make.wordpress.org/training/tag/training/) channel on Monday with date, time, Zoom link, moderator and topic | | 8 | Rico will write the recap of this session and share it with all attendees for review before publication | ## Recommendations | # | Recommendation | Consensus of attendees | | 1 | Change the section order of the Tuesday meeting: Contributor Updates and Contribution Acknowledgement to the front, News toward the end | Yes | | 2 | Leave out sections with nothing to report in a given week instead of keeping them empty | Yes | | 3 | Welcome new team members by name and tag an existing member to accompany them | Yes | | 4 | Do not repeat News items for more than two to three weeks | Yes | | 5 | In “Come and Contribute”, address two to three issues to named people and leave one open | Yes; unclear issues and missing rights are resolved by the TT-Admins or the team reps | | 6 | Rename Contributor Updates to “Contributor Spotlight” and address two to three active people directly | Yes | | 7 | Give props in the Tuesday meeting in a way that they appear on the WordPress.org profile without contributors having to ask for it | Yes, as a proposal | | 8 | Open the Open Discussion with a real, current question; someone other than the moderator asks it, and the moderator joins the discussion | Yes | | 9 | Change the recap deadline in the meeting script to Friday | Yes | | 10 | Hold a short TT-Admins meeting right before the weekly meeting and select the tickets for the Tuesday meeting there | Yes, as a proposal | | 11 | Create short tutorial videos for recurring admin tasks | Yes, as a proposal | ## Action Items | Issue | Task | Owner | Status | | [#3641](https://github.com/WordPress/Learn/issues/3641) | Run and document the September 26 Office Hours, publish the minutes | vasantrajput | open | | [#3644](https://github.com/WordPress/Learn/issues/3644) | Set up the TT-Admins meeting: invitation by email, monthly, on Zoom | sumitsinghwp | open | | [#3644](https://github.com/WordPress/Learn/issues/3644) | Write a short description of the Office Hours format, review it together and publish it | sumitsinghwp (draft: rfluethi) | draft available | | [#3644](https://github.com/WordPress/Learn/issues/3644) | Define the sessions and subgroups in the handbook: tasks, goals, members, contact person | sumitsinghwp | open | | [#3646](https://github.com/WordPress/Learn/issues/3646) | Change the recap deadline to Friday and link the existing template from the meeting script | vasantrajput | open | | [#3642](https://github.com/WordPress/Learn/issues/3642) | Clarify the lesson order before the language connection is rolled out | rjekic | open | | [#3676](https://github.com/WordPress/Learn/issues/3676) | Hand the accepted proposals to the team reps and revise the Tuesday meeting format | vasantrajput | new | | [#3677](https://github.com/WordPress/Learn/issues/3677) | Create missing and outdated lesson thumbnails | vasantrajput | new | | [#3678](https://github.com/WordPress/Learn/issues/3678) | Record and follow up on decisions | team-reps (@devmuhib009 [@rjekic](https://profiles.wordpress.org/rjekic/) @sumitsinghwp) | new | | [#3679](https://github.com/WordPress/Learn/issues/3679) | Present the weekday trial as a proposal at the Tuesday meeting and set the date | sumitsinghwp | new | | [#3679](https://github.com/WordPress/Learn/issues/3679) | Assign moderator and note-taker for the next Office Hours once the date is set | sumitsinghwp | new | ## Next meeting * **Date:** open. The session will take place on a weekday as a trial, avoiding Monday and Friday. Because of Navratri and Dussehra in India (October 11 to 20), it will take place in the last week of October: Tuesday, October 27, Wednesday, October 28, or Thursday, October 29, 2026. Sumit will set the date and time after the proposal at the Tuesday meeting * **Time:** open, to be set together with the date * **Moderator:** open, to be assigned by Sumit once the date is set * **Note-taker:** open, to be assigned by Sumit once the date is set **Focus topic:** open. Following the established process, the moderator will put three topics up for selection at the Tuesday meeting and then announce the chosen topic on Slack. [#meeting-recap](https://make.wordpress.org/training/tag/meeting-recap/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F09%2F29%2Foffice-hours-meeting-recap-september-26-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/gohelkunjan/) [Kunjan Gohel](https://profiles.wordpress.org/gohelkunjan/) 7:45 am _on_ September 27, 2026 Tags: [meeting recap ( 187 )](https://make.wordpress.org/training/tag/meeting-recap/), [training ( 367 )](https://make.wordpress.org/training/tag/training/), [Training-team ( 252 )](https://make.wordpress.org/training/tag/training-team/) # 󠀁[Training Team Meeting Recap – 22nd September 2026](https://make.wordpress.org/training/2026/09/27/training-team-meeting-recap-22nd-september-2026/)󠁿 This meeting followed this meeting agenda in [GitHub](https://github.com/WordPress/Learn/issues/3673) and [P2 Post](https://make.wordpress.org/training/2026/09/21/meeting-agenda-for-september-22nd-2026/). You can see conversations from the meeting in this [Slack Log](https://wordpress.slack.com/archives/C02RW657Q/p1790060429323609).( If you don’t have a SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) account, you can [set one up](https://make.wordpress.org/chat/).) ## **Introductions and Welcome** **There were 24 attendees:** [@pravin1996](https://profiles.wordpress.org/pravin1996/), [@sonaliprajapati](https://profiles.wordpress.org/sonaliprajapati/), [@alkesh7](https://profiles.wordpress.org/alkesh7/), [@gohelkunjan](https://profiles.wordpress.org/gohelkunjan/), [@Vishitshah](https://profiles.wordpress.org/vishitshah/), [@rfluethi](https://profiles.wordpress.org/rfluethi/), [@rjekic](https://profiles.wordpress.org/rjekic/), [@jenish1234](https://profiles.wordpress.org/jenish1234/), [@dilip2615](https://profiles.wordpress.org/dilip2615/), [@praful2111](https://profiles.wordpress.org/praful2111/), [@makanikaran](https://profiles.wordpress.org/makanikaran/), [@abduremon](https://profiles.wordpress.org/abduremon/), [@ishahinakhter](https://profiles.wordpress.org/ishahinakhter/), [@bigod](https://profiles.wordpress.org/bigod/), [@freewebmentor](https://profiles.wordpress.org/freewebmentor/), [@devmuhib](https://profiles.wordpress.org/devmuhib/), [@aqdesk](https://profiles.wordpress.org/aqdesk/), [@andrewssanya](https://profiles.wordpress.org/andrewssanya/), [@harshjadav003](https://profiles.wordpress.org/harshjadav003/)( async), [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) (async), [@valeriewandeler](https://profiles.wordpress.org/valeriewandeler/)( async), [@sibokul](https://profiles.wordpress.org/sibokul/) (async), [@ravigadhiyawp](https://profiles.wordpress.org/ravigadhiyawp/)( async), [@VasantRajput](https://profiles.wordpress.org/vasantrajput/) (async) **Newcomers:** [@thecmg](https://profiles.wordpress.org/thecmg/), [@som3669](https://profiles.wordpress.org/som3669/) **Meeting hosted by:** [@rjekic](https://profiles.wordpress.org/rjekic/) **Note Taker:** [@gohelkunjan](https://profiles.wordpress.org/gohelkunjan/) **Note Reviewer:** [@VasantRajput](https://profiles.wordpress.org/vasantrajput/) Welcome! Please post in the [#training](https://wordpress.slack.com/archives/C02RW657Q) channel or reach out to a team member to help you with contributing. Resources to check out [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/), and our [Guide Program](https://make.wordpress.org/training/handbook/guide-program/). ## News ### 󠀁[Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/)󠁿 Here is our current note taker roster: * 22nd September – [@gohelkunjan](https://profiles.wordpress.org/gohelkunjan/) * 29th September – [@pravin1996](https://profiles.wordpress.org/pravin1996/) * 6th October – [@makanikaran](https://profiles.wordpress.org/makanikaran/) * 13th October – [@alkesh7](https://profiles.wordpress.org/alkesh7/) **Important note**: If anyone needs more information on note-taking or a guide to creating a Recap Note Post, they can DM [Vasantsinh Rajput](https://wordpress.slack.com/team/U0818LF4W4X). He will guide you on a Recap Note, and he will review & publish your Recap Post. ### Looking for feedback * Our colleague [@clk87](https://profiles.wordpress.org/clk87/) [proposed Training team’s site homepage visual improvement](https://github.com/WordPress/Learn/issues/3674). Join us in discussion and let’s move this forward asap! * We had a great conversation around exploring text-to-speech / read-aloud for course lesson content, and [@softglaze](https://profiles.wordpress.org/softglaze/) [has built some prototypes for us](https://github.com/WordPress/Learn/issues/3649). It would be great to get more feedback from Training Team members before we move to working 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. for implementation * We have discussed starting a regular 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/](https://github.com/) triage meeting, and we will start from this week. - Proposed schedule: Triage Squad GitHub triage – biweekly on Thursdays at [07:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?hour=07&min=00&sec=0). - Please let us know if you would be interested in joining this Slack meeting if we decide to move forward with it. * We’re actively updating the Training Team handbooks, and there’s still time to contribute. If you have any suggestions, improvements, or ideas, please share them – we’d greatly appreciate your input: [Update Handbook : “Handbook” #3447](https://github.com/WordPress/Learn/issues/3447). * Our colleague, [@mebo](https://profiles.wordpress.org/mebo/), revived the [Learning Pathway Course: Intermediate Plugin Developer #2044](https://github.com/WordPress/Learn/issues/2044). She started working on course modules and lessons, and you can help her by suggesting and giving your opinion on newly created content – [Rendering plugin data #2182 (comment)](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201) ### Looking for volunteers * We need your help in finding all the content that could be updated and consolidated. We would love to have two groups of volunteers – one that will go through all the handbook content, and one that will check the courses. Please state your interest, and we will help you organise and start working on these important issues. * Also, we started working on creating thumbnails for all lessons that need them. You’re very welcome to join us and contribute to this important and creative project. Here’s the issue with details on how to work on the remaining thumbnails: [Create Thumbnails for Learn WordPress Lessons #3428](https://github.com/WordPress/Learn/issues/3428) * We currently have many issues open. It would be most effective to divide them into smaller categories and work through them one by one. - We can start with a label that is suitable for everyone to review. We suggest this simple workflow: * Going through issues one by one * Identifying outdated or irrelevant issues * Suggesting fixes or next steps * Adding comments where needed (before closing or updating) - We labelled some of the issues as Good First Issues – if you want to start contributing, this is your starting point. Just go and find issues labelled as [Good First Issue](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), particularly those that have Feedback in the issue title – help us verify them, and you will earn the Training Team Contributor badge in no time. Just [follow this handbook article.](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues) - For the upcoming sessions, we should divide the open issues into smaller groups and work through one categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. at a time. This should make the process more organised and easier for everyone to participate in. * We could begin with: [[Content] Needs Translation Reviewer](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22)–– Based on feedback from our last meeting, [@rfluethi](https://profiles.wordpress.org/rfluethi/) suggested starting with issues in the Bug category, as these are both the highest priority and likely the easiest to address. Please review the open tickets and share any feedback or suggestions you may have. * However, we would appreciate your suggestions on which category would be the easiest and most useful for everyone to start with. Other available categories include: - [Issues without a label](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel) - [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22) - [[Content] Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22) - [[Type] Bug](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) * Please share which category you think we should review first. Once selected, we can divide the issues and work through them together, one by one. - Let’s work together to clean up and keep the repository well-organised. ### Updates from last week’s Triage Squad session * N/A ### Office Hours session * We are also planning an Office Hours session on Saturday, September 26, 2026: - Topic: [Run and document Office Hours on September 26, 2026 #3641](https://github.com/WordPress/Learn/issues/3641) * Moderation: [@vasantrajput](https://profiles.wordpress.org/vasantrajput/) * Minute-taking: [@andrewssanya](https://profiles.wordpress.org/andrewssanya/) - Please join the discussion and help us make Training Team Office Hours better! ### Other News * Training Team Monthly update for August is published – [Training Team Update – September 7th, 2026](https://make.wordpress.org/updates/2026/09/07/training-team-update-september-7th-2026/) * **The Learn WordPress DACH team** finished its **first German-language course cohort, “Starten mit WordPress”** – seven weeks, seven live sessions, always two facilitators, a prepared curriculum for every single session, and answers in Slack in between. In the final session, every participant presented a website they had built themselves. Wonderful commitment, and **a great model from which all of us can learn**. Thank you! * [How to Bring Your Community to Make WordPress Slack?](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/) * [Call for testing: WordPress community groups on events.WordPress.org](https://make.wordpress.org/meta/2026/08/28/call-for-testing-wordpress-community-groups-on-events-wordpress-org/) ## Come and Contribute ### This week’s contribution focus area * [Content ready for review](https://github.com/orgs/WordPress/projects/33/views/17) - See [Guidelines for reviewing content](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) when reviewing content. - We have 9 issues ready for review * [Feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3) - See [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on validating feedback. - We have 38 issues that require validation * [Topics awaiting vetting](https://github.com/orgs/WordPress/projects/105/views/1) - See [Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/) for step-by-step guidance on vetting topic ideas. - We have 2 issues that require vetting * [Validated feedback awaiting fix](https://github.com/orgs/WordPress/projects/78/views/4) - Contributors, see [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on applying feedback that has been validated. - We have 25 issues awaiting a fix ## Contribution Acknowledgement * **Badges awarded**:  - No badges awarded this week * **Give** **Props**: - [@devmuhib](https://profiles.wordpress.org/devmuhib/): Props to [@rjekic](https://profiles.wordpress.org/rjekic/) and [@sumitsingh](https://profiles.wordpress.org/sumitsingh/) for taking care of the training team and helping all team members. ## Project updates * Thanks to our colleague [](https://github.com/Piyopiyo-Kitsune)[@Destiny](https://profiles.wordpress.org/destiny/), the course [_AI Literacy through WordPress_](https://learn.wordpress.org/course/ai-literacy-through-wordpress/) is now live on Learn WordPress! * Building on the momentum of our last learning cohort (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. Theme Development Course cohort), we are excited to launch our next cohort focused on 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem. ## Upcoming Online Workshops * No workshop scheduled ## 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 issue. * Looks like we don’t have anything at the moment. If anyone has anything async. Please reply in this thread and we can keep the discussion going. And that concludes this week’s meeting. Thanks to all who participated in sync and to those that will in the future. * We’ll see you all next week! * Currently, no new topics have been raised, but asynchronous contributions are welcome via the [Slack thread](https://wordpress.slack.com/archives/C02RW657Q/p1790062807795409) to continue the discussion. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. [#meeting-recap](https://make.wordpress.org/training/tag/meeting-recap/), [#training](https://make.wordpress.org/training/tag/training/), [#training-team](https://make.wordpress.org/training/tag/training-team/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F09%2F27%2Ftraining-team-meeting-recap-22nd-september-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/rjekic/) [Rade Jekić](https://profiles.wordpress.org/rjekic/) 6:17 pm _on_ September 21, 2026 Tags: [training ( 367 )](https://make.wordpress.org/training/tag/training/) # 󠀁[Meeting Agenda for September 22nd, 2026](https://make.wordpress.org/training/2026/09/21/meeting-agenda-for-september-22nd-2026/)󠁿 This week’s meeting will be held on Tuesday, September 15th, 2026, at [07:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?hour=07&min=00&sec=0). The meeting will be held on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), in the [#training](https://make.wordpress.org/training/tag/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 [@rjekic](https://profiles.wordpress.org/rjekic/). ## 1. Intro/Welcome Welcome to all the new teammates who joined the Training Team this week! ## 2. News 1. [Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/) 2. * Sep 22nd – @gohelkunjan * Sep 29th – @pravin1996 * Oct 6th – [@makanikaran](https://profiles.wordpress.org/makanikaran/) * Oct 13th – [@alkesh7](https://profiles.wordpress.org/alkesh7/) 3. Looking for feedback 4. * We had a great conversation around exploring text-to-speech / read-aloud for course lesson content, and [@softglaze](https://profiles.wordpress.org/softglaze/) [has built some prototypes for us](https://github.com/WordPress/Learn/issues/3649). It would be great to get more feedback from Training Team members before we move to working 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 for implementation * We are planning an Office Hours session on Saturday, September 26, 2026: - **Topic**: [Run and document Office Hours on September 26, 2026 #3641](https://github.com/WordPress/Learn/issues/3641) * We have discussed starting a regular 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/](https://github.com/) triage meeting. - **Proposed schedule:** Triage Squad GitHub triage – biweekly on Thursdays at 07:00 UTC. - Please let us know if you would be interested to join this Slack meeting. * We’re actively updating the Training Team handbooks, and there’s still time to contribute. If you have any suggestions, improvements, or ideas, please share them – we’d greatly appreciate your input:  [Update Handbook : “Handbook” #3447](https://github.com/WordPress/Learn/issues/3447). * Our colleague, [@mebo](https://profiles.wordpress.org/mebo/), revived the ** Learning Pathway Course: 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Developer** **Course** – [https://github.com/WordPress/Learn/issues/2044](https://github.com/WordPress/Learn/issues/2044). She started working on course modules and lessons, and we are waiting for your suggestions and opinions on the proposal she created – [Rendering plugin data #2182 (comment)](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201). Remember, GitHub activity is one of the easiest and most convenient ways to contribute. 5. Looking for volunteers 6. * We need your help in finding all the content that could be updated and consolidated. We would love to have two groups of volunteers – one that will go through all the handbook content, and one that will check the courses. Please state your interest, and we will help you organize and start working on these important issues. * Also, we started working on creating thumbnails for all lessons that need them. You’re very welcome to join us and contribute to this important and creative project. Here’s the issue with details on how to work on the remaining thumbnails: [https://github.com/WordPress/Learn/issues/3428](https://github.com/WordPress/Learn/issues/3428) * We currently have 586 open issues. It would be most effective to divide them into smaller categories and work through them one by one. - We can start with a label that is suitable for everyone to review. We suggest this simple workflow: * Going through issues one by one * Identifying outdated or irrelevant issues * Suggesting fixes or next steps * Adding comments where needed (before closing or updating) * We labeled some of the issues as **Good First Issues** – if you want to start contributing, this is your starting point. Just go and find issues labeled as [Good First Issue](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), particularly those that have Feedback in the issue title – help us verify them, and you will earn the Training Team Contributor badge in no time. Just follow this handbook article –[https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues) - For the upcoming sessions, we should divide the open issues into smaller groups and work through one categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. at a time. This should make the process more organised and easier for everyone to participate in. * We could begin with: **[Content] Needs Translation Reviewer** – [https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22)– Based on feedback from our last meeting, [@rfluethi](https://profiles.wordpress.org/rfluethi/) suggested starting with issues in the **Bug** category, as these are both the highest priority and likely the easiest to address. Please review the open tickets and share any feedback or suggestions you may have. - However, we would appreciate your suggestions on which category would be the easiest and most useful for everyone to start with. Other available categories include: * [Issues without a label](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel) * [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22) * [[Content] Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22) * [[Type] Bug](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) - Please share which category you think we should review first. Once selected, we can divide the issues and work through them together, one by one. - Let’s work together to clean up and keep the repository well-organized 7. Updates from last week’s Triage Squad session 8. * No triage squad meetings last week * We are planning to start, so if you are interested, comment here or join the [#Training team channel on WordPress Slack](https://wordpress.slack.com/archives/C02RW657Q) 9. Other announcements and news 10. * Training Team Monthly update for August is published – [Training Team Update – September 7th, 2026](https://make.wordpress.org/updates/2026/09/07/training-team-update-september-7th-2026/) * **The Learn WordPress DACH team** finished its **first German-language course cohort, “Starten mit WordPress” **– seven weeks, seven live sessions, always two facilitators, a prepared curriculum for every single session, and answers in Slack in between. In the final session, every participant presented a website they had built themselves. Wonderful commitment, and a great model from which all of us can learn. Thank you! * How to Bring Your Community to Make WordPress Slack? [https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/) * Call for testing: WordPress community groups on events.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/](https://wordpress.org/) – [https://make.wordpress.org/meta/2026/08/28/call-for-testing-wordpress-community-groups-on-events-wordpress-org/](https://make.wordpress.org/meta/2026/08/28/call-for-testing-wordpress-community-groups-on-events-wordpress-org/) ## 2. Come and Contribute * [Content ready for review](https://github.com/orgs/WordPress/projects/33/views/17) - See [Guidelines for reviewing content](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) when reviewing content. * We have 9 issues ready for review * [[[Feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3) - See [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on validating feedback. * We have 38 issues that require validation * [Topics awaiting vetting](https://github.com/orgs/WordPress/projects/105/views/1) - See [Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/) for step-by-step guidance on vetting topic ideas. * We have 2 issues that require vetting * [Validated feedback awaiting fix](https://github.com/orgs/WordPress/projects/78/views/4) - Contributors, see [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on applying feedback that has been validated. * We have 25 issues awaiting a fix ## 3. Contribution Acknowledgement * Badges awarded: - No badges awarded this week ## 4. Project updates * Thanks to our colleague @Piyopiyo-Kitsune, the course **_[AI Literacy through WordPress](https://learn.wordpress.org/course/ai-literacy-through-wordpress/)_** is now live on Learn WordPress! * Building on the momentum of our last learning cohort (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. Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem. ## 5. Upcoming Online Workshops * No workshop scheduled ## 6. 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? ## 7. Open Discussions If you have topics you’d like discussed in the meeting, please leave them as a comment on this post. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F09%2F21%2Fmeeting-agenda-for-september-22nd-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/vasantrajput/) [Vasantsinh Rajput](https://profiles.wordpress.org/vasantrajput/) 7:23 am _on_ September 21, 2026 Tags: [meeting recap ( 187 )](https://make.wordpress.org/training/tag/meeting-recap/), [training ( 367 )](https://make.wordpress.org/training/tag/training/), [Training-team ( 252 )](https://make.wordpress.org/training/tag/training-team/) # 󠀁[Training Team Meeting Recap – 15th September 2026](https://make.wordpress.org/training/2026/09/21/training-team-meeting-recap-15th-september-2026/)󠁿 This meeting followed this meeting agenda in [GitHub ](https://github.com/WordPress/Learn/issues/3670) and [P2 Post](https://make.wordpress.org/training/2026/09/14/meeting-agenda-for-september-15th-2026/). You can see conversations from the meeting in this [Slack Log ](https://wordpress.slack.com/archives/C02RW657Q/p1789455681128599).( If you don’t have a SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) account, you can [set one up](https://make.wordpress.org/chat/).) ## **Introductions and Welcome** **There were 30 attendees:** [@pravin1996](https://profiles.wordpress.org/pravin1996/), [@jenish1234](https://profiles.wordpress.org/jenish1234/), [@sonaliprajapati](https://profiles.wordpress.org/sonaliprajapati/), [@csheba](https://profiles.wordpress.org/csheba/), [@sagarmodi1700](https://profiles.wordpress.org/sagarmodi1700/), [@rjekic](https://profiles.wordpress.org/rjekic/), [@shivashankerbhatta](https://profiles.wordpress.org/shivashankerbhatta/), [@syrah44](https://profiles.wordpress.org/syrah44/), [@praful2111](https://profiles.wordpress.org/praful2111/), [@rfluethi](https://profiles.wordpress.org/rfluethi/), [@ishahinakhter](https://profiles.wordpress.org/ishahinakhter/), [@sumitjavia](https://profiles.wordpress.org/sumitjavia/), [@harshjadav003](https://profiles.wordpress.org/harshjadav003/), [@andrewssanya](https://profiles.wordpress.org/andrewssanya/), [@makanikaran](https://profiles.wordpress.org/makanikaran/), [@dilip2615](https://profiles.wordpress.org/dilip2615/), [@rithika3](https://profiles.wordpress.org/rithika3/), [@alkesh7](https://profiles.wordpress.org/alkesh7/), [@gohelkunjan](https://profiles.wordpress.org/gohelkunjan/), [@freewebmentor](https://profiles.wordpress.org/freewebmentor/) (async), [@softglaze](https://profiles.wordpress.org/softglaze/)( async), [@sibokul](https://profiles.wordpress.org/sibokul/) (async), [@valeriewandeler](https://profiles.wordpress.org/valeriewandeler/)( async), [@priyankaadbrains](https://profiles.wordpress.org/priyankaadbrains/) (async), [@bhavesh456](https://profiles.wordpress.org/bhavesh456/) (async), [@ranupatel11](https://profiles.wordpress.org/ranupatel11/)( async), [@jagirbahesh](https://profiles.wordpress.org/jagirbahesh/) (async), [@VasantRajput](https://profiles.wordpress.org/vasantrajput/)( async), [@ursha](https://profiles.wordpress.org/ursha/) (async), [@vishitshah](https://profiles.wordpress.org/vishitshah/)( async) **Newcomers:** [@sagarmodi1700](https://profiles.wordpress.org/sagarmodi1700/), [@obaid2013](https://profiles.wordpress.org/obaid2013/) **Meeting hosted by:** [@SumitSingh](https://profiles.wordpress.org/sumitsingh/) **Note Taker:** [@VasantRajput](https://profiles.wordpress.org/vasantrajput/) **Note Reviewer:** [@VasantRajput](https://profiles.wordpress.org/vasantrajput/) Welcome! Please post in the [#training](https://wordpress.slack.com/archives/C02RW657Q) channel or reach out to a team member to help you with contributing. Resources to check out [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/), and our [Guide Program](https://make.wordpress.org/training/handbook/guide-program/). ## News ### 󠀁[Meeting Note Takers](https://make.wordpress.org/training/handbook/about/team-roles/)󠁿 Here is our current note taker roster: * 15th September – [@VasantRajput](https://profiles.wordpress.org/vasantrajput/) * 22nd September – [@gohelkunjan](https://profiles.wordpress.org/gohelkunjan/) * 29th September – [@pravin1996](https://profiles.wordpress.org/pravin1996/) * 6th October – [@makanikaran](https://profiles.wordpress.org/makanikaran/) **Important note**: If anyone needs to know more about note-taking and needs guidance in creating a Recap Note Post, they can [DM ](https://wordpress.slack.com/team/U0818LF4W4X) [@VasantRajput](https://profiles.wordpress.org/vasantrajput/). He will guide you for a Recap Note and he will review & publish your Recap Post. ### Looking for feedback * Error in video and content in lesson “Dimensions: Padding, margin and blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. spacing”– [https://github.com/WordPress/Learn/issues/3647](https://github.com/WordPress/Learn/issues/3647) * Proposing content update in lesson “Helping Students Get Started” – [https://github.com/WordPress/Learn/issues/3548](https://github.com/WordPress/Learn/issues/3548) * Wording of the quiz question in lesson “Managing spam on your site” – [https://github.com/WordPress/Learn/issues/3544](https://github.com/WordPress/Learn/issues/3544) * Outdated content in lesson “Retrieving WordPress data records” – [https://github.com/WordPress/Learn/issues/3546](https://github.com/WordPress/Learn/issues/3546) * Outdated content in course “Creating a 4-page business website” – https://github. com/WordPress/Learn/issues/3528 * We had a great conversation around exploring text-to-speech / read-aloud for course lesson content, and [@softglaze](https://profiles.wordpress.org/softglaze/) [has built some prototypes for us](https://github.com/WordPress/Learn/issues/3649). It would be great to get more feedback from Training Team members before we move to working 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. for implementation * We are planning an Office Hours session on Saturday, September 26, 2026: - **Topic**: Run and document Office Hours for September 26, 2026: [Run and document Office Hours on September 26, 2026 #3641](https://github.com/WordPress/Learn/issues/3641) * We have discussed starting a regular 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/](https://github.com/) triage meeting. - Proposed schedule: Triage Squad GitHub triage – biweekly on Thursdays at 07: 00 UTC. - Please let us know if you would be interested in joining this Slack meeting if we decide to move forward with it. * We’re actively updating the Training Team handbooks, and there’s still time to contribute. If you have any suggestions, improvements, or ideas, please share them – we’d greatly appreciate your input:  [Update Handbook : “Handbook” #3447](https://github.com/WordPress/Learn/issues/3447). * Our colleague, [@mebo](https://profiles.wordpress.org/mebo/), revived the **Learning Pathway Course: 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Developer** **Course** – [https://github.com/WordPress/Learn/issues/2044](https://github.com/WordPress/Learn/issues/2044). She started working on course modules and lessons, and we are waiting for your suggestions and opinions on the proposal she created – [Rendering plugin data #2182 (comment)](https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201). Remember, GitHub activity is one of the easiest and most convenient ways to contribute. ### Looking for volunteers * Needs Translation Reviewer for Lesson – [Check All issues](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22) * We need your help in finding all the content that could be updated and consolidated. We would love to have two groups of volunteers – one that will go through all the handbook content, and one that will check the courses. Please state your interest, and we will help you organize and start working on these important issues. * Also, we started working on creating thumbnails for all lessons that need them. You’re very welcome to join us and contribute to this important and creative project. Here’s the issue with details on how to work on the remaining thumbnails: [https://github.com/WordPress/Learn/issues/3428](https://github.com/WordPress/Learn/issues/3428) * We currently have 590 open issues. It would be most effective to divide them into smaller categories and work through them one by one. - We can start with a label that is suitable for everyone to review. We suggest this simple workflow: * Going through issues one by one * Identifying outdated or irrelevant issues * Suggesting fixes or next steps * Adding comments where needed (before closing or updating) * We labeled some of the issues as **Good First Issues** – if you want to start contributing, this is your starting point. Just go and find issues labeled as [Good First Issue](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Good%20First%20Issue%22), particularly those that have Feedback in the issue title – help us verify them, and you will earn the Training Team Contributor badge in no time. Just follow this handbook article – [Open handbook article](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues) - For the upcoming sessions, we should divide the open issues into smaller groups and work through one categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. at a time. This should make the process more organised and easier for everyone to participate in. * We could begin with: **[Content] [Needs Translation Reviewer](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22)**– Based on feedback from our last meeting, [@rfluethi](https://profiles.wordpress.org/rfluethi/) suggested starting with issues in the **Bug** category, as these are both the highest priority and likely the easiest to address. Please review the open tickets and share any feedback or suggestions you may have. - However, we would appreciate your suggestions on which category would be the easiest and most useful for everyone to start with. Other available categories include: * [Issues without a label](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20no%3Alabel) * [Awaiting Triage](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Awaiting%20Triage%22) * [[Content] Feedback](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Feedback%22) * [[Type] Bug](https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BType%5D%20Bug%22) - Please share which category you think we should review first. Once selected, we can divide the issues and work through them together, one by one. - Let’s work together to clean up and keep the repository well-organized ### Updates from last week’s Triage Squad session * N/A ### Other News * Training Team Monthly update for August is published – [Training Team Update – September 7th, 2026](https://make.wordpress.org/updates/2026/09/07/training-team-update-september-7th-2026/) * How to Bring Your Community to Make WordPress Slack? [https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/](https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/) * Call for testing: WordPress community groups on events.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/](https://wordpress.org/) – [https://make.wordpress.org/meta/2026/08/28/call-for-testing-wordpress-community-groups-on-events-wordpress-org/](https://make.wordpress.org/meta/2026/08/28/call-for-testing-wordpress-community-groups-on-events-wordpress-org/) ## Come and Contribute ### This week’s contribution focus area * [Content ready for review](https://github.com/orgs/WordPress/projects/33/views/17) - See [Guidelines for reviewing content](https://make.wordpress.org/training/handbook/training-team-how-to-guides/guidelines-for-reviewing-content-on-learn/) when reviewing content. - We have [10] issues ready for review * [Feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3) - See [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on validating feedback. - We have [37] issues that require validation * [Topics awaiting vetting](https://github.com/orgs/WordPress/projects/105/views/1) - See [Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/) for step-by-step guidance on vetting topic ideas. - We have [2] issues that require vetting * [Validated feedback awaiting fix](https://github.com/orgs/WordPress/projects/78/views/4) - Contributors, see [Validating and Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/) for step-by-step guidance on applying feedback that has been validated. - We have [26] issues awaiting a fix ## Contribution Acknowledgement * **Badges awarded**:  - N/A * **Give** **Props**: - [@rfluethi](https://profiles.wordpress.org/rfluethi/): Props to [@bigod](https://profiles.wordpress.org/bigod/), [@tikolan](https://profiles.wordpress.org/tikolan/), [@zittau](https://profiles.wordpress.org/zittau/), [@ursha](https://profiles.wordpress.org/ursha/), [@valeriewandeler](https://profiles.wordpress.org/valeriewandeler/) for facilitating the Training Team DACH’s first guided learning cohort, “Starten mit WordPress.” Seven weeks, seven live sessions, always two facilitators, a prepared curriculum for every single session and answers in Slack in between. In the final session, every participant presented a website they had built themselves. Wonderful commitment. Thank you! - [@softglaze](https://profiles.wordpress.org/softglaze/): Props to [@SumitSingh](https://profiles.wordpress.org/sumitsingh/) for hosting this meeting - [@VasantRajput](https://profiles.wordpress.org/vasantrajput/): Props to [@priyankaadbrains](https://profiles.wordpress.org/priyankaadbrains/) for finishing her first Meeting Recap, even while she were busy with the Campus Connect event. Really appreciate your effort and commitment! - [@priyankaadbrains](https://profiles.wordpress.org/priyankaadbrains/): Props to [@dilip2615](https://profiles.wordpress.org/dilip2615/) for guiding me while preparing Meeting Recap Note. ## Project updates * From July 28 to September 8, the Training Team DACH (Germany, Austria, Switzerland) ran its first guided learning cohort, “Starten mit WordPress” (Getting Started with WordPress). It was based on the Learn WordPress course “Beginner WordPress User.” Participants worked through the lessons on their own. After a kickoff session, they met live on Zoom for seven weekly sessions of 90 minutes each. Between sessions, the group stayed in touch on Slack.By the numbersWe deliberately scheduled this first cohort during the summer break because we wanted to test the concept with a small group first. - 6 people signed up and 4 completed. The other two paused and would like to rejoin in the next cohort. - All four completed the Learn WordPress course and presented their own website in the final session. - Six facilitators from our team led the sessions, always in pairs. * What we learned - The live sessions were the biggest strength. Participants mainly asked for more time for their own questions and their own websites. - We had too much content for 90 minutes, so hands-on practice fell short. For the next cohort, we will use a flipped classroom approach: participants complete the lessons before each session, and the session focuses on their questions and on working on their own websites. - Terminology is a hurdle. The lessons use terms like “patterns” and “templates,” while the German version of the WordPress interface translates several of these as “Vorlage.” We are creating a glossary to help with this. * If there is interest, we are happy to share a detailed report once our evaluation is complete. Just let us know, especially if you are planning something similar. - Building on the momentum of our last learning cohort (Block Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem. ## Upcoming Online Workshops * N/A ## 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 issue. * What’s your plan in 2026 related to WordPress? * Currently, no new topics have been raised, but asynchronous contributions are welcome via the [Slack thread](https://wordpress.slack.com/archives/C02RW657Q/p1789457707292689) to continue the discussion. --- You can see all meetings scheduled on [this meeting calendar](https://make.wordpress.org/meetings/#training). If you are new to the Training Team, then come walk through [our onboarding program](https://make.wordpress.org/training/handbook/getting-started/) 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](https://wordpress.slack.com/archives/C02RW657Q) at any time. [#meeting-recap](https://make.wordpress.org/training/tag/meeting-recap/), [#training](https://make.wordpress.org/training/tag/training/), [#training-team](https://make.wordpress.org/training/tag/training-team/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F09%2F21%2Ftraining-team-meeting-recap-15th-september-2026%2F%23respond&locale=en_US) ## Post navigation [← Older posts](https://make.wordpress.org/training/page/2/?output_format=md)