Recipe Versions and History

FourFork automatically tracks all changes to recipes, allowing you to view previous versions and understand how a recipe has evolved.

How Versioning Works

• Every time you publish changes to a recipe, a new version is created
• Versions are numbered sequentially (v1.0, v1.1, v1.2, etc.)
• The current published version is what users see
• Previous versions are preserved and can be viewed

Viewing Recipe History

1. Open any recipe you created
2. Click the "Revisions" or "History" button
3. See a list of all versions with timestamps
4. Each version shows what changed:
   • Ingredient modifications
   • Instruction changes
   • Metadata updates (title, description, etc.)

What's Tracked

FourFork tracks changes to:

• Recipe title and description
• Ingredient list (additions, removals, quantity changes)
• Instructions (new steps, edits, reordering)
• Prep time, cook time, rest time
• Servings
• Cuisine, difficulty, dietary tags
• Equipment list
• Images

Version Details

Each version includes:

• Version number (e.g., v1.3)
• Date and time of change
• Summary of what changed
• Complete snapshot of the recipe at that point

Why Versioning Matters

For Recipe Creators

• Track your recipe development over time
• See which version performed best with users
• Revert to previous versions if needed
• Document recipe refinements

For Recipe Users

• Understand recipe evolution
• Reference the exact version you cooked
• See if changes might affect your saved copy
• Trust that recipes improve over time

Shopping Cart Locking

When you add a recipe to your shopping cart:

• The specific version is locked to your cart
• Updates to the recipe don't affect your shopping list
• Ensures ingredient consistency for your planned meal

Calendar Locking

When you schedule a recipe on your meal calendar:

• The current version is saved with that calendar entry
• Future recipe updates don't change your planned meal
• You know exactly what you're planning to cook

Best Practices

• Make meaningful changes before publishing new versions
• Don't create versions for minor typo fixes
• Add notes explaining significant changes
• Test recipe changes before publishing
• Review how changes affect existing users

Version Notes

When editing recipes, you can add notes explaining:

• Why you made the change
• What you're trying to improve
• Testing results
• User feedback you're addressing