Hi @redimp,
First of all, thank you for the amazing work on Otter Wiki — the clean UI, git-backed storage, and extended Markdown support (wikilinks, mermaid, fancy blocks) make it one of the best lightweight wiki solutions out there.
I'd like to propose adding a static export / read-only mode that allows publishing an Otter Wiki to platforms like GitHub Pages (or any static hosting) with zero backend requirements.
Use Case
Otter Wiki already excels at keeping a clean, pure-Markdown document library under git version control. For users who value this simplicity, there is a natural next step: sharing those documents publicly — whether as a knowledge base, a personal blog, or a project wiki — without the overhead of running a Python server.
In my search, I haven't found another tool that combines Otter Wiki's clean git-native Markdown editing with a dead-simple static publishing option. Most alternatives force you into heavy SSG frameworks or sacrifice the wiki-like browsing experience.
Scope (Deliberately Narrow)
This request is intentionally limited to a read-only, auth-less subset:
| Keep |
Drop |
| Rendered Markdown pages |
Login / auth / user management |
| Wikilink resolution |
Edit / preview / save |
| Sidebar / page index |
SQLite database features |
| Mermaid / code highlighting |
History / blame / diff |
| Attachments / images |
Admin panel |
| Basic search |
Git push/pull web server |
The goal is not to turn Otter Wiki into a full static-site generator, but to offer a zero-backend "publish" mode for readers.
Willing to Help
I'm happy to help test, provide feedback, or contribute if this aligns with the project's direction.
Would love to hear your thoughts on whether this fits the roadmap.
Thanks for considering!
Hi @redimp,
First of all, thank you for the amazing work on Otter Wiki — the clean UI, git-backed storage, and extended Markdown support (wikilinks, mermaid, fancy blocks) make it one of the best lightweight wiki solutions out there.
I'd like to propose adding a static export / read-only mode that allows publishing an Otter Wiki to platforms like GitHub Pages (or any static hosting) with zero backend requirements.
Use Case
Otter Wiki already excels at keeping a clean, pure-Markdown document library under git version control. For users who value this simplicity, there is a natural next step: sharing those documents publicly — whether as a knowledge base, a personal blog, or a project wiki — without the overhead of running a Python server.
In my search, I haven't found another tool that combines Otter Wiki's clean git-native Markdown editing with a dead-simple static publishing option. Most alternatives force you into heavy SSG frameworks or sacrifice the wiki-like browsing experience.
Scope (Deliberately Narrow)
This request is intentionally limited to a read-only, auth-less subset:
The goal is not to turn Otter Wiki into a full static-site generator, but to offer a zero-backend "publish" mode for readers.
Willing to Help
I'm happy to help test, provide feedback, or contribute if this aligns with the project's direction.
Would love to hear your thoughts on whether this fits the roadmap.
Thanks for considering!