Internet Web Page Development Standards Technical Procedures and Requirements

Back to Web Authoring Homepage Back to Web Page Development Standards

The following items describe and govern the technical procedures and requirements surrounding the creation, testing, and maintenance of district web pages.

1. Pages under development or significant change will be maintained in the WEBTEST directory. This is located at http://www.csd99.k12.il.us/webtest.
2. Security will be granted for WEBTEST when pages need to be placed there for review. One security clearance will allow update rights to the entire WEBTEST area. Since this is a test (temporary) area individual security levels will not be granted. The security password will be changed on a regular basis.
3. Security will be granted to the production web area based on areas of responsibility. For example, a few key people at the ASC, North, and South will be administrators and have update rights to the majority of the web tree for management and control purposes. Others will be developers who have update access only to a portion of the tree (Fine Arts, or Rod’s class pages) for example. All security is defined by specifying the highest point (in the directory tree) of access; everything below that point in the structure is included. Developers must change their own passwords on a regular basis. Administrator passwords will be changed on a regular basis.
4. Directory and file names must follow the 8.3 convention. All names must be in lower case. This will ensure compatibility across platforms and operating systems. This means that files should be specified as .HTM, not .HTML.
5. Users who develop web pages for inclusion in the district site must keep their related HTM files in a single main directory. Each directory must have an INDEX.HTM or HOME.HTM page representing the top level in that area. If a person develops web pages for several different content areas, they would have a directory for each logical content area or project.
6. All graphics files used must be stored in a single sub-directory within the developer’s main directory. This will make integration of the final pages into the district pages much easier.
7. If links are specified to other pages within the developer’s directory, these pages can be referenced simply with the name of the page, e.g. descrp.htm.
8. If links are specified to pages outside of the developer’s directory, the entire path must be referenced. For example, http://www.csd99.k12.il.us/south/math/…..
9. Users who include graphics files in their pages must include the actual graphics file. Real time links to graphics outside the directory structure add unacceptable overhead processing.
10. File names must be as meaningful as possible. Avoid generic names such as page2.htm, page3.htm, etc.