Content type: Handbook

  • Defending the community: What’s not appropriate

    Negativity happens, combat it with positivity. It goes without saying that we all respond better to positive reinforcement than negative, so keep your responses upbeat and helpful, even when you disagree with another forum volunteer. Instead of saying something like “that’s a bad, buggy plugin,” it is more helpful to say something like “you might…

  • Using your profile to see replies

    Your profile lists threads you have started as well as those to which you have replied, and whether there has been activity since. If you do not use the “Notify me of follow-up posts via email” feature then your profile is the best way to stay informed about what has happened.

  • Giving good support

    Users coming to the Support Forums for help may be in wildly varying emotional states – from mildly frustrated, to desperate, to quite angry. At all times, keep in mind that you’re there to provide help. This attitude will predispose you to deal with Forum users in a professional and courteous manner, regardless. If a user…

  • The ‘No replies’ view

    You can filter the forum posts by different criteria. A filter often used is “No replies” – posts which got no answer. This is the link that selects the posts with no replies: https://wordpress.org/support/view/no-replies

  • Adding New Users

    Locale Managers of each locale team have permission to add other users to their Rosetta site. For further details of user roles for Polyglots contributors, check out the Roles and Capabilities page. Adding new Editors, Authors, and Contributors Adding a Rosetta Site User If you want other team members to help maintain the Rosetta site…

  • Setting Up Your Machine

    TL;DR: We recommend VVV, along with the WordPress Meta Environment addon. At the bottom of the page you can find some dockerized environments, which are more up to date than VVV, to work in some sections of worpress.org. The basic requirement is to have a local web server on your machine that you can run WordPress…

  • About the Accessibility Team

    WordPress constantly evolves and improves. It is never “done.” The same is true of WordPress accessibility. Changes in design, user experience, and code need to be evaluated. The Accessibility Team provides continuing reviewing and educational support for WordPress’ accessibility. Team meetings are held every two weeks in the #accessibility channel on Slack. Check the schedule…

  • Site Feedback Guide

    On occasion, the Make WordPress Accessible group has been asked to review a wordpress.org site and provide feedback on any accessibility issues. The following document contains a series of guidelines (organised by skill level and technology usage) that should enable you to do so — irrespective of whether you are a technical developer or a…

  • Accessibility Team Handbook

    In this Make WordPress Accessibility Handbook you will learn about the WordPress Accessibiliy Team and how to get involved in WordPress Accessibility. Our Mission The Accessibility Team works to make WordPress accessible to as many people as possible. This means making sure people are not just able to read web pages but also to create…

  • Accessibility Guidelines

    The primary guidance for web accessibility on a global basis are the Web Content Accessibility Guidelines, commonly referred to as WCAG. WordPress requires that all content meet WCAG guidelines, but also pushes to provide accessibility beyond that minimum whenever possible. WordPress Accessibility Coding Standard All new or updated code released in WordPress must conform with…