Table of Contents:
Introduction
Principles
Preliminary Analysis
Mechanics
General HTML Concerns
Specific HTML Concerns
Graphics
Required Elements
|
|
Mechanics
The preferred format for content on the web is HTML
(with .gifs and .jpgs for graphics). A second choice for formats
would lie in Web-incorporated formats, such as Adobe Acrobat (PDF),
Postscript, and other formats that are viewable using free web
'helper applications'; followed by formats that require a downloadable
plug-in application. Unconverted files created by
productivity applications, such as Wordperfect, Quattro Pro, Lotus,
or Powerpoint, should provided only as a last resort, or for
collaboration within the University, and should be supported with
translations in HTML whenever possible.
To support the widest possible range of accessibility, adherence to
standards
is expected. Official pages should be designed using generic, not
browser-specific, HTML. Familiarity with and use of
accessibility guidelines is strongly recommended.
Documents, file names, and directory names should be constructed
to facilitate ease of maintenance. Platform-specific file and directory
name conventions should be avoided if at all possible. Subdirectories
should be used to group files by context and/or subject.
Lehigh does not endorse or specify any specific
browser or HTML production package. Displaying META FORMATTER tags or
Best Viewed with... text or graphics for a specific browser or
formatter is highly discouraged.
Directory structure:
- The main directory should contain the home page in a file with
an identifiable file name (use
index.html to
automatically display the home page rather than a directory tree).
- The file names should be meaningful and descriptive.
- The home directory should have a README file that contains
information about the logical and physical structure of the pages.
- The account should incorporate the use of sub-directories that
reflect the presentation of information.
- relative pathnames should be used within subdirectories.
|
|
