This commit is contained in:
Paulus Schoutsen 2018-06-20 16:05:11 -04:00
parent 62ef1442f1
commit cfe5279ced
2 changed files with 1 additions and 2 deletions

View File

@ -74,7 +74,6 @@ To use a custom card, set the card type in `ui-lovelace.yaml` to `custom:<YOUR C
```yaml
# ui-lovelace.yaml example
title: Example Main title
views:
- name: Example
cards:

View File

@ -11,7 +11,7 @@ The Lovelace UI is:
- **Extremely fast**. We create the user interface when the UI configuration changes. When a state changes, we just make the UI represent the current state.
- **Extremely customizable**. We have a new file for just configuration. In the past, we declined UI specific options because they did not fit in the state machine. They will fit in a configuration file for a user interface.
- **Extremely extensible**. It's based on the web standard [custom elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements). Don't like the built-in cards? Make your own! Custom cards are treated the same as built-in cards and care configured the same way.
- **Extremely extensible**. It's based on the web standard [custom elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements). Don't like the built-in cards? Make your own! Custom cards are treated the same as built-in cards and are configured the same way. [Check the docs.](lovelace_custom_card.md)
- **Making the backend faster**. With Lovelace, the backend will no longer need to maintain entities like groups for the sole purpose of showing them on the frontend.
## How it works