Nightly design-system contact sheet

A design systems team runs this nightly. The component tiles already exist. The tiles are what change, as library components change. You want a folder you can diff in the morning, so visual drift shows up as a changed PNG.

This is a schedule someone already has. You do not want a new product for it. You want one command, run overnight, writing a flat folder.

The job is a full PNG set of the component tiles, written --flat so everything lands in one folder for easy browsing. Data is unchanged. You are not swapping copy. You are re-rendering the real components.

Give Lerret the tile artboards under .lerret/ and leave the data as it is. export writes PNGs. Same components, new render. There is no batch product, no queue, no orchestrator.

The components are the component tiles from .lerret/design-system/component-tile.jsx: the real library component centered on a labeled tile. One artboard per component under .lerret/design-system/, each with colocated data naming the component and its demo props. That is the same set as the showcase tiles. This case does not add a second library of tiles. The tiles render the real library components. Night to night, the components themselves are what change.

Data is unchanged. You do not pass a new --data file. The components themselves are what change. The colocated files stay put. A nightly run just exports again.

The images are the full PNG set, --flat so everything lands in one folder for easy browsing.

A nightly run turns visual drift into a folder you can diff. One command on a schedule someone already has. You compare last night’s folder to tonight’s. --flat is what puts the whole set in one place.

Point export at the design-system tiles and pass --flat. Data stays as it is. The command writes one folder of PNGs for browsing and for a folder diff. Nothing about the run needs a queue. It is one command on a schedule someone already has.

npx @lerret/cli@latest export --flat

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