csslint VS Sass

CSS Lint

With that being said, you could run some css linter I believe if you really decided to let them to do. Maybe leverage something like this: https://github.com/CSSLint/csslint

http://csslint.net/ ?

Thanks in advance folks, if anyone would like to see any info or pics or whatever, I can post. If I haven't gone mad or blind from going thru too many lines of code. (it's hard to use things like CSSLint because of all the !importants you have to use to supercede stuff, and csslint.net flags every --variable-name as an error, so even after switching off everything but basic checking it doesnt work too well, not catching simple syntax errors even... maybe I should look into something better there)

VSCode can do real-time linting for you, or you can run it through an online linter.

Sorry, meant http://csslint.net - edited to change.

Second, check to make sure you didn't make a change to your CSS which broke all of the CSS after that point. You could use a site like CSS Lint to help check that for you (just copy-and-paste all of your CSS there and click "Lint").

You can use a linting site, such as http://csslint.net/, to check for syntax & redundancy errors before you save them to your sub's stylesheet.

Also you could look into linting your css (http://csslint.net/) This will force consistency in the way you write and catch mistakes

You might want to run your CSS code through a CSS error checker, like CSS Lint, to help you find errors like that. (Note: It's very picky, so you may get lots of warnings that you may be able to ignore, but you should definitely fix any errors.)

SASS(.scss) [ https://sass-lang.com ]

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these days are Sass, Less, and Stylus. Any examples I give going forward will be about Sass as that's what I'm most familiar with.

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below.

Scss

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers.

Sass is also a css preprocessor. Op is likely confused

sass -> An improvement over CSS. It provides nice features for managing CSS. good for mid-sized or even larger projects.

Sass (Syntactically Awesome Style Sheets) - A CSS preprocessor that simplifies and enhances your CSS workflow. Website: https://sass-lang.com/

Personally, my preference is Sass: I find that the mixins, partials, and operators are hugely useful when it comes to creating re-usable snippets of code for a design system. And, since it’s “just” a pre-processor and not a framework, it’s not opinionated in a design sense and there’s no default values (colors, spacing values, etc.) that will need to be overwritten.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.