Skip to content

[Docs Handbook] Reporting an Issue page recommends Slack over GitHub, causing confusion for new contributors #2207

@centeno2606

Description

@centeno2606

Issue Description

The Reporting an Issue page in the Docs Handbook states that the easiest
way to report documentation issues is via the #docs Slack channel.
However, this recommendation may not be accessible or clear to all
contributors, especially those who are just getting started.

URL of the Page with the Issue

https://make.wordpress.org/docs/handbook/workflows/reporting-an-issue/

Section of Page with the issue

The section recommending Slack as the primary/easiest method to report issues.

Why is this a problem?

  • Not all contributors have Slack access
  • New contributors may not know how to join WordPress Slack
  • This creates confusion since GitHub Issues are also the primary
    reporting method
  • This page targets new contributors specifically, so clarity here
    is especially important

Suggested Fix

Consider clarifying the intended workflow by:

  1. Adding a clear recommendation to use GitHub Issues as the primary method
  2. Including instructions or a link on how to join WordPress Slack
    (if Slack is still recommended as a secondary option)
  3. Explaining when to use Slack vs GitHub Issues, so contributors
    know which channel is appropriate for which situation

This would reduce friction for new contributors and make the onboarding
experience more consistent with the current GitHub-based workflow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions