i think part of the confusion is that dendron has two types of nodes,

schemas

and

notes

, and that the two relate to each other but are also independent. ### schemas - namespace: a schema can be designated as a namespace. if so, it will match all its children and designate them as a match ### notes

.
├── root.md  --> absolute root of vault
└── project.md  --> root of project hierarchy. also referred to as the hierarchy **domain**
    └── project.foo.md --> a note within the project hierarchy

### add behavior - for all below examples, assume that

pro.dendron.demo.md

is opened and that

pro

matches a namespace schema - childOfDomain: add new note as child of the current domain (aka root of current hierarchy). doesn't take into account schema - output:

pro.journal

- childOfDomainNamespace: add new note as child of the current domain. if domain matches a namespace schema, make it into a child of that instead - output:

pro.dendron.journal

- childOfCurrent: add new note as child of whatever note your currently on - output:

pro.dendron.demo.journal

- asOwnDomain: add new note as its own domain. dis-regards current open note - output:

journal

(domain name specified by

default{NodeType}Name

)