flexboxgrid VS compiled

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

tags inside SFCs are typically injected as native </code> tags during development to support hot updates. <strong>For production they can be extracted and merged into a single CSS file.</strong></p> </blockquote> <p>There are also 3rd party CSS libs that do the same thing such as <a href="https://linaria.dev/">linaria</a>, <a href="https://vanilla-extract.style/">vanilla-extract</a>, and <a href="https://compiledcssinjs.com/">compiled CSS</a>. Which can be used in the event you're stuck with something that doesn't have baked in support via SFC formats (looking at you React).</p> <p>These are my preferred ways of handing it.</p> <ol> <li>Tailwind</li> </ol> <p>Option 2 is tailwind, which works backwards.</p> <p>That is, instead of the above with extraction where you write the styles, and the framework or libs extract them and replace them with class names, it's the other way around.</p> <p>You're writing class names first (which are essentially aggregated CSS property-values) which then generate and/or reference styles.</p> <p>It has the advantage of being easy to write (assuming you've got editor LSP, linting, etc), but as you've discovered, it's difficult to read / can get really messy really fast.</p> <p>As far as all the other claims on the Tailwind site, it's all marketing, at least 80% bullshit.</p> </div>

Your choice of CSS lib. Bootstrap can still be a valid choice, tho you may want to check the docs of whatever SSR / SSG framework you end up using as they may have better (or worse support). For example if you wanted to do CSS-in-JS (Next) i'd consider Linaria, vanilla-extract, or compiled.

So to be extremely clear, the issue isn't CSS-in-JS per se, it's just that the author only looked at implementations that don't generate create CSS files. He notably mentioned the (apparent) zero-runtime solutions Vanilla Extract and Linaria, only to skip them and complain that Compiled inserts nodes at runtime.

Compiled

Link: https://compiledcssinjs.com/

Compiled (Compile time CSS-in-JS solution from Atlassian)

Stitches Is near zero runtime and vanilla-extract claims it's zero runtime and typed. There's atlassian compiled as well but I never used it.

Author here, I haven't had time to play around with it, but this library[0] from Atlassian looks like a "best of the both worlds" styling approach: CSS-in-JS authorship without the runtime penalty.

[0] https://compiledcssinjs.com/