>From Yslow http://developer.yahoo.com/performance/
Reduce the number of css files used Link to them in the top of the page, no inline styles Gzip and reduce the whitespace when going to production. These are fairly simple steps for the average web developer. Visit yslow for more performance tips. _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ross Bruniges Sent: Tuesday, May 06, 2008 4:31 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] :: CSS Code Formatting :: Ultimately you want to use one version during your development process (to ensure readability between your development team) but then have a smaller/compacted version to be used once you deploy to the live server (and at which point it's not the end of the world if your CSS is difficult to read) A best of both worlds approach ;-> ----- Original Message ---- From: Amrinder <[EMAIL PROTECTED]> To: WebStandards Discussion Lish <wsg@webstandardsgroup.org> Sent: Tuesday, 6 May, 2008 2:49:24 PM Subject: [WSG] :: CSS Code Formatting :: Which approach is better? Should we go for code readability as described by Smashing Magazine or follow what Andy said. _____ Sent from Yahoo! Mail <http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http:/us.rd.yahoo.com/e vt=52418/*http:/uk.docs.yahoo.com/nowyoucan.html> . A Smarter Email. ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
