Hi @dave,

After the glitch earlier today (at least in my time zone), it looks like there is an issue with the CSS. The site doesn't format properly in Firefox (it does in Edge) and Firebug shows the following errors:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://maxcdn.bootstrapcdn.com.... (Reason: CORS header 'Access-Control-Allow-Origin' missing).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://maxcdn.bootstrapcdn.com.... (Reason: CORS header 'Access-Control-Allow-Origin' missing).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://maxcdn.bootstrapcdn.com.... (Reason: CORS header 'Access-Control-Allow-Origin' missing).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://maxcdn.bootstrapcdn.com.... (Reason: CORS header 'Access-Control-Allow-Origin' missing).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://maxcdn.bootstrapcdn.com.... (Reason: CORS header 'Access-Control-Allow-Origin' missing).
None of the "sha384" hashes in the integrity attribute match the content of the subresource.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://maxcdn.bootstrapcdn.com.... (Reason: CORS header 'Access-Control-Allow-Origin' missing).
None of the "sha384" hashes in the integrity attribute match the content of the subresource.

I'm guessing something's gone wrong with the headers?

Hi again @dave,

Sorry, my mistake - apparently the Firefox addon "HTTPS Everywhere" had been reactivated for garden.org today... not sure why. It was the cause of the issue.