User-Stories for an Inclusive Language Checker on make/WordPress

[CoachBirgit]

Summary

This document outlines user stories for different roles in the WordPress community, including meeting coordinators, documentation writers, support responders, and bug reporters. Each user story emphasizes the importance of inclusivity, accessibility, and clear communication in their respective tasks.

1. Ava, the Meeting Coordinator:
   • Ava is responsible for publishing meeting notes and agendas on a Make/WordPress blog.
   • User Story: As a meeting coordinator, Ava wants to ensure that her meeting notes and agendas are clear, inclusive, and accessible to all community members, regardless of their native language or cultural background.
2. Liam, the Developer Documentation Writer:
   • Liam contributes by writing developer documentation for WordPress.
   • User Story: As a developer documentation writer, Liam needs to use technical language that is also inclusive and easy to understand, helping developers from diverse backgrounds to effectively engage with WordPress.
3. Mia, the End User Documentation Author:
   • Mia focuses on writing documentation for end users of WordPress.
   • User Story: As an end user documentation author, Mia aims to create content that is not only informative but also accessible and easy to comprehend for users with different levels of WordPress expertise and varying cultural contexts.
4. Noah, the Contributor Guide Creator:
   • Noah writes documentation aimed at guiding new contributors to WordPress.
   • User Story: As a contributor guide creator, Noah needs to ensure his guides are welcoming, clear, and inclusive, encouraging participation from people of all backgrounds and skill levels.
5. Emma, the Release Notes Publisher:
   • Emma is tasked with writing comprehensive and accessible release notes for WordPress updates.
   • User Story: As a release notes publisher, Emma wants to create notes that are both technically accurate and easy to understand, catering to a wide range of users from experts to novices.
6. Ethan, the Support Responder:
   • Ethan volunteers by replying to support tickets from WordPress users.
   • User Story: As a support responder, Ethan aims to provide helpful, respectful, and clear responses that cater to users’ diverse technical backgrounds and language proficiencies.
7. Sophia, the Bug Reporter:
   • Sophia actively participates in the WordPress community by filing bug reports.
   • User Story: As a bug reporter, Sophia needs to describe issues in a way that is clear and understandable to developers and community members from various cultures, ensuring that problems are effectively communicated and resolved.

Missing Personas?

• Theme Review
• GitHub Tickets
• Locale manager on Rosetta sites

[zzap]

We could add a GitHub issues coordinator - a person who initially responds to reported issues. There might not be a lot of use cases for this, but in the case of a first-time contributor reporting an issue, it is extremely important how the first response will look.

[zzap]

Question: Does this concern only documentation or any written communication? For example, running the meeting in Slack can't really be controlled by any tool, but language and attitude go a long way. Is this case out of the project's scope (as in covered by the documentation and Code of Conduct)?