Designing in the browser — still a thing?

Code:

:root { --accent: #4f7cff; }

— CSS variables made my theming life so much easier.

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

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

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

Interesting — I will have to try that.

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

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

Good point, I had not thought of it that way.

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

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

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

Thanks for sharing, saved me a lot of time.

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

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

I disagree slightly, but I can see where you are coming from.

Thanks for sharing, saved me a lot of time.

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

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

Could not agree more.

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

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

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

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

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

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

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