Update unordered list and list items to markdown format

Author: ntwb

wordpress-coding-standards/css.md

@@ -7,11 +7,11 @@ Within core stylesheets, inconsistencies will often be found. We are working on
 ## Structure
 
 There are plenty of different methods for structuring a stylesheet. With the CSS in core, it is important to retain a high degree of legibility. This enables subsequent contributors to have a clear understanding of the flow of the document.
-<ul>
- 	<li>Use tabs, not spaces, to indent each property.</li>
- 	<li>Add two blank lines between sections and one blank line between blocks in a section.</li>
- 	<li>Each selector should be on its own line, ending in either a comma or an opening curly brace. Property-value pairs should be on their own line, with one tab of indentation and an ending semicolon. The closing brace should be flush left, using the same level of indentation as the opening selector.</li>
-</ul>
+
+- Use tabs, not spaces, to indent each property.
+- Add two blank lines between sections and one blank line between blocks in a section.
+- Each selector should be on its own line, ending in either a comma or an opening curly brace. Property-value pairs should be on their own line, with one tab of indentation and an ending semicolon. The closing brace should be flush left, using the same level of indentation as the opening selector.
+
 Correct:
 
 ```css
@@ -37,12 +37,12 @@ Incorrect:
 ## Selectors
 
 With specificity, comes great responsibility. Broad selectors allow us to be efficient, yet can have adverse consequences if not tested. Location-specific selectors can save us time, but will quickly lead to a cluttered stylesheet. Exercise your best judgement to create selectors that find the right balance between contributing to the overall style and layout of the DOM.
-<ul>
- 	<li>Similar to the <a href="https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#naming-conventions">WordPress PHP Coding Standards</a> for file names, use lowercase and separate words with hyphens when naming selectors. Avoid camelcase and underscores.</li>
- 	<li>Use human readable selectors that describe what element(s) they style.</li>
- 	<li>Attribute selectors should use double quotes around values</li>
- 	<li>Refrain from using over-qualified selectors, <code>div.container</code> can simply be stated as <code>.container</code></li>
-</ul>
+
+- Similar to the <a href="https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#naming-conventions">WordPress PHP Coding Standards</a> for file names, use lowercase and separate words with hyphens when naming selectors. Avoid camelcase and underscores.
+- Use human readable selectors that describe what element(s) they style.
+- Attribute selectors should use double quotes around values
+- Refrain from using over-qualified selectors, <code>div.container</code> can simply be stated as <code>.container</code>
+
 Correct:
 
 ```css
