Project Thread: Retiring the Faculty Program

Project objective

After discussion, the Training team has decided to go forward with retiring the Faculty Program, in order to streamline processes, help the team run more efficiently, and free up people’s time to focus on higher-impact areas. 

Project members

Project lead: @zoonini

Members: the team reps – @piyopiyofox, @digitalchild, @lada7042

Project timeline

Start: July 18, 2024

End: September 12, 2024


The Faculty Program consisted of a group of Training team members who helped establish team processes, catch up on a backlog of tasks, and set up the team for future success. With the team evolving over time, it became evident that many Faculty members were no longer active on the team, many roles were under-used and difficult to recruit for, and the program required time-consuming administrative overhead. In addition, needing to apply to be part of the Faculty program could be seen by contributors as a barrier to doing certain types of work on the team. In addition, the now-established Guide Program serves as a welcoming path for people to get more involved with the team’s activities.


The plan includes:

  • Adding a new area in the handbook, outlining the history of and the Training team. This section will include the names of past team reps and Faculty members, so that folks’ contributions are visible and recognized in the context of the Training team’s history.
  • Shifting the work done by the current Faculty Admin group to a smaller group of administrators, starting with the team reps. Additional admins will be added over time, while the current admin needs of the team are reassessed. We will likely look for Training team members who have made consistent contributions over the last 6-12 months.
  • Updating the handbook to remove the Faculty Program section.

Below is a detailed schedule outlining the tasks to be performed and target completion dates.

If there are any questions about this process, please feel free to drop them in the comments.

Once again, a big thank you to everyone who has been a part of the Faculty Program over the years. Your invaluable help has made the Training team stronger than ever.

2024-07-18Access updates– Update access as needed, including Canvas with login info
– Let people know if any access has been changed
2024-08-08Research & write new handbook page compiling a history of the Training team– Collect names of all past & current team reps and Faculty program members
– Include a general history section 
– Draft page
– Share page with Training team for feedback
– Make revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. as needed
– Publish page
2024-08-15SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at updates– Determine what Slack changes are needed
– Archive current Faculty channel
– Review and update Slack bookmarks and pinned channel items in #training and related channels
2024-08-29Process updates– Go through all team processes and make a list of what will need updating, in collaboration with team reps
2024-09-12Handbook updates– Update old handbook pages as needed, based on discovery above. 
– Unpublish pages related to the Faculty Program
– Keep a log of which pages were unpublished, to be included in final project update
2024-09-12Help Scout updates– Go through all Help Scout Saved Replies and update as needed

Brainstorm & Table Lead – WordCamp US 2024 Contributor Day

The WordCamp US Contributor Day will be taking place on the 17th of September 2024! In preparation for the day, we’d like you to share ideas of what contributors at the Training Team table can get involved with that day.

You can read our Preparing for a Flagship WordCamp Contributor Day handbook page to learn more about how the Training Team prepares for Flagship WordCampWordCamp WordCamps 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. Contributor Days.

Table Leads

We are looking for Contributor DayContributor Day Contributor 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 There are many teams that people can participate in, each with a different focus. table co-leads for WordCamp US 2024– do we have any volunteers?


Below are some ideas to kick-start discussions. Feel free to comment on this post with your ideas, too!

This brainstorming is open until Monday, August 19th.

Team reps and table leads will consider all ideas and publish a post with a final plan by August 30th.

Experienced Contributors

  • Review Ready for Review content
  • Write a script for a learning pathway lesson or other lessons under Ready to Create
  • Assist with Project Thread: Learning Pathways on Learn WordPress
  • Join a session discussing practical insights into lesson creation
  • Create content
  • Work on Content Localization
  • Vet Topic Ideas
  • Cross-team collaboration opportunities  

New Contributors

  • Contributors walk through the Onboarding Paths
  • Review online courses and submit feedback
  • Write a script for a learning pathway lesson or other lessons under Ready to Create 
  • Review published content and submit an error report
    • Spelling mistakes
    • Outdated content
    • Something is not clear and needs improvement
    • Screenshot/images missing.

#contributor-days, #wordcampus

Project Thread: Learning Pathways on Learn WordPress

Project Objective: Create and launch progressive user-friendly learning pathways tailored to different types of Learners on Learn WordPress.

