as in you mean the "root" like projects.md isn't necessary

I'd have projects.dendron

and it'd still have projects

in the graph yes

If you want to read more about possible future improvements to the graph Read through this RFC ->https://wiki.dendron.so/notes/c998c642-a748-4f77-9285-cfec35330251.html

lots of things to consider I see, sure, makes sense

hm earlier ctrl+enter worked to create a new note but now doesn't, does it exclusively work with no hierarchy links?

That acutally works perfectly fine for me

ah I accidentally linked to an existing one, I guess just confusing UX, as I expected it'd take me there regardless

Hi there, is it possible to give the main 'vault'-Folder in a workspace another name like 'MyNotes'?

Do you mean the directory in the file system shall be called 'MyNotes'?

yes

I tried to rename the folder and the workspace-settings, but it didn't work

its a series of steps to rename a vault right now: https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html#renaming-a-vault

Haha I was about to write the same

Thanks!

I am interested in publishing just one of my vaults. My thought was to make the vault I want into a git repo, push to github, then set up a github page. Unfortunately, it seems that the dendron.yml files exist at the root, so I would need to push my whole Dendron directory. I don't want to do this, because github only offers free github pages for public repos. Is there an option to publish a single vault, without exposing everything on github?

What gets published is the

docs

directory created when you run the

dendron-cli -- buildSiteV2 ...

command. So you can locally run the cli and take the content of the docs to publish.

you can also create a new workspace and import the one vault you want to publish and commit that to github

which

import

command would that be? all I see is the

pod import

command

If you create a new dendron workspace, you can use the

add vault

command to add just the vault you want to publish.

That way on your local machine you'd have both a workspace with all your vaults that you use for most things but then a workspace that gets published.

Would this approach (create new workspace, then

add vault

) use the same "live" files & vault as the "regular" multivault? Put differently: does it make duplicate copies or are they the same primary files?

They're the same primary files (and even the same git repo if you've got one git repo per vault). @User

did the update to 0.37 do away with the idea of a scratch journal??? Ctrl-Shift-S just gives a blank lookup, no longer populated with "scratch.2021.04.13", unless the active tab is also a scratch note... and if I create that note, it gets a title of '13' instead of '2021-04-13'

ok so that wasn't just me 😄 I thought I was doing something wrong

ah! so maybe we have a regression bug?

wait.. it's now working again.

I can't repro anymore. maybe it doesn't work in some edge cases.

hmm