docs: hide docs for experimental feature (backport k248) (#17295)

Co-authored-by: J Stickler <julie.stickler@grafana.com>

Author: loki-gh-app[bot]

docs/sources/operations/loki-ui/_index.md

@@ -1,45 +1,57 @@
 ---
-title: Loki Deployment UI 
+title: Loki deployment user interface
 menuTitle: Loki UI
-description: Describes how to setup and use the Loki Deployment UI
+description: Describes how to setup and use the Loki Deployment UI.
+draft: true
 weight: 100
 ---
-# Loki Deployment UI 
+
+# Loki deployment user interface 
 
 {{< admonition type="warning" >}}
-The Loki Deployment UI is experimental and subject to change. Before attempting to deploy the Loki make sure to consult the [Considerations](#considerations) section.
+The Loki Deployment UI is experimental and subject to change. Before attempting to deploy the Loki UI, make sure to consult the [Considerations](#considerations) section.
 {{< /admonition >}}
 
 The Loki Deployment UI is a web-based user interface that allows you to manage and monitor a Loki deployment in [microservice mode](https://grafana.com/docs/loki/<LOKI_VERSION>/get-started/deployment-modes/#microservices-mode) or [single binary mode](https://grafana.com/docs/loki/<LOKI_VERSION>/get-started/deployment-modes/#monolithic-mode).
 
 {{< figure max-width="100%" src="/media/docs/loki/loki-ui.png" caption="Loki UI Home Page" >}}
 
-## Accessing the Loki Deployment UI
-
-The Loki Deployment UI is available at the following URL:
-
-```
-http://<LOKI_HOST>:<LOKI_PORT>/ui
-```
+## Considerations
 
-Where `<LOKI_HOST>` is the hostname or IP address of the Loki server and `<LOKI_PORT>` is the port number that Loki is running on. By default, Loki runs on port `3100`. If you are running Loki in Kubernetes the UI is made accessible via the `loki-gateway` service. Either by port-forwarding or by exposing the service via a LoadBalancer. 
+The Loki Deployment UI is experimental and subject to change. Before attempting to deploy the Loki make sure to consult the following considerations:
 
-{{< admonition type="caution" >}}
-`/ui` currently cannot be changed to another path. This would require further contribution.
-{{< /admonition >}}
+1. Not all features are available in the Loki Deployment UI. Some features are still in development.
+1. There is no authentication or authorization in the Loki Deployment UI. This means that anyone with access to the UI can make make delete requests, change log levels, etc.
+1. This UI is not intended to replace meta-monitoring for Loki.
 
 ## Deployment
 
-Each Loki component now includes the UI service. When running Loki as a docker container, the UI service is enabled by default. No additional configuration is required. 
+Each Loki component now includes the UI service. 
 
-For Loki helm users discoverability of the UI service needs to be enabled in the Loki configuration. To enable the UI discoverability, add the following paramter to the `loki` section of the `values.yaml` file:
+When running Loki as a docker container, the UI service is enabled by default. No additional configuration is required. 
+
+For Loki Helm users discoverability of the UI service needs to be enabled in the Loki configuration. To enable the UI discoverability, add the following paramter to the `loki` section of the `values.yaml` file:
 
 ```yaml
 loki:
   ui:
    enabled: true
 ```
 
+## Accessing the Loki Deployment UI
+
+The Loki Deployment UI is available at the following URL:
+
+```
+http://<LOKI_HOST>:<LOKI_PORT>/ui
+```
+
+Where `<LOKI_HOST>` is the hostname or IP address of the Loki server and `<LOKI_PORT>` is the port number that Loki is running on. By default, Loki runs on port `3100`. If you are running Loki in Kubernetes the UI is made accessible via the `loki-gateway` service. Either by port-forwarding or by exposing the service via a LoadBalancer. 
+
+{{< admonition type="caution" >}}
+Currently `/ui` cannot be changed to another path. This would require further contributions to the code base.
+{{< /admonition >}}
+
 ## Features
 
 The Loki Deployment UI provides the following features to manage and monitor a Loki deployment:
@@ -56,7 +68,6 @@ The Loki Deployment UI provides the following features to manage and monitor a L
 | [Labels](#labels) | View Label stats | Coming Soon |
 | [Rules](#rules) | View and manage rules | Coming Soon |
 
-
 ### Nodes
 
 The Nodes page displays the status of each Loki component deployed. Depending on the deployment mode, each component will either be considered a node or a service. Below is a screenshot of the Nodes table for a microservices deployment:
@@ -99,7 +110,6 @@ This feature is coming soon.
 
 {{< /admonition >}}
 
-
 ### Rings
 
 Rings section of the Loki UI provides a view of the status of the ring members. There can be a total of 5 rings in a Loki deployment. Each ring is responsible for a specific task. Note that not all rings will be present in a deployment, this is dependent on how you have configured your Loki deployment. For example Index Gateway and Query Scheduler both require explicit configuration to be enabled.
@@ -194,11 +204,4 @@ This feature is coming soon.
 
 This feature is coming soon.
 
-{{< /admonition >}}
-
-## Considerations
-
-The Loki Deployment UI is experimental and subject to change. Before attempting to deploy the Loki make sure to consult the following considerations:
-1. Not all features are available in the Loki Deployment UI. Some features are still in development.
-2. There is no authentication or authorization in the Loki Deployment UI. This means that anyone with access to the UI can make make delete requests, change log levels, etc.
-3. This UI is not intended to replace meta monitoring for Loki.
+{{< /admonition >}}