I'm looking for a small to medium sized public Dendron vault to use as test data for some scripts I am writing. Would be good if it made use of images and the different kinds of embeds. The Dendron wiki vault has a bit too many notes. Although I guess I could just delete a bunch.

Also, is there a command to expand the whole tree or the current subtree of the tree view? When restarting VSCode, everything is collapsed and I have to expand stuff manually.

you may want to know that, for now, VS Code is performing way better than vscodium (regretfully for me)

But on the other hand, this is good, because you helped me to bypass the problem that was experiencing, which rended dendron almost useless (one of the things I love is that it's really fast by default)

Hey, quick question: - is there a way to quickly switch between Vaults? Currently I'm switching with mouse click on the tree. I'm moving lots of info between notes/structure of different Vaults, it would be nice to have something similar to Ctrl + Tab

Hi, I've recently discovered Dendron and was wondering what's the benefit of embedding the structure in the finename instead of using tags for instance?

Using tags and sub-tags (eg: #software/language/typescript)

When I first saw dendron the concept of embedding the taxonomy in the file names was new to me too. Since then I have come to appreciate the following pros: - easier to keep a consistent taxonomy compared to inline tags - example set by dendron makes note paths concise - compared to folders, I do not have to create the structure before creating the note

Thanks @User As far as I understood, all files live in the same folder. Isn't there any performance consideration when having 10k+ files with long file names in the same folder?

Is there any way to have markdown titles using a larger police while in editing mode?

Are there any specific advantages of using Dendron over say Obsidian for developers? Said another way are there any possibilities to connect notes and maybe notebooks or other code artifacts?

Dendron shines for structured knowledge like about programming languages etc. thats why their are actual folks that use dendron and obsidian in tandem and have their dendron vault inside of obsidian.

The

dendron-site

has around 780 notes. If you also add

dendron-docs

that's another 550 notes. These are both Github repositories of the Dendron organization, is that around what you were looking for?

I don't think so unfortunately

Could you expand a bit what you mean by this? Generally you don't have to switch between vaults, you can just use the lookup. The lookup can find notes across all of your vaults, so you don't have to worry about which vault you're in.

We have 10k+ notes in the internal team vault, and we haven't seen any performance impacts yet. If it ends up causing performance issues one day, we can always tackle the problem then.

Dendron does have tags by the way, so you're welcome to use tags in your notes as well: https://wiki.dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821/

You can link to files that are not notes: https://wiki.dendron.so/notes/3472226a-ff3c-432d-bf5d-10926f39f6c2/#file-links Combined with native workspaces (https://wiki.dendron.so/notes/lamzybrD6SgQlJ9BpwkQk/), you can use Dendron to document your projects, and you can link to the source files in your project from the documentation.

I believe it's a limitation of VSCode, but we can't resize individual lines in the editor. We have plans to write our own visual editor one day which would support that, but we don't have a timeline for when it would come out.

I imagine that 10k is certainly not a major concern when manipulated programmatically. However, how does it work when in file view? I understand that file view is certainly not the most appropriate view, even more so with that many files, but aren't you overloading the system if you hit file view by inadvertence or when browsing around using the OS provided file explorer.

Just tried opening the folder in a file manager, it opened instantly without any delays. Same when I open the file explorer section of VSCode. I don't think it's enough files to be overwhelming, but if you have a usecase that uses many more files where you are hitting any limits, please do let us know and we'll think about how we can fix it.

Sure, I understand that

tags

are available but I'm wondering why not use a specific keyword to hold the hierarchy (eg: tax: software/language/rust or tax: software.language.rust)? As long as you provide the tools to organize notes around this concept it sounds very similar (a taxonomy view, the possibility to drag and drop notes in the taxonomy view, etc...). Just curious to know why you opted for such a "specific" approach?

the reason we use the file name to represent hierarchy is for a bunch of reasons: - its a lightweight mechanism for representing hierarchy that is portable across any text editor (eg. you can explore a dendron directory almost as easily in vim as in vscode) - we get around the limitations of how folders are implemented in the filesystem - a folder cannot also be a file (it can only contain other files) - a folder is heavy to create and manipulate - simplification for refactoring - since hierarchies are encoded in the file name itself, refactoring hierarchies can be mapped to regex replacement

Compared to folders, that sounds perfectly reasonable and legit. However, compared to using "tag" or any other "keyword " in the front-matter? For instance (but I'm not an expert by any means), Obsidian seems to be able to reproduce the kind of hierarchy that is part of Dendron philosophy by using hierarchical tags (eg: #tab/sub-tag/sub-sub-tag). Did you balance and compare these 2 possible approaches?

yep. these two and many many more. you could use a tag tree to represent an hierarchy. the difference is where the emphasis is. for the tag/keyword based approach: - hierarchy is not baked into the representation of your notes. its added metadata. this means you would need to add hierarchy as metadata to every note that you create - in dendron, because hierarchy is baked in to the filename itself, everything becomes part of a hierarchy by default. this means everything is traversable via lookup - the act of creating a note is also the act of putting it in a hierarchy

As the devil's advocate, I could argue that I doubt anyone would not add some metadata anyway. Isn't there a concept of "ID" in Dendron that makes it more likely to have a front-matter? However, you are right, even without any metadata, you can structure your notes in a meaningful hierarchical way. I guess I will have to give it a try and see for myself 🙂

Yes. I think that issue covers it. I gave a 👍

Thanks! I'll have a look at those!

What if I would like to have 2 different hierarchies to access the same information. Say, I have a note on

Typescript Interview questions

and the way I think of it could be: * software.language.typescript * learning.dev.typescript In Obsidian (that I'm currently testing), I could use nested tags. What's your take on this using Dendron? How would you approach this?

If you need to have the same note in multiple locations, consider having the note itself in a fairly flat hierarchy (say, 2 hierarchies deep, like

ref.typescript-interview-questions

), and then use note references (https://wiki.dendron.so/notes/f1af56bb-db27-47ae-8406-61a98de6c78c/) in

software.language.typescript

and

learning.dev.typescript

.

![[ref.typescript-interview-questions]]

the recommendation for having the referenced note in a flat hierarchy is to make it mentally more easier to retrieve, but since you can use fuzzy searching with lookup you don't really need to. You could easily compile all interview question somewhere more deep like

ref.dev.interview.lang.ts

and reference this when you have to.