Theoleff
Joined 2 years ago
Karma
30
Submissions
26
Member since
Aug 13
Recent submissions
Comment · 12 days ago
Agreed. I think part of why it's hard to convey is that a lot of people formed their idea of CSS back when flexbox was new. These days an accordion is a few <details>, and a reading progress bar is a fixed div with animation-timeline: scroll(). You don't need JS for either.
(Full disclosure, I wrote a book on this, so I'm not exactly neutral: https://theosoti.com/you-dont-need-js/)
Comment · 12 days ago
Less than you'd think. A lot of it is just knowing the right element exists. A slide-out menu that closes on Esc or when you click outside is a button with popovertarget, a nav with popover, and a few lines of CSS for the animation.
(I'm biased, I ended up writing a book about this kind of stuff: https://theosoti.com/you-dont-need-js/)
Comment · 9 months ago
Here's my blog https://theosoti.com/ where I share mainly about CSS. They are a mix of long articles and some short ones to talk about stuff I'm currently learning.
Comment · 10 months ago
Happy New Year everyone. 2025 was a big year for me.
I spent a lot of time writing and sharing technical content, mostly about modern CSS. I didn’t expect much from it at first, but it slowly compounded.
Over the past year:
- On LinkedIn[0], my posts reached ~10M impressions and ~15k people decided to follow along.
- 1,800+ joined my newsletter.
- My blog[1] went from ~1–2 Google clicks/day to ~40/day.
- I published a book[2] about building UI with less JavaScript (185 copies sold so far).
What surprised me most wasn’t the numbers, but how much people care about clear, practical explanations and simple tools.
May 2026 be even better :)
[0]: https://www.linkedin.com/in/theosoti/ [1]: https://theosoti.com/ [2]: https://theosoti.com/you-dont-need-js/
Comment · 10 months ago
Thank you, it means a lot!
I originally started writing it because I was tired of books becoming obsolete every two years while the underlying problems stayed the same.
Comment · 10 months ago
Thanks for sharing that! It’s a super common story. Frontend patterns moved fast (especially for the last 3 years), and not always in a way that encouraged checking what the browser itself could already do.
If you want to improve a bit and discover more what CSS and HTML can do today, I also try to post daily on my LinkedIn: https://www.linkedin.com/in/theosoti/
Comment · 10 months ago
Yup, at this point it feels more like habit than necessity. People learned to build things like dropdowns in JavaScript years ago, so they keep doing it that way.
A lot of devs simply don’t look any further when it comes to what HTML and CSS already provide.
Comment · 10 months ago
The interesting part here isn’t “no JavaScript”, it’s that HTML already covers more use cases than people remember (forms, dialogs, validation, navigation).
I ran into this repeatedly while writing my book "You Don’t Need JavaScript"[0]: most JS in these cases isn’t adding capability, it’s compensating for forgotten platform features.
https://theosoti.com/you-dont-need-js
I also have a blog here: https://theosoti.com