Theme demo: pick a theme on the right. Log in as demo / demo to try posting. Everything resets every night.
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Threaded Mode
Administrator
*******
201 13 Nov 2026 0
#31

I still reach for Bootstrap when a client needs to maintain it afterwards.

Nice thread, following for the replies.
Reply
Member
***
231 20 Feb 2026 0
#32

CSS variables + one class toggle is my whole dark mode stack.

Container queries are great but I still add a media-query fallback.

Could not agree more.
Reply
Moderator
*****
221 21 Oct 2026 0
#33

I still reach for Bootstrap when a client needs to maintain it afterwards.

Refactoring legacy CSS one component at a time is the only sane way.

That has been my experience as well.
Reply
Member
***
229 22 Oct 2026 0
#34

Container queries are great but I still add a media-query fallback.
Reply
Member
***
207 20 Feb 2026 0
#35

:has() feels like cheating compared to what we used to do.

Interesting — I will have to try that.
Reply
Super Moderator
******
226 15 Oct 2025 0
#36

(07-21-2026, 05:30 AM)TurboTom Wrote: :has() feels like cheating compared to what we used to do.
:has() feels like cheating compared to what we used to do.

Thanks for sharing, saved me a lot of time.
Reply
Administrator
*******
201 13 Nov 2026 0
#37

Refactoring legacy CSS one component at a time is the only sane way.

Good point, I had not thought of it that way.
Reply
Banned
209 16 Oct 2025
#38

Refactoring legacy CSS one component at a time is the only sane way.
Reply
Administrator
*******
234 20 Nov 2026 0
#39

Container queries are great but I still add a media-query fallback.

:has() feels like cheating compared to what we used to do.

That has been my experience as well.

Interesting — I will have to try that.
Reply
Member
***
235 21 Dec 2025 0
#40

:has() feels like cheating compared to what we used to do.

I still reach for Bootstrap when a client needs to maintain it afterwards.
Reply

Users browsing this thread: 1 Guest(s)

Forum Jump: