---
version: alpha
name: "PyPI"
description: "PyPI makes an enormous Python package index navigable through a clean near-white canvas, PyPI blue actions, compact package metadata, and a direct route from search to release details. The extraction should communicate community scale while keeping version, files, license, and project links inspectable."
colors:
  bg: "#fdfdfd"
  surface: "#e8f1f7"
  text: "#464646"
  brand: "#006dad"
  on-brand: "#ffffff"
  border: "#cfdbe3"
  text-soft: "#687985"
  border-strong: "#9fb8c8"
  accent-warm: "#f4c242"
  accent-navy: "#2c3e50"
typography:
  display:
    fontFamily: "Source Sans 3"
    fontSize: "80px"
    lineHeight: 1.55
    letterSpacing: "-0.03em"
  body:
    fontFamily: "Source Sans 3"
    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

PyPI should feel like a calm public index: near-white reading space, blue route markers, package names and release dates in clear hierarchy, and a practical handoff to pip. Keep community breadth visible without overwhelming the package detail task. 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 near-white for the index ground, pale blue for metadata groups, PyPI blue for links and package actions, charcoal for reading, and Python yellow as a small release or ecosystem accent with text. 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 3 keeps package names, release metadata, and long descriptions readable. Use heavier headings for package identity, regular text for descriptions, and monospace for pip commands, version ranges, and file names. 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 1180px index shell with search and package identity at the top, a 760px description column, and a stable release/files rail. On mobile, stack release metadata and preserve file names and commands in bounded regions. 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 package name, latest release, and pip command visible before the long description. At 1024px, collapse secondary project links. Let long file names scroll inside table cells or wrap without causing page overflow. 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 blue surfaces and thin borders for package groups. Keep the file table flat and inspectable; a single raised command panel is enough to show the pip handoff. 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 3px inputs, 6px action buttons, and 8px metadata panels. Keep the index dense and workmanlike; pills are for version or compatibility labels only. 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 package search, release selectors, file tables, project links, pip command blocks, metadata badges, and report controls. File type, Python version, platform, and release status need visible labels. 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 120ms for copy and release selection, 180ms for search, and 220ms for expanding file metadata. Reduced motion leaves selected release and compatibility state immediately visible. 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.

Give file tables real headers, expose Python version and platform compatibility in text, verify blue action contrast, label pip copy controls, and announce search and release changes. 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 index verbs: “Install with pip”, “Choose a release”, “Download a file”, “Read project description”, and “Report a problem”. State compatibility, version, and file consequence explicitly. 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 near-white index theme. A dark package-reader mode needs separate file table, code, focus, and warning tokens while preserving blue links and readable compatibility labels. 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.

PyPI sits between package indexes, release archives, Python tooling, and community-maintained documentation. Its design should let a package consumer verify the artifact before installing it. 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 PyPI public site supplied the near-white canvas, blue identity, package/release index structure, and pip-first discovery workflow.

## Do's and Don'ts

**Do**
- Show package and release identity.
- Keep pip commands copyable.
- Make file compatibility explicit.
- Use blue for package routes.
- Give file tables headers.
- Expose project links and license context.
- Keep release selection stable.
- Preserve long descriptions on mobile.

**Don't**
- Do not hide Python compatibility.
- Do not make file type color-only.
- Do not clip artifact names.
- Do not replace release data with a vague freshness badge.
- Do not put the package index inside a decorative card.
- Do not bury pip installation.
- Do not use blue for every semantic state.
- Do not make reporting paths hard to find.

### 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 calm Python package index with a near-white canvas, PyPI blue routes, clear package and release metadata, compatibility-aware file tables, copyable pip commands, and inspectable project context.

### Iteration Order

First make search, package identity, release, and pip handoff obvious, then build compatibility and file metadata, then tune dense tables for mobile. Verify headers, labels, copy feedback, and long names.