Project Overview

The WordPress Training Team recognizes the need for a clear, structured, and user-friendly approach to presenting Learn WordPress content. This need has been confirmed by feedback from the individual learner survey and WordCamp EU Contributor Day attendees. As a result, this project aims to deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. an improved Learn WordPress website experience that provides an easy-to-navigate, goal-oriented learning environment that caters to learners of different roles and skill levels.

This project will serve as a foundational start, establishing a framework and functionality that will allow for the expansion and growth of the learning system over time. To meet our objective, this project includes a website redesign that offers clear learning pathways to reach target Learners such as Developers, End Users, and Designers. We will also focus on making relevant content easier to find and the inclusion of a framework that classifies content by skill level. We believe this will enhance user engagement, improve learning outcomes, and increase user adoption of Learn WordPress resources.

Our journey will not end with the initial deployment of the new site. Rather, it is just the beginning of an iterative process of continuous improvement and expansion, leveraging feedback and data analytics to enhance the user experience continually.

We hope that this project will help us better serve the wider WordPress community by promoting knowledge transfer and ensuring a thriving community with diverse skills and abilities.

Thank you to @courane01 for getting this work kicked off in your Creating Learning Pathways for Learn WordPress and subsequent GitHub issue.

Project Members

Project lead: TBD

Members: @jominney @piyopiyofox @west7 @psykro @zoonini @bsanevans

Project Timeline

Start: July 24, 2023

End: July 2024

Project Deliverables

  • Develop a website redesign for Learn WordPress that delivers a clear, user-friendly pathway for learners of different levels, roles, and use-cases.
  • Enhance the discoverability and searchability of relevant Learn WordPress content through the integration of new search filters and content organization strategies.
  • Establish a skill level classification framework for Learn WordPress content that enables clear content filtering and search results based on learner needs.



Tasks in this section scope out project parameters and requirements for the success of this project.

Project Management

  • Recruit project members
  • Establish cross-team collaboration points of contact

Information Architecture

  • Create outlines and storyboards that detail learning pathway components based on the proposed information architecture
  • Map out content to provide a proposed information architecture (i.e. content types, taxonomies, relationships) that integrates Pathways
  • Conduct targeted user research to validate content decisions such as language, information architecture, outlines/storyboards

Deadline: September 18th 2023

Content Creation

Cross-team collaboration point of contact: @west7

These are tasks that Training Team Content Creators can help us accomplish

  • Outline specific skill levels and learning outcomes for each pathway.
  • Identify existing content that can be used within pathways.
  • Create outlines and storyboards that detail learning pathway components. (Either Miro or Google Jamboard will be used)
  • Develop a content creation guidelines that enable the Learning Pathways to scale, with a clear process for developing, reviewing, and updating content.

Deadline: November 2023

  • Develop new content where gaps exist.
  • Develop clear and concise learning pathways for target Learners.

Deadline: March 2024


Cross-team collaboration point of contact: @fcoveram

These are tasks we will need to do in collaboration with the Make WordPress Design Team.

  • Develop a cohesive design concept for the Learn WordPress site.
  • Develop visual language for skill level classifications.
  • Ensure that the site design aligns with the learning pathways vision and goals.
  • Ensure that all visual elements are accessible and meet accessibilityAccessibility 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). ( standards, such as color contrast ratios and readable typography.

Deadline: January 2024


Cross-team collaboration point of contact: @adamwood

These are tasks we will need to do in collaboration with the Make WordPress MetaMeta Meta 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. team and Training Team developers.

  • Ensure that the Learn WordPress site redesign accommodates various learning pathways and skill levels.
  • Build out any new functionality required to support learning pathways and content classification.
  • Collaborate with content creators to ensure that the site structure and content is optimized for user experience.
  • Ensure that the site is optimized for searchability and discoverability of content
  • Implement user tracking and analytics features to capture data on user behavior and engagement with Learning Pathways.
  • Ensure that the site is optimized for fast page load times and is easily accessible on various devices, including desktop, mobile, and tablet.
  • Ensure that the Learning Pathways are integrated with any relevant third-party tools or services that may further enhance the user experience, such as social sharing, reminders and bookmarking tools.

Deadline: May 2024


Cross-team collaboration point of contact: @sereedmedia

These are tasks we will need to do in collaboration with the Make WordPress Marketing Team..

  • Develop a strategic marketing plan for promoting Learn WordPress learning pathways.
  • Identify target audiences within the three groups of Learners and develop targeted campaigns for each group.
  • Develop clear messaging that speaks to each Learner group’s specific needs and pain points.
  • Track engagement and optimize marketing efforts over time.
  • Partner with the content creators and designers to create promotional materials, including blog posts, social media graphics, and email marketing campaigns, to promote the Learning Pathways effectively.

Deadline: July 2024

Thank you to the following contributors who helped shape this project plan: @courane01 @bsanevans @jominney @digitalchild @fcoveram @ardianimaya @tobifjellner @yvettesonneveld @askdesign @west7 @lesleysim @sereedmedia

Let’s start testing

The new is launching soon, complete with four courses in the User and Developer Learning Pathways. Your help is needed to QA/test the new site! Please follow these steps and report any bugs you find

Testing steps

  • Log into The 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. if you’re not already.
  • Visit or click the “Preview the new theme” link in the admin bar.
  • Navigate the site and make sure all links work as expected, and everything looks as expected.
  • Register for a course and go through all the lessons/quizzes.
  • Try different browsers and devices, including mobile devices.
  • Repeat the above steps – except for course registration – while logged out. (The new-theme preview link now works while logged out.)

Pages to visit

Testing Courses and Quizzes

Reporting Bugs

If you find any issues:

  • Search the Learn WordPress GitHub repository to see whether the issue has already been reported. (See also list of current reported bugs, and milestones of issues for launch and post-launch.)
  • If it’s a new report, create a new GitHubGitHub 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. issue in the Learn repository using the Feedback template.
  • Mention in your issue that the report is for the new Learn WordPress site.
  • If you have the ability to assign the issue to a GitHub Project, select “ Redesign” project, and if possible, also the “LearnWP Website Development” project. If not, no worries – leave Project blank and it will be assigned for you. 
  • Please include:
    • Your OS and version
    • Your browser and version
    • Link to the specific page you found the bug on
    • Screenshot or screencast showing the problem

Known issues, enhancements, and prioritization

  • Current reported bugs.
  • The thumbnail creation process is still ongoing, so some lessons and other content “cards” do not have custom thumbnails yet. You can still help create more thumbnails – get all the details.
  • While suggestions for future enhancements are also welcome, the priority at the moment is to find urgent bugs that may affect the launch.
  • The dev team will prioritize bugs that are blockers to launch, with other issues set to be addressed post-launch.
  • Don’t worry if you’re not sure whether something has already been reported or isn’t actually a bug. Better to report it just in case.


Please log all GitHub issues by July 17, if possible.

Thank you in advance for helping make the new Learn WordPress the best it can be!


Training Team Meeting Recap – 11th July 2024

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 SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at account, you can set one up.)

Introductions and Welcome

There were 22 attendees @lada7042, @jagirbahesh, @piyopiyofox, @digitalchild, @dhaval59, @zeelthakkar,@noruzzaman, @nazmul111, @voboghure (async), @devmuhib (async), @sumitsingh(async), @rithika3(async), @nishitajoshi(async), @Maya(async), @zoonini, @psykro, @ironnysh(async), @west7, @iRonnysh, @rinkuiihglobal, @askdesign, @zoonini

Welcome all the new contributors who joined the Training Team’s Slack channel in the last week:

@hellosatya, @Vince, @mustakim5@archanasolanki, @roelof, @eizwanzulkipli, @Hardip ,@Julia @KeithN, @teuila_mau, @rjfrizz, @piotrmonka, @enamulwp, @sam33r42, @keithnoseworthy, @raissamatho, @priyazes, @imranex

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

If you haven’t seen them yet, then I recommend checking out our onboarding program, and our Guide Program


Meeting Note Takers

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 in this handbook page.

Looking for feedback

@lada7042 shared some thoughts with on
What is Learn WordPress’ North Star?
– Learn WordPress’s north star

– Is Learn WordPress the site where folks come to learn about the most relevant and up to date content on WordPress?

Is it the place where we encourage and guide folks to be at the forefront of the software?

– fostering a collaborative learning community

