I’ve started building some fairly involved stories and I’m realizing I have no safety net if something breaks or I accidentally overwrite something important. Is there a way to version control Tines stories or at least keep reliable backups? Curious what workflows others have put in place for this.
Tines actually has built-in versioning for stories! You can create new versions, name and rename versions, clone versions to new stories, or export the JSON of any version. You can also view older versions and see any changes between the live story and the version you are viewing.
Integration with a version control system like Git is pretty seamless too. You can export your Tines stories (as JSON) via API on a schedule and commit them to a repository. Then you essentially have your full version history stored in GitHub. Check out this story in the library that does just that!
Tines also has pretty extensive change management capabilities, if that is something your team is interested in - you can learn more from Tines University, our Docs, and Tines Explained.