nothing then really, was just looking for nice hilighting because that's something i've found so key to my ability to do things well.

ty

So I am trying to create a custom frontmatter with the help of the template (in the schema). Can someone help me ? How do i do this I know I am doing it wrong? My Query is that : 1. when trying to customise the frontmatter using the template how shouid i add this custom lines so that with every new note being created the custom frontmatter should be made

This how I would Like my Frontmatter to look like for all my notes

root.schema.yml

serves as the root of all schemas, but we currently don't support applying global schemas. You would have to create a separate schema for a specific hierarchy. Do you want this frontmatter to apply to every single note in your workspace?

Yes to every single note in this vault

do the notes in that vault share any single parent other than the root?

No

i will send you my tree pic

sure. that would help a lot coming up with a schema that works for you.

I am using the library of congress to sort/classify my note so Like 'RG' there will be more additions as the days go by

I would have a single parent for all notes that you want to have the template applied. just guessing here, but I'm assuming you wouldn't want the templates applied to anything under

tags.*

,

templates.*

,

Things-to-link-afterwards

and so on.

Yes

I was thinking of how to put 'tag, templates, Things-to-link-afterwards' under the folder asset or create a new one

This is a minimal structure I've come up that might work for you: content of `templates.preg.maternal-changes`:

---
id: 0l1omgwyc3g4327nrv0ljju
title: Maternal Changes
desc: 'The physical changes manifested in the body of the mother in order to compansate for the increase demands duriing the pregnancy'
classification:
  - '[[RG.551-591]]'
  - '[[RG.940-991]]'
updated: 1654664260893
created: 1654663967751
---

content of `preg.schema.yml`:

version: 1
imports: []
schemas:
  - id: preg
    children:
      - maternal-changes
    title: preg
    parent: root
  - id: maternal-changes
    template: templates.preg.maternal-changes
    namespace: true

With this schema and tree structure, whenever you add a note under

preg.maternal-changes.*

, the template will be applied to that note.

This is deviating from your current structure where you have

preg

as a tag (though this would actually have to be under

tags.preg

to work as intended as a tag), because schemas become useful when you structure your notes in a hierarchical manner. Like I mentioned we currently don't support global schema behaviors so if you want to keep your flat structure, you would need to use the

Apply Template

command on each note.

Ok i will tweak it a bit but mostly follow what u said will get back to u once I am done

I have a question is it possible to use handlebar to accomplish this global schema setup?

Handlebar handles everything related to resolving expressions within a template when the template is applied. Handlebar doesn't handle where / when the template is applied. The mechanism for applying the template will still be the same (using the

Apply Template

command, or specifying a template in the schema).

Is there a way to make sure that all new notes keep eg:

Preg

as the parent note instead of the

ROOT

?

There isn't a way to ensure that, but you can modify the keybinding for lookup note to alway pre-fill the value you choose as a default.

in `keybindings.json`:

...
    {
        "command": "dendron.lookupNote",
        "key": "cmd+l", // any key combination of your choice
        "args": {
            "initialValue": "preg",
        }
    }

When the template is being applied the emojies are not being applied correctly

Yes, this is a known issue. emojis are not preserved when yaml (frontmatter) is resolved. see: https://github.com/dendronhq/dendron/issues/3055

Is there a supported use case for Dendron as codespace docs? I'd like to have a docs folder in our repo and then be able to publish from that folder on deployment. Would we be able to have the entire project in dendron or would we have to just open the docs folder (which I'm assuming would be a vault). Any best practices or published workflows? I haven't been able to find any.

can I use template variable in frontmatter? I want all my notes'

title

(in frontmatter) will have form

research YYYY-MM-DD

The monorepo for Dendron actually has a Dendron workspace in the

docs

directory See: https://github.com/dendronhq/dendron/tree/master/docs

We don't directly publish from here at the moment but it should be possible with Github workflows.

What is the easiest way to export a group of linked notes as linked html files? I've tried following the guides in the documentation but I kept getting errors and it's too technical for me.

We recently introduced handlebars support for templates but unfortunately we don't currently support variable substitution in frontmatter I believe. (Correct me if I'm wrong @kevins8) You can however create a custom note trait and specify an

OnCreate

behavior to set the title. You can write plain javascript to customize what the note title will be on creation with note traits. See: https://wiki.dendron.so/notes/bdZhT3nF8Yz3WDzKp7hqh/