-
Notifications
You must be signed in to change notification settings - Fork 181
[Security] New solution navigation for 9.2 #3405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔍 Preview links for changed docs |
florent-leborgne
approved these changes
Oct 9, 2025
Contributor
florent-leborgne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
rhr323
pushed a commit
to rhr323/docs-content
that referenced
this pull request
Oct 27, 2025
Resolves elastic#2590. This PR: * Removes the **Navigation menu** section. Explaining how to use the navigation menu felt like overkill – the UI should be intuitive enough not to need docs. Also, updating this section to account for the 9.2 changes while keeping it accurate for pre-9.2 versions would have made the section complex by adding more versioning tags, without necessarily adding much user value. * Makes the wording around management and project settings sections more general, so it applies to all 9.x versions. Since some items are moving from **Stack Management** to a new **Data management** section, maintaining precise lists of menu items for both 9.2 and pre-9.2 versions and serverless would have introduced more versioning/tagging complexity. This also reduces maintenance complexity for future version updates. * Reorders sections to reflect the order of pages in the 9.2 UI. * Adds missing sections for attack discovery and notes. * Updates any mention of items that have moved from **Stack Management** to **Data management**. * Updates any screenshots that show the navigation menu. Preview: [Elastic Security UI](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3405/solutions/security/get-started/elastic-security-ui)
naemono
pushed a commit
to naemono/docs-content
that referenced
this pull request
Oct 28, 2025
Resolves elastic#2590. This PR: * Removes the **Navigation menu** section. Explaining how to use the navigation menu felt like overkill – the UI should be intuitive enough not to need docs. Also, updating this section to account for the 9.2 changes while keeping it accurate for pre-9.2 versions would have made the section complex by adding more versioning tags, without necessarily adding much user value. * Makes the wording around management and project settings sections more general, so it applies to all 9.x versions. Since some items are moving from **Stack Management** to a new **Data management** section, maintaining precise lists of menu items for both 9.2 and pre-9.2 versions and serverless would have introduced more versioning/tagging complexity. This also reduces maintenance complexity for future version updates. * Reorders sections to reflect the order of pages in the 9.2 UI. * Adds missing sections for attack discovery and notes. * Updates any mention of items that have moved from **Stack Management** to **Data management**. * Updates any screenshots that show the navigation menu. Preview: [Elastic Security UI](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3405/solutions/security/get-started/elastic-security-ui)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #2590.
This PR:
Preview: Elastic Security UI