Triage Squad GitHubGitHubGitHub 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 by the repository owner. https://github.com/ triage: Biweekly on Thursdays 07:00 UTC
Additionally, the recently concluded Content Localization Foundations project received feedback that it is difficult for Content Translators to track translation items inย GitHubGitHubGitHub 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 by the repository owner. https://github.com/ also. It was suggested that content localization issues be moved into their own GitHub project board to make contributing and managing easier.
To respond to these pieces of feedback, @courtneypk and I propose creating two new GitHub project boards directed at the SMEsโ and Content Translatorsโ workflows.
Note: This proposal DOES NOT make large changes to the current workflows for Content Creators, SMEs, or Content Translators. It is a proposal to break three separate processes out into their own project boards for better management, and to make it easier for contributors to get involved.
Proposal
Currently, Content Creators, SMEs, and Content Translators sift through the teamโs LearnWP Content Development GitHub project board to find items they can contribute to. This process has received feedback from both SMEs and Translators that it raises the barrier to making contributions. @courtneypk and I propose creating project boards that match each area of contribution in the team. This would make it easier for contributors to find issues they can get involved in. It would also make triaging work easier for Faculty members as there would be less types of issues jumbled in one location.
Creating project boards for SMEs and Translators
The Training Team currently has 4 project boards. We propose adding two more:
Administrators (dev-squad), MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
Each project has columns which represent statuses issues move through. Each project board also has views which can be used to filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. issues by labels etc. (Example: Content Development project board) Below are the proposed details for the two new projects.
LearnWP Topic Vetting โ project details
Column name
Awaiting Triage
Awaiting Vetting
Vetted Topics
Closed Topics
Issue details
This is where topic ideas initially land when submitted.
Ideas are waiting for an SME to flesh out and prepare for content development.
Vetted issues are cleaned up before being sent to the Content Development project board.
Issues that were closed and didnโt make it to Content Development.
Issues moves to the next column whenโฆ
An Admin has confirmed an issue isnโt spam, isnโt a duplicate of content that already exists, and has added labels for the subject matters related to the topic.
An SME has finalized the โdescriptionโ, assigned a priority, and listed related resources. (Of the current assessment criteria, only items 2 and 3 would be required.)
โReady to Create โ You can Helpโ column in Content Development project board
โ
The project board would have views set up for each subject matter label (BlockBlockBlock 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. Editor, security, site development, etc.) and only show issues in the โAwaiting Vettingโ column. SMEs would only have to periodically check the views of the subject matters theyโre experts in, and move issues to โVetted Topicsโ once theyโve vetted them.
LearnWP Content Localization โ project details
Column name
Awaiting Triage
Translation in Progress
Awaiting Review
Published or Closed
Issue details
This is where localization issues initially land when submitted.
Issues are being worked on by a Content Translator.
A Translation Coordinator1 has confirmed an issue isnโt spam, has added labels for the locale, and provided the translator with necessary access to Learn.
A Content Translator has completed the translation of the piece of content.
A reviewer has completed a translation review and the content has been published.
โ
Next destination
โTranslation in Progressโ column
โAwaiting Reviewโ column
โPublished or Closedโ column
โ
1: A translation Coordinator is the Faculty equivalent of Content Translator. They are currently referenced to as Locale Ambassadors, but a change has been suggested in Recap: Content Localization Foundations Project.
The project board would have views set up for each locale label (Italian, Gujarati, Indonesian, etc.) and only show issues in the โAwaiting Reviewโ column. This will make it easier for content translators (reviewers) to find content waiting a review in their locale, as reviewing is an easier task to perform in short stints of availability.
Updates to the current LearnWP Content Development project
The two new projects listed above should help tidy up the current Content Development board, too. Here is what the updated board would look like.
Column name
Ready to Create โ You can Help
Drafts in Progress
Reviews in Progress
Published or Closed
Issue details
Issues have been vetted and relevant labels have been added.
Issues being worked on by a Content Creator.
Content waiting for reviews.
Completed issues.
Issues moves to the next column whenโฆ
A Content Creator has commented on the issue, volunteering to create it. An Admin has confirmed the volunteer has necessary access to create the content on Learn.
A Content Creator has attached the created piece of content.
A content has received three reviews, and has been published.
โ
Next destination
โDrafts in Progressโ column
โReviews in Progressโ column
โPublished or Closedโ column
โ
The project board views could be tidied up to just have the following:
High Priority topics ready to create (New!!)
Reviews in progress
Recent releases
We tried to brainstorm updates that would make it easier for SMEs and Content Translators, but not affect the current flows Content Creators are used to. To note, weโd expect seasoned Content Creators to skip the LearnWP Topic Vetting project board all together and just start making content in the LearnWP Content Development project board.
What are your thoughts?
How does all this sound? Please leave your thoughts by May 21st. As long as there arenโt major objections, we plan on implementing these changes by the end of May.
Learning pathways are a structured sequence of educational experiences or courses that are designed to help individuals acquire knowledge and skills in a specific field or discipline.
@carlosย is working on it and wanted feedback if this is something that would work as a course or would work better as a learning path
Should sharing presentation slides be a requirement for Online Workshop presenters?
@courtneypkย started this conversation in this Slack threadย . if you have any thoughts on it. I request you to please go to this thread and share your thoughts.
Recentlyย WordPress Developer Blogย was officially launched. Many of those articles contain links to code example repositories, usually in the authorโs GitHubGitHubGitHub 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 by the repository owner. https://github.com/ account. Jonathanย and other developer educators in the team also create code example repositories for our workshops, tutorials, and courses forย Learnย WordPress, also hosted on our own accounts. Josepha suggested it might be useful to repurpose the wptrainingteam organization, renaming it to something likeย learn-WordPress. So weโd like to find out what theย trainingย team thinks of this idea. As far as I know that GitHub organization isnโt actively used anymore, so repurposing it as the official place for example code for all Learning related content for WordPress makes sense.
WordPress Community Summit 2023 โ Leadership is looking especially for newer contributors to join, who can bring fresh perspective to the WordPress project. If you are even a little interested in joining, pleaseย apply to attend.
Other news
Weโve published a new handbook page that details each of the Faculty roles:ย Faculty Role Guides
The marketing team is looking for blogging prompts for the 20th anniversary. (Slack thread with more details)(Please note: this link will take you away from this meeting flow)
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 Training Teamโs efforts have historically been focused on creatingย content for Learn.WordPress.org in the English language. The Content Localization Foundations project was the teamโs first efforts to onboard contributors who speak other languages and translate content into different locales.
Over the course of 5 months, 28 volunteers created 36 pieces of localized content across 10 locales. Additionally, volunteers translated some of the Training Teamโs handbook pages related to content translation into 5 locales.
The project achieved some of the objectives initially laid out. Many points were learned that would improve the entry to localizing content on Learn.WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. Some necessary changes for the Locale Ambassador role were also identified. The team will continue to iterate on content localization processes to respond to these findings.
Project Achievements
The following are what this project achieved in its six month duration from November 2022 to April 2023.
Content Translation
Goal: Translate 10 priority learning content into each target language (Inclusive of Lesson Plans, and Tutorials)
Completed: The team translated the following pieces of content:
Locale
Published content
Translations waiting review
Translated handbook pages
Project contributors
Arabic
1 Lesson Plan
โ
โ
2
French
1 Tutorial
โ
2
2
Greek
โ
9 Tutorials
โ
2
Gujarati
4 Lesson Plans, 1 Tutorial
โ
14
5
Hindi
6 Lesson Plans
โ
2
4
Indonesian
1 Lesson Plan, 2 Tutorial
โ
โ
3
Italian
2 Lesson Plans
1 Lesson Plan
5
3
Japanese
1 Online Workshop
โ
โ
3
Khmer
โ
1 Lesson Plan
โ
1
Tamil
6 Lesson Plans
โ
2
3
Total
20 Lesson Plans, 4 Tutorials, 1 Online Workshop
2 Lesson Plans, 9 Tutorials
25
28
Number of content translated, by locale
Learnings: The project wasnโt able to translate 10 pieces of content in any one language.
Part way through, the project recognized the process of translating a Tutorial (recording and editing a video) was more involved than most translators were able to contribute to. The project changed priorities to translating Tutorial subtitles instead, but not early enough to reach the goal of โ10 pieces of translated contentโ in any locale.
Next steps: Continue translating content in different locales, but focus on text-based content as a priority.
Onboarding and Documentation
Goal: Create a workflow of onboarding and how-to guides that take folks through the journey of joining the Training Team to publishing localized content
Learnings: Feedback was provided on how it was difficult for many contributors to track translation items in GitHubGitHubGitHub 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 by the repository owner. https://github.com/ amongst other content creation issues.
Additionally, we received mixed feedback regarding using GitHub to manage translations. In general, those with experience using GitHub found the documented processes easy to follow. At the same time, others with little/no experience using GitHub showed hesitation to getting involved.ย
Next steps: To make tracking issues easier, we can move content localization issues into their own GitHub project board.
As for the perceived difficulties of GitHub itself, we can either improve the current onboarding to provide more assistance, or the team can consider using a different tool to manage translations (such as translation plugins, or Computer Assisted Translation tools). This is something the team will investigate further.
Goal: Bring in at least two new Training Team Members from the following locale communities: Spanish, Japanese, German, French, and Italian
Results: The project had 28 contributors across 10 locales that contributed to publishing content.
Learnings: The project was able to bring in project contributors from 3 of the 5 most used WordPress locales. WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what theyโve learned throughout the year and share the joy. Learn more. Asia was a good onboarding opportunity, where we saw multiple contributors from other locales join the project. Many contributors joined either through the Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ event or after hearing a presentation from @bsanevans on the Training Teamโs localization efforts. (View slides here.)
Next steps: These results encourage the Training Team to continue having a presence at different events โ especially WordCamps and Contributor Days โ where the team can present the need for content localization to different communities.
Enlisting Locale Ambassadors
Goal: Establish the Locale Ambassador role. Enlist at least five Locale Ambassadors.
Completed: The Locale Ambassador handbook page was published. 6 contributors (in 5 locales) volunteered to be Locale Ambassadors for this project. Of these, 2 locales were able to publish content.
Notably, @piermario and @margheweb did a fantastic job as Italian Locale Ambassadors. They actively onboarded contributors and translation reviewers. They also represented the Training Team at Contributor Day at WordCamp Torino, leading a table focused on translating content for Learn.WordPress.org.ย
Learnings: The project received the following feedback about the Locale Ambassador role:
Some are hesitant at joining the role as its definition includes a broad range of responsibilities. (โโA Locale Ambassador is someone who bridges their local community and the Training Team through various initiatives such as, but not limited to: bringing contributors into the Training Team, onboarding contributors to the Training Teamโs processes and providing language support, creating localized content.)
Some would become a Locale Ambassador if they werenโt alone in the role in their locale.
Currently, Locale Ambassadors continue to rely on Faculty Administrators to triage GitHub issues or provide translators with website access, causing a bottleneck in the translation process.
Next steps: The project suggests renewing the Locale Ambassador role in the following ways:
Renaming the role to โTranslation Coordinatorsโ to better describe the main focus of the role.
Positioning โTranslation Coordinatorsโ as a fifth role in the Faculty Program.
While this adds a vetting process to joining the role, it will provide the role with the same GitHub/website access as Faculty Administrators, empowering them to conduct the various tasks that currently rely on an Administrator to perform.
It will also connect Translation Coordinators with others already in the Faculty program, providing better support.
Website Development
Goal: Enable locale tagging for Courses, Tutorials, and Online Workshops
Goal: Have localized content show first on the Learn WordPress homepage when someone visits the page in their native locale
Completed: Localized Tutorials show on the homepage when viewed in a locale that has one.
Next steps
While this project will now be closed, the need to localize content on Learn.โโWordPress.org continues. The project suggests the Training Team continue to iterate on the content localization process, starting with these points:
Renew the Locale Ambassador role as a fifth Faculty role: โTranslation Coordinatorsโ.
Focus localization efforts on text-based content.
Create a dedicated project board within the teamโs GitHub repository to track content localization.
Continue raising awareness of the localization needs of Learn.WordPress.org at events.
(We have alternated our weekly team meetings according to the timezone. This week we are having the Team Meeting in the EMEA timezone, and a Coffee Hour was held in the APAC timezone at 7:00 UTC.)
Do you have any thoughts on the proposed improvements to the Faculty program? Or perhaps you have additional ideas? Please leave any thoughts you have in the comments section of the post. (NOTE: Feedback is welcome from both Faculty and non-Faculty members)ย
Learning pathways are a structured sequence of educational experiences or courses that are designed to help individuals acquire knowledge and skills in a specific field or discipline. @courane01ย is working on it. If you have any thoughts, Please do share your thoughts in the comments.
Jamie produces fantastic content for YouTube, and heโs looking for feedback about whether theyโd be a good fit for Learn WordPress, too. Please check out the information in the following GitHubGitHubGitHub 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 by the repository owner. https://github.com/ issue, and leave your thoughts as comments there: https://github.com/WordPress/Learn/issues/1439
If you are interested in helping with this, please share your interest in this Slack thread.
Discussion: How can we streamline the meeting agenda/recap posts? Reps have two ideas:
Agenda in GitHub, recap on the blog
Detailed agenda on the blog, and add notable discussions in the comments section.
Please share your thoughts in this Slack thread. Which of the two options do you think is better, and why? Or, do you have other suggestions too?
Project Update News
Until last week, at the end of each meeting, we had a section titled โOther projectsโ where we would ask project leads for an update. However, some projects move slower than others, and we donโt want to burden folks with excess notifications. The last week, we excluded the on-hold projects from the meeting agenda and add them back when they are resumed. You will find a note about these paused projects on the Teamโs Administration GitHub board.
Weโre looking for ideas to streamline the process of reviewing subtitle files, as GitHub doesnโt accept .ttml file uploads. Please leave your comments onย this Slack thread.
Due to unforeseen circumstances, the data analysis publication date has been postponed until further notice. An update will be posted once we have more information.
Other Ways to Contribute
Ready to start contributing? Here are a couple of ways to get involved today!
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.
Do you have any thoughts on the proposed improvements to the Faculty program? Or perhaps you have additional ideas? Please leave any thoughts you have in the comments section of the post. (NOTE: Feedback is welcome from both Faculty and non-Faculty members)
Learning pathways are a structured sequence of educational experiences or courses that are designed to help individuals acquire knowledge and skills in a specific field or discipline. Please leave any thoughts you have in the comments section of the post.
If you are interested in creating content for Learn, then take a look at the proposal in the GitHubGitHubGitHub 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 by the repository owner. https://github.com/ thread above. Weโd love to hear your thoughts (CC: @faculty-content-creators on Slack)
Open Question: Should sharing presentation slides be a requirement for Online Workshop presenters?
A Slack thread was started to discuss whether sharing presentations slides should remain an option, or a requirement, for Online Workshop presenters. Please leave you thoughts in the Slack thread.
โOn May 27, 2023, WordPress celebrates a significant milestone in its journey as the project reaches its 20th anniversary. As part of the planned activities to mark this achievement, project leadership commissioned a book last year to document the years since its first commissioned work, Milestones โ The Story of WordPress (2003-2013.)
The next volume, Building Blocks: The Evolution of WordPress, spans the history of WordPress from 2013-2023 and catalogs its wins, learnings, and everything in between.โ
If youโd like to get involved, please provide feedback via GitHub with first-look access to the upcoming WP20 Book.ย
Iโve been checking in with members of the project, getting their feedback in preparation for a wrap-up/next-steps post. Thank you to everyone who has responded so far.
If anyone has any feedback about the content translation process in the team, please let @bsanevans know.
Due to unforeseen circumstances, the data analysis publication date has been postponed until further notice. An update will be posted once we have more information.
This is a new project that was just published by @amitpatelmd. The project will work on the following points:
Custom GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses โblocksโ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/gutenberg/blockBlockBlock 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. development
Adding SEO MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. fields
Adding language switcher menu for translated pages/posts
@faguni22: โEid al-Fitr is this Saturday April 22nd. So Eid Mubarak to all!โย
Ways to Contribute to the WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Training Team
Help us welcome new members to the Training Team and foster our growing community.
Also, check out a list of upcoming Online Workshops on our calendar with events shown in your local timezone:
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.
(Others are welcome to join in on the efforts, too! Let us know if youโre interested ๐)
Project Timeline
Will be posted shortlyโฆ
Project Details
1. Custom GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses โblocksโ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/gutenberg/blockBlockBlock 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. development
Proposing custom Gutenberg blocks for meeting recap notes, faculty meetings, onboarding posts, etc. This will help to speed up adding/editing the content part.
The idea is to give the simplest user interface for adding required data for meeting recap notes, agenda posts, etc in no time. This will also encourage new contributors to create and work on posts.
2. Adding SEO MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. fields.
Coordinating with codebase team members and adding meta fields for every post and page for training and learn websites.
This feature is going to be completely customizable without utilizing any plugins.
3. Adding language switcher menu for translated pages/posts.
Setting up and enabling language switcher options somewhere in headerHeaderThe header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitorโs opinion about your content and you/ your organizationโs brand. It may also look different on different screen sizes. and footer navigation for learn and training websites. This will help to map same content with their language variations.
This will enable quicker navigation and engage users to find quickly what they are looking for.
