Cross-compatibility with markdown viewers: replace "{{DOC_PATH}}" / {{APP_PATH}}" by relative links

[ilyasdc]

Hi,

Thank you very much for your nice software. It is very useful to share it my less text-editor inclined colleagues (researcher in a public institution in Poland). But I would also like to edit the markdown files by myself and for instance attach images inline. However if I attach an image via Wikidocs it appears [image]{{DOC_PATH}}filename.ext in the markdown file and cannot be viewed (e.g. by obsidian), reciprocally if I attach a file compatible with most viewers using the relative syntax [image](./relative/location.ext it doesn't render in wikidoc

[ffiesta]

Hi @ilyasdc,

Regarding ![]({{DOC_PATH}}image.ext) or your example ![image]({{DOC_PATH}}image.ext), this is the obfuscated path syntax for the relative path ![image](/datasets/documents/homepage/imagem/image.ext).

I’ve noticed that Joplin and Obsidian store all uploaded images in a single folder, which can get messy when you try to locate files directly through the file explorer. In contrast, WikiDocs saves files (like *.png, *.docx, *.pdf, etc.) relative to the wiki note’s folder. This keeps things organized and makes it easier to find specific images or documents since WikiDocs aggregates the content logically.

I’m not sure if future versions of WikiDocs will change this behavior or add an option to choose where files are stored (e.g., in the wiki note’s folder or a shared global folder). However, that seems unlikely for now.

If this workflow doesn’t suit your needs, you might want to explore other apps for editing WikiDocs files.

Quick Example:
You could set up a simple XAMPP or Laragon server with WikiDocs and use its rsync function to sync all files or just selected ones. This works very well and eliminates the need for third-party apps.

[ilyasdc]

Hello @ffiesta,

Thank you very much for you quick reply. I however am not sure if I understand correctly what you mean by "relative path" in the context of wikidocs. Don't you agree that the path /datasets/documents/homepage/imagem/image.ext is rather absolute than relative ? Regarding Obsidian, I just checked and you are correct, by default it stores all images in the root of the vault which is rather dubious, I don't think there's any need to change the current location of images w/r to markdown files.

However in Obsidian or most of markdown renderers, if one moves the file to the same folder as the markdown file and uses relative path (e.g. ![image](./image-name.ext)) where image and markdown are in the same folder it displays the image and I think is relatively standard markdown syntax (e.g. mkdocs will show the image with the relative path)

[ffiesta]

HI @ilyasdc,

Wikidocs use relative path in somr cases and another full path. In mobile its hard to write here! Lol

But in resume
Wikidocs ofuscate path to content.md files

• domain.pt/homepage (load content.md file inside folder homepage)
• domain.pt/homepage/xpto (load content.md file inside folder xpto)
• domain.pt/wiskas (load content.md)
• domain.pt/wiskas/folder-2/test (load content.md file)

wikidocs convert writed relative path's to {{DOC_PATH}}. This {{DOC_PATH}}/pdf.pdf is write to content.md file insted absolute path/pdf.pdf, although you see absolute path or relative path when you edit, and this doc-path change if wikidocs is on a domain/subfolder or on domain, because this you need to maintain file strutured like it create, but you can force this like write https://domain.pt/datasets/documents/*/pdf.pdf but whe you chande this into another folder you have a problem.

Create a example folder and open editor > and after with sub-editor that have a side by side editor|viewer and try adding images or files and you see what I am saying.

After came her and i try to help.

[ilyasdc]

Hi @ffiesta,

I know the path is obfuscated. But if I modify the .md with a text editor and replace {{DOC_PATH}} to a relative path (e.g ./) the image is not rendered because Wikidocs doesn't understand relative paths AFAIK.

• ![](/datasets/documents/foo/bar/baz/image-name.jpeg)/ => works
• ![](./image-name.jpeg)/ => doesn't work

[ffiesta]

Now I understand the problem, and... after some analysis, it makes sense since it would allow direct editing with text-based programs like Notepad.

This approach would make WikiDocs backward compatible (at least with paths inserted as ).

Based on this—and after analyzing the shortcuts for .pdf attachments—it would also make sense to standardize them, so some wouldn’t use {{DOC_PATH}} while others use {{APP_PATH}}.