[DOCS][Roadmap] Reorg Kibana Guide

[gchaps]

This is a roadmap for creating a Kibana developer doc and reorganizing the user and admin content based on task.

Goal

Our current docs are organized by how the feature appears in the Kibana side navigation. This isn't ideal for our users--lots of good content is buried under generic headings. We'll reorganize the content into a developer and user guide and make information easier to find. As we implement this task-based structure, we'll flesh out the docs with more use cases and examples and embed introductory videos for beginning users. Because writing is the responsibility of the entire team, we'll provide templates to help everyone structure their docs and improve consistency.

User and admin guide

Here is the proposed top-level structure for the User guide

• Introduction
• Get started
• Set up Kibana
• Get data into Kibana
• Visualize & explore
• Extend your use case
• Make your data responsive
• Advanced data modeling
• Manage your cluster data
• Monitor your cluster health
• Stack development tools
• REST APIs
• Plugins
• Release Notes

Developer guide

Content for the developer guide is discussed in a separate issue.

Phase 1: Developer guide

Create a developer guide that incorporates the ideas discussed in this issue.

• Create a folder for the developer docs: [DOCS] Creates developer folder #45280
• Change Kibana Reference to Kibana guide: Change Kibana Reference to Kibana Guide docs#1149
• Change Kibana User Guide to Kibana Guide: [DOCS] Change title of Kibana book #44957
• Move appropriate existing content into dev folder: [DOCS] Create developer guide part #44954
  - [ ] Fix any places in other repos where we "include" the existing dev files, since their paths will have changed
• Update landing pages to link to developer doc. See the mockup here.

Phase 2: User and admin guide

Create a task-based user/admin guide.

• Create a folder for the user docs: [DOCS] Adds user folder #45411
• Create a folder for the admin docs
• Define which content is user and which is admin
• Create content outline
• Move appropriate content into user or admin folders (staged)
• Fix any places in other repos where we "include" those files, since their paths will have changed: [DOCS] Fixes link to Kibana security elasticsearch#46690, Updates path in Stack Overview to Kibana monitoring stack-docs#510, [DOCS] Updates links to reporting content elasticsearch#46717 ...
• Define whether content belongs in one guide or two
• Update landing page

[elasticmachine]

Pinging @elastic/kibana-docs

[KOTungseth]

This is mostly done, so we are closing. When the new docs vision is approved, we'll create a new roadmap.