WordPress / WordPress/Learn

Feedback - Proposing content update in lesson "Your Support Network: People, Channels, and Communities"

Open
#3,549 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Type of feedback

//content

Description

Content URL
https://learn.wordpress.org/lesson/your-support-network-people-channels-and-communities/

Are you reporting an error or providing other feedback?
Providing feedback (such as an idea for improvement)

What are you reporting?
As an WordCamp organiser I do not know after reading below mentioned abstracts what is the difference between these 2 roles.

Event Supporters. Event Supporters (formerly known as Mentors) are experienced WordPress community members who are assigned to guide organizers through events. For Campus Connect organizers, an Event Supporter is typically assigned during the application and review process. They are your primary human touchpoint within the WordPress community structure during event planning and execution. If you have a question about how something should work, your Event Supporter is usually the right first contact.

Program Supporters. Program Supporters (formerly known as Community Deputies) review applications, interview organizers, and keep events moving through the process. They are the people who manage the operational side of WordPress Education Programs at the community level. If your application is in review, if there is a question about your event's status, or if something is stuck in the process, a Program Supporter is the right contact.

Example

Who I should contact with if during WordCamp something is not going OK?

Event Supporters
They are your primary human touchpoint within the WordPress community structure during event planning and execution

Program Supporters
if there is a question about your event's status, or if something is stuck in the process

Other information (optional)

This issue is created following the HS ticket 3325019623

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 lesson at the provided Content URL and review the Event Supporters and Program Supporters sections together. Update the content so the roles and the appropriate contact for an event problem are clearly distinguished, then verify the revised lesson gives organizers an unambiguous example.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.