Clyro automatically tracks your changes, but following these best practices will help you manage your theme history effectively.
Understanding Clyro's Version History
Every time you apply an edit, Clyro:
- •Saves the changes to your theme
- •Records the prompt you used
- •Creates a version snapshot
- •Allows you to rollback if needed
Creating Checkpoints
Checkpoints are named snapshots you can create manually. Use them to mark important milestones.
When to Create Checkpoints
- •Before major changes: About to redesign the header? Create a checkpoint first
- •After completing sections: Finished the footer? Checkpoint it
- •Before experimenting: Want to try something risky? Checkpoint first
- •Before theme updates: Updating your Shopify theme? Checkpoint first
How to Create a Checkpoint
- 1.Go to your Clyro dashboard
- 2.Click on "History"
- 3.Click "Create Checkpoint"
- 4.Give it a descriptive name
- 5.Click "Save"
Good checkpoint names:
- •"Header redesign complete - March 15"
- •"Before Black Friday sale changes"
- •"Mobile optimization done"
- •"Safe baseline - ready for experiments"
When to Rollback
Don't be afraid to use rollback. It's there to help you:
- •An edit didn't turn out as expected
- •You made a mistake and want to undo
- •Multiple edits compounded into issues
- •You want to try a different approach
- •Something broke after changes
Rollback Options
- •Rollback last edit: Undoes just the most recent change
- •Rollback to checkpoint: Restores to a named milestone
- •Rollback to specific edit: Goes back to a particular point in history
Important: Rolling back affects your live theme. Consider the impact before rolling back multiple edits at once.
Maintaining a Clean History
Follow these practices to keep your history useful:
Write Clear Prompts
Your prompts become your history log. When you look back:
Hard to understand later:
"Make it blue"
Clear and specific:
"Change header background to navy #1a1a2e"
Group Related Changes
Instead of making three separate edits:
- •Edit 1: "Change button color"
- •Edit 2: "Change button font"
- •Edit 3: "Change button size"
Consider one combined edit:
- •Edit 1: "Update all buttons: green color, bold font, 16px size"
Grouped edits are easier to rollback if needed.
Don't Over-Checkpoint
Create checkpoints for meaningful milestones, not every small change. Too many checkpoints make it hard to find important ones.
Recovery Strategies
If Something Breaks
- 1.Don't panic, your history is preserved
- 2.Identify when the problem started
- 3.Rollback to the last working state
- 4.Re-apply changes more carefully
If You're Not Sure What Changed
- 1.Review your recent edit history
- 2.Look at the prompts for each edit
- 3.Use preview to compare versions
- 4.Identify which edit caused issues
Before Major Store Events
Before sales, launches, or busy periods:
- 1.Create a checkpoint named with the date
- 2.Test all store functionality
- 3.Document what changes were made recently
- 4.Know how to quickly rollback if needed
Pre-sale checklist:
- ☐Created checkpoint: "Before Black Friday 2024"
- ☐Tested checkout flow
- ☐Verified mobile experience
- ☐Confirmed all recent changes are applied
Coordinating with Theme Updates
When your Shopify theme updates:
- 1.Create a checkpoint before updating
- 2.Update your theme in Shopify
- 3.Check if Clyro edits are still intact
- 4.Re-apply any edits that were overwritten
- 5.Use your checkpoint to reference previous changes
Best practice: Keep a written list of your important customizations. If a theme update overwrites something, you'll know exactly what to re-apply.
Was this article helpful?