flexboxgrid VS prettier-plugin-tailwindcss

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

Since this was a problem that many people had already encountered, there was already a solution. The first thing I found was Tailwind's official Prettier plugin, which ensures that class names are always ordered according to a certain rule. Best of all, it's auto-correcting, so I don't accidentally miss something or commit a different order.

It's not as if the correct order for the rules is mysterious. It's implemented in the Tailwind compiler. Tools like prettier-plugin-tailwindcss, which automatically sorts the class names in your HTML code to match the order in which Tailwind generates them in your CSS output, use a public API in Tailwind to get this order.

Other than that, you can get Prettier sorting your classes with the Tailwind Prettier plugin. And one more quality-of-life extension that might help your eye sores from a long list of classes is Tailwind Fold.

I everyone. I am using Electron react boilerplate and I have successfully added tailwindcss to the project. However, I am struggling to get the Prettier plugin tailwindcss to work. I’ve tried following the instructions in the readme but no luck. I’ve tried moving my prettier.config.js to the .erc/config dir with no luck either.

Others have already replied, but if you need to structure your TailwindCSS classes, I recommend their official Prettier plugin which integrates well into an ESLint setup.

> Except that I read that it's great for writing, but a nightmare for reading.

This is true at first. I can see it being pretty daunting to come into an existing project and trying to understand the styling of components. Starting from scratch and easing it into an existing project is much easier imo. That's what I did for a personal website. Now that I understand it and have converted the entire website to Tailwind, I don't want to switch to anything else going forward.

Here's a Prettier plugin that sort the classes to keep everything consistent across components: https://github.com/tailwindlabs/prettier-plugin-tailwindcss

Tailwind combined with classnames (https://github.com/JedWatson/classnames) makes it really easy to have conditional styling based on component state.

Despite the existence of Prettier, arguments about code style such as how to sort ES module imports still exist. Manually sorting ES modules wastes time, and usually leads to losing context when you are writing code and then have to navigate to the top of a file to modify your import statements. I love using the @trivago/prettier-plugin-sort-imports plugin which automatically sorts new imports, and works perfectly together with TypeScript's auto-import feature. Similarly, prettier-plugin-tailwindcss automatically sorts Tailwind classes in your code.

Added the tailwind-prettier-plugin as not everyone uses headwind