hgrid-css VS css

Another solution is to only use a mixin like the one here: https://github.com/ahansson/hgrid-css/blob/main/sass/mixins/_mixins.scss

https://hgrid.io maybe, but with PostCSS, see the production build section of the docs.

https://hgrid.io using it everywhere

https://hgrid.io is a utility kit that is simple and has what you need.

I use my own package hgrid-css (https://hgrid.io) for everything because it's light, written in Sass, and has everything I need without the overhead of the bigger ones.

This is the most "modern" reset I know and is why I used it in my utility framework: https://github.com/ahansson/hgrid-css/blob/main/sass/base/_base.scss

As I use my own css framework (hgrid-css) I always have a whole bunch of classes in my css output that aren't used. I just purge all these and it works. I never touch the framework partials as part of the project itself, so I (almost) never have mess in my working scss files that need to be cleaned out, unlike what your issue is. As I don't have a problem with all the unused sass styles, I don't care to try to maintain the sass at all. I mostly work with purged CSS both on localhost and in prod, so I never see all the unused mess. If you take a look at the hgrid.io repository you'll see in package.json how I run purgecss on every start command and build command. So when sass is watching file changes I now and then have to stop and restart to reevaluate with purgecss. This way I always debug css based on what's really in my browser, and not what is in my source code.

You could try speeding up development with something simpler than Tailwind and less opinionated and easier to customize than Bootstrap. It has most of the utilities you need, check out https://hgrid.io

`hgrid-css` comes both as an npm package and as a single css file, you decide. Check out hgrid.io and the prebuilt files on GitHub: https://github.com/ahansson/hgrid-css/tree/main/dist

With Webpixels CSS I took these two concepts and extended them to cover 80% of the use cases. I added some new components that are not existing yet in Bootstrap, and I create a comprehensive list of utility classes using the included API. You can see them all documented in our documentation.

As I previously mentioned, we'll be using Webpixels CSS to style our site. It is a utility and component-centric design system based on Bootstrap for fast, responsive UI development. It will help us to build a modern website much faster.

Check out the documentation to see all the utility classes included in Webpixels CSS using the Bootstrap utility API.

Using the utility API you can create classes like mx-auto or shadow-5 to change the default style of an element, just like Tailwind does. This is a great approach that allows us to remain consistent, by having pre-built patterns (buttons, cards, etc.) and these classes to tweak these components quickly without messing with CSS. Here is the demo: https://webpixels.io/docs/css/1.0/transform and the GitHub repo: https://github.com/webpixels/css.

The stylish design is possible thanks to our custom-designed CSS design system, also built with Bootstrap.

It is called Webpixels CSS and you can start using it in your project right away. Browse the code on Github or read the docs on our website

GitHub Repo