Draft
Conversation
Move the individual EDOT SDK tocs (Android, .NET, iOS, Java, Node.js, PHP, Python, Browser) out from under the EDOT group and into a dedicated "EDOT SDKs" sibling group at the same level as Fleet, APM, Beats, etc. The group links to the existing edot-sdks index page. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
alexandra5000
changed the title
Add TocOverrideNode wrapper in SiteNavigationV2 so that when a toc: entry in navigation-v2.yml declares explicit children, those are used instead of the full V1 node tree — without mutating the shared node. Update navigation-v2.yml to limit opentelemetry://reference children to motlp, edot-cloud-forwarder, and edot-collector, keeping individual EDOT SDKs only in the new sibling EDOT SDKs group. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The edot-sdks deduplication is now handled upstream in elastic/opentelemetry by removing edot-sdks/index.md from the reference toc. No children override needed here — toc: opentelemetry://reference renders cleanly without the SDKs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Group the individual SDK tocs under opentelemetry://reference/edot-sdks in navigation.yml with path_prefix reference/opentelemetry/edot-sdks, so nav-v2 can reference it as a toc: entry with a correct URL. Update navigation-v2.yml to use toc: opentelemetry://reference/edot-sdks instead of group: + page:, which was producing a 404 due to naive URI path resolution ignoring the path_prefix. Co-Authored-By: Claude Sonnet 4.6 <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
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.
To be continued...
Summary
Proposes restructuring the EDOT section in
navigation-v2.ymlby extracting the individual SDK tocs into a dedicated sibling group.Before: All EDOT SDK content (Android, .NET, iOS, Java, Node.js, PHP, Python, Browser) is nested inside the
Elastic Distributions of OpenTelemetry (EDOT)group, making it hard to navigate and giving EDOT a very long, flat list.After: A new
EDOT SDKsgroup sits at the same level as Fleet, APM, Beats, etc., with theedot-sdks/index.mdpage as its root and each SDK as a direct child.Rationale
The SDKs are a distinct product surface from the EDOT observability tooling (Collector, Cloud Forwarder, etc.) — grouping them separately makes each easier to discover, especially for developers who come in looking for a specific language SDK.
Note
This is a proposal on top of #2927 — open to discussion on naming, ordering, and whether the EDOT core group should also have its own index page trimmed.
🤖 Generated with Claude Code