From 792a18b9a81630c2d0941862660d819ec26b1a0a Mon Sep 17 00:00:00 2001
From: perjury <phil@pjrprojects.co.uk>
Date: Fri, 31 Jan 2020 10:50:44 +0000
Subject: [PATCH] Rationalisation (#11908)

Move options for visible to be under Visible heading
---
 source/lovelace/views.markdown | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

diff --git a/source/lovelace/views.markdown b/source/lovelace/views.markdown
index 2b73b35b912..1c745a7292a 100644
--- a/source/lovelace/views.markdown
+++ b/source/lovelace/views.markdown
@@ -57,17 +57,6 @@ views:
       default: true
 {% endconfiguration %}
 
-### Options For Visible
-
-If you define `visible` as objects instead of a boolean to specify conditions for displaying the view tab:
-
-{% configuration badges %}
-user:
-  required: true
-  description: User id that can see the view tab (unique hex value found on the Users configuration page).
-  type: string
-{% endconfiguration %}
-
 #### Example
 
 View config:
@@ -141,6 +130,16 @@ views:
     cards:
       ...
 ```
+### Options For Visible
+
+If you define `visible` as objects instead of a boolean to specify conditions for displaying the view tab:
+
+{% configuration badges %}
+user:
+  required: true
+  description: User id that can see the view tab (unique hex value found on the Users configuration page).
+  type: string
+{% endconfiguration %}
 
 ## Panel