ITCSS improvements (on WP projects too) about generator-chisel

[thymikee]

Apart from above, I'd like to adjust our current ITCSS structure.

• Move normalize to generic/ dir
• Make clearfix a mixin instead of placeholder beacuse of known problems
• Use BEM naming. Add .footer__list and .footer__list-item to _footer.scss component plus couple of extra components. Developers are more likely to follow a given pattern if there is such, so we need to provide good foundation :)
• Add more documentation on why we're using ITCSS

[luboskmetko]

Sounds good!

One thing - how would you move normalize to generic if normalize is installed via npm?

[thymikee]

Maybe there's an issue I'm not aware of, but doing

/* generic/_reset.scss */
@import 'normalize-scss/sass/normalize/import-now';

inside e.g. generic/_reset.scss works for me, as it's just an import from node_modules.

[luboskmetko]

Ok, thanks

[danekszy]

Hey guys.
@thymikee All suggestions look good to me except No. 3...
I wouldn't drop the c- prefix for classes, since doing so would make it less obvious whether (the previous) developer followed the guidelines or not. This way I wouldn't be able to tell if something is a component class, or some deviation from our recommended style (or even some 3rd party vendor stuff).

[luboskmetko]

I had doubts about no. 3 as well, I would rather stick to the convention. On the other hand, if writing c- over and over would bother developers or make them sick of ITCSS, we could allow this small departure from the standard or let developers decide ("Components' class names can be written with .c- prefix or without it...")

[thymikee]

Ok, so let's leave it to promote good practices and avoid confusion for newcomers.

[arturkot]

Just wanted to write I'm glad we decided to keep c- prefixes. :)