Recap of March 14, 2017 meeting

Lesson Plan Update

None.

Copyediting

@Donkiely said the Themes/Plugins Relationship lesson plan (https://make.wordpress.org/training/handbook/theme-school/themesplugins-relationship/) is copyedited but really needs someone knowledgeable in the subject to go over it. The LP seems more like an outline than a finished product.

@coachwp agreed. Paul and I worked on that and it might need more information.

@chantaboune volunteered to take a look at it.

@donkiely copyediting site performance LP.

Question regarding customizing header and background images and if it had been edited. @skarjune had fixed some problem found earlier and @estes.chris went over it as copyeditor.

Testing Updates

@coachwp did High Level Overview and One Touch Install using Bluehost and both went well. Question is being written up by @melindahelt.

Q&A/Announcements

@chanthaboune asked if we should be working to help create some movement around learn.wordpress.com work. @bethsoderberg replied: I think it would be super helpful if people workshopped a plan around how to present the completed lesson plans, perhaps a list of suggested workshops or a new teacher’s guide, etc.

@melindahelt pointed out that Trello cards can’t be edited. Thought is that it may be because people have to be granted membership, which is limited in free version. @melindahelt and @bethsoderberg will research further.

@melindahelt wondered if we would move the meeting due to DST.

Voted to vote. Discussion switched to audit of discussion times for everyone. Final decision was to meet at the same time DST.

Recap of March 7 Meeting

Lesson Plan Updates

None given.

Copyediting Updates

@donkiely: Finished the WooCommerce plan. Many changes, so a review is needed.

@bethsoderberg will mark it in need of review.

Testing Updates

@coachwp giving first session in NYC Mar. 8.

@skarjune started ongoing between workshop on WordPress Content Management with a focus group of 4 communications professionals.

This continued with a discussion of confusion between .com and .org, and between WordPress and commercial site builders. @skarjune is starting with getting a wordpress.com account as an introduction into the ecosystem. Also discussed is the differences in the admin interfaces and how that can be confusing to a person new to WordPress.

WCEU Community Summit

@chanthaboune and @bethsoderberg are trying to dig up the suggested topics from a CSV and PDF. Request for more topics.

@chanthaboune wondered if @wpaleks and @juliekuel would be available.

@bethsoderberg: one suggested topic is: Certification / Gamification / Testing / Whatever

@bethsoderberg, viewing Preview of CSV/PDF files, found several that were just titles with no description and tagged with other a bunch of other teams.

@bethsoderberg: I think it’s hard to propose much given that we know most of us won’t be there.

@chanthaboune agrees and suggest that we not have any topics but that she come as a rep proxy.

@bethsoderberg suggest a virtual “team summit” video meeting after WCEU to have an open forum with this team. Cannot talk about things discussed at WCEU because of safe spaces rule.

@donkiely: Is Trello current on what LPs are ready for copyediting.

@bethsoderberg: It is unless there are updates from last week.

@donkiely to update on some that he may grab

Recap of February 28, 2017 Meeting

Lesson Plan Updates
@juliekuehl is working on Internationalization this week.

Copyediting
@esteschris: copyediting is done on https://make.wordpress.org/training/handbook/theme-school/customizer-header-and-background-images/

Testing
@chanthaboune is pulling all the theme lessons into a workshop for Hack the Hood.

@morganestes tested https://make.wordpress.org/training/handbook/user-lessons/choosing-and-installing-a-theme/ at the OKCWP meetup Feb. 27. There’s a typo on the quiz that mixes up the right answer numbers, but the rest of the content in the lesson plan is good. The quiz is at https://make.wordpress.org/training/handbook/user-lessons/choosing-and-installing-a-theme/#quiz

Community Building
@juliekuehl suggested Certification / Gamification / Testing / Whatevs
She will be submitting it at https://wceurope.polldaddy.com/s/community-summit-2017-call-for-non-active-contributors

Q&A
@melindahelt asked about the status of the Trello board. Will ask again when @bethsoderberg is present.

Recap of February 21, 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

  • @bethsoderberg has an audit update. There are a few lessons that we’re missing updates on. Current Trello board: https://trello.com/b/zFnkQF91/wordpress-training-team-copyediting-flow
    • Let’s do a better job of sending links to lessons when we talk about them in chat.
  • @esteschris, @vmarie is also interested, @donkiely, and @meaganhanes are in need of new lessons for copyediting.
  • @esteschris: Copyediting is done on https://make.wordpress.org/training/handbook/theme-school/customizer-header-and-background-images/ and had questions about how to make images available for everyone. Chris will confirm all necessary changes are made.
    • Once we’ve edited it, do we move it on the board?
    • No, let’s do it in the weekly check-ins (either Slack or on the agenda post) so that it’s all tracked in one place.

Testing Updates

  • @coachwp’s program starts on March 8th. This program is for kids and features 6 sessions once a month.
  • Morgan Estes is testing Choosing and Installing Themes with the Oklahoma City meetup group

Updates

  • WCEU has a community summit AND a contributor day this year, so let’s figure out if we have topics we need to cover.
  • Please leave feedback on the accessibility workshop outline: https://make.wordpress.org/training/2017/02/14/accessibility-lesson-plans/
  • @esteschris and @chanthaboune will be at the WordCamp Atlanta contributor day.

Accessibility Lesson Plan(s)

Currently there is a lesson plan titled “Theme Accessibility” (https://make.wordpress.org/training/handbook/theme-school/theme-accessibility/). Upon initial testing of this lesson plan, feedback was received that indicated we should consider a user-oriented lesson and a theme-developer oriented lesson.

So the questions are: should there be two accessibility lesson plans, one for users and one for theme school? If so, what would they look like? If not, what would that look like?

Discuss. 🙂

Agenda for February 14, 2017 Meeting

The training team will be in the #training channel on Slack later today for our weekly meeting at our regular time: 20:00 UTC. If you can’t make it, please leave us a note in the comments and we’ll include your thoughts and/or updates in the meeting!

1. Welcome!
2. Lesson Plan Updates
3. Copyediting Updates
4. Testing Updates
5. Announcements and Questions

Did I miss something? Add it in the comments!

Recap of February 7, 2017 Meeting

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

Welcome

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 make.wordpress.org 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.

Goals for 2017

In 2016 we had a pretty clear goal set out for us. We haven’t had any discussions about goals for 2017, though, so now is the time!

Does anyone have something they would like to see from or for the team this year? Put your thoughts in the comments below and we’ll prioritize everything in the coming weeks!

#goals

Recap of January 24, 2017 Meeting

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

Welcome

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.

Lesson Plan Style Guide and Glossary

The Training team is reviewing the status of the Lesson Plan Style Guide and how it’s used with lesson plans, and considering if a Glossary might be added. During the January 10, 2017 meeting, some concerns were raised:

@donkiely was concerned about grammar usage, such as while/although
@estes.chris mentioned Oxford commas (serial commas)
@pbarthmaier mentioned post vs Post and page vs Page
@juliekuehl said that “We’ve avoided using one of the major style guides and have worked out our own.”
@chanthaboune indicated that @bethsoderberg keeps the styleguide current.
@donkiely has noticed: I’ve spotted several places where existing lessons and placeholders don’t comply with the style guide.”
@donkiely asked “So the main question is, too heavy handed? Or, too subtle to worry about?”
@chanthaboune said: “I’m of two minds about it. On the one hand, if it’s going to help with understanding, that’s important. But on the other, these aren’t word-for-word scripts in many cases. So getting picky for stylistic reasons seems to be a forest for the trees situation.”

The team agreed that some of these concerns are already covered in the Lesson Plan Style Guide. For example, the Grammar section details WordPress elements as regular nouns, not proper nouns, and the use of the Oxford comma before the final conjunction. The range of topics in the guide includes:

Content: Resources, Tone, Grammar
Structure: Description, Objectives, Prerequisite Skills, Assets, Screening Questions, Teacher Notes, Hands-on Walkthrough, Exercises, Quiz
Assets: Approved Themes, Images, Screenshots, Placeholders, Naming Conventions, Content Colors,
Formatting: Basic Conventions, Emphasized Text, Code Examples,
Issues
Accessibility: General Items, Links, Images, Multimedia, Abbreviations

The guide references additional resources for more detailed guidelines:

  • Anatomy of a Lesson Plan (Training companion)
  • Bloom’s Taxonomy (external PDF)
  • Approved Themes list of Twenty Twelve through Twenty Sixteen
  • Theme Unit Test Data (import file from Automattic)
  • lipsum.com (Lorem Ipsum generator)
  • Placekitten (placeholder images)
  • W3C HTML and CSS Recommendations (separate content from styling)
  • W3C’s Web Content Accessibility Guidelines

In general the team thinks that the Lesson Plan Style Guide is complete, may need some minor revisions and review, and that the main issue is that copyediting should check for consistency with both the guide and the Anatomy of a Lesson Plan reference.

Some areas for review are the use of assets, images, screenshots, and sample content, as this is where the context of various lesson plans can enter gray areas and they may add constraints for copyediting or updating the material.

While the team maintains a Training style guide, an external style guide might considered as an additional external reference. However, all major style guides, such as Chicago Manual of Style and Associated Press Stylebook, are proprietary and fee-based for online use. As an alternative, MailChimp has a MailChimp Content Style Guide available under a Creative Commons license and publicly available on GitHub:

This is our company style guide. It helps us write clear and consistent content across teams and channels. Please use it as a reference when you’re writing for MailChimp.

This guide goes beyond basic grammar and style points. It’s not traditional in format or content. We break a number of grammar rules for clarity, practicality, or preference.

We invite you to use and adapt this style guide as you see fit. It’s completely public and available under a Creative Commons Attribution-NonCommercial 4.0 International license. All we ask is that you credit MailChimp.

The team was divided about the need for a Glossary to accompany the existing resources, and whether or not we should reference an existing resource or build or own. There are two major WordPress glossaries available that could be referenced as resources:

WordPress Codex Glossary: This document is designed to offer definitions of various terms, exclusive to WordPress, that users may not be familiar with.

WordPress.com Learn Get Lingo: You’ve got a blog: huzzah! Whether you want to be a WordPress.com pro or just need to learn the basics, you’ve come to the right place.

The team suggested that Training inquire with the Docs team for information about how the Codex Glossary is maintained and used. At a recent meeting on January 10, 2017, the Docs team discussed creation of a new Glossary being performed by @normalize. Documentation Team Lead @kenshino suggested that the new format could use a Custom Post Type (CPT) for each glossary item, as they are short and can link to full Codex articles for more information. The Docs team is looking at how this would be implemented in the new Helphub.