Obsidian-based Wiki Engine

Use case or problem

I have an idea of the new paid service from Obsidian: Obsidian Wiki Engine.

Or maybe just another paid feature for Obsidian Publish.

The idea is to be able to have community editing features, just from the browser with the ability to download the entire vault for local editing, if needed.

I think this product might have a good place in the market, as I didn’t see good markdown-based wiki engines. For example, BookStack supports some subset of markdown but many useful features are missing and maintaining local markdown mirror is not supported.

I would definitely buy such product as I am not satisfied with any of the existing wiki engines available on the market.

Proposed solution

  1. Create new paid service Obsidian Wiki or add another paid feature for Obsidian Publish.
  2. Allow editing markdown from the browser.
  3. Allow download entire vault locally.
  4. Add more advanced security permission model comparing to current Obsidian Publish. We need to be able to allow people to self-register like in usual wiki engines such as MediaWiki, DokuWiki, BookStack etc.
  5. Consider allowing self-hosted solutions.

Current workaround (optional)

The workaround is extremely lame.

Currently I am managing one wiki like that for the Russian-speaking Obsidian community.

In order to be able to accept the changes, I host the vault on GitHub and allow pull requests for the community members to make modifications.

But this is way more technically challenging than the normal wiki experience, that’s why I came here with such request.

Related feature requests (optional)


+1 to this and/or commenting on Publish. I believe a paid solution would sell well.

1 Like