Proposed Handbook Outline


  1. About
    1. What we do
    2. Origin story
    3. Vision
    4. Tasks
    5. Team leadership
  2. Get Involved
    1. First steps
    2. Contributor Day
      1. Organize
      2. Participate
    3. Areas to contribute
      1. Present a lesson & Feedback
      2. Write a lesson
      3. Review lesson plans
      4. Other
  3. Communication
    1. Meetings
      1. agenda/notes etc P2
      2. Slack
    2. Trello
    3. Github
    4. Creating meeting notes
  4. General Guides
    1. Style Guide
      1. Tools (screenshots)
      2. Lesson plan
        1. Template
        2. Example
      3. Slides
        1. Template
        2. Example
    2. Presenting
      1. Single plans
      2. Workshop
  5. Roadmap
  6. Learn WordPress site
  7. Resources
  8. FAQ
  9. Old lessons (until Learn launches)

Training Team Meeting Agenda 7 June 2018

Please join us at 19:30 UTC in the #training Slack channel for our weekly meeting!

Today’s Meeting

  1. Design of Learn site
  2. WordCamp EU Contributor Day preparations
  3. Recruitment
  4. Lesson Plan Example: Anatomy of a Theme
  5. Videos
  6. Open announcements / discussion

Welcome to @Govind Kuman @drpepper2soda @njwrigley @abhijitrakas and @grimlord1 who joined the #training Slack channel this week!

NOTE: The “Welcome” item has been removed from the agenda. You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.

Training Team Mission

The WordPress training team creates downloadable lesson plans and related materials for instructors to use in live workshop environments.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

Team Links:

Proposed Change to Lesson Plan Template

The Training Team has been using the same lesson plan template for the past few years. It works well! I would like to suggest just a couple of improvements to make to more understandable, to provide some additional information about the lesson plan, and to help keep the emphasis on it being a lesson PLAN intended for instructor led training such as meetups, WordCamp workshops, or other such events. (Our focus is not on building online tutorials). Since we are rebuilding many lesson plans from the ground up at the moment, this seems like a good time to make this change.

Current Lesson Plan Outline

1. Description
2. Objectives
3. Prerequisite Skills
4. Assets
5. Screening Questions
6. Teacher Notes
7. Hands-on Walkthrough
8. Exercises
9. Quiz
10. Additional Resources

Proposed Lesson Plan Outline

1. Description
2. Objectives
3. Time Estimate
4. Prerequisite Skills
5. Teaching Materials
6. Readiness Questions
7. Teaching Strategies
8. Teacher Notes
9. Lesson Overview
10. Exercises
11. Differentiation Strategies
12. Assessment
13. Additional Resources
14. Hands-on Walkthrough

What Changed?

  • “Time Estimate” is added (and will be confirmed or changed base on testing experiences)
  • “Assets” is renamed “Teaching Materials” to be more understandable
  • “Screening Questions” is renamed “Readiness Questions” to be less intimidating
  • “Teaching Strategies” is added to help identify the best way to convey the material
  • “Lesson Overview” is added to provide a true plan for the lesson
  • “Differentiation Strategies” is added to provide ideas on how to accommodate different learning styles and speeds
  • “Quiz” is renamed “Assessment” to be more about whether the objectives were met and less about whether students “passed”
  • “Hands-on Walkthrough” is moved to the bottom so that the Exercises, Assessment, and Additional Resources don’t get overlooked, and to somewhat de-emphasize it.

I took the liberty of testing out the proposed template for the Content Editor Overview lesson plan if you want to see an example.


Training Team Meeting Agenda 24 May 2018

Please join us at 19:30 UTC in the #training Slack channel for our weekly meeting!

Today’s Meeting

  1. Trello board review/update
  2. GitHub review/update
  3. WordCamp EU Contributor Day preparations
  4. Workshop project (see the bottom of
  5. Team update
  6. Open announcements / discussion

Welcome to @GetITWorking and @gloryw who joined the #training Slack channel this week!

NOTE: The “Welcome” item has been removed from the agenda. You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.

Training Team Mission

The WordPress training team creates downloadable lesson plans and related materials for instructors to use in live workshop environments.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

Team Links:

Recap of May 10, 2018 Meeting

@juliekuehl: First up today is the Contributor Day info. That is a card that should be useful to anyone who wants to help with the training team during a contributor day. The marketing team graciously helped to create a Training Team specific onboarding document, which is uploaded to that card.

@juliekuehl: It has just basic info on which accounts would be needed to help the team (, Trello, GitHub, Slack…)

@juliekuehl: The other Trello card related to Contributor Days is this one, which is specific to WordCamp EU in June.

@chetan200891 @davidneeham is there anything else that you would need to lead that effort? I know we’ll need a list of lesson plans that would be good ones to work one. That’s a rolling list though.

@juliekuehl: This document is also meant for Contributor Days, but it’s going to be helpful for anyone new to the team:

@juliekuehl: There are several options there on how to jump in and get started.

@juliekuehl: So with that Google Doc in place (and it should move to the Make site before WCEU) I think we have what we need for Contributor Days now. So I think if anyone wants to represent the Training Team at any Contributor Day, we have materials to help them do so.


@juliekuehl: Slides have been a hot topic for years and the issues surrounding them have been documented here We had talked about using Reveal.js as our solution for slides, but recently had the #accessibility team recommend Show-er. I did run it by a meta team person as to whether that would work on the site and got a thumbs up.

@juliekuehl: So I wanted to be clear that our slide solution at this point is Show-er, not Reveal and we’ll get some documentation and workflows put together around that.


@juliekuehl: Ideally we would have one stylesheet for all the slide decks that could be updated and all that would be needed is the markup (HTML?, md?) file.

Learn.WordPress.Org Site

@juliekuehl: So that’s it for item 2 on the agenda, but it leads into item 3 – the site

The Trello card has some information on it as to how we can get started to design and actually start using that domain.

@juliekuehl: We need to create a Trac ticket for the #meta team and alert #design and #marketing to get their input too. There are some wireframes on that Trello card too as a rough concept of what that site could look like. But the idea would be to be able to push lesson plans from GitHub to the Learn site. (which may mean we need to slightly adjust how we are working with the master branches).

@juliekuehl: I can get that Trac ticket started as I would think it would be weeks/months before all the details would be worked out and we’d be able to actually get things together for that.


chetan200891replied to a thread: But the idea would be to be able to push lesson plans from Git: You mean embed. Correct?

@juliekuehl: That’s some of the details that would have to be worked out by the #meta team.

@juliekuehl: Just so everyone is aware, both the Make blog site and the Learn site are not your typical WordPress installs and they have quirks and restrictions that we have to work within. The #meta team are the ones that can help us navigate that.

@juliekuehl: I wanted to wait until after today’s meeting to get that Trac ticket started. So if you have any thoughts about it, please either DM me or drop your thoughts on the Trello card or here in the #training channel. I’m sure it will take me a few days to write it up and get it submitted.

Team Survey

@juliekuehl: We have gone through so many changes in the past few months and there are many new faces here in the channel. I will admit to having lost track of who is all here and what brings them to the team.

@juliekuehl: Apologies, since I know I’ve chatted with several of you. But I think it’s time to get a little more information from folks regarding interests and skill.

@juliekuehl: I would like to ask everyone to consider filling out the information here just so we have a better understanding of what you are interested in and able to help with. This is an optional form. You are not required to participate, but it would sure be helpful , to get the work of the team moving forward. Currently the info is restricted to just team leadership (there’s about five of us).

@tmichellemoore: @juliekuehl Would you be able to summarize the changes? I understand the team has been around for a while but am just curious as to why so many changes in the short time I have been here. I am not averse to change, just trying to gauge is it constant or was there something that happened recently?

@juliekuehl: The underlying big change was the move to GitHub. There were many reasons behind it: the loss of our image assets on the Make site, the difficulty in managing the lesson plan workflow, the difficulty in maintaining them and keeping them up to date, and there was no “workspace” everything was publicly available as it was being worked on (people were finding old, half-written info and that’s not good), and last, the Make site was intended to be a handbook (like every other team) – not the place lesson plans were actually published.

@juliekuehl: We made the decision to move probably around the time of WordCamp US and started in earnest around the first of the year.

@juliekuehl: And we had two of the three meeting leaders step away for a few months so there were changes due to that too (meaning I had no idea how it was supposed to be done, so I just made something up)

@pbrocks: Really, we have been talking about this for close to a year, it seems, and we all agreed that what we had wasn’t working and at WCUS, i was able to get FINAL confirmation that the images weren’t ever coming back. so in our meeting that Sunday we went forward full steam.

@juliekuehl: Thank you for asking @tmichellemoore. I really should put that in a blog post for the record.

Trello and LP Workflow

@juliekuehl: After looking at scores of lesson plans, I realized what a wide variation we have in approaches and quality. I think we need a QA step before copyediting. I added a “Lesson Plans Needing Instructional Review” list to the board.

@juliekuehl: Before having folks go through with a fine-toothed comb looking for typos, grammar, and style, I think we need a forest and not tree review to make sure the lesson plan fits the team’s goals. For instance, @Taylor found two duplicates already. No sense in pushing both of them forward.

@juliekuehl: And if there are any instructional designers here today, Bloom’s Taxonomy standards are lax and objective – assessment connection is practically non-existent in some of them.

@juliekuehl: Now that I think of it, there’s a new role for the team that’s not listed on the Trello board. So if you have any education / instructional design background, that would be a very good place to help out.

@tmichellemoore: I actually have a masters in instructional design.

@tmichellemoore appointed to take control of the list.

Many LP’s lacking Owners

@juliekuehl: Some need to be written from scratch while others need to be updated/rewritten – or possibly just quickly reviewed and pushed forward.

@juliekuehl: Just add yourself to the card as a Member and type your name in as Current Owner on the card and have at it. If you need any help with any part of the process, this is the place to ask!

@juliekuehl: I know it took us a while to get the GitHub workflow sorted out (and we may have just changed it slightly this morning) but we should be good to go now.

@chetan200891: I have worked on this so in Trello work flow Can i check first 3 development checklist?

@juliekuehl: I would say only the first one.

@tmichellemoore: I have a few questions on process: I got a merge notice. I needed to add one more thing to the lesson.
If I had anything I needed to add, could I have added it before the merge or should I wait until the merge request goes through?
Who does copyedit #2?
What do I do with the card once I finish copyedit #1?

@juliekuehl: The reason there are two copy edits (and three testing rounds) is to simply have more eyeballs on the lesson plan. We’ll need to address the whole multiple branches / rebasing / etc. issue (hint hint @pbrocks).

@juliekuehl: But as far as copyediting goes, when you’re finished (meaning the pull request has been merged) we’ll need someone else to step up for the second round and do the same.

@pbrocks: When you have a branch and you do a Pull Request which is a request to merge, like @tmichellemoore is asking about they will get applied to the original pull request. IF you want them to be separate, then ou create another branch.

@juliekuehl: A video is needed to demonstrate / explain

Meeting Time

@juliekuehl: I have one final question before I have to bolt out the door… would moving this meeting up 30 minutes be a problem? Then I wouldn’t have to leave so quickly every time. I may schedule it a half hour earlier next week and see what happens.

[Crosspost] Training Team Update 26 April 2018

Transcript in Slack

New Trello Board

WordPress Training Team Lesson Plan Development

There are new lists on the board, new cards in lists, and new information on cards.

  1. The START HERE list now has a GitHub workflow card with screencasts of how to work with the lesson plans in GitHub.
  2. There are some Power Ups enabled on the Trello board that we are experimenting with. GitHub, Slack, Custom Fields are likely the ones we’ll keep, but we also looked at Card Aging. (We are limited to three.)
  3. There’s a new list on the Trello board for Team Roles with a card for each role. Descriptions need to be completed and members who are contributing in that role added to the cards.

GitHub Update

WP Training Team

The lesson plans are all in GitHub as separate repos.

  1. There’s a new “repo-template” repo that is meant to be an example of how to set up new lesson plan repos.
  2. The workflow for working on lesson plans has been tested and documented (somewhat). There’s information in Trello on the current workflow.
  3. Rather than commenting in Github, comments are likely better done in Trello.

Lesson Plans in Focus

At the bottom of the GitHub Page there were some ideas on how to combine lesson plans into workshops. The lessons for the “Welcome to WordPress” workshop are our current focus and will be used to further test our new tools and processes. Volunteers needed to help with those!

Special Meeting 19 April 2018

Please join us at 19:30 UTC for a special presentation!

There have been a lot of changes to the Training Team’s tools and workflow recently. A presentation to go over all the changes is going to be a better way to communicate them than our usual Slack chat. Therefore, this week’s gathering of the Training Team will video presentation (webinar) style. We will be going over the new Trello board and the GitHub repositories and how they (and us!) will work together.

So join us at the usual time but in a slightly different location. We will be using the Zoom meeting service, and a link for the event will be posted in the #training Slack channel shortly before the meeting time. The presentation will be recorded.

If you have any questions (before, during, or after) please ask in Slack! Expect homework assignments!

Team Links:

  • Getting Started ( a little out of date at the moment
  • Our Team Blog (
  • Our Roadmap (
  • Our Lesson Plans (

Automated Greeting in the #training Slack Channel

It is possible that we could set up a Slackbot to send a greeting when new people join the #training channel. (Hat tip to the #design team for this idea.) What would we want to see in that message?

Proposed content (add your ideas in the comments below!):

Welcome to the WordPress Training Team! We create downloadable lesson plans and related materials for instructors to use in live workshop environments. This all-volunteer team needs people with all kinds of skills!

Here are some handy links to get started in our community:

  • The Make WordPress Training blog is where you’ll find meeting agendas and summaries
  • We communicate in the WordPress Slack #training channel. If you have questions, this is the best way to contact the team.
  • Check out our GitHub page to get an overview of what the Training Team is working on.
  • Take a look at our GitHub account where the actual work is done. You can find our in-progress lesson plans there too!
  • We have more details in our handbook
  • Finally, introduce yourself in the #training channel on Slack. It would be great to know where in the world you are located, what brings you to the training team, what your skills/background might be, and how you would like to contribute!

Great to have you onboard 🙂

(Note that the actual bot will need to be created by a WP Slack Admin.)

Slack Integration with the Team GitHub Account

Since we are moving our team’s workspace to GitHub, it is possible to connect GitHub with the team #training channel in Slack. We would be able to get notices when activities take place in GitHub. What activities you ask? Things like:

  • issues
  • pulls
  • statuses
  • commits
  • deployments
  • public
  • reviews
  • comments
  • branches
  • commits:all

We can choose which of these, if any, we think would be useful to be notified of in the Slack channel. We can turn them on or off as needed if the are/aren’t working for us.

Is this something we want to do? Now? Later? All of it? Some of it? Please share your thoughts in the comments below!

(More info available at

Meeting Agenda for Thursday 12 April 2018

Please join us at 19:30 UTC in the #training Slack channel for our weekly meeting!

A brief agenda for the meeting:

1. Welcome
2. Discussion on verification workflow in GitHub
3. Discussion on lesson plan development in GitHub
4. Updates on other current projects
5. Open announcements/discussions

If you have any other items to add to the agenda, please list them in the comments. If you have progress updates but will not be able to make the meeting, please comment on this post or leave a note for the team in Slack. We’ll see you soon!