Link to the pathway
https://make.wordpress.org/handbook/pathways/write/file-a-documentation-issue/
What kind of issue?
Unclear or confusing steps
What's wrong?
Steps section
Please review my comment on the Walkthrough issue for feedback on steps.
Intro section
Also link the words "Documentation Issue Tracker" in the intro: Documentation Issue Tracker
What happens next section
- Move this section above the "Contributions checklist" section so content follows a more logical reading order. After submitting an issue for review, users will. naturally wonder what happens next.
- Edit access is mentioned in the Steps, but not here. Recommend including in just one place or both.
- Update link text "working on one" to "working on an existing issue" so it's more clear for screen readers what this link is about.
- This section repeats what's in Step 5, but does not include information about edit access so it feels like it's missing content.
- Suggest something like the following:
- "A contributor will review your work and comment with any suggestions, or they will apply the changes and close the issue. If you have not received a response from reviewers after 2-3 weeks, politely ping the #docs Slack channel to request a review. If you have editing access to make changes, after someone has reviewed your changes, you may update the document and close the issue."
- Make sure "#docs" is linked
Contributions checklist section
- Add period after each list item so they follow the same convention as other lists on the page.
- Link to the "#docs" channel
- Rephrase "Content follows the documentation style guides" to "Content follows documentation style guidelines and best practices. Refer to the Help section for more details."
- It's not clear what is meant by "documentation style guides," but they are all referenced under the "further reading section." As a new contributor, I have not seen these before, and they are very helpful.
Suggested fix
I've included suggested fixes to problems up above
Link to the pathway
https://make.wordpress.org/handbook/pathways/write/file-a-documentation-issue/
What kind of issue?
Unclear or confusing steps
What's wrong?
Steps section
Please review my comment on the Walkthrough issue for feedback on steps.
Intro section
Also link the words "Documentation Issue Tracker" in the intro: Documentation Issue Tracker
What happens next section
Contributions checklist section
Suggested fix
I've included suggested fixes to problems up above