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 Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. account, you can set one up.)
Introductions and Welcome
There were 21 attendees @lada7042, @piyopiyofox, @zeelthakkar, @gwallace87, @rebeensarbast, @voboghure, @jagirbahesh, @digitalchild, @west7, @rithika3, @devmuhib(async), @nishitajoshi(async), @dhaval59(async), @darshanprajapat09(async), @noruzzaman(async), @psykro(async), @zoonini(async), @sierratr(async), @shalomt(async), @cnormandigital(async), @ironnysh(async)
Welcome, to all the new contributors who joined the Training Team’s Slack channel in the last week:
@rebeensarbast, @Mathieu Lamiot, @Oliver Bock, @Brett McSherry, @EidolonNight
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 Learn.WordPress.org.
If you haven’t seen them yet, then I recommend checking out our onboarding program, and our Guide Program
News
August 15 – @zeelthakkar
August 22 – @noruzzaman
August 29 – @Marar Rithika
Sept. 5 – @nishitajoshi
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
Vote for the Learn WordPress North Star by submitting their choice in this survey
With the launch of the new Learn WordPress site, several post-launch tasks need attention. You can view the list here: https://github.com/WordPress/Learn/milestone/21. If you find any bugs or have suggestions for improvements, please use the feedback template on GitHub 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. https://github.com/.
With the new learning pathways published, some courses have become outdated. To streamline content, @west7 and @psykro propose deprecating several courses and directing users to the relevant pathways. This will reduce duplication and make updates easier. If you have suggestions for other courses to deprecate or believe any on the list should be kept, please share your thoughts in the thread.
Looking for volunteers
Call for contributors: Intermediate Plugin Developer Learning Pathway
@psykro is working on this and is looking for scriptwriters, video editors, and researchers to assist. If you have time to help, please reach out.
Project Thread: Content Maintenance Process Update Phase 1
We’re currently reviewing all learning materials, and setting up clear guidelines will make this task easier in the future.
Call for Testing: Playground Block 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. on Learn WordPress
Thanks to @alexstine and @brandonpayton, a11y Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues in the Playground block have been addressed. We’re now asking other a11y experts to help with testing. More details are available in the testing issue #2352.
Updates from last week’s dev-squad triage session
Attendees: @psykro, @rfluethi, @noruzzaman, @digitalchild
User reporting strange behaviour when attempting to access course content #2774
Dev squad meetings are now scheduled biweekly on Thursdays at 07:00 UTC. Check the Training Team site welcome box for the updated calendar.
Other News
Until we test TranslatePress and document a new localization process, do not publish new translated courses or lessons. Prepare translations outside of Sensei for future use. (See Installing TranslatePress Pro on Learn #2445 &
Test TranslatePress #2339)
Thanks to @Jamie Madden and feedback from others, we clarified the admin approval process for videos. @Kathryn Presner & @Laura A updated the guidelines, and @Destiny will add an Approve button for categories. Thanks to @nilovelez for the feedback.
Callout blocks are deprecated. Use Notice blocks instead. When updating lessons, transfer text from Callout to Notice blocks. @Kathryn Presner added this update to the Learn.WordPress.org handbook.
Slack groups @faculty, @faculty-admin, @faculty-content-creators, @faculty-editors, @faculty-smes, @faculty-dev-squad, and @faculty-translation-coordinators have been retired. The private Faculty Program channel will be archived on Aug. 15. We’ll assess the need for new groups or channels based on feedback.
Come and Contribute
Feedback awaiting validation
Contributor Acknowledgement
@west7 suggested giving props to:
Kudos to @iRonnysh for finishing two new scripts for the Advanced user learning pathway.
Cheers to @Emmanuel for his first draft script on advanced SEO techniques.
Shoutout to @Ervan Yuffrizal for consistently producing high-quality videos.
Thanks to @Jamie Madden for script reviews.
Appreciation to @Maya for writing and organizing Spotlight posts.
Shoutout to @Soir and @Roelof Wobben for content reviews.
Project Updates
Project Thread: Learning Pathways on Learn WordPress
See the latest project update here: https://make.wordpress.org/training/2023/07/07/project-thread-learning-pathways-on-learn-wordpress/#comment-4336
Open Discussions
@Jonathan suggests discussing the application of a feedback framework for GitHub issues related to the Learn WordPress site. With the new theme allowing the use of modern WordPress features, it’s crucial to balance control and influence. @Jonathan proposes addressing key questions: distinguishing features from bugs, setting priorities, determining testing and feedback timelines, and conducting risk analysis before implementing new changes. He seeks to start a discussion to establish and document a clear approach in the team handbook.
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
