WordPress.org

Make WordPress Training

Welcome to the WordPress training team

The training team creates downloadable lesson plans and related materials for instructors to use in a live workshop environment. If you enjoy teaching people how to use and build stuff for WordPress, immediately stop what you’re doing and

join our team!

Contact Us

There are a few ways to connect with us

Get Involved

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • bethsoderberg 2:12 pm on August 1, 2015 Permalink |  

    Recap of July 31 Slides Meeting 

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

    We held a special meeting to discuss the subject of lesson plan slides.

    Background

    Last year at the community summit we discussed the inclusion of slides and were able to lay out some of the bigger concerns about using them. Since then we have tried a few different things along with coming up with a basic list of what we would want if we had a plugin. Most recently there has been an attempt to use the photoshop comps made about a year ago and try them as google slides. This would have still been a stop-gap measure as many of the concerns brought up are really only solvable via a plugin. Concerns the team has discussed related to the slides include:

    • accessibility
    • backwards compatibility
    • reuse
    • learning curve
    • lack of internet
    • design consistency between different sets of slides
    • maintainability
    • ease of updates

    We’ve discussed the plugin many times over the past year including in January.

    Pros and Cons of Google Slides
    Pros

    1. The platform is similar to something many are familiar with as it’s much like PPT or Keynote.
    2. Allows color changes that would address accessibility issues.
    3. Allows offline mode and downloading of PDF versions.
    4. Allows for submission of template on Google Slides’ “repo”.

    Cons

    1. There is no way to import the lesson plan content automatically as updates occur.
    2. May be hard to use.
    3. Seems to require fixed aspect ratio.
    4. Keeping design consistency from slide to slide, even with the master template, seems impossible to control with lots of people editing since you can just drag and drop elements on each slide.

    The Reveal Option
    Reveal came about as an idea after @bethsoderberg‘s initial HTML/CSS cutup earlier this year failed because of the impossibility of controlling vertical height issues. Reveal is just HTML, CSS, and JS and accounts for the slide height issues and theoretically it could also be integrated with a plugin.

    Suggestions
    @courtneydawn suggested a course of action moving forward that was discussed and agreed to by meeting attendees:

    1. We go back to creating a document that serves as a requirements definition doc for our pretend plugin.
      This will allow us all as a team to say what we think are necessary functionalities of our dream slide plugin
      and what would be just nice to have. We finish this by the time WCUSA comes around so we can workshop it with other teams and see if there are people out there who can help us.
    2. Rework the Google slides (if there is a volunteer) with no design components so that we can see what happens when the aesthetic functionality is not an issue. (@melindahelt volunteered to take this on with her most recent set of slides)
    3. See if someone who is going to do a test of one of our plans wants to create a set of slides of either Google or Reveal nature.

    The overarching goal here is to create a series of functional test cases to look at together so that we can all discuss at WCUSA.

    Moving forward @courtneydawn will lead a slides conversation every other week in the weekly team meetings that will establish the scope required for a plugin as well as enable the team to have a true sense of the universe of needs and issues with the slides so that we can make informed decisions at WCUSA.

     
  • bethsoderberg 2:55 am on July 29, 2015 Permalink |  

    Recap of July 28, 2015 Meeting 

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

    1. Welcome and recap of last meeting
    2. Lesson plan updates
    3. Testing updates
      • @stephs8919 is testing the WordPress Basics lesson tonight.
      • At the end of the meeting we talked about the possibility of soliciting student feedback when testing lesson plans. Though we generally agreed that student feedback would be useful, we also identified a number of challenges to getting such feedback (added complexity reducing overall feedback submission rates, challenges of automating something, possibility that it might be easier to get feedback from students than presenters)
    4. Slides
      • We decided to table the slides conversation and have a separate meeting to discuss slides this Friday, July 31, at 17:00 UTC.
    5. Review initial Contributor Day process
      • @courtneyengle spoke with #outreach and there was a sense from that team that connecting participants to Slack and the larger “getting started” materials is happening at these contributor days already and that there is nothing extra that we should be doing to make sure that part happens.
      • We should use our Getting Started page to include anything we need for onboarding contributor day contributors.
      • We briefly reconsidered our initial brainstorm and decided that the general ideas behind it still apply, particularly the timed messages on Slack for contributor days.
     
  • Courtney Engle Robertson 5:00 pm on July 27, 2015 Permalink |  

    Agenda for July 28, 2015 

    1. Greetings
    2. Recap of last meeting
    3. Lesson plans status and questions
    4. Testing status and questions
    5. Slides update
    6. Review initial Contributor Day process
      1. Get Started page
    7. Questions

    Please add any additional agenda items in the comments!

     
  • Courtney Engle Robertson 4:23 pm on July 21, 2015 Permalink |  

    Recap of last meeting July 21 2015 

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

    • Recap of last meeting
    • Lesson plans status and questions
    • Testing status and questions
      • @melindahelt shared her lesson plan testing experience with Dashboard overview and High Level Overview
    • Slides update
    • Slides – Master view to tweak updates
    • Review initial Contributor Day process 
    • Questions & Misc
      • Welcome Wagon members will communicate together on who reached out to new members to avoid duplication
     
  • bethsoderberg 3:13 am on July 21, 2015 Permalink |  

    Agenda for July 21, 2015 

    1. Greetings
    2. Recap of last meeting
    3. Lesson plans status and questions
    4. Testing status and questions
    5. Slides update
    6. Review initial Contributor Day process
    7. Questions

    Please add any additional agenda items in the comments!

     
  • bethsoderberg 5:43 pm on July 14, 2015 Permalink |  

    Recap of July 14, 2015 Meeting 

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

    1. Welcome and recap of last meeting
    2. Lesson plan updates
    3. Testing updates
      • @melindahelt has testing feedback that she will submit this week.
    4. Slides
      • @bethsoderberg found some small font size and spacing issues when comparing the PSDs and Google Slides. We’ll check to see if @ariwinokur has a report on anything he’s found next week.
    5. Contributor Day logistics
      • @courtneyengle checked with the Outreach Team and found that they do not have a specific RSS/iCal/etc feed of Contributor Days at this time. The hope was to use this with some automation that @ariwinokur was working on.  However, we’ll need to stick to manual for now.
      • @bethsoderberg will start a draft plan for next week to handle contributor days for each of the following scenarios. @melindahelt will take on whatever needs to be done on the plan next week.
        • Someone from team can attend the contributor day
        • Someone from team can monitor Slack on the contributor day
        • No one from team can attend or monitor Slack on the contributor day
    6. Future logistics discussions
      • We all agree that we’d like to discuss lesson plan continuity in the future.  As updates to WordPress are released, we’d like our content to be reviewed to ensure that it’s current. When we have this conversation we’ll want to revisit the Content Audit plugin conversation we had in October 2014. @courtneyengle is going to check with the WPTV team to see how the TV video plugin is developing and how they plan to maintain and address changes in content as WP evolves.
     
  • Courtney Engle Robertson 7:29 pm on July 13, 2015 Permalink |
    Tags: Contributor Day, , WordCamp   

    Agenda for July 14, 2015 

    1. Greetings
    2. Recap of last meeting
    3. Lesson plans status and questions
    4. Testing status and questions
    5. Slides update
    6. Continue Contributor Day brainstorm
      1. No Contributor Day RSS/iCal feed yet
      2. Automation
    7. Questions

    Please add any additional agenda items to the comments!

     
  • bethsoderberg 2:14 am on July 8, 2015 Permalink |  

    Recap of July 7, 2015 Meeting 

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

    1. Welcome and recap of last meeting
    2. Lesson plan updates
      • @wpnzach is working on the menu documentation and will work on the current menu configuration in his plan. He’ll also work on a non-public draft that covers the future customizer menus.
    3. Testing updates
      • @stephs8919 found a venue for her training and will lead a WordPress basics class at the end of the month.
    4. Slides
    5. Contributor Day logistics
      • @ariwinokur is working on a way to automate pings to the #training Slack channel when a contributor day is happening. Right now he is using IFTTT to create an automatic notification to the channel. It is currently pulling the info from a Google Calendar he created off the WordCamp schedule iCal. The group agrees that a curated calendar of that includes just contributor days would be better than the WordCamp calendar and that an automated contributor day calendar would be best.
      • @courtneyengle will check with the Outreach Team to see if they maintain a calendar of contributor days that we could pull data from.
      • A new idea related to contributor day logistics was to have an automated message appear in the #training Slack channel on those days with introductory information.
    6. Process for abandoned lesson plans
      • @bethsoderberg and @abuango have been working together on a new process, which will debut in August. Moving forward, we will ping the channel regarding plans we’ve identified as possibly abandoned during the first meeting of each month and for the two meetings after that. Once those three pings go out, then any plans that haven’t been accounted for or claimed will open up for others to work on.
    7. Upcoming WordCamps
      • At least one representative from team training will be in attendance at the following upcoming WordCamps: Salt Lake City, Boston, Baltimore, New York, and possibly Scranton
      • @stephs8919 and @courtneyengle are coordinating to put together a “How to Contribute to WordPress” talk for WordCamp Baltimore.
    8. Meeting Agendas
      • Team training meeting agendas are posted every Monday in preparation for Tuesday’s meetings. Please add any agenda items you have to the comments.
     
  • bethsoderberg 11:45 pm on July 6, 2015 Permalink |  

    Agenda for July 7, 2015 

    Please add any additional agenda items to the comments!

    1. Greetings
    2. Recap of last meeting
    3. Lesson plans status and questions
    4. Testing status and questions
    5. Slides update
    6. Continue Contributor Day brainstorm
    7. Process for abandoned lesson plans
    8. Questions
     
  • bethsoderberg 1:03 am on July 1, 2015 Permalink |  

    Recap of June 30, 2015 Meeting 

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

    1. Welcome and recap of last meeting
    2. No updates on lesson plans in progress or on testing
    3. Slides
      • @courtneyengle put together a draft version of a slide template from the PSDs we have using Google Slides.
      • There are some concerns about the slides as they are now, including the following issues:
        • Eventually we will want these in both 4:3 and 16:9, depending upon the projectors available. Will it be unsustainable to maintain two versions of the slides for each lesson plan?
        • Folks who aren’t familiar with the templates may have trouble with the formatting for a correct answer and for quotes.
      • If we use Google Slides in the future, we’ll need to set up a process for folks to use the templates maintained by team training and transfer ownership of the sliders to the team after creation.
      • @bethsoderberg and @ariwinokur will check the PSDs against the Google Slide templates this week.
    4. WordCamp Contributor Day brainstorm
      • We brainstormed some ideas about how the training team can interact with folks at contributor days both when a team representative can be present and when we can not.
      • In general, we had a bunch of ideas about creating lists of things people at contributor days can do to help out. These ideas included the following:
        • Translating plans
        • Making plans to test plans
        • Checking to confirm that plans are still up to date after new WP releases
        • An ongoing list of little tasks
      • We all agreed that it would be awesome if a representative could always be there, but since that’s not possible we talked about having a representative video chat with contributors and/or be available via Slack to help with questions, setting people up, etc.
      • Not every Contributor Day is attached to a WordCamp and not every WordCamp has a Contributor Day.
      • @ariwinokur will look into automating Slack notifications from a feed of upcoming events and @juliekuehl will work on an initial list of upcoming contributor days if automation isn’t possible.
     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel