PHASE 3 — WORKING SAFELY · MODULE 9 OF 11
Saving, Publishing & Previewing Changes
By the end of this module you will save deliberately, preview responsibly, and understand that on a published page, saving means live — immediately.
What you’ll learn
- Find where Save lives in the Avada Live toolbar and spot unsaved changes
- Understand that saving a published page makes changes live immediately
- Preview a saved change like a visitor would — including on a phone
- Know that page revisions exist as a safety net GM&F can restore
Watch first
Watch for: the builder toolbar and its preferences — this is the strip where saving lives. (Video: How to Use the Avada Live Builder Preferences, official Avada channel.)
Step-by-step instructions
- Find Save in the Avada Live toolbar. When you have unsaved edits, the builder shows it clearly — get used to glancing there.
- On a published page, Save = live immediately. There is no staging step. That is exactly why Module 8’s one-change-at-a-time ritual exists.
- Preview responsibly: after saving, open the page in a normal browser tab and look at it as a visitor. Then check it on your phone — a surprising number of visitors will only ever see the phone version.
- Revisions are your safety net: WordPress quietly keeps earlier versions of each page. If an edit goes wrong after saving, tell GM&F what changed and roughly when — any previous version can be restored. Nothing is lost forever.
- Drafts exist for new pages; edits to existing pages have no draft mode in this workflow — another reason for small, verified changes.
What you should practice
- Make one small edit, watch the unsaved-changes indicator appear, save, and verify the change in a fresh tab.
- Open the same page on your phone and check it there too.
Common mistakes to avoid
- Leaving the builder without deciding. Save or discard — never close the tab “to decide later” with edits half-made.
- Saving a half-finished thought on a live page. “I’ll fix the rest after lunch” means visitors see lunch-break state.
- Refresh-panic. If the live page shows old content right after saving, it is almost always your browser’s cache — hard refresh first (Ctrl+Shift+R / Cmd+Shift+R).