Recap of March 21, 2017 Meeting

@donkiely finished copyediting Improving Site Performance LP and is looking for feedback. He notes: I’m not sure that it couldn’t use an overhaul. It takes a rather conceptual approach rather than a hands-on walkthrough. First I’ve seen like that, so I’m not sure if that’s what we want. I feel like it needs fleshing out. There are some steps that can be demonstrated and not just talked about. I suppose it’s okay as an overview, so maybe a follow-on lesson that digs deeper?

See LP at

@bethsoderberg, can you update Trello with this information?

@coachWP reported an excellent first session of his WordPress class for high school students using training team materials.

@chanthaboune wondered if we’re at a point right now where we can maybe backburner the creation of new individual lesson plans and instead focus on really getting the workshops into a polished state. The idea being that if we have them polished up and useable, we may get more proof of concept after they are used/tested.

@melindahelt shared as a potential way to have some tech workshops create and install WordPress to have a local install to work on.

@donkiely will work on auditing lessons that have not been copy edited since the last release to flag any lessons that should be updated based on the new features.

Recap of February 14, 2017 Meeting

Slack log (requires Slack login to view. Set one up if you don’t have a Slack account).

Lesson Plan Updates

Copyediting Updates

  • @donkiely finished copyediting the template tour plan and is currently working on copyediting the WooCommerce plan
  • @skarjune finished copyediting the widget areas plan and it is ready for testing.

Testing Updates

From @melindahelt: We had 5 in attendance. No real theme developers, so I presented the same information but highlighted the user side of the application (selecting H1, H2 in editor vs coding into a theme).

Overall, the content was great, but it did feel a little basic for a “theme” lesson plan.

We did have a blind software developer attendee who came specifically to learn more about WordPress. We took advantage of having a subject matter expert and launched into a larger discussion/Q&A after the presentation, which was enjoyed by all.

One specific suggestion from the software developer was to include at least a mention of form accessibility. Even though this is just a taste of accessibility, that’s an area where things can go wrong very quickly and a form can be completely un-accessable to screen readers.

A second attendee sent me the following after our meeting:
1) A skip navigation link.
Once someone has screen read the navigation/menu a number of times they no longer need to hear it. Insert near the top of the html a link <a class=”screen-reader-tex­t skip-link” href=”#MainContent” title=”Skip to content”>Skip to content</a>, and then just before the content <a name=”maincontent” id=”maincontent”><­/a>
See­ for a more detailed explanation.

2) Include an audio file of a screen reader reading an html page.
Perhaps done by having the page with an audio button, so the user can see what the screen reader is reading.
I was already thinking a little bit about suggestion #2. We talked about screen readers and the blind developer offered to do a demo for us some day. But, perhaps a video/audio clip showing a screen reader as it navigates through a page would be a helpful resource. I know there’s way to turn that on with some operating systems, but having something ready to go for instructors would be helpful.

  • Given this feedback, we talked about expanding the plan to have a separate plan for users and one for theme developers. We also talked about pushing this out into a full workshop and will talk about this on the blog and in next week’s meeting.

Other Things

  • @donkiely noticed that the Storefront theme used in the WooCommerce plan is not included in the style guide. We decided to change the style guide to say that Storefront is “approved” for WooCommerce lesson plans, but to make sure that people know that other themes can be used with WooCommerce. We also double checked that Storefront is GPL compliant.

Recap of February 7, 2017 Meeting

Slack log (requires Slack login to view. Set one up if you don’t have a Slack account).


Lesson Plan Updates

  • @bethsoderberg had a friend reach out about a plan to work on and will suggest the enqueueing scripts plan, with @pbarthmaier on point to answer questions
  • A note from @chanthaboune to review on our current focus: “When we thought about what it meant to have lessons for a certain subset of plugins, we realized it was more of an endorsement than we first thought, so we put those on hold to focus on themes and will revisit it after that.”

Copyediting Updates

  • @bethsoderberg is continuing to move information to the new Trello board and has found tons of loose ends, but since this is an intensive process to go through our archival data will come back with a full list of loose ends once she’s gone through everything.
  • @skarjune has completed copyediting of Customizer: Taglines, is almost done with Building a Sitemap, and will move on to Widget Areas after that.

