[Docs] Add Guide For Users Coming From Obsidian

[ShaunaGordon]

Is your feature request related to a problem? Please describe.

I've noticed in the Discord a number of users coming from Obsidian, and a quick search through Issues here show a number of feature requests for parity with it.

Describe the solution you'd like

I think it would be useful to have a page or section that talks about the differences from Obsidian, how to migrate (perhaps with link to tools like what might have been created some time ago in #46 ), and the open feature parity requests.

Describe alternatives you've considered

There's not really alternatives to be had to this, other than to keep revisiting these requests on the Discord server.

Screenshots or Videos

No response

[krishnasvp]

Hey! @ShaunaGordon my name is Krishna, could you please guide me as to how I could contribute to this issue in the best way possible.

[ShaunaGordon]

Hi @krishnasvp !

If you're asking about the technical steps of contributing, I think there's a Contributors file in the repository that should tell you the expectations.

For the documentation itself, I'm thinking a good place to start is going through and collecting a list of Obsidian features that people ask about in the Discord and in the GitHub Issues, then either showing how to do the equivalent in Foam, or link to the existing GitHub Issue.

There's also the migration Issue that might benefit from usage instructions, if it still works or is applicable.

[meymeynard]

Hello. Just a question. It might not be related but, is it possible to use the Foam's VSCode Extension on the Obsidian vault folder?

[riccardoferretti]

I don't use Obsidian myself, but Foam works with a simple directory of markdown files, which in the end is that a Vault is. Unless you are using some specific Obsidian extensions (that is, if you are only using standard md), then I wouldn't expect to see any issue.

[arden13]

Hey I have a related question. I have used *.md files a lot at work, and am now trying to use Foam to organize and make links between them. I have some where links are breaking and I'm not sure why, but it only seems to be for older files. Are there any watchouts (e.g. filename conventions) that might help explain what to clean up?

For example my workspace I have

old_folder_1: {
     my_old_file.md # I put a link to some new file here [[new_file]]
},
new_file.md # generated after clicking

I can go between my_old_file.md and new_file.md all day (presuming I've linked). However if I move new_file.md to a new folder everything breaks.

old_folder_1: {
     my_old_file.md
},
other_old_folder: {
     new_file.md 
}

Now if I click on any of the links between the files, it regenerates a new file in the parent directory

old_folder_1: {
     my_old_file.md
},
other_old_folder: {
     new_file.md 
},
my_old_file.md, # after having clicked link in new_file
new_fild.md # after having clicked link in my_old_file

However with new files I don't seem to get this behavior. I just tried generating two files, moving one to a new folder, and no problems

[riccardoferretti]

Hi @arden13, sounds like a bug related to moving a file. Please open a new issue describing the steps to reproduce it. Thanks!

[arden13]

Will see if I can reproduce it or if that's just one special folder 😅

[arden13]

I was trying to reproduce and it seemed to be related to the wikilink context at the bottom. I suspect it has to do with not saving a file prior to moving it?

Either way it seems to have resolved itself for the time being 🤷