The first thing that the chapter regarding Performance and Organization takes up is establishing a structure for your CSS.
Whilst I'm well aware that the approach made towards separation of similar classes into multiple files is a good one, I've seen it argued that the usage of @import or linking multiple stylesheets has a significant impact on performance.
The guide even mentions the important practice of combining all styles into one stylesheet in order to avoid multiple http requests, but only later on, in a different section.
I don't think the first section does a good job at stressing this. It ought to at least mention that some form of preprocessing should be present here, if only to minify and combine the files.
To me, it seems a bit counter-intuitive that this first section of the guide could be interpreted incorrectly by a newcommer (''I should separate everything and include it all in a nice, fancy list of link tags!'')
Just some feedback. I must say that I feel like the guide so far is representative of most of the gems I came across whilst trying to improve my webdev, doing small-company websites on the side whilst studying, starting with some basic HTML3/4 and CSS2 knowledge and working on 3-4 projects over the course of 2 years.
It's what I now wish I had known before diving into my first project.
Just some feedback. I must say that I feel like the guide so far is representative of most of the gems I came across whilst trying to improve my webdev, doing small-company websites on the side whilst studying, starting with some basic HTML3/4 and CSS2 knowledge and working on 3-4 projects over the course of 2 years. It's what I now wish I had known before diving into my first project.