Skip to content

Administration

Shared design kit across your sites.

Keep design tokens, classes, components and saved sections on the fleet console and offer each new version to your sites as drafts.

When you run many sites, keep the shared design in one place – your fleet console – and let each site take new versions when you are ready.

On the console

In Fleet → Shared kit choose what the kit holds: the design system, all or selected classes, selected components and saved sections. Publish a new kit version. The history shows which version each site has applied.

On each site

In Settings → Fleet console tick Receive the shared design kit. With the next hourly report the site fetches the new version and puts it into drafts:

  • tokens and classes into the draft look – review it in Site appearance and click Publish look;
  • components get a new draft – their published version stays until you publish;
  • saved sections go into the section library.

Nothing goes live by itself. The site checks the console's signature and the kit's fingerprint and refuses anything changed on the way; a kit never carries custom code.

Still stuck?

Ask on GitHub or write to info@kaletacms.com – the guide gets better with every question.