I added light and dark themes to my blog along with some responsive fixes on smaller screens with a little help.
Why className and style props make your life harder, not easier
A WAFRN theme using the pds-landing Catppuccin terminal aesthetic — dark forest-green palette, JetBrains Mono, soft rounded cards.
I had a lovely chat with someone about critical CSS and optimizations. All optimizations come with tradeoffs, but many are acceptable tradeoffs. Algorithms might optimize for speed and Big-O complexity at the expense of memory. Websites might optimize for offline support at the expense of first load duration (needing to download an offline database). There are tricks and slight-of-hand to make optimizations feel better to users, but they're still there. Famously, the Instagram team makes it so your photo uploads silently in the background as you write the caption so that it's ready by the time you hit "Post". It's a neat trick!
According to data collected by Android Authority (2,514 respondents) and an analysis by Thomas Steiner, over 80% of users use a dark theme. Of course, it’s hard to call this sample entirely representative, since the surveys were conducted on technical forums, but overall, we can say that a good half of the internet uses a dark theme.
A dark theme for nighttime use isn’t the only reason for adding theming to a website. Another important goal is service accessibility. Worldwide, there are 285 million people with total or partial vision loss; in Russia, there are 218,000, and up to 2.2 billion with various visual impairments
Everyone else has been talking about Tailwind CSS lately so I might as well jump on this bandwagon. And, actually, I've not seen anyone state my point of view on it yet so I have something to add.
A common misconception I see is that responsive web development means loading up your CSS files with media queries for everything.
Sometimes you just need a element to shrink or grow in height proportionally with the width.
My solution to the so called "Impossible Layout".