-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting Agenda May 9, 2024 #2424
Comments
I wanted to share this content feedback on one of my original tutorials from 2020. The learner came across my (very long) tutorial and shared feedback that the content was out of date. I replied with the updated tutorials for that same content. However, I did note that the learner came to the tutorial via organic search, so it got me thinking, as we move towards the learning pathways/learn redesign, what should we plan for when it comes to older content. We should probably do some sort of review as to what content is still coming up in online searches, and then add similar notices to the ones I added on this tutorial, about how there are updated versions. So I wanted to bring this up, and maybe start a larger conversation around formalising how we deprecate older content. |
Update: removed dev-squad as there was no triage last week. |
Update on the Learn WordPress remake from one of the developers on the project: |
I'd like to ask content creators and developers in the training team to share their thoughts and feedback on the following lesson This is a collaboration between myself and @ agiljulio. Agil's style of content creation is sightly different from mine, s0 I want to use this to explore what we (the training team) think works and should be kept, and what not. Things to consider (some of which have been altered during the initial review):
Please watch the different versions of the video, as well as the review feedback shared so far, and share any other thoughts you might have in the comments. |
Please also make a note that no one from dev-squad is available to host triage this week, and so we've agreed to move it to next week. |
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
2. Looking for feedback
3. Looking for volunteers
4. Other news
2. Come and Contribute
Content ready for review
Feedback awaiting validation
Topics awaiting vetting
Good first issues for developers
Validated feedback awaiting fix
3. Contribution Acknowledgement
4. Project updates
5. Faculty Updates
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.
The text was updated successfully, but these errors were encountered: