Platform constraints
These are not style choices — they are the preconditions for running inside atomm.
| Constraint | Requirement |
|---|---|
| Export goes through the platform button | Place <div data-atomm-export-button></div> where you want it and register atomm.lifecycle.on('export', …). The SDK renders the button, and only its --atomm-export-* variables can be themed.A submission with no registered export hook is rejected automatically during review.During development you may render a fallback button in the same slot, but the SDK must always take precedence when present |
| Treat the export as machine-facing | 1:1 physical size, mm units, and a viewBox in width="200mm" coordinates. Cut-line colour may be mapped to a machine operation by the device, so changing it needs its own sign-off and does not ride along with the interface ramp. Reference imagery used for preview never enters the cut file |
| The top bar belongs to the platform | Branding, account, credits. Don't rebuild it and don't imitate it. Your generator's own controls (project, save, history) go in a light bar above your own content area |
| You are inside someone else's container | You cannot cover the platform chrome, you do not know the viewport size, and your stacking context is entirely your own — one overlay layer plus one toast layer is enough, so z-index cap at 3 |