A style sheet, or CSS file, can be a thing of efficiency, or a complete mess. To keep it from being the latter, think in terms of the cascade. Use the broadest selector to set the most of a given declaration. The most basic example is setting the base font. Here, use
body as the selector, as everything inside body will follow the rules you set.
There is a sequence that reflects this kind of efficiency. The order below mostly works from big to small, following the HTML.
- variables (with preprocessor)
- mixins (with preprocessor)
body(to set base font)
- stand-alones (general rules that don't need context)
- follow the HTML…
- media queries
@imports, whether just a reset stylesheet (which should be considered an absolute necessity), or parts of a library, come first, as these rules (etc.) need to be established first. If using a reset sheet, you want everything reset before you start setting things. Logical.
If you are using web fonts, the browser needs to know where those fonts are. This is always in relation to your stylesheet, the CSS. If you are using a preprocessor (SASS or Less), make sure the src path is from your CSS, not the SCSS file.
I use the body tag/element to set the base font. The base font is the main font for text. Typographically, all other typographic decisions are based off this. One can use the universal selector (*), or the
html selector for this, but I think
body makes more sense.
This is my own term, but these are very general rules that don't need a context, such as that for indenting paragraphs, or setting display parameters for images:
follow the HTML
This is simply a matter of using the main block-level elements, in order. I most often start with a wrapper div, and set its display (usually either flex or grid) and any additional rules for that, as well as its width and margins. Then I proceed in order of the main elements (
footer, etc.), setting display/placement parameters first, then moving to details.
Again, logic. Once the site is set up, media queries can be used to instill responsiveness. This may seem to mostly contradict the "mobile first" mantra, but it seems, at least to me, to be the logical way to work. Get everything established, then mess with it.