Docs

API & registry reference

Everything in the gallery is consumable programmatically: JSON endpoints per dimension, an open OPF registry, llms.txt discovery, and a prebuilt search index. All endpoints are public, read-only, and require no authentication.

Catalog JSON endpoints

Each live gallery dimension is exposed as a static JSON endpoint. Responses use a shared catalog envelope with version, dimension, and items at minimum, plus dimension-specific supporting data (best practices, categories, legacy aliases).

Dimension	Endpoint	Items
Layouts	GET /api/layouts.json	470
Color Schemes	GET /api/color-schemes.json	14
Font Schemes	GET /api/font-schemes.json	89
Backgrounds	GET /api/backgrounds.json	6
Narratives	GET /api/narratives.json	10
Charts	GET /api/charts.json	76
Themes	GET /api/themes.json	4
Audiences	GET /api/audiences.json	14
Tones	GET /api/tones.json	7
Languages	GET /api/languages.json	93
Socials	GET /api/socials.json	10
Headers & Footers	GET /api/headers-footers.json	10
Content Blocks	GET /api/blocks.json	32
Image Treatments	GET /api/image-treatments.json	15

Envelope shape

{
  "version": "1.0",
  "dimension": "color-schemes",
  "items": [ ... ],
  "name": "Color Schemes",
  "description": "...",
  "routes": {
    "web": "https://www.pptx.gallery/colors",
    "api": "https://www.pptx.gallery/api/color-schemes.json"
  },
  "opfSchema": {
    "name": "design.colors.scheme",
    "url": "https://pptx.dev/schema/opf/v1#/$defs/ColorScheme/properties/scheme"
  }
}

Legacy aliases redirect with HTTP 308: /api/colors.json → /api/color-schemes.json, /api/typography.json → /api/font-schemes.json, and /api/social-platforms.json → /api/socials.json.

OPF registry

The registry is the delivery contract for OPF design choices — the shadcn-style mechanism that CLIs and agents read to inject OPF into a deck. The canonical index lives at /registry.json; each item has a descriptor at /registry/{category}/{slug}.json.

Index shape

{
  "$schema": "https://pptx.dev/schema/registry.schema.json",
  "opf_version": "1.0",
  "items": [
    {
      "name": "hero-split",
      "type": "registry:layout",
      "registry_url": "https://www.pptx.gallery/registry/layouts/hero-split.json",
      "dependencies": [],
      "opf_version": "1.0"
    }
  ]
}

Registry categories

layouts — registry:layout (470 descriptors)
color-schemes — registry:color-scheme (14 descriptors)
font-schemes — registry:font-scheme (89 descriptors)
backgrounds — registry:background (6 descriptors)
narratives — registry:narrative (10 descriptors)
charts — registry:chart (76 descriptors)
themes — registry:theme (4 descriptors)

Descriptor fields

Field	Meaning
name	Stable item name; matches the gallery slug.
type	Registry item type, e.g. registry:layout or registry:color-scheme.
registry_url	Canonical URL of this descriptor.
slug / category	Route slug and registry category.
description	Human-readable summary of the design choice.
web_url	The browsable gallery page for the item.
opf	Copyable OPF snippet(s) — the same JSON shown on the gallery page.
copy_targets	Pre-rendered copy payloads (e.g. raw OPF JSON) with content types.
metadata	Dimension-specific metadata such as tags, categories, or source info.
dependencies	Slugs of other registry items this item references.
opf_version	Catalog API version the descriptor was generated against.

The registry format is open: third parties can publish their own registry.json (e.g. a brand-team OPF registry) using the same schema, and downstream tools can consume it interchangeably. Breaking changes to the format require a version bump and a migration path.

Discovery endpoints

/llms.txt — full machine-readable catalog index for LLMs and AI agents: every dimension, item, JSON endpoint, and registry descriptor.
/sitemap.xml — every catalog page and how-to article.
/api/search-index.json — prebuilt search index over all gallery items, dimensions, and articles (title, href, group, description, keywords). The same index powers the site’s ⌘K search.

The stable-slug contract

Every gallery item has a stable, human-readable slug (e.g. color-scheme/corporate-trust) that OPF documents reference by name. Renaming a slug is a breaking change across the ecosystem.
Detail pages follow /{dimension}/{slug}; legacy routes (/colors, /typography) remain for SEO continuity.
Responses are static and cacheable; endpoints send Cache-Control headers and are safe to fetch at build or generation time.
No authentication, no rate limiting, no accounts. The catalog is a public good.