Highlighted Posts

Categorize a post as Highlight to add it to this section.

Meeting Agenda for July 5 – 7, 2022

Please join us for our Team Meeting Tuesdays at 16:00 UTC OR Thursdays at 11:30 UTC (APAC friendly) OR Coffee Hour Friday at 13:00 UTC in the #training Slack channel for our weekly meetings!


This Week’s Agenda

  1. Intro/Welcome
  2. News
    1. Meeting Note Takers
      1. July 5 – @courtneypk
      2. July 12 – @samanthaxmunoz
      3. July 19 – @kryzpt
      4. July 26 – @psykro
    1. GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ automation updatesCopyeditor checklist
      1. New Projects BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.
    2. Update about the individual survey
    3. Needs Analysis working group poll
    4. Naming suggestions for lesson plans, workshops, and social learning spaces
    5. Learn WordPress Development: Creating a Public Roadmap for Content Creation
    6. Training Team Goals and Strategy Call
    7. Rethinking the Lesson Plan Creation & Updating Process
    8. Social Learning Spaces on Learn WordPress
    9. Big Picture Goals 2022
  3. Monthly Sprint
    1. Progress
      1. Drafts
      2. Reviews
      3. Published
    2. Help Needed
      1. Content
        1. Ready to Create – You Can Help
          1. High Priority
          2. Medium Priority
          3. Quick Fix
        2. Topic Ideas
      2. Website Development
        1. High Priority Issues
        2. Medium Priority Issues
        3. Good First Issues
      3. Training Team Administration
    3. Check-in
      1. What did you do last week?
      2. What are you doing this week?
      3. Any Blockers?
    4. Monthly Retrospective
      1. June July Sprint
      2. Training Team Goals
  4. Open Discussions

Upcoming Meetings

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 helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Workshops
    3. Courses
    4. Social Learning Spaces
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#agenda, #learn-wordpress, #training

Discussion: Naming content types on Learn WordPress

There are currently four types of content on Learn WordPress:

  • Workshops (5-15 minute instructional videos)
  • Courses (long-form content with multiple lessons in multiple media formats)
  • Social Learning Spaces (live and collaborative learning sessions)
  • Lesson Plans (structured plans that trainers can use to teach others)

There have been several discussions over the past few months about the names of some of these things – specifically, workshops and SLSs. It is clear that the current names for these elements are not universally understood and not always simple to translate, so it would be a good idea to look closely at these names and come up with alternatives that are both easy to understand and easy to translate. Indeed, based on the definition of a “workshop” it is clear that what we currently refer to as SLSs would be better labelled as workshops.

From many informal discussion around this, the names for ‘courses’ and ‘lesson plans’ haven’t come up and seem to be clear enough as they are right now, so let’s look at what workshops and SLSs are and see how that can inform what we name them:

Workshops

Learn WordPress workshops are short (5-15 minute) videos that show WordPress users how to do a specific thing. They are generally focused on one feature at a time and have specific learning outcomes. They are not interactive, although they do sometimes have an optional follow-up quiz to assist learners in knowledge consolidation.

With that in mind, here are some potential names we could use here (please feel free to suggest more):

  • Videos
  • Tutorials
  • Video Tutorials
  • How-tos
  • Explainers

I’m leaning towards “tutorials” here as I think that is the most universally understood term for this kind of thing. It also gives us the flexibility to expand the use of the content type to include text-based tutorials alongside (or instead of) the videos at some point in the future if we ever decide to do that.

Social Learning Spaces

Social Learning Spaces (SLSs) are live learning sessions, usually facilitated over Zoom. They are ideally highly interactive and are generally 1-2 hours long. They are regularly recorded and made available for learners to view on their own time, although watching the recording obviously removes the interactivity from the experience. This recent post has much more detail about what they are and how they work.

With that in mind, here are some potential names we could use here (please feel free to suggest more):

  • Webinars
  • Classes
  • Workshops
  • Live workshops
  • Meetups
  • Live learning sessions

I’m personally leaning towards “live workshops” here, but I’m also open to other suggestions. The immediate potential issue with that option is the fact that we currently use ‘workshops’ for a different content type, so that may present a problem with this.

Feedback

So what do you think? Please comment with your thoughts on these names for workshops and SLSs and what you feel would be a good way forward.

Social Learning Spaces on Learn WordPress

Tl;dr: Social Learning Spaces (SLS) have proved to be useful and accessible learning spaces for community members to learn more about various WordPress topics. This post hopes to clarify who and what these spaces are for, and how folks can get more involved.

What are Social Learning Spaces (SLS)?

Social Learning Spaces (SLS) are live and collaborative learning sessions that were introduced on Learn WordPress in January 2022. These sessions tackle a variety of WordPress topics and can be run in any language and from any part of the world. 

The reason why these sessions are currently called “Social Learning Space” is because they follow the theory of social learning practice from Etienne and Beverly Wenger-Trayner. The “social” aspect is the act of us gathering synchronously to “learn” in a designated “space”. 

Social Learning Spaces are scheduled in the WordPress Social Learning Meetup Group here and appear on our Training Team’s SLS calendar here.

Who can join an SLS?

Absolutely everyone, time permitting of course! We also record most sessions, enable transcription, and put these videos up on WordPress.tv.

Also, anyone can apply to become a Social Learning Space Facilitator here, and you can see how facilitator applications are vetted in our handbook here.

I want to facilitate an SLS, but don’t know where to start!

No need to stress, we have our guide for getting started here, various topic ideas on the Training Team’s Content Development GitHub board here, and you can also work with a Training Team member to make your SLS dream a reality. 

The Training Team has already assisted over 10 contributors in facilitating their own SLS, and are ready to provide guidance and mentorship along the way.

Still have questions about Social Learning Spaces? Feel free to ask here in the comments, or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me (@Destiny) or a Training Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. in the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.’s #training channel here.

Rethinking the Lesson Plan Creation & Updating Process

Tl;dr: Some contributors express confusion when attempting to contribute to lesson plan creation. This post aims to look at how we can improve that experience by documenting the barriers experienced by these contributors, raising additional questions for the team’s consideration, and making suggestions for consideration on how to move forward.

What barriers are the team seeing?

Since June of last year, we’ve seen about 1-2 lesson plans reach publication per month. Alongside those accomplishments, we’re also seeing a number of inconsistencies being flagged in our documentation around the process, and new contributors voicing apprehension about getting involved. 

I’m sure that together we can work toward some good solutions for folks, so I’ve listed the inconsistencies I’ve picked up from contributors below for consideration:

  • There exists conflicting information on creating lesson plans:
    • The Workshop on Creating a Lesson Plan is inconsistent with the Lesson Plan and The Handbook (How to Submit a Lesson Plan Idea).
    • There are three different lesson plan style guides, two from the Training Team Handbook (here and here), and one that exists as the GitHub Issue template.
      • The format in the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue template is the correct one to follow, but that is more a template, not a step-by-step detailed guide to putting together a lesson plan.
      • This Lesson Plan Style Guide linked on the How to Conduct an Instructional Review page here seems to be a more effective guide on how to fill in the details of each section but doesn’t include the updated items from the template. Getting that style guide updated would require an understanding of what’s required for the new sections, and including details there.
  • There are steps without any documentation:

Additional questions for discussion

These additional questions can branch off into their own respective posts if needed, but as they relate to the current lesson plan process, I’ve included them below for consideration as well:

  • What is a reasonable turnaround time for content reviews, for the purpose of keeping contributors motivated and eager to come back to do more? (41 are currently awaiting review)
  • What is a good goal to set in regards to lesson plan publications? (We currently do not metrics noted in the team goals, and since the How to Create a Lesson Plan workshop was created on June 14 2021, there have been 22 lesson plans published on Learn)
  • What can we do to ensure that this process is inclusive? (Ranging from diversity of submitters, to published languages, etc)?
  • How long should it ideally take to design a lesson plan from start to finish?
    • For those of us who are writing lesson plans, what’s working for you? Where are some places you’ve gotten stuck and why?
    • For those of us who want to write lesson plans but aren’t, what’s an obstacle in your way?
    • Team reps, what do you absolutely love about our process? What steps are essential in the designing of lesson plans?

