logo

Toolbox Banner

HTML File Structure

Main Tools

CleanAir Doctrines

Innovation

Interns

Job Descriptions

Job Postings

Multi-Team Processes

Team Processes

Orientation

Partnershipping

Quality

Staffing

Library

Technical Library

the CleanAir System

Web Page Standards


Toolbox Site Map


Best Practice Team People

Leadership Help



File Structure Guide is Now on the Wiki

The file stucture is as follows:

1. Every 1st level or main page such as cleanair.com or cleanair.net or hotair.com etc. have the following in the main folder:


a. index.html

b. image folder (for images used by more than one sub folder)

c.   2nd level folder for each link or "link group" (an example of a link group is Source & Source Schedule)

d. no other html without a separate 2nd level folder unless approved by the Dreamweaver users group.

e. Move everything that does not have a link in the index to a folder without a index.htm(l) file if you want them to be index by the Google Appliance.


2. Every 2nd level Sub-Folder should have:


a. index.html
b. image folder (for images used only by this 2nd level topic )
c. 3rd level folder for each link or "link group"

3.     3rd level folder should NOT follow the same concept unless ever page in the folder apears as a link in a index page. Use good judgment based on number of documents.


4. Use sub-folders in image folders to group images into logical categories and to limit the maximum number of images in one folder to about 20.

5. Please do not use the following characters in folder names;

$, ! ,+, {,  }, &, [, ],%, #, •, and $

6. Illegal filename characters:

\ (backslash), / (forward slash), : (colon), * (asterisk), ? (question mark), " (double quotes), < (left angle bracket), > (right angle bracket), | (pipe).

Most of these are Windows OS constraints; Mac allows all except a colon (though a forward slash, /, can cause issues for POSIX paths). The aim here is to allow problem-free cross-platform use. An all-Windows or all-Mac organisation may need to interact with others using different OSs, so the safe method is to observe both OS' limitations, even if you mostly/always work on only one OS.

Updated: