Skip to content
Cortex

Theme Manifest

Define a community theme family, display metadata, and safe light and dark stylesheet paths.

1 min readEdit on GitHub

Every community theme needs a root manifest.json. cortex create <name> --theme scaffolds one, and cortex check validates it.

Shape#

json
{	"id": "warm-notes",	"name": "warm-notes",	"displayName": "Warm Notes",	"author": "Your Name",	"authorUrl": "https://example.com",	"version": "0.1.0",	"minAppVersion": "0.1.0",	"colorschemes": {		"light": "light.css",		"dark": "dark.css"	}}
FieldRequiredNotes
idYesTheme install id. Reviewed listings must match this id.
nameYesTheme family slug. Must equal id and match ^[a-z0-9][a-z0-9-]*$.
displayNameYesUser-facing family name.
authorYesDisplayed in theme and reviewed listing surfaces.
authorUrlNoValid URL for the author or organization.
versionYesPlain MAJOR.MINOR.PATCH. Pre-release suffixes break update checks.
minAppVersionNoMinimum Cortex version expected by the theme.
colorschemes.lightYesSafe relative path to the light CSS file.
colorschemes.darkYesSafe relative path to the dark CSS file.

Safe Stylesheet Paths#

Stylesheet paths must be relative to the theme folder. Cortex rejects:

  • Empty paths.
  • Absolute paths.
  • Windows drive-letter paths.
  • Paths containing ...

Good:

json
{ "light": "light.css", "dark": "schemes/dark.css" }

Bad:

json
{ "light": "../light.css", "dark": "/tmp/dark.css" }

Runtime Theme Names#

For a manifest with "name": "warm-notes", Cortex registers:

  • warm-notes-light
  • warm-notes-dark

The active runtime theme is applied to the body as:

html
<body class="theme-warm-notes-light" data-theme-scheme="light">

Write CSS selectors against those runtime body classes.

Search docs

Search Cortex documentation pages and headings.