Version Control
The Canvelete (opens in a new tab) Design Editor includes comprehensive version control features that help you track changes, collaborate safely, and maintain a complete history of your design evolution. This system ensures you never lose work and can always return to previous versions.
Understanding Version Control
What is Design Versioning?
Version control in Canvelete tracks every significant change to your design:
- Automatic Snapshots: System creates versions at key moments
- Manual Saves: Create named versions at important milestones
- Change Tracking: Monitor what changed between versions
- Rollback Capability: Restore any previous version instantly
Version Types
The system maintains different types of versions:
- Auto-saves: Frequent automatic backups (every 30 seconds)
- Manual Versions: User-created snapshots with descriptions
- Milestone Versions: Major design phases or approvals
- Branch Versions: Alternative design directions
Version Manager Interface
Accessing Version Control
The Version Manager is available through multiple entry points:
- Header Menu: Click the version/history icon in the top bar
- Keyboard Shortcut: Ctrl+Shift+H to open version history
- Right-click Menu: Access from canvas context menu
- Auto-save Indicator: Click the save status to see recent versions
Version History Panel
The history panel displays:
- Version Timeline: Chronological list of all versions
- Version Thumbnails: Visual previews of each version
- Version Names: Descriptive titles for manual versions
- Timestamps: When each version was created
- Author Information: Who created each version (in collaborative projects)
- Change Descriptions: What modifications were made
Version Details
Each version entry shows:
- Version Number: Unique identifier (v1.0, v1.1, etc.)
- Creation Date: Exact timestamp of version creation
- File Size: Storage space used by this version
- Element Count: Number of design elements in this version
- Changelog: Summary of changes from previous version
Creating Versions
Manual Version Creation
Save important design states manually:
Save Version Dialog
- Open Save Dialog: Click "Save Version" button
- Version Name: Enter descriptive name (e.g., "Final Logo Design")
- Description: Add detailed notes about changes
- Tags: Add searchable tags for organization
- Visibility: Set version as public or private
Version Naming Best Practices
v1.0_Initial_Concept
v1.1_Client_Feedback_Applied
v2.0_Color_Scheme_Updated
v2.1_Typography_Refined
v3.0_Final_ApprovedAutomatic Versioning
The system creates versions automatically:
- Time-based: Every 5 minutes during active editing
- Action-based: After significant changes (adding/removing elements)
- Session-based: When opening/closing the editor
- Collaboration-based: When team members make changes
Version Triggers
Automatic versions are created when:
- Major Edits: Adding or removing multiple elements
- Style Changes: Significant color or typography modifications
- Layout Changes: Moving or resizing multiple elements
- Import Operations: Adding new assets or images
- Export Actions: Before generating final outputs
Version Navigation
Browsing History
Navigate through your design history:
- Timeline View: Scroll through chronological versions
- Grid View: See multiple version thumbnails at once
- List View: Detailed text-based version list
- Search Versions: Find specific versions by name or date
Version Comparison
Compare different versions side-by-side:
- Visual Diff: Highlight differences between versions
- Element Changes: Show added, removed, or modified elements
- Property Changes: Display style and positioning changes
- Overlay Mode: Superimpose versions to see differences
Version Preview
Preview versions without restoring:
- Thumbnail Preview: Quick visual overview
- Full Preview: Open version in read-only mode
- Zoom and Pan: Examine version details closely
- Element Inspection: View properties of elements in old versions
Restoring Versions
Version Restoration Process
Restore any previous version of your design:
- Select Version: Choose the version to restore from history
- Preview Changes: Review what will change in current design
- Confirm Restoration: Confirm you want to restore this version
- Automatic Backup: System creates backup of current state
- Apply Changes: Design reverts to selected version
Restoration Options
Choose how to restore versions:
- Full Restore: Replace entire design with selected version
- Selective Restore: Restore only specific elements or properties
- Merge Restore: Combine elements from multiple versions
- Branch Restore: Create new branch from old version
Restoration Safety
Built-in protections prevent data loss:
- Current State Backup: Always backup current design before restoring
- Confirmation Dialogs: Multiple confirmations for major changes
- Undo Support: Restoration can be undone immediately
- Recovery Mode: Recover from failed restorations
Branching and Merging
Design Branches
Create alternative design directions:
- Branch Creation: Start new design direction from any version
- Branch Naming: Give descriptive names to branches
- Branch Switching: Move between different design directions
- Branch Comparison: Compare different design approaches
Branch Management
Organize multiple design directions:
- Main Branch: Primary design development line
- Feature Branches: Specific design experiments
- Client Branches: Different versions for different clients
- Archive Branches: Store old or unused design directions
Merging Branches
Combine work from different branches:
- Merge Conflicts: Handle conflicting changes between branches
- Selective Merge: Choose specific elements to merge
- Merge Preview: See results before applying merge
- Merge History: Track all merge operations
Collaboration and Versions
Team Version Control
Coordinate version control across team members:
- Shared History: All team members see complete version history
- Author Tracking: Know who created each version
- Concurrent Editing: Handle simultaneous edits safely
- Version Conflicts: Resolve conflicts when multiple people edit
Permission Management
Control who can create and restore versions:
- Version Creation Rights: Who can save manual versions
- Restoration Permissions: Who can restore old versions
- Branch Management: Who can create and merge branches
- History Access: Control access to version history
Collaborative Workflows
Establish team version control practices:
- Review Cycles: Use versions for design review stages
- Approval Process: Mark versions as approved or rejected
- Feedback Integration: Link comments to specific versions
- Release Management: Tag versions for different release stages
Version Storage and Limits
Storage Management
Understand how versions are stored:
- Storage Quota: Available space for version history
- Compression: How versions are compressed to save space
- Cleanup Policies: Automatic removal of old versions
- Archive Options: Long-term storage for important versions
Version Limits
System limits for version control:
- Maximum Versions: Total number of versions per design
- History Depth: How far back history is maintained
- File Size Limits: Maximum size for individual versions
- Retention Periods: How long versions are kept
Optimization Tips
Manage version storage efficiently:
- Regular Cleanup: Remove unnecessary versions periodically
- Meaningful Names: Use descriptive names for important versions
- Archive Old Versions: Move old versions to archive storage
- Compress Large Designs: Optimize designs before saving versions
Advanced Version Features
Version Analytics
Track design evolution over time:
- Change Metrics: Measure how much designs change over time
- Activity Patterns: See when most changes occur
- Collaboration Stats: Track team member contributions
- Version Performance: Monitor version creation and restoration speed
Integration Features
Connect version control with other tools:
- Export Versions: Download specific versions as files
- API Access: Programmatic access to version history
- Webhook Notifications: Get notified of version changes
- External Backup: Sync versions to external storage
Version Automation
Automate version control tasks:
- Scheduled Versions: Create versions on schedule
- Trigger-based Versions: Versions based on specific actions
- Batch Operations: Perform operations on multiple versions
- Automated Cleanup: Remove old versions automatically
Best Practices
Version Control Workflow
Establish effective version control practices:
- Start with v1.0: Begin each project with initial version
- Regular Saves: Create versions at logical stopping points
- Descriptive Names: Use clear, descriptive version names
- Document Changes: Add detailed descriptions to versions
- Test Before Restore: Always preview before restoring versions
Naming Conventions
Use consistent version naming:
Major.Minor.Patch_Description
1.0.0_Initial_Design
1.1.0_Client_Feedback
1.1.1_Typography_Fix
2.0.0_Complete_RedesignCollaboration Guidelines
- Communicate Changes: Notify team of major version changes
- Review Before Restore: Get approval before restoring old versions
- Use Branches: Create branches for experimental changes
- Regular Syncing: Keep local versions synchronized with team
This comprehensive version control system ensures your design work is always protected, trackable, and recoverable, enabling confident experimentation and seamless collaboration.
Next Steps
- Learn about Collaboration for team workflows
- Explore Layer Management for organizing designs
- Check out the API Reference for programmatic version access
- Start versioning at canvelete.com/dashboard (opens in a new tab)