“We’re at booth N” conference card
Field marketing makes this card per conference. Event name, booth number, dates. Five conferences a year is five data files, not five design files. The files live in git next to the campaign notes.
This is field work. Each conference has a booth number and a date span. The logo slot and the team photo slot stay on the component. What changes is { event, booth, dates }. You should not duplicate last conference’s design file and miss the dates.
The job is one 1200×630 image that says where the team is. You swap the three fields, you export, you post. Next conference, same component, new file. The booth number is a field, so it cannot silently stay last event’s number.
Give Lerret a React component under .lerret/ and optional data. export writes a PNG. Same component, data swapped, next image. There is no batch product, no queue, no orchestrator.
The component is .lerret/social/conference-presence.jsx. It draws the event logo slot, the booth number, the dates, and the team photo slot. One component for every conference on the calendar. The slots are on the component. The event facts are in the data. The path sits under .lerret/social/ with the rest of the social cards.
Data is { event, booth, dates } swapped per conference via --data. That is the first of the four bulk patterns: re-run export with a different --data file. Five conferences a year, five data files that live in git next to the campaign notes. --data applies to every artboard in the run and is never written back into .lerret/.
The image is a PNG at 1200×630. One file, one conference, one export.
You use Lerret because five conferences a year share one component and five data files that live in git next to the campaign notes. A design file per conference will drift the booth type. A screenshot of last year’s booth graphic, with the number painted over, will keep last year’s dates if someone misses them.
npx @lerret/cli@latest export --data
Start a project with npx create-lerret@latest. More in the use cases index.