Dreamweaver - Locating a css file

Author

Locating a css file

Trent SC

2006-02-12, 6:34 pm

I'm interested in the group's view of where one should save a css file. In
the past I have always saved it to the root directory of the main web site
folder, amongst the html files, but have been told that it is "good
practice" to place it in a separate folder of its own.

While I know that neither makes any practical difference to the
functionality of the site, I'm anxious, for want of a better phrase, "to do
the right thing".

What's the consensus?

Ta muchly.

Michael Fesser

2006-02-12, 6:34 pm

..oO(Trent SC)

>I'm interested in the group's view of where one should save a css file. In
>the past I have always saved it to the root directory of the main web site
>folder, amongst the html files, but have been told that it is "good
>practice" to place it in a separate folder of its own.

Do whatever you like. I prefer a sub directory 'css' for my stylesheets.
The files itself are usually named after their media type:

screen.css
print.css

>What's the consensus?

I don't think there is any. It's jsut personal preference.

Micha

clintonG

2006-02-12, 6:34 pm

My philosophy started right in my bedroom. I put all my socks in a sock
drawer and all of the underwear in an underwear drawer. After I wear them is
when I throw them on the floor -- actually I really am kidding -- I am a
clean machine and keep my room spotless but I think you get the idea. Files
in the root are like dirty socks and underwear on the floor.

So put css files in a "styles" directory. There will come a day when you
will have different style file types and keeping all style file types in a
single drawer will make it easier to manage and reuse the assets.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

"Trent SC" <trent@invalid.invalid> wrote in message
news:dsdppr$d2f$1@forums.macromedia.com...
> I'm interested in the group's view of where one should save a css file.
> In the past I have always saved it to the root directory of the main web
> site folder, amongst the html files, but have been told that it is "good
> practice" to place it in a separate folder of its own.
>
> While I know that neither makes any practical difference to the
> functionality of the site, I'm anxious, for want of a better phrase, "to
> do the right thing".
>
> What's the consensus?
>
> Ta muchly.
>

crash

2006-02-12, 6:34 pm

I keep all of my includes in a "common" or "com" directory. I then use
naming conventions to separate them:

css-main.css
css-print.css
img-Building01.jpg
img-Empl-ShraderJeff.jpg
js-MenuBuilder.js
flash-Ad-42356.swf
flash-Game-TicTacToe.swf
ssi-MenuItems.txt

I find it enables me to a) backup easier on network, as I can simple
zip/transfer one folder instead of an entire site b) allows me to transfer
the entire directory with one click instead of transferring multiple folders
c) makes my code easier b/c I know I can go to root/common/ for anything
that I want to include.

I *used* tokeep my "masters" folder in here as well, but found that
intefered with my backups and transfers as it was simply so large (it's
where the originals of anything emailed or source files are kept). I also
like keeping this above root (now) so that non-paying customers get what
they paid for (the published files) and not what I'm working on (the source
files).

HTH,

Jon

"Trent SC" <trent@invalid.invalid> wrote in message
news:dsdppr$d2f$1@forums.macromedia.com...
> I'm interested in the group's view of where one should save a css file.
> In the past I have always saved it to the root directory of the main web
> site folder, amongst the html files, but have been told that it is "good
> practice" to place it in a separate folder of its own.
>
> While I know that neither makes any practical difference to the
> functionality of the site, I'm anxious, for want of a better phrase, "to
> do the right thing".
>
> What's the consensus?
>
> Ta muchly.
>