Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Welcome to the Yoast Contributor Day - WordPress Documentation Team's #1742

Open
estelaris opened this issue Oct 15, 2024 · 1 comment
Open
Assignees
Labels
6.1 Changes in 6.1 release 6.2 Changes in 6.2 release 6.3 Changes in 6.3 release 6.4 Changes in 6.4 release 6.5 Changes in 6.5 release 6.6 Changes in 6.6 release Contributor Day Issues providing info for specific Contributor Days

Comments

@estelaris
Copy link
Member

estelaris commented Oct 15, 2024

The Make WordPress Documentation Team's participation in the Yoast Contributor Day. It’s held on the fourth Tuesday of each month.

You can join us on October 17, between 7:30 - 14:00 UTC.

For those attending this Contributor Day

If you attend this Contributor Day, please comment below with:

  • Your WordPress.org profile username
  • Link(s) to the issue(s) you're working on during the Contributor Day
  • People to go ask for help on: @estelaris,

Environment

You can set WordPress install in one click by visiting https://playground.wordpress.net/ use InstaWP sandbox https://app.instawp.io/onboard

Any questions you have, aks them in the Zoom call or go to #docs Slack channel in the WordPress Slack.

New(er) contributors

If this is your first time contributing to the Documentation team, please make sure you have the following accounts:

Following videos/onboarding sessions can be helpful for performing the tasks we plan to work on:

For general details on how GitHub works, check out GitHub’s Getting Started Guide.

When you find issue you'd like to work on in the Docs Team Issue Tracker here on GitHub:

  1. Please leave a comment in that issue with /assign to assign yourself to the issue and avoid more than one person working on the same issue, and
  2. When the issue is complete and you're submitting your content, also add /review to the comment so the issue can automatically have its status switched so that it's set to be reviewed.

Onboarding during Contributor Day

If you have questions or need onboarding, feel free to ask in the #docs channel on Slack or in the call.

Task list for new(er) contributors

For those who wish to contribute who are new(er) to the team, once you have taken a look at the onboarding material above, please feel free to take a look at our project boards that have issues labeled as a "good first issue":

Person to go to for help: @estelaris

General task list

Tasks we plan to work on during the day:

Updating block editor end user documentation

WordPress 6.6: 31
WordPress 6.5: 16
WordPress 6.4: 115
WordPress 6.3: 27
WordPress 6.2: 20
WordPress 6.1: 1

Other options for contributing

If the above list doesn't work for you, we have plenty of other issues you can work on:

high priority
good first issue
developer documentation (DevHub)
user documentation (HelpHub)
advanced administration
contributor documentation
and many more.. just take a look at all the labels.

@estelaris estelaris added 6.1 Changes in 6.1 release 6.2 Changes in 6.2 release 6.3 Changes in 6.3 release 6.4 Changes in 6.4 release 6.5 Changes in 6.5 release 6.6 Changes in 6.6 release Contributor Day Issues providing info for specific Contributor Days labels Oct 15, 2024
@estelaris estelaris self-assigned this Oct 15, 2024
Copy link

Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.1 Changes in 6.1 release 6.2 Changes in 6.2 release 6.3 Changes in 6.3 release 6.4 Changes in 6.4 release 6.5 Changes in 6.5 release 6.6 Changes in 6.6 release Contributor Day Issues providing info for specific Contributor Days
Projects
Status: No status
Status: No status
Status: No status
Status: No status
Development

No branches or pull requests

1 participant