Commands
Every command takes --target-org <alias> (or -o <alias>), except validate, which works offline.
Export: pull templates out of an org
Section titled “Export: pull templates out of an org”# Everything in the org
sf sliick docs export --target-org staging --all --out templates/
# A specific list of templates
sf sliick docs export --target-org staging --templates Invoice,Quote --out templates/
# A whole bundle (member templates are included by default)
sf sliick docs export --target-org staging --bundles "Onboarding Pack" --out templates/
# Skip image files for a fast, text-only diff
sf sliick docs export --target-org staging --all --no-files --out templates/
The export writes one file, sliick-export.sdt, into the --out folder (default: the current folder). Watermarks and image blocks of any size are included, unless you pass --no-files.
Import: push a .sdt into the target org
Section titled “Import: push a .sdt into the target org”# Single artefact
sf sliick docs import templates/invoice.sdt --target-org prod
# A directory of artefacts, processed in lexical order, one transaction per file
sf sliick docs import templates/ --target-org prod
# Dry run: see what would change, write nothing
sf sliick docs import templates/invoice.sdt --target-org prod --dry-run
# CI mode: fail the build on any warning
sf sliick docs import templates/ --target-org prod --fail-on-warnings
# Import and publish in one step
sf sliick docs import templates/invoice.sdt --target-org prod --auto-publish
The defaults suit CI:
--match-by external-idmatches templates by External Id, so anInvoicefrom staging updates the sameInvoicein prod even though the record Ids differ.--on-conflict updateupdates the existing template’s draft. Published versions are never overwritten.
Imported templates land as drafts for an admin to publish in-org. Pass --auto-publish to publish them automatically.
Auto-publish is all or nothing. If any template in the file fails validation in the target org (for example, a merge field points to a field that does not exist there), the whole import rolls back. Nothing is imported and nothing is published, so it is safe to use in CI.
Diff: preview the changes before you run them
Section titled “Diff: preview the changes before you run them”sf sliick docs diff templates/invoice.sdt --target-org prod
The output marks each template and bundle as CREATE, UPDATE or SKIP. Run it during release review, or post it as a pull-request comment so reviewers see the changes before they approve.
Validate: check the artefact without an org
Section titled “Validate: check the artefact without an org”sf sliick docs validate templates/invoice.sdt
Validate runs offline. It checks the file structure, the schema of the metadata files, and the integrity of any embedded image references. It is fast, so run it first in CI, before diff or import.
template list: query an org live
Section titled “template list: query an org live”sf sliick docs template list --target-org prod
sf sliick docs template list --target-org prod --json
The list shows each template’s External Id, its active (published) version, its latest draft version, and whether it has an unpublished draft. Use --json in scripts.