Roadmap

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 metadata directly to pages using frontmatter. Browse and filter by tags in a dedicated UI.

Automatic table of contents for longer pages. Makes technical documentation and reference pages easier to navigate.

Render mathematical notation directly in pages using KaTeX.

Find and replace text inside the editor without leaving the page.

Authenticate users through a trusted HTTP header set by a reverse proxy — Authentik, Authelia, Keycloak, or nginx basic auth. Available via `--enable-http-remote-user`.

Link pages by title using [[Title]] syntax. The editor offers autocomplete and ambiguous titles open a disambiguation dialog.

Pages save automatically while you type. Conflict detection prevents overwriting concurrent changes. With --enable-revision, edits from the same session are grouped into a single revision.

Secure accounts with time-based one-time passwords. Required for teams where IT security policies apply.

Pin important pages so they appear at the top of the navigation for everyone — not just the user who pinned them.

Paste content from Word, OneNote, and similar tools directly into the editor. Basic structure like headings and lists is preserved as Markdown.

Mark pages as favorites for quick access. Personal to each user — no shared state.

Ongoing improvements to the editor, navigation, and general interaction quality based on real usage and feedback.

Push page content to a Git repository automatically — keeping documentation in sync with version control without manual exports.

Filter and browse pages by their frontmatter properties. Focused on a minimal, practical interface — not a database query builder.

Guides for common operational tasks — backup and restore procedures, upgrade paths, reverse proxy setups, and migration scenarios.

Password reset and user invitations via email. Configurable SMTP — no external mail service required.

Create new pages from predefined templates — incident reports, meeting notes, runbooks. Templates are stored as regular pages.

Save a page as a draft before publishing. Drafts are visible to editors but not to viewers or public access.

Sections can display an auto-generated overview page listing all child pages — sortable by title, last modified, or creation date. Useful for larger documentation sets.

UI translations for languages beyond English. Contribution-driven.

A documented HTTP API for reading and writing wiki content. Useful for integrations, scripts, and automation.

Back up or mirror wiki content to an S3-compatible bucket for offsite storage or archival.

Get notified when a page you follow is updated. Delivery via email or webhook.

Sign in with an identity provider directly — GitHub, Google, or a corporate IdP. Proxy authentication covers many setups already; native SSO is for teams that need it without a reverse proxy.

An overview of broken internal and external links across the wiki. Helps keep large documentation sets clean over time.

A chronological feed of recent changes across the wiki — which pages were created, edited, or deleted, and by whom. Useful for staying on top of a shared knowledge base.

Embed and edit draw.io or Excalidraw diagrams directly inside pages. Diagrams are stored as files alongside the page content.

Page-level comments for feedback and async discussion. Scoped to editors — not a public forum.

Reusable content blocks embedded directly in pages — for example a page list filtered by tag, rendered inline. A lightweight alternative to database views.

Embed an image gallery block in a page. Useful for hardware documentation, visual guides, or any content that needs multiple images presented together.

Priorities are shaped by real usage. Open an issue on GitHub if you have a specific need or use case.