The promotion model
The plugin follows one flow:
Author in staging org -> Export -> Commit .sdt to git -> CI imports to prod
The unit of promotion
Section titled “The unit of promotion”You promote a .sdt file (a Sliick Docs Template archive). It carries:
- Template metadata: name, configuration, editor state.
- Bundle membership.
- Image files: watermark and image-block assets, at any size.
- Optionally, version history, with
--include-history.
How a .sdt is reviewed
Section titled “How a .sdt is reviewed”Commit .sdt files to git alongside your Apex and LWC. The file is not human-readable, so review the template by proofing it in the org before export. To see what an import will change, run diff.
What does not travel this way
Section titled “What does not travel this way”The plugin moves templates and bundles only. Themes and org-wide settings (Docs_Theme__mdt, Docs_Setting__mdt) are custom metadata, so keep moving them by Change Set or sf project deploy.