Managing Storyline File Versions

Defines version control practices for Storyline files during development and final handover.

Core Protocols

1. Centralized Storage
   • Maintain the most up-to-date Storyline file in Dropbox at all times
2. Final Version Labeling
   • Before handover:
   • Rename the Storyline file to include “FINAL” (e.g., CourseName_FINAL.story)
   • Store it in the development folder

Naming Conventions (Optional but Recommended)

Iterative Development

• Use incremental version labels for draft files:
  • [ProjectName]_v0.9.story (Initial draft)
  • [ProjectName]_v1.0.story (First review-ready version)
  • [ProjectName]_v1.1.story (Post-feedback update)

Rules

• Avoid ambiguous terms like “latest” or “new”
• Never use special characters (e.g., #, &)

Validation Checklist

• Confirm final Storyline file is in both:
  • Dropbox (active project folder)
  • Development folder (labeled “FINAL”)
• Verify no conflicting versions exist in local drives