Updated documentation

CONTRIBUTING.md

@@ -13,15 +13,17 @@ Contains the code to interact with WeMo switches. Called if type=wemo in switch
 **homeassistant/components/switch/tellstick.py**
 Contains the code to interact with Tellstick switches. Called if type=tellstick in switch config.
 
-If a component exists, your job is easy. Have a look at how the component works with other platforms and create a similar file for the platform that you would like to add.If you cannot find a suitable component, you'll have to add it yourself. When writing a component try to structure it after the Switch component to maximize reusability.
+If a component exists, your job is easy. Have a look at how the component works with other platforms and create a similar file for the platform that you would like to add. If you cannot find a suitable component, you'll have to add it yourself. When writing a component try to structure it after the Switch component to maximize reusability.
 
 Communication between Home Assistant and devices should happen via third-party libraries that implement the device API. This will make sure the platform support code stays as small as possible.
 
+For help on building your component, please see the See the documentation on [further customizing Home Assistant](https://github.com/balloob/home-assistant#further-customizing-home-assistant).
+
 After you finish adding support for your device:
 
  - update the supported devices in README.md.
  - add any new dependencies to requirements.txt.
- - Make sure all your code passes Pylint and PEP8 validation. To generate reports, run `pylint homeassistant > pylint.txt` and `pep8 homeassistant --exclude bower_components,external > pep8.txt`.
+ - Make sure all your code passes Pylint, flake8 (PEP8 and some more) validation. To generate reports, run `pylint homeassistant > pylint.txt` and `flake8 homeassistant --exclude bower_components,external > flake8.txt`.
 
 If you've added a component:
 

README.md

@@ -27,9 +27,11 @@ Home Assistant also includes functionality for controlling HTPCs:
 
 The system is built modular so support for other devices or actions can be implemented easily. See also the [section on architecture](#architecture) and the [section on customizing](#customizing).
 
+If you run into issues while using Home Assistant or during development of a component, reach out to the [Home Assistant developer community](https://groups.google.com/forum/#!forum/home-assistant-dev).
+
 ## Installation instructions / Quick-start guide
 
-Running Home Assistant requires that python3 and the packages pyephem and requests are installed.
+Running Home Assistant requires that python3 and the package requests are installed.
 
 Run the following code to get up and running with the minimum setup:
 
@@ -51,6 +53,8 @@ docker run -d --name="home-assistant" -v /path/to/homeassistant/config:/config -
 
 After you got the demo mode running it is time to enable some real components and get started. An example configuration file has been provided in [/config/home-assistant.conf.example](https://github.com/balloob/home-assistant/blob/master/config/home-assistant.conf.example).
 
+*Note:* you can append `?api_password=YOUR_PASSWORD` to the url of the web interface to log in automatically.
+
 ### Philips Hue
 To get Philips Hue working you will have to connect Home Assistant to the Hue bridge.
 
@@ -88,21 +92,17 @@ Once tracking the `device_tracker` component will maintain a file in your config
 <a name='customizing'></a>
 ## Further customizing Home Assistant
 
-If you run into issues while developing your component, reach out to the [Home Assistant developer community](https://groups.google.com/forum/#!forum/home-assistant-dev).
-
 Home Assistant can be extended by components. Components can listen for- or trigger events and offer services. Components are written in Python and can do all the goodness that Python has to offer.
 
 Home Assistant offers [built-in components](#components) but it is easy to built your own. An example component can be found in [`/config/custom_components/example.py`](https://github.com/balloob/home-assistant/blob/master/config/custom_components/example.py).
 
-*Note:* Home Assistant will use the directory that contains your config file as the directory that holds your customizations. By default this is the `./config` folder but this can be placed anywhere on the filesystem.
+*Note:* Home Assistant will use the directory that contains your config file as the directory that holds your customizations. By default this is the `./config` folder but this can be pointed anywhere on the filesystem by using the `--config /YOUR/CONFIG/PATH/` argument.
 
 A component will be loaded on start if a section (ie. `[light]`) for it exists in the config file or a module that depends on the component is loaded. When loading a component Home Assistant will check the following paths:
 
  * &lt;config file directory>/custom_components/&lt;component name>.py
  * homeassistant/components/&lt;component name>.py (built-in components)
 
-Upon loading of a component it will be validated to see if the required fields (`DOMAIN`, `DEPENDENCIES`) and required method ( `setup(hass, config)` ) are available.
-
 Once loaded, a component will only be setup if all dependencies can be loaded and are able to setup. Keep an eye on the logs to see if loading and setup of your component went well.
 
 *Warning:* You can override a built-in component by offering a component with the same name in your custom_components folder. This is not recommended and may lead to unexpected behavior!
@@ -133,6 +133,8 @@ host=paulusschoutsen.nl
 
 Then in the setup-method of your component you will be able to refer to `config[example][host]` to get the value `paulusschoutsen.nl`.
 
+If you want to get your component included with the Home Assistant distribution, please take a look at the [contributing page](https://github.com/balloob/home-assistant/blob/master/CONTRIBUTING.md).
+
 <a name="architecture"></a>
 ## Architecture