I'm going to have to balance looks with ease of use ... The looks of the uncompressed generated file(s) is kinda gnarly, but /* ... */ style comments are easier than //'ing every line (though, ST2 Cmd + / is pretty easy).
I'm definitely not pleased with the look of my uncompressed generated CSS. Anything I can do to make it look better, I guess I'm game to do ...
The uncompressed version of my CSS has a whole bunch of comments that don't go with any CSS (for various reasons).
From what I can tell, only
// ...comments will get removed when SASS is set tostyle : 'expanded':Multiline SASS comments
The docs: http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#comments
I'm going to have to balance looks with ease of use ... The looks of the uncompressed generated file(s) is kinda gnarly, but
/* ... */style comments are easier than//'ing every line (though, ST2 Cmd + / is pretty easy).I'm definitely not pleased with the look of my uncompressed generated CSS. Anything I can do to make it look better, I guess I'm game to do ...
Don't forget about:
http://jacobrask.github.io/styledocco/
... that was mentioned in a SASS issue/thread.
Looks like there's a Grunt task:
https://github.com/indieisaconcept/grunt-styleguide
I <3 Grunt!
I'd probably want to generate docs based on the pre-SASSed version of the code.
Need to explore my options here.