NNexusDocumentation
Live demo
GuideDeploy & Maintain

Nexus UI CSS & CDN Releases

Understand the bundled customer stylesheet and the separate immutable CDN workflow used by the hosted demo.

10 min readDeploy & MaintainUpdated for Nexus 0.1
On this page 5

What you will learn

  • Choose bundled or CDN CSS.
  • Know when to bump the UI version.
  • Publish and verify an authorized UI release.

Customer default

Customer releases use the bundled public/nexus-ui/nexus.css when NEXUS_UI_CSS_URL is empty. This keeps the template self-contained and does not depend on Azora infrastructure.

dotenv
NEXUS_UI_CSS_URL=
NEXUS_UI_CSS_INTEGRITY=

Hosted demo

The hosted demo may load an immutable CDN stylesheet and verify it using Subresource Integrity. The URL and integrity must come from the same generated manifest.

When to publish

Publish a new shared UI version only when app/globals.css or shared UI inputs change. Page-specific app/template.css changes do not require a UI version bump.

  1. Edit the canonical shared source.
  2. Increment nexus-ui.config.json.
  3. Run pnpm ui:release with authorized credentials.
  4. Read the URL and integrity from public/nexus-ui/manifest.json.
  5. Update the hosted demo environment.
  6. Build, restart, and smoke-test the public demo.

Local-only rebuild

Use ui:build when you need to regenerate the bundled file without publishing.

bash
pnpm ui:build
pnpm check

Continue learning