Roadmap
What is available today, what is being worked on, and what comes later. Priorities are shaped by real usage and community feedback.
Built-in editor with side-by-side Markdown preview and a formatting toolbar.
Pages are organized in a folder-like tree. Structure is explicit and user-controlled.
Fast, built-in search across all page titles and content. No external service required.
Upload images and files directly. Drag & drop and paste from clipboard are supported.
Render diagrams from Mermaid code blocks inside Markdown.
Info, warning, success, and error callout blocks in Markdown.
See which pages link to the current page.
Separate admin, editor, and viewer roles. Secure defaults out of the box.
Share documentation publicly while keeping editing and administration behind login.
Import existing Markdown files and folder structures from a ZIP package. Linked pages, local assets, and Obsidian-style wiki links can be migrated together.
Customize the wiki's visual identity from the admin settings.
Provide a custom CSS file to override or extend the default styles.
Full dark mode support across the UI.
Usable on mobile devices for reading and editing.
Shortcuts for editing, saving, search, and navigation.
Deploy with a single Go binary or Docker container. SQLite is built in, so there is no external database to manage.
Organize pages into collapsible sections in the navigation tree.
Detects conflicting saves so small teams do not silently overwrite each other while editing the same page.
Per-page history and restore flow are available behind the `--enable-revision` feature flag.
Internal links can be rewritten when pages are renamed or moved. Available behind the `--enable-link-refactor` feature flag.
Deploy behind a subpath such as `/wiki` using `--base-path`.
Add lightweight structure for classification and filtering without pushing LeafWiki toward a database-heavy workspace model.
UI translations for languages beyond English. Contribution-driven.
Additional capabilities will stay focused on long-lived docs, self-hosted use, and small-team knowledge bases rather than enterprise workflow engines.
Priorities are shaped by real usage. Open an issue on GitHub if you have a specific need or use case.
Have a specific need or use case? Open an issue on GitHub →