It's a nice and simple way to serve a webpage or two. Here's an example: I have a folder with an `index.html` and a `image.jpg` in it. The HTML file can refe

It's a nice and simple way to serve a webpage or two. Here's an example: I have a folder with an `index.html` and a `image.jpg` in it. The HTML file can reference that JPG by requesting `./image.jpg`, the browser will try to fetch it from the same directory — and it will find it. Also, the links to an users `Public` folder will not expire. With the new'ish "share link" functionality, I can't do that, since every file is served from is own path, from its own preview page. To get that link, I need to query the API; to get the direct/media link, I need to query the API again, the resulting link will be different, and it will expire after four hours. So no more dropping a mockup for a client in a folder, sending her the link to the `index.html` and be done with it. That's a step backwards. Yes, I could store the files on my own server, but that's besides the point.