Blog

v0.9.0 adds revision history, link refactoring, optimistic locking, and permalinks — four features that solve real problems in shared documentation.

Notion locks your content in. Confluence is too heavy. Wiki.js needs a real database. BookStack needs PHP. None of them hit the middle ground I was looking for.

A wiki is only useful if opening it costs no effort. Here is how LeafWiki handles the daily editing workflow: keyboard-first navigation, Ctrl+V image uploads, and a live Markdown preview.

v0.8 brings two significant additions: a new section type for organizing pages in the tree view, and a built-in Markdown importer for bringing existing documentation into LeafWiki.

LeafWiki is built around a small set of hard constraints: Markdown on disk, no external database, explicit tree structure, self-hosted by design. Here is what those constraints mean in practice.