Process improvement recommendations for discussion

Of course before launching into solutions, it would be helpful and great to also hear from other training team members and our Reps about what they like, why they did what they already did, and what they want to see change. 

The suggestions listed below are to help start fruitful conversation about what was flagged above:

  • Set a metric goal for lesson plans to help us sustainably tackle the backlog
  • Decide if the steps with missing pages are necessary, optional (nice to have), or should be deleted
  • Review, simplify, and consolidate the “Creating a Lesson Plan” guides in the Handbook, Workshop, and GitHub; reducing link-outs where duplicative
  • Shorten and Simplify the ‘Development Checklist” in Github
  • Identify ideal turnaround times for each step in the production -> publication process

#lesson-plans

Training Team Goals and Strategy Call

On Tuesday, June 28, 2022 19:00UTC (AMER) and Wednesday, June 29, 2022 05:00UTC (APAC), the Training Team Reps and Faculty Program Members held two calls to discuss the progress of the training team goals and our strategy for meeting them.

Outlined below are the notes taken from these two calls.

Attendees

AMER call: @pbrocks @ndiego @piyopiyofox @arasae @courtneypk @azhiyadev @annezazu

APAC call: @webtechpooja @bsanevans @psykro @wes

Notes

  • We discussed the current state of the Training team goals – https://make.wordpress.org/training/2022/01/18/training-team-goals-for-2022/
    • When this goals post was created, it had been a year since Learn had been launched when the first meeting around the goals occurred.
    • What still needs to be done from Q1?
      • Brainstorm and discovery for the creation of a Needs Analysis.
      • Learner Survey.
      • Plan promotions with the Marketing Team (Currently in the Training Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.’s hands).
      • Create Instructor/Facilitator resources portion on LearnWP.
        • There is a Learning Path document that @courane01 put together. It breaks things down so that a meeting organizer can use this. 
      • Look into automation for the content creation/review process.
    • What needs to be tackled in Q2
      • Training Needs Analysis.
      • Release roadmap of new content (that isn’t tied to WP releases/features).
      • Overhaul the “Submit an Idea” form. Build in conditional logic for workshop, lesson plan, and course.
    • It was noted that we’d like for SME’s to set the priorities for the content we seek to create and telling us when it should be created.
    • We learned that folks tend to have a pretty solid idea before the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. period of what features are going to make it into the release, so we can use this knowledge for timing content releases.
  • Faculty Program Structure & Vision
    • Feedback:
      • Knowing when SME’s need to chime in would be great– can we have an alert world? It can be tough to know when to engage.
      • Having a buddy system / mentor program would be great.
  • Open Discussion
    • SLSes
      • Nick has found them to be a very interesting way to engage with the community, and would love to see it grow into a more important part of Learn.
      • Tying SLSes to topical things can make SLSes a vehicle for learning WordPress more intuitively.
      • Let’s put effort into spreading SLS sessions into APAC and other timezones
        • Folks in APAC may need to continue hosting these even with minimal attendance to grow the attendance, and then the contributors will come.
        • Let’s run SLSs about running SLSs.
    • Contributing to the technical needs of Learn WordPress
      • The way Learn WordPress is currently set up requires developers to cross a few hurdles before they can actually contribute to the issues we’ve listed.
        • It would be great if we can find a way to set developers up with the necessary tools, so that they can more easily contribute to those technical issues
    • Can we streamline https://make.wordpress.org/training/ so that it isn’t as intimidating for new folk?
      • We already have some conversations going on about what we can do about this.
      • Reality is, we are limited somewhat by the structure of Make itself. MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team is working on that.
      • What we could do is collect feedback, and send that to Meta to help with their work.

Action items

