Move content from CONTRIBUTING.md and split existing content

source/_includes/asides/developers_navigation.html

@@ -9,7 +9,16 @@
         <ul>
           <li>{% active_link /developers/architecture/ Architecture %}</li>
           <li>{% active_link /developers/architecture_components/ Components %}</li>
-          <li>{% active_link /developers/development_environment/ Setup Dev Environment %}</li>
+        </ul>
+      </li>
+      <li>
+        {% active_link /developers/development/ Starting with Development %}
+        <ul>
+          <li>{% active_link /developers/development_environment/ Setting up Environment %}</li>
+          <li>{% active_link /developers/development_submitting/ Submit your Work %}</li>
+          <li>{% active_link /developers/development_checklist/ Checklist %}</li>
+          <li>{% active_link /developers/development_testing/ Testing %}</li>
+          <li>{% active_link /developers/development_catching_up/ Catching up with Reality %}</li>
         </ul>
       </li>
       <li>
@@ -26,6 +35,8 @@
           <li>{% active_link /developers/component_deps_and_reqs/ Requirements & Dependencies %}</li>
           <li>{% active_link /developers/component_initialization/ Initialization %}</li>
           <li>{% active_link /developers/component_events/ Handling events %}</li>
+          <li>{% active_link /developers/component_states/ States %}</li>
+          <li>{% active_link /developers/component_visibility/ Visibility %}</li>
           <li>{% active_link /developers/component_generic_discovery/ Loading Platforms %}</li>
           <li>{% active_link /developers/component_discovery/ Component Discovery %}</li>
         </ul>

source/developers/development.markdown

