Publish and deploy

Publishing and deploying

With your template designed in the editor, the next step is to publish the draft and deploy it to an environment where it can serve real document generation requests.

Publishing a version

A draft version is your work in progress — editable and not yet available for rendering. When you’re satisfied with the content, publish it:

• The draft becomes Published: its layout, theme snapshot, and schema hash are frozen
• The content is now immutable — the same input will always produce the same output
• A new draft can be created for the next round of changes

The deployment matrix

Navigate to the Deployments tab on the template detail page. The deployment matrix shows:

• Rows — One per variant
• Columns — One per environment (e.g., Development, Acceptance, Production)
• Cells — The active version for each variant/environment pair

Select a version in any cell to deploy it immediately — the change takes effect via HTMX with no page reload.

Version comparison

Before deploying, you can compare two versions side by side. The comparison dialog renders both versions with the same data example and displays them as PDFs in a fullscreen view. Access it from the Compare button in the deployment matrix.

The version lifecycle

Versions move through three states:

1. DRAFT — Editable, at most one per variant
2. PUBLISHED — Frozen and immutable, available for deployment
3. ARCHIVED — Read-only, preserved for audit and historical reference

Next steps

Your template is published and deployed. Now let’s generate an actual document from it.