postcss-preset-env VS normalize.css

Switching from a ready-made tool like Sass or a recommendation package like cssnext (deprecated since 2019) or PostCSS Preset Env (archived in 2022), to the modular PostCSS Preset Env plugin set we can choose a helpful and convenient set of future CSS features beyond the current stable client CSS.

To enable the future CSS there is also a plugin called PostCSS Preset Env. This plugin will take the unreleased CSS selectors and change it to the present usable CSS. More info at PostCSS Preset Env

Third, we enable the postcss-preset-env plugin, which adds support for many other cool things

My PostCSS Config contains postcss-preset-env already which should support for CSS nesting. I also installed postcss-nested & postcss-css-variables, just in case.

To solve this I used postcss-preset-env, which allowed me to define a "custom-media" with the name --viewport-lg and the value (min-width: 1024px). As postcss-preset-env also supported nested CSS this allowed for some pretty readable CSS.

If you use PostCSS, postcss-preset-env[1] is pretty neat for reading up on the latest features. E.g. here is the place properties feature[2].

1: https://preset-env.cssdb.org/

postcss-preset-env - it lets you use some cutting-edge CSS but understandable by modern browsers.

https://stylelint.io https://github.com/csstools/postcss-preset-env

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.