– Relevant + most up to date

– The place to come to learn about WordPress

@lada7042 set for The original Training Team site is archived
Can #dev-squad help with this?Please share your feedback

Looking for volunteers

We are looking for folks – Thumbnail Creation Project creating and uploading the new thumbnails.

Testing the new Learn WordPress

Help test the new Learn WordPress site and report any bugs you find. Full guide here:

Other News

Content Overriding Issue: As mentioned in the Slack channel, original content was overridden by a translated version. Thank you to everyone who communicated and resolved the issue.

Important Reminder: Please DO NOT assign translated lessons to a course. Publish them as standalone lessons.

Updates: @piyopiyofox has updated the handbook page. See the Slack post “Translating and Publishing a Lesson”

Tutorial Deprecation: To reduce content types on the Learn WP site, Tutorials are being deprecated and will be converted into Lessons (Tutorial data migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. #2393). A note has been added to all Tutorial-related handbook pages. Once the conversion is complete, these pages will be fully retired.

Join us for an opportunity to discuss and collaborate on learning pathway content. Whether you’re working on content or interested in contributing, this is the perfect time to meet, ask questions, and find projects to work on. Meetings alternate between two time zones each month

Come and Contribute

This Week’s Focus: Review 10 issues following the content review guidelines.

Feedback Awaiting Validation: 25 issues need validation. Refer to “Validating and Applying Content Feedback” for guidance.

Topics Awaiting Vetting: 4 issues need vetting. Refer to “Vetting Topic Ideas” for guidance.

Good First Issues for Developers: Currently, no issues require development. Refer to “Developing Learn WordPress” for instructions.

Validated Feedback Awaiting Fix: 20 issues need fixes. Faculty Editors should follow the “Validating and Applying Content Feedback” guide.

Contribution Acknowledgement

Badges Awarded:

  • At the end of the month


  • Special thanks to @devmuhib for uploading many thumbnails and organizing a local Contributor Hour to create more thumbnails.
  • Any other props for this week? Please add to the thread.

Contributors in the Community:

  • Check out an interview with content creator @west7 in the recent WP Briefing podcast discussing Learning Pathways and their benefits for WordPress learners.

Project updates

Learn WP Remake project update:

Open Discussions:

If you have topics for the meeting, please comment on this issue.

Contributors in the Community:

  • Check out @zoonini‘s presentation, “Untangling Templates,” from WC Canada. Look for the live stream or replay.

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.

#meeting-recap, #training, #training-team

Recap: The second Learn WordPress course cohort

The Training Team has just facilitated Learn’s second course cohort. We saw great improvement from the first cohort, both in learner engagement and ease of administration. We think this is an effective learning method that can be continued on a regular basis.

Cohort overview

  • Invitations were sent to the 37 applicants on the waitlist from the first course cohort, and to 2 people who contacted cohort administrators showing interest to join.
  • Of those, 19 responded (51%) and 17 accepted (46%).
  • The cohort ran for 6 weeks (May 9th – June 20th) and included 6 calls.
  • An average of 9.3 participants attended each week’s call.
  • 5 participants completed the course content by the final call.
  • 2 participants did not start on the content.

Changes from the first cohort

  • The roles of course administration and teaching were split, with @bsanevans and @zoonini serving as administrators, and @psykro as the Subject Matter Expert (SME).
  • As the waitlist from the last cohort was used, no public call for participants was made.
  • All communication happened on SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at both prior to and during the cohort.
  • There was no content drip and participants were given access to all content on the first day.

Feedback survey results

Participants were asked to complete a feedback survey once they had completed the course. 

  • Of 17 participants, 10 filled out the survey (59%).
  • 70% of respondents indicated that the course achieved all of their expected learning outcomes, while 30% said it achieved many of their learning outcomes.
  • 80% of the participants thought there was enough time to complete the course, while another 20% felt that “the course workload was manageable, but external factors kept me from completing the course in time.”
View more survey feedback

Respondents highlighted the following areas as aspects they liked about the way the course content was presented:

  • The course walked through a pretty clear step-by-step approach with the most important part of each lesson at the beginning, with supplemental information afterward. I also appreciate that there was written content in addition to the video. I personally don’t like learning from videos and much prefer written content, so I don’t think I watched any of the videos, only read the content, which contained everything I needed. 
  • It was very bite-sized. I enjoyed that.
  • I really liked the way the course was presented.
  • Live demonstration.
  • The classes were the fun part. The live coding really helped as did Jonathan’s work to get people to interact in the class.
  • Clearly outlined / Inclusive of all skill levels / Feedback loops / Code review / Weekly meetings     
  • It was very well structured. It had the feeling of learning, taking stock of where I was and then moving on.
  • This was my first time doing any course where there was a live and real-time chat component so I did love having that ability to ask questions in realtime! Also, felt Jonathan & team were awesome. Really wanted us to succeed but also was realistic about development too and the issues that pop up. Looking forward to more from the Learn team!

Only one respondent highlighted a missing topic they expected to learn in this course: the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) “in detail.” Another respondent added, “BlockBlock 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. creation is quite a vast topic. Considering the regular development going on, it’s difficult to include everything and learn. Any guidance on how to keep up to date with upcoming features is helpful.” One more respondent shared, “The course was well designed and explained. It had some challenges but nothing that was too difficult to overcome with a little work.”

