Code Files Assets tree with Has Changes and Save Changes
Virtual disk vs live

Appifio Creator · Lesson T01 · Glossary

Virtual disk
what it is

One idea - why visitors still see the old site after AI or Inspector “finished,” and why Discard can wipe an entire working session.

Goals: Tell the virtual disk (session draft) apart from the live site; read the unpublished-draft signal correctly; know when work “vanishes.”

Time: 10-12 minutes · Before: A03 · Next: T02

UI labels: Current · Changes · Save changes · Discard · Unpublished draft · Reload

1. Two storage layers

[You / AI / Inspector]
↓ write into
VIRTUAL DISK (temp session) ← preview via: "Changes"
↓ only when you click "Save changes"
LIVE SITE ← preview via: "Current" · visitors hit the public URL
"Discard" = drop the virtual disk and return to the last published files

2. Glossary

TermMeaningWhere you see it
Virtual diskTemporary working copy of all HTML/CSS/JS/assets in this Creator sessionHidden in the system; surfaced via Changes
Live sitePublished files - what visitors seeCurrent · public URL
Unpublished draftBadge: virtual disk differs from liveTop toolbar
Unpublished draft linkShareable preview of the virtual disk without opening CreatorTab menu / preview link

3. Observe it in the UI

  1. Open Creator → tab dropdown → View & edit.
  2. Ask the AI to change one line of text (prompt box → Send) or edit with Inspector.
  3. Watch the Unpublished draft badge appear; Save changes and Discard show up.
  4. Click Changes - see the new draft. Click Current - see the old live site.
  5. Open the public URL in a private window → still Current until you Save changes.
  6. Try Discard on a throwaway session (after Clone on the Versions tab) to feel it: the virtual disk is dropped and preview returns to live.

4. How it works

Creator does not write straight to the live server on every AI reply. Edits land on the virtual disk first. Aura Storage JSON also has its own draft/session layer in some contexts, but for HTML/CSS/JS you see the pair Current / Changes. Save changes = publish to the live site (may bump FS revision). Reload only refreshes the iframe - it does not publish. The Versions tab shows rev N / N rev behind / Unsaved; when Site online, use Sync from site to pull live into the session (not a substitute for Save).

5. Comparisons

  • Webflow: Designer vs Published - same draft/live idea.
  • WordPress: Draft vs Publish - close, but WP drafts a post in the DB; Creator drafts the whole file tree.
  • Lovable / v0: often apply straight into a sandbox; Appifio keeps a clear preview toggle plus Save changes.

6. Can / can’t

You can: edit freely on the draft; compare both views; share an unpublished draft link; Discard the whole draft.
You can’t: expect visitors to see the draft (unless you share the draft link); unlimited Undo after Discard; automatic Git commit on Save.

7. Security

An Unpublished draft link exposes content that is not public yet - share only with people you trust. Secrets on the draft can still be read if you share that link.

8. Common issues

SituationFix
“AI already fixed it but visitors don’t see it”You haven’t Save changes; or you’re viewing Current by mistake
Everything gone after DiscardBy design; next time Checkpoint / Create new (Clone) first
Preview looks wrongReload; confirm you’re on Changes

9. Tips

  • Before a large edit: Clone a version → then ask the AI.
  • Always compare Changes vs Current before Save.
  • Don’t Discard when you’re tired - close the tab to keep the session if you’re unsure.

10. Checklist

  1. Can you explain why visitors don’t see the AI’s latest edit yet?
  2. Do you know Discard clears the virtual disk - not “undo one line”?

Next

T02 - appifio_client and bootstrap inject

Internal navigation (same language)

Appifio Creator · User guide · T01