Listed below are action items created from our discussion and their assignments

  • Create a spreadsheet with release tab organization for this board https://github.com/WordPress/Learn/projects/2 for SMEs to go through and help prioritize / @piyopiyofox
  • Check if our current lesson plan / workshop creation handbook includes a step to include a “timestamp + WordPress version”.
  • Create template slides for SLSes / @piyopiyofox
  • Create alert words for SMEs, Content Creators, Editors, Administrators, and then the full faculty / @courtneypk
  • Provide information about critical features that require content for 6.1 / @annezazu
  • Draft a proposal for creating a Faculty Program Mentor/Mentee program / @arasae
  • Set up time for next monthly call / @piyopiyofox

#faculty-program

Learn WordPress Development: Creating a Public Roadmap for Content Creation

Introduction

From the Training Team Goals for 2022:

Vision

In 2022, the Training Team will empower users to achieve their goals with WordPress through actionable and practical learning experiences that bring the community together.

Last year, @courane01 shared a High-Level Roadmap to Learning WordPress Development and provided some excellent thoughts and visual elements to help describe the pathway to learning WordPress development. That research covered the entire range of WordPress development, from creating posts and pages and designing sites, all the way up to and including contributing to WordPress.

This post serves to gather initial ideas and feedback from the community on what specific programming/technical content should be created for Learn WordPress in order for a WordPress developer who uses no-code tools to learn to use the programming languages and APIs that power WordPress, and extend WordPress beyond what the no-code tools provide.

the_content()

Much of what is required to become a WordPress extender is contained in the WordPress Developer Resources site. At first glance, it might appear that it would be a good idea to cover each of the top-level handbooks on that site.

However, in order to create a logical learning path for a new WordPress extender, it might be worth considering re-categorizing some of this content, based on a predefined learning curve.

register_taxonomy()

This is one proposal, but the most straightforward approach to categorizing this content could be guided by the high-level topics in the official WordPress Developer Resources handbook:

  • Fundamentals of WordPress development
  • Common WordPress APIs
  • Developing WordPress themes
  • Developing WordPress plugins
  • Developing WordPress blocks
  • The WordPress REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.
  • Advanced WordPress development

add_filter( ‘the_content’, ‘wp_learn_content_path’ );

Given the categories above, we could then break down the content to fit into each categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., by creating new Learn content based on the existing handbook entries, as well as content for any items that aren’t already covered in the handbooks. At the same time, we can move some of the topics around a bit, to create a more logical help with planning a future roadmap/learning path, as described in the following content outline:

Update: I should point out that this list is not my proposal for a roadmap (i.e. what item should follow from the next), and is more of an overview of the development content we should cover. Eventually, this content can be molded into a roadmap, but that list is definitely not what I would consider the pathway someone should take to learn WordPress development.

wp_insert_comment()

It’s time to share your thoughts on this suggested content outline.

  1. Do the categories make sense, could they be extended, or streamlined, or improved upon in some way?
  2. What’s missing, either from the handbooks, other documentation, the High-Level Roadmap to Learning WordPress Development, or any other WordPress development/programming-related resource.
  3. What doesn’t belong, and could be left out?
  4. What is not sufficiently detailed, and could be expanded upon. How could it be expanded?
  5. What needs to move from one category to another?

You are welcome to leave feedback in the comments here or comment on specific sections in this Google Doc, which is a copy of the content outline shared above.

Comments are welcome until Friday, July 15, at which time all feedback will be incorporated, and an updated content outline will be published.

Thanks to @courane01, @annezazu, and @hlashbrooke for reviewing this post.

+make.wordpress.org/core/
+make.wordpress.org/themes/
+make.wordpress.org/plugins/
+make.wordpress.org/docs/
+make.wordpress.org/test/

Training Team Meeting Recap – June 21 & 23

Slack Log for EMEA/Americas Meeting (Tuesday, June 21, 2022)
Slack Log for APAC Meeting (Thursday, June 23, 2022)

(Logs require a SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. login to view. Set one up if you don’t have a Slack account.)

The agenda for both meetings can be found here.

1. Introductions and Welcome

