You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The web is littered with Ikea-style CSS frameworks and opinionated lowest-common-denominator web design tools. But pre-processors like Sass have opened the door for more flexible toolkits, and a thriving open-source community. You don't need to be a "ninja" with 3 million followers and your own clearfix to contribute. You don't even need a clever new idea — just a willingness to share, interact, and learn. Showing and sharing can help your code and your career.
We'll talk about the complete process of building and maintaining open-source Sass extensions. From concept to documentation, testing, licensing, releasing, and contributing to other projects.
The text was updated successfully, but these errors were encountered:
This is heavily based on my own experience releasing a very rough draft of Susy on the first day I ever encountered Sass or Github. The code was bad, and the documentation was worse — but open-source, community iteration is a powerful thing. I'll show you what I did wrong, and how I learned to do it better.
The web is littered with Ikea-style CSS frameworks and opinionated lowest-common-denominator web design tools. But pre-processors like Sass have opened the door for more flexible toolkits, and a thriving open-source community. You don't need to be a "ninja" with 3 million followers and your own clearfix to contribute. You don't even need a clever new idea — just a willingness to share, interact, and learn. Showing and sharing can help your code and your career.
We'll talk about the complete process of building and maintaining open-source Sass extensions. From concept to documentation, testing, licensing, releasing, and contributing to other projects.
The text was updated successfully, but these errors were encountered: