Why I crafted my own SASS framework

Why I crafted my own SASS framework

I always loved simplicity and all the benefits that come along with it, such as flexibilityextensibilityorganized stuff, and so on. And I always hated things that did a lot of stuff I never needed.

Also, I have my own preferred way of writing CSS and HTML and couldn’t cope with most of the available frameworks around that time (and even now), simply because they don’t make sense for me. I am in no way an arrogant bastard saying I’m doing the best things and everything, it’s just me not liking some way(s) of implementing and using things.

And the things I like to use are also the things I reuse a lot of times, so in the long run, it’s better to have them together, well-organized and in place, ready to be reused when I need them.

Since I discovered SASS, I fell in love with it and its beautiful ways of writing modular and flexible code that will result in well-organized CSS code. I also loved the Ruby-ish clearconcise and elegant programming idioms it has (since it’s based on the Ruby programming language), so SASS was definitely the way to go for me in the world of CSS preprocessors.

Not long since diving into SASS, I already created some reusable stuff such as small components, some useful and commonly used mixins and functions, and was already using them frequently in my projects. That’s when it came to me it was time to craft my own SASS framework, with all the stuff I oftenly use bundled in it.

Along with its simple way of doing things, flexibility and modularity, I also wanted to make available all of its core and 3rd party components, and I created for it a Component Manager, where I stored in an organised way all the components available to use, with HTML code attached to each of the components, making it easy for everyone to grabchange to fit needs, and use.

The framework’s features are very loosely-coupled, meaning you can add, change, or remove any feature without harming anything in the framework. Just keep what you really need and add your own stuff and what you might need further.

As the framework grew and matured, I decided it’s time to share it with other people and this is just what I did few weeks ago, making it available on Github and on its own website at http://www.html5depot.com/blackhole/.

I am also preparing to release a second version of it which will be more granular that it is now, facilitating an even more organized structure and array of features.

Post Comment