Versions tab Create New Clean and Create New Clone
Clone before big changes

Appifio Creator · Lesson K02 · Technical

Work safely:
Clone → edit → Diff → Save

A professional checklist before every large change - less risk of accidental Discard, AI breaking layout, or publishing before review.

Learning goals: Master Clone → edit → Diff → preview → Save changes; tell Clone vs Clean apart; don’t confuse Save changes with Routes Save.

Reading time: about 15 minutes

Prerequisites: E01 (Versions), E03 (Current/Changes), H04 (Diff), T10 (Checkpoint).

Previous: K01 - Prompt engineering.

Next: K03 - Responsive Canvas breakpoints.

Main UI labels:

Versions · Create new (Clone) · Create new (Clean) · Refresh Compare changes: · Add (+) · Remove (−) · Apply changes · Close Current · Changes · Unpublished draft · Save changes · Discard

1. Safe pipeline diagram

0. Live site stable → check Site online / rev behind → if stale: Sync from site or Clone fresh
1. Versions tab → Create new (Clone)
2. Edit on the clone (AI / Inspector) - preview Changes
3. AI returns files → Compare changes: → ✓ accept · ✗ reject · Apply changes
4. Compare preview Changes vs Current (Canvas/Mobile)
5. (Optional) Checkpoint on an AI message (T10) · Diff vs site if Site online
6. Badge Unpublished draft → only when OK → Save changes (publish)
Not OK → Discard on the clone / switch back - live stays intact if you haven’t Saved

2. Glossary

TermMeaningWhere in the UI
CloneCopy the current version to experimentVersionsCreate new (Clone)
CleanEmpty version - wipes drafts; dangerous if mistakenCreate new (Clean)
DiffLine compare Add (+) / Remove (−)Compare changes: panel
Save changesPublish draft to livePreview toolbar (≠ Routes Save)
Unpublished draftBadge: draft not published yetNear Save changes
RefreshReload the versions listVersions tab
Site online / Sync from siteOnline = live site + stale warnings. Sync = pull live into the session (does not publish)Link settings · Versions tab

3. Step by step

Toolbar Has Changes Save Changes and Discard
Save vs Discard
  1. Step 1 - Clone: tab dropdown → VersionsCreate new (Clone) → wait → Refresh if the list hasn’t updated.
  2. Step 2 - Confirm version: make sure you’re on the clone (not Clean unless you intentionally start over).
  3. Step 3 - Edit: AI prompt or Inspector on the Changes draft.
  4. Step 4 - Diff required: when AI returns files → open Compare changes: → ✓/✗ per file → Apply changes or Close.
  5. Step 5 - Multi-viewport preview: toolbar Changes → compare Current on Canvas (K03).
  6. Step 6 - Checkpoint (optional): flag an important AI message before risky experiments (T10).
  7. Step 7 - Controlled publish: when badge Unpublished draft and everything looks good → Save changes. Only Discard if you accept losing the draft.

4. Related features

Clone vs Clean - don’t mix them up

Create new (Clone) keeps all current files - safe for experiments. Create new (Clean) starts empty - only for intentional rebuilds. Mistaking Clean = lose the draft you’re working on.

Diff hint ✓/✗

Each AI-proposed file has accept ✓ or reject ✗. You can accept CSS and reject JS - not all-or-nothing.

Save changes ≠ Routes Save

Save changes publishes HTML/CSS/JS to live. The Save button on the Routes tab only saves route config - two independent actions.

5. Compared with other workflows

WorkflowEquivalentCreator note
Git branch + PRClone ≈ branch · Diff ≈ review · Save ≈ mergeNo Git required - visual UI
Webflow stagingDraft vs PublishedChanges/Current + Unpublished draft badge
Edit production directlyNo stagingHigh risk - avoid; use Clone

6. Can / can’t

You can

  • Run large AI experiments on a clone while live stays unchanged
  • Accept part of a Diff, reject the rest
  • Switch back to an older version if the clone goes wrong

Limits

  • Clone isn’t external CI/CD - only inside Creator
  • Save changes has no automatic undo - Clone/Checkpoint first
  • After publish, visitors see it immediately - no default “schedule publish”

7. Security before Save

  • Review Diff for API keys, admin endpoints, or sensitive logging.
  • Test forms/backend on Changes preview before publish - don’t ship auth bugs live.
  • Clone before AI edits Backend/Secrets - avoid publishing the wrong config.

8. Common issues

SituationFix
Edited the main version then DiscardedNext time always Clone first; Checkpoint early (T10)
Saved without reviewing DiffHabit: Diff required before Save changes
Hit Clean by mistake, lost draftSwitch to the previous version in Versions; read labels carefully
Unpublished draft badge but empty previewSelect Changes; reload preview; confirm active version

9. Tips

  • Golden rule: Clone first, Save later - every large AI prompt.
  • Diff is the last gate - don’t click Apply changes before reading Remove (−).
  • Compare Current side-by-side with Changes on mobile before publish.
  • Name/note clone versions when the UI allows - easier with many experiments.

10. Self-check & next

  1. Clone vs Clean - when to use each?
  2. Order: Diff → preview → Save - can you restate it?
  3. Save changes vs Routes Save?
  4. Does live change when you only edit a clone and haven’t Saved?
  5. How do ✓/✗ help when AI edits 3 files but you only want 1?

Next lesson

K03 - Responsive with Canvas breakpoints

After Clone/Diff safety, check layout on Desktop · Tablet · Mobile before Save.

Appifio Creator · User guide · K02