Use Cases
What LeafWiki is well-suited for today, and where a different tool would serve you better.
Good fit
Technical notes, how-to guides, reference documentation you write for yourself. You control the structure, the content stays on your server, and nothing requires a subscription or an account on someone else's platform. The explicit tree structure keeps a growing knowledge base organized without things drifting into a flat list of undiscoverable notes.
Incident runbooks, deployment procedures, architecture notes, onboarding documentation. LeafWiki provides structure and fast search without the setup overhead of a larger platform. Keyboard shortcuts and fast full-text search make it practical to use during incidents or when you need to find something quickly.
Write and edit internally while making content readable to anyone โ no login required for visitors if public access is enabled. Works well for open-source project documentation, homelab notes, or technical guides you want to share without giving write access.
If you already write in Markdown and want to publish it in an organized, searchable format โ without converting it to a database or a static site generator setup โ LeafWiki handles that with minimal configuration.
Not a good fit
LeafWiki does not support real-time collaborative editing. It uses optimistic locking for concurrent edits, which works well for small teams but is not designed for many people editing the same page at once.
LeafWiki is not an approval workflow, document control system, or a replacement for enterprise wiki platforms with complex permission models. If those are requirements, a different tool is the right choice.
See the roadmap for what is planned next.