[Internal]: [Security] Document UI changes for the new left-side solution navigation

[natasha-moore-elastic]

Description

• Sub issue of [Internal]: New left-side solution navigation for 9.2 #2566.

This issue tracks the work for updating Security docs to reflect the new left-side solution navigation.

Resources

PR

Product review

Slack

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

The visual design will be the same across all deployment methods.
The items in the menu hierarchy will be different across ECH and Serverless (it will mostly replicate the existing structure)

What release is this request related to?

9.2

Serverless release

Mid-October

Collaboration model

The documentation team

Point of contact.

Main contact: @alexmarhaba

Stakeholders:

[natasha-moore-elastic]

Demo of UI changes in the Security nav presented in Sep 2 Security all hands.

[florent-leborgne]

Guidance:

Screenshot guidance

• General guidelines https://stunning-adventure-qrvr1k2.pages.github.io/style-guide/ui-writing/#screenshots
• Specific for this issue:
  • Show the latest only, no need to version/applies_to screenshots showing the nav.
  • Update screenshots with the following priorities in all doc sets:
    1. For 9.2: Refresh screenshots in getting started docs and docs around how to navigate in Kibana (when they exist)
    2. If time, after 9.2 is fine if other priorities: Any other screenshot shouldn't show the navigation. Either remove the screenshot, or edit/retake it to only show the feature / area of focus

Versioning guidance for pre&post 9.2 navs

It's important to stay correct regardless of the version that users are on. In this case, pages aren't changing name, but are moving to a different parent menu:

• Main features accessible in the navigation menu are still going to remain the same, so no update to plan there. Still, each solution handled their nav changes, so a quick double check might be necessary.
• Some management features (ingest and data management) are moving away from Stack management and moving into a new Data management menu in 9.2 and serverless.

We must avoid adding too many versioning notes, especially in what is generally the 1st step of a procedure. For that reason, we'll simplify menu cascades to omit the "Stack management" part, still mention that the page is a "management" page to hint on the fact that the page is found in the settings/management part of the UI, and advise users to find the page using the global search field if needed.

Example:

1. Go to Stack Management > Index Lifecycle Policies, and select Create policy.

should become

1. Go to the **Index Lifecycles Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
2. Select **Create policy**.

Where the note is a single snippet that we can include wherever needed.

[florent-leborgne]

A quick not to say that sometimes "Stack management", or "Stack Management" is also referenced using a variable: {{stack-manage-app}}