Repository navigation
Mount AutoOps insights under a docs-content parent page - #4499
Merged
Merged
Conversation
Mounts docs-content://reference/autoops-insights as the AutoOps insights parent and moves the Elasticsearch toc under it as a child at reference/autoops-insights/elasticsearch. Cloud and Kibana follow once their tocs exist on autoops-insights main. Related to elastic/docs-eng-team#1094 Related to #4495 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1 of 2 tasks
Contributor
Docs preview (local build)Handbook preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/4499/ |
akira28
approved these changes
Oct 19, 2026
theletterf
added a commit
that referenced
this pull request
Oct 19, 2026
… docs (#4503) * Add a temporary phantom for the AutoOps insights parent page elastic/docs-content#8900 adds reference/autoops-insights as a parent toc, but its docs-build fails the prefix check because autoops-insights pages still resolve to the same URLs under the current navigation. A phantom for the new parent makes the checker skip that prefix, so #8900 can pass and merge before the real mount in #4499. Related to elastic/docs-eng-team#1094 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * Add a temporary phantom for the AutoOps insights cloud docs elastic/autoops-insights#186 and #189 add generated/docs/cloud, which fails the prefix check because no navigation entry covers autoops-insights://cloud. A phantom unblocks them until the real child mount is added. Related to elastic/docs-eng-team#1094 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> Co-authored-by: Andrea De Pirro <andrea.depirro@elastic.co>
The temporary phantom for docs-content://reference/autoops-insights/ from #4503 only existed so elastic/docs-content#8900 could pass before this mount. The cloud phantom stays until the cloud child is mounted. Related to elastic/docs-eng-team#1094 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
alexandra5000
pushed a commit
to alexandra5000/docs-content
that referenced
this pull request
Oct 19, 2026
## Summary The AutoOps insights docs are about to grow past Elasticsearch. The `autoops-insights` repo is adding Cloud pages now, with Kibana to follow, and two content PRs there (elastic/autoops-insights#186 and #189) are blocked on navigation. We agreed on a single "AutoOps insights" parent with one child per component, so this PR creates the parent. It adds `reference/autoops-insights/` with a short landing page and a `toc.yml`, and lists the new toc in `reference/toc.yml`. The children stay in `elastic/autoops-insights` and get assembled under the parent by `navigation.yml`, the same way `reference/elasticsearch-clients` works. The landing page links only to the Elasticsearch insights for now. I'll add Cloud and Kibana links as those children land. Moving the Elasticsearch insights under the parent changes their URLs, from `reference/autoops-insights/<page>` to `reference/autoops-insights/elasticsearch/<page>`. The pages are already published, so I added a redirect for each of the 132 pages, pointing at the new cross-repo target (`autoops-insights://elasticsearch/<page>.md`). The old index URL needs no redirect, because it becomes this landing page. The redirects have to live here rather than in `autoops-insights`: I checked how the assembler resolves redirect keys, and a key in the `autoops-insights` docset would resolve to the wrong URL once the parent is in `docs-content`. This PR depends on a companion change in `elastic/docs-builder` that mounts the parent and the Elasticsearch child in `config/navigation.yml`. The two need to merge close together. That change is elastic/docs-builder#4499. Locally, a full build of this branch finishes with 0 errors and Vale reports 0 errors. I haven't verified the redirects end to end in an assembler build: an isolated build skips cross-repo redirect targets by design, so the redirect resolution is only checked against the resolver class, not a full site build. Related to elastic/docs-eng-team#1094 ## Generative AI disclosure 1. Did you use a generative AI (GenAI) tool to assist in creating this contribution? - [x] Yes - [ ] No Tool(s) and model(s) used: Claude Code (Claude Sonnet 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
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
2 participants
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.
autoops-insightsis adding Cloud docs next to Elasticsearch, and the navigation only mounts the Elasticsearch toc. That is what failsNavigationPrefixCheckeron elastic/autoops-insights#186 and #189 (#4495). We agreed on a single "AutoOps insights" parent with one child per component, so this PR sets up that shape. It is phase 2 of a two-phase merge: the temporary phantoms from #4503 are already onmain, and this PR removes the one for the parent.It replaces the single
autoops-insights://elasticsearchentry inconfig/navigation.ymlwith a parent,docs-content://reference/autoops-insights, and mounts the Elasticsearch toc as its child atreference/autoops-insights/elasticsearch. The parent page and the redirects for the moved URLs are in elastic/docs-content#8900. This is the same pattern asreference/elasticsearch-clients. The child setsnavigation_title: Elasticsearch, because the Elasticsearch index page is itself titled "AutoOps insights" and the sidebar would otherwise show that label twice. I also removed the parent phantom, since the real mount replaces it.I did not mount Cloud here.
cloud/toc.ymlonly exists on the openautoops-insightsPRs, and the assembler errors on a child toc that is missing frommain("Could not find navigation node"). Theautoops-insights://cloudphantom from #4503 stays until the Cloud child is added in a follow-up, once one of those PRs merges.I tested the branch locally after merging in
mainand removing the phantom. With the #8900 build,assembler navigation validate-link-referencereports 0 errors. With a build of #189 it also reports 0, covered by the Cloud phantom.assembler navigation validate, the CI check, reports 0 as well. I did not run a full assembler build, so the rendered sidebar is not verified.This still waits on elastic/docs-content#8900. The assembler preview here fails with "Could not find navigation node for identifier: docs-content://reference/autoops-insights" until the parent toc is on
docs-contentmain, so #8900 has to merge first.Related to elastic/docs-eng-team#1094
🤖 Generated with Claude Code