Update generated readme from #18.

Author: T4rk1n

{{cookiecutter.project_shortname}}/README.md

@@ -38,6 +38,14 @@ If you have selected install_dependencies during the prompt, you can skip this p
         ```
         $ python usage.py
         ```
+- Write tests for your component.
+    - A sample test is available in `tests/test_usage.py`, it will load `usage.py` and you can then automate interactions with selenium.
+    - Run the tests with `$ pytest tests`.
+    - The Dash team uses these types of integration tests extensively. Browse the Dash component code on GitHub for more examples of testing (e.g. https://github.com/plotly/dash-core-components)
+- Add custom styles to your component by putting your custom CSS files into your distribution folder (`{{cookiecutter.project_shortname}}`).
+    - Make sure that they are referenced in `MANIFEST.in` so that they get properly included when you're ready to publish your component.
+    - Make sure the stylesheets are added to the `_css_dist` dict in `{{cookiecutter.project_shortname}}/__init__.py` so dash will serve them automatically when the component suite is requested.
+- [Review your code](./review_checklist.md)
 
 ### Create a production build and publish:
 
@@ -69,20 +77,10 @@ If you have selected install_dependencies during the prompt, you can skip this p
         ```
         $ npm publish
         ```
+        _Publishing your component to NPM will make the JavaScript bundles available on the unpkg CDN. By default, Dash servers the component library's CSS and JS from the remote unpkg CDN, so if you haven't published the component package to NPM you'll need to set the `serve_locally` flags to `True` (unless you choose `False` on `publish_on_npm`). We will eventually make `serve_locally=True` the default, [follow our progress in this issue](https://github.com/plotly/dash/issues/284)._
 5. Share your component with the community! https://community.plot.ly/c/dash
 
-## More details
-- Include CSS files in your distribution folder (`{{cookiecutter.project_shortname}}`) and reference them in `MANIFEST.in`
-- The `tests` folder contains a sample integration test. This will run a sample Dash app in a browser. Run this with:
-    ```
-    $ pytest tests
-    ```
-    The Dash team uses these types of integration tests extensively. Browse the Dash component code on GitHub for more examples of testing (e.g. https://github.com/plotly/dash-core-components)
-- Publishing your component to NPM will make the JavaScript bundles available on the unpkg CDN. By default, Dash servers the component library's CSS and JS from the remote unpkg CDN, so if you haven't published the component package to NPM you'll need to set the `serve_locally` flags to `True` (unless you choose `False` on `publish_on_npm`). We will eventually make `serve_locally=True` the default, [follow our progress in this issue](https://github.com/plotly/dash/issues/284).
-- Watch the [component boilerplate repository](https://github.com/plotly/dash-component-boilerplate) to stay informed of changes to our components.
-
-
 ## More Resources
 - Learn more about Dash: https://dash.plot.ly
-- View the original component boilerplate: https://github.com/plotly/dash-component-boilerplate
+- Watch the [component boilerplate repository](https://github.com/plotly/dash-component-boilerplate) to stay informed of changes to our components.
 - [React guide for python developers](https://dash.plot.ly/react-for-python-developers)

{{cookiecutter.project_shortname}}/review_checklist.md

@@ -0,0 +1,46 @@
+# Code Review Checklist
+
+## Code quality & design
+
+-   Is your code clear? If you had to go back to it in a month, would you be happy to? If someone else had to contribute to it, would they be able to?
+
+    A few suggestions:
+
+    -   Make your variable names descriptive and use the same naming conventions throughout the code.
+
+    -   For more complex pieces of logic, consider putting a comment, and maybe an example.
+
+    -   In the comments, focus on describing _why_ the code does what it does, rather than describing _what_ it does. The reader can most likely read the code, but not necessarily understand why it was necessary.
+
+    -   Don't overdo it in the comments. The code should be clear enough to speak for itself. Stale comments that no longer reflect the intent of the code can hurt code comprehension.
+
+*   Don't repeat yourself. Any time you see that the same piece of logic can be applied in multiple places, factor it out into a function, or variable, and reuse that code.
+*   Scan your code for expensive operations (large computations, DOM queries, React re-renders). Have you done your possible to limit their impact? If not, it is going to slow your app down.
+
+## Component API
+
+-   Have you tested your component on the Python side by creating an app in `usage.py` ?
+
+    Do all of your component's props work when set from the back-end?
+
+    Should all of them be settable from the back-end or are some only relevant to user interactions in the front-end?
+
+-   Have you provided some basic documentation about your component? The Dash community uses [react docstrings](https://github.com/plotly/dash-docs/blob/master/tutorial/plugins.py#L45) to provide basic information about dash components. Take a look at this [Checklist component example](https://github.com/plotly/dash-core-components/blob/master/src/components/Checklist.react.js) and others from the dash-core-components repository.
+
+    At a minimum, you should describe what your component does, and describe its props and the features they enable.
+
+    Be careful to use the correct formatting for your docstrings for them to be properly recognized.
+
+## Tests
+
+-   The Dash team uses integration tests extensively, and we highly encourage you to write tests for the main functionality of your component. In the `tests` folder of the boilerplate, you can see a sample integration test. By launching it, you will run a sample Dash app in a browser. You can run the test with:
+    ```
+    python -m tests.test_render
+    ```
+    [Browse the Dash component code on GitHub for more examples of testing.](https://github.com/plotly/dash-core-components)
+
+## Ready to publish? Final scan
+
+-   Take a last look at the external resources that your component is using. Are all the external resources used [referenced in `MANIFEST.in`](https://github.com/plotly/dash-docs/blob/0b2fd8f892db720a7f3dc1c404b4cff464b5f8d4/tutorial/plugins.py#L55)?
+
+-   You're ready to publish! Continue to [step #9 here](README.md#publishing).