On 7/19/2007 4:11 AM, -Lost wrote [in part]:
Quote:
Originally Posted by
And by assets, just in case it is a moronic term, I mean CSS,
JavaScript, images, server-side includes et cetera.
>
Primarily I am worried about just the CSS, JavaScript, and image aspect.
>
I've always for example, separated, layout and positioning from say
style or how elements should look. So for each "theme" I might have 2
CSS files. They would go into a directory like /theme/theme_name/css
I structure my site in a way that facilitates maintenance. For that,
one of the most important considerations is locating all files relating
to a particular topic. Thus, if I have 5 or more Web pages relating to
the same topic, I generally place them into a subdirectory for that topic.
I have a single, global CSS file in my main directory. If I need
additional styles or need to over-ride a style for a subdirectory, I
place the CSS file for that into the subdirectory containing the HTML
files. (I also have a reprints.css file in my main directory to
over-ride my global CSS file; reprints.css is used to format pages that
are reprints of newspaper pages.)
Image files that are used by files in my main directory or that are used
by more than one subdirectory go in my main directory. Image files that
are used by only one subdirectory go in that subdirectory.
For all of the above, references within a subdirectory are done relative
to that subdirectory. References to other subdirectories are relative
to my site's main directory. This will facilitate moving my Web site if
I decide to change hosting services.
Because of the way SSIs are accessed, all my SSI scripts are together in
the same /cgi-bin subdirectory. This is not my choice; this is dictated
by my ISP's Web server, which hosts my site.
--
David E. Ross
<http://www.rossde.com/>.
Don't ask "Why is there road rage?" Instead, ask
"Why NOT Road Rage?" or "Why Is There No Such
Thing as Fast Enough?"
<http://www.rossde.com/roadrage.html>
