I was reading the article Integrated Web Design: Strategies for Long-Term CSS Hack Management: http://www.informit.com/articles/article.asp?p=170511 Referred to by Russ in his very useful "links for light reading" and I read this article.
Amongst other things it suggests not putting hacks into your CSS file, but instead importing them from another external hack file. Like this: [code] /* importing hi-pass filter */ @import "hi-pass.css"; [/code] The article says that by using this method, you have all your hacks in files external to the main css file and can easily be dispensed with when you finally determine that time has moved along and the hacks are no longer required. Fair enough. I understand the point, I think, except that I don't think you gain anything at all by it, except more complexity in the site's file structure. Every hack now represents one more file that has to be uploaded, version controlled, backed up, managed etc. I'd have thought it was simpler to have the hack actually in the main css file, and commented adequately so it was easy to find there. Or am I missing the point? Does anyone else agree? Disagree? Cheers Mike Kear Windsor, NSW, Australia AFP Webworks http://afpwebworks.com ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
