Replies: 2 comments 8 replies
-
I would love to see this feature! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Great suggestion! I've found myself wanting to have a different structure in my vault than in the published site. I think the implementation suggested here would be great, and allow for lots of customisations without getting overly complicated. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, the note URL is being determined by the
dg-permalink
key, and in its absence, by location in the vault. A thing to notice here is, no matter what the permalink is, it will always be placed in the file tree as in the vault.Another thing is, a gardener might want a different organization in the published garden which can differ from the vault.
To achieve more control over the representations I thought of two solutions which will complement each other.
Path Rewrite Rules
A textarea in the settings where the users can add rewrite rules. For example:
In every line of colon-delimited rules, the first part is to be the
from
part, and the second part is to be theto
part.dg-path
A frontmatter entry to provide the path of the note.
Precedences in Path resolution
Precedences for URL generation
Beta Was this translation helpful? Give feedback.
All reactions