Obsidian as a documentation editor

Use case or problem

I have alot of case-specific information stored in alot of respective locations, and i mainly use Markdown. As i understand, Vaults allow to limit indexing features to a manageable folder, and contain user data (workspace and etc).

Obsidian appears to have the best existing WYSIWYG editor, and some of its other features, like Canvases, are great, plus extensibility on top of that. But currently, it simply can’t be used across user content. If one wants to describe a single large topic, they can use Obsidian, but if there are from hundreds up to hundreds of thousands of topics, its unusable.

Lets say its possible that one would blacklist ./.obsidian/ in SCM and synchronization apps, though potentially that is a huge effort which should be removed by Obsidian allowing to use OS-user-wide storage for these workspace files. Then, there needs to be “Open with Obsidian” context menu item for folders in Windows Explorer and such, and ability to open files directly from the file managers. Because of user setups of the file manager context menus and that other apps are also contribute to them.

Proposed solution

  1. Add setting which will make Obsidian: use OS-user-wide storage instead of local .obsidian folders, unless such folder already exists and path from it to opened file/folder, is shorter or equal than from the closest corresponding location recorded in the user storage.
  2. Add “Open with Obsidian” to OS context menu for folders.
  3. Have Obsidian be the handler of .md files / Add ability to use Obsidian as a markdown editor on files outside vault (file association) - #7 by Joschua

There also needs to be ability to propagate some settings across Vaults/Workspaces, like the one to show name of file as a heading . I wish i could use Obsidian, but currently the app is completely impractical .

Also, when folder with markdown files which link to each other is opened, Obsidian doesn’t handle/load the links and creates new files when the links are followed .

This happens when the links use // separator.