Theme token roles
The semantic roles accepted by the theme token contract.
Released definition#
The semantic roles accepted by the theme token contract. This is a reference snapshot, not a replacement for server validation or capability checks.
{
"bg": "Page background.",
"surface": "Cards and boxes that sit on the page.",
"tint": "Soft background: the in-between tone.",
"dark": "Dark background: navy on one site, off-black on another.",
"accent": "Highlights: links, labels, rules, the active tab.",
"accent-2": "Secondary highlight for small marks only (stars, badges, icons, rules), never text. Defaults to accent.",
"accent-bg": "Background of the accent tone (defaults to accent).",
"heading": "Heading color on light backgrounds.",
"ink": "Body text on light backgrounds.",
"muted": "Secondary text on light backgrounds.",
"line": "Borders and dividers.",
"on-dark": "Headings and strong text on the dark tone.",
"on-dark-muted": "Body text on the dark tone.",
"accent-on-dark": "Highlights on the dark tone.",
"on-accent": "Text on the accent tone.",
"display": "Heading font stack.",
"body": "Body font stack.",
"radius": "Corner rounding for photos, cards and boxes."
}
Use in an integration#
Preserve enum values and stable identifiers exactly. Use visible labels for people and serialized keys for requests. A missing key can invoke a default; it should not be treated as equivalent to every possible empty value. Re-read the installed version’s schema when updating an integration.