I get that I'm critiquing you within your apparent wheelhouse, but this aesthetic also matters a lot to me.
img[data-astro-cid-vnzlvqnm] {
width: 48px;
height: 48px;
image-rendering: pixelated;
object-fit: contain;
margin-bottom: 0.5rem;
}
I understand the goal here, but it works really poorly IMO when the source images are generally 32x32 (and some of them are smaller to arbitrary degrees because the content has been cropped — this doesn't seem to distort aspect ratios, but e.g. the "eye" icon gets stretched to fill the space, and thus scales with a bespoke 48/25 factor). Meanwhile the hover cursor looks pixel-precise, but definitely too big compared to the icons. (It seems to have been scaled 2x ahead of time, from an authentic 16x16.) The background scale is also pixel-precise (I don't know whether it's 2x scaled just to scale it, or to look like a 2x2 "pattern") so the difference in approaches is just really jarring to me.
(I think the font is also doing some anti-aliasing; probably can't really control that. It looks really cool, though.)
I would really recommend not cropping to content, and either using integer-scale boxes or just accepting some sampling interpolation. Or just leaving everything at 1:1 scale. It'd be noticeably physically smaller than authentic for typical desktop displays, but that's just hardware doing what it does. (And as it stands, it might be bigger than authentic!) Bonus points for a `@media` query on device resolution to make the choice.
(Edit: after reading through https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/P... I'm not really sure Firefox is working as advertised...? But I think x1.5 scaling for pixel art is always going to involve compromise.)