Expected Behavior

Right now, non-rendered files (SVGs, PDFs, C source code, etc.) work as static resources but it would be nice if they could also work as resources linked to in the local directory.

Possible Solution

Files which aren't indexed by other indexers could be indexed as "asset" files, and get a new endpoint (e.g. /_assets/) which maps to them.

For security/privacy (to prevent the download of raw entry content files etc.), the _assets endpoint should be in the form of _assets/<id:str>/<filename:str> where the ID is (pseudo?)randomly generated, perhaps based on the file hash, and both the ID and the filename should match.

There should also be a configuration for which file extensions should be whitelisted into the asset store.

Context

Being able to keep a .pdf or .svg or .cpp or whatever alongside the entry that refers to it, making asset management simpler instead of having to think about whether a file is stored in the static folder or not.