Hi Claude,
I use Markdown for the same reason you do.
X-item links are not the only way to link to files. I think one should think about how long this note will live before choosing the link syntax.
1.) X-item links
X-devonthink-item link are good as long as you use DEVONthink and they are powerful and work independent from the acutally location of the linked file. But they are broken if you leave DEVONthink.
2.) Relative file link
A relative file link works independent from DEVONthink but is needs a strong folder structure:
[LINK-TEXT](./FILE_IN_SAME_FOLDER.MD)
[LINK-TEXT](./FOLDER/FILE_IN_SUBFOLDER.MD)
[LINK-TEXT](/DOGS/FILE_IN_DOGS_FOLDER_AT_ROOT_LEVEL.MD)
From DEVONthink help:
Linking: You can reference local images, scripts, and other resources using item links, downward-relative (traveling subgroups; it’s not possible to travel up with ‘…’ as documents can have multiple parents) or absolute (start with a forward slash) paths.
You see that your file structure has to be strong for this relative file links to stay alive. It would be great to have a x-item-link at the OS level for whole MacOS.
3.) iCloud file links
Did anybody say OS level file links? Yeah, it is not exactly that, but something comparable. If you got your files in the iCloud (many other Cloud providers got the same functionality) you can share them through the Finder-APP and link to the URL in Markdown.
Not hot, but another option.
I think you go best longterm with #2. Build a strong folder structure and use relative file links.
For me the best would be some exporting script, which would transform the x-devonthink-item links of all text files in the exported folders to valid relative file links just before exporting to the file system. As I think DEVONthink will not vanish tomorrow you will be able to export your databases to the macOS file system.
@BLUEFROG Maybe something like this script will be included ?