Business card artwork

Anyone does this on a new hire or a rebrand. You need print artwork: name, title, contact lines, logo. Twelve people means twelve cards that should still be regenerable years later, from the repo, not from a design file on someone’s departed laptop.

This is print artwork that has to outlive the person who made the first file. A new hire is one more file. A rebrand is the same files against the updated component.

The job is one component and one data file per person. Twelve files, twelve runs.

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 .lerret/brand/business-card.jsx, as in the acme preset. It shows the name, title, contact lines, and logo. Those slots are the card. The preset is how you get the artboard. The path is what you export.

Data is one data file per person. That’s bulk pattern 1: re-run export with a different --data file. Same component, new person, new image. The file is text, so a wrong title is a one-line diff. You don’t re-layout a card because someone changed teams.

The image is a PNG at print size and resolution. The size is the print size the artboard already uses. Lerret writes the artwork. Sending it to a printer is outside this.

You use Lerret because twelve people, twelve files, and one component keep the print artwork regenerable years later. It’s code in git. The person is data. The card is the component. A rebrand re-exports the same files. A design file per person, or a screenshot of a styled HTML card, will not be there years later.

Name, title, contact lines, and logo are the card, as in the acme preset. One data file per person. Twelve people is twelve --data runs. Years later the artwork is still regenerable because the component is in git.

npx @lerret/cli@latest export --data

Pass one person file per run. Start a project with npx create-lerret@latest. More in the use cases index.