When to document new features #488
-
On https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/What_we_write, the following is written:
Of course! it goes on:
Browsers that implement new features generally want to document them, and will document them. My question surrounds deciding when to include that documentation. The page continues:
the issue is, there is no "and" or "or" in that list. I think it should be "and" but we've been doing "or". |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
There is a "when" section further down: https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/What_we_write#when_we_document_a_new_technology
^^^ That is the priority. In practice it is more like "Be implemented by at least one rendering engine." AND one of the other lines. Things don't have to be on the standards track or be in stable versions, so those definitely are "OR" (more about prioritization) |
Beta Was this translation helpful? Give feedback.
There is a "when" section further down: https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/What_we_write#when_we_document_a_new_technology
^^^ That is the priority.
In practice it is more like "Be implemented by at least one rendering engine." AND one of the other lines. Things don't have to be on the standards …