flexboxgrid VS vanilla-extract

May you provide a specific scenario? A decade old 960gs provide a custom grid that could be easily tuned to any "proportion of the screen". Random super minimalistic http://flexboxgrid.com/ from the 10 seconds google search had a flex-basis param that could tune grid on the fly. Every other modern "flex css grid framework" has mediaqueries and basic components slapped on top. Barebones grid and flexbox provide tons of control without much effort for a simple drip-in positioning.

Here is a great CSS library that is just the column system. http://flexboxgrid.com/ It has the same naming as bootstrap. I personally just use flex and grid since it so powerful I have no need for a grid system. I just use grid template columns and then flex for pretty much everything else. Tis is why I love Tailwind CSS. It so much more powerful it has all the break points for you and then just lets you get to work and only generates the styles you actually use. On top of that you can easily create plugins and use the JIT styles where ever you need.

if it helps this is my go-to flex grid system when I start a new project. I usually build the big blocks using the utility classes provided by flexboxgrid (which is percentage-based), and then go in each component and fine tune each one. I also extended it a little bit to cover some uses cases that I felt it missed

Did you check out it's documentation? http://flexboxgrid.com/

Okay, so basically I am just out looking at what other developers do to get some of my own inspiration on how to proceed with my project. As of now, I am using some CSS libraries like normalize.css and flexboxgrid just to get some sense of structure on my design. I have looked at tailwindcss as an alternative too instead of writing most of the CSS myself. I know there are both up/downsides to both. But looking for other peoples opinions on this matter. To be a bit more specific, what I am working with is a Laravel backend with VueJS in the front. I saw earlier today that one should get the design done first, before scratching the backend, so that is basically what I am trying to do right now.

It does and I held off on learning CSS Grid even after I quit my job because flexbox does everything I need it to. I often used flexboxgrid (http://flexboxgrid.com/) to create my grids for my sites but since learning CSS Grid I have found that I can write a lot less HTML (fewer containers) and less CSS (fewer media queries) and layout a site faster and visually with properties like

In our experience, the best testing strategy for modern frontends is a combination of E2E testing (using Playwright+NextJS), and unit testing. Visual regression testing is not worth the effort in our opinion, especially with the advent of better CSS tooling like TailwindCSS and Vanilla Extract.

For building component libraries I’ve been a big fan of vanilla extract. Apparently it’s from the same people who made css modules

This sounds exactly like Vanilla Extract. https://vanilla-extract.style/

KumaUI : Another relatively new contender, Kuma uses zero runtime CSS-in-JS to create headless UI components which allows a lot of flexibility. It was heavily inspired by other zero runtime CSS-in-JS solutions such as PandaCSS, Vanilla Extract, and Linaria, as well as by Styled System, ChakraUI, and Native Base. ### Vue

The components are styled with CSS modules. When building the library, these styles will get transformed to normal CSS style sheets. This means that the consuming application will not even be required to support CSS modules. (In the future I want to extend this tutorial to use vanilla-extract instead.)

I do a lot of UI work and have never understood the appeal of Tailwind. It’s like relearning a new language. Tailwind was released in 2017. Maybe the CSS landscape wasn’t as good back then? Modern CSS is pretty awesome.

I’ve enjoyed using Vanilla Extract https://vanilla-extract.style/. It’s like css-in-js with none of the downsides as everything gets compiled to css.

Nah, I used enough Tailwind to know it becomes a spaghetti mess. I stick with CSS now, and in React I use https://vanilla-extract.style, compile time CSS in TypeScript.

Vanilla Extract is my current choice for the next greenfield project. I would also recommend checking out how and why this team integrated it with Tailwind.

I'm not trying to call a particular org or library out, because I think the ones I've been digging through (and prompted me to write this) are very high quality. It's vanilla-extract (a build-time CSS-in-JS library) and Braid Design System (built on vanilla-extract).

Apart from what has been suggested, there is also https://vanilla-extract.style/.