flexboxgrid VS stitches

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

Over the past few years, I've worked with React apps utilising various CSS-in-JS libraries, starting with styled-components, transitioning through emotion, Theme UI, and finally Stitches. I've also integrated MUI, Mantine, and Chakra in numerous client projects.

Radix has some great ideas that challenge the way components are usually built. I'd love to use it, but am somewhat burned by how Stitches stopped being maintained due to the changes in React 18. Context: https://github.com/stitchesjs/stitches/discussions/1149#disc...

To be clear, it's not so much that they decided to not spend time, energy and money into maintaining it, but that there's seemingly been very little (if any) interest in letting others maintain it despite several people expressing interest. I'm sure it's scare handing over commit access, but if you're giving it up anyway then why not just do it, see what happens? Instead it's just dead in the water.

I'd happily pay license fees to use Radix and/or Stitches, if that guarantees maintenance. Sadly that's not an option it seems.

I work on a lot of more "creative" projects where frameworks like TailwindCSS or Bootstrap just don't cut it. My approach has always been to use some kind of library to ease the process of creating my own CSS framework that can then be used by other people. I find that Stitches does it pretty well. You set your design tokens, then you have IntelliSense to help people understand the design system.

Some libraries, such as Stitches, claim near-zero runtime performance overhead by tackling the first issue (parsing JavaScript CSS objects). Nevertheless, they still inject the parsed CSS into the DOM at runtime, which means they haven’t entirely eliminated the performance concerns.

Stitches allows you to map your design system

Define strict system of colors, spaces, etc then attempt to synchronize usage of it in both design and code (tools like https://vanilla-extract.style/ or https://stitches.dev/ can help with enforcing system on software side)

Curious to understand what is trending. We've been big fans of Stitches, however, unfortunately the project is no longer maintained.

There are some issues with SSR and NextJS in React 18: https://github.com/stitchesjs/stitches/issues/863

According to the docs, NextUI is a React UI library that allows you to make beautiful, modern, and fast websites/applications regardless of your design experience. It is created with React and Stitches, based on React Aria, and inspired by Vuesax.

Stitches CSS customization