Repository navigation
Add temporary phantoms for the AutoOps insights parent page and cloud docs - #4503
Merged
Merged
Conversation
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>
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>
theletterf
changed the title
akira28
approved these changes
Oct 19, 2026
Contributor
Docs preview (local build)Handbook preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/4503/ |
theletterf
added a commit
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>
theletterf
added a commit
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.
This is the first step of a two-phase merge for the AutoOps insights navigation, following the phantom approach Martijn suggested in #docs-eng. It adds two temporary phantoms to
config/navigation.yml.The first one,
docs-content://reference/autoops-insights/, unblocks elastic/docs-content#8900. That PR adds a parent page atreference/autoops-insights/, and #4499 mounts it in the navigation. They depend on each other. #8900 fails thevalidate-link-referencecheck, because theautoops-insightspages still resolve to the same URLs under today's navigation. #4499 fails its assembler preview, because the parent page is not ondocs-contentmainyet. The checker skips registering a phantom prefix, so the conflict goes away. The trailing slash matters: the checker compares against paths that end in/, and without it the phantom has no effect.The second one,
autoops-insights://cloud, unblocks elastic/autoops-insights#186 and #189 (#4495). Both addgenerated/docs/cloud, and the prefix check fails oncloud/...because no navigation entry covers it. A phantom makes the checker accept those paths. It does not publish the Cloud pages: they get no sidebar entry or mapped URL until the real child mount is added in a follow-up.I tested both locally. With the #8900 branch build,
assembler navigation validate-link-referencereports 133 conflict errors againstmain's navigation, the same as CI, and 0 with the first phantom. With the PR #189 build, it reports 2 errors againstmain's navigation and 0 with the second phantom.assembler navigation validatereports 0 in both cases. I did not run a full assembler build, so I have not checked how the phantom parent page renders.The plan from here:
edgeimage to rebuild.docs-buildcheck on Add an AutoOps insights parent page and redirects docs-content#8900, then merge it. The Cloud PRs inautoops-insightscan re-run their checks at the same point.Related to elastic/docs-eng-team#1094
🤖 Generated with Claude Code