Brand theme sweep before a rebrand ships

The brand owner does this once, before the switch. Palette and type are about to change. You want to see every existing artboard in the next brand before anyone commits that change into .lerret/. The current look has to stay the default until you decide.

This is a preview, not a commit. You need the whole library in the next theme, in one folder, before the switch. If the next palette fails on a long headline, you want that in the preview, not after the brand is live.

The job is a full export of the project under the next theme. Source artboards stay as they are. Data stays as it is. --config brand-next.json swaps palette and type vars for the run only. You review the complete PNG set, then keep or drop the config file.

Give Lerret a React component under .lerret/ and optional data. export writes a PNG. Same component, data swapped, many images. There is no batch product, no queue, no orchestrator.

The component is every artboard in the project. There isn’t one file to name. A rebrand touches the vars those artboards already read, so the sweep is the whole library in one run. You don’t rewrite each component to preview the next look. If it’s an artboard in the project, it’s in the sweep.

Data is unchanged. This is bulk pattern 4: --config to swap theme vars without touching the source. brand-next.json applies to every artboard in the run. --config is never written back into .lerret/, so a preview can’t become the committed brand by accident. That’s the point of the flag here. The default brand stays the default.

The image is a complete PNG set under --out lerret-export/rebrand-preview. Same artboards, same dimensions they already have, new vars. You look at the folder as one set: every asset, one theme, one place.

You use Lerret because you see the entire asset library in the new brand before committing anything. Because --config is never written back, the current brand is untouched. Opening a design file and restyling frames by hand is the thing this run replaces. The preview folder is throwaway until you decide the next brand is ready.

npx @lerret/cli@latest export --config brand-next.json --out lerret-export/rebrand-preview

Start a project with npx create-lerret@latest. More in the use cases index.