Problems with File Path nesting

[AlmostAPhysicist]

There are currently no options to sync paths as relative. The plugin, as of now, as far as I have tested, regardless of quartz settings, always appends vault path to any file path in the attachments.

There are further problems with this absolute path since if the target folder in the repo is content/subfolder instead of simply content, then the plugin does NOT prepend subfolder in the attachments file paths.

Hence, neither relative, nor absolute paths are completely error prone without some inconvenient workarounds.

[AlmostAPhysicist]

Got a solution to it.
It turns out that the plugin treats ./path/to/file as relative and everything else as something to be crawled and extended up to the root.
Better Markdown Links plugin from Obsidian helps appending a ./ in the file path that sorts the issue.

EDIT:
For some reason that is beyond me, Quartz Syncer only keeps absolute paths for ./pathto.excalidraw files as relative. All other file paths, regardless of what the pattern is, for wiki links to say the least, are converted to a path from the root.

I can not really find a way to just leave paths as they are. It is my request to @saberzero1 to maybe add a simple toggle. I really love the plugin and how it looks and feels. This is the one thing it does weirdly. Again, the reason I want to have this is I want to point my Obsidian vault to not just content but a certain subfolder of content to categorize my vaults nicely. That and the ability to simply drag and drop an isolated folder really show why relative links are important.

There are several possible workarounds that I think one can try:

1. Change the Quartz Syncer source code manually. I am honestly not so capable of doing this
2. Use the Git Obsidian plugin to gain total control over the system and push things to the repo yourself. Personally, I don't like this since I don't want to clutter my repo with .git folders and everything and I think submodules are a little pain to deal with.
3. Try other github syncer plugins. Enveloppe is the closest I think but can cause plenty merge issues easily. You can probably get around that. But I just like the Quartz Syncer plugin UI and feel much better (but the links and how they are transformed).
4. Create your own plugin
5. (This is what I am doing) Create a Github Actions workflow to convert back all links to relative links. I am doing this with a python script. The general idea of the algorithm that I use is to both crawl down the path tree and crawl it up to content, therefore searching in both directions for a valid path. Once found, python can easily convert valid paths to a relative path for files. I then run this script with a workflow YAML file to run every time quartz syncer pushes something to the repo, which fixes the links for any newly added file. This is probably very involved and complicated. But it does boil down to 2 files that live in my repo that I never touch, and never clutter my Obsidian Vaults. If someone wants, I can probably share my scripts too. But I would certainly like the plugin devs to just add a toggle to keep links as they are (they would, from my understanding, get the path from vault root anyways to actually add the files with the correct folder setup)

[saberzero1]

Hey, I'm a little confused about your exact setup.

Quartz Syncer allows you to configure the vault root differently on both ends (so a subdirectory in your vault and a separate subdirectory in your Quartz repository can be configured.)

If you're using Quartz Syncer, your vault explicitly shouldn't be the content directory in your Quartz repository, because Quartz Syncer is a one-way sync.

[AlmostAPhysicist]

Hey! Sure, I guess its on me to not elaborate.

As an example, say I have two vaults:
Let's call them Music and Recipe for illustration purposes.
I want to set up the entire workflow such that within my quartz website, I have the content of the Music vault under the Music folder and the Recipe vault under the Recipe folder.

But on its own, the Music vault has no idea about where it is going to be used - its just an ordinary vault on my device.
(Another example may be different notes vaults for different college semester: Spring2025 and Fall2025. just regular vaults I had on my device)

Say that the music Vault looks like this:
Music Vault:

Pop:
    - song1.md                           // contains ![[./Attachments/image.png]]
    Attachments:
        - image.png 
Jazz:
(and so on)

I would want to set the Content Folder of the Quartz Syncer plugin to content/Music (since that is where I want the contents of the vault to sync to)

When I publish Pop/song1.md that exists in my Music vault, Quartz Syncer correctly syncs within repo:

content:
    Music:
        Pop:
            - song1.md
            Attachments:
                - image.png

Essentially, taking the Pop/song1.md file and all relevant attachments from the vault exactly as structured and appending that structure onto the Music folder (the one dedicated for the Vault)

This works fantastically EXCEPT, for some reason beyond my control, Quartz Syncer changes:
![[./Attachments/image.png]] to ![[Pop/Attachments/image.png]] within the song1.md file's raw code.

But this link just isn't valid in Quartz.
Either, Quartz should append Music (the particular sub-folder of content within the Content Folder) and make the link
![[Music/Pop/Attachments/image.png]] which indeed would work in quartz just fine. OR it could just leave the link as a relative link, exactly as it was (![[./Attachments/image.png]]).

I am guessing that you must compute the path to all links from the vault root (eg: Pop/Attachments/image.png) in order to append the right structure to content/Music in the repo. However, I think the plugin should also append the Music prefix to all the link paths on top of converting them to be from vault root.

I think an even better thing to do would be to have a toggle to not change the link paths inside links within a file at all.
A convention may be to leave absolute paths starting with ./ or ../ be unchanged and change paths that start differently (especially with /folder-from-root/) and to also have prepended the slice of Content Folder that excludes the content substring for paths from root.

My personal workaround has been to go through every file and turn links that the plugin uploaded within the file back to relative:
![[Pop/Attachments/image.png]] back to ![[./Attachments/image.png]]

The algorithm is a little bit more complicated that just dropping a name due to some edge cases, but the idea is that all this would be unnecessary if the plugin had some toggle or link conversion rule defined in the settings.

TLDR:
I may have over complicated things for myself for no reason. Do let me know if there already exists a way to do something like this that I just could not find. Regardless, it was very interesting to set up the GitHub workflow since I never did that before.
Thanks! I hope it is much more clear now!