I've noticed in the docs that there are a lot of instances that refer to the

dendron

package. AFAIK this is deprecated in favor of

dendron-cli

? I can go and make a PR for a few of the places I've spotted this (if I have my above facts straight)

other way around.

dendron-cli

is now aliased to

dendron

😅

oh interesting, because dendron-cli commands work for me, but

dendron

commands return "command not found"

what version of dendro-cli are you running?

am i correct that

root.schema.yml

and

root.md

are mandatory for every vault? does

root

function like

index.html

in webserver?

or is it more/only for vault metadata?

yes, root is a special note that is mandatory for every vault for now.

this may change in the future: https://github.com/dendronhq/dendron/issues/483

it's kind of hard to reconcile

root

and also the use of word

'schema'

in the yml with the concept of vault's namespace

could you elaborate on the issue? I would love to help.

just a quick dump before i lost the train of thought, it's making it unintuitive wrt namespace. if i have a vault for 'learning programming languages', and i make namespace like

learn.lang.python.modules.re

,

learn.lang.js.node

, and somehow i'm trying to have a really high point of view about what's covered in

learn

it seems like -

root.md

renamed to

learn.md

is the most logical choice, as

learn

is the namespace's root -

root.schema.yml

when renaming is introduced in future version, (or maybe autogenerated at creation based on vault's name or namespace?) is the natural configuration place if there are options that can enhance data schema related to the subjects inside the vault/namespace (say like for template system, or automating reference insert to external documentation, etc)

sorry i had to type the reply before this quick before reading the issue #483

i guess what i'm saying is, in order for users to have a more cohesive grasp of the concept of what

root

is in context of namespace/structure/day-to-day usage/how dendron perceive a

root

, it needs to either be - (taking example from your issue) make

Celebrarium

the actual root, not a proxy, perhaps (throwing a wild idea) by changing dendron so that only one file can have

.root

extension. OR... - remove

root.md

&

root.schema.yml

completely from users POV, by hiding them, make them invisible from UI, graphs, and so on, basically necessitates Dendron to treat them as internal data/metadata and enables user to determine whether they make

Celebrarium

as root or other documents

understood. and that was my exact point when creating that issue 👍 for now having

learn.md

along side

root.md

, you will be having a

learn

domain. you can treat this as the root of that hierarchy.

are you intending to use the vault exclusively for everything

learn

and not have any other namespaces?

i see... it's just that in my personal view, the semantic of

schema

tied to a root is quite strong, and i wonder how that's going to be designed in the future wrt to the user's domain and well, day-to-day experience

currently i have 4 vaults, which i don't see any way to cleanly separate them: -

learn

for learning subjects -

wiki

for knowledge collection, for the ones surrounding a topic/subject (say something like GDPR policy, how it's implemented), specifications, hardwares for specc'ing, that sort of thing, or about future interests (raspberry pi, hardware accessories, etc) -

dev

for development subjects -

post-production

for my previous field specific topics they're all interconnected and whenever using dendron i keep thinking about some ways to suggest improvements in multi vault experience, especially with tags and graph

Why not have all of those in the same vault, especially if they are interconnected?

helps to make it easier to separate mentally, i guess

like post production is very niche, and development is very broad & deep

with namespacing, easier to have

post.hardwares.display

and

dev.hardwares.display

than trying to come up with a root name that covers everything

IRL, the two of them connected at some point in time, but mapping that in metadata & tagging system is expensive mentally if i don't have a separation. (i guess?)

you can have a

post

namespace and

dev

namespace in the same vault. i.e.)

root.md
dev.md
dev.hardwares.md
dev.hardwares.display.md
...
post.md
post.hardwares.md
post.hardwares.display.md
...

This will achieve the separation you are going for

personally i don't really see why they should be inside a single vault

i mean for context it's personal opinion, but i'm more comfortable with viewing from tags POV, which is very loose and can be very messy, than from namespace and filesystem like foldering. what i'm doing now with dendron is basically forcing my POV to fit dendron

or is it the other way around

having multiple vaults for each of your namespace is perfectly valid, and in that case I can see that having an enforced

root.md

in your way could be a bit unnatural.

i wonder how you guys manage to deal with the complexity of making taxonomy works for many people, it must be extremely exhausting lol... that's why i prefer tagging as primary way to approach taxonomy, like it's just a metadata labeling, can be as many as i see relevant and i can change it in the future as often as i see fit

i suppose the cost of doing that can be high for people who like to have a once & done way of categorizing, but it fits my way of thinking as i often see connections/relationships as context

re: my previous question i guess i need to read the doc on schema more carefully