In Kanorio, Drafts are the working versions that you and your team are modifying in the background, while the Live Version is what visitors actually see when they open your public URL.
Think of a draft like a new menu being tested in a kitchen: as you type, swap images, or adjust layouts, the system automatically saves your draft and keeps a 30-day version history. Visitors will never see your work-in-progress. Only when you have verified your changes and clicked "Publish" in the top right corner will your public website be updated.
| Action | Saving and Publishing |
|---|---|
| Edit existing modules, headers, or footers | The central preview updates in real-time. Changes are automatically saved to draft after a brief pause in typing (the top-right corner shows "Saving... → Saved"). Even if you close the panel or lose connection, unsent changes will be automatically synced upon reconnection. |
| Drag to reorder, change layout, hide, duplicate, or delete modules | Changes are immediately written to draft (an "Undo" prompt appears at the bottom of the screen after hiding or changing layouts). |
| Select a "New Module" from the directory | The preview will show the effect first. When you are ready to keep it, click "Add to Website" at the bottom of the panel to write it to the draft. Once added, subsequent edits are automatically saved. |
| Change site-wide settings in the "Design" or "Brand" panels | The top-left of the preview will show "Preview contains unsaved changes." Click "Save" at the bottom of the panel to write to the draft (Note: Business Contact Info and Back to Top button will update the live website immediately upon saving). |
| Write blog posts or edit single-page SEO settings | Changes are automatically saved after a brief pause in typing (Single-page SEO updates live search results immediately after saving on a published page; blog posts require clicking "Publish" in the top-right corner of the post editor). |
Kanorio includes two layers of protection in both the "Website Editor" and the "Blog Post Editor":
| Scenario | Feature | Location and Shortcuts | Retention |
|---|---|---|---|
| Typo, accidental module deletion, or wrong layout change | Undo / Redo | The ↶ ↷ buttons on the left of the top toolbar and top-right of the module panel (Keyboard: ⌘Z / Ctrl+Z, ⇧⌘Z) | During the current editor session (up to 50 steps; cleared upon page refresh) |
| Restore a version from hours, yesterday, or last week | Version History | "Version History" on the left of the top toolbar (on mobile, tap "More › Version History" at the bottom) | Shared across devices and teams. All plans retain history for 30 days (the latest "Published" version is kept permanently) |
↶ Undo repeatedly to go back.The system automatically saves versions at four key moments: every 10 minutes during editing, every time you click "Publish", before major AI modifications (Pre-AI Backup), and before performing a version restore (Pre-Restore Backup). Each version is labeled with the name of the team member or AI key that made the change.
When there are unpublished draft changes on your site or in a post, an orange dot will appear next to the name on the left side of the top toolbar, and the button in the top right will display "Publish Updates".
| What you modified | How to make changes live for visitors? |
|---|---|
| Website pages, modules, headers, footers, design, and share buttons | After verifying the mobile preview in the editor, click "Publish" in the top-right corner to sync the entire site draft to the live website (see for the initial launch process). |
| Blog posts | Blog posts are completely independent of website pages (publishing or restoring the site in the website editor will not affect blog posts). Please open the post in and click "Publish" or "Update" in the top-right corner of the post editor. |
Please ensure the URL is correct and open it in your browser's "Incognito/Private Window" (or perform a hard refresh) to rule out browser cache issues.
Because "Publish" pushes the entire site's current draft live, when collaborating or using the AI Assistant (MCP), we recommend checking the "Version History" before publishing to ensure you aren't accidentally publishing a colleague's work-in-progress. If you need to download a full JSON backup and raw assets ZIP before a major update, please use Website Backup.