A wiki is only useful if you reach for it without thinking. If opening it requires effort, you write things down somewhere else. If finding something is uncertain, you stop trusting it. The tool disappears into the background, and the knowledge disappears with it.
LeafWiki is built around the assumption that daily use matters more than feature count.
The editing loop
Opening a page, making a change, and saving it should take seconds. In LeafWiki, the keyboard shortcut flow is:
Ctrl+E— enter edit mode from anywhereCtrl+S— save without leaving the editorCtrl+Alt+P— open the page switcher and jump somewhere elseCtrl+Shift+F— search across all content
That covers the majority of what you do in a wiki. None of these require a mouse.
Paste images directly
The most common friction point in documentation tools is images. You take a screenshot, then you have to open a file picker, upload it, copy a URL, and paste it into the Markdown. That sequence is enough to make you skip the image entirely.
In LeafWiki, you take a screenshot and paste it directly into the editor with Ctrl+V. The image is uploaded immediately and the Markdown link is inserted. That is it.
The same applies to dragging images from your desktop or file manager into the editor.
Live preview
The editor shows rendered Markdown side by side as you type. Tables, Mermaid diagrams, callout blocks, and code blocks render in real time. There is no save-and-reload loop. You see what you are writing as you write it.
This matters most with Mermaid diagrams. You write a flowchart or sequence diagram in a fenced code block, and the preview shows the rendered diagram immediately. No context switch to a separate tool, no copy-paste back.
Structure you can navigate
LeafWiki uses an explicit tree. Pages live in sections, sections live in other sections. The structure is always visible in the sidebar, and it is entirely under your control.
This sounds simple, but it has a practical consequence: as a wiki grows, you can still find things. There is no flat list of hundreds of pages with unclear relationships. You develop a spatial memory of where things are, the same way you know where files live in a project directory.
The quick page switcher (Ctrl+Alt+P) lets you jump directly to any page by typing part of its name. For pages you visit often, it is faster than clicking through the tree.
Backlinks
Every page shows which other pages link to it. For runbooks and reference documentation, this turns out to be more useful than it sounds. You add a link somewhere, and later you can find all the places that depend on or reference a piece of documentation — without maintaining that list manually.
What this rules out
LeafWiki is optimized for the single-writer or low-concurrency team case. There is no real-time collaborative editing. Instead, LeafWiki uses optimistic locking to help prevent silent overwrites when two people edit the same page. For most personal wikis and small team wikis, this is a good fit. For teams that need simultaneous editing on shared pages, it is not the right tool.
The tradeoff is intentional. A simpler concurrency model means a simpler data layer, which means Markdown files on disk, which means your content is always readable and portable outside of LeafWiki.
If you want to see the editing flow in practice, the live demo is the fastest way. No account required.