To provide a structured, scalable and maintainable component-based architecture that is well documented and easy to use.
But what does that really mean?!
Structured: predictable structure makes everyone's life easier. You can simply glance at the code and can understand a variety of characteristics about how the UI hangs together.
Scalable: Blaze utilises ITCSS; a proven method of managing large scale CSS. It is also modular, so you can take only what you need, or take it all! It's got a small footprint.
Maintainable: the hardest parts of building a CSS framework is the difficulty in maintaining it. Blaze hopes to improve that experience by utilising BEM naming conventions and ITCSS methodologies to provide meaning and context to the code.
Well documented: A product should always be well documented in my opinion. It makes it easier to use, provides help when needed and ratifies the thinking of the product creator. Documentation takes a lot of effort but it is worth it.
Feedback from users of Blaze so far has been positive, but this is only the beginning.
So why back Blaze development?
Building, maintaining, writing documentation, addressing people's issues and pull requests takes a considerable amount of time and effort. Time and effort you as a consumer don't have to invest in yourself.
Sponsoring Blaze development sends a clear message that your product relies on an actively maintained open source project. It makes business sense if you're using Blaze in a commercial environment and gives you peace of mind as an individual developer or freelancer.
Not to mention a warm fuzzy feeling in your heart!