despite cohost being unusually friendly to custom CSS in posts, its use of utility rather than semantic classes for its own styling makes it particularly painful to write custom styles to, for example, de-emphasize likes and rehosts in the notification feed
- she/her
enthusiast enthusiast
offsite reposts: @nex3-reposts
clips & pics: @nex3-moments
Cohost utilities:
- Image grid generator
- Backloggd formatter
- Letterboxd formatter
- Timeline deduplicator
- Syntax highlighter
header photo by me
You must log in to comment.
in reply to @nex3's post:
this is extremely valid although i can say we were previously using semantic CSS classes and it took an extremely long time to implement anything. utility classes acted as a force multiplier that made shipping the website how it is even possible.
i don’t intend to change how we’re writing our styles BUT at some point i’ll add data tags to make selecting elements easier
(second side note: im starting on an extremely fine grained notification filtering toolset after search ships, so this specific use case will be irrelevant Soon)
yeah my opinion as a Vaunted CSS Professional is that utility classes are great for use-cases like yours, with a small team where velocity is the watchword. semantic stuff starts to become more important the more relevant maintainability and shareability becomes, which is obviously in the "good problems to have" zone right now
Pinned Tags