Testing Updates

  • @melindahelt is doing the accessibility plan tonight at the Pittsburgh meetup
  • @chanthaboune has continued to work with Hack the Hood on our next workshop with them and it’s looking like one might happen late in March or early in April

Edit Flow

  • @chanthaboune talked to the meta team about Edit Flow and when we last talked it was very much one of those things they don’t really have the bandwidth to add + maintain for our work. It was left with sort of an open-ended “but that’s not a never” sort of sentiment, so we left the discussion fairly open as well.
  • In general, we discussed it and came to the conflusion that we can’t have a plugin right now and need to move forward with other ways of streamlining our workflow.
  • @bethsoderberg is moving archival data into Trello as a next step towards making tracking of work easier. In the meantime, please continue to add updates to the spreadsheet. We’ll talk about it as a group when it’s time to send the spreadsheet out to pasture.

Team Description on Meta Site

  • @rocio from the Community Team and she is working with the Meta team on the redesign of the page and they need a shorter version of the team descriptions. They are using this as an opportunity to re-think and update those descriptions.
  • In our meeting we voted to approve the following description of our team: We create lesson plans for instructors to use in a live workshop environment.

Recap of January 24, 2017 Meeting

Slack Log (Requires Slack login to view. Set one up if you don’t have a Slack account)


Lesson Plan Updates

Copyediting Updates

  • @donkiely will copyedit Templates and Woocommerce
  • @estes.chris believes Site Icons and Logos is copyedited already
  • @skarjune will edit Customer: taglines, Widget Areas, Building a sitemap
  • @danstramer will edit Help Regenerate Thumbnails
  • @bethsoderberg suggested Trello for tracking copyediting and will put together a draft list of status’s by next week’s meeting. Someday this might be replaced by Edit Flow
  • We had a discussion around the capitalization of code in titles. The consensus is if the snippet isn’t capitalized in the code, don’t capitalize it in the title of a plan.

Testing Updates

  • @melindahelt will test the theme accessibility plan in February
  • @estes.chris is training a client in content management in a week or so and will try to work in some beginner plans.
  • @skarjune is assembling a focus group for Getting Started training to start mid-Feb. in a weekly format with some professionals as students that could include: writer, art critic, entrepreneur, graphic designer, corporate trainer.

Recap of January 3, 2017 Meeting

Lessons in Progress

Speaker Lessons/ @coachwp
Intro to Common Plugins/ Carol Stambaugh
Basic Theme Config/ @chmchm
Theme Documentation/ @estes.chris
Themes/Plugin relationships/ @coachwp
Theme a11y/ @juliekuehl
Theme i18n/ @danstramer

@juliekuehl should have Theme A11Y done next week


Discussed proposed edits by @estes.chris to Customizer: Site Icons and Logos, Customizer: Header and Background Images. @estes.chris will update screenshots based on edits to Header and Background Images LP.

Copyediting in Progress
Content editor overview (lots of suggested changes)/ @librariancrafter
Basics of WP (lots of suggested changes)/ @patcosta
Static Front Page vs. Content Feed/ @donkiely
Managing Menus/ @donkiely

Copyediting Complete
Web Fonts/ @noplanman
Forgotten password/ @estes.chris
Dashboard overview/ @yvbrooks and Carol Stambaugh


  • @coachwp is working on an after school program for high school students that will start in February and will be using some training team materials
  • @chanthaboune will add the Theme and Accessibility lesson plans to the Ready to Test page

2017 Goals


  • Training Team badges should now be active on profiles. If you don’t have one, let @bethsoderberg know.
  • The WCEU team is looking for someone who is attending WCEU and wants to rep the training team at contributor day. Let @bethsoderberg or @chanthaboune know if interested.

Recap of Dec. 13, 2016 Meeting

Lesson Plan Updates

@juliekuehl is working to revise the accessibility lesson plan based on feedback from Joe Dolson

@coachwp is working on finalizing the speaker lesson plans

@donkiely has finished reviewing settings, including updated 4.7 screenshots. Notes are included on the post.

