And welcome to the community. Let us know when you have more questions like this. It's cozy in here 🙂

Thank you for the reply. I'm not at all on the software development side or lingo. I'm sure I'm over simplifying to probably a point of annoyance to the initiated. Please allow me to clarify. If I'm in, say, Obsidian. If I setup a hierarchical tagging system and I have templates for schema, what is it about Dendron that would bring a capability this cannot achieve. For example, if I want to refactor all notes with tag.foo to tag.bar, I would go to the tag and changing the name (effectively changing all instances of the tag in every note it appears. I feel like I'm missing the really big point of Dendron because of a lack of experience. This is why I humbly came here to try to understand from those much further down the road of obstacles once a PKM gets huge.

Thanks for the warm welcome

Firstly welcome to the Dendron Community For me the big point about Dendron is the ability to have Hierarchy’s and give my Notes a structure through the usage of Hierarchy’s and Schemas to validate the Hierarchy's and the ability to build a tree from it. Without needing to use Hierarchy’s. Secondly that it is Open-source and that I have the ability to contribute to it to improve it or fork / extend it to fit my needs and Providing them back to the community if they are wanted. But the most important thing for me is the ease of retrieval of finding notes, making it pretty easy to use Dendron as a Cache of knowledge for me that I repeatedly need, even if infrequently (you can look here for more informations on this workflow https://wiki.dendron.so/notes/3e7baac6-f120-4378-a667-92e7a0869dca.html) To your point about Maintainability of big Hierarchy’s you can refactor the Hierarchy’s as mentioned by @User, but you can split it into multiple Vaults of Knowledge as well, while still having them connected to each other. And you have the ability to Enforce certain Hierarchy’s through the usage of Schemas, to validate them and making searching through them easier for retrieval. Additionally having the Hierarchy’s in the file name allows those that have the knowledge to Provide tools, to others to easier navigate these hierarchy’s (Search, filter, etc.) for a first narrowing of files to search through for specific knowledge without needing to open the files. An example for this could be if you have a room full of Shelves that contain Multiple boxes that contain folders which contain paper notes, without a system to index what is contained in a Shelve, box, folder, you would need dam long to find a specific paper note. Now those Shelves could be interpreted as Domains in dendron, the boxes are the next level of Hierarchy and the folders are another level of Hierarchy. So having the Hierarchy's in the file names, provides the possibility for tools to limit the actual number of files that need to be read for finding what you search for. Becouse we know in which Shelve, Box and Folder to look for what you are searching for. So if the structure is only defined in the Tags that are written on the Notes, a tool would still need to look through all notes to find which notes have the same Hierarchy reducing the performance. I hope I didn't confuse you further, feel free to ask further questions.

what happens to asset files and asset file names on migration? (images, etc.) also what does this line "drag the markdown file into VSCode" mean here? https://wiki.dendron.so/notes/f9b4fc21-7613-4c8a-9257-cec4c06b67f9.html thanks

if you use the our pod import, asset files are copied to the

assets

folder. see https://wiki.dendron.so/notes/f23a6290-2dec-45dc-b616-c218ee53db6b.html#example another way of importing is to drag the files from your file explorer into the vscode file explorer

Thanks, got it. Maybe something to add to the doc. Have you encountered problems with path lengths with all this dot separation and uuids?

not in practice. for hierarchies, the sweet spot is between 2-4 levels of hierarchy. any more and its probably an indicator to rebalance.

I am getting an error with dendron, when I open a few specific files I get the error that says:

Cannot destructure property 'start' of 'e.position' as it is undefined.

I have observed this happening with some notes that have UUID as

id

. This does not happen with other notes (nanoID).

Moreover, I can't see the backlinks for the notes that show this error.

OK, so I am trying to import existing markdown files. 1. Import pod initiates a process and then just hangs showing "importing". It also blocks subsequent operations. Is there a way to specify the path correctly (Windows). Can it fail in a more understandable way? 2. If I move files to vscode manually, no headers are created, links do not work, it is not clear what is meant to happen with embedded images. It might be missing something but I am stuck at the first step.

Thanks for explanation and your paradigm.

I definitely see the use case being when you get to a critical mass of notes. Even one hierarchy can reduce complexity by 90%.

Does it matter if there are quotations marks around the title in YAML header?

---
title: Hello
---

or

---
title: "Hello"
---

?

You will need the quotation Marks if you include certain chars in the title

yaml
- title: Test # does work 
- title: #test does not work
- title: "#test" # does work

Got it. Good to be sure they are allowed

Is there a plug-in or ability to go from Dendron to Anki? Just curious on anyone’s workflow.

When I create a new note in Dendron, I often start with a heading typed as '# My Heading Text'. I noticed that this immediately makes the Markdown Lint plugin grumble with "MD025/single-title/single-h1: Multiple top-level headings in the same document". I realized that starting my heading with '## My Heading Text' makes the plugin happier. From this I have hypothesized that i) the title: part of frontmatter is somehow equivalent to a heading started with a single # i.e. the h1 heading and ii) Markdown Lint wants me to have only one line with a h1 heading. <-- Anyone else experiencing this? From a user perspective, it initially felt odd to start note headings with ## instead of # (although I was able to convince myself that it made sense.. that an h1 heading is a title, a note should have only one title, that title is in the frontmatter, so the headings I create should start with ##)

I am seeing the same. Also, in the standard Preview, the YAML title entry is ignored. In the dendron Preview, the entries in the YAML title and under # are both rendered, resulting in the duplicated title.

@User take a look at this config option https://wiki.dendron.so/notes/f83c1d87-eac0-48f3-a5cf-8a69989d8ec1.html#usefmtitle in your dendron.yml tus should explain why dendron gets renders it double if set to true for explanation if set to true then you want Markdown Lint to recognise the fm title and if you have set it to false you need to tell Markdown Lint to ignore the title field in the frontmatter.

Well, what is better?

That Depends on you and what you prefer, but most are using the fm title as the h1 title

🙂 I cannot imagine any reason to prefer one or the other

Hello, sorry to ask a noob question - but I am just getting started with Dendron, but the Lookup is not working for me. I am using Dendron on windows - I hit Ctrl + L but nothing happens. I do have vim extension installed. Any suggestions on what I could be missing or how should I debug this ?

It could be a shortcut issue. Can you try opening the command palette (

Ctrl+Shift+P

by default, not sure what the vim extension sets it to) and run "Dendron: Lookup"?

oh, this is a cache issue. we recently changed the way we store link position data. you can fix this by removing

.dendron.cache.json

in your vault

That does work! Thank you! But apparently the shortcut is

Ctrl + Shift + S

now

we have a migration on upgrade that will auto clear the cache but it only occured when you first upgraded. we've sinced fixed that to run on a per workspace basis

not natively but there are vscode extensions that do this https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html#use-dendron-with-anki

this is a keybinding conflict with vim. you can fix it with the following 1. open command palette and run

Open Keyboard Shortcuts (JSON)

2. add the following shortcut override

json
  {
    "key": "cmd+l",
    "command": "-expandLineSelection",
    "when": "textInputFocus"
  }