If I understand correctly you have a single given scratch note you want to move into a permanent position. Then rename is the way to go as @SeriousBug mentions. If however you have a bunch of related scratch notes that should go into a specific hierarchy you would be faster with refactor hierarchy

I've got a problem. I can't figure out how to add my already existing dendron folder to a new github repo?

Also, dendron stops working when I move my vault to another folder

Anyone else have issues with the Markdown Preview Enhanced not honoring font sizes?

This may strike as an odd question, but to what degree of interoperability is there with .org files? Are these files editable in Dendron, compatible with the hierarchy tooling, etc.? What degree of support is present and is foreseen to be present? I’m asking because I want to plan my note-taking journey, and I’d like to know whether I could interact with my non-markdown files within Dendron.

.org files should be editable in the sense that their plaintext and you can open plpaintext using vscode. we don't provide any dendron native functionality on top of it (eg. lookup, preview, etc)

I then suppose the friction is with importing .org files. This should be fairly easy: Emacs export to .md > Dendron Markdown Pod. If you can represent them in the file tree as a separate vault, there’s a secondary option to use VSCode as an alternative editor for the files. It is surprising to me how little support .org files receive outside of their natural habitat. Maybe the consensus is that Org-Mode provides all you need to work with the files. But in the case of Dendron, I could see value in outlining/taking hierarchical scratch notes in Org-Mode, and then refactoring the headings into Dendron hierarchies. The outstanding concern for the first option is, how does the markdown import in Dendron handle metadata, since Dendron creates new metadata upon conversion? I suppose the support for .org files will be based on demand, because there are much greater priorities.

I wrote a little elisp script to batch export org files (from org-roam) to Dendron markdown. I was using already hierarchies with org-roam so the migration was about getting links right

Does anyone know what could be causing this on the published github pages site?

This is often due to an incorrect

assetsPrefix

in your

dendron.yml

. Here is an example of how it should be set: https://wiki.dendron.so/notes/230d0ccf-5758-4a8f-b39b-3b68e1482e2b.html#examples

From what I can tell it's correct. My site is at https://tristan401-2000.github.io/tristans-notes/. The siteUrl is https://tristan401-2000.github.io and the assetsPrefix is tristans-notes

Oh wait, after a rebuild and giving it time, it's fine

Great, glad to hear it works!

Thanks for the help!

Hi everyone, i like using dendron more and more every day (just started 2-3 days ago) but i cant wrap my head around why my template is not working when i generate a new daily journal entry the schema i use is the following: > version: 1 > imports: [] > schemas: > - id: daily > title: daily > parent: root > children: > - journal > - id: journal > namespace: true > template: > id: templates.journal.daily > type: note

not sure how you created the journal files (through what syntax?) but I suggest you to follow the wiki

yml
schemas:
- id: journal
  title: journal
  desc: ""
  parent: root
  children:
    - year
- id: year
  title: year
  pattern: "[0-2][0-9][0-9][0-9]"
  children: 
    - month
- id: month
  title: month
  pattern: "[0-9][0-9]"
  children: 
    - day
- id: day
  title: day
  pattern: "[0-9][0-9]"
  namespace: true
  template:
    # identifier for the template (for a note based template, it would be the name of the note)
    id: journal.template.daily
    # what sort of template we are creating. currently, only 'note' is supported
    type: note

creating the journal files via the dendron command

so the created journal file is

daily.2021.01.01

?

daily.journal.2021.06.02

is that not how it should look like? haha

I think the problem is the template is for the files under the

journal

hierarchy but not for hierarchies under than that In order to apply it, I think you can try to create different hierarchies like the schema I'd mentioned just now

does the schema template show up if you create a note like:

daily.journal.2021-06-02

?

i had to change the default journal date format setting to

y-MM-dd

for the schema template to take

Treeview V2 is not showing for me since updated to 0.44. Is this happening to anyone else?

Yes, this is a known issue. Kevin is working on it I believe.

Good to know! Thanks @User ! 🙂

also not. Must be something stupid i know it

could you share with us the file?

the schema?