@melindahelt and @bethsoderberg will review edits to child theme lesson plan.

Copy Editing

If you’d like to copy edit any of the following plans, please comment below.

Customizer: Taglines/
Static Front Page vs. Content Feed/
Site Icons and Logos/
Header and Background Images/
Managing Menus/


@chanthaboune has a resource for testing the accessibility lesson plan when it’s ready.

Other Updates

If you haven’t posted your WCUS Contributor Day updates to, please do so.

If you are an active member of the training team and do not have a training badge on your .org profile, please DM @bethsoderberg with your .org username/email address and she’ll add you to the list.

Recap of Nov. 22, 2016 Meeting

Lesson Plan Updates

@coachwp is done with Theme and Plugin Relationship Lesson Plan and it’s ready for copyediting

@bethsoderberg and @melindahelt will review child theme lesson plan revision and related questions

Copyediting Updates

@bethsoderberg will update copyediting list in time for WCUS
@c3zh will copy edit customizer: header and background images

Team Rep Elections

All Make teams are working towards having yearly elections for team representatives
@chanthaboune will draft a P2 about roles and responsibilities and we’ll discuss as a group at WCUS


The plan is to have a few meetings to discuss broader team issues, for those that want to participate and a list of priority lesson plans for contributors to write and/or edit.

Broader issues include:
1. Developer Training
3. Lesson plan priorities
4. workshops
5. team reps

@bethsoderberg will update the copyediting worksheet

@chanthaboune will update (or will advise who will) the lesson plan priority sheet

The Training Team will meet at the convention center (same area where Contributor Day is taking place) at 9 a.m. for coffee/getting to know each other time. The meetup is BYOC (bring your own coffee or other beverage of choice)

Recap of Nov. 15, 2016 Meeting

Lesson Plan Updates

@skarjune – Customizer: Header and Background Images is Ready for Copyediting is ready for copyediting

@melidnahelt – Customizer: Site Icons and Logos is ready for copy editing

@bethsoderberg offered to look at Child theme revisions with @melindahelt

If anyone wants to give a lesson plan back, let @bethsoderberg or @chanthaboune know. If anyone has “priority” themes assigned to them and they know they won’t get to it, let us know so that we can perhaps have someone work on them at WCUS

@melindahelt asked about status of plugin lesson plans and it was decided that we will discuss direction at WCUS

Copyediting Updates

No updates during the meeting. If you have any updates, please post in the comments.

Testing Updates

@melindahelt tested the updated Child Theme LP at Pittsburgh meetup, but requests that someone else tests it as well for a second set of eyes (after it’s been edited)

@chanthaboune: “What is Open Source” and related lessons might get pulled into a workshop soon to use as an educational resource that is platform agnostic.

WCUS Contributor Day

If you have not commented on the P2, please do:

Our goal is to have a concrete list of priorities going into Contributor Day so that we can make the day as productive as possible.

Team Reps

@chanthaboune proposed the question of electing new Team Leads and explained “By electing team reps, I mean that we’ll have nominations (ostensibly that will be from people on the team currently) and then the top two voted on folks will become co-reps for the year.”

Look for information/P2/Discussion at WCUS to follow with additional information and responsibilities for team leads.

WCUS Team Meetup

We had a discussion about having a team coffee at some point over the weekend and the group seems to be leaning towards meeting at the convention center at 9 a.m. on Sunday just before the start of Contributor Day – BYOC (bring your own coffee), but please share any/all thoughts/comments below.

Recap of November 1, 2016 Meeting

Slack Log (Requires Slack login to view. Set one up if you don’t have a Slack account)

Lesson Plan Updates

  • @meaganhanes‘ plan is in progress
  • @coachwp is giving his plan one last look over and then it will be ready for copyediting
  • @melindahelt worked on updating the child theme plan to cover the Twenty Sixteen theme and will update the plan once she tests her work at the Pittsburgh meetup tonight.
  • @pbarthmaier is aiming to have the Duplicator plan finished for next week.
  • @juliekuehl started to the theme accessibility plan at a contributor day last weekend and had some questions about scope of the plan. We talked about it and she is going to approach it as an intro plan that is more like six-quick-things-you-can-do-today rather than all of the possible accessibility things that could be included in a theme building workshop.
  • @estes.chris updated the MAMP local install lesson plan and @chanthaboune will look over the edits to the plan.
  • @estes.chris asked about how we deal with major WP updates, which is timely because 4.7 is going to be the first major stress test of our current system, which is: audit, flag out of date lessons, update lessons.

Copyediting Updates

Testing Updates

  • @melindahelt is doing some tests today at the WordPress Pittsburgh meetup
  • @chanthaboune is compiling feedback from the most recent Hack the Hood workshops

WordCamp US Contributor Day Planning

  • Please comment on our P2 post regarding what you’d like to see on an agenda for WordCamp US’s Contributor Day. We’ll take all of the feedback on this post and work on hashing out an agenda in next week’s meeting.
  • We talked about tackling conversations that may be easier to have in person and having specific tasks prepared for newer contributors. We also talked about having someone live updating our Slack channel if video communication with remote team members is not possible.
  • Big potential topics of discussion mentioned included: lesson plan/workshop development (to include developer training), website, planning for learn, etc.

Other Things

  • @mindsize started a discussion about editorial workflow and will write a post on the blog here so that everyone can read a more concise version of the backscroll on this topic and contribute to the larger conversation.

Recap of October 25, 2016 Meeting

Slack Log (Requires Slack login to view. Set one up if you don’t have a Slack account)

Lesson plans in progress:

Customizer: Menus/ @mindsize
Templates/ @juliekuehl
Themes/Plugins Relationships/ @coachwp
Customizer: Site Icons and Logos/ @melindahelt
Basic Theme Configuration/ @chmchm
Theme Documentation/ @meaganhanes
*How to Find Theme-Specific Documentation/
*Customizer: Header and Background Images/ @skarjune
*Theme Troubleshooting/
Theme Accessibility/
Theme Internationalization/

Lesson Plan Updates:
Theme Documentation by @meaganhanes and Customizer: Site Icons and Logos by @melindahelt are partially done

@pbarthmaier offered to help @coachwp work out a few issues with his lesson plan

Copyediting in progress:
What is Contact Form 7 /@estes.chris
What is Google XML Sitemap / @pauloyler
building a sitemap for a site /
Improving Your Site’s Performance / @mindsize
What is W3 Total Cache /
Dashboard Icons (higher priority than the others) / @pbarthmaier
Help Regenerate Thumbnails /
Template Tour / @estes.chris
Customizer: Static Front Page vs. Content Feed/ @c3zh
Templates /

Copyediting updates:
@bethsoderberg will be able to jump back into copy editing after US Election

@pbarthmaier has completed first pass at copy editing and reached out to @epetrashen for clarification

@mindsize is leading discussion to scope out a plugin for tracking copy editing. The general thought is that lessons would follow this progression: Pitched > In Progress > Needs Editing > Editing In Progress > Editorial Peer Review > Ready to Publish > Published> Tested

then, depending on the outcome of the lesson plan test:
Needs Editing > Editing In Progress > Editorial Peer Review > Ready to Publish > Published > More Testing

This process will formalize the informal review process that’s been in progress for a long time:
“The peer reviewer pushes it into the publishing queue for final review by someone with publish permissions, and that publisher gives it one final overall review to decide if there is anything missing or unclear before it is published. Also, adding peer review ensures that there is never a way to get anything through the entire process without having three sets of eyes on it.”

Look for a future P2 post, or share your comments below on this proposed copyediting process.

Testing Updates
@melindahelt will test Child Themes at Pittsburgh Meetup next week

WordCamp US Contributor Day
@bethsoderberg to check on feasibility of doing a video hangout with team members not in attendance

So far, @juliekuehl, @melindahelt, @bethsoderberg, @pbarthmaier, @c3zh and maybe @courtneyengle will be in attendance.

@bethsoderberg will start a P2 post to brainstorm priorities for contributor day

Discussion about if the current time (3 p.m. EST) still works for people and should remain after Daylight Savings Time ends. For now, consensus of those in attendance is meeting will remain the same, but please comment below if you feel differently.