grumpywizards

5 ms·

1. 1.▲
   by grumpywizards 10y ago

   Any feedback you can give would be appreciated ;)
2. 2.▲
   by grumpywizards 10y ago

   Blaze doesn't mention Bootstrap specifically regards opt in. But Bootstrap does apply CSS to some elements without permission. Foundation even more so. SemanticUI too. Blaze is different than all of these in that it gives the power bac
3. 3.▲
   by grumpywizards 10y ago

   Fixed ;)
4. 4.▲
   by grumpywizards 10y ago

   Mentioned above: It's un-opinionated as in styling is drawn back but not to the point of it being ugly. Look at a Blaze site and it doesn't look like a Blaze site. Everyone can tell when a site has been Bootstrapped. It's aim
5. 5.▲
   by grumpywizards 10y ago

   Single Reaponsibility principal. Create a class called .button. The responsibility of that class is to define what a button looks like. Then create a class called .button--primary whose sole responsibility is to define what a primary button
6. 6.▲
   by grumpywizards 10y ago

   Could raise an issue in the repo if it's still a problem?
7. 7.▲
   by grumpywizards 10y ago

   Thanks! Worked hard on the grid!
8. 8.▲
   by grumpywizards 10y ago

   From my experience this is a non-issue in the OSS environment, you got to pick your frameworks based on other criteria; popularity, fit for purpose, community engagement, learning curve to maintain yourself etc. All of which has nothing to
9. 9.▲
   by grumpywizards 10y ago

   It's un-opinionated as in styling is drawn back but not to the point of it being ugly. Look at a Blaze site and it doesn't look like a Blaze site. Everyone can tell when a site has been Bootstrapped. It's aiming for an un-opi
10. 10.▲
    Show HN: BlazeCSS. Modular Customisable and Lightweight CSS Framework(blazecss.com)

    1 points by grumpywizards 10y ago|0 comments