# display {nice}
## CSS Utility Class Mashup

Taking the parts I liked most in [Tachyons](http://tachyons.io/), [Shed CSS](http://tedconf.github.io/shed-css/) and [Beard](http://buildwithbeard.com/) and mashing up my own set of utility classes.

Under active development, please don't use anything and rely on it, it can and it will break.

## Ideas
- I love the general concept of Tachyons' feature set and the overall naming conventions, but I miss easy ways to extend the core features
- I like Beard's easy extendability, especially when it comes to custom breakpoints, but I'm not too fond of class names and breakpoint prefixes
- I prefer Shed's method to trigger responsive states using the _at-syntax_ (`@xxl`)
- I need an easy way to change and add new breakpoints
- I need to be able to drop the framework into existing Sass projects
- I want to use [Mappy Breakpoints](https://github.com/zellwk/mappy-breakpoints) to manage and apply breakpoints
# {display: nice}
## CSS Utility Class Mashup

Taking the parts I liked most in [Tachyons](http://tachyons.io/), [Shed CSS](http://tedconf.github.io/shed-css/) and [Beard](http://buildwithbeard.com/) and mashing up my own set of utility classes.

Under active development, please don't use anything and rely on it, it can and it will break.

## Ideas
- I love the general concept of Tachyons' feature set and the overall naming conventions, but I miss easy ways to extend the core features
- I like Beard's easy extendability, especially when it comes to custom breakpoints, but I'm not too fond of class names and breakpoint prefixes
- I prefer Shed's method to trigger responsive states using the _at-syntax_ (`@xxl`)
- I need an easy way to change and add new breakpoints
- I need to be able to drop the framework into existing Sass projects
- I want to use [Mappy Breakpoints](https://github.com/zellwk/mappy-breakpoints) to manage and apply breakpoints
Fix curly braces of project name ^^
Fix curly braces of project name ^^