jackyzha0
[Feature Request] No-Compromise Vault Structure
Is your feature request related to a problem? Please describe. Quartz requires vaults to have URL-compliant note names and Markdown links. This:
- Makes the vault harder to work with in Obsidian, with links not corresponding to
titles - Makes migrating a vault to Quartz require mass edits and link fixes
- Makes setup more difficult (in that Quartz is not plug and play)
- Makes the vault less pretty in disallowing spaces and emojis and imposing nonstandard capitalization
Describe the solution you'd like Ingest a Quartz-noncompliant vault with obsidian-quartz-sanitizer to generate a Quartz-compliant one on run, which would then be served.
Describe alternatives you've considered Running a personal script that does the same thing, workarounds for Wikilinks (which doesn't fix file names)
Additional context
This would potentially allow the person using Quartz to not have to change anything about their vault, which takes away a big chunk of barrier to entry. They may even not have to specify title:, which can be generated from the filename, making Quartz use almost plug and play
Strongly agree with this! Note titles and URLs should be independent so that you can import notes from an existing Obsidian vault and everything "just works".
For example, a note titled Let's go.md is not compatible with Quartz. This took me a while to figure out. Ideally Quartz would automatically form the URL as /lets-go or at least allow the frontmatter slug parameter to be used to define that URL e.g. slug: lets-go.
This is exactly what I would need to start using Quartz. To be honest out of all other Digital Garden "solutions" Quartz seems the most useful and beautiful, and this wikilinks/markdown links issue together with the absolute path requirement is just something I cannot accept and is the biggest barrier for me to start using it...
