Recover a draft
Undo and Redo cover recent changes in the current session. In History, use Search versions and Version type to find a snapshot, then Previous and Next to browse results. Choose Restore and wait for the selected version to load. Review Added, Changed and Removed items; expand them to compare Current draft with Selected version before choosing Restore as draft. The live website stays unchanged; preview the restored draft before publishing. Restoring a project snapshot can replace unrelated recent edits. If loading fails, use Try again; a failed restoration keeps its confirmation open so you can retry or cancel.
If a save fails, keep the editor open and correct the error or retry. Unsaved changes may be lost when the tab closes. A conflict means someone saved a newer version. Download your changes before refreshing, then reconcile them with the current draft; simultaneous edits are not automatically merged.
Administrators can download a project export for recovery. Keep exports safe. Changing content storage must preserve drafts, publication and revision history; do not maintain independent file and database copies.
What is available
- Cloud manages accounts, project access, Studio, CMS, private preview and managed publication. A separate website repository or SDK setup is not required.
- Flat files are the default content storage; PostgreSQL is optional. Hosting shows the price for that website’s storage choice. Storage cannot change while hosting or payment setup is active.
- Hosting and Website address show whether payments and domain connections are available. A pending connection or an account plan label does not confirm that a website is live.
- External SvelteKit SDK integration and independent hosting remain future capabilities. Existing SDK files are not a completed production connection.
- Cloud renders trusted, deployed components. Uploading arbitrary Svelte source does not install or execute it in Cloud.