OPEN Web-Page Checklist

Use this checklist to proof your Web pages before publishing them. The checklist covers the main points in the OPEN Web Server Standards & Guidelines. See that document for specifics. You can download this checklist in Word 97 or RTF format.

Filenames:

____

Use all lowercase

____

Do not exceed 14 characters for filename, 4 for file extension

____

Use approved file extensions (html, jpg, gif, cgi, ncgi, mtpl, tpl, etc.)

____

Use meaningful names

Directories:

____

Use all lowercase

____

Contain an index.html file (except images directories)

____

Store images in a project image directory

Markup:

____

Include a meaningful title; title identifies the project (e.g., JITT, OSLIS) and OPEN

____

Include DTD (Document Type Definition)

____

Include meta Review, Pull, OR Archive Date in "dd mmm yyyy" format

____

Include meta Author

____

Include meta E-mail Address for contact person

____

Include meta Keywords

____

Include meta Description

____

Include meta "set: document.modified" date in "dd Mmm yyyy" format

____

Make relative reference to files on the OPEN site

____

Use standard site or project includes for header, footer, and/or project navigation

____

Include text links for image maps or other graphical navigation

____

Include ALT tags for images

____

Include HEIGHT and WIDTH tags for images

____

Call site-wide images from /images

____

Call project-specific images from /project/images

____

Include BORDER="0" tag for linked images

____

Include file size for linked files & downloadable files if larger than 50 KB

____

Comment the HTML source

Content:

____

Read it to be sure it makes sense

____

Proof spelling and grammar

____

Check for "pesky" white spaces (e.g., "adapta ble")

Links/HTML:

____

Test all links, including navigation

____

Validate HTML (HomeSite, Tidy, W3C HTML Validation Service)

____

Test in Lynx

____

Optimize for download time at 14.4 bps

All development work is done on beta. Only after documents have passed quality control should they be published to /open. Important: For Fly/database applications, coordinate with the server administrator before publishing to /open.