Re: Directory structure for multi-page site

Hubert,

It seems the method Dan describes is the most common method of organization
that I've observed in my travels on the internet.  I recently began using it
myself.  One advantage to having files such as images in their own directory
is you can quickly locate them for reuse in any other page on your website
while not chewing up anymore of your valuable webspace for multiple copies.
For large websites, your concern over accidentally deleting the wrong file
is valid.  Programs such as Front Page and Homesite have website management
tools to help with this.  Whether you have management tools or not, two
additional suggestions I can make:

1. Always mirror your website on your computer.
2. Backup your computer regularly.

hth,
Steve

> From: "Daniel McMurray" <mcmurd(at)ccaa.edu>

> I recently got really anal about my directory structure.  It may seem like
> overkill, but it works for me.
>
> I keep large subsections of sites in their own subdirectory.  I also keep
> a main Images (or Sounds or Whatevers) directory, using the same directory
> structure as the subdirectories for my HTML pages.  It could potentially
> look like this;
>
> Root (with index page, maybe smaller subsections)
>  |
>   - Foo (dir, with only HTML pages)
>  |
>   - Bar (dir, with only HTML pages)
>  |
>   - Images (dir)
>     |
>      - Foo (dir, with images associated with /Foo)
>     |
>      - Bar (dir, with images associated with /Bar)
>
> I keep commonly used images, like spacer.gif, simply in the /Images
> directory.  I like this method because the directories tend to be less
> crowded, and therefore easier to find files.
>
> This is probably just me, though.  I'm an organization nut when it comes
> to this stuff.
>
> On Wed, 12 Jul 2000, Hubert Earl wrote:

> > Hi,
> >
> > I'm building a web site composed of a number of web pages, with image
> > and sound files.  I'd like to put it in some sort of directory
> > structure, so that all the pages and accompanying files aren't in one
> > directory.  Which of the following structures would be best, in terms of
> > allowing me to make changes without deleting files belonging to the
> > wrong page for example?
> >
> > 1.  Putting each page and its accompanying files in separate directories
> >
> > 2.  Putting all pages in one directory, but with the image and sound
> > files associated with each in separate directories
> > 3.  Some other way of organizing them that you can suggest

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA