Themes without application-code replacement

Theme administration

Open Admin → Themes. Each card presents a full-width preview, identity, semantic version, scope, compatibility, palette, and available actions.

Install a ZIP package

1. Acquire a trusted archive. Use EKR Marketplace or a package from a publisher you have independently verified.
2. Select the ZIP. Audoryx enforces the upload size and rejects nested executables or unexpected paths.
3. Verify and install. Manifest schema, identifier, version, scope, compatibility, assets, and hashes are checked before extraction.
4. Review the preview. Confirm landing, login, creator, administrative, responsive, RTL, maintenance, 404, and 500 surfaces as applicable.
5. Apply deliberately. Switch only after the validation checklist passes.

Per-theme content

Landing and presentation content is theme-scoped. In Admin → Brand & content, select the theme before editing its hero, sections, authentication copy, cards, media, maintenance page, or error-page content. Switching themes does not overwrite another theme's content.

• Use a separate landing screenshot and preview metadata for each theme.
• Use an actual image or video only after upload succeeds and the license inventory is complete.
• Keep essential meaning in text, not only in decorative imagery.
• Verify English and an RTL language at desktop and narrow viewport sizes.

Theme-aware fallback covers

ElevenLabs Music and Google Lyria creations that have no generated artwork use the active theme's default music cover: a theme-consistent gradient and music-note mark. Suno-compatible results retain provider-generated artwork when present. The fallback can appear as soon as the audio becomes safely streamable and preserves the image blur transition.

Theme manifest v3

A package is declarative. It may provide scoped CSS, referenced assets, design tokens, page-level style overrides, and approved component-style overrides. It must not replace Laravel, React, route, controller, migration, executable JavaScript, or vendor files.

{
  "schema_version": 3,
  "id": "publisher-theme",
  "name": "Publisher Theme",
  "version": "1.0.0",
  "author": "Publisher",
  "scope": "dashboard_and_frontend",
  "compatibility": {
    "audoryx": ">=1.0.0 <2.0.0"
  },
  "styles": ["assets/theme.css"],
  "assets": {
    "preview": "assets/preview.webp"
  },
  "tokens": {}
}

Use the authoritative JSON Schema and the included package example. The engineering rules and token inventory are preserved in the theme technical guide.

Package rules

• The identifier is stable, lowercase, namespaced where appropriate, and matches updates.
• The version uses semantic versioning and increases for every released archive.
• Every path is relative, normalized, within the package, and explicitly declared.
• CSS selectors remain under the Audoryx theme root and do not leak into admin or third-party surfaces unintentionally.
• Preview, fonts, icons, photos, and videos are recorded in the asset-license inventory.
• The package contains no credentials, generated caches, source maps with private paths, or executable backend code.

Theme QA matrix