While most of the respondents indicated that the course instructions were clear and easy to follow, one person mentioned that it was hard to see and follow the live coding portions without being zoomed in, while another said that, “Instructions were fairly clear, but I had to ask questions to clarify some details.”

When asked if there was anything that would have made this course more successful, respondents shared the following suggestions:

  • Bonus quests/jumping off points after lessons, such as, “Try to add XYZ support” or “Take a look at this CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block [link] and determine how it stores its data and renders it dynamically”     
  • I wonder if it would be worth splitting cohorts by experience level; e.g. one cohort for people who are more experienced developers and one for complete novices.
  • Links to advanced learning, Any example blocks challenges if we can try etc
  • I really would have liked some pair programming. This might be something that can be added to the course to have people work together. I think that it would foster a better experience when the meetings happened as it would allow for people to talk about the experiences with the curriculum.     

Other feedback and suggestions:

  • I didn’t get a ton of value from the weekly calls. I think I went into them expecting a deeper dive on the week’s lesson, rather than just a Q&A time. That’s okay though, because other folks seemed to get a lot out of the weekly calls.  
  • Use of git Roadmap for block development 
  • Thank you for the time and effort that has gone into creating and delivering this course; it’s been really useful.    
  • The only feedback I have is that I would have loved to have a lesson/challenge at the end of like, now that you’ve completed this, please try to do X, you will use what you learned and should be able to do this small task of adding this to your block.     
  • Jonathan & Kathryn were helpful. They were patient with our questions and their down to earth approach made me comfortable to ask questions.

Some participants also shared feedback on their blogs and social media:

Summary and next steps

The aim of this cohort was to build a sustainable program the Training Team can continue to administer for learners on Learn. In that light:

  • Administrative changes tested this time around all contributed to a more effective cohort management, and have been reflected in the course cohort handbook page.
  • The drop-off rate of participants throughout the cohort was similar to that of the last cohort. Based on these, inviting around 40 applicants will result in around 10 engaged participants and is a comfortably manageable cohort size.

The goals of a course cohort are similar to those of Online Workshops. The two differ only in that course cohorts happen across consecutive sessions while Online Workshops are generally one-off sessions.

  • By reconsidering course cohorts as an extension of Online Workshops, the administration of hosting course cohorts could probably be reduced further.
  • With the launch of Learning Pathways, the team now has multiple courses that could be used as the subject of course cohorts.

Based on these observations, we propose that the Training Team look to host future course cohorts as a series of Online Workshops that walks participants through Learning Pathways content.

Please comment below with any additional thoughts or questions. Thanks!

This post was written by @bsanevans with additional material by @zoonini.

Exploring WordPress Certifications

Over the years, there have been a few discussions about creating formalised certifications for WordPress, most notably in 2013 as seen on Torque and WP Tavern. While those discussions are nearly 10 years old, they are still relevant and, now that an open learning platform for WordPress exists, this is a good time to revisit those conversations.

Before we get anywhere near implementation, let’s take a step back and gather some initial thoughts on how a WordPress certification should be approached. Certifying open-source software has some inherent challenges, but also some wonderful advantages. With that in mind here is some interesting content to review:


Since this is an exploratory post and not a proposal for anything concrete, please comment with your answers to the questions below, as well as any other thoughts you have about this topic:

  • What benefits would certifications provide?
  • What would be some effective ways to use certifications in the WordPress space?
  • What potential pitfalls need to be kept in mind, should we proceed?

Project thread: The second Learn WordPress Course Cohort

Project Objective

Conduct a course cohort on the same content as the 2023 cohort. Experiment applying learnings from the last cohort, with an aim to build a sustainable program the Training Team can continue to administer for Learners on Learn.

Project Overview

One of the Training Team’s goals this year is to run 1-2 outcome/project-based course cohorts. A course cohort is defined as a group of people who go through a learning journey at the same time. In 2023, the Training Team conducted a cohort where learners worked through the Course “Developing your first WordPress BlockBlock 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. Participants gathered for a synchronous call each week where they could ask the instructor questions around the content they had worked through. The cohort received positive feedback from learners, but there were multiple takeaways in the administration of the cohort which are documented in this recap.

The aim of this project is to experiment applying the learnings from the last cohort, with the hopes of turning course cohorts into a sustainable educational offering on Learn. The project will use the same material as the last cohort, and will be offered to all applicants on the waiting list from the last cohort. All content will all be made available at the start of the cohort so that participants can move through content better at their own pace.

Project Members

@bsanevans (lead), @psykro (content instructor), @zoonini

Project Timeline

Start: May 1st, 2024
End: July 4th, 2024

  • May 2nd – Reach out to applicants from the last cohort about joining this cohort. Applicants who respond are added to the cohort’s SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel as cohort participants.
  • May 9th – Introductory message in Slack. Participants start working on course content.
  • May 16th – Synchronous call #1, discussing previous week’s content.
  • May 23rd – Synchronous call #2, discussing previous week’s content.
  • May 30th – Synchronous call #3, discussing previous week’s content.
  • June 6th – Synchronous call #4, discussing previous week’s content.
  • June 13th – Synchronous call #5, discussing previous week’s content.
  • June 20th – Synchronous call #6, cohort wrap-up.
  • July 4th – Archive the cohort’s Slack account.

Thumbnail Creation Project

If you’re still interested in helping create thumbnails for, feel free to check out this recording of the Online Workshop that took place on June 25, where I walked participants through the process outlined below.

In preparation for the relaunch of and Learning Pathways scheduled for July, we need to create a large quantity of small graphics – called thumbnails – to serve as featured images for each course, lesson, and tutorial. This will create a visually appealing site that will entice learners to dive in and get started on their learning journey.

We invite volunteers at WCEU’s Contributor Day on June 13 – and beyond – to pitch in and create as many of these thumbnails as possible. Even if you’re not attending WCEU in person, you’re welcome to help out. Just follow the steps below, and let the team know in the #training channel in Slack so we can recognize your contributions.

Thank you in advance to everyone who’s able to lend a hand with this group effort! We’ll keep the project going for as long as needed.


  • Create a free Figma account – required.
  • Download the Figma app – optional, as Figma can also be run in the browser.
  • Carefully read the Figma thumbnail generator guide in the Design handbook and watch the video walkthrough. (Also below)
  • Generate a couple of test thumbnails, exporting, and verify that they look as expected.
See transcript below the video here


Step 1: Choose your content

  • Open the content-tracking spreadsheet. (You’ll find the link in the Training team’s SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at bookmarks – screenshot.)
  • Working from the top down in one of the three sheets (tabs), choose a lesson, course, or tutorial for which you’ll create a thumbnail. (Ignore anything with a “Deprecated” status.)
  • Put your name in the Thumbnail by column to claim it.
  • For those who speak a language other than English, see if there are any lessons, courses, or tutorials in that language and prioritize those first.

Step 2: Create your thumbnail

Create the thumbnail by going through the thumbnail creation guide, also following these important points specific to this project:

  • Vary the colour palette and slide template style. Try not to repeat the same template or colour palette on consecutive images. Keep in mind that the order in which the content is listed in the spreadsheet is the order in which the thumbnails will appear on the site, so the idea is to vary the thumbnail styles and colours that are next to each other. The goal is to end up with something a bit random like this:

