I’ve been “fighting” against Tailwind for a while, and there’s 4 different kinds of reactions: Please stfu, Tailwind is awesome, [insert technical argument] Johan, why do you bore me with these technical things? Can you please tweet about cooking? And where is your new post about sim racing? If you don’t like it, just don’t […]
Category Archives: css
Why you’ll probably regret using Tailwind
- Posted in css development tailwind webdev - 16 comments
I see Tailwind being used by a lot of people. I totally get why it’s so popular. It looks great, the design choices are sensible, and you have copy-pastable code that reliably renders in the same way. It nets you results quickly which feels nice and rewarding. I think Tailwind is a perfect framework for […]
CSS4 – Let’s not go there!
A reponse to CSS4 is a Bad Idea* As a teacher of sorts, I for one don’t want to explain the difference between CSS3 and CSS4 to junior web devs. There is simply no point. CSS is just CSS. We should be happy that it’s stable. We should be happy that we dropped the 3. […]
Thoughts on Tailwind CSS
- Posted in css development - 3 comments
I looked deeper into Tailwind this weekend. I was aware of this framework and its popularity, but I wanted to dive deeper into it as I was researching it for a future project. If you have to choose your CSS strategy in 2019, there are different options: Use a framework that “comes with everything”: frameworks […]
Overengineered packages?
- Posted in css development javascript npm react - 1 comment
Is a package like classnames “overengineered”? I stated on Twitter that a package called classnames felt overengineered to me. I based myself on the npm page where this code example is given: var btnClass = classNames(‘btn’, this.props.className, { ‘btn-pressed’: this.state.isPressed, ‘btn-over’: !this.state.isPressed && this.state.isHovered}); The first reason I felt this was overengineered was because this kind of code actually belongs in […]
Re: The technical side of design systems
(or: should designers write React code?) This is some extended writing that got kickstarted by watching Brad Frost’s talk about Design Systems at the recent CSS Day 2019. If you are interested the video is online. Before the conference I had heard a podcast episode where Brad was talking about design vs. dev and design […]
CSS day 2019 – Part 1: UI special (2/2)
- Posted in conference css design
Continuing on from my first post about the first day of CSS day, here’s the second post which covers two more talks. The CSS day team already put up all the videos from CSS day on YouTube, so you can already watch all of the talks! Amazing. 1.5 Brad Frost – The technical side of […]
CSS day 2019 – Part 1: UI special (1/2)
- Posted in conference css design
I wrote so much about CSS day that I decided to split the content in multiple blog posts. I posted the intro yesterday. Now it’s time to get into the talks. CSS day is a 2 day conference. Day one was the “UI day” with a focus on design talks, often zooming in on the […]
CSS day 2019 is over (and it was great!)
- Posted in conference css report
Just like last year I went to CSS day – and I had a blast. Two days filled with a well curated programme. Perfect organization in a perfect venue. This year I took two of my colleagues along – Eva and Emily – and judging from their feedback they had a great time as well. […]
Reduced motion media query
- Posted in accessibility css
I wrote about making a website dark according to user preferences. I also pleaded for a standards-based implementation of a way to detect high contrast mode. There are other media queries that can make a website accord to user preferences. Something that has existed for a while now is the “Prefers reduced motion” media query which helps […]