> @User Hi. For a note reference, could you make its background slightly darker or draw a frame around it so we know it is a "quote" from which note? @Handuo yep. can you file a feature request so we can put it on the roadmap? https://github.com/dendronhq/dendron/issues/new/choose

> One thing I continue to struggle with is keeping context when I use the backlinks/links in a note. I sometimes have "main notes" that link to lots of other ones and what I really want to happen is to open new Windows when I click on them but I haven't figured out how to do that yet. Does anyone know how or if there's some shortcut to get VSCode to open markdown links in new Windows? @Kiran i know you can change your tab settings to disable previews which will force vscode to open all links in a new tab

not by computer right now but will dig it up in the morning 😅

@User - Yeah, all my links open as new tabs BUT that tab covers up my previous page. I'd actually like to click 5 links and have 5 different Windows show up around VS Code.

lol no rush @User 🙂

@User I just submitted feature requrest174 and 175. This is based on my personal experience and I hope you also find it useful😆 Thanks for the fascinating work!

it’s something i’ve been thinking about doing but was waiting for someone to bring it up first 😅

@User I was looking through the Frontmatter docs and did not see namespace as a reserved word. Is it? In any event, I think it might be good to include a description: what? why? how? example. IMO

that's because

namespace

is used in schemas but not in frontmatter so its not a reserved keyword in that sense

@User should I change the

id

or

title

of a schema to change its display name when publish?

Also, I'm back with dendron after playing around Roam and Obsidian

Gonna try Dendron for a couple weeks from now

you mean the frontmatter of the note? (so that's the bit between the

--- ... ---

)

yep

and the answer to that is the

title

the

id

should stay constant as you work with your note

this is what lets us make sure your published notes always have the same urls even as you rename and change their underlying hierarhcy

also, happy to have you back with us @User 🙂

can i ask what prompted the return?

I've play around Roam and Obsidian and I have some comments: Roam: Roam is getting viral from a long time ago, the cool features, the awesome UI and many many, many informations out there for a begineer. However, the "cult" is not a community formation that I would prefer (you can see our discussion about this in the productivists server) Also, I would not like to give my notes to a random server. Obsidian: What pushes me to Obsidian is the community and the local-save. Block reference is not a big issue for me, but definitely a plus ➕ if have. However, Obsi lacks a great publish system, unlike Roam, you can't publish easily (in the same format in the native Obsidian app). Of course, you can do this with git but Roam's publish is more mature as it saves data in the server (cloud) and every Roam graph maintains the same format in everywhere. (I really like Obsi's UI) Dendron: Eventually I came back to Dendron because Dendron have the two pros from Roam and Obsi. Cool features + community. However, the learning curve for Dendron is steep if you never touched Github/git or VSc before. The phillosophy of note taking in Dendron is also different, everything heavily relys on hierarchy in here. I'm curious of how and where will Dendron lead me to if I keep taking notes in it since I never tried this kind of approach before.

@kevins8 But I think is the updates prompted the return haha Like the development are super quick bro, every two or three days I see some new features in the announcement😆 😆

got it. appreciate the detailed feedback. one of the primary goals this month is to make dendron easier to use. that being said, we've already made some progress in that department. - @User created this getting started video that is well paced and understandable for people without a software background: - we now have a cheatsheet which is accessible under

show help

that has shortcuts, descriptions, and videos of all commands: https://www.dendron.so/notes/f9540bb6-7a5a-46db-ae7c-e1a606f28c73.html As for the philosophy, I agree that it takes a bit to get your head around. working on putting together some thoughts and best practices on dendron's "hierarchy first approach to note taking". you can see the existing work here: - https://www.kevinslin.com/notes/e9c72b4f-adb8-4f15-a6aa-9f9d81538561.html

> @User But I think is the updates prompted the return haha > Like the development are super quick bro, every two or three days I see some new features in the announcement😆 😆 @User haha, thanks. move fast and (try our best) to not break things is the name of the game 🙂

Haha great

I found the cheatsheet super useful

So when working with note for different domains, do you create different vaults? I see that you can have multi-domain notes distinguished by the fist word of note filename, e.g. dendron and cli in the examples, are they separately publishable when this is so, if so, how?

a vault can have any number of domains. we support selective publication by domain https://www.dendron.so/notes/73d395c9-5041-4d0d-9db7-080d9586136e.html#sitehierarchies-str

@User vaults have somewhat sparse documentation, especially possible multi-vault setups. Let's say I'd like to separate work and home into distinct vaults, maybe even so that other vault is a symbolic link to dropbox or whatever. Would that work? Also, what happens if there's a filename collision across vaults?

I hve a question around the same context, say you consider all of your vault to be private and not really shareable, but you would still like to share bits and pieces from a couple notes and make them public. Would creating, say a

public.*

or

garden.*

hierarchy and then in each note you would reference the interesting bits and pieces from the rest of the private notes be feasible ? I guess to simplify my question: can you publish notes that have references to private / non-published notes ?

@User yep, its still vague because multi-vault setups aren't currently well supported. the way to have multiple vaults today is to have separate workspaces as dendron currently only supports one vault per workspace. multi-vault support is on the roadmap for this year. for naming collisions, i was thinking the following: - by default, surface all results with the vault name in the prefix say a user has the following vaults

.
└── workspace
    ├── kevin-vault
    │   └── python.hello.md
    └── jojo-vault
        └── python.hello.md

user enters the following lookup:

python.hello

they should see the following result

python.hello - kevin vault
python.hello - jojo vault

we can also introduce a vault specific prefix (eg. {vault}/{path}) to un-ambiguously specify our result user would type

kevin-vault/python.hello

to specify they want to access

kevin-vault