> Hi. Is there a simple guide on how to use Dendron? I've read the help, but continue to be a bit lost. @User currently, the comprehensive guide consists of following the quickstart here (https://www.dendron.so/notes/e86ac3ab-dbe1-47a1-bcd7-9df0d0490b40.html). working on making the docs easier to follow and less technical

i'm also doing 30min onboarding with all new users to walk through any hiccups you might encounter so feel free to book a time slot here (https://calendly.com/thence/meet) 🙂

Its really awesome that you take your tine to help out people. Is it possible to watch a recording of one of these?

> @User yep. you can do so by using labeled links -> [[label1 | foo]] and [[label2 | foo]] both point to foo.md @User That might be a solution, but I think I meant it more as being able to write both [[Watson]] and [[Dr. John Watson]] to link to Watson.md. [[Watson]] -> Watson.md is the regular link, but I want to be able to add multiple additional links (link alias..es?). This is because I often associate different things with the same "file". For example I can link to [[the end]], but it points me to [[death]]. Having to write [[the end|death]] would heavily detract from that, as I get the "validation" of my thought up-front, i.e. I already have to know the answer to be able to link it. (I hope this didn't get too philosophical).

> Its really awesome that you take your tine to help out people. Is it possible to watch a recording of one of these? @User the initial onboarding aren't recorded but i've been thinking of doing recorded office hours moving forward. would you be interested in that?

> @User That might be a solution, but I think I meant it more as being able to write both [[Watson]] and [[Dr. John Watson]] to link to Watson.md. [[Watson]] -> Watson.md is the regular link, but I want to be able to add multiple additional links (link alias..es?). This is because I often associate different things with the same "file". For example I can link to [[the end]], but it points me to [[death]]. Having to write [[the end|death]] would heavily detract from that, as I get the "validation" of my thought up-front, i.e. I already have to know the answer to be able to link it. (I hope this didn't get too philosophical). @User got it! not currently supported but have been thinking about adding something like that. could you create an issue so we can track progress? https://github.com/dendronhq/dendron/issues/new/choose

@kevins8 that would be interesting, indeed

is it possible to customize how titles are formatted in the frontmatter of a newly created note? For example, when I use the lookup command to create a new note, it already sets the title as capitalized. Can I configure it so the note is created with lower-case titles?

not right now but that's something I plan on adding, both as a global config and as a schema specific override

if you have specific use cases in mind, could you create an issue to describe them? that will help inform how I ship this https://github.com/dendronhq/dendron/issues/new/choose

Hi, is the

root.md

file in a vault supposed to have only metadata? with the latest release, whenever i run

show graph

command, the

root.md

file contents, except the metadata, gets wiped out (without any errors) and the graph is rendered with correct hierarchies

hmm,

show graph

shouldn't do anything to the file contents. can you run

Dendron:Dev: Open Logs

and send me the output to this dropbox link? https://www.dropbox.com/request/6PuqQuZKAYli0tR95aVc

what version is "Dendron Markdown Links"?

Dendron Markdown Links: 0.6.5.

well, now i reloaded the window, rebuilt index and reinstalled plugins which seem to have fixed the problem. but when i change the

title

in the file

root.md

to anything other than

root

, the graph still shows it as

root

. Other nodes in the graph work as expected

yeah - currently, you can't change the frontmatter in

root

but the contents is adjustable

is there a way to change the title to something other than root? frankly, i dont quite understand the relationship between

dendron.yml

file in workspace root and

root.md

+

root.shchema.yml

files inside the vaults.

yes and that's been on my roadmap. can you submit an issue for it here so I don't forget? https://github.com/dendronhq/dendron/issues/new/choose

as for the extra files, they are currently part of dendron due to some implementation details https://www.dendron.so/notes/a6c03f9b-8959-4d67-8394-4d204ab69bfe.html#why-does-dendron-create-root-files-in-my-vault

the dendron.yml file is used for dendron specific configuration outside of vscode. right now, it's used for publishing configuration https://www.dendron.so/notes/73d395c9-5041-4d0d-9db7-080d9586136e.html#dendronyml

so should root.md be used to add content right now or should it be left as-is till the planned features land?

root.md can be used to add content. the frontmatter is read-only but the content is yours

got it!

eg. sample root

as far as features or issues go, feel free to let me know whenever you run into something that seems weird or missing. i have a HUGE backlog of things I'm planning on adding and part of my selection algorithm is that people bring it up in discord 😅

and i've been telling other members, because dendron can be a little much to get started with, i'm doing 30min onboarding sessions with new users. that's where i try to understand your primary purpose for adopting dendron, go through any questions you might have as well as show some popular use cases and ways of setting up your dendron. link below in case you're interested 🙂 https://calendly.com/thence/meet

definitely! i'll keep a list of things i run into and add issues for them. thanks for your help, really appreciate it.

can the

refactor hierarchy

command work with notes at root level? e.g. i want to rename all notes to now have a new parent. so a note will go from root -> foo.md to root -> fooparent -> foo.md (and all notes will be renamed according to same pattern). when i try to do this with existing command i get following error:

nvm, i just did a plain old mv over all files in directory. 😛

haha, yeah, that would work too