Designs
Artwork, fields, variables and version history.
A design is artwork plus the positions of the things that change.
Artwork
PDF, PNG or JPEG. A PDF becomes the page itself and keeps its own size and vector detail; a raster image cannot be a page, so it is drawn full-bleed onto a page whose size you state.
The page is measured, never assumed. Every field is positioned in millimetres from the top-left of that page, so a design whose stored page disagrees with its artwork prints every field in the wrong place — and does not complain, because nothing has gone wrong as far as the renderer is concerned.
Fields
Add, duplicate, remove and restyle fields. A text field can hold {variables}, which are filled in
at issue time.
Shrink-to-fit matters more than it sounds. A recipient's name is the one value whose length nobody controls: a six-character name and a twenty-eight-character name cannot share a fixed size, and without auto-scaling the long one runs off the certificate.
Variables
A field may only use a placeholder its design declares. That is a hard rule, not a convenience: there is one list of what a design asks for, and issuing, bulk upload and validation all read it.
Binding a custom attribute copies its definition onto the design rather than pointing at it, which is what makes archiving an attribute safe — an existing design goes on asking for exactly what it asked for yesterday.
Versions
Saving a change creates a version, and a credential records which version printed it. The page size is frozen too, so restoring an old version prints at the size it was printed at rather than at today's.
Nothing ever edits a version in place. That is what lets a continuing-education provider reissue an identical certificate six years later.
Badges
A badge is a design like any other, in the same millimetre geometry, authored with shapes and text. It is delivered as a PNG rather than a PDF, and that PNG carries its own credential inside the file — see Open Badges.