[DOC] Create new doc for Dashboard application

[vagimeli]

Signed-off-by: vagimeli vagimeli@amazon.com

Description

Create new site page titled Dashboard; create new content on creating your first dashboard

Issues Resolved

#2349
#2294

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[joshuarrrr]

Looking good!

The only major issue is that the instructions mention a "Vertical Bar" chart type where it should be guage.

Other than that, there were a few subtleties of behavior where I tried to provide some clarifying info which can be used or ignored.

[joshuarrrr]

Helpful! ❤️

[joshuarrrr]

These steps and the screenshot refer to a gauge chart, but L62 specifies "Vertical Bar", and should be updated to match.

[joshuarrrr]

Note that it is possible to change chart colors directly from the legend within a dashboard panel. The only difference is that those changes are only saved for that particular dashboard and panel, and don't affect the saved visualization. These steps save the colors on the visualization itself, which will apply to any dashboard that links to the visualization (unless they have already specified different panel colors).

[joshuarrrr]

"without applying the changes across the dashboard overall" isn't quite right - changing panel titles only affects the particular panel on the particular dashboard, and won't affect any other panel containing that same visualization (or any other dashboard).

[natebower]

@kolchfa-aws Please see my comments and changes and let me know if you have any questions. Thanks!

[natebower]

Suggested change

In this tutorial you'll learn the basics of creating a dashboard using the **Dashboard** application and OpenSearch sample data. The sample dataset has existing sample visualizations, and you can use those visualizations or create new visualizations for the dashboard. For this tutorial, you'll do both. Once you've completed this tutorial, you'll have learned the foundations of creating a new dashboard with multiple panels in OpenSearch Dashboards.

In this tutorial you'll learn the basics of creating a dashboard using the **Dashboard** application and OpenSearch sample data. The sample dataset has existing sample visualizations, and you can use those visualizations or create new visualizations for the dashboard. In this tutorial, you'll do both. Once you've completed this tutorial, you'll have learned the foundations of creating a new dashboard with multiple panels in OpenSearch Dashboards.

[natebower]

Suggested change

This OpenSearch playground [dashboard example](https://playground.opensearch.org/app/dashboards#/view/722b74f0-b882-11e8-a6d9-e546fe2bba5f?_g=(filters:!(),refreshInterval:(pause:!f,value:900000),time:(from:now-7d,to:now))&_a=(description:'Analyze%20mock%20eCommerce%20orders%20and%20revenue',filters:!(),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:'%5BeCommerce%5D%20Revenue%20Dashboard',viewMode:view)) shows you what's possible with OpenSearch Dashboards.

This OpenSearch Playground [dashboard example](https://playground.opensearch.org/app/dashboards#/view/722b74f0-b882-11e8-a6d9-e546fe2bba5f?_g=(filters:!(),refreshInterval:(pause:!f,value:900000),time:(from:now-7d,to:now))&_a=(description:'Analyze%20mock%20eCommerce%20orders%20and%20revenue',filters:!(),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:'%5BeCommerce%5D%20Revenue%20Dashboard',viewMode:view)) shows you what's possible with OpenSearch Dashboards.

[natebower]

Suggested change

	## Getting familiar with user interface
	## Getting familiar with the UI

[natebower]

Suggested change

	Before getting started, let's get familiar with the **Dashboard** user interface. The user interface comprises the following main parts:
	Before getting started, let's get familiar with the **Dashboard** UI. The UI comprises the following main parts:

[natebower]

Maybe "elements" or "components" instead of "parts"?

[natebower]

Suggested change

	Learn some useful terminology for working with OpenSearch Dashboards and the **Dashboard** application.
	The following is some useful terminology for working with OpenSearch Dashboards and the **Dashboard** application:

[natebower]

Suggested change

	To organize panels, arrange them side-by-side, or resize them, you can use these options:
	To organize panels, arrange them side by side, or resize them, you can use these options:

[natebower]

Suggested change

	- To move, select and hold the panel title or the panel top and drag to the new location.
	- To move a panel, select and hold the panel title or the panel top and drag to the new location.

[natebower]

Is there better terminology than "panel top"?

[natebower]

Suggested change

	- To resize, select the resize icon in the panel's lower right corner and drag to the new dimensions.
	- To resize a panel, choose the resize icon in the panel's lower-right corner and drag to the new dimensions.

[natebower]

Suggested change

	- To view in fullscreen mode, select the gear icon (edit mode) or vertical ellipsis (⋮) in the top right of the panel and select **Maximize panel**. To minimize the fullscreen mode, select the gear icon or vertical ellipsis and select **Minimize**.
	- To view a panel in full screen mode, choose the gear icon (edit mode) or vertical ellipsis (⋮) at the top right of the panel and select **Maximize panel**. To minimize the full screen mode, choose the gear icon or vertical ellipsis and select **Minimize**.

[natebower]

Suggested change

	The following is an example of a customized dashboard created in this tutorial.
	The following is an example of a customized dashboard created by using this tutorial.

[opensearch-trigger-bot]

The backport to 1.3 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-1.3 1.3
# Navigate to the new working tree
pushd ../.worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-2350-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-1.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-2350-to-1.3.

[opensearch-trigger-bot]

The backport to 2.0 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.0 2.0
# Navigate to the new working tree
pushd ../.worktrees/backport-2.0
# Create a new branch
git switch --create backport/backport-2350-to-2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-2.0
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.0

Then, create a pull request where the base branch is 2.0 and the compare/head branch is backport/backport-2350-to-2.0.

[opensearch-trigger-bot]

The backport to 2.1 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.1 2.1
# Navigate to the new working tree
pushd ../.worktrees/backport-2.1
# Create a new branch
git switch --create backport/backport-2350-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-2.1
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.1

Then, create a pull request where the base branch is 2.1 and the compare/head branch is backport/backport-2350-to-2.1.

[opensearch-trigger-bot]

The backport to 2.2 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.2 2.2
# Navigate to the new working tree
pushd ../.worktrees/backport-2.2
# Create a new branch
git switch --create backport/backport-2350-to-2.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-2.2
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.2

Then, create a pull request where the base branch is 2.2 and the compare/head branch is backport/backport-2350-to-2.2.

[opensearch-trigger-bot]

The backport to 2.3 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.3 2.3
# Navigate to the new working tree
pushd ../.worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-2350-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-2.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.3

Then, create a pull request where the base branch is 2.3 and the compare/head branch is backport/backport-2350-to-2.3.

[opensearch-trigger-bot]

The backport to 2.4 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.4 2.4
# Navigate to the new working tree
pushd ../.worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-2350-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-2.4
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.4

Then, create a pull request where the base branch is 2.4 and the compare/head branch is backport/backport-2350-to-2.4.

[opensearch-trigger-bot]

The backport to 2.5 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.5 2.5
# Navigate to the new working tree
pushd ../.worktrees/backport-2.5
# Create a new branch
git switch --create backport/backport-2350-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-2.5
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.5

Then, create a pull request where the base branch is 2.5 and the compare/head branch is backport/backport-2350-to-2.5.

[opensearch-trigger-bot]

The backport to 2.6 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.6 2.6
# Navigate to the new working tree
pushd ../.worktrees/backport-2.6
# Create a new branch
git switch --create backport/backport-2350-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7213507f9c7c1cea7858fe1663fca1313ac6755a
# Push it to GitHub
git push --set-upstream origin backport/backport-2350-to-2.6
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.6

Then, create a pull request where the base branch is 2.6 and the compare/head branch is backport/backport-2350-to-2.6.