Manifesto / statement poster

A founder or a team does this occasionally. The statement is long-form type, set as a poster. The words will get revised. The poster should follow the words.

This is revision work on a type-heavy poster. Copy revisions are the worst case in a design tool and the easiest case here. You edit an array. You run export. You do not place each sentence by hand after a rewrite.

The job is to typeset { lines: [] } as a poster and re-export when a line changes. The poster is a derived file.

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/brand/manifesto.jsx. It is a long-form statement typeset as a poster. The lines are the statement. The component does the type. A revision is a change to the array, not a redraw of every line on the board.

Data is { lines: [] }, the statement as an array, easy to revise. Pass it with --data. A revision is an edit to an element, or an insert, or a delete. Re-export. The poster is a derived file. The array is easy to revise because each line is one item.

The image is a PNG at poster dimensions. The size is the poster size the artboard already declares. Lerret writes the image. Print is outside this case.

You use Lerret because copy revisions on a type-heavy poster are the worst case in a design tool and the easiest case here. The statement is an array. The poster is the component. A find-and-replace on a line is a text edit, not a redraw. A design file you dread opening puts you back in the worst case.

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/. Copy revisions on a type-heavy poster are the worst case in a design tool and the easiest case here.

npx @lerret/cli@latest export --data

Pass the { lines: [] } file when the statement changes. 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 statement lives as { lines: [] }, easy to revise. The list is stills from local files.

Copy revisions on a type-heavy poster are the worst case in a design tool and the easiest case here. That is the inventory reason. The PNG is at poster dimensions. The artboard already has the size.