@@ -82,12 +82,12 @@ input[type=text] { /&042; Should be [type="text"] &042;/
 ## Properties
 
 Similar to selectors, properties that are too specific will hinder the flexibility of the design. Less is more. Make sure you are not repeating styling or introducing fixed dimensions (when a fluid solution is more acceptable).
-<ul>
- 	<li>Properties should be followed by a colon and a space.</li>
- 	<li>All properties and values should be lowercase, except for font names and vendor-specific properties.</li>
- 	<li>Use hex code for colors, or rgba() if opacity is needed. Avoid RGB format and uppercase, and shorten values when possible: <code>#fff</code> instead of <code>#FFFFFF</code>.</li>
- 	<li>Use shorthand (except when overriding styles) for background, border, font, list-style, margin, and padding values as much as possible. (For a shorthand reference, see <a href="https://codex.wordpress.org/CSS_Shorthand">CSS Shorthand</a>.)</li>
-</ul>
+
+- Properties should be followed by a colon and a space.
+- All properties and values should be lowercase, except for font names and vendor-specific properties.
+- Use hex code for colors, or rgba() if opacity is needed. Avoid RGB format and uppercase, and shorten values when possible: <code>#fff</code> instead of <code>#FFFFFF</code>.
+- Use shorthand (except when overriding styles) for background, border, font, list-style, margin, and padding values as much as possible. (For a shorthand reference, see <a href="https://codex.wordpress.org/CSS_Shorthand">CSS Shorthand</a>.)
+
 Correct:
 
 ```css
@@ -114,14 +114,15 @@ Incorrect:
 
 <blockquote>"Group like properties together, especially if you have a lot of them."
 -- Nacin</blockquote>
+
 Above all else, choose something that is meaningful to you and semantic in some way. Random ordering is chaos, not poetry. In WordPress Core, our choice is logical or grouped ordering, wherein properties are grouped by meaning and ordered specifically within those groups. The properties within groups are also strategically ordered to create transitions between sections, such as background directly before color. The baseline for ordering is:
-<ul>
- 	<li>Display</li>
- 	<li>Positioning</li>
- 	<li>Box model</li>
- 	<li>Colors and Typography</li>
- 	<li>Other</li>
-</ul>
+
+- Display
+- Positioning
+- Box model
+- Colors and Typography
+- Other
+
 Things that are not yet used in core itself, such as CSS3 animations, may not have a prescribed place above but likely would fit into one of the above in a logical manner. Just as CSS is evolving, so our standards will evolve with it.
 
 Top/Right/Bottom/Left (TRBL/trouble) should be the order for any relevant properties (e.g. margin), much as the order goes in values. Corner specifiers (e.g. border-radius-*-*) should be top-left, top-right, bottom-right, bottom-left. This is derived from how shorthand values would be ordered.
@@ -169,18 +170,18 @@ We use <a href="https://github.com/postcss/autoprefixer">Autoprefixer</a> as a p
 ## Values
 
 There are numerous ways to input values for properties. Follow the guidelines below to help us retain a high degree of consistency.
-<ul>
- 	<li>Space before the value, after the colon.</li>
- 	<li>Do not pad parentheses with spaces.</li>
- 	<li>Always end in a semicolon.</li>
- 	<li>Use double quotes rather than single quotes, and only when needed, such as when a font name has a space or for the values of the <code>content</code> property.</li>
- 	<li>Font weights should be defined using numeric values (e.g. <code>400</code> instead of <code>normal</code>, <code>700</code> rather than <code>bold</code>).</li>
- 	<li>0 values should not have units unless necessary, such as with transition-duration.</li>
- 	<li>Line height should also be unit-less, unless necessary to be defined as a specific pixel value. This is more than just a style convention, but is worth mentioning here. More information: <a href="http://meyerweb.com/eric/thoughts/2006/02/08/unitless-line-heights/">http://meyerweb.com/eric/thoughts/2006/02/08/unitless-line-heights/</a></li>
- 	<li>Use a leading zero for decimal values, including in rgba().</li>
- 	<li>Multiple comma-separated values for one property should be separated by either a space or a newline. For better readability newlines should be used for lengthier multi-part values such as those for shorthand properties like box-shadow and text-shadow, including before the first value. Values should then be indented one level in from the property.</li>
- 	<li>Lists of values within a value, like within rgba(), should be separated by a space.</li>
-</ul>
+
+- Space before the value, after the colon.
+- Do not pad parentheses with spaces.
+- Always end in a semicolon.
+- Use double quotes rather than single quotes, and only when needed, such as when a font name has a space or for the values of the <code>content</code> property.
+- Font weights should be defined using numeric values (e.g. <code>400</code> instead of <code>normal</code>, <code>700</code> rather than <code>bold</code>).
+- 0 values should not have units unless necessary, such as with transition-duration.
+- Line height should also be unit-less, unless necessary to be defined as a specific pixel value. This is more than just a style convention, but is worth mentioning here. More information: <a href="http://meyerweb.com/eric/thoughts/2006/02/08/unitless-line-heights/">http://meyerweb.com/eric/thoughts/2006/02/08/unitless-line-heights/</a>
+- Use a leading zero for decimal values, including in rgba().
+- Multiple comma-separated values for one property should be separated by either a space or a newline. For better readability newlines should be used for lengthier multi-part values such as those for shorthand properties like box-shadow and text-shadow, including before the first value. Values should then be indented one level in from the property.
+- Lists of values within a value, like within rgba(), should be separated by a space.
+
 Correct:
 
 ```css
@@ -236,14 +237,11 @@ Incorrect:
 ## Media Queries
 
 Media queries allow us to gracefully degrade the DOM for different screen sizes. If you are adding any, be sure to test above and below the break-point you are targeting.
-<ul>
- 	<li>It is generally advisable to keep media queries grouped by media at the bottom of the stylesheet.
-<ul>
- 	<li>An exception is made for the wp-admin.css file in core, as it is very large and each section essentially represents a stylesheet of its own. Media queries are therefore added at the bottom of sections as applicable.</li>
-</ul>
-</li>
- 	<li>Rule sets for media queries should be indented one level in.</li>
-</ul>
+
+- It is generally advisable to keep media queries grouped by media at the bottom of the stylesheet.
+    - An exception is made for the wp-admin.css file in core, as it is very large and each section essentially represents a stylesheet of its own. Media queries are therefore added at the bottom of sections as applicable.
+- Rule sets for media queries should be indented one level in.
+
 Example:
 
 ```css
@@ -254,11 +252,10 @@ Example:
 
 ## Commenting
 
-<ul>
- 	<li>Comment, and comment liberally. If there are concerns about file size, utilize minified files and the SCRIPT_DEBUG constant. Long comments should manually break the line length at 80 characters.</li>
- 	<li>A table of contents should be utilized for longer stylesheets, especially those that are highly sectioned. Using an index number (1.0, 1.1, 2.0, etc.) aids in searching and jumping to a location.</li>
- 	<li>Comments should be formatted much as PHPDoc is. The <a href="http://web.archive.org/web/20070601200419/http://cssdoc.net/">CSSDoc</a> standard is not necessarily widely accepted or used but some aspects of it may be adopted over time. Section/subsection headers should have newlines before and after. Inline comments should not have empty newlines separating the comment from the item to which it relates.</li>
-</ul>
+- Comment, and comment liberally. If there are concerns about file size, utilize minified files and the SCRIPT_DEBUG constant. Long comments should manually break the line length at 80 characters.
+- A table of contents should be utilized for longer stylesheets, especially those that are highly sectioned. Using an index number (1.0, 1.1, 2.0, etc.) aids in searching and jumping to a location.
+- Comments should be formatted much as PHPDoc is. The <a href="http://web.archive.org/web/20070601200419/http://cssdoc.net/">CSSDoc</a> standard is not necessarily widely accepted or used but some aspects of it may be adopted over time. Section/subsection headers should have newlines before and after. Inline comments should not have empty newlines separating the comment from the item to which it relates.
+
 For sections and subsections:
 
 ```css
@@ -286,20 +283,18 @@ For inline:
 ## Best Practices
 
 Stylesheets tend to grow in length and complexity, and as they grow the chance of redundancy increases. By following some best practices we can help our CSS maintain focus and flexibility as it evolves:
-<ul>
- 	<li>If you are attempting to fix an issue, attempt to remove code before adding more.</li>
- 	<li>Magic Numbers are unlucky. These are numbers that are used as quick fixes on a one-off basis. Example: <code>.box { margin-top: 37px }</code>.</li>
- 	<li>DOM will change over time, target the element you want to use as opposed to "finding it" through its parents. Example: Use <code>.highlight</code> on the element as opposed to <code>.highlight a</code> (where the selector is on the parent)</li>
- 	<li>Know when to use the height property. It should be used when you are including outside elements (such as images). Otherwise use line-height for more flexibility.</li>
- 	<li>Do not restate default property &amp; value combinations (for instance <code>display: block;</code> on block-level elements).</li>
-</ul>
+
+- If you are attempting to fix an issue, attempt to remove code before adding more.
+- Magic Numbers are unlucky. These are numbers that are used as quick fixes on a one-off basis. Example: <code>.box { margin-top: 37px }</code>.
+- DOM will change over time, target the element you want to use as opposed to "finding it" through its parents. Example: Use <code>.highlight</code> on the element as opposed to <code>.highlight a</code> (where the selector is on the parent)
+- Know when to use the height property. It should be used when you are including outside elements (such as images). Otherwise use line-height for more flexibility.
+- Do not restate default property &amp; value combinations (for instance <code>display: block;</code> on block-level elements).
+
 
 ### WP Admin CSS
 
 Check out the <a href="https://wordpress.github.io/css-audit/public/wp-admin">WP Admin CSS Audit</a>, a report generated to document the health of the WP Admin CSS code. Read more in <a href="https://github.com/WordPress/css-audit/blob/trunk/README.md">the repository's README</a>.
 
 ## Related Links
 
-<ul>
- 	<li>Principles of writing consistent, idiomatic CSS: <a href="https://github.com/necolas/idiomatic-css">https://github.com/necolas/idiomatic-css</a></li>
-</ul>
+- Principles of writing consistent, idiomatic CSS: <a href="https://github.com/necolas/idiomatic-css">https://github.com/necolas/idiomatic-css</a>