Request for feedback: Lesson Handbook pages

Welcome

The WordPress Training Team helps people learn to use, extend, and contribute to WordPress through learn.wordpress.org.

Are you new to the team?

Getting Started – Join the team through this self-guided onboarding program.

Current Focus Areas – What we’re currently focusing on.

Goals for 2024– the goals include the team’s vision, values, and a quarterly breakdown of project milestones.

Already onboarded and ready to get involved?

See How we use GitHub to get started on one of our 6 project boards

Meetings (Calendar)

Weekly Global team meeting: Thursdays 00:00 UTC

Dev-squad GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ triage: Biweekly on Thursdays 07:00 UTC

See Meeting Details for more information.

As we work towards launching the Learning Pathways in 2024 we will need to create a new set of content creation guidelines that enable the Learning Pathways to scale, with a clear process for developing, reviewing, and updating content.

I would therefore like to propose that we create a new Handbook section which will include the following pages:

Lessons
Lesson Creation Process
Lesson tasks
Creating a lesson
Lesson Review
Publish your lesson
Adding the Lesson to Learn.WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/
Creating Lesson Module Quizzes/Activities

I have created a draft Google doc containing these initial pages, as well as content that has been drawn primarily from our existing documentation on Tutorials, but with some added sections drawn from other handbook pages.

https://docs.google.com/document/d/1twvDGmVZsyjBZbi9abiqoA_a2G7O_WNis_iGL2Sccg0/edit?usp=sharing

I would like to call on all members of the Training Team to review this new set of handbook pages and share their feedback on the different sections.

You are welcome to share your thoughts in the comment section on this post or use the Google Doc comments feature.

I will leave this post and the doc open for feedback and comments until Tuesday 19 December 2023, after which I will add the new pages to the Training Team handbook.

Benjamin Evans 8:41 am on December 11, 2023
These were a great first draft. I’ve left comments throughout.

I did have some thoughts about the page structure you’ve laid out.
- “Lesson Creation Process” and “Lesson Tasks” seem like pages with a similar goal – providing an overview of the steps needed to create a lesson. Can they be combined into one?
- As those pages are still just an overview, I think that content could go into the parent “Lessons” page.
- At the moment, the review processes laid out doesn’t look very different for the review process already documented. If there aren’t any lesson-specific steps that need to be noted, could this page be deleted altogether?
- Jonathan Bossenger 7:24 am on December 20, 2023
  
  “Lesson Creation Process” and “Lesson Tasks” seem like pages with a similar goal
  
  The idea between separate pages was that the Lesson Creation Process page provides an overview of the process for the first-time creator. The Lesson Tasks exist for both the first-time creator, as well as the experienced creator, to be able to bookmark and quickly find the markdown checklist to add to their issue comment.
  
  At the moment, the review processes laid out doesn’t look very different for the review process already documented.
  
  . I’m not sure which review process you’re discussing here.
  
  At the moment, the only handbook page I’m aware of that discussed the review period from the point of view of the content creator exists under the handbook pages for Tutorials, so it made sense to include a specific page for Lessons.
  
  If you were referring to the Guidelines for Reviewing Content, that’s written from the point of view of the reviewer, and so doesn’t include things like review times or number of reviews.
  
  With Tutorials eventually being superseded by Lessons, I would assume the Tutorial handbook pages would also get removed at some point.
  - Benjamin Evans 5:26 am on December 21, 2023
    
    Ah, gotcha, to both of those 👍🏼
Cynthia Norman 12:01 pm on December 12, 2023

Within the Lesson Creation Process, you state “When working on Lessons that form part of a Learning Pathway, it’s generally a good idea to check in with the contributor(s) who are managing the specific Learning Pathway, to ensure that the content you are working on matches the intent of the pathway in question.”, so I’m wondering if that process could use a link to the spreadsheet of learning pathways and contact links for reaching out to their managing contributors.

The Content Development (general) template needs to include Lesson in the list of content types. Also consider revising the template to include Learning Pathway (User, Designer, Developer), and Experience Level (Beginner, Intermediate, Expert)
- Jonathan Bossenger 7:26 am on December 20, 2023
  
  I’m wondering if that process could use a link to the spreadsheet of learning pathways and contact links for reaching out to their managing contributors.
  
  That’s a good question. That does mean one more spreadsheet to manage though. What has been in place so far is that the managing contributor is always assigned to the relevant GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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, and so one can contact that contributor through the GitHub issue comments. Do you think if we add something along those lines, that would be sufficient?
  - Jonathan Bossenger 7:28 am on December 20, 2023
    
    The Content Development (general) template needs to include Lesson in the list of content types. Also consider revising the template to include Learning Pathway (User, Designer, Developer), and Experience Level (Beginner, Intermediate, Expert)
    
    Yes, we will need to revise and update those templates, which we will be able to do once the Guidelines have been published. There will be a short duration where we might have to edit the content of those templates until the changes are made to GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/, but I have started this process by creating a PR to add a //lesson automation.
Jonathan Bossenger 10:41 am on December 21, 2023

Thanks to everyone who either commented here or commented on the doc.

There are still some open conversations about expanding/enhancing the new docs, but we will pick up those conversations in the new year.

The new handbook pages will be published on Friday, 22 December, 2024.

Comments are closed.

Welcome

Meetings (Calendar)

Share this: