OpenSite/Guides/Manage document files
Use Save, Save As, multiple documents and close prompts without losing track of your work.
- Stable identifier
opensite.help.manage-document-files
Prerequisites
Two small practice documents; do not experiment with the only copy of a project.
Steps
Keep documents and scripts distinct
Engineering documents use .osdoc. Python editor files use .py. Plots are separate view tabs. Saving one does not save all three kinds of work.
Open or activate a document
Use File → Open. Already-open paths are associated with the current workspace rather than meant to become conflicting independent editors. Activate the document in the tree/tab and check its title/path.
Choose Save or Save As
Save writes the active document to its bound path, asking for a location when needed. Save As chooses a new destination. Use a new destination to retain an earlier checkpoint. Keep file copies in a backup location before testing a new build.
Use Save All carefully
Save All processes open engineering documents. Script editors have their own save workflow. Check any dialog/error; do not infer that every file was saved merely because the command was clicked.
Understand close prompts
Save attempts a save before close. A cancelled file dialog or failed save keeps close from completing. Discard closes without retaining unsaved changes. Cancel stops the close. Closing multiple documents can stop when one answer cancels; inspect what remains open.
Plan for recovery
Undo/redo is session history, not a backup and not persisted in the file. Autosave/crash-recovery is not implemented. Save named checkpoints and keep external backups.
Expected result
You know which file each document is bound to and can explain what a close prompt will do.
Limitations
A file already written to disk is not rolled back by a later undo. Saving does not preserve session undo history.
