Skip to content

docs(canvas): canvases are files in the vault, not encrypted blobs - #982

Merged
h4yfans merged 1 commit into
mainfrom
docs/canvas-file-backed-saving
Aug 6, 2026
Merged

docs(canvas): canvases are files in the vault, not encrypted blobs#982
h4yfans merged 1 commit into
mainfrom
docs/canvas-file-backed-saving

Conversation

@h4yfans

@h4yfans h4yfans commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

What

  • Canvas overview no longer claims "Canvases are not files on disk" — each board is a plain .excalidraw file in <vault>/canvases/, and a file dropped in there is adopted on the next vault open.
  • Corrected the reason the engine's Open / Save to... actions are hidden: the vault is the only store, not the absence of a file.
  • Stopped implying image export is gone — saveAsImage was never disabled, so Export image... is still in the menu.
  • Shape library is a plain library.excalidrawlib, not "stored encrypted" (two places).

Why

The user guide still described the pre-#946 model. Verified against canvas/scene-file.ts, canvas/reconcile.ts, canvas/library-file.ts, and the UIOptions in canvas-editor.tsx.

The user guide still described the pre-#946 model: "Canvases are not files
on disk", and the shape library as stored encrypted. Both are stale.

- Canvases are plain `.excalidraw` files in `<vault>/canvases/`, adopted on
  the next vault open when dropped in by hand.
- The hidden Open / "Save to..." actions are hidden because the vault is the
  only store, not because no file exists. "Export image..." was never
  disabled, so stop implying it is gone.
- The shape library is a plain `library.excalidrawlib`, not encrypted.
@h4yfans
h4yfans marked this pull request as ready for review August 6, 2026 21:57
@h4yfans
h4yfans merged commit fd7d668 into main Aug 6, 2026
0 of 2 checks passed
h4yfans added a commit that referenced this pull request Aug 7, 2026
The push run for 083ad3a was left unrecoverable by the 2026-08-06 Actions
incident (stuck queued, zero jobs, refuses both cancel and re-run), and the
E2E jobs only run on a push to main, so neither workflow_dispatch nor the
docs-only #982 could reach them. Empty commit, no tree change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant