Concepts
A handful of settings show up in many places across the design editor — how a component is positioned, when it is shown or hidden, which style it uses, and the merge-field syntax for dynamic text.
Rather than repeat the same explanation in every component's documentation, those shared concepts are documented once here. The per-component pages reference back to these.
Positioning
Every component's Layout tab controls where it sits. What that tab offers depends on which tab of the design the component lives on: overlays get an absolute Position, content components get a relative Offset. Most also carry a Width.
Visibility & conditions
Every component has a Visibility section in its editor that controls whether — and on which pages — it appears in the rendered PDF. There are several layers, and a component is shown only if all of them allow it.
Applying styles
Wherever a component prints text or renders a table, it doesn't carry its own font or borders — it points at a style defined once on the design's Styles tab. Update the style, and every component using it updates at the same time.
Merge fields & Twig syntax
Anywhere you can type text that ends up on the PDF — Text components, HTML Text components, translation strings, the Details Box, image link URLs, QR code contents — you can include merge fields. These are placeholders that get replaced with real invoice, client, or company data at render time.