Recap for May 17, 2016 Meeting

Slack Log (Requires SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at login to view. Set one up if you don’t have a Slack account)

  1. Welcome
  2. Updates on in-progress lesson plans
    1. @bethsoderberg updated the master spreadsheet in accordance with the lesson plan amnesty audit that we finished up last week, so that is now accurate.
  3. Copyediting updates
    1. @skarjune will resume copyediting things after WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Minneapolis happens.
    2. @bethsoderberg finished copyediting of the General History plan, which was written by @Becks979.
  4. Discussing team goals for next set of workshops
    1. Last week we discussed that having a more concrete goal of completing the initial workshops for the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party, theme, and basic-intermediate troubleshooting workshops would be good. Roughly, if we can get these done by the end of September, then we can roll into testing in October. This week, we started to outline the steps to make this happen.
      1. @melindahelt had some great suggestions regarding how to approach Tier 2:
        • “those with assignments keep working on them as we can”
        • “prior to any upcoming contributor days, take an honest look at the assignments and if there are any that are not started, see if the author would like to give those up if someone is able to start/finish at contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus. That way we have relevant things for people to work on and can make progress.”
        • “If we work backwards saying that we want to test in October, we want all plans completed by September 1 (to allow time for copy editing), and they maybe pick a date that if the author is not in progress by X date then the plan can be reassigned.”
      2. @bethsoderberg suggested figuring out what the theme workshop is going to look like and then focusing on the themes and top-level plugin plans first, with a secondary consideration for the plugin-specific plans and speaker stuff.
    2. Plugin Workshop
      1. List of “parent” lesson plans for this workshop:
        • Adding Additional Fields – assigned
        • Adding Custom Sidebars
        • Adding Forms to a Site – assigned
        • Building a Sitemap for a Site
        • Connecting Your Sites – assigned
        • Editing Plugins – assigned
        • Improve Site Performance with Caching
        • Keeping WordPress Sites Secure – assigned
        • Managing Spam on a Site – assigned
        • Migrate, Copy or Clone a Site – assigned
        • Onsite SEO
        • Plugins: Where to Find Answers – assigned
        • Site Backup – assigned
      2. We talked about the fact that people are having a hard time writing these plans in part because it’s unclear how they should be structured in relation to the “child” plans that will be about specific plugins.
      3. We brainstormed a basic structure that these plans could follow and @bethsoderberg will write a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at post on this soon for everyone to review and comment on. Basically the structure we identified would intro the concepts related to the plugins and then list the plugins for which we have child plans.
    3. Theme Workshop
      1. We talked about the theme plans proposed for voting in this P2 post from last month and outlined what the individual plans could be as follows:
        1. Basic Theme Configuration
        2. How to Find Theme-Specific Documentation
        3. Font Management
        4. CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.: CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. Changes
        5. Customizer: Taglines
        6. Customizer: Static Front PageStatic Front Page A WordPress website can have a dynamic blog-like front page, or a “static front page” which is used to show customized content. Typically this is the first page you see when you visit a site url, like for example. vs. Content Feed
        7. Customizer: Site Icons and Logos
        8. Customizer: HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. and Background Images
        9. Customizer: Menus
      2. We discussed the details of what the first two of these plans would contain and decided that “Basic Theme Configuration” would be about what types of things you can change (e.g. an intro to what the customizer is), not the specific instructions for changing things, but a general overview of what you can do. We think the theme-specific documentation plan could cover how to look at the links to the theme profile in the repo, tags in support and things like that, an explanation that different theme authors do this differently, and notes that there may not be documentation at all.
      3. The attendees of the meeting voted unanimously on the 9 plans listed above to be the starting point for the Tier 2 themes workshop.
    4. Troubleshooting Workshop
      1. @bethsoderberg is setting a May 31 deadline for herself to audit what exists already for this workshop.
  5. Questions & Announcements
    1. @melindahelt has a ton of feedback from the Pittsburgh workshops she ran and is going to write a P2 post to share it with the team for comments and creation of new action items.