Prerequisites

Sliick Docs templates are data, not metadata. They live as Template__c rows inside the managed package, which means a Change Set or sf project deploy will not move them between orgs.

The @sliick/sfdx-plugin closes that gap. It is a thin sf CLI plugin over the template portability surface in the managed package, and it gives you the same promotion model you already use for Apex and LWC: author in a staging org, export to a portable .sdt artefact, commit to git, and let CI import to production. Templates get the process you already run for code: a branch, a pull request, a diff, an automated import and an audit log.

These pages are a developer reference. If you only need to move one template between two orgs by hand, use the in-org Export and import modal instead.

Before you install

• Salesforce CLI sf v2 or later. Run sf --version to check.
• Node.js 18 or later. The plugin is published as a standard oclif package.
• Sliick Docs 1.6.0 or later installed in every org you intend to target. The plugin checks the package version at runtime and refuses to run against older installs.
• The user that authenticates to each org must have the Sliick_Docs_Admin permission set assigned. The same permission set gates the in-org Export and Import modal, so most Sliick Docs admins already have it.