Attendance EMEA/Americas Meeting:  @azhiyadev, @courane01, @webtechpooja, @samanthaxmunoz @caraya @piyopiyofox @eboxnet @Kryzpt @kartiks16 @WebCommsat @Kemmy99 @courtneypk @bsanevans

Attendance APAC Meeting: @webtechpooja, @Kryzpt, @eboxnet, @sabbir16, @chaion07, @AfshanaDiya, @shubhamsedani, @psykro, @courtneypk @wpscholar @mysweetcate @kp4net

Welcoming the newcomers joining the Training team in the last week (Slack usernames): 
@Sagar Nasit, @Vagelis, @kp4net, @mysweetcate

Meeting Note Takers

2. News

GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ automation updates :

Take a look at the Github beta project here, you can swap between BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. and regular projects. We use GitHub projects to track website development, content development, and team administration. We received access to Projects Beta, and we have started to move our Content Development over. We are next working on actions and automation.

What we want to have is that if someone submits a lesson plan or workshop, then the next group of people that are to review that would be pinged, with a checklist of what to look for.

Copyeditor checklist

We will be relaunching who is interested/willing to contribute to various team roles soon, including those that want to copy edit and organise within GitHub teams to use notifications there for this activity.

Team roles & Faculty Roles

Before moving to GitHub, we had these organized in TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing.. We’re working to move these to GitHub, which will later help us organize those call-ins on the contribution

Faculty Program Members

This is an unpublished page, but ready for the team to see on a public preview link. Thanks to @Destiny for the revision so far.  We’re still having some conversations about linking to the GitHub issues for the list, so stay tuned for more info.

 Update about Individual Learner Survey

 Specifically, the form is not GDPR compliant and everyone is concerned about, who owns the account where the data is stored?

@Destiny has looked into some options for surveys and in the past, we seem to have used Crowdsignal (although that is Automattic owned). 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party is currently disabled on Learn.
#marketing has also suggested SurveyMonkey and SmartSurvey but there is no official tool used by the team. @Angela Jin is checking to see what we use for WordCamps (it may be Crowdsignal).

Needs Analysis working group

We are still working to build the thorough Needs Analysis per how organizations would anticipate this type of a survey, and the value it would be for them.

Badges:

Meeting notes and more: @Destiny @Makinde Ruth Oluwakemi  @Jonathan  @Femy @boogah

Content creation: @artdecotech @Benachi @kafleg @Carlos

Congratulations folks for training team badges. We greatly appreciate your contribution.

Naming suggestions

We are in sync with #polyglots and #marketing for naming suggestions for lesson plans, workshops, and SLS (Social learning spaces). It needs brainstorming. We are thinking to start a poll and we will soon work on it.

3. Sprint

June-July Sprint

The Training team is using Sprints to determine what we are working on and to determine our time frame for delivery.

Drafts in Progress

We currently have 24 items currently being drafted.

These lesson plans are under Review Process:

  1. Block Locking – Lesson Plan
  2. Upload a Theme to the WordPress Repository – Lesson Plan
  3. What to Include in Functions.php – Lesson Plan
  4. Gallery Block – Lesson Plan
  5. Child Theme for Block Themes – Lesson Plan
  6. WebP – Lesson Plan
  7. Styling Your Site with Global Styles – Lesson Plan
  8. User Management – Workshop
  9. Managing Media lesson plan – Lesson Plan

New videos in Portuguese are ready to review,

https://wordpress.slack.com/archives/C02RW657Q/p1655844289202409
https://wordpress.slack.com/archives/C02RW657Q/p1655921849888749

Ready to publish – Theme.json – Lesson Plan

4. Open Discussion

Feel free to claim any of the issues on our Content Development and Website Development boards.

WordCamp Kathmandu 2022

WordPress Speaker Workshop for Women Voices in India (Sept 24 & 25)

Upcoming Meetings

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 helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Workshops
    3. Courses
    4. Social Learning Spaces
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#training

Meeting Agenda for June 28 – 30, 2022

Please join us for our Team Meeting Tuesdays at 16:00 UTC OR Thursdays at 11:30 UTC (APAC friendly) OR Coffee Hour Friday at 13:00 UTC in the #training Slack channel for our weekly meetings!


This Week’s Agenda

  1. Intro/Welcome
  2. News
    1. Meeting Note Takers
      1. June 28 – @psykro
      2. July 5 – @courtneypk
      3. July 12 – @samanthaxmunoz
      4. July 19 – @kryzpt
      5. July 26
    2. 6.1 planning roundup
    3. GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ automation updates
      1. Copyeditor checklist
      2. New Projects BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.
    4. Update about the individual survey
    5. Needs Analysis working group poll
    6. Naming suggestions for lesson plans, workshops, social learning spaces
    7. Tracking social learning spaces
    8. Badges
      1. Content creation: @fellyph
  3. Monthly Sprint
    1. Progress
      1. Drafts
      2. Reviews
      3. Published
    2. Help Needed
      1. Content
        1. Ready to Create – You Can Help
          1. High Priority
          2. Medium Priority
          3. Quick Fix
        2. Topic Ideas
      2. Website Development
        1. High Priority Issues
        2. Medium Priority Issues
        3. Good First Issues
      3. Training Team Administration
  4. Open Discussions

Upcoming Meetings

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 helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Workshops
    3. Courses
    4. Social Learning Spaces
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#learn-wordpress, #training-team

Discussion: Tracking Social Learning Spaces

As we get more comfortable settling our content into our team GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, I thought it might be time to start tracking our social learning space topics. Another facilitator and I recently very nearly scheduled the same topic for a social learning space–simply knowing where to look to see if another similar topic was in the works would have immediately fixed this situation for us.

So, how should we track Social Learning Space topics?

How do we all feel about creating a Github template with the title and description that would appear on MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. (similar but not as extensive as a lesson plan) for social learning space ideas?

To be clear, this would not replace Meetup, but it would allow us to see which spaces are in progress and which have already been created to avoid an unfortunate overlap. Adding these as issues/tasks in GitHub also allows us to better track team contributions and award badges.

Some thoughts:

  1. Some social learning spaces occur more than once (they can be repeated!), so I’m not sure the best way to track them. 
  2. It may help to have a “Planned” column, “Scheduled” column, and “Past SLS” column where frequent or semi-frequent contributors can move issues from one stage to the next… would it be okay if they moved back into “scheduled” if they’re a repeat topic?
  3. Once an SLS is complete, It would help to provide links to the recording of the SLS in this same space.

Important: It’s important to note that just because a social learning space has been taught online before, doesn’t mean it cannot be repeated for a new audience, or that a new facilitator cannot run the same social learning space on the same topic. New facilitators bring new knowledge, new audiences bring their own unique perspectives and experiences. Especially as these spaces become more and more interactive, each discussion will shed new light, attendees will build their own projects, and it will allow us to stay current with the most recent WordPress developments.

The ask: Is Github the right place to track social learning space topics? 

What is a useful way to track it–what I described, or something else? 

Please leave your thoughts in the comments. We would appreciate them!

#learn-wordpress, #social-learning, #training-team

May 2022 Sprint Retrospective

Training Team works in monthly sprints. At the end of each sprint, we ask ourselves the following questions. Below is a compilation of the responses from the team following the retrospective discussions held in the #training SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel:

What went well?

  • Items related to the release that we worked on and improved planning and joint working.
  • Tracking issues across GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ from the source in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repo.
  • Launch of the Faculty Program.
  • Interaction between meetings and so many new faces are joining us.

What could we improve?

  • Finish the GitHub automation/actions to be more clear about what contributors can do.
  • Contribute to quarterly goals at least as much as release-related initiatives.
  • Call for Content Creation.
  • Fast track the content review and publish it soon, what we decided earlier in 2-3 weeks.

What will we do differently?

  • Start tracking Gutenberg issues that impact revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. this week.
  • Releases are not stacked right against an international 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. with all the prep for it. And contributor days right after release.
  • Organize a virtual zoom call (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 https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.) of 2-3 hours, to kick off the review and publish content part. And audit previous content for the latest release.

#retro

#meta, #retro, #training