GitHub Discussions
On MDN Web Docs, we encourage our community to start and engage in discussions around topics related to the project. We ask that you keep each discussion focused on the topic at hand instead of covering multiple subjects in a discussion.
[!NOTE] Don’t use GitHub Discussions to report bugs. If you see something wrong on MDN Web Docs, open a GitHub issue in the the relevant GitHub repository.
If you’re not sure whether to open a GitHub issue or discussion, here’s what each are for:
- Issues are for reporting bugs or tracking a work item with defined and actionable tasks and outcomes.
- Discussions are for reaching consensus about how we’re working and for defining tasks.
If your discussion doesn’t progress or you’re unsure of the next steps, refer to the Guidelines for managing and resolving discussions for advice on moving forward, including expectations on timelines.
Check out the subject of each discussion category below so that you can start your discussion in the proper place.
| Discussion Category | Subject |
|---|---|
| 📣 Announcements | Reserved for MDN Web Docs staff. We ask that you choose one of the other available categories. |
| 🔮 Browser compatibility data | The browser-compat-data project which documents compatibility data for browsers. |
| ✏️ Content | The content repository on MDN Web Docs. Don’t ask for coding help here - if you’re stuck on a problem, try the Learn Web Development area. |
| 🌐 Localization | The translated-content repository covering our supported locales. This is also where deprecation notices happen. |
| 👾 MDN Plus | The MDN Plus features as well as your ideas. For MDN Plus support such as subscriptions, refer to Mozilla’s official support channel. |
| 🛠️ Platform | The frontend and build system of MDN Web Docs. If you found a bug, report it on the relevant repository. NOTE: There is a separate discussion category for MDN Plus. |