Markdown Shortcuts for Daily Editing

Shortcuts matter because long files punish friction

A long draft turns small delays into real interruptions. If every save, view change, tab switch, or jump back to a section needs a mouse trip, the file feels harder than the writing itself.

Shortcuts are not there to look advanced. They are there to keep the document moving while your attention stays on the text, the table, or the section you are revising.

- `Ctrl/Cmd + S` saves the file
- `Ctrl/Cmd + W` closes the current tab
- `Ctrl/Cmd + 1` switches to writing
- `Ctrl/Cmd + 2` switches to split view
- `Ctrl/Cmd + 3` switches to preview

Keep the common combinations predictable

The desktop app should follow the normal platform habit: Ctrl on Windows and Linux, Cmd on macOS. That is more useful than inventing a custom scheme for every action.

A writer should be able to save, close, switch views, and move between open files without first remembering which app they are in. Predictable keys make the app feel native instead of framed.

The same workflow should work on every platform:

1. Save the draft
2. Switch to split view
3. Check the preview
4. Return to writing
5. Close the tab when done

Marks help when a document has more than one important place

Long notes rarely have one place you need to return to. You may want one mark near the main idea, one near a table or example, and one near the paragraph you are still fixing.

That is why VeloWrite supports several quick mark slots per tab. One mark is easy to forget. A few marks are enough to cover the useful places in a writing session.

The point is not to build a miniature navigation language. The point is to make a return trip cheap when you move away from the current section.

# Draft

## M1
Use this near the opening summary.

## M2
Use this near the table or checklist.

## M3
Use this near the paragraph you are still revising.

Use shortcuts together with tables and images

Tables and images are where long drafts often slow down. A table may need formatting after a paste. An image path may need checking after a move. If the document jumps to a different place while you fix them, the editor has made the work harder than it needed to be.

A good editing flow is simple: set a mark near the section, fix the table or image, then jump back to the mark and continue. That keeps the page readable and reduces the chance of losing the thought you were writing.

| Action | Use it for |
| --- | --- |
| Format tables | Keep comparisons readable |
| Check image paths | Reduce broken previews |
| Jump to marks | Return to the section you were editing |

A daily editing loop that stays fast

Start in write mode, add the rough text, then switch to split view when you want to confirm the result beside the source. If the file is long, set one mark before you move to another section.

If the document has several active areas, use more than one mark slot. One can point to the introduction, one to the table, and one to the last place you were editing. That is enough for most daily work.

The goal is a short loop: write, check, jump back, continue. Anything that makes that loop harder should be treated as friction, not power.

What to keep consistent across the app

Keep shortcut labels visible in menus, keep mark behavior the same in write, split, and preview modes, and keep the active tab isolated so one document does not change another.

That consistency matters more than adding more commands. If the app behaves the same way every time, users will trust the shortcuts and marks enough to use them without thinking.

Continue with VeloWrite

Try the Editor

Read Long Draft Guide