CSS is the easiest part of the design cycle. (The hard part is actually mocking something to look great.. implementing it is the fun part.)<p>Creating CSS which matches your design should not really be an issue, and as others have pointed out, if you see something on another website that you like, then you can just use chrome inspector which would always work by an order of magnitude better than using a main.max.css sheet as you suggest.<p>I'm not going to be elitist and say that learning CSS is a non-issue, but maintaining a commented CSS would be ridiculous. Especially when all of my CSS is automatically compliled (lessCSS) and comments are stripped.<p>What would your main.max.css look like?<p><pre><code> .container {
border: 1px solid black; // This adds a solid black border
float: left; // Remove element from doc flow, and align left
padding: 10px; // This adds a 10px padding
background: white; // This sets the background white
}
</code></pre>
When I read the title of this post, I thought that you might of been suggesting that developers maintain two sheets, a<p>[1] main.min.css<p>[2] main.max.css<p>Inside of the min CSS, you might use all of your layouting styles <i>and lightweight background styles</i>. However, inside of the max you would add all of your complementary styles.<p>Such as all of the background gradients. All of your vendor specific box shadows, border-radius', box-sizing, opacitys, etc. Getting background gradients compatible accross different browser vendors totally bloats my CSS (by about a 100-140kb (since I use alot of high quality gradients instead of png).<p>I could perhaps get behind the idea to seperate two sheets. One min.css for pure templating and layout, and a max.css for all that awesomeness.<p>The only benefit this would give is being able to detect a user agent and serve up the more lightweight version.<p>Anyway, big NO NO, for your suggestion. I can't get behind that idea.