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 https://wptrainingteam.github.io/
  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:

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.

Thoughts?

Training Team Meeting Agenda 17 May 2018

Today’s Meeting

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

Today will be a slightly different format and more of an “office hours” style. @pbrocks will be leading a discussion on:

  1. Working in GitHub
  2. Slides – Show-er
  3. Open announcements / discussion

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.

https://trello.com/c/XK6lfmsm. 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 (WordPress.org, Trello, GitHub, Slack…)

@juliekuehl: The other Trello card related to Contributor Days is this one https://trello.com/c/cxKWo7KC, 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: https://docs.google.com/document/d/1Mh0vGq075pH-CqyUbMNdrOz9AVaEUm9ofli0YrNaFsg/edit?usp=sharing.

@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.

Slides

@juliekuehl: Slides have been a hot topic for years and the issues surrounding them have been documented here https://trello.com/c/jpp5ob7t. 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 learn.wordpress.org 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.

@pbrocks: https://github.com/wptrainingteam/shower.

@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 learn.wordpress.org site

The Trello card https://trello.com/c/ck3UjgcA 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.

Thoughts?

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 https://goo.gl/forms/Tuus9yo3yWXRZgqA3 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 https://github.com/wptrainingteam/widget-areas so in Trello work flow https://trello.com/c/8dd1RKWd/130-widget-areas. 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.

Training Team Meeting Agenda 10 May 2018

