Show HN: inuit.css—lightweight, Sass-based, OOCSS framework(inuitcss.com)
inuitcss.com
Show HN: inuit.css—lightweight, Sass-based, OOCSS framework
http://inuitcss.com
3 comments
Have you tried http://foundation.zurb.com/?
It seems to be a more designer-friendly framework.
Haven't tried inuit.
It seems to be a more designer-friendly framework.
Haven't tried inuit.
Bootstrap sites only look cookie cutter if you use the default styling out of the box. If you take time customize the styles, you can get fairly differentiated sites.
Check out some of the styles on https://wrapbootstrap.com/.
Check out some of the styles on https://wrapbootstrap.com/.
Project creator here! If anyone has any questions then please fire away. This blog post may also shed some light on a few things: http://csswizardry.com/2012/09/inuit-css-v4-oocss-sass-and-m...
Cheers, H
Cheers, H
What was the inspiration for the name?
I was discussing wanting to build a decent framework with my ex, and I said it would be a ‘cool’ thing to do. A brief bit of word association to-and-fro and me being reminded of the lyric/phrase ‘Cooler than a polar bear’s toenails’ I/we arrived at Inuit :)
Made me immediately think of QuickBooks: http://www.intuit.com/
For a brief instant I thought it could be an official release from them, but then I realized they aren't that cool of a company.
For a brief instant I thought it could be an official release from them, but then I realized they aren't that cool of a company.
Any reason it's all contained in one file instead of broken up?
Broken it up! Thanks :)
https://github.com/csswizardry/inuit.css/blob/master/inuit.c...
https://github.com/csswizardry/inuit.css/blob/master/inuit.c...
I personally like working that way, but I think I might split it out so that dropping an object only takes deleting one line from a file and not dozens :)
More importantly when people contribute or wish to extend the project they can do so by adding a new module file instead of editing the existing code. Open closed principle.
Also if people are importing using SMACSS they can also select individual modules to import if they prefer that to importing everything.
Also if people are importing using SMACSS they can also select individual modules to import if they prefer that to importing everything.
Why would you want to break it up?
As far as I'm concerned CSS is no different than any other code and should be separated into modules so it's easier to read and understand. This is especially true if you're using something like SCSS.
This SMACSS book recommends this and frameworks like Bootstrap and Foundation pretty much follow that approach.
This SMACSS book recommends this and frameworks like Bootstrap and Foundation pretty much follow that approach.
For a framework it might be a nicer option, so that you can drop a module by only deleting the include reference rather than permanently deleting dozens of lines. Perhaps. It’s largely down to taste I imagine :)
I recently used a bastardisation of v3 and v4 (I was using v3 then you released v4) and I split each object into separate files and left the imports commented out in the main.scss file.
I then uncommented each object as I used it so I didn't reach the end of the project with unused objects in the CSS and not being able to remember whether or not I had actually used them.
I did a similar thing with the grid module: commented out all sizes and uncommented what I used as I went.
I then uncommented each object as I used it so I didn't reach the end of the project with unused objects in the CSS and not being able to remember whether or not I had actually used them.
I did a similar thing with the grid module: commented out all sizes and uncommented what I used as I went.
The trend lately seems to be immediately reaching for Bootstrap, which is a little bit shameful for those who might consider themselves legit front-end devs. While bootstrap is a great tool for prototyping, it's also led to a lot of boring, cookie-cutter apps.