MDN Web Docs needs your help! We have a large number of typos to fix, examples to write, bugs to fix, people to talk to, and more, and the number is growing as more people start using the site. This page outlines what you can do to help.
If you haven't contributed to MDN previously, the Getting Started guide can help you pick a task to jump in and help with.
What can I do to help?
There are multiple avenues you can take to contribute to MDN depending on your skillset and interests. Along with each task we provide a short description and an approximate time that each type of task typically takes.
If you are not sure what to do, you are always welcome to ask for help.
Primary contribution types
The links in this section lead to detailed guides explaining how to do a particular contribution task that we are most interested in getting community help with, either because they are a critical function, and/or because they have a large backlog associated with them. Please consider helping out with these tasks before you consider contributing in other ways.
|Fixing MDN content bugs||Our sprints repo is where people submit issues to report problems found with MDN docs. We get a lot of these, and any help you can give in fixing them would be much appreciated.||
|Help beginners to learn on MDN||Our Learn web development pages get over a million views per month and have active forums where people go to ask for general help, or request that their assessments be marked. We’d love some help with answering posts and growing our learning community.||
We will add more tasks here as time goes on.
Other task types
If our main priorities listed above don't interest you, you can find a number of other, more general task types to get involved with below, split up by skillset.
If you are more interested in words, you could do the following:
- Set the summary for a page (5-15 minutes)
- Update an existing article with new information (5 minutes-1 hour)
- Write a new entry in the Glossary (15 minutes-1 hour)
- Write an article to help people learn about the web (1-3 hours)
If you are more interested in code, you could try your hand at the following:
- Convert code samples to be "live" (30 minutes)
- Send a code patch to the Kuma codebase (1 hour)
- Write an interactive example (1 hour)
If you are interested in words and code, you could try your hand at the following:
- Technical reviews (30 minutes)
- Write or update an API reference (30 minutes to 2 hours, or more)
- Write a new article on a topic you are familiar with (1 hour or more)
- Add or update browser compatibility data on a reference page (30 minutes to 1 hour)
Note: If you have found something that is incorrect on MDN but you're not sure how to fix it, you can report problems by filing a documentation issue. Please give the issue a descriptive title. (It's not helpful to say "Dead link" without saying where you found the link. Pro tip: Most "dead links" on MDN are to articles that haven't been written yet.)
Other useful pages
- Documentation processes
- The MDN documentation project is enormous; there are a vast number of technologies we cover through the assistance of hundreds of contributors from across the world. To help us bring order to chaos, we have standard processes to follow when working on specific documentation-related tasks. Here you'll find guides to those processes.
- Fixing MDN content bugs
- Our sprints repo is where people submit issues to report problems found with MDN docs. We get a lot of these, and any help you can give in fixing them would be much appreciated.
- Getting started on MDN
- We are an open community of developers building resources for a better Web, regardless of brand, browser, or platform. Anyone can contribute and each person who does makes us stronger. Together we can continue to drive innovation on the Web to serve the greater good. It starts here, with you.
- GitHub best practices
- This page is a set of best practices for working with GitHub, which are useful when contributing to many different task types on MDN.
- Help beginners to learn on MDN!
- Our Learn web development pages get over a million views per month, and have active forums where people go to ask for general help, or request that their assessments be marked. We’d love some help with answering posts, and growing our learning community.
- Localizing MDN
- MDN is used by people all over the world as a reference and guide to Web technologies, as well as to the internals of Firefox itself. Our localization communities are a key part of the Mozilla project; their work in translating and localizing our documentation helps people around the world develop for the open Web. If you'd like to learn more about localization, or even start a new localization, this is the place to begin.
- MDN web docs: How-to guides
- These articles provide step-by-step guides to accomplishing specific goals when contributing to MDN.
- MDN web docs: Onboarding Guide
- This document covers topics that a professional writer who will be working full-time on MDN needs to know to get started. If you contribute to MDN on a casual basis, you don't need to worry about this
- Send feedback about MDN Web Docs
- If you have suggestions for, or are having problems using the MDN Web Docs, this is the right place to be. The very fact that you're interested in offering feedback makes you even more a part of the Mozilla community, and we thank you in advance for your interest.You have several options for offering your insight; this article will help you do so.