Today’s Meeting

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

  1. Contributor Day materials
  2. Slides – Show-er
  3. Learn site
  4. Team survey
  5. Trello board update – slight change to workflow
  6. Lesson plans needing volunteers (see the “User Plans Ready for Drafting” list in Trello
  7. Open announcements / discussion

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:

Training Team Meeting Recap 3 May 2018

Contributor Day Onboarding

The information requested by the WordCamp EU Team for Contributor Day info can be found at https://docs.google.com/document/d/1Mh0vGq075pH-CqyUbMNdrOz9AVaEUm9ofli0YrNaFsg/edit?usp=sharing. It outlines how contributors can help the Training Team during a Contributor Day event, but it is also helpful for the team in general. The Marketing Team is also helping to create a handout specific to the Training Team that can be used to help people get started.

The learn.wordpress.org site

That site has always been the end game for the team’s lesson plans. So in this whole workflow revamp an attempt to reverse engineer our product/processes based on that being the end game was attempted. This Trello card (https://trello.com/c/ck3UjgcA) has a PDF with a few wireframes of what perhaps that site could look like. It has identified a couple of things missing from our lesson plans/workflow. We need to gather more information regarding the learn.wordpress.org site.

There was a big takeaway from that exercise. We need to be writing lesson plans with time constraints in mind. And we should be writing lesson plans that identify:

  1. Length: < 1 hour, 2 hours, 4 hours, 8 hours, possibly multi-day
  2. Audience: Speaker, User, Themer, Plugins, Developers
  3. Level: beginner, intermediate, advanced

Update on slides (Shower – show-er)

The Slides card on the Trello board has the original discussion regarding slides including the requirements and pros/cons of the various alternatives. The #accessibility team suggested https://github.com/shower/shower / https://shwr.me/

So we need to do some work on whether there are pros/cons to Reveal.js (which is what we had been considering as a solution) versus Shower (pronounced show-er). But HTML/CSS/JS still seems the best “official” alternative. Unofficial alternatives, such as Google Slides or PPT files, could be shared, hosted, used for drafting and linked to on the GitHub /slides/README.md files.

May not be the most friendly solution, but we can still allow people to create their slides using whatever tool they like best. Then one of the final tasks before publishing a lesson plan to learn.wordpress.com would be to convert the slides to Reveal or Show-er. Either way the actual slides are just HTML lists divided by sections and has the ability to “theme” the slides. Just like WordPress itself we can keep presentation separate from content.

It’s probable that it won’t be the authors creating these slides (but they can if they want to!), but perhaps a“specialized” role on team to do before “official” publishing.

Team members, roles, meetings

Random thoughts:

  • First random thought: There’s a feeling of a desperate need for a nearly all-day “summit” to talk through things and or make decisions.
  • Second random thought: A survey of members to see what their skills and interests are might be something we need to do.
  • Third random thought: Perhaps a few GitHub help sessions would be good to schedule.
  • Fourth random thought: Our meetings are a bit one-sided at the moment. It should be more of a team event.
  • Fifth random thought: We are missing quality control in our lesson plans – there’s wide variance in what we have.
  • Sixth random thought: We may need another Trello list/job description/step in our workflow to take care of that.
  • Seventh random thought: All these random thoughts reiterate the first random thought.

Training Team Meeting Agenda 3 May 2018

Today’s Meeting

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

  1. Contributor Day onboarding
  2. learn.wordpress.org site
  3. Update on slides (Shower – show-er)
  4. Team members, roles, meetings
  5. Open announcements/discussion

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:

[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 https://wptrainingteam.github.io/ 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!

Recap of April 26, 2018 meeting

Please note that unless otherwise indicated, it should be assumed Julie Kuehl (@juliekuehl) is the one speaking.

Update on Trello Board (https://trello.com/b/BsfzszRM/wordpress-training-team-lesson-plan-development).

@juliekuehl

First. In the START HERE list, the GitHub workflow card now has links to a couple of screencasts of how to work with lesson plans in GitHub. So there’s a quick overview of how to fork a lesson plan and then how to edit and commit (save changes) lesson plans.

Whether you are or aren’t comfortable with GitHub please take five minutes to see how we’d like that process to work.

Second. We’ve enabled a couple of “Power Ups” on the Trello board. These are just experiments at the moment. We are only allowed three (as far as I can tell) and we’re trying to decide which will be the most useful to the team. Ideas welcome. Trello card created for that. Make comments there.

Right now we have Custom Fields and Aging Card Power Ups, in addition to the GitHub one.

We’ll likely want to have the Slack Power Up added. (Working on that.)

There was a blog post about integrating GitHub with Slack but as it’s turning out, Trello and Slack is going to be much more useful.

If anyone has a favorite Power Up that they’d like to suggest, I’d love to hear in that Trello card how you think it would help the team!

Third. There’s a new list to the right of the board with “Team Roles”. We started talking about these at WordCamp US back in December and I think we should do some more work to flesh those out. Ideally, the description would describe the role and the Members added to the card would be the person(s) who are acting in that role currently. Many of the descriptions need to be completed. And it would be great if every team member would add themselves to at least one of the roles (e.g., copy editing, testing, etc.).

Questions and Comments on Trello Boards

@davidneeham: Who are the liaisons? People on their team or people on our team who coordinate with that other team?

@juliekuehl: Great question!!! I’ve been winding up on other teams’ Make blogs and seeing how they work and what they’ve been up to and it feels like we should be more aware of what they are doing. Lots of chances to work together!

@davidneeham: Gotcha. One of my colleagues is super active in the marketing team. I could help be the liaison there.

@juliekuehl: That’s a team that seems to be doing really interesting things!
We may have things they’d be interested in and I’ve seen things that they are working on that I think we’re pretty interested in too. Add yourself to that card then @davidneeham!

@jillbinder: What’s the role for folks like me who are creating trainings? Content creator?

@juliekuehl: I was thinking those liaison roles would be one of the Training Team members who would keep up with what’s going on over at that other team and see where there might be opportunities to benefit each other. Jill, your role of creating trainings would be under the Lesson Plan Writers role.

@juliekuehl: Design Team and Docs Team were the other two.

@jillbinder: Great work, Julie. You’re taking a huge project and breaking it down to be simple for us, bit by bit.

GitHub

@juliekuehl

One thing that was added this was was a “Repo Template” https://github.com/wptrainingteam/repo-template.

It’s meant to be our current best practice for our repos as far as folders and README files, lesson plan template, and even milestone issues. We’ll see how useful it actually is as we go along, but I think it’s always nice to have an example of what we’re shooting for.

@tmichellemoore: Did you decide on a slide deck technology?

@juliekuehl: Yes and no? The “official” slides will likely have to be in Reveal.js due to accessibility and other concerns. But the beauty of GitHub is that if other folks want to add their slide decks to the repo they can. That way they are shared for all to see or use. The final Reveal.js version may wind up being a synthesis of those and part of the final steps before approving a lesson plan for “official” publishing. GitHub is unofficial – a workspace.

The second thing that we discovered this week is that we should be working from “develop” branches and not the master branch. The screencasts that were created reflect this. Thanks to @wpnzach for figuring that out!

The third “revelation” regarding GitHub this week is that it’s probably not going to be a good place for comments. I think we may have talked about having “high-level” comments in the Trello cards and more specific questions about lesson plans in GitHub. But further thought says that if you’ve forked the repo and are dropping comments there, no one is likely to see them. So that means that most, if not all, comments should be in Trello.

And if we can get Trello integrated with Slack, then those comments will appear here and we should all see them and be able to respond as needed.

Questions and Comments on Github

@tmichellemoore: Just one – can I delete the original repository I forked? It is in my account. I want to follow the new forking process.

@juliekuehl: If you’ve forked and made no changes, you can delete that and fork again. If you’ve made changes you want to keep, it gets a little more complicated. This is something we will need to address in a screencast at some point though. It’s going to happen. Frequently.

@tmichellemoore: I changed the branch to develop before forking and it pulls both. So it appears we need to make sure we change the branch before editing.

@juliekuehl: That would be the best practice. Branch then fork. And make sure you’re editing on the new branch. (not on master).

@wpnzach: We have to fork, then branch. We can’t branch on the wptrainingteam repos. Forking the repo grabs all branches.

@juliekuehl: Argh. Sometimes having Owner privileges complicates this for me. Thanks for letting me know @wpnzach. Will make sure screencast reflects this.

Random Ideas

@juliekuehl

At the bottom of our GitHub Page (https://wptrainingteam.github.io/), there are a couple of lists that were just random ideas I had about combining lesson plans into workshops. As it turns out, those aren’t half bad. I’ve been using the Speaker lessons as guinea pigs as we’ve built out our processes.

I think we should do the same with those workshops. A small group of lesson plans to work with that we can run through the process from beginning to end to make sure our processes work. Shakedown cruise style.

What I’d like to see is the “Welcome to WordPress” lessons built out, edited, tested, and prepped for publish.

Welcome to WordPress

General History of WordPress
What Can You Do With WordPress
One-Click Install Using Bluehost
Dashboard Overview
Content Editor Overview

They are more text and screenshot oriented lessons so should be something that pretty much any of us would be “experts” in. And I believe they’ve already been drafted, but need to be reviewed now that we’re in GitHub.

Can we get some volunteers to take those on and begin editing them? They are all on the “User Lesson Plans Ready for Drafting” list in Trello. All with a deadline of today. (smile).

@tmichellemoore: When I finish editing the current one that I am working on, I can move to that list. Unfortunately it won’t be today. (slightly_smiling_face) But I should be able to start on Monday.

@juliekuehl: I may reach out to a few of you to see how we can get those moving ahead. There may not be much to do to get them over to copy editing and testing.

@jillbinder: When mine are copy-edited, will I be able to review before the edits are assimilated? I’ve got sensitive material that has been tested a lot (informally) that I’m nervous about changes to…

@wpnzach: You can “Watch” a repo to get notifications when a pull request is opened. Basically, you can get a notification whenever someone suggests a change officially, and there is a way for you to comment on it

@juliekuehl: The beauty of Git is that any change never wipes out previous information. It can always be changed back if needed. And nothing can be “pulled” unless it’s been “approved” Reviewing edits are what pull requests are all about!

@wpnzach: If you click that button (shown in Slack image) on the repo you want to watch, you’ll get an email when someone suggests an edit. then, you’ll be able to comment on the edit on the actual pull request, like this one here: https://github.com/wptrainingteam/what-to-do-when-you-forget-your-password/pull/2

Questions and Announcements

@tmichellemoore: The title in the Readme.md of the lesson I am editing is – Creating Your WordPress Talk [and Diversity Speaker Outreach]. The lesson focuses mainly on Creating Your WordPress Talk. Where does the Diversity Speaker Outreach come in? Is that an aspiration or is there supposed to be content on that? It has been throwing me off. Isn’t that really a separate topic?

@juliekuehl: @tmichellemoore and @jillbinder you should probably pass a few comments back and forth on that Trello card regarding that.

Training Team Meeting Agenda for 26 April 2018

Today’s Meeting

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

  1. Trello board overview and update
  2. GitHub overview and update
  3. Lesson plans needing volunteers (see the “User Plans Ready for Drafting” list in Trello)
  4. Open announcements / discussion

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: