Use case or problem
“Subscribe” to another vault in a chosen folder inside the current local vault.
Only the contents of the external vault are downloaded, the “.obsidian” folder is excluded.
This would allow easier vault nesting.
Usage examples
- Have one separate vault for your phone and desktop (phone vault being lighter).
- Subscribe to public vaults, like libraries or collections.
- Subscribe to a shared wiki/knowledge base of your work team:
- You can link shared work notes in your PKM vault, no need to copy/paste.
Handling changes
- Local changes are visibly marked.
- Changes on the root external vault are synced
- Conflicts can be solved by leaving the edited version as a copy.
- The owner of the root vault decides who can subscribe and who can “push” their changes like a pull request.
- Ex: only team members can subscribe to a work knowledge base, and only a subgroup can edit the root files.
Proposed solution
Same current logic of Sync, just nested instead of vault wide.
Maybe free users can subscribe to external vaults without permissions for local edit.
Current workaround (optional)
Could be implemented with git.
Haven’t implemented it because of the effort it would take to set it up on automatic updates.