Teaser card before a reveal

Marketing does this a few days before a launch. The card is an obscured wordmark, a date, and minimal type. The hint gets less vague each day. You re-run once a day.

This is a daily drip. You are not making five separate design files for a five-day drip. Same component, new hint, new PNG. The wordmark stays obscured. The date and the hint are the fields that move.

The job is a daily one-field edit on { date, hint }. Five days is five edits and five runs over one component.

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

The component is .lerret/marketing/teaser.jsx. It shows an obscured wordmark, a date, and minimal type. That is the teaser. Minimal type means the card stays quiet. The hint is the one line that gets less vague.

Data is { date, hint }. The hint gets less vague each day, one re-run per day. Pass the file with --data. Edit the hint. Export again. The date can stay if the launch day did not move. Five days is five edits and five runs over one component. That is bulk pattern 1: re-run export with a different --data file, or the same file after a one-field edit.

The image is a PNG 1200×630. One card per day. Lerret writes the image. Posting the card is outside this case.

You use Lerret because a daily drip is a daily one-field edit, not five separate design files. The cheap version of that campaign is one component and a file you touch each day. Five one-off exports that drift are the expensive version.

That is the first of the four bulk patterns: re-run export with a different --data file each time. Same components, new values, new images. --data applies to every artboard in the run and is never written back into .lerret/. This is the cheapest possible version of a campaign that would otherwise be five separate design files. The card is a still from a local file.

npx @lerret/cli@latest export --data

Pass the { date, hint } file each day. Start a project with npx create-lerret@latest. More in the use cases index.

--data applies to the run and is never written back into .lerret/. The list is stills from local files. A few days before a launch, one re-run per day.

This is the cheapest possible version of a campaign that would otherwise be five separate design files. Obscured wordmark, a date, minimal type. The hint gets less vague each day.