-This map always shows the location of all tracked devices. If you want to hide certain entities, you should look into the [Map Card](/lovelace/map/).
+This map always shows the location of all tracked devices. If you want to hide certain entities, you should look into the [Map Card](/dashboards/map/).
diff --git a/source/_integrations/meteo_france.markdown b/source/_integrations/meteo_france.markdown
index f2d2e518469..73f13d89d38 100644
--- a/source/_integrations/meteo_france.markdown
+++ b/source/_integrations/meteo_france.markdown
@@ -31,7 +31,7 @@ It displays the current weather along with a 5 days forecast and create sensors,
## Weather platform
-To be used with the weather Lovelace card to access current condition, today and next four days forecast.
+To be used with the weather dashboard card to access current condition, today and next four days forecast.
The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
diff --git a/source/_integrations/motioneye.markdown b/source/_integrations/motioneye.markdown
index d6e2fb6219a..267503f7a83 100644
--- a/source/_integrations/motioneye.markdown
+++ b/source/_integrations/motioneye.markdown
@@ -296,9 +296,9 @@ of the "overlapping" cameras are queried. Use different root directories (in mot
`File Storage -> Root Directory`) to ensure motionEye (and thus this integration) will
correctly associate media with the camera from which that media was captured.
-## Example Lovelace Card
+## Example Dashboard Card
-A Lovelace card with icons that will call the `action` service to send action commands to motionEye.
+A dashboard card with icons that will call the `action` service to send action commands to motionEye.
```yaml
- type: picture-glance
diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown
index 1e7de3a872d..9603d92e501 100644
--- a/source/_integrations/nest.markdown
+++ b/source/_integrations/nest.markdown
@@ -303,7 +303,7 @@ Additional Nest Temperature Sensors are not supported by the SDM API.
Home Assistant supports all SDM API features. However, every Camera or Doorbell device has a different set of built-in capabilities. A Camera device has one of the following live stream types:
- **RTSP**: These devices have an HLS stream served by the Home Assistant Core. These cameras support server-side `camera` services like stream recording or image preview. See [Low Latency HLS](/integrations/stream#ll-hls) as a great option to enable to reduce stream latency.
-- **WebRTC**: These devices support direct browser to camera communication and a super low latency stream. A [Picture Glance Card](/lovelace/picture-glance/) can show the live stream in the grid with the *Camera View* set to `live` (not recommended for battery-powered cameras). `camera` services like stream recording are *not supported*.
+- **WebRTC**: These devices support direct browser to camera communication and a super low latency stream. A [Picture Glance Card](/dashboards/picture-glance/) can show the live stream in the grid with the *Camera View* set to `live` (not recommended for battery-powered cameras). `camera` services like stream recording are *not supported*.
diff --git a/source/_integrations/panel_iframe.markdown b/source/_integrations/panel_iframe.markdown
index cfbe1b1f535..99a0e374c01 100644
--- a/source/_integrations/panel_iframe.markdown
+++ b/source/_integrations/panel_iframe.markdown
@@ -66,6 +66,6 @@ panel_iframe:
-Do **not** create one that is named `lovelace` it will overwrite Lovelace causing it to never load.
+Do **not** create one that is named `lovelace` it will overwrite existing Dashboards, causing it to never load.
diff --git a/source/_integrations/seventeentrack.markdown b/source/_integrations/seventeentrack.markdown
index ed6a81379af..3c3094cdb98 100644
--- a/source/_integrations/seventeentrack.markdown
+++ b/source/_integrations/seventeentrack.markdown
@@ -53,7 +53,7 @@ show_delivered:
## Examples
-### Lovelace summary card
+### Dashboard summary card
Use the following templated Markdown card to list all packages in transit along with their status:
diff --git a/source/_integrations/shopping_list.markdown b/source/_integrations/shopping_list.markdown
index 4506103e339..ba8f35524ef 100644
--- a/source/_integrations/shopping_list.markdown
+++ b/source/_integrations/shopping_list.markdown
@@ -12,7 +12,7 @@ ha_domain: shopping_list
The `shopping_list` integration allows you to keep track of shopping list items.
-Your shopping list will be accessible from the sidebar, and you can optionally add the [Shopping List card](/lovelace/shopping-list/) to your Lovelace dashboard. With the [Conversation integration](/integrations/conversation/) you can add items to your shopping list using voice commands like "Add eggs to my shopping list."
+Your shopping list will be accessible from the sidebar, and you can optionally add the [Shopping List card](/dashboards/shopping-list/) to your dashboard. With the [Conversation integration](/integrations/conversation/) you can add items to your shopping list using voice commands like "Add eggs to my shopping list."
{% include integrations/config_flow.md %}
diff --git a/source/_integrations/system_health.markdown b/source/_integrations/system_health.markdown
index d71bd8879b8..e8dbcb79e99 100644
--- a/source/_integrations/system_health.markdown
+++ b/source/_integrations/system_health.markdown
@@ -19,4 +19,4 @@ system_health:
System Health integration data can be viewed at **Configuration** -> **Info**.
-Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of Lovelace [Dashboards](/lovelace/dashboards/) and [Views](/lovelace/views/) you have, and more.
+Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of [Dashboards](/dashboards/dashboards/) and [Views](/dashboards/views/) you have, and more.
diff --git a/source/_integrations/transmission.markdown b/source/_integrations/transmission.markdown
index 21eb1e6bdbe..4759e4c9273 100644
--- a/source/_integrations/transmission.markdown
+++ b/source/_integrations/transmission.markdown
@@ -120,7 +120,7 @@ Stops a torrent.
### Attribute `torrent_info`
-All `*_torrents` sensors e.g. `sensor.transmission_total_torrents` or `sensor.transmission_started_torrents` have a state attribute `torrent_info` that contains information about the torrents that are currently in a corresponding state. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_total_torrents` -> **Attributes**, or by adding a [Markdown card](/lovelace/markdown/) to Lovelace with the following code:
+All `*_torrents` sensors e.g. `sensor.transmission_total_torrents` or `sensor.transmission_started_torrents` have a state attribute `torrent_info` that contains information about the torrents that are currently in a corresponding state. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_total_torrents` -> **Attributes**, or by adding a [Markdown card](/dashboards/markdown/) to a dashboard with the following code:
{% raw %}
diff --git a/source/_integrations/usgs_earthquakes_feed.markdown b/source/_integrations/usgs_earthquakes_feed.markdown
index 3d79c9ab690..76ab2b56130 100644
--- a/source/_integrations/usgs_earthquakes_feed.markdown
+++ b/source/_integrations/usgs_earthquakes_feed.markdown
@@ -122,7 +122,7 @@ geo_location:
```
## Card Example
-Assuming you configure this service using `feed_type: past_week_all_earthquakes`, you can create a corresponding map card in the Lovelace UI with the following card:
+Assuming you configure this service using `feed_type: past_week_all_earthquakes`, you can create a corresponding map card in a dashboard with the following card:
```yaml
type: map
geo_location_sources:
diff --git a/source/_integrations/waze_travel_time.markdown b/source/_integrations/waze_travel_time.markdown
index 2526ee58fd3..e44cb1e4760 100644
--- a/source/_integrations/waze_travel_time.markdown
+++ b/source/_integrations/waze_travel_time.markdown
@@ -104,5 +104,5 @@ In this example we are using the entity ID of a zone as the origin and the frien
## Using the live map in an iFrame
If you plan to use [Waze's live map](https://developers.google.com/waze/iframe/)
-in Lovelace [iframe](/lovelace/iframe/) then use
+in a dashboard [iframe](/dashboards/iframe/) then use
[https://embed.waze.com/iframe](https://embed.waze.com/iframe) and not the live map URL itself.
diff --git a/source/_integrations/xbox.markdown b/source/_integrations/xbox.markdown
index 2c8d1b67da0..abf9be38325 100644
--- a/source/_integrations/xbox.markdown
+++ b/source/_integrations/xbox.markdown
@@ -100,11 +100,11 @@ delay_sec: 0.1
### Picture Elements Card
-Below is a picture elements card that can be added to Lovelace to provide an Xbox controller interface in your frontend. It utilizes the services detailed above. Replace `remote.xboxone_remote` and `media_player.xboxone` with the names of your entities and enjoy! Courtesy of [@SeanPM5](https://github.com/SeanPM5) and [@hunterjm](https://github.com/hunterjm).
+Below is a picture elements card that can be added to a dashboard to provide an Xbox controller interface in your frontend. It utilizes the services detailed above. Replace `remote.xboxone_remote` and `media_player.xboxone` with the names of your entities and enjoy! Courtesy of [@SeanPM5](https://github.com/SeanPM5) and [@hunterjm](https://github.com/hunterjm).
-
- Screenshot showing Xbox Controller in Lovelace.
+
+ Screenshot showing Xbox Controller in a dashboard.
```yaml
diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown
index 482f20d8b4b..e40d97496f1 100644
--- a/source/_integrations/xiaomi_miio.markdown
+++ b/source/_integrations/xiaomi_miio.markdown
@@ -1103,7 +1103,7 @@ remote:
- pronto:pronto_hex:[optional_repeat]
```
-### Add command as entity button in Lovelace UI
+### Add command as entity button to a dashboard
```yaml
type: entity-button
diff --git a/source/_integrations/yandex_transport.markdown b/source/_integrations/yandex_transport.markdown
index 35ec3682a4a..61099251e58 100644
--- a/source/_integrations/yandex_transport.markdown
+++ b/source/_integrations/yandex_transport.markdown
@@ -72,7 +72,7 @@ sensor:
## Options For Entities
-You can configure view information about the next bus using Lovelace card.
+You can configure view information about the next bus using dashboard card.
To enable displaying the relative time in your `default_view` add the following lines:
```yaml
diff --git a/source/_posts/2018-07-06-release-73.markdown b/source/_posts/2018-07-06-release-73.markdown
index e94be71d26d..7f8e8a8e05e 100644
--- a/source/_posts/2018-07-06-release-73.markdown
+++ b/source/_posts/2018-07-06-release-73.markdown
@@ -17,7 +17,7 @@ In the meanwhile, we're also working hard on the new authentication system. A pr
This release also includes a TON of love for the new Lovelace UI. Yes, it's still experimental but daaang, it's already so awesome that you should probably just go ahead and try it out. Thanks to all the devs who have jumped on this: [@c727], [@ciotlosm] and [@jeradM].
-We don't have time to go through all the changes in this release, but [@ciotlosm] has been keeping [a very detailed changelog](/lovelace/changelog/). I'll just leave this screenshot by [@arsaboo] of the new picture-elements card and [the Lovelace configuration](https://github.com/arsaboo/homeassistant-config/blob/master/ui-lovelace.yaml#L15-L158):
+We don't have time to go through all the changes in this release, but [@ciotlosm] has been keeping a very detailed changelog. I'll just leave this screenshot by [@arsaboo] of the new picture-elements card and [the Lovelace configuration](https://github.com/arsaboo/homeassistant-config/blob/master/ui-lovelace.yaml#L15-L158):
diff --git a/source/_posts/2018-07-21-release-74.markdown b/source/_posts/2018-07-21-release-74.markdown
index bc2bd6baeae..6fa4184516e 100644
--- a/source/_posts/2018-07-21-release-74.markdown
+++ b/source/_posts/2018-07-21-release-74.markdown
@@ -32,7 +32,7 @@ To try it out today, [read these instructions](https://developers.home-assistant
We keep seeing [great examples](https://twitter.com/home_assistant/status/1019579208622845953) of UIs built with Lovelace. Follow us on social media ([FB](https://www.facebook.com/homeassistantio/?ref=bookmarks), [Twitter](https://twitter.com/home_assistant)) where we will keep sharing great examples.
-For the Lovelace changes in this release, check out the [changelog](/lovelace/changelog/). To help our development and design teams, we've also introduced a [Lovelace card gallery](https://www.awesome-ha.com/).
+To help our development and design teams, we've also introduced a [Lovelace card gallery](https://www.awesome-ha.com/).
Thanks to [@c727], [@jeradM] and [@ciotlosm] for leading this effort ❤️
diff --git a/source/_posts/2018-10-12-release-80.markdown b/source/_posts/2018-10-12-release-80.markdown
index 4383741f7f2..333b0e7e0de 100644
--- a/source/_posts/2018-10-12-release-80.markdown
+++ b/source/_posts/2018-10-12-release-80.markdown
@@ -15,8 +15,8 @@ October 12, 2018. 12 days into Hacktoberfest and it's been busier than ever on t
Alright, new release, we got some cool stuff! Let's start with our [Lovelace UI](/lovelace). We have integrated into Lovelace UI some of the custom cards that our amazing community have built, making them easily accessible to all users. The cards are [Gauge][ll-gauge] and [Sensor][ll-sensor]:
-[ll-gauge]: /lovelace/gauge/
-[ll-sensor]: /lovelace/sensor/
+[ll-gauge]: /dashboards/gauge/
+[ll-sensor]: /dashboards/sensor/
diff --git a/source/_posts/2018-10-29-release-81.markdown b/source/_posts/2018-10-29-release-81.markdown
index b69e8fc3758..edcf6d16646 100644
--- a/source/_posts/2018-10-29-release-81.markdown
+++ b/source/_posts/2018-10-29-release-81.markdown
@@ -18,7 +18,7 @@ To go with the configuration entry support, MQTT also now also integrates with t
Lovelace has another three new cards, the alarm panel, the button card, and the thermostat card:
-
+
Screenshot of the thermostat card.
diff --git a/source/_posts/2018-12-12-release-84.markdown b/source/_posts/2018-12-12-release-84.markdown
index 96c1938141e..042ad8a851a 100644
--- a/source/_posts/2018-12-12-release-84.markdown
+++ b/source/_posts/2018-12-12-release-84.markdown
@@ -45,9 +45,9 @@ If you are currently testing Lovelace, please read the notes thoroughly as a lot
So if you were using Lovelace before 0.84, you now have two options. Option one is to use the new storage mode and import your existing file. You can do this by opening the Lovelace UI and click on Configure UI, this will prompt you to change to storage mode. This will unlock a new option in the menu called "raw config editor". Open this and paste the content of your `ui-lovelace.yaml` file into it and click save. Note that YAML comments are not persisted and `!include`/`!secret` are not supported if in storage mode.
-If you want to continue managing a YAML file, [check here how to enable the YAML mode](/lovelace/yaml-mode/). The file `ui-lovelace.yaml` will now follow the same options as `configuration.yaml`. This means that the Lovelace YAML config is now parsed with YAML 1.1 instead of YAML 1.2. Major change is that you need to make sure that you wrap `on` and `off` with quotes in your configs!
+If you want to continue managing a YAML file, [check here how to enable the YAML mode](/dashboards/yaml-mode/). The file `ui-lovelace.yaml` will now follow the same options as `configuration.yaml`. This means that the Lovelace YAML config is now parsed with YAML 1.1 instead of YAML 1.2. Major change is that you need to make sure that you wrap `on` and `off` with quotes in your configs!
-We have also aligned the configuration of all the cards, causing breaking changes. Changes are especially focused around how we define actions for short and long presses. See [the docs](/lovelace/changelog/) for more info.
+We have also aligned the configuration of all the cards, causing breaking changes. Changes are especially focused around how we define actions for short and long presses. See [the docs](/dashboards/changelog/) for more info.
Editor UI is now further processed. You can manage your Lovelace UI without leaving your browser! It is possible to add, edit and delete views. It is possible to add, edit, move and delete cards, including custom cards!
diff --git a/source/_posts/2019-01-23-lovelace-released.markdown b/source/_posts/2019-01-23-lovelace-released.markdown
index b5e9618f478..1048534c7aa 100644
--- a/source/_posts/2019-01-23-lovelace-released.markdown
+++ b/source/_posts/2019-01-23-lovelace-released.markdown
@@ -13,7 +13,7 @@ og_image: /images/blog/2019-01-lovelace/demo.png
Today we're happy to announce that our new Lovelace UI, which has been in beta for the last 8 months, is becoming the new default interface of [Home Assistant 0.86](/blog/2019/01/23/release-86/). With Lovelace we're taking a new approach to building user interfaces for Home Assistant. We're no longer storing the look and feel of your UI in your configuration.yaml, requiring restarts for changes. With Lovelace we're keeping the UI concerns in the UI
1, unlocking a whole new set of features:
- - [24 cards](/lovelace/alarm-panel/) to place and configure as you like.
+ - [24 cards](/dashboards/alarm-panel/) to place and configure as you like.
- UI Editor. A configuration UI to manage your Lovelace UI including live preview when editing cards.
- Fast. Using a static config allows us to build up the UI once.
- Customizable.
@@ -30,9 +30,9 @@ In case you're reading this and want to give it a try right now: we've updated [
For a deep dive into all the new features, check out the [latest episode of the Home Assistant podcast](https://hasspodcast.io/ha042/), featuring an interview with [Zack Arnett][@zsarnett] from the Lovelace team.
-For an overview of all the different features, check out the [Lovelace documentation](/lovelace/).
+For an overview of all the different features, check out the [Lovelace documentation](/dashboards/).
-
1: If you prefer to write your Lovelace config in YAML, Lovelace also includes an optional [YAML mode](/lovelace/yaml-mode/).
+
1: If you prefer to write your Dashboard config in YAML, Home Assistant also includes an optional [YAML mode](/dashboards/yaml-mode/).
## Migrating to Lovelace
diff --git a/source/_posts/2019-08-07-release-97.markdown b/source/_posts/2019-08-07-release-97.markdown
index 522c9ded1db..e8a4043da65 100644
--- a/source/_posts/2019-08-07-release-97.markdown
+++ b/source/_posts/2019-08-07-release-97.markdown
@@ -45,7 +45,7 @@ Home Assistant Cast opens a whole new world of possibilities for using Lovelace,
This release contains a couple of notable UI changes:
-- [New Cast row available](/lovelace/entities/#cast) in the Lovelace entities card to start Home Assistant Cast.
+- [New Cast row available](/dashboards/entities/#cast) in the Lovelace entities card to start Home Assistant Cast.
- Improved accessibility for visually impaired users. This is an [ongoing effort](https://github.com/home-assistant/home-assistant-polymer/issues/3267) on making the frontend accessible.
- Split out `configuration.yaml` actions from the core configuration into a new server control config panel. Thanks [@IcyPalm]
- Markdown card now has a size + 1, if it has a header defined. Some layouts might be moved around due to this.
diff --git a/source/_posts/2020-02-05-release-105.markdown b/source/_posts/2020-02-05-release-105.markdown
index 9fc3faf5c09..9e18d1b5fb3 100644
--- a/source/_posts/2020-02-05-release-105.markdown
+++ b/source/_posts/2020-02-05-release-105.markdown
@@ -141,7 +141,7 @@ So if you have a light named "Living room lights" that is in the area "Living ro
- We added many accessibility features to Lovelace; you can navigate almost everything with the tab key.
We will continue to work on this so that people with disabilities can also enjoy Home Assistant.
-For a full list of changes, see the [Lovelace changelog](/lovelace/changelog/).
+For a full list of changes, see the Lovelace changelog.
Even more frontend improvements:
diff --git a/source/_posts/2020-03-18-release-107.markdown b/source/_posts/2020-03-18-release-107.markdown
index 2fd39bdbfff..6d4e29abf94 100644
--- a/source/_posts/2020-03-18-release-107.markdown
+++ b/source/_posts/2020-03-18-release-107.markdown
@@ -69,7 +69,7 @@ admin users only.
An unlimited amount of dashboards can be created right from the UI in the new
Lovelace configuration panel, and YAML dashboards can be set up in
-`configuration.yaml`, see [the documentation](/lovelace/yaml-mode/).
+`configuration.yaml`, see [the documentation](/dashboards/yaml-mode/).
This awesome new feature comes with a deprecation if you use Lovelace in
manual YAML mode: You need to move the `resources` section from
@@ -176,14 +176,14 @@ Experiencing issues introduced by this release? Please report them in our [issue
- **Input Number** - Adds an entity ID to input_number warning. Passing an out of range value to `input_number.set_value` will now raise a validation error. Incrementing/decrementing an `input_number` will no longer cause warnings. - ([@balloob] - [#32012]) ([input_number docs])
-- **History Graph** - The `history_graph` integration has been deprecated in Home Assistant 0.105 and is now removed. This integration was used for the old states UI, which is no longer available. A Lovelace an equivalent is available: [The Lovelace History Graph](/lovelace/history-graph/). ([@frenck] - [#32028])
+- **History Graph** - The `history_graph` integration has been deprecated in Home Assistant 0.105 and is now removed. This integration was used for the old states UI, which is no longer available. A Lovelace an equivalent is available: [The Lovelace History Graph](/dashboards/history-graph/). ([@frenck] - [#32028])
- **Weblink** - The `weblink` integration is was deprecated in 0.105.0 and now removed. This integration only works with the old states UI, which is no longer available. ([@frenck] - [#32024])
With Lovelace, the same can be achieved using:
- - [The Lovelace Markdown card](/lovelace/markdown/)
- - [The Lovelace Entities card](/lovelace/entities/#weblink)
+ - [The Lovelace Markdown card](/dashboards/markdown/)
+ - [The Lovelace Entities card](/dashboards/entities/#weblink)
- **Environment Canada** - This integration was previously using web scraping for weather alert details. The details attribute has been removed to make it compliant. (ADR-0004) - ([@michaeldavie] - [#32077]) ([environment_canada docs])
diff --git a/source/_posts/2020-05-20-release-110.markdown b/source/_posts/2020-05-20-release-110.markdown
index 18d419bebb3..229d8087efb 100644
--- a/source/_posts/2020-05-20-release-110.markdown
+++ b/source/_posts/2020-05-20-release-110.markdown
@@ -148,7 +148,7 @@ You can also set the attribute you want to show as the secondary information.
Screenshot of the updated weather card.
-Check the [documentation](/lovelace/weather-forecast/) for more information.
+Check the [documentation](/dashboards/weather-forecast/) for more information.
## Internal & External URLs
diff --git a/source/_posts/2020-08-05-mobile-apps-new-features.markdown b/source/_posts/2020-08-05-mobile-apps-new-features.markdown
index 06d5001449c..4d21b706fec 100644
--- a/source/_posts/2020-08-05-mobile-apps-new-features.markdown
+++ b/source/_posts/2020-08-05-mobile-apps-new-features.markdown
@@ -93,7 +93,7 @@ We have also been hard at working making improvements in other areas of the app:
* There are now 2 [widgets](https://companion.home-assistant.io/docs/integrations/android-widgets) that you can set up, with Entity State being the latest addition. The Entity State widget will display the state and any attribute of the selected entity. It will update once every 30 minutes or when tapped. The Service Call widget was also enhanced to allow you to select from a list of valid and available services along with the ability to add additional data fields that the service may require.
* In App Configuration the Home Network WiFi SSID option now allows the user to select multiple SSIDs.
-* A Cookie Manager was added to our WebView that will allow you to save cookies from sites that you may use in the [webpage card](/lovelace/iframe/).
+* A Cookie Manager was added to our WebView that will allow you to save cookies from sites that you may use in the [webpage card](/dashboards/iframe/).
* More descriptive SSL error messages were added to help users resolve local issues they may encounter while setting up the app.
* Device ID is now sent with the event data for actionable notifications.
diff --git a/source/_posts/2021-04-09-android-april-2021-release.markdown b/source/_posts/2021-04-09-android-april-2021-release.markdown
index ab17c30f09c..7a111e1fcc4 100644
--- a/source/_posts/2021-04-09-android-april-2021-release.markdown
+++ b/source/_posts/2021-04-09-android-april-2021-release.markdown
@@ -37,7 +37,7 @@ Screenshot of Sensor Search & Filter.
## Shortcuts
-Sometimes when you open the app you may already know exactly where you want to go. You may find yourself on the same view often to see your cameras or give the nursery a quick look to make sure things are ok. You may even want to quickly see the history of an entity like when the door was last opened. In this release, we have introduced [Android Shortcuts](https://developer.android.com/guide/topics/ui/shortcuts) which will let you get to anywhere in the Home Assistant frontend quickly, directly from your home screen. Shortcuts will look like a separate app on the home screen allowing you to make them easily accessible and even place them into a folder for better organization. You can navigate to any Lovelace [view or dashboard](/lovelace/dashboards-and-views/) including other pages like the [Shopping List](/integrations/shopping_list/). You can also navigate to any entity directly to get more information like the history or see the graph.
+Sometimes when you open the app you may already know exactly where you want to go. You may find yourself on the same view often to see your cameras or give the nursery a quick look to make sure things are ok. You may even want to quickly see the history of an entity like when the door was last opened. In this release, we have introduced [Android Shortcuts](https://developer.android.com/guide/topics/ui/shortcuts) which will let you get to anywhere in the Home Assistant frontend quickly, directly from your home screen. Shortcuts will look like a separate app on the home screen allowing you to make them easily accessible and even place them into a folder for better organization. You can navigate to any Lovelace [view or dashboard](/dashboards/dashboards-and-views/) including other pages like the [Shopping List](/integrations/shopping_list/). You can also navigate to any entity directly to get more information like the history or see the graph.
There are a few different shortcut types and in the nature of Home Assistant, we have opted not to add static shortcuts because they are static! We support dynamic shortcuts which will show up under the app long-press menu. Once you create a shortcut, you will be able to drag it onto your home screen. There is also support for pinned shortcuts that can be added automatically to your home screen without needing to drag the icon, given your device and launcher support pinned shortcuts. Check out the [documentation](https://companion.home-assistant.io/docs/integrations/android-shortcuts) for more details including known limitations.
diff --git a/source/_posts/2021-08-04-home-energy-management.markdown b/source/_posts/2021-08-04-home-energy-management.markdown
index 20d7c558f46..d1d3a0ef9a8 100644
--- a/source/_posts/2021-08-04-home-energy-management.markdown
+++ b/source/_posts/2021-08-04-home-energy-management.markdown
@@ -110,9 +110,9 @@ If you're interested in helping out, don't hesitate to stop by the new #devs_ene
### New possibilities for advanced users
-Every home is different and so are the needs of individual users. The energy management feature in Home Assistant is created with existing Home Assistant building blocks: Lovelace & Data storage. This means that our advanced users can choose to build up their own dashboards and use [the pieces from the energy dashboard](/lovelace/energy/) that they like.
+Every home is different and so are the needs of individual users. The energy management feature in Home Assistant is created with existing Home Assistant building blocks: Lovelace & Data storage. This means that our advanced users can choose to build up their own dashboards and use [the pieces from the energy dashboard](/dashboards/energy/) that they like.
-On top of that, advanced users will have access to the new [long-term statistics](/lovelace/statistics-graph/) that have been added to Home Assistant. This data allows you to easily monitor most sensor data over long periods of time, not just energy data.
+On top of that, advanced users will have access to the new [long-term statistics](/dashboards/statistics-graph/) that have been added to Home Assistant. This data allows you to easily monitor most sensor data over long periods of time, not just energy data.
### Thank you community
diff --git a/source/_posts/2021-08-04-release-20218.markdown b/source/_posts/2021-08-04-release-20218.markdown
index 5eb0fc0d35f..e7dfcb3cdc7 100644
--- a/source/_posts/2021-08-04-release-20218.markdown
+++ b/source/_posts/2021-08-04-release-20218.markdown
@@ -121,7 +121,7 @@ Every hour, we calculate things like mean, min/max values, or the difference
created that hour and store just that result in our long-term statistics.
These statistics is what partly powers the new Energy dashboard, however,
-they can be used for anything else: Introducing the Lovelace [statistics graph card](/lovelace/statistics-graph/).
+they can be used for anything else: Introducing the Lovelace [statistics graph card](/dashboards/statistics-graph/).
@@ -170,7 +170,7 @@ Screenshot of the Gauge card in needle mode with severity configured.
These settings are available straight from the Lovelace UI editor; More
-information and examples can be found in the [Gauge card documentation](/lovelace/gauge/).
+information and examples can be found in the [Gauge card documentation](/dashboards/gauge/).
## Currency core setting
diff --git a/source/_posts/2022-03-02-release-20223.markdown b/source/_posts/2022-03-02-release-20223.markdown
index 5761f822938..21bcd9a37fd 100644
--- a/source/_posts/2022-03-02-release-20223.markdown
+++ b/source/_posts/2022-03-02-release-20223.markdown
@@ -205,7 +205,7 @@ Click the My button below to test it out on your Home Assistant instance:
{% my developer_template badge %}
[@kubawolanin]: https://github.com/kubawolanin
-[Lovelace cards]: /lovelace/cards
+[Lovelace cards]: /dashboards/cards
[Tim Cowell]: https://github.com/tgcowell
[Waves]: https://github.com/tgcowell/waves
diff --git a/source/_redirects b/source/_redirects
index 1e93fff3919..b05d8bc89fa 100644
--- a/source/_redirects
+++ b/source/_redirects
@@ -1060,7 +1060,7 @@
/integrations/cover.modbus /integrations/modbus
/integrations/fan.xiaomi_miio /integrations/xiaomi_miio
/integrations/light.xiaomi_miio /integrations/xiaomi_miio
-/integrations/lovelace /lovelace
+/integrations/lovelace /dashboards
/integrations/remote.xiaomi_miio /integrations/xiaomi_miio
/integrations/sensor.websocket_api /integrations/websocket_api
/integrations/sensor.modbus /integrations/modbus
@@ -2182,11 +2182,14 @@
/tag/* /tag 200
# Lovelace documentation
-/lovelace/entity-button /lovelace/button
-/lovelace/views /lovelace/dashboards-and-views
-/lovelace/yaml-mode /lovelace/dashboards-and-views
-/lovelace/calendar-card /lovelace/calendar
-/integrations/lovelace /lovelace
+/lovelace/entity-button /dashboards/button
+/lovelace/views /dashboards/dashboards-and-views
+/lovelace/yaml-mode /dashboards/dashboards-and-views
+/lovelace/calendar-card /dashboards/calendar
+/integrations/lovelace /dashboards
+/lovelace/* /dashboards/:splat
+/images/lovelace/* /images/dashboards/:splat
+
# Removed documentation
/docs/installation /getting-started
diff --git a/source/lovelace/actions.markdown b/source/dashboards/actions.markdown
similarity index 95%
rename from source/lovelace/actions.markdown
rename to source/dashboards/actions.markdown
index 099e5f8477d..82ed55aa709 100644
--- a/source/lovelace/actions.markdown
+++ b/source/dashboards/actions.markdown
@@ -7,14 +7,14 @@ Some cards have support for tap actions. These actions define what will happen w
Actions can be enabled on:
-- [Button](/lovelace/button/)
-- [Entities](/lovelace/entities/)
-- [Glance](/lovelace/glance/)
-- [Light](/lovelace/light/)
-- [Picture](/lovelace/picture/)
-- [Picture Element](/lovelace/picture-elements/)
-- [Picture Entity](/lovelace/picture-entity/)
-- [Picture Glance](/lovelace/picture-glance/)
+- [Button](/dashboards/button/)
+- [Entities](/dashboards/entities/)
+- [Glance](/dashboards/glance/)
+- [Light](/dashboards/light/)
+- [Picture](/dashboards/picture/)
+- [Picture Element](/dashboards/picture-elements/)
+- [Picture Entity](/dashboards/picture-entity/)
+- [Picture Glance](/dashboards/picture-glance/)
## Tap-Action
diff --git a/source/lovelace/badges.markdown b/source/dashboards/badges.markdown
similarity index 98%
rename from source/lovelace/badges.markdown
rename to source/dashboards/badges.markdown
index e101fabb8a0..04ed51f9025 100644
--- a/source/lovelace/badges.markdown
+++ b/source/dashboards/badges.markdown
@@ -7,7 +7,7 @@ Badges are widgets that sit at the top of a panel, above all the cards.
## State Label Badge
-The State Label badge allows you to display a state badge. This badge supports [actions](/lovelace/actions/).
+The State Label badge allows you to display a state badge. This badge supports [actions](/dashboards/actions/).
```yaml
type: state-label
diff --git a/source/lovelace/cards.markdown b/source/dashboards/cards.markdown
similarity index 100%
rename from source/lovelace/cards.markdown
rename to source/dashboards/cards.markdown
diff --git a/source/lovelace/dashboards.markdown b/source/dashboards/dashboards.markdown
similarity index 97%
rename from source/lovelace/dashboards.markdown
rename to source/dashboards/dashboards.markdown
index 237697c30d8..411472ca27f 100644
--- a/source/lovelace/dashboards.markdown
+++ b/source/dashboards/dashboards.markdown
@@ -1,6 +1,6 @@
---
-title: "Dashboards"
-description: "A powerful and configurable interface for Home Assistant."
+title: "Multiple Dashboards"
+description: "Multiple powerful and configurable dashboards in Home Assistant."
---
You can define multiple dashboards in Home Assistant. Each dashboard can be added to the sidebar. This makes it possible to create separate control dashboards for each individual part of your house.
@@ -70,10 +70,10 @@ lovelace:
title: YAML
icon: mdi:script
show_in_sidebar: true
- filename: lovelace.yaml
+ filename: dashboards.yaml
```
-{% configuration Lovelace %}
+{% configuration dashboards %}
mode:
required: true
description: "In what mode should the main dashboard be, `yaml` or `storage` (UI managed)."
diff --git a/source/lovelace/header-footer.markdown b/source/dashboards/header-footer.markdown
similarity index 84%
rename from source/lovelace/header-footer.markdown
rename to source/dashboards/header-footer.markdown
index 9785f832be0..36c3abe675e 100644
--- a/source/lovelace/header-footer.markdown
+++ b/source/dashboards/header-footer.markdown
@@ -5,7 +5,7 @@ description: "Decorate your dashboard cards with header and footer widgets."
Some dashboard cards have support for header and footer widgets. These widgets fill up the whole available space in a card.
-
+
Screenshot of an entities card with a picture header and buttons footer.
@@ -16,7 +16,7 @@ Widget to show a picture as a header or a footer. A picture can have touch actio
```yaml
header:
type: picture
- image: "https://www.home-assistant.io/images/lovelace/header-footer/balloons-header.png"
+ image: "https://www.home-assistant.io/images/dashboards/header-footer/balloons-header.png"
```
{% configuration header-footer %}
@@ -30,15 +30,15 @@ image:
type: string
tap_action:
required: false
- description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
+ description: Action taken on card tap. See [action documentation](/dashboards/actions/#tap-action).
type: map
hold_action:
required: false
- description: Action to take on tap-and-hold. See [action documentation](/lovelace/actions/#hold-action).
+ description: Action to take on tap-and-hold. See [action documentation](/dashboards/actions/#hold-action).
type: map
double_tap_action:
required: false
- description: Action to take on double tap. See [action documentation](/lovelace/actions/#double-tap-action).
+ description: Action to take on double tap. See [action documentation](/dashboards/actions/#double-tap-action).
type: map
{% endconfiguration %}
@@ -85,7 +85,7 @@ entities:
Widget to show an entity in the sensor domain as a graph in the header or footer.
-
+
Screenshot of an entities card with a graph footer.
diff --git a/source/lovelace/index.markdown b/source/dashboards/index.markdown
similarity index 87%
rename from source/lovelace/index.markdown
rename to source/dashboards/index.markdown
index f7d94b61d0d..63526f9f56f 100644
--- a/source/lovelace/index.markdown
+++ b/source/dashboards/index.markdown
@@ -1,9 +1,9 @@
---
-title: "Dashboard"
-description: "A powerful and configurable dashboard for Home Assistant."
+title: "Dashboards"
+description: "Powerful and configurable dashboards for Home Assistant."
---
-The Home Assistant dashboard is a fast, customizable and powerful way for users to manage their home using their mobiles and desktops.
+Home Assistant dashboards are a fast, customizable and powerful way for users to manage their home using their mobiles and desktops.
- 29 different cards to place and configure as you like.
- Dashboard Editor: Allows you to manage your dashboard by including a live preview when editing cards.
diff --git a/source/lovelace/views.markdown b/source/dashboards/views.markdown
similarity index 97%
rename from source/lovelace/views.markdown
rename to source/dashboards/views.markdown
index f3cad05230c..9a54d1d8d39 100644
--- a/source/lovelace/views.markdown
+++ b/source/dashboards/views.markdown
@@ -10,7 +10,7 @@ You can add a view to your user interface, by clicking the menu (three dots at t
Click the `+` button in the top menu bar.
-
+
Use titles and icons to describe the content of views.
@@ -86,7 +86,7 @@ user:
## Type
-You can change the layout of a view by using a different view type. The default is [`masonry`](/lovelace/masonry).
+You can change the layout of a view by using a different view type. The default is [`masonry`](/dashboards/masonry).
#### Example
diff --git a/source/docs/index.markdown b/source/docs/index.markdown
index 8ccc3fbfa86..e97d2950b09 100644
--- a/source/docs/index.markdown
+++ b/source/docs/index.markdown
@@ -25,11 +25,11 @@ The documentation covers beginner to advanced topics around the installation, se