Update name

This commit is contained in:
Fabian Affolter 2017-07-18 17:51:51 +02:00
parent bb6bab823f
commit a959d384b7
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336

View File

@ -11,17 +11,17 @@ ha_release: 0.38
---
If you would like to use your own [State card](/developers/frontend_add_card/) without merging your code into [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer/) you can create your own implementation.
- Put the element source file and its dependencies in `www/custom_ui/` directory under your homeassistant config directory.
Put the element source file and its dependencies in `www/custom_ui/` directory under your Home Assistant [configuration](/docs/configuration/) directory.
For example if creating a state card for the `light` domain named `my_custom_light_card` put `state-card-my_custom_light_card.html` in `www/custom_ui/`.
That file should implement `<state-card-my_custom_light_card>` tag with Polymer.
In `state-card-my_custom_light_card.html` you should use `<link rel="import">` to import all the dependencies **not** used by Homeassistant UI.
Do not import any dependencies used by Homeassistant UI.
In `state-card-my_custom_light_card.html` you should use `<link rel="import">` to import all the dependencies **not** used by Home Assistant's UI.
Do not import any dependencies used by the Home Assistant UI.
Importing those will work in `development: 1` mode, but will fail in production mode.
- In the `customize:` section of `configuration.yaml` put `custom_ui_state_card: <element-name>`.
In the `customize:` section of the `configuration.yaml` file put `custom_ui_state_card: <element-name>`.
For example:
```yaml
@ -31,5 +31,4 @@ homeassistant:
custom_ui_state_card: my_custom_light_card
```
For more possibilities, see the [Custom UI section](/cookbook/#user-interface) on our Examples page.