# HTML Standard contributor guidelines
These are the guidelines for contributing to the HTML Standard. First see the [WHATWG contributor guidelines](https://github.com/whatwg/meta/blob/master/CONTRIBUTING.md).
The HTML Standard is quite complex and people notice minor and larger issues with it all the time. We'd love your help fixing these. Pull requests for typographical and grammar errors are also most welcome.
We label [good first issues](https://github.com/whatwg/html/labels/good%20first%20issue) that you could help us fix, to get a taste for how to submit pull requests, how the build process works, and so on.
We'd be happy to mentor you through this process. If you're interested and need help getting started, leave a comment on the issue or bug, or ask around [on IRC](https://wiki.whatwg.org/wiki/IRC). The [FAQ](FAQ.md) may also be helpful.
## Pull requests
In short, change `source` and submit your patch, with a [good commit message](https://github.com/erlang/otp/wiki/Writing-good-commit-messages). Try to follow the source formatting rules below.
Note that `source` is written in a dialect of HTML, which is eventually compiled into the deployed standard by a tool called [Wattsi](https://github.com/whatwg/wattsi). Documentation for this dialect can be found [in the Wattsi repository](https://github.com/whatwg/wattsi/blob/master/Syntax.md).
Please add your name to the Acknowledgments section (search for `<!-- ACKS`) in your first pull request, even for trivial fixes. The names are sorted lexicographically.
To preview your changes locally, follow the instructions in the [html-build repository](https://github.com/whatwg/html-build).
## The developer's edition
In addition to generating the [singlepage](https://html.spec.whatwg.org/) and [multipage](https://html.spec.whatwg.org/multipage/) specifications, we also generate an [edition for developers](https://html.spec.whatwg.org/dev/). This is meant to exclude content that is of interest only to implementers. We can always use community help in properly enforcing this distinction, especially since for a long period the developer's edition was not working and so we made a lot of changes without properly considering their impact on it.
To mark an element as being omitted from the developer's edition, use a `w-nodev` attribute. To only include it in the developer's edition, use a `w-dev` attribute. This may require introducing container `<div>`s or `<span>`s; that's fine. Note that Web IDL blocks (`<pre class="idl">`) are automatically omitted by the build process, and so don't need `w-nodev` attributes. (There also exist `w-nohtml`, `w-nosnap`, and `w-noreview` attributes which exclude information from the Living Standard, the Commit Snapshot, and the Review Draft respectively. Day-to-day changes will not require them.)
Another interesting feature is the `subdfn` attribute. This is useful for when something is defined inside text that is not present in the developer's edition (such as a Web IDL block). In that case, we can use the `subdfn` attribute on something which has a matching `data-x` attribute, to indicate the definition of the term for the purposes of the developer's edition.
In general we want to omit from the developer's edition:
* Any Web IDL; instead, the `<dl class="domintro">` descriptions suffice.
* The definitions of IDL attributes and operations as algorithmic steps (ditto).
* Other instructions for user agents on how to implement a feature.
* Definitions of low-level concepts and terms that do not impact web development.
On the other hand, we want to especially keep:
* High-level descriptions and introductions
* Authoring instructions
* Helpful notes about common situations
In between these clear-cut categories, there is some gray area. Please feel free to open an issue if you think something is being included that shouldn't be, or is being excluded but should be kept.
## Source formatting
Due to the long legacy of the existing text the guidelines below are not always applied. We do require that you apply the guidelines when making changes, though are happy to provide assistance if this proves to be a blocker to you.
Use a column width of 100 characters and add newlines where whitespace is used. (Emacs, set `fill-column` to `100`; in Vim, set `textwidth` to `100`; and in Sublime, set `wrap_width` to `100`.)
Using newlines between "inline" element tag names and their content is forbidden. (This actually alters the content, by adding spaces.) That is,
<dd><span>Parse error</span>. Create a new DOCTYPE token. Set its <i data-x="force-quirks
flag">force-quirks flag</i> to …
is fine and
<dd><span>Parse error</span>. Create a new DOCTYPE token. Set its <i data-x="force-quirks flag">
force-quirks flag</i> to …
Using newlines between attributes and inside attribute values that contain whitespace is allowed.
Always wrap after putting the maximum number of characters on a single line within these guidelines.
An `<li>` element always has a `<p>` element inside it, unless it's a child of `<ul class="brief">`.
List items (`<li>`, `<dt>`, and `<dd>`) always start on their own line with a newline between them
and the previous list item. No extra newline at the start or end of the list though:
<li><p>Let <var>x</var> be 1.</p></li>
<li><p>Increment <var>x</var> by 2.</p></li>
If a "block" element contains a single "block" element, do not put it on a new line.
Do not indent for anything except a new "block" element. For instance
<li><p>Let <var>corsAttributeState</var> be the current state of the element's <code
data-x="attr-link-crossorigin">crossorigin</code> content attribute.</p></li>
is not indented, but
<p>For each <var>element</var> in <var>candidate elements</var>, run the following
End tags must not be omitted (except where it is consistent to do so) and attribute values must be quoted (use double quotes).