Kaleta 2.16.0

Kaleta 2.16 keeps shared design in one place: your fleet console. Every other site receives it as drafts, never pushed live.

Shared design kit

On the fleet console (Fleet → Shared kit), choose what the kit holds:

• the design system (tokens);
• all classes or selected ones;
• selected components;
• selected saved sections.

Then publish a new kit version. The history shows which version each site has applied.

On every member site that switches it on (Settings → Fleet console → Receive the shared design kit, off by default), the next heartbeat brings the new version:

• tokens and classes go into the draft look, which you review and publish with Publish look;
• components get a new draft, so their published build and their properties stay until you publish;
• saved sections go into the section library.

The settings tab shows the version received and links to what is waiting for review.

Safe by design

• Sites still only call the console, never the other way round. A kit is fetched by the site, signed by the console, and checked against the console's key and the announced hash before anything is applied. A tampered kit is refused and recorded as an event.
• Everything is cleaned as if it were saved locally. A kit carries no custom code and no custom HTML elements, and custom font files stay on the console.
• Claude sees the applied kit in site_info, and on the console the kit version of each site in list_sites.

Smaller changes

• In the German admin, the Requests section is now called Aufträge, because Anfragen already means enquiries.

Updating

Update from Settings → Backups and updates. It works from every earlier release. The update adds:

• a table for kit versions on the console;
• a kit key on components and saved sections.