docs: emphasize some points on what makes a good audit

docs/new-audits.md

@@ -3,19 +3,44 @@ document is to help you understand what constitutes as a "good" audit for Lighth
 to propose a new audit. 
 
 ## New audit principles
-Lighthouse audits that surface in the report should be: 
-- Applicable to a significant portion of web developers (based on scale and severity of impact) 
-- Contribute significantly towards making the mobile web experience better for end users. 
-- Not have a significant impact on our runtime performance or bundle size. 
-- Something that is new, and not something that is already measured by existing audits. 
-- Important for our strategic goals as a product.
-- Measurable (especially for performance audits) or have clear pass/fail states. 
-- Not use 3rd party APIs for completing the audit check. 
 
+Lighthouse audits that surface in the report should:
+- be applicable to a significant portion of web developers (based on scale and severity of impact) 
+- contribute significantly towards making the mobile web experience better for end users. 
+- not have a significant impact on our runtime performance or bundle size. 
+- be new, not something that is already measured by existing audits. 
+- be measurable (especially for performance audits) or have clear pass/fail states.
+- be actionable - when failing, specific advice should be given. If the failure can be tied to a specific resource (a DOM element, script, line of code), use the appropriate detail type (see below). If multiple failures can occur for a page, return a table.
+- not use 3rd party APIs for completing the audit check. 
+
+## Actionability
+
+1. Specific advice should be given if the audit fails. If an audit can fail in multiple ways, each way should have  specific guidance that the user should take to resolve the problem.
+1. If the failure can be applied to a specific resource, use the appropriate detail type (see subsection).
+1. If multiple failures can occur on a single page, show each (use a table - don't just return a binary score).
+
+### Detail Types
+
+An audit can return a number of different [detail types](https://github.com/GoogleChrome/lighthouse/blob/master/types/audit-details.d.ts).
+
+| detail type               | resource              | notes                                  |
+|---------------------------|-----------------------|----------------------------------------|
+| `'node'`                  | DOM element           | set path to a devtoolsNodePath         |
+| `'source-location'`       | Code Network Resource | use to point to specific line, column  |
+| `'code'`                  | N/A; freeform         | render as monospace font `like this`   |
+| `'url'`                   | Network Resource      | we will make it a pretty link          |
+| `'thumbnail'`             | Image Resource        | same as above, but we show a thumbnail |
+| `'link'`                  | -                     | arbitrary link / url combination       |
+| `'text'\|'ms'\|'numeric'` | -                     |                                        |
+
+
+<!--- https://docs.google.com/document/d/1KS6PGPYDfE_TWrRdw55Rd67P-g_MU4KdMetT3cTPHjI/edit#heading=h.32w9jjm4c70w -->
+![Detail type examples](../assets/detail-type-examples.png)
 
 ## Process for creating a new audit
-1. Briefly scan the criteria we’ve laid out above. If you think the principles match with your proposed new audit, then proceed! 
-2. Next step is to create an issue on GitHub with answers to the following questions: 
+
+1. Scan the criteria we’ve laid out above. If you think the principles match with your proposed new audit, then proceed! 
+1. Next step is to create an issue on GitHub with answers to the following questions: 
 ```
 #### Provide a basic description of the audit
 #### How would the audit appear in the report? 
@@ -34,4 +59,4 @@ Lighthouse audits that surface in the report should be:
 ```
 3. Once the proposal is submitted, then Lighthouse team will take a look and followup. We will discuss possible implementation approaches, and associated runtime overhead.
 With this new information we can better understand the impl cost and effort required and prioritize the audit into our sprint/roadmap. 
-4. Depending on the prioritization, we'll then work with you to figure out the necessary engineering/UX/product details. 
+1. Depending on the prioritization, we'll then work with you to figure out the necessary engineering/UX/product details. 

docs/plugins.md

@@ -17,7 +17,7 @@
 
 ## Introduction
 
-If you're new to Lighthouse development, start by reading up on the overall [architecture](./architecture.md) and how [configuration](./configuration.md) works before continuing.
+If you're new to Lighthouse development, start by reading up on the overall [architecture](./architecture.md), how [configuration](./configuration.md) works, and what makes a [good audit](./new-audits.md) before continuing.
 
 ### What is a Lighthouse Plugin?
 

readme.md

@@ -232,6 +232,7 @@ Useful documentation, examples, and recipes to get you started.
 - [Using Lighthouse programmatically](./docs/readme.md#using-programmatically)
 - [Testing a site with authentication](./docs/authenticated-pages.md)
 - [Developing Plugins](./docs/plugins.md)
+- [Making a New Audit](./docs/new-audits.md)
 - [Testing on a mobile device](./docs/readme.md#testing-on-a-mobile-device)
 - [Lighthouse Architecture](./docs/architecture.md)