I’m happy to announce that version 0.8.0 of CSS Lint is now available on the web site, via GitHub, and through npm. This release focused very heavily on two things: documentation and web UI improvements.

The documentation work has continued over on the wiki, where we’ve added some initial documentation on using CSS Lint in a build system (we’d love contributions to this, by the way). The Developer Guide has been reorganized to be more useful and more details have been added regarding tests and rule creation. The rules documentation has also had a facelift as part of our ongoing efforts to improve documentation around rules.

Other notable changes in this release:

  • Based on a suggestion from Kevin Sweeney, the web UI now remembers your settings in between visits.
  • You can also specify which rules to use as a hash in the URL for the web UI. For example, http://csslint.net#warnings=ids,import,important. The hash is automatically updated whenever you change which rules you’re applying, so it’s easy to copy-paste the URL to a friend and share your favorite settings.
  • Eric Wendelin added an error/warning indication to the compact CLI output format. As a bonus, you can copy the hash and use it with the CLI.
  • Based on a suggestion from Mahonnaise, you can now configure warnings and errors by rule in the CSS Lint CLI. You can now specify --warnings and --errors with lists of rules. The --rules option is deprecated. For more, checkout the CLI documentation.
  • After a lengthy debate, the Broken Box Model rule has been renamed to the Box Model Sizing rule to better indicate the rule’s intent.
  • The rules that checks for known properties got smarter. Instead of just checking property names, it also checks their values. Not all properties are supported yet, but CSS Lint is now capable of helping you out with a large number of properties.
  • New Rule: The box-sizing rule warns when box-sizing is used (rule documentation).
  • New Rule: Our first accessibility rules warns when you use outline: none (rule documentation).

Thanks once again to all of the great feedback and contributions we’ve been receiving from the growing CSS Lint community.

Disclaimer: Any viewpoints and opinions expressed in this article are those of Nicholas C. Zakas and do not, in any way, reflect those of my employer, my colleagues, Wrox Publishing, O'Reilly Publishing, or anyone else. I speak only for myself, not for them.

Both comments and pings are currently closed.