And not end up with something where there are a lot of the same colour-palette variations repeated next to each other, like this:

  • Copy-paste the course/lesson/tutorial title into the text area of the thumbnail generator, from the column that says Lesson (tutorial/course) title – for copying. It’s not obligatory to use the title in your graphic; if you find a great image to represent the course/lesson/tutorial, feel free to use one of the templates without text. (More on finding images below.) 
  • We are not using Faces or Guest names for these thumbnails. If you’ve chosen a template with any Faces (avatars), click the Faces component and click the eye icon next to it to hide it, or right-click the component and select the “Show/Hide” option in the menu.

  • Similarly, if you’re using a template with Guest names, select the Speaker component and and click the eye icon next to it to hide it, or right-click the component and select the “Show/Hide” option in the menu.

  • If you’ve chosen a template that features an image (other than the ones that feature a preselected BlockBlock 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. Editor image), replace it with an open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. image from the WordPress Photo Directory, Openverse, or Pexels. Make sure no credit is required in the image’s license terms.

Step 3: Export, upload, and record your thumbnail

  • Export your thumbnail by following the handbook instructions. Rename the file using this naming convention: yyyy-mm-dd-name-of-tutorial-or-other-content-type
    Example: 2024-06-13-introducing-the-twenty-twenty-four-theme for a tutorial titled “Introducing the Twenty Twenty-Four theme.” (Do not use any spaces or uppercase letters in the file name.) The file will automatically be given the .png extension by the generator – don’t change it.
  • Upload the thumbnail file to the Google Drive, in either the Courses, Lessons, or Tutorials folder. (You’ll find the link in the Training team’s Slack bookmarks – screenshot.)
  • In the spreadsheet’s Thumbnail URLURL A specific web address of a website or web page on the Internet, such as a website’s URL column, paste the URL from the Google Drive by clicking the three dots next to the file > Share > Copy link.
  • Leave all other columns blank, unless you receive further instructions.
  • If you haven’t been able to upload thumbnails for all the ones you “claimed” in step 1, go back and remove your name next to that piece of content so someone else can get to it.


  • Thumbnail creation guide.
  • Google Drive for uploading thumbnails – the drive has sub-folders for these three content types:
    • Courses
    • Lessons
    • Tutorials
  • Content tracking spreadsheet

For security reasons, you’ll find links to the Google Drive and tracking spreadsheet in the Training team’s Slack bookmarks:

#training team Slack - bookmarks in the "Thumbnail project" folder

Project Thread: Content Maintenance Process Update Phase 1

Project Overview

Project Objective: Create comprehensive and sustainable process for maintaining content on Learn WordPress.

Based on the feedback from Proposal: Learn WordPress Content Maintenance Process, we will align as a team on what our content maintenance priorities are for Learn, research what modern learning sites do with out of date content, utilize data to make informed decisions, and publish documentation on our content maintenance process.

Project Members

Project lead: TBD

Members: @piyopiyofox @zoonini

Project Timeline

Start: July 1, 2024

End: November 30, 2024



As the Training Team, let’s discuss and align on the follow question: What is Learn WordPress’s north star and content commitments?

  • For example, we have the WordPress Codex, Documentation, and Developer handbook sites which contain plenty of out of date content for those not on the most recent versions of WordPress. Do we really feel it’s necessary to duplicate this content further on Learn WordPress?
  • Is Learn WordPress the site where folks come to about the most relevant and up to date content on WordPress? Is it the place where we encourage and guide folks to be at the forefront of the software?

Deadline: September 15, 2024


  • What do other modern learning sites do with out of date / irrelevant content?
  • What is the current view rate for Lesson Plans and Tutorials (Document started) on Learn?

Deadline: October 31, 2024

Plan & Document

  • Develop the deprecation/out of date evaluation framework
  • Create a data-driven framework and review checklist for content deprecation inclusive of:
    • Reviewing the view stats of video content marked for deprecation (Ex. If we are seeing low viewership for certain out of date content, then we deem it safe to deprecate)
    • Have a two review process, with a third review to “tie break” as needed
    • Research what other modern learning websites (even for certain products) leave deprecated/out of date content up on their Learning sites and how do they maintain that content?
  • Set up bi-annual review cycle

Deadline: November 30, 2024