WordPress / WordPress/Learn

Content Feedback - Course: Community Meeting Etiquette (Audit Feedback)

Open
#1,747 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Content] Feedback [Content] Needs Update
Dominant language
PHP
Stars
333
Forks
127
Avg merge
1d 7h
Merged PRs (30d)
11

Description

Overview

Feedback Details.

  • There are only 2 Lesson modules and a quiz at the end of each one. I'd like to suggest having a 'Continue' or 'Next Lesson' button available after completing the first lesson quiz. Currently, the learner has to click on the sidebar menu item to proceed to next lesson.
  • The course seems to be more of a guideline for hosting a meeting, rather than how participants should conduct themselves when attending a meeting. It might be better for the title to reflect this. Or add/edit separate lessons for hosting a meeting and participating in a meeting.
  • Aside from an answer choice on the last quiz, there's no mention of Slack or GitHub being the primary venues where meetings take place and meeting agendas are posted, respectively. It would be helpful for this info and corresponding links to be included, and may even encourage onboarding new participants and contributors.

Next steps for Training Team member

Please follow the team handbook "Validating Content Feedback issues" to validate this feedback.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Community Meeting Etiquette course at the linked Learn WordPress URL and read the Training Team handbook section on validating content feedback. Review the two lessons, quizzes, navigation, and referenced meeting resources against the three suggestions. Done means the feedback is validated and the resulting content changes or follow-up decisions are recorded.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.