---
version: alpha
name: "OpenTelemetry"
description: "OpenTelemetry turns observability standards into a public system: a calm light documentation mode, a deep dark technical mode, purple-blue identity, and a clear route through signals, collectors, SDKs, and ecosystem integrations. The extraction should make distributed systems concepts approachable without hiding their operational depth."
colors:
  bg: "#ffffff"
  surface: "#f3f4f8"
  text: "#28303d"
  brand: "#4f61ab"
  on-brand: "#ffffff"
  border: "#d9dce5"
  text-soft: "#687080"
  border-strong: "#aeb5c5"
  accent-warm: "#c7a44a"
  accent-teal: "#2b9a8f"
typography:
  display:
    fontFamily: "Inter"
    fontSize: "80px"
    lineHeight: 1.55
    letterSpacing: "-0.03em"
  body:
    fontFamily: "Inter"
    fontSize: "16px"
    lineHeight: 1.55
  mono:
    fontFamily: "SFMono-Regular"
rounded:
  button: "8px"
  card: "12px"
  pill: "9999px"
spacing:
  xs: "0px"
  sm: "4px"
  md: "12px"
  lg: "32px"
  xl: "64px"
---

## Overview

## Overview

OpenTelemetry should feel calm enough for learning and serious enough for production operations. Use the light mode for concept discovery and the dark mode for telemetry, code, and system diagrams. The visual anchor is a clear signal model, not a decorative dashboard. Keep the actual project, package, runtime, or infrastructure subject visible in the first useful viewport. The visual system should help an agent or human move from recognition to a concrete developer task.

**Key Characteristics**
- A visible first action
- Stable technical hierarchy
- Readable version and status metadata
- Inspectable code or configuration
- Responsive documentation structure
- Text equivalents for visual state

## Colors

In light mode, use white, pale lavender-gray, slate text, and purple-blue actions. In dark mode, use charcoal, violet-slate surfaces, bright readable text, and a lighter purple-blue primary. Teal can identify an adjacent signal or healthy state only when labeled. Use role names consistently: light background, light surface, light text, light brand, light border, and their dark-theme equivalents. Preview swatches show the page ground, primary action, and primary reading color. Semantic states need both color and text.

## Typography

Use a neutral system sans for cross-platform documentation. Keep headings sturdy and explanatory, use compact metadata for signal type and SDK language, and use monospace for spans, attributes, exporters, and configuration. Suggested hierarchy: display-hero for the first promise, display-lg for a major concept, h1 for the current task, h2 for grouped content, h3 for examples or cards, body-lg for introductions, body for explanations, body-sm for metadata, label for controls, and caption for timestamps. Keep tracking at zero unless the source evidence requires otherwise.

## Layout

Use a 1240px shell with a signal-oriented hero, a 12-column integration grid, and a 760px reading column for guides. Keep the collector and SDK path adjacent to the concept explanation. On mobile, stack signal tabs and preserve configuration width through bounded scrolling. Prefer full-width bands with constrained inner content over decorative nested cards. Stable grid tracks, fixed control dimensions, and bounded code regions prevent dynamic labels from shifting the page.

At 640px, stack signal and language selectors while keeping “Get started” visible. At 1024px, collapse the integration rail. Preserve trace and configuration content in bounded scroll regions with readable labels. Responsive changes should reflow tasks rather than merely scale the desktop composition. Preserve the subject, first useful action, version context, and state explanation at every breakpoint.

## Elevation & Depth

Light surfaces should use quiet borders; dark surfaces can use a slightly brighter edge for code and telemetry panels. Avoid floating dashboard cards around a diagram that users need to inspect. Elevation should explain interaction or layering. If contrast, spacing, and a border are sufficient, do not add a shadow. Every overlay needs a title, an escape path, and focus restoration.

## Shapes

Use 4px for controls, 8px for code and integration panels, and 12px for a signal group. Avoid excessive pills; use them only for signal type or language tags. A radius should communicate a control or grouped item, not decorate every section. Keep code, tables, and reference content aligned to a predictable baseline.

## Components

Build signal tabs, language selectors, collector configuration blocks, trace cards, integration lists, and a visible docs search. Every signal tab needs a label, selected state, and text explanation; every diagram needs a summary. Treat every control as a stateful system: default, hover, pressed, disabled, and visible keyboard focus. Use familiar icons inside tool buttons, give unfamiliar icons a tooltip, and keep the action consequence beside the control.

Use 150ms for signal switching, 220ms for integration filters, and 280ms for expanding a collector explanation. Do not animate traces continuously; reduced motion leaves the signal path visible and still. Use motion to confirm an action, expose a relationship, or orient the user. Do not use looping motion to manufacture attention, and make the final state available without animation.

Never make signal type or health color-only. Label trace and collector diagrams with text, keep purple-blue contrast verified in both themes, expose the active SDK language, and make code blocks keyboard-scrollable. Use semantic landmarks, one logical heading order, keyboard-operable controls, and text alternatives for diagrams, charts, code state, and status. Do not use color as the only error, progress, rating, health, or selection signal.

Use operational copy: “Instrument a service”, “Choose a signal”, “Configure a collector”, “Export traces”, and “Read the specification”. Define every acronym at first use and state what data moves where. Microcopy should state the object, action, and consequence. Empty states should offer a valid next step, errors should be recoverable, and technical terms should be defined at the point of use.

Light is the learning default and dark is a first-class technical mode. Keep role names stable across both themes, define separate code and focus surfaces, and announce the current theme without changing the meaning of signal colors. Theme tokens must cover background, surface, text, muted text, border, primary action, primary foreground, focus ring, and semantic states. A theme toggle should preserve position and announce the current mode; never invert code or imagery blindly.

OpenTelemetry sits at the intersection of observability dashboards, distributed tracing, instrumentation SDKs, and open standards. Its design should connect an abstract signal model to a concrete service path. The lineage is a design rationale, not a claim that the source site uses every implementation token in this file. The sampled source URL and recorded production observations remain the authority for brand-specific decisions.

The audit evidence records this source observation: The OpenTelemetry public site supplied the light/dark documentation split, purple-blue identity, signal taxonomy, and collector/SDK ecosystem framing.

## Do's and Don'ts

**Do**
- Make signal type explicit.
- Show the service-to-exporter path.
- Keep code and configuration copyable.
- Use purple-blue consistently across themes.
- Give diagrams a text summary.
- Make SDK language selectable.
- Expose specification and getting-started routes.
- Keep integrations comparable.

**Don't**
- Do not animate traces continuously.
- Do not use health color without a label.
- Do not hide collector configuration.
- Do not make signal tabs icon-only.
- Do not flatten the dark technical mode into a color inversion.
- Do not show a dashboard without data context.
- Do not overload the hero with acronyms.
- Do not clip configuration on mobile.

### Quick Color Reference

- Background: use the page ground token.
- Foreground: use the primary reading token.
- Primary: use the brand action token.
- Surface: use the grouped-content token.
- Border: use the quiet structural divider.
- Focus: use a high-contrast visible ring.

### Build Prompt

Create an observability standards surface with light and dark technical modes, purple-blue signal actions, explicit traces/metrics/logs navigation, copyable collector configuration, SDK context, and text summaries for diagrams.

### Iteration Order

First establish the signal model and getting-started path, then add SDK and collector configuration, then tune light/dark surfaces and integration filtering. Test signal labels, focus, and mobile configuration overflow.