I'm not sure I 'get' this. To deploy a static site, I rename the 'old' directory and then rename the 'new' directory to the original name. What's all this about parsing HTML and not supporting 'files that aren't HTML, JS or CSS (images, videos, etc.)'?

Just a bit confused.

Lets say your html file points to two javascript files, app.js and lib.js. You make some changes to both files, and deploy.

With browser and CDN caching, users could get the old app.js with the new lib.js, or vice versa, until the caches have expired. In other words, there's no guarantee that both caches will expire at the same time. This can easily cause mysterious and transitory issues which disappear before you can debug them, but reoccur after future deploys.

This fixes that by ensuring that your html files explicitly point to a consistent set of css and js files.

That makes sense, I see, thanks.

This is really cool. I'll have to take a look into it for my personal blog for no other reason than to have some fun with a new technology.

Nice, looks useful. Thanks for building this