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
Super Moderator
******
205 22 Oct 2025 0
#1

I design in the browser almost exclusively now; mockups only for client sign-off.

Container queries changed how I build card layouts — the component adapts to its slot, not the viewport.

Code:
:root { --accent: #4f7cff; }
— CSS variables made my theming life so much easier.
Member
***
222 16 Feb 2026 0
#2

:has() feels like cheating compared to what we used to do.
Member
***
240 24 Jul 2026 0
#3

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

Interesting — I will have to try that.
Member
***
209 15 Mar 2026 0
#4

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

Good point, I had not thought of it that way.
Administrator
*******
201 13 Nov 2026 0
#5

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

Bumping this because I ran into the same thing today.
Account not Activated
215 24 Feb 2026
#6

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

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

I disagree slightly, but I can see where you are coming from.
Member
***
235 21 Dec 2025 0
#7

(08-11-2026, 10:34 AM)ByteBruce Wrote: Refactoring legacy CSS one component at a time is the only sane way.
:has() feels like cheating compared to what we used to do.

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

Nice thread, following for the replies.

Users browsing this thread: 1 Guest(s)

Forum Jump: