The following guidelines cover how to write HTML example code for MDN Web Docs.
Opinions on correct indentation, whitespace, and line lengths have always been controversial. Discussions on these topics are a distraction from creating and maintaining content.
On MDN Web Docs, we use Prettier as a code formatter to keep the code style consistent (and to avoid off-topic discussions). You can consult our configuration file to learn about the current rules, and read the Prettier documentation.
Prettier formats all the code and keeps the style consistent. Nevertheless, there are a few additional rules that you need to follow.
Note: The guidelines in this section apply only when you need to show a complete HTML document. A snippet is usually enough to demonstrate a feature. When using the EmbedLiveSample macro, just include the HTML snippet; it will automatically be inserted into a full HTML document when displayed.
You should use the HTML5 doctype. It is short, easy to remember, and backwards compatible.
You should also define your document's characterset like so:
<meta charset="utf-8" />
Use UTF-8 unless you have a very good reason not to; it will cover all character needs pretty much regardless of what language you are using in your document.
Finally, you should always add the viewport meta tag into your HTML
<head> to give the code example a better chance of working on mobile devices. You should include at least the following in your document, which can be modified later on as the need arises:
<meta name="viewport" content="width=device-width" />
See Using the viewport meta tag to control layout on mobile browsers for further details.
You should put all attribute values in double quotes. It is tempting to omit quotes since HTML5 allows this, but markup is neater and easier to read if you do include them. For example, this is better:
<img src="images/logo.jpg" alt="A circular globe icon" class="no-border" />
<img src=images/logo.jpg alt=A circular globe icon class=no-border>
Omitting quotes can also cause problems. In the above example, the
alt attribute will be interpreted as multiple attributes because there are no quotes to specify that "A circular globe icon" is a single attribute value.
Don't include values for boolean attributes (but do include values for enumerated attributes); you can just write the attribute name to set it. For example, you can write:
<input required />
This is perfectly understandable and works fine. If a boolean HTML attribute is present, the value is true. While including a value will work, it is not necessary and incorrect:
<input required="required" />
Use lowercase for all element names and attribute names/values because it looks neater and means you can write markup faster. For example:
<p class="nice">This looks nice and neat</p>
<P CLASS="WHOA-THERE">Why is my markup shouting?</P>
Don't use entity references unnecessarily — use the literal character wherever possible (you'll still need to escape characters like angle brackets and quote marks).
As an example, you could just write:
<p>© 2018 Me</p>
<p>© 2018 Me</p>
There are some rules for writing about HTML elements on MDN Web Docs. Adhering to these rules produces consistent descriptions of elements and their components and also ensures correct linking to detailed documentation.
Element names: Use the
HTMLElementmacro, which creates a link to the MDN Web Docs page for that element. For example, writing
<title>". If you don't want to create a link, enclose the name in angle brackets and use the "Inline Code" style (e.g.,
Attribute names: Use "Inline Code" style to put attribute names in
code font. Additionally, put them in
bold facewhen the attribute is mentioned in association with an explanation of what it does or when it is used for the first time on the page.
- Attribute values: Use the "Inline Code" style to apply
<code>to attribute values, and don't use quotation marks around string values, unless needed by the syntax of a code sample. For example, "When the
typeattribute of an
<input>element is set to