@@ -0,0 +1,19 @@
+---
+layout: page
+title: "Starting with Development"
+description: "Everything to get you started developing for Home Assistant."
+date: 2014-12-21 13:32
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+Home Assistant is built from the ground up to be easily-extensible by other developers using components. It uses [Python 3](https://www.python.org/) for the backend and [Polymer (Web components)](https://www.polymer-project.org/) for the frontend.
+
+Home Assistant is open-source and MIT licensed. The source can be found here:
+
+ - [home-assistant](https://github.com/home-assistant/home-assistant) - Python server backend
+ - [home-assistant-js](https://github.com/home-assistant/home-assistant-js) - JavaScript backend powering the client
+ - [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer) - Polymer UI
+

source/developers/development_catching_up.markdown

@@ -0,0 +1,35 @@
+---
+layout: page
+title: "Catching up with Reality"
+description: "Update your fork with the latest commit."
+date: 2016-07-01 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+If you're taking a while developing your feature and would like to catch up with what's in the current Home Assistant `dev` branch, you can use `git rebase` to do so. This will pull the latest Home Assistant changes locally, rewind your commits, bring in the latest changes from Home Assistant and then replay all of your commits on top.
+
+```bash
+# Run this from your feature branch
+$ git fetch upstream dev  # to pull the latest changes into a local dev branch
+$ git rebase upstream/dev # to put those changes into your feature branch before your changes
+```
+
+If rebase detects conflicts, you can repeat the following process until all changes have been resolved:
+
+1. `git status` will show you the file with the conflict.
+2. Edit the file and resolving the lines between `<<<< | >>>>`
+3. Add the modified file `git add <file>` or `git add .`
+4. Continue rebase `git rebase --continue`
+5. Repeat until you've resolved all conflicts.
+
+There is other workflows that is covered in detail in the [Github documentation](https://help.github.com/articles/fork-a-repo/). Add an additional `remote` after you clone your fork.
+
+```bash
+$ git remote add upstream https://github.com/home-assistant/home-assistant.git
+```
+
+and then simply `git pull --rebase upstream dev`.
+

source/developers/development_checklist.markdown

@@ -0,0 +1,19 @@
+---
+layout: page
+title: "Checklist"
+description: "Overview of the requirements for an improvment for Home Assistant."
+date: 2016-07-01 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+
+After you finish your work:
+
+ - Check that all dependencies are included via the `REQUIREMENTS` variable in your platform/component and only imported inside functions that use them.
+ - Add any new dependencies to `requirements_all.txt` if needed. Use `script/gen_requirements_all.py`.
+ - Update the `.coveragerc` file to exclude your platform if there are no tests available or your new code uses a 3rd party library for communication with the device/service/sensor.
+ - Provide some documentation for [home-assistant.io](https://home-assistant.io/). It's OK to just add a docstring with configuration details (sample entry for `configuration.yaml` file and alike) to the file header as a start. Visit the [website documentation](/developers/website/) for further information on contributing to [home-assistant.io](https://github.com/home-assistant/home-assistant.io).
+

source/developers/development_environment.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
-title: "Setup Development"
+title: "Setup Development Environment"
-description: "Everything to get you started developing for Home Assistant."
+description: "Setup your environment to start developing for Home Assistant."
 date: 2014-12-21 13:32
 sidebar: true
 comments: false
@@ -9,16 +9,6 @@ sharing: true
 footer: true
 ---
 
-Home Assistant is built from the ground up to be easily-extensible by other developers using components. It uses [Python 3](https://www.python.org/) for the backend and [Polymer (Web components)](https://www.polymer-project.org/) for the frontend.
-
-Home Assistant is open-source and MIT licensed. The source can be found here:
-
- - [home-assistant](https://github.com/home-assistant/home-assistant) - Python server backend
- - [home-assistant-js](https://github.com/home-assistant/home-assistant-js) - JavaScript backend powering the client
- - [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer) - Polymer UI
-
-### {% linkable_title Starting development %}
-
 You will need to set up a development environment if you want to start developing a new feature or component for Home Assistant. Please follow these steps to get setup.
 Visit the [the Home Assistant repository](https://github.com/home-assistant/home-assistant) first and click fork in the top right.
 
@@ -34,66 +24,3 @@ On Windows you can use `python setup.py develop` instead of the setup script.
 
 After following these steps, running `hass` will invoke your local installation.
 
-### {% linkable_title Testing your work %}
-
-Testing your work requires `tox` to be installed:
-
-```bash
-$ pip3 install tox
-```
-
-### {% linkable_title Prevent Linter Errors %}
-
-Home Assistant enforces strict [PEP8 style](https://www.python.org/dev/peps/pep-0008/) compliance on all code submitted. You can save yourself the hassle of extra commits just to fix style errors by enabling the flake8 git commit hook. It will check your code when you attempt to commit to the repo. It will block the commit if there are any style issues, giving you a chance to fix it.
-
-```bash
-$ pip install flake8 flake8-docstrings
-$ flake8 --install-hook
-```
-
-The flake8-docstrings extension will check docstrings according to [PEP257](https://www.python.org/dev/peps/pep-0257/) when running flake8.
-
-### {% linkable_title Submitting improvements %}
-
-Improvements to Home Assistant should be submitted one feature at a time using GitHub [pull requests](https://help.github.com/articles/using-pull-requests).
-
- 1. From your fork, create a new branch to hold your changes
-    `git checkout -b some-feature`
- 2. Make the changes you want
- 3. Test your changes and check for style violations
-    `tox`
- 4. Commit the changes
-    `git add .`
-    `git commit -m "Added some-feature"`
- 5. Push your committed changes back to your fork on GitHub
-    `git push origin HEAD`
- 6. Follow [these steps](https://help.github.com/articles/creating-a-pull-request/) to create your pull request.
-
-### {% linkable_title Catching up with Reality %}
-
-If you're taking a while developing your feature request and would like to catch up with what's in the current Home Assistant dev branch, you can use git rebase to do so. This will pull the latest Home Assistant changes locally, rewind your commits, bring in the latest changes from Home Assistant and then replay all of your commits on top.
-
-```bash
-# Run this from your feature branch
-$ git fetch upstream dev  # to pull the latest changes into a local dev branch
-$ git rebase upstream/dev # to put those changes into your feature branch before your changes
-```
-
-If rebase detects conflicts, you can repeat the following process until all changes have been resolved:
-
-1. `git status` will show you the file with the conflict.
-2. Edit the file and resolving the lines between `<<<< | >>>>`
-3. Add the modified file `git add <file>` or `git add .`
-4. Continue rebase `git rebase --continue`
-5. Repeat until you've resolved all conflicts.
-
-### {% linkable_title Further reading %}
-
-- [Home Assistant Architecture](/developers/architecture/)
-- [Frontend development](/developers/frontend/)
-- [Creating a custom component](/developers/creating_components/)
-- [Adding support for a new platform](/developers/add_new_platform/)
-- [Rest API](/developers/api/)
-- [Server-sent events](/developers/server_sent_events/)
-- [Website](/developers/website/)
-- [Home Assitant on Github - CONTRIBUTING.md](https://github.com/home-assistant/home-assistant/blob/dev/CONTRIBUTING.md)

source/developers/development_submitting.markdown

@@ -0,0 +1,26 @@
+---
+layout: page
+title: "Submit your work"
+description: "Submit your work as Pull Request for Home Assistant."
+date: 2016-07-01 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+Improvements, fixes, and new features to Home Assistant should be submitted one feature at a time using GitHub [Pull Requests](https://help.github.com/articles/using-pull-requests).
+
+ 1. From your fork, create a new branch to hold your changes
+    `git checkout -b some-feature`
+ 2. Make the changes you want, create a [new platform](/developers/add_new_platform/), develop a [new component](/developers/creating_components/), or fix [issues](https://github.com/home-assistant/home-assistant/issues).
+ 3. [Test your changes](/developers/development_testing/) and check for style violations
+ 4. Commit the changes if all [musts](/developers/development_checklist/) are covered.
+    `git add .`
+    `git commit -m "Added some-feature"`
+ 5. Consider to add tests to ensure that the code works.
+ 6. Push your committed changes back to your fork on GitHub
+    `git push origin HEAD`
+ 7. Follow [these steps](https://help.github.com/articles/creating-a-pull-request/) to create your pull request.
+ 8. Check for comments and suggestions on your Pull Request and keep an eye on the [CI output](https://travis-ci.org/home-assistant/home-assistant/).
+

source/developers/development_testing.markdown

@@ -0,0 +1,48 @@
+---
+layout: page
+title: "Testing your code"
+description: "Make sure that your code passes the checks"
+date: 2016-07-01 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+Home Assistant enforces strict [PEP8 style](https://www.python.org/dev/peps/pep-0008/) compliance on all code submitted. Every Pull Request is automatically tested with [Coveralls](https://coveralls.io/github/home-assistant/home-assistant) and [Travis CI](https://travis-ci.org/home-assistant/home-assistant) after it is created.
+
+### {% linkable_title Local testing %}
+
+It's highly recommanded to run `tox` before you create your Pull Request to avoid annoying fixes. Local testing requires `tox` to be installed.
+
+```bash
+$ pip3 install tox
+```
+
+Start the test of your code with `tox`.
+
+```bash
+$ tox
+```
+
+This will run unit tests against python 3.4 and 3.5 (if both are available locally), as well as run a set of tests which validate `pep8` and `pylint` style of the code.
+
+You can optionally run tests on only one tox target using the `-e` option to select an environment.
+
+For instance `tox -e lint` will run the linters only, `tox -e py34` will run unit tests only on python 3.4.
+
+### {% linkable_title Prevent Linter Errors %}
+ 
+You can save yourself the hassle of extra commits just to fix style errors by enabling the flake8 git commit hook. It will check your code when you attempt to commit to the repository. It will block the commit if there are any style issues, giving you a chance to fix it.
+
+```bash
+$ pip3 install flake8 flake8-docstrings
+$ flake8 --install-hook
+```
+
+The flake8-docstrings extension will check docstrings according to [PEP257](https://www.python.org/dev/peps/pep-0257/) when running flake8.
+
+### {% linkable_title Notes on PyLint and PEP8 validation %}
+
+In case a PyLint warning cannot be avoided, add a comment to disable the PyLint check for that line. This can be done using the format `# pylint: disable=YOUR-ERROR-NAME`. Example of an unavoidable PyLint warning is if you do not use the passed in datetime if you're listening for time change.
+