Files & notes

Scope and prerequisites

These source-based workflows apply to builds with the relevant editor and note-space components. Formal package verification is pending. Preview support varies with the bundled engine and file type.

Edit and save a file

1. Use File → Open File to open your own non-sensitive test copy. Confirm the document path and content type.
2. Make a small edit and save it. Reopen the file and check that the change persists.
3. For Markdown, switch between edit, split and preview where available. Preview does not rewrite the source document.
4. HTML preview is static by default. Running page scripts or JavaScript requires an explicit action; read and trust the sample first.

Organize a note

1. Create a note in a note-space group and enter a short test entry.
2. Wait for and check the saved state. Close and reopen it from the tree to confirm the contents.
3. Use groups to organize notes. Opened Files navigates active editors; it does not mean an external file has been imported.
4. Export a copy to a location outside the note space when needed. The original note keeps its identity.

Recover a note

Delete only the test note you created. Open the recycle bin and restore it; handle a name conflict without overwriting another note. Permanent deletion cannot be undone. Closing an editor does not delete its file.

Common problems

If saving fails, keep the editor open and export a copy before troubleshooting storage. If another window changes the same note, preserve your current version before reloading; changes are not automatically merged. Do not delete active lock files. Office, PDF and HTML previews depend on runtime components, so a missing preview is not proof of a damaged document.