jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-06-25 03:26:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Sections view: add steps on migrating into sections view (#35585)

Browse Source 
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
This commit is contained in:
c0ffeeca7 2024-11-05 17:52:36 +01:00 committed by Franck Nijhof
parent 2012a0e838
commit c38d5bfa3e
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
1 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
source/dashboards/views.markdown
View File

@ -35,9 +35,9 @@ Views control the layout.
There are four different view types:
- **Sections (default)**: Arranges cards in a grid system and lets you group them in sections.
- **Masonry**: Arranges cards in columns based on their card size.
- **Panel**: Displays one card in full width. For example a map or an image.
- **Sidebar**: Arranges cards in 2 columns, a wide one and a smaller one on the right.
- **Masonry**: Arranges cards in columns based on their card size.
## Adding a view to a dashboard
@ -67,6 +67,28 @@ There are four different view types:
- Sidebar and panel views do not support badges.
6. By default, the new section is visible to all users. On the **Visibility** tab, you can disable the view for users.
## Migrating a view into a sections view
If you have already defined a view but you would now like to have it in a section view type, you can migrate that content. For example, you can migrate from a masonry to a sections view. Currently, you cannot migrate a sections view type into another view type.
Migrating does not affect the current view. It will stay as is, and a new, additional view is created.
To migrate a view into a sections view type, follow these steps:
1. Open the view you want to migrate, and go into edit mode.
2. In the configuration dialog, select the new view type.
3. If the new view type offers additional settings, define those settings.
- For more information on those settings, refer to the documentation of that view type.
4. In the top-right corner, select **Convert**.
- **Result**: A new, additional view is created.
- Your current view will stay untouched.
- A new tab opens, and all your cards are imported to the new view.
5. In the **Imported cards** section, pick each of the cards, and place them into the sections.
- To edit and customize the view, follow the steps in the [sections view](/dashboards/sections/) documentation.
6. To save your changes, select **Done**.
- **Result**: Your new dashboard is shown.
- If you have cards that were not yet integrated, you can still add them later. They are still available in the Edit mode, in the **Imported cards** section.
## URL of a view
You can link to one view from a card in another view when using cards that support navigation (`navigation_path`). The string supplied here will be appended to the string `/lovelace/` to create the path to the view. Do not use special characters in paths. Do not begin a path with a number. This will cause the parser to read your path as a view index.