Training Team Meeting Recap – 18th April 2024

This meeting followed this meeting agenda in GitHub. You can see conversations from the meeting in this Slack Log. (If you don’t have a SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at account, you can set one up.)

Introductions and Welcome

There were 21 attendees @piyopiyofox, @westnz, @lada7042, @pooja9712, @voboghure (async), @devmuhib (async), @onealtr (async), @mebo (async), @jhimross (async), @sumitsingh (async), @psykro (async), @cnormandigital (async), @freewebmentor (async), @jagirbahesh (async), @zeelthakkar (async), @amitpatelmd (async), @manukk (async), @bsanevans (async), @leogopal (async), @backpocketace (async), @eboxnet (async)

Welcome all the new contributors who joined the Training Team’s Slack channel in the last week:

@arjunhadke96, @tejaskhatri, @oguzakankan, @ahsan03, @miteshru, @mmuhsin

For those who are new here, the WordPress Training Team helps people learn to use, extend, and contribute to WordPress through educational content hosted on

If you haven’t seen them yet, then I recommend checking out our onboarding program, and our Guide Program


Meeting Note Takers

Meeting recap notes are one of the best ways to get started contributing to a team, and you can find details on how to write notes in this handbook page.

Looking for feedback

Looking for feedback: Thumbnails for the Learn redesign – Please take a moment to generate thumbnails using the provided template and provide your feedback in the comments by April 19th (tomorrow!).

@bsanevans proposes setting up a workflow so that content creators would type //published to close a published issue, rather than press close. The workflow could do the following:

  • Add a new [Content] Published label
  • Remove [Content] Needs Co-host label (← this has been an outstanding request)
  • Close issue

With this new workflow, we’d then be able to filterFilter Filters are one of the two types of Hooks They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. out issues with the new [Content] Published label as those that were actually completed.

The proposal has been met with positive feedback from the team. Here are the key points of discussion:

  • @lada7042: Questioned if the co-host label would be lost entirely. She likes the idea of using a keyword to close the issue.
  • @westnz and @devmuhib: Found the proposal helpful.
  • @leogopal: Mentioned that he is working on a similar workflow automation for the Community Team, suggesting a collaboration.
  • @psykro: Liked the idea for its simplicity and suggested a shorter keyword, “//publish”, to align with WordPress terminology.
  • @bsanevans: Clarified that the automation would remove the “[Content] Needs Co-host” label only if it should have been removed already. He agreed with using “//publish” as the keyword.

The implementation is scheduled for the first week of May, with @bsanevans and @leogopal agreeing to collaborate on it. The script has been completed and is ready for testing in the Community Team’s GitHub repository.

Looking for volunteers

We need help with reviewing lessons. If you know anyone who might want to contribute. Reviewer application Let us know.

Updates from last week’s dev-squad triage session

Attendees: @devmuhib, @huzaifaalmesbah, @mebo

  • Worked with 4 PR.
  • Triaged 3 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 be the repository owner. issues.

The team would also like to discuss about this issue related to accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( Need insights from other team members that will help to increase accessibility of Learn WordPress website.

@psykro suggests making content creators aware of using the aria-label attribute values of user interface elements when referring to them. For instance, instead of describing a button as “the icon with the SIX dots,” it should be referred to as the “Options” button, which is its aria-label attribute value. He proposes adding this information to the Lesson creation guidelines, possibly in a section dedicated to Accessibility tips. @psykro has self-assigned the task of updating the quizzes in the course to reflect this guideline for the upcoming week.

Other news

WordCamp US speaker applications are now open

We are here to help folks Speak at a WordCamp or Meetup About the Training Team and Learn WordPress! Reach out if you’re looking for assistance.

For members who identify as being part of the Black diaspora, I’d also like to share this resource from BlackPress If you have been approved to be a speaker and need financial assistance you could apply at Support Inclusion in Tech

Come and Contribute

This week we’d love the team to focus on Content ready for review

 Feedback awaiting validation

Topics awaiting vetting

  • See Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.
    • We have 31 issue that requires vetting

Good first issues for developers

  • See Developing Learn WordPress for instructions on contributing to the Learn WordPress code.
    • We have 15 issues that need a look

Validated feedback awaiting fix

Contributor Acknowledgement

Props: Does anyone have some props to share with a teammate this week?

Props to @lada7042 for completing and adding a new lesson about Global Styles to the Intermediate user learning pathway.

Project updates

Open Discussion

Ooop– faculty updates happened last week

Does anyone have an open discussion topic they’d like to bring to the team?

@gusa replied: I’d like to reference this panel discussion @bsanevans will be part of tomorrow along with the agenda for the next Mentorship chat (also tomorrow).

Seems like the latter could provide an entry point for collaboration across teams and working groups on overlapping projects/programs like extending the Mentorship program, Five for the Future, and events like do_action by incorporating training and learning resources (see this issue/comment for examples).

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