hgrid-css VS normalize.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

You can also consider using stylesheets like Normalize.css, Eric Mayer's CSS reset rules to establish a baseline layout across browsers.

==> Click here to get the code from necolas.github.io!

4. Understanding the box model A thorough understanding of the box model is essential for effective CSS debugging. The box model, encompassing margin, border, and padding, plays a fundamental role in CSS styling. By familiarizing yourself with the box model, you can better identify and resolve many styling issues. Browser issues. Different browsers render our styling differently. This is because browsers have their own default stylesheets called user-agent styles. To override these inconsistencies you should consider resetting your CSS to provide cross-browser consistency. A good resource I use when writing vanilla CSS is Normalize CSS. For example, it resets the margin, padding to zero, and the box-sizing property to border-box.

In addition to the answers below about flex, grid and media queries, you can also additionally take a look to the "clearfix hack" (https://www.w3schools.com/howto/howto_css_clearfix.asp) which is a common issue when you position elements and also use something like Normalize.css (see https://github.com/necolas/normalize.css) to avoid some weird bugs in your front end.

is this github what you used? Seems like it hasn't been updated in a while

You can just download the normalize.css file from their Github, and then include it on your page(s) as the first stylesheet link. It will basically override the "default" styles of the various browsers so that you have a common starting point. That should handle various things like margins and paddings.

I want to use a CSS normalizer for the first time on a new project I'm doing, and in the code there is a couple -webkit-appearance properties that VSCode is telling me are not standard. However, when I search up if this is really a problem or not, I don't find anything saying yes or no. So... Is it actually a problem to use this property?

reset.css — download here

This might be helpful.

https://necolas.github.io/normalize.css/

Design decisions, though, are ultimately up to your taste and judgement.