The fedoraproject.org website is currently being replaced with what will become the next getfedora.org with F38 release.

The CSS you mention was from a (very) old version of getfedora, when it was still deployed on this domain. This version no longer exists.
I would recommend bringing this CSS (and all other statics you might need) in your own deployment instead.
You can find this old CSS here: https://pagure.io/fedora-websites/blob/d940d7d6/f/fedoraproject.org/static/css/fedora.css

I haven't looked at the CSS file super closely, but I wonder if there's a strong case for having a centralized Fedora CSS file that folks can use in other applications. That seems better than having everyone make their own and it would simplify updates if we decide to make some changes. SInce individual pages can supersede the central CSS file, there's not a lot of downside.

I haven't looked at the CSS file super closely, but I wonder if there's a strong case for having a centralized Fedora CSS file that folks can use in other applications. That seems better than having everyone make their own and it would simplify updates if we decide to make some changes. SInce individual pages can supersede the central CSS file, there's not a lot of downside.

This is something I've been wondering lately: it would be nice to have a place where shared content like fedora-bootstrap could be pulled from.
Usually things like fedora-bootstrap, jquery and other static content are embedded in html through links to CDN, but I think the majority of our websites are avoiding the usage of external CDNs (at least, Bodhi does that and bundle everything within its sources).

Meanwhile, for the problem here, I'm going to bundle the old fedora.css file in package-review-status code. Thanks @darknao for the link to the old source file.

I haven't looked at the CSS file super closely, but I wonder if there's a strong case for having a centralized Fedora CSS file that folks can use in other applications. That seems better than having everyone make their own and it would simplify updates if we decide to make some changes. SInce individual pages can supersede the central CSS file, there's not a lot of downside.

I'm really not sure about this.
With a centralized CSS, maintainers lose all control over the lifecycle of this file, and every single update can break all other websites depending on it.
I think a better way would be to use a common theme library, something like https://gitlab.com/fedora/websites-apps/themes/fedora-bootstrap.
For the new fedoraproject website, we use Tailwind instead. It's currently bundled in the main codebase, but I think the idea was to make it available in a separate repository for everyone to use.

If we really want to have a common CSS (or any statics) available for everyone, that needs to be versioned so we are not forcing updates on everyone relying on it.

If we really want to have a common CSS (or any statics) available for everyone, that needs to be versioned so we are not forcing updates on everyone relying on it.

That would be a good solution. A hypothetical intentionally-central CSS file would probably have a lot less than the old one and shouldn't change often. The idea is that it's a common starting point for some basic settings. But versioning it would be a good approach, assuming we allow minor changes without bumping the version, otherwise there's not much point.

But in any case, that's more of a Web & Apps team question, not an Infra question.

So, bundling the old fedora.css file into review_stats partially fixed the problem, because the old css requires some image files to be available alongside the style. However the webpages are now 99% usable.

I think this bug can be closed as it turned out not to be a infra question. I will however get in touch with web&apps to check the likelihood of having a shared stylesheet for simple pages like these, otherwise I will rewrite review_stats css to be fully custom (when I'll have time to do so).

Thanks!