Please note, this is a STATIC archive of website developer.mozilla.org from 03 Nov 2016, cach3.com does not collect or store any user information, there is no "phishing" involved.

Guidelines

Our volunteers haven't translated this article into عربي yet. Join us and help get the job done!

These guides provide details on how MDN documentation should be written and formatted, as well as how our code samples and other content should be presented. By following these guides, you can ensure that the material you produce is clean and easy to use.

Best practices
This article describes recommended ways of working with content on MDN. These guidelines describe preferred ways of doing things that lead to better results, or offer advice on deciding among multiple ways of doing similar things.
CSS style guide
MDN has many built-in global styles available for use when styling and laying out articles — this article serves as a reference guide to what's available, explaining which styles are available and how to use each one.
Code sample guidelines
The biggest advantage to adhering to these guidelines is that it will foster consistency across our samples and demos on MDN, which increases readability and comprehension overall.
Does this belong on MDN?
If you're preparing to document something, you may be trying to decide where to put the information. There are several places that documentation can go, and while MDN is among the largest documentation repositories on the Web, it's not the only one.
Writing style guide
In an effort to present documentation in an organized, standardized and easy-to-read manner, the Mozilla Developer Network style guide describes how text should be organized, spelled, formatted, and so on. These are guidelines rather than strict rules.

Document Tags and Contributors

 Contributors to this page: jswisher, Sheppy
 Last updated by: jswisher,