Originally created by: jnewsome
I'm considering using markdown files in my code repo as the primary documentation source (instead of splitting documentation between in-repo documents and a wiki).
It'd be nice to be able to link to other files in the repo in a succinct way that looks nice when viewing the raw markdown.
The following gets rendered as the expected link when viewed on the web, but isn't very nice when viewing or editing the raw markdown:
[subdir](subdir) is a directory containing...
It'd be nice to instead be able to do something like artifact links on the wiki:
[subdir] is a directory containing...
Originally by: jnewsome
Potential solutions discussed on irc:
Making repo files artifacts
Extending artifact linking
~~~~~~
<brondsem> one idea would be to extend our artifact linking so not everything has to be an artifact
<brondsem> specifically, [tool:artifact] is a more verbose version of our artifact linking syntax, and we might be able to make [git:some/file/path] work without some/file/path being an artifact, but some sort of lookup function that the git tool provides
<jnewsome> that'd be nice for linking from the wiki to files in the repo
<jnewsome> but it doesn't address the use-case of having a markdown file in the repo that looks like sane plaintext and links to other files next to it in the repo
<brondsem> another option is the <url> syntax which seems to only accept fully qualified urls
<brondsem> a relative path would be handy there
~~~~~