Publish
Save the current builder document and compiled output back to the dashboard record once the edit is ready to become the new saved version.
Publishing is the moment where Template Studio moves from draft editing into a saved dashboard record.
That is why publish should be treated as an intentional handoff step, not just a routine click.
What publish does
When you publish, Template Studio compiles the current document and saves:
- the current builder document
- the generated output used by the record
That means publish is what turns the current work-in-progress into the saved version that other users or workflows will rely on.
Errors versus warnings
Template Studio distinguishes between warnings and errors during validation:
- errors block publish until they are fixed
- warnings still matter, but they do not automatically stop every publish
If publish is unavailable, the current document still has validation blockers that need attention.
How to unblock publish
When publish is blocked:
- open Preview to inspect diagnostics
- use the Layers panel warning and error filters to narrow down the affected blocks
- fix the blocking issues, then re-run preview before publishing again
This is usually faster than scanning the entire document manually.
When to publish
Use publish when:
- the record is ready to become the saved version in Leadpush
- validation blockers are resolved
- the mobile preview has been checked
- the current version is ready for teammates or downstream workflows to use
Best practices
- Treat errors as blockers and warnings as review items.
- Publish after meaningful milestones so the saved baseline stays current.
- Recheck preview after fixing validation issues instead of publishing immediately.
- Be especially careful when editing reusable records like layouts, since publish updates the shared baseline for that record.