Content-Length: 281205 | pFad | http://github.com/github/docs/issues/39246

D5 Suggestion to Add New Labels for Better Issue Categorization and Contribution Clarity · Issue #39246 · github/docs · GitHub
Skip to content

Suggestion to Add New Labels for Better Issue Categorization and Contribution Clarity #39246

Open
@surajsk2003

Description

@surajsk2003

Code of Conduct

What article on docs.github.com is affected?

Not a specific article, but the Label reference section under the contributing area (found at: docs.github.com) which lists available issue labels.

Image

What changes are you suggesting?

I propose the addition of a few new labels that can make the contribution process more streamlined and accessible:

Suggested New Labels

label: accessibility
Description: Issues related to accessibility standards (like screen reader compatibility, keyboard navigation, color contrast, etc.).

label: UX improvement
Description: Suggestions or issues that aim to enhance user experience and UI clarity on docs.github.com.

label: translation/internationalization
Description: Issues related to translating content or making the site more usable across different languages/locales.

label: infra/config
Description: Issues about deployment scripts, CI/CD workflows, repository configuration, GitHub Actions, etc.

label: feedback-needed
Description: Issues or PRs that need community or maintainer input before proceeding.

Why should the docs be changed? What use cases does it support?

-Makes issues more searchable and filtered according to contributor interest/expertise.

-Helps newcomers navigate based on skills (e.g., UI vs backend vs translation).

-Gives maintainers more precision in classifying and managing incoming contributions.

-Expands inclusivity — especially with labels like translation and accessibility.

What is the expected outcome?

-Addition of 3–5 new labels with proper descriptions and possibly linking them from the label reference section in the docs.

-More organized and discoverable contribution workflow.

-Improved contributor onboarding experience.

Additional information

I'm happy to help implement the label addition or update documentation pages accordingly.
This suggestion is based on best practices from other OSS repositories like Node.js, MDN, and Next.js.

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions









      ApplySandwichStrip

      pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


      --- a PPN by Garber Painting Akron. With Image Size Reduction included!

      Fetched URL: http://github.com/github/docs/issues/39246

      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy