next steps

Author: shainaraskas

deploy-manage/deploy/self-managed/_snippets/install-kib-next-steps.md

@@ -0,0 +1,5 @@
+You now have a basic {{kib}} instance set up. Consider the following next steps:
+
+* Learn how to [configure {{kib}}](/deploy-manage/deploy/self-managed/configure-kibana.md).
+* Learn how to [access {{kib}}](/deploy-manage/deploy/self-managed/access-kibana.md).
+* Explore [key configuration topics](/deploy-manage/deploy/self-managed/configure-kibana.md#additional-guides) to learn how to secure and manage {{kib}}.

deploy-manage/deploy/self-managed/_snippets/install-next-steps.md

@@ -1,4 +1,12 @@
 You now have a test {{es}} environment set up. Before you start serious development or go into production with {{es}}, you must do some additional setup:
 
 * Learn how to [configure {{es}}](/deploy-manage/deploy/self-managed/configure-elasticsearch.md).
-* Configure [important {{es}} settings](/deploy-manage/deploy/self-managed/important-settings-configuration.md).
+* Configure [important {{es}} settings](/deploy-manage/deploy/self-managed/important-settings-configuration.md).
+* Install [{{kib}}](/deploy-manage/deploy/self-managed/install-kibana.md), the user interface for all Elastic solutions.
+
+You can also do the following:
+
+* Consider installing [additional {{stack}} components](/get-started/the-stack.md).
+* Learn how to [ingest data into {{es}}](/manage-data/index.md).
+* Learn about [production considerations](/deploy-manage/production-guidance.md).
+* Explore [other topics](/deploy-manage/deploy/self-managed#other-important-sections.md) to learn how to secure and manage your cluster.

deploy-manage/deploy/self-managed/configure-elasticsearch.md

@@ -131,7 +131,7 @@ Static settings can only be configured on an unstarted or shut down node using `
 
 Static settings must be set on every relevant node in the cluster.
 
-## Additional guides
+## Additional topics
 
 Refer to the following documentation to learn how to perform key configuration tasks for {{es}}: 
 

deploy-manage/deploy/self-managed/configure-kibana.md

@@ -31,12 +31,13 @@ Environment variables can be injected into configuration using `${MY_ENV_VAR}` s
 
 For a complete list of settings that you can apply to {{kib}}, refer to [{{kib}} configuration reference](kibana:///reference/configuration-reference.md).
 
-## Additional guides
+## Additional topics
 
 Refer to the following documentation to learn how to perform key configuration tasks for {{kib}}: 
 
 * [Configure SSL certificates](/deploy-manage/security/set-up-basic-security-plus-https.md#encrypt-kibana-browser) to encrypt traffic between client browsers and {{kib}}
 * [Enable authentication providers](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md) for {{kib}}
+* Configure the {{kib}} [reporting feature](/deploy-manage/deploy/kibana-reporting-configuration.md)
 * Use [Spaces](/deploy-manage/manage-spaces.md) to organize content in {{kib}}, and restrict access to this content to specific users
 * Use [Connectors](/deploy-manage/manage-connectors.md) to manage connection information between {{es}}, {{kib}}, and third-party systems
 * Present a [user access agreement](/deploy-manage/users-roles/cluster-or-deployment-auth/access-agreement.md) when logging on to {{kib}}

deploy-manage/deploy/self-managed/install-kibana-from-archive-on-linux-macos.md

@@ -111,3 +111,8 @@ This is very convenient because you don’t have to create any directories to st
 | config | Configuration files including `kibana.yml` | `$KIBANA_HOME\config` | `[KBN_PATH_CONF](configure.md)` |
 | data | The location of the data files written to disk by {{kib}} and its plugins | `$KIBANA_HOME\data` |  |
 | plugins | Plugin files location. Each plugin will be contained in a subdirectory. | `$KIBANA_HOME\plugins` |  |
+
+## Next steps
+
+:::{include} _snippets/install-kib-next-steps.md
+:::

deploy-manage/deploy/self-managed/install-kibana-on-windows.md

@@ -70,3 +70,8 @@ This is very convenient because you don’t have to create any directories to st
 | config | Configuration files including `kibana.yml` | `$KIBANA_HOME\config` | `[KBN_PATH_CONF](configure.md)` |
 |  | data | `The location of the data files written to disk by {{kib}} and its plugins` | `$KIBANA_HOME\data` |
 |  | plugins | `Plugin files location. Each plugin will be contained in a subdirectory.` | `$KIBANA_HOME\plugins` |
+
+## Next steps
+
+:::{include} _snippets/install-kib-next-steps.md
+:::

deploy-manage/deploy/self-managed/install-kibana-with-debian-package.md

@@ -143,3 +143,8 @@ The Debian package places config files, logs, and the data directory in the appr
 | data | The location of the data files written to disk by {{kib}} and its plugins | `/var/lib/kibana` | `path.data` |
 | logs | Logs files location | `/var/log/kibana` | `[Logging configuration](../../monitor/logging-configuration/kibana-logging.md)` |
 | plugins | Plugin files location. Each plugin will be contained in a subdirectory. | `/usr/share/kibana/plugins` |  |
+
+## Next steps
+
+:::{include} _snippets/install-kib-next-steps.md
+:::

deploy-manage/deploy/self-managed/install-kibana-with-docker.md

@@ -188,19 +188,13 @@ All information that you include in environment variables is visible through the
 
 Some example translations are shown here:
 
-**Environment Variable**
-:   **{{kib}} Setting**
+| Environment variable | {{kib}} setting | 
+| --- | --- |
+| `SERVER_NAME` | `server.name` |
+| `SERVER_BASEPATH` | `server.basePath`| 
+| `ELASTICSEARCH_HOSTS` | `elasticsearch.hosts` |
 
-`SERVER_NAME`
-:   `server.name`
-
-`SERVER_BASEPATH`
-:   `server.basePath`
-
-`ELASTICSEARCH_HOSTS`
-:   `elasticsearch.hosts`
-
-In general, any setting listed in [*Configure {{kib}}*](configure.md) can be configured with this technique.
+In general, any setting listed in [](configure-kibana.md) can be configured with this technique.
 
 Supplying array options can be tricky. The following example shows the syntax for providing an array to `ELASTICSEARCH_HOSTS`.
 
@@ -240,3 +234,8 @@ These settings are defined in the default `kibana.yml`. They can be overridden w
 ::::{important}
 If replacing `kibana.yml` with a custom version, be sure to copy the defaults to the custom file if you want to retain them. If not, they will be "masked" by the new file.
 ::::
+
+## Next steps
+
+:::{include} _snippets/install-kib-next-steps.md
+:::

deploy-manage/deploy/self-managed/install-kibana-with-rpm.md

@@ -134,3 +134,8 @@ The RPM places config files, logs, and the data directory in the appropriate loc
 | data | The location of the data files written to disk by {{kib}} and its plugins | `/var/lib/kibana` | `path.data` |
 | logs | Logs files location | `/var/log/kibana` | `[Logging configuration](../../monitor/logging-configuration/kibana-logging.md)` |
 | plugins | Plugin files location. Each plugin will be contained in a subdirectory. | `/usr/share/kibana/plugins` |  |
+
+## Next steps
+
+:::{include} _snippets/install-kib-next-steps.md
+:::

deploy-manage/deploy/self-managed/install-kibana.md

@@ -11,55 +11,33 @@ sub:
 
 # Install {{kib}}
 
-This section includes information on how to setup {{kib}} and get it running, including:
+{{kib}} provides the user interface for all Elastic solutions. It’s a powerful tool for visualizing and analyzing your data, and for managing and monitoring the {{stack}}. Although {{kib}} is not required to use {{es}}, it's required for most use cases.
 
+This section includes information on how to set up {{kib}} and get it running, including:
 
-* Downloading
-* Installing
-* Starting
-* Configuring
-* Upgrading
+* Downloading and installing {{kib}}
+* Enrolling {{kib}} with an {{es}} cluster
+* Configuring {{kib}}
 
+To quickly set up {{es}} and {{kib}} in Docker for local development or testing, jump to [](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md).
 
 ## Supported platforms [supported-platforms] 
 
-Packages of {{kib}} are provided for and tested against Linux, Darwin, and Windows. Since {{kib}} runs on Node.js, we include the necessary Node.js binaries for these platforms. Running {{kib}} against a separately maintained version of Node.js is not supported.
+Packages of {{kib}} are provided for and tested against Linux, Darwin, and Windows. Because {{kib}} runs on Node.js, we include the necessary Node.js binaries for these platforms. Running {{kib}} against a separately maintained version of Node.js is not supported.
 
 To support certain older Linux platforms (most notably CentOS7/RHEL7), {{kib}} for Linux ships with a custom build of Node.js with glibc 2.17 support. For details, see [Custom builds of Node.js](kibana://extend/upgrading-nodejs.md#custom-nodejs-builds).
 
 ## {{kib}} install packages [install]
 
 {{kib}} is provided in the following package formats:
 
-`tar.gz`/`zip`
-:   The `tar.gz` packages are provided for installation on Linux and Darwin and are the easiest choice for getting started with {{kib}}.
-
-    The `zip` package is the only supported package for Windows.
-
-    [Install from archive on Linux or macOS](/deploy-manage/deploy/self-managed/install-from-archive-on-linux-macos.md) or [Install on Windows](/deploy-manage/deploy/self-managed/install-on-windows.md)
-
-
-`deb`
-:   The `deb` package is suitable for Debian, Ubuntu, and other Debian-based systems.  Debian packages may be downloaded from the Elastic website or from our Debian repository.
-
-    [Install with Debian package](/deploy-manage/deploy/self-managed/install-with-debian-package.md)
-
-
-`rpm`
-:   The `rpm` package is suitable for installation on Red Hat, SLES, OpenSuSE and other RPM-based systems.  RPMs may be downloaded from the Elastic website or from our RPM repository.
-
-    [Install with RPM](/deploy-manage/deploy/self-managed/install-with-rpm.md)
-
-
-`docker`
-:   Images are available for running {{kib}} as a Docker container. They may be downloaded from the Elastic Docker Registry.
-
-    [Running {{kib}} on Docker](/deploy-manage/deploy/self-managed/install-with-docker.md)
-
-
-::::{important} 
-If your {{es}} installation is protected by [{{stack-security-features}}](/deploy-manage/security.md) see [Configuring security in {{kib}}](/deploy-manage/security.md) for additional setup instructions.
-::::
+| Format | Description | Instructions |
+| --- | --- | --- |
+| `tar.gz` | The `tar.gz` packages are provided for installation on Linux and Darwin and are the easiest choice for getting started with {{kib}}. | [Install from archive on Linux or macOS](/deploy-manage/deploy/self-managed/install-from-archive-on-linux-macos.md)|
+| `zip` | The `zip` package is the only supported package for Windows.| [Install on Windows](/deploy-manage/deploy/self-managed/install-on-windows.md)|
+| `deb` | The `deb` package is suitable for Debian, Ubuntu, and other Debian-based systems.  Debian packages may be downloaded from the Elastic website or from our Debian repository. | [Install with Debian package](/deploy-manage/deploy/self-managed/install-with-debian-package.md) |
+| `rpm` | The `rpm` package is suitable for installation on Red Hat, SLES, OpenSuSE and other RPM-based systems.  RPMs may be downloaded from the Elastic website or from our RPM repository. | [Install with RPM](/deploy-manage/deploy/self-managed/install-with-rpm.md) |
+| `docker` | Images are available for running {{kib}} as a Docker container. They may be downloaded from the Elastic Docker Registry. | [Running {{kib}} on Docker](/deploy-manage/deploy/self-managed/install-with-docker.md) |
 
 ## {{es}} version [elasticsearch-version]