Hi @spjack, there doesn’t seem to be anything wrong with Sparkle’s generated code as far as I can see.
Just as a tip on how I look at potential caching issue, I look at the website headers from the command line like this:
% curl --head http://www.jhmresearch.com
HTTP/1.1 200 OK
Date: Mon, 29 Mar 2021 10:00:08 GMT
Last-Modified: Mon, 29 Mar 2021 02:48:19 GMT
Expires: Mon, 29 Mar 2021 10:10:08 GMT
Vary: header is an indication that there is likely to be a server side cache.
A server side cache will cause the side effect of pages not updating as soon as they’re published, and in this case it looks like the cache is somehow stuck and has broken the page for good.
The cache breaks the page for example by producing an older html file, that refers to css files that are no longer on the server (they’re replaced/renamed every time you publish).
Unless there was some other problem with publishing, that would cause a similar issue, right now the index.html file is referring to a number of files (with a timestamp of sorts in their filename), that are not found:
The reason the top of the page is instead working is due to the CSS embedded in the HTML, a technique referred to as “critical CSS extraction”, which is one of the many optimizations Sparkle implements to get websites to load faster.
I suggest you contact your web host and ask them to deactivate the server cache for your domain.