Hierarchical naming system examples

taking notes and organizing them should be very fluid processes. When there are "friction" of this nature, something is wrong with our way of doing things. A system should be simple and holistic. We must be able to trust him. The hierarchical organization can sometimes lead to unexpected difficulties: where to store such a note? in which hierarchy? If I put it here, why not there too? A less rigid organization makes it possible to overcome this questioning and let things happen naturally.

We must therefore not hesitate sometimes not to want to prioritize everything and simply create massive links between notes to see (potentially) emerge a storage/organization method. It is on this point in particular that I too stumble; not everything can be hierarchical and wanting to force things necessarily removes value from recording concepts or notes. Finally writing this, I realize my own mistakes in wanting to do things in very organized and hierarchical ways.

Question: let's say I want to use 2 different tools for my notes (Dendron, for one and Logseq as a backup), how should I do this ? I know that Logseq is also flat-based but I also know it exposes several folders to the users (pages and journal).

If it is not possible easily I will try to find a way to test Logseq separately on demo data.

Been using Dendron for a couple days now and I just wanted to say I love it, great work 👍

Because I use both Windows and MacOS, what would you guys recommend to have my notes synced cross-platform - should I just put my code folder on dropbox or do it through the Git/GitHub repo way

i know i could probably use OpenSSH but it's a bit too much of a hassle for me

Folks, when I am using ctrl + l (I am on a windows machne), and look up notes, I seem to open the new note it in the place of an existing note rather than a new tab. Is there any mechanism to override this? Thanks.

This does not happen all the time though. Only every now and then,. Maybe, it is something that I am goofing up.

You may have the VSCode setting for preview mode on: https://code.visualstudio.com/docs/getstarted/userinterface#_preview-mode

Thanks. I will check this and ping if this is the case.

I did check. It was actually disabled. But this works fine now. I am able to open in a new tab. I will check this and see if this happens again. Thanks!

I'm noticed that the published html only uses instead of headings for "backlinks" and "children". For accessibility reasons this should use headings. This is especially important for screen readers which uses headings for quick navigation. Should one report things like this as a bug or a feature request?

will defer to folks that use logseq more consistently. adding @WildMagic in case they have more to add here

depends on how much you want to use git. simple way is dropbox. if you want to use the git workflow, you can use git. if you go the later route, dendron has a command to convert your existing vault to a git based one > https://wiki.dendron.so/notes/6682fca0-65ed-402c-8634-94cd51463cc4#vault-convert

feel free to report it as a bug. thanks!

Just opened VS Code today. Looks like a recent VS Code update happened (I received release notes). Dendron opened up with these error messages: Thoughts?

@seadude: https://github.com/dendronhq/dendron/issues/3364 Looks like a regression in 107, you can roll back to 106 in vscode until this is resolved:

for folks that have a moment - can you see if this new patch fixes the issue?

Thanks for the quick reply. I'm assuming you're saying 1.70? I just tried 1.69 and the same errors show

I can go back to 1.70 then test

How do I install the .vsix file?

I'm back on 1.70. Will install .vsix file now

for folks that have a moment can you see

Can I limit 'Refactor' to a specific Vault ? Sounds like it insists on doing the refactoring for all vaults in the current WS

Frankly, you can imitate the experience of Logseq in Dendron by simply writing everything into your daily notes (equivalent to journal in Logseq), instead of putting in separate hierarchy. Then you can categorize the daily journal with hierarchical tags in Dendron (similar to namespace concept in Logseq). When you find a good reason, you will create a dedicated hierarchy structure for new notes (similar to creating a page in Logseq)

This is a great tidbit! Thanks!

I think you cannot currently. You can upvote this issue. https://github.com/dendronhq/dendron/issues/1304