Skip to content

Commit

Permalink
Remove guidance to use specific libraries/tools
Browse files Browse the repository at this point in the history
- Authors should pick and use tools based on the needs of the project
- We are amongst an explosion in front-end tooling; suggesting this
  small list of libraries/tools/framework is shortsighted
- "Use Bourbon for a Sass library" is confusing because "Sass library"
  is not a defined "thing" that serves every project equally
- Now that CSS Grid Layout has broad browser support, Neat or any grid
  framework might not be needed
- It was strange to categorize these guidelines under "Organization"
- I have a hunch that this guideline is rooted in a time when Bourbon
  was used primarily as a prefixing library, before Autoprefixer was a
  thing and when prefixes were a core need in any project; this is no
  longer the case today
  • Loading branch information
tysongach committed Jul 23, 2018
1 parent 1db985f commit 533167e
Showing 1 changed file with 1 addition and 4 deletions.
5 changes: 1 addition & 4 deletions style/sass/README.md
Expand Up @@ -50,9 +50,6 @@

## Organization

* Use Bourbon for a Sass library.
* Use Neat for a grid framework.
* Use Bitters/`base` directory for styling element selectors, global variables, global extends and global mixins.
* Use [Normalize](https://github.com/necolas/normalize.css) for browser rendering consistency, rather than a reset.
* Use a `base` directory for styling element selectors, global variables, global extends and global mixins.
* Use HTML structure for ordering of selectors. Don't just put styles at the bottom of the Sass file.
* Avoid having files longer than 100 lines.

0 comments on commit 533167e

Please sign in to comment.