👋 Welcome to the MDN Web Docs project! We are delighted with your interest in this project.
At MDN, we put people first and do our best to recognize, appreciate, and respect the diversity of our global contributors. We welcome contributions from everyone who shares our goals and wants to contribute constructively and respectfully to this project.
mdn-community is the repository where you will find the public feedback discussions for the MDN Web Docs project.
Note: By participating in and contributing to our projects and discussions, you acknowledge that you have read and agree to the Mozilla community participation guidelines.
On MDN Web Docs, we encourage our community to start and/or engage in discussions around topics related to the overall project. Discussions are categorized by different topics areas. We ask that you keep each discussion focused on the topic at hand, instead of covering multiple topics in one discussion.
NOTE: mdn-community/discussions is not the place to report problems. For content-related problems you come across on MDN Web Docs, it is best to raise issues against the relevant project. If you're ever in doubt about whether to open an issue or a discussion, consider the following guidelines:
- Issues are for reporting a bug with a clearly defined and actionable outcome.
- If the issue needs a discussion to agree upon a course of action or define an actionable piece of work, you are in the right place.
Check out the definition of each discussion category below so that you can start your discussion in the proper place.
| Discussion category | Category subject |
|---|---|
| 📣 Announcements | This category is reserved for MDN Web Docs staff to make any announcements in relation to the MDN project |
| 🔮 Browser compatibility data | Discussions related to the browser-compat-data project. |
| ✏️ Content | Discussions related to the content on MDN Web Docs. Note: This is not the place to ask for help with code examples. For code-related help, please join our community on Discourse. |
| 🎨 Design system | Discussions related to design improvements. Design is subjective, but we are always open to suggestions from the community. Any improvement that can help the MDN Web Docs experience even better for a wider audience is welcome. If you have constructive feedback around the design, user experience, and accessibility of MDN Web Docs, we'd love to hear from you. |
| 👩💻 Code examples | Discussions related to all code examples on MDN Web Docs. This includes interactive examples, live samples and static code examples. For help with general coding challenges on MDN Web Docs, please join our community on Discourse. |
| 🌐 Localization | Discussions related to the translated-content repository covering our supported locales. This is also typically where announcements of macro deprecation will happen. |
| 👾 MDN Plus | Discussions related to the existing MDN Plus feature set as well as feature ideas. For MDN Plus support such as subscriptions, please refer to our official support channel. |
| 🛠️ Platform | Discussions related to the core MDN Web Docs platform. Your suggestions to improve the architecture and existing features, such as navigation and search, are welcome. However, if you believe you found a bug related to the platform, please report it on the Yari repository. This is also the place for discussions related to existing tooling, such as BoB, markdown, reusable workflows, etc. NOTE: This category is not for MDN Plus-related feature discussions. There is a separate discussion category for MDN Plus. |
| 🤖 Polls | This category is meant for use by the MDN Web Docs staff. We will use this category to run polls around topics where we need your input. So, keep your eyes peeled 👀 |
A note on discussions labelled as archived: We label some discussions with an
archivelabel because we sometimes find two or more discussions around the same topic. Currently, you cannot merge two discussions into one; our workaround is to add a link in the most active discussion that references the least active discussion(s). We will lock older discussions and add thearchivedlabel, which allows us to keep the older discussion history but focus on active discussions.
To ensure we maintain a healthy, friendly, and welcoming community, we want to highlight the behaviours we expect from our community.
- Being respectful
- Value each other’s ideas, styles, and viewpoints. We may not always agree, but disagreement is no excuse for poor manners.
- Being direct but professional
- We must be able to speak directly when we disagree and when we think we need to improve. We need to be honest and direct, as well as respectful.
- Being inclusive
- Seek diverse perspectives. Diversity of views and of people on teams powers innovation, even if it is not always comfortable. Encourage all voices.
- Understanding different perspectives
- Our goal should not be to “win” every disagreement or argument. A more productive goal is to be open to ideas that make our own ideas better.
- Appreciating and accommodating our similarities and differences
- Be respectful of people with different cultural practices, attitudes, and beliefs. Work to eliminate your own biases, prejudices, and discriminatory practices. Think of others’ needs from their point of view.
- Leading by example
- Design your community and your work for inclusion. Hold yourself and others accountable for inclusive behaviours. Make decisions based on the highest good.
As important as knowing how you should conduct yourself is understanding unacceptable conduct.
- Violence and threats of violence
- Violence and threats of violence are not acceptable - online or offline.
- Personal attacks
- Conflicts will inevitably arise, but frustration should never turn into a personal attack. It is not okay to insult, demean, or belittle others.
- Derogatory language
- If you’re unsure if a word is derogatory, don’t use it. This also includes repeated subtle and/or indirect discrimination; when asked to stop, stop the behaviour in question.
- Unwelcome sexual attention or physical contact
- This includes sexualised comments, jokes or imagery in interactions, communications, or presentation materials, as well as inappropriate touching, groping, or sexual advances.
- Disruptive behaviour
- Sustained disruption of events, forums, or meetings, including talks and presentations, will not be tolerated.