FEDIDEVS

> Science confirms it: Websites really do all look the same.

Sometimes you need to decide against going the well-trodden path.
https://cssence.com/2021/beyond-100vw/

#CSSDay

Thanks @fantasai and everyone in the Web Standards world for doing what you are doing. The people in this #CSSDay church and online would probably not have the career they’re having without you.

@pixelambacht Can you feature-detect (as in: does font support it) font-variant-position to avoid superscript being not superscript, i.e. only the “browser default override” succeeds? Taking into account that a fallback font from the font-family chain may kick in.

#CSSDay

@pixelambacht Mission (already) accomplished, many times over. 👏

#CSSDay

@pixelambacht mentioned his goal for #CSSDay is to turn one or two people on to nice web typography.

🤞

https://cssence.com/2018/no-webfont-no-cry/

@julia_miocene Do you have to put a “No Divs Were Harmed in the Making of This Character” disclaimer next to your creations?

#CSSDay 🤯

I limit inline styles to #CSS custom properties.

https://cssence.com/2020/css-variables-in-style-attributes/

(Also makes things easier on #CSSNakedDay.)

#CSSDay

@KrijnHoetmer All good.

```
#CSSDay {
counter-reset: marriage;
}
```

Ah yes, `.visually-hidden`, curious to see where we are heading on that front.
https://cssence.com/2024/native-visually-hidden/

#CSSDay #A11y

Big yes to `reading-order-items`, #A11y FTW!

That said, I don't wanna be a browser maker having to implement this. 😰

@rachelandrew #CSSDay