Repository navigation
Add an AutoOps insights parent page and redirects - #8900
Merged
Merged
Conversation
Adds reference/autoops-insights as a parent toc with a landing page, so AutoOps insights can be grouped by component (Elasticsearch now, Cloud and Kibana later) with the component docs assembled from elastic/autoops-insights. The 132 existing Elasticsearch insight pages move from reference/autoops-insights/<page> to reference/autoops-insights/elasticsearch/<page>, so each old URL gets a redirect to its new cross-repo target. Related to elastic/docs-eng-team#1094 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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. |
akira28
approved these changes
Oct 19, 2026
theletterf
added a commit
to elastic/docs-builder
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>
theletterf
added a commit
to elastic/docs-builder
that referenced
this pull request
Oct 19, 2026
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>
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! 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. |
theletterf
added a commit
to elastic/docs-builder
that referenced
this pull request
Oct 19, 2026
* Mount AutoOps insights under a docs-content parent page 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> * Remove the parent phantom now that the real mount replaces it 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> --------- 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.
Summary
The AutoOps insights docs are about to grow past Elasticsearch. The
autoops-insightsrepo 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 atoc.yml, and lists the new toc inreference/toc.yml. The children stay inelastic/autoops-insightsand get assembled under the parent bynavigation.yml, the same wayreference/elasticsearch-clientsworks. 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>toreference/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 inautoops-insights: I checked how the assembler resolves redirect keys, and a key in theautoops-insightsdocset would resolve to the wrong URL once the parent is indocs-content.This PR depends on a companion change in
elastic/docs-builderthat mounts the parent and the Elasticsearch child inconfig/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
Tool(s) and model(s) used: Claude Code (Claude Sonnet 5.5)
🤖 Generated with Claude Code