Public static assets

[Fil]

The public/ directory currently contains assets that will be copied over to dist/_observablehq/, namely .css and client .js files.

Where should a user store their own public assets? (Maybe they need a logo, a favicon, custom css, some custom js to be called from the footer, etc.)

[mbostock]

You can put them in docs if they are referenced somewhere… but yeah we probably need a public folder for files that we don’t detect through static analysis.

[mbostock]

I think we shouldn’t do this, and we should do #692 instead. Or maybe we could do both, but I think unless we’re rewriting links, having a public folder will always be a footgun — and we’re rewriting links, we don’t need the public folder to tell us what to copy. Also, a public folder likely wouldn’t be compatible with cache-breaking hashes #260.