Training Team Meeting Recap – 10th October 2023

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,  @sumitsingh,  @webtechpooja,  @chetan200891,  @nahidsharifkomol,  @devmuhib,  @iqbalpb,  @jdy68,  @psykro,  @sancastiza,  @nayanchamp7,  @karthickmurugan,  @huzaifaalmesbah(async),  @lada7042(async),  @sierratr(async),  @west7(async),  @courtneypk(async),  @benjirahmed(async),  @quitevisible(async),  @mebo(async),  @vanpariyar(async)

We’ve had several new people join the channel recently. Let’s get introduced to 7 new people here: @Stuti Goyal @Vincent Martinat @Lisa Sabin-Wilson @zstepek @Nabin @Parag Wadhwani @Rashi Gupta  


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.

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 on this handbook page.

Looking for feedback

Updates from last week’s dev-squad triage session

This week, the dev-squad triaged 2 new PRs and one new bug:

There was some discussion around #1880, which the dev squad would like to bring to the team.

Other News

Please see the Nomination for Training Team Reps 2023 post for details on how we handled nominating new team reps last year. We are hoping to make this process more clear for future reps and potential leaders.

  • Badges Rewarded  – Congrats @Muhibul Haque! Thank you for your contributions to the team.

Open requests for review

See our Guidelines for reviewing content to review the following content.


Translated Content

If you are able to pick any of these reviews up, please comment on the issue directly.

Project Updates

Open Discussions

The discussion topic at hand revolves around GitHub issue #1880, which involves adding IDs to headings for anchor links on the website. The dev squad is seeking clarity on whether to use sentence case or all lowercase for internal anchor link fragments. The HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. spec doesn’t specify a requirement, but lowercase is the common practice.

The dilemma is whether to formalize and document this practice across the site. @Jonathan suggests switching to all lowercase, but this would require a thorough review and update of existing lesson plans. The group is open to discussion on this matter.

@Destiny raises whether this issue will still be relevant if the content is consolidated according to the new information architecture for Learn. @Jonathan mentions that it depends on whether the “Tip” section in the Lesson Plan synced pattern is carried over to the new content types. Removing the tip section entirely is a possible solution.

The group agrees that the new architecture may change the current situation, so they consider merging the PR and addressing individual lesson plans on a case-by-case basis.

Asynchronous participants are encouraged to share their thoughts on the GitHub issue. @Jonathan notes that it’s essential to consider the impact of the new architecture.

The conversation ends with @Destiny mentioning a request for members of the dev-squad to review and test a PR for the Sensei Pro upgrade created by @Jonathan, asking for help from contributors with developer experience.

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.

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