Meeting Agenda February 22, 2024

[Piyopiyo-Kitsune]

Training Team meetings start at 00:00 UTC weekly on Thursdays. 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 also incorporate these asynchronous conversations.

This week’s meeting will be hosted by @Piyopiyo-Kitsune.

1. News

1. Meeting Note Takers

• February 22 – need volunteer
• February 29 – narolainfotech
• March 7 – need volunteer
• March 14 – need volunteer

2. Looking for feedback

• Discussion: Bringing accessibility-first approaches into content development

3. Looking for volunteers

• WordCamp Asia 2024 Contributor Day -- looking for a host on site for the online portion.

4. Updates from last week's dev-squad triage session

Attendees: Jonathan (@psykro) and Muhibul Haque (@devmuhib)

There were no new PRs or bugs to triage this week, so we moved into triaging Content Feedback issues.

• [Related Course: Create a Custom Block Theme #1] Saving Your Work: Create Block Theme - Lesson Plan #853 (fixed and closed)
• Content Feedback - #1692 (outdated, so closed)

We also updated the Dev-squad triage handbook page to include details on validating Content Feedback issues for future meetings.

5. Other news

• Discussion: Translation Plugin on Learn — we will proceed with testing Polylang and WPML for our translation needs.
• Brainstorm: What trends about Learn WordPress learners do we want to observe?
• Discussion: Training’s contribution to the 6.5 release (and beyond)
  • @psykro and @greenshady are planning on facilitating Online Workshops regarding developer focused features (reference).
  • @trynet and @lada7042 are preparing an Online Workshop showcasing user-facing features.
  • @west7 and @digitalchild have distilled user-facing priority content from @annezazu ’s source of truth and created GitHub issues for these to be worked on at WordCamp Asia Contributor Day.
  • Process update: One GitHub issue will be created that will reference all the content that requires updating - @abhansnuk & @courtneyr-dev

2. Come and Contribute

Content ready for review

• See Guidelines for reviewing content when reviewing content.

Feedback awaiting validation

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

Topics awaiting vetting

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

Good first issues for developers

• See Developing Learn WordPress for instructions on contributing to the Learn WordPress code.

Validated feedback awaiting fix

• Faculty Editors, see Validating and Applying Content Feedback for step-by-step guidance on applying feedback that has been validated.

3. Contribution Acknowledgement

• Props: Any props to share?
  • Destiny gives props to Jonathan for the huge amount of work shared re: developer pathway.

4. Project updates

• Project Thread: Learning Pathways on Learn WordPress
  • Thumbnail templates are currently being created

5. Faculty 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 Faculty or Training Team members help you in some way?

6. Open Discussions

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

---

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.

[speedyprem]

@Piyopiyo-Kitsune I am interested to work as note taker for 22th February.

[jonathanbossenger]

Dev squad notes have been added to the agenda.

[jonathanbossenger]

I'd like to share this Accessibility issue on course excerpts raised by @amberhinds.

I have fixed the two featured course excerpts, but it might be useful to review all our other course excerpts, to make sure there are no more ambiguous links.