I like both. What attracts me to Dendron is the enforced structure using schema's. I started my journey with Obsidian and then stumbled across Dendron as a curiosity. Now I am torn between the two. Obsidian is ahead in development in some ways, but there are features in Dendron that I really like - and it is coming along nicely.

Don't worry we won't judge 😉

If anything, the whole point of Markdown as the basis of your notes is so that you can migrate with ease or even use multiple apps together

true, that's why I prefer markdown and local-save note taking apps like Obsidian and Dendron

that's a quite strange combination 😜

@User we share so many discord servers I have to scroll

maybe you should join The Productivists, we discuss everything about productivity and we have an Obsidian channel too

I'll dm you an invite

cool thanks

markdown-based portable note taking is an intimate community 🙂 exciting to see everyone 🌱

@imalightbulb may I have an invite too

sure!

dm me if you guys want an invite 🙂

I would be interested as well @User - I am always looking for new ideas and discussion

This was a super useful note @User - just so I make sure I understand this correctly ... today, there's no possibility of using folders and this weekend vaults will automatically get pulled into separate folders right?

And then we can initialize separate git repos.

So, it wouldn't be wasted work if I organized my notes between 2 different vaults right now right?

> today, there's no possibility of using folders and this weekend vaults will automatically get pulled into separate folders right? uhmm... hard time parsing that sentence 😅 elaborate?

lol fine I'll be clearer. With multi-vaults today, every note is still in the same folder despite being logically in two separate vaults.

So I can't have separate git repos for each vault.

However, you're planning on shipping the feature which puts each vault into separate folders and can thus be initialized with different git repos.

ah

today, with multi-vault, notes are actually in different folders

When that happens, it should be fairly easy to go from the multi-vault structure that we have now (in one folder) and split them out into separate folders.

you can query them as if they were in the same folder but they are actually logically different

oh man, I now see that. So I CAN initialize them with separate repos.

yep

the only difference between the implementation today and in the doc is that the config files are directly inside the

workspaceroot

instead of the

config folder

. the change i'm making is to make the config a subdirectory of the workspace root so we can more easily separate the config from the vaults

legacy workspace is what we have today

new vaults are in different folders. the only issue is that the config is also mixed in within the workspace root