> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Theme Studio

> Design how a passport looks in Theme Studio, using a closed set of colour, typography, spacing and layout tokens published as reusable themes.

Theme Studio is where the visual presentation of a passport is designed. It controls **how** the passport looks, fonts, colour tokens, spacing, and layout, without affecting **what** content the passport carries.

## Token Model

Themes are expressed as a closed set of design tokens (colour, typography, spacing, radius, and elevation) bound to semantic roles. Editors change the tokens; the renderer applies them consistently across every section.

## Boundary Contract

The Theme engine operates on a **pre-assembled presentation payload**. It performs no database joins of its own at render time. This boundary is what allows the same theme to render identically across:

* The in-app passport preview
* The publish-time snapshot rendered into the immutable HTML artifact
* The public consumer resolver

See the unified theme engine ADR for the full contract.

## Default Theme

Each workspace has a default theme assigned during the Setup Wizard. New passports inherit this theme unless overridden at the product or batch level.

## Publishing a Theme

Themes are saved as drafts and published explicitly. Publishing a theme does **not** retroactively alter previously published passports, passports are immutable snapshots and must be re-published to pick up theme changes.

## Related Docs

* [Content Studio](/authoring-studios/content-studio)
* [Advanced Studio](/authoring-studios/advanced-studio-track-b)
* [Themes & Presentation](/passports/themes-presentation)