Editing and recovery
Rigel keeps editing, Save and Publish separate. The preview reflects your current draft. Browser recovery can help after an interruption, while GitHub history lets you inspect earlier saved content.
Keyboard shortcuts
Use Cmd on macOS and Ctrl on Windows or Linux.
| Action | Shortcut |
|---|---|
| Search content | Cmd/Ctrl + K |
| Save | Cmd/Ctrl + S |
| Switch Browse and Edit | Cmd/Ctrl + Shift + E |
| Toggle navigation sidebar | Cmd/Ctrl + B |
| Toggle properties panel | Cmd/Ctrl + Shift + Y |
| Open keyboard shortcuts | Cmd/Ctrl + / |
| Close a dialog, menu or search | Escape |
Search and Save also work inside the prepared preview. Save uses the same validation, connection and busy-state checks as the button. Layout shortcuts are ignored while a text input or rich-text block has focus, so the usual bold shortcut still works in an article. Shortcuts are fixed rather than user-remappable.
Recover an unsaved draft
The editor backs up dirty page, article, document and menu drafts in browser localStorage on the editor’s origin. Reopen the editor after an interruption and use the recovery offer for the matching entry. Recovery changes the in-memory draft; it does not save content files or publish. Unsaved new entries can also have recovery records.
GitHub recovery is scoped to the verified account, repository, workspace branch and content configuration. Local mode uses the project’s recovery scope; demo mode has no recovery. A schema or configuration change can make an older backup ineligible. Recovery records are limited to 1 MiB each. Browser storage can be unavailable, full or cleared, so a backup is not guaranteed and is not a substitute for Save.
If the saved content has changed since the backup, review the recovery warning before replacing your draft. Existing conflict checks still apply when saving. Signing out or changing accounts clears recovery data; Clear File Cache does not. Erase All Data removes browser recovery as well as the editor’s other managed browser data. Copy important unsaved work before signing out or clearing storage.
Inspect GitHub history
For an existing page, article, schema document or menu in GitHub mode, open History beside Save. Select a commit to inspect its saved values and article text. The history preview is data-only; historical templates and scripts do not execute.
Restore to editor replaces the active draft after confirmation when it is dirty. Save writes the restored content as a new change; publishing remains separate. Restoration does not reset the current conflict snapshot or rewrite Git history.
History loads on demand from the loaded workspace head, in pages of 20 commits up to 200. Renamed file paths can have separate history. Missing files or revisions incompatible with the current schema cannot be restored. Local and demo modes do not expose GitHub history.
See GitHub publishing for the repository workflow and Media for upload progress, usage checks and deletion protection.