Part 1: Update docs for cloud nav redesign - #8192
Open
wajihaparvez wants to merge 5 commits into
Open
Conversation
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
Contributor
Elastic Docs Style Checker (Vale)Summary: 4 warnings found
|
| File | Line | Rule | Message |
|---|---|---|---|
| deploy-manage/api-keys/elastic-cloud-api-keys.md | 53 | Elastic.MenuArrowsBold | Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy. |
| deploy-manage/api-keys/elastic-cloud-api-keys.md | 107 | Elastic.MenuArrowsBold | Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy. |
| deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md | 26 | Elastic.MenuArrowsBold | Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy. |
| manage-data/ingest/ingesting-data-from-applications/ingest-data-with-python-on-elasticsearch-service.md | 83 | Elastic.MenuArrows | Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy. |
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Updates docs to reflect new nav changes in cloud UI.
Rel docs issue: https://github.com/elastic/docs-content-internal/issues/1688
Side nav reorg
Lots of items in the nav moved around to new sections (listed here). In most cases, I opted to exclude subsections and just document the
top-level section > target page(e.g. Organization> Identity and access> Members) to future-proof in case subsections are moved again. The subsections are not clickable in the UI anyway.Rel cloud UI PR: https://github.com/elastic/cloud-ui/pull/4127
Reset password path (ECH and ECE)
Previously, users could reset their password from their deployment's Security page or Overview > Actions menu. The Security path is going away now.
Rel cloud UI PR: https://github.com/elastic/cloud-ui/pull/4279
Bonus
I found a bunch of ECH/ECE “reset the password” links that pointed to the self-managed built-in users page, which then directed cloud users to the ECH/ECE page (2 steps later). Fixed to point to the ECH/ECE page directly.
Generative AI disclosure