The most important aspect of portability lies the file format (Obsidian flavoured markdown).
It deviates from standard markdown syntax in several different ways, so that opening file links in other editors is nearly impossible without errors.
Obsidian has a very unique interpretation of Wikilinks AND standard markdown links that differs from any other app. Therefore one can’t just keep using the markdown files in a another editor without running scripts or import processes.
See relevant issues:
- Broken links in relative path mode: Broken links in relative path mode on move/rename - #34 by fluidform
- Add settings to control link resulution: Add settings to control link resolution mode
- relative-path-mode-pathmode broken: In relative path mode (path from current file), always add `./` and `../` in front of links
One needs to export the whole vault to use it somewhere else.
A milesstone in development is the community plugin “better markdown links”. This brought me to Obsidian. Obsidian broke quite a few links of mine before, I must add, when I tried Obsidian initially.
I use 4 different editors at the same time: Obsidian with QOwnNotes, and Micro-Editor and ocasionally VS-Codium.
QOwnNotes allows to change from Obsidian flavour to Github flavoured markdown in the most important aspects `[link](file.md#link-to-heading` vs. `[link](file.md#link%20to%20heading)`) which allows to directly use pandoc and github linking to headings (otherwise you can’t link to headings).
Compatibilitywise:
- Plugin “better markdown links” (make Obsidian use standard markdown notation)
- no embeds
- no wikilinks,
- no block referencess
- editing in other editors must not break plugin behaviour
Pluginwise most things have come up in this forum:
- does it actually improve productivity?
- Do not overlink things, set smart links and set them dilligently
- Does it insert code commands that can not be read otherwise?