Re: [css-d] css organization - (divide and conquer) or not?

2007-07-19 Thread Jack Toering
I was wondering what is best You already know this could be a Ford vs. Chevy post, but here is what time has taught me. Unorganized is not the way to go. It will cost you even during the initial development if it isn't organized. This is what shook out from my experience: A, I have one main

Re: [css-d] css organization - (divide and conquer) or not?

2007-07-18 Thread Emanuele Venezia
Personally, I tried once method 2 and lately had to repent for it, because I kept going forward and backward in the file to change the rules or to find a mistake etc. I'm not an expert web developer, but recently I approached another method involving more files. I prefer to have a basic file

[css-d] css organization - (divide and conquer) or not?

2007-07-17 Thread Arian Hojat
I have been looking at some tutorials. and some recommend the usual 'split into basic.css, typography.css, layout.css, colors.css, etc', but I can see a few peoples' arguments that to make a change for 1 thing, you might be looking at changing alot of files. For example, when you want do change

Re: [css-d] css organization - (divide and conquer) or not?

2007-07-17 Thread Paul Hanson
One thing to consider for your 3rd idea is that if you have to pass the project off to someone else, the other two methods require the new person to understand your logic and why you split things up into multiple files. This could lead to frustration on their part if they don't fully understand

Re: [css-d] css organization - (divide and conquer) or not?

2007-07-17 Thread David Hucklesby
On Tue, 17 Jul 2007 13:18:17 -0400, Arian Hojat wrote: I have been looking at some tutorials. and some recommend the usual 'split into basic.css, typography.css, layout.css, colors.css, etc', but I can see a few peoples' arguments that to make a change for 1 thing, you might be looking at

Re: [css-d] css organization - (divide and conquer) or not?

2007-07-17 Thread Don Stefani
Or... Just use some comments to explain what each file does. If your reason for splitting things up is valid, then share the reasons and explain. The next person may think you are smart and write sexy code. And you know, chicks dig sexy code. - dstefani

Re: [css-d] css organization - (divide and conquer) or not?

2007-07-17 Thread Arian Hojat
Cool thanks. I think I'll stick to 1 file and separate by areas on the page (generic/basic rules for page; nav, header, content, mainContent, sidebar, footer, etc). Sometimes I get the rule that applies to generic things like a hyperlink in nav, header, content areas, so im not sure where to group

Re: [css-d] css organization - (divide and conquer) or not?

2007-07-17 Thread david
Paul Hanson wrote: #Method3 - have to change 1 files, un-organized .posts{ color: orange; background-color: black; font-size: 1em; font-family:Verdana, Arial, Helvetica, sans-serif; float:left; width: 200px; } I was wondering what is best, for a quick job, i'd probably do #3; but for a

Re: [css-d] css organization - (divide and conquer) or not?

2007-07-17 Thread Rakesh Pai
May I add: Method 4: /* Header styles */ div#header { /* all header related styles, making no distinction between of layout and typography */ } div#header img { /* style rules for the logo */ } /* Navigation */ ... /* Content area */ ... /* Footer */ ... I personally find this to be