Files in assets without hash in their names?

[CanadianBeaver]

Is it possible to put some files in assets folder without any changes in their names? F.e. I have some .zip files and link from markdown to them like:
[download](../myfiles/myfile.zip)
but the link to this file is changing every time when content of file changed like:
myfile-4fb9ebecd28b6fe6d14e167d763a6f7.zip
I prefer to have a permanent link to this file.

[slorber]

You can put the file in static/myfiles/myfile.zip

Then link to it in 2 ways:

[download](/myfiles/myfile.zip)

[download](pathname:///myfiles/myfile.zip)

The 1st option will use our regular asset pipeline, adding a hash so that you can cache requests aggressively (note, your file will still exist at https://mySite.com/myfiles/myfile.zip, all static files are served as is, and we only create a new hashed copy)

The 2nd option will opt out of our asset pipeline and leave the link 100% unmodified

[CanadianBeaver]

Using static folder is not compatible with references in markdown on GitHub

[CanadianBeaver]

I mean, that if i have in markdown in doc folder something like:

[my file](../files/myfile.zip)

this file will be accessible on github, when somebody see that markdown. But if I use static feature, then link in markdown on github is wrong.

[slorber]

If you care about having a stable permalink url with no hash inside, then you could just harcode the link including the domain instead of trying to use a relative path.

[my file](https://myDocusaurusSite.com/files/myfile.zip)

If you don't care about having a stable permalink, then the fact there is a hash in the URL shouldn't matter

[CanadianBeaver]

This is the worst option. Firstly, there is a strongly dependence on the domain in markdown files. Secondly, the link on github's markdown will lead not to the file in repository, but to a file on the domain.

[CanadianBeaver]

the best working option could be something like:

  presets: [
    [
      'classic',
      {
        docs: {
          path: '../docs',
          exclude: ['README.md'],
          excludehash: ['*zip'] // HERE

[slorber]

This is the worst option. Firstly, there is a strongly dependence on the domain in markdown files.

Yes, that's the point of a permalink, it includes the domain on purpose.

Secondly, the link on github's markdown will lead not to the file in repository, but to a file on the domain.

I see no reason why you would want a permalink and yet have your github using a github.com link while your site uses a site.com link. If you want to have permalinks, pick one or another option and hardcode the link.

the best working option could be something like:

I'm sorry but I'm not going to add a new config option for a niche use case only one user asks for with unconvincing motivations. We will only ever consider this if multiple users complain about it.

If you are looking for a workaround, you could keep this link in your source:

[download](../myfiles/myfile.zip) 

And then write a small remark plugin so that inside your Docusaurus site, it gets "rewritten" to

[download](../myfiles/myfile.zip)

This is pseudo code but something like this should work:

export default function plugin(options) {
  return async (root) => {
    const {visit} = await import('unist-util-visit');
    visit(root, 'link', (link: Link) => {
      if (link.url === "../myfiles/myfile.zip") {
        link.url = "pathname:///myfiles/myfile.zip"
      }
    });
  };
}