Updates, release notes, and thoughts on LeafWiki development.
v0.13.0 adds German and Spanish UI translations, Git backup and public mode as runtime settings, email password reset and invitations, and editor and print fixes.
v0.12.0 adds full backup and restore, TOTP-based two-factor authentication, drag & drop page reordering, favorites, and a resizable editor.
v0.11.0 adds [[WikiLink]] syntax with autocomplete, auto-save with conflict detection, and broad mobile improvements.
v0.10.0 adds Tags & Properties, Table of Contents, KaTeX support, Proxy Auth, and editor improvements.
v0.9.0 adds revision history, link refactoring, optimistic locking, and permalinks: four features that solve real problems in shared documentation.
A practical look at hosted wiki options for teams that want real Markdown, portable content, and no lock-in.
Confluence is powerful, but most of that power is aimed at large organizations. A look at what small teams actually need instead.
Obsidian Publish is a fair deal, and it can have more than one collaborator now. They just still need the vault synced locally first, not a plain login.
A practical look at LeafWiki as a Wiki.js alternative for small teams.
A practical comparison of DokuWiki and LeafWiki.
Why Obsidian over Git works well for one person and falls apart the moment a second person needs to write something.
Everyone is building the next Notion, Confluence, or Obsidian clone. I built a single Go binary that stores Markdown files on disk. Here’s why.
A self-hosted wiki should preserve knowledge without turning documentation into another production system to babysit.
Not a growth chart. A sequence of individual moments: an issue after a long quiet summer, a stranger’s pull request, a sponsor who never said a word.
How a conversation at a bar turned into an open-source project used by people I’ve never met.