Skip to content

Prerequisites

Sliick Docs templates are records, not metadata. A Change Set or sf project deploy will not move them between orgs.

The @sliick/sfdx-plugin fills that gap. It adds sf sliick docs commands so you can promote templates the way you promote code: author in a staging org, export to a .sdt file, commit it to git, and let CI import it to production. You get a branch, a pull request, a diff, an automated import and an audit log.

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

  • Salesforce CLI sf v2 or later. Run sf --version to check.
  • Node.js 18 or later.
  • 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. Most Sliick Docs admins already have it, because the in-org Export and Import modal needs it too.