Developer Docs
Fork, Version, and Restore
Safe template evolution workflow with forking, immutable version snapshots, and restore practices.
Forking and version restore are the safest way to evolve templates without breaking production output.
Why fork before editing
- Protects active production template behavior
- Allows side-by-side comparison before publish
- Improves rollback safety if a change regresses formatting
Versioning model
Template changes create immutable snapshots that can be listed and restored. This enables auditability and controlled release workflows.
Restore strategy
- Identify last known-good version
- Restore and preview with multiple candidate profiles
- Communicate restore to template users
Team workflow checklist
- Require fork for major structural changes
- Validate restores before broad rollout
- Document intended use-case per version
- Keep template ownership and review responsibilities clear