Closed ghost closed 3 months ago
kathrynwp
commented
3 months ago Until we've been able to test TranslatePress and document a new process for content localization, please do not publish any new translated courses or lessons. (See #2445 & #2339) Do feel free to prepare translations outside of Sensei so they are ready to go once the new process has been determined.
kathrynwp
commented
3 months ago For those creating lessons, please note that:
I also added a note to that effect on the Create the Lesson on Learn.WordPress.org handbook page.
reference/context: https://github.com/WordPress/Learn/issues/2739#issuecomment-2276663747
kathrynwp
commented
3 months ago As part of the previously announced Faculty Program retirement plan, the following Slack groups have been retired:
@faculty @faculty-admin @faculty-content-creators @faculty-editors @faculty-smes @faculty-dev-squad @faculty-translation-coordinators
On Aug. 15, the private Faculty Program channel will be archived. As discussed with the team reps, we’ll give the changes a bit of time and see how it goes. If folks find a need to ping particular sets of people going forward and this channel and/or DMs aren’t working, we can come up with a solution at that point, like creating a new group or new channel, if needed.
jonathanbossenger
commented
3 months ago With the initial learning pathways now published, some courses have become redundant or outdated. To streamline our offerings and ensure we provide the most current content to our learners, @westnz and @psykro propose deprecating the following courses and directing users to the relevant learning pathway.
Deprecating these courses will help eliminate duplication and simplify updates, as the learning pathways will be easier to maintain and will consolidate content updates into a single location.
Please let us know if you feel any other courses should be deprecated and directed to a learning pathway or if there are any on this list we should consider keeping.
jonathanbossenger
commented
3 months ago Thanks to the work of @alexstine and @brandonpayton, we have been testing and fixing a11y issues in the Playground block on Learn WordPress. All of the outstanding issues have now been fixed, so we'd like to ask other a11y experts to help us test.
You can find more details on this testing issue: https://github.com/WordPress/Learn/issues/2352
jonathanbossenger
commented
3 months ago I (@psykro) would like us to consider researching and applying some sort of feedback framework to GitHub issues related to the Learn WordPress site.
With the implementation of the new theme, we (the training team) are now able to better use more modern WordPress features and any new products that exist (now or in the future) in our ecosystem.
When suggesting, testing, and implementing any of these new features, it is important to find a balance between what we can control and what we can only influence. Some recent conversations come to mind, like the implementation of a translation plugin, the inclusion of the playground block, and the support for full-width alignment for lesson content.
When discussing these on GitHub, I think it's important that we have answers to the following questions in our minds:
I don't currently have answers to these questions, only opinions, so I'd like to start a discussion so that we can agree on a way forward and document it in our team handbook.
kathrynwp
commented
3 months ago See project update: https://make.wordpress.org/training/2023/07/07/project-thread-learning-pathways-on-learn-wordpress/#comment-4336
Zeelthakkar1207
commented
3 months ago Meeting recap post published : https://make.wordpress.org/training/2024/08/21/training-team-meeting-recap-15th-august-2024/
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 lada7042.
Ice Breaker: What is one thing you like about the updated Learn WordPress site?
1. News
1. Meeting Note Takers
2. Looking for feedback
Now that the new Learn WordPress site has launched, There are a number of items on the post-launch list, which you can see here: https://github.com/WordPress/Learn/milestone/21 If you encounter any bugs or want to suggest an enhancement, please use the feedback template in GitHub: https://github.com/WordPress/Learn/issues/new?assignees=&labels=Awaiting+Triage&projects=&template=00-feedback.md&title=Feedback+-
Course deprecation With the initial learning pathways now published, some courses have become redundant or outdated. To streamline our offerings and ensure we provide the most current content to our learners, @westnz and @psykro propose deprecating the following courses and directing users to the relevant learning pathway.
https://learn.wordpress.org/course/simple-site-design-with-full-site-editing/
https://learn.wordpress.org/course/part-2-personalized-site-design-with-full-site-editing-and-theme-blocks/
https://learn.wordpress.org/course/part-3-advanced-site-design-with-full-site-editing-site-editor-templates-and-template-parts/
https://learn.wordpress.org/course/developing-with-the-wordpress-rest-api/
https://learn.wordpress.org/course/converting-a-shortcode-to-a-block/
https://learn.wordpress.org/course/a-developers-guide-to-block-themes-part-1/
https://learn.wordpress.org/course/a-developers-guide-to-block-themes-part-2/
Deprecating these courses will help eliminate duplication and simplify updates, as the learning pathways will be easier to maintain and will consolidate content updates into a single location.
Please let us know if you feel any other courses should be deprecated and directed to a learning pathway or if there are any on this list we should consider keeping.
3. Looking for volunteers
4. Updates from last week's dev-squad triage session
Dev squad triage recap for August 8, 2024
5. Other news
Callout blocks are deprecated should no longer be used Use the Notice block instead If we’re updating a lesson, copy the text from the Callout block into a Notice block Kathryn also added a note to that effect on the Create the Lesson on Learn.WordPress.org handbook page.
reference/context: https://github.com/WordPress/Learn/issues/2739#issuecomment-2276663747
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
-Project Thread: Learning Pathways on Learn WordPress [See the latest project update here](- See project update: https://make.wordpress.org/training/2023/07/07/project-thread-learning-pathways-on-learn-wordpress/#comment-4336)
5. Contributor Updates
6. Open Discussions
If you have topics you’d like discussed in the meeting, please leave them as a comment on this issue.
With the implementation of the new theme, we (the training team) are now able to better use more modern WordPress features and any new products that exist (now or in the future) in our ecosystem.
When suggesting, testing, and implementing any of these new features, it is important to find a balance between what we can control and what we can only influence. Some recent conversations come to mind, like the implementation of a translation plugin, the inclusion of the playground block, and the support for full-width alignment for lesson content.
When discussing these on GitHub, I think it's important that we have answers to the following questions in our minds:
What is a feature vs. a bug? How do we decide the difference?
How do we determine what is a priority, and what is not?
Once something has been verified as "fixed" or "ready" how long should we wait for testing and feedback before it is implemented?
Before we implement something new, should we perform some sort of risk analysis, to determine the impact of this change?
I don't currently have answers to these questions, only opinions, so I'd like to start a discussion so that we can agree on a way forward and document it in our 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.