---
version: alpha
name: "Python"
description: "Python’s public system balances language documentation, downloads, community, and learning with a recognizable blue-and-yellow identity. Use a white documentation canvas, Python blue actions, yellow learning accents, and a clear route from first program to reference and ecosystem."
colors:
  bg: "#ffffff"
  surface: "#f3f5f7"
  text: "#444444"
  brand: "#3776ab"
  on-brand: "#ffffff"
  border: "#d9dee3"
  text-soft: "#6d777f"
  border-strong: "#aeb9c1"
  accent-warm: "#ffd343"
  accent-yellow: "#ffd343"
  accent-navy: "#2b5b84"
typography:
  display:
    fontFamily: "Source Sans Pro"
    fontSize: "80px"
    lineHeight: 1.55
    letterSpacing: "-0.03em"
  body:
    fontFamily: "Source Sans Pro"
    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

Python should feel welcoming without becoming childish: white documentation space, reliable blue actions, yellow learning cues, and visible paths for beginners, maintainers, and reference readers. Keep the first program and the deeper ecosystem in one coherent system. 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

Use white for the learning and documentation ground, pale gray for grouped content, Python blue for primary actions and links, charcoal for reading, and yellow for learning, release, or community emphasis with text labels. Use role names consistently: background, surface, text, brand, on-brand, border, text-soft, border-strong, and accent tokens. Preview swatches show the page ground, primary action, and primary reading color. Semantic states need both color and text.

## Typography

Source Sans Pro supports Python’s readable, inclusive register. Use strong display type for getting started and language concepts, regular text for tutorials, and monospace for code, REPL prompts, package names, and version commands. 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 1200px shell with beginner and reference paths visible in the first viewport, a 780px prose column, and a stable documentation rail. On mobile, stack learning routes and keep the download/platform action easy to reach. 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, keep “Get started” and download context visible before secondary community routes. At 1024px, collapse the docs rail. Wrap tutorial prose and keep code in bounded horizontal scroll regions. 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

Use pale surfaces and borders to distinguish tutorials, downloads, and reference. Avoid nested card stacks around code; let code blocks remain directly inspectable. 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 controls, 8px code surfaces, and 12px learning groups. Keep buttons rectangular and approachable; reserve pills for version or audience 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

Use download selectors, beginner routes, code examples, version switchers, documentation search, community cards, and package links. Platform and version states must be labeled; code copy needs a named control. 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 version and platform changes, 200ms for navigation, and 260ms for tutorial step expansion. Reduced motion keeps code and learning state stable. 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.

Expose audience, platform, version, and code state in text. Verify blue actions and yellow accents, label code copy, preserve heading order, and provide text equivalents for illustrated learning concepts. 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 welcoming concrete copy: “Learn Python”, “Download Python”, “Read the tutorial”, “Browse the library”, and “Join the community”. State the audience and next action without assuming prior knowledge. 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.

The default is a light documentation and learning theme. A dark code mode should define code, focus, warning, and link tokens separately while preserving Python blue and yellow roles. 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.

Python sits in the lineage of readable programming languages, community documentation, teaching environments, and package ecosystems. Its public design should make the first step and the long-term reference feel connected. 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 Python public site supplied the white canvas, blue-and-yellow identity, tutorial/download/reference split, and community-oriented language system.

## Do's and Don'ts

**Do**
- Make the first program path visible.
- Show platform and version context.
- Keep code examples copyable.
- Use blue for primary language routes.
- Use yellow as a labeled learning accent.
- Connect tutorials to reference.
- Expose package and community paths.
- Preserve code readability on mobile.

**Don't**
- Do not assume expert knowledge.
- Do not use yellow without a text meaning.
- Do not hide platform downloads.
- Do not clip Python examples.
- Do not separate tutorials from reference context.
- Do not make learning routes icon-only.
- Do not bury release notes.
- Do not turn the language system into generic education SaaS.

### 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 a welcoming programming-language documentation surface with a white canvas, Python blue actions, yellow learning accents, visible beginner and reference routes, copyable code, version/platform context, and community links.

### Iteration Order

First establish beginner, download, and reference paths, then add version/platform and code states, then tune blue/yellow contrast and mobile tutorials. Verify audience labels, copy controls, and code overflow.