@User just making sure i wasn't going insane 😅 let me know if the link I posted solves your issue. it should be a setting you can toggle in the markdown preview

@User > Hello, when creating a new note (new) from an existing note (old), is it possible to have a link from old to new embedded in the new so that I can trace back "up" the chain of notes? that's exactly what the link2Selection option is for in lookup https://dendron.so/notes/a7c3a810-28c8-4b47-96a6-8156b1524af3.html#creating-notes-with-a-selection you can trigger it automatically when you create a scratch note https://dendron.so/notes/5c213aa6-e4ba-49e8-85c5-1bdcb33ce202.html#scratch-note

is it possible to get seo friendly urls in the published garden?

you mean not publishing by the unique ids?

yes, but filename instead perhaps or using a separate front matter specified url?

currently that isn't supported since its how dendron has permanent ids: https://dendron.so/notes/5fcb8564-7209-4a80-9bb8-025bc8eb489b.html#permanent-ids in the future, we will implement SEO friendly version of the unique identifier using the same trick that stack overflow does (https://stackoverflow.com/questions/820493/can-an-seo-friendly-url-contain-a-unique-id) this preserves seo friendliness as well as making sure the links don't break the caveat is that this does require a server/proxy. we're looking into offering hosted publishing around december/january which can offer this functionality as well as the ability to publish privately or share with select people by email

very interesting. thanks for the quick reply

Hi. I'm new here and a newbie (in note-taking, knowledge management etc. Really digging the customization provided by VSCode + the huge potential of Dendron. How to change the preview font?

Thanks!

Did something change with templates? My template for my daily journal stopped working a few releases back.

Anybody know if there has been a change to them?

Could it be the schema itself? It needs to list a version number if it does not, a couple of users found this to cause problems with templates not applying properly

have a question related to publishing - i publish the notes as a project site on github pages, and because github publishes it to a subdirectory url like {myusername}.github.io/{project-name} i noticed all the images aren't displayed since it's pointing to assets/{imagename} . anybody run into this before? I tried something like this https://jekyllrb.com/docs/github-pages/#project-page-url-structure but doesn't seem to work awesome tool btw 🙂

also, noticed when i run "Build Pod" it always deletes

docs/assets/images/log.png

and

docs/assets/images/log-banner.png

> Could it be the schema itself? It needs to list a version number if it does not, a couple of users found this to cause problems with templates not applying properly @User That might be it. I don't have a version. What should it be?

ok i got it working 🙂

I added Version: 1 to the top

@User this can be fixed with the

assetPrefix

directive https://dendron.so/notes/ffa6a4ba-5eda-48c7-add5-8e2333ba27b4.html#assetsprefix-str

if you create a github repo in the following format

{username}.github.io

, than the above steps won't be necessary 🙂

I have some odd behavior for schema matching. i split up my projects into subprojects simply by naming convention "pro.pro1", "pro.pro1-sub1" and "pro.proj-sub2" my schema is mostly copied from the example:

version: 1
schemas:
# this will match "pro.*" notes
- id: pro 
  # human readable description of hierarchy
  desc: active projects
  # add this to the domain of your schema hierarchy
  parent: root
  # when a schema is a namespace, it can have arbitrary children. equivalent to pro.* glob pattern
  namespace: true 
  children:
    - people
    - journal
    - todo

but it seems like the

-

in the project name is preventing subprojects from being matched:

thinking about it... i'd much rather prefer to have a "subprojects" namespace for each project with the same schema. are self-referencing schemas possible?

@User not right now though its something we could support if folks are interested. for sub-projects, I usually like to link the together using backlinks rather than hierarchy

- pro.main.md
- pro.sub-a.md
- pro.sub-b.md

Inside pro.main, I would have the following:

# Projects

- [[pro.sub-a]]
- [[pro.sub-b]]

The reason for this is to keep my hierarchies as short as possible. This makes it easier to navigate and I usually know what projects I'm working with at any given time so it's not a big deal that they are all at the top level. I also tend to prefix my projects with the date for easy filtering

- pro.2020-main.md
- pro.2020-sub-a.md
- pro.2020-sub-b.md

refactoring question - i have a bunch of notes that start with maths, but have stuff like maths.linalg, maths.complexnumbers, etc etc - i want to change maths to math but retain all the rest of the hierarchy. ie. change maths.linalg to math.linalg and maths.complexnumbers to math.

i tried with maths.* which matches all the right ones, but then the change i tried specifying math.*

but then in the preview it looks like it'll cutoff everything after the - it writes it will rename maths.linalg to math.* and maths.complexnumbers to math.*

im just slightly afraid to press go, cause it doesn't seem like it'll do the right thing. my question is; how do i change the name of a top hierarchy and retain the rest of the hierarchy?

@User : try the following.

capture: ^maths

rename: math