Change style.css to main.css

[corydorning]

Does it make sense to go ahead and change style.css to main.css to provide some consistency with the recent change of script.js to main.js.

I realize there was more to it than just the name 'script.js' (RequireJS) and that there's only one CSS file, but it seems, dare I say, more 'semantic'.

[davidmurdoch]

I personally split style.css into common.css (css normalization), main.css (for author stuff), and helpers.css (.visuallyHidden, .clearfix etc). I don't like having to scroll all over the place to find my "author" styles.

I always thought style was redundant ... its a Style Sheet; we already know that it contains styles.
Anyway, I'm +1 on the name change (and for splitting them into 3 parts to be concatenated by the build script, of course).

[corydorning]

agreed. for me its a base.css (which includes normalization and helpers) and main.css for site specific styling.

[necolas]

I quite like this idea too, even if it's just for project consistency.

[chenzihui]

+1 on name change for consistency with main.js

[Gavrisimo]

+1

[jonrundle]

+1 for main.css

[grayghostvisuals]

+1 for consistency and main.css

[jacobbednarz]

For large projects I would agree with @davidmurdoch however for this project, I think consistency is more important. +1 for the name change to main.css

[necolas]

For large projects, you should really be using more than 3 CSS files anyway :)

[Gavrisimo]

For large projects you should really be using css preprocessors... ;D

[jacobbednarz]

That's opening a whole new argument there @Gavrisimo :p

[wamatt]

I'm with @corydorning @davidmurdoch on the the idea of seperating the normalization and helpers out from the site specific code.

[drublic]

Please have a look at PR #1140. There you can see an approach to that.