docs(observe): Traces, Spans, Quickstart pages + Release notes nav#698
Merged
Conversation
Add the revamped Observe concept pages (Traces, Spans), the new Quickstart, and a lightened Get started overview, with all internal links repointed to dev's current IA so nothing 404s. Supporting fixes so the pages render correctly: - Register the Mermaid MDX component (vite-docs-transform COMPONENT_MAP) - Move the Steps step-chain CSS and the Mermaid SVG centering into global.css so they survive client-side (FastNav) navigation instead of being dropped with page-scoped <style> tags - Stop the global copy-button from injecting into Mermaid diagrams (it broke the parser on client-side nav) Nav: repoint the Observe Traces/Spans/Quickstart entries to the new pages and add a Release notes section under Get Started.
The Quickstart 'Confirm the trace' step references /images/docs/observe/llm-tracing-overview.webp, which was absent from the repo source (only present as a stale dist/ build artifact). Restore it so the image renders.
commitPirate
approved these changes
Jul 1, 2026
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.
What
Ships the four completed Observe pages to
dev, scoped to only the relevant changes (no nav restructure):Why these aren't a clean cherry-pick
The pages were authored for the new IA (a
traceaitab,observe/concepts,observe/reference,observe/troubleshooting) that isn't ondevyet. To avoid shipping dead links, every internal link was repointed to dev's current paths:observe/concepts/oteltracing/concepts/otelobserve/concepts/traceaitracing/concepts/traceaiobserve/concepts/sessions-and-usersobserve/features/sessiontraceai/manual-instrumentation/set-up-tracingobserve/features/manual-tracing/set-up-tracingtraceai/manual-instrumentation/create-tool-spansobserve/features/manual-tracing/create-tool-spanstraceai/autotracing/autoThree links with no dev equivalent were dropped:
observability-model,reference/span-types,troubleshooting/no-traces-appearing. All remaining internal links resolve on dev.Supporting fixes (needed for the pages to render)
vite-docs-transform(dev had no entry, so<Mermaid>wouldn't import)global.cssso they survive client-side (FastNav) navigation rather than being dropped with page-scoped<style>tagsVerified
dev🤖 Generated with Claude Code