Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: Where to keep css files?

  • Subject: Re: Where to keep css files?
  • From: Roy Schestowitz <newsgroups@xxxxxxxxxxxxxxx>
  • Date: Mon, 29 Aug 2005 16:30:48 +0100
  • Newsgroups: alt.html
  • Organization: schestowitz.com / MCC / Manchester University
  • References: <89thd3851bf7.dlg@ID-104726.news.individual.net>
  • Reply-to: newsgroups@xxxxxxxxxxxxxxx
  • User-agent: KNode/0.7.2
__/ [Jim Scott] on Monday 29 August 2005 15:00 \__

> On my site which is mainly images, I keep my images in a separate folder,
> mainly because it makes them easier for me to find.

That's a good thing. When you have too many images, consider subdirectories,
but _DO NOT_ move existing images from ~/img. Crawlers index them and
refresh their indices for images very, very infrequently. Consider adding
new files in subsubdirectories too (see reason below[1]).

> Every .htm/.html page
> uses two css files.
> Does it make any difference to loading speed whether I store the css files
> with the images ot in the main site?

The performance penalty would be merely proportional to putting an extra
straw on a camel's back.

Put CSS files in ~/css. It would give you to better room to expand while
remaining tidy. It also would make your source code more elegant.

> It may not matter, but I noticed the Nvu stores all files other then
> .htmls together and I wondered if there is a good reason for this.

Maybe historical reasons should be considered here. My site is quite messy
due to changes in scale that occurred through the years. If it weren't for
crawlers (or laziness), changes would have been made. I am sure that even
the largest businesses started small too.

[1]If you view or list files in a directory with thousands of files, loading
time can be horribly affected. There are more issues to consider like
naming collisions, extensibility and so forth.


Roy S. Schestowitz        "These characters were randomly picked"

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index