Skip to the content of the web site.

Web Operational Management Group

CSS Group Report
Implementation Plan

The conversion does not necessarily include a redesign of the page. Generic templates (with associated CSS files) have been prepared to cover the current formatting of most pages. Some specialized sections may require their own templates (e.g., UMD Library web site, news @ your library, discipline pages) that will be created by WebOps.

Scope of the Project

Steps for the Conversion

  1. Charles burns the Library Web sites to a CD for archival purposes. (Freeze placed on editing during this process.)
  2. Esther runs Linkbot and sends individual messages to web maintainers identifying orphan files in their directories.
  3. WebOps arranges an information session for all Web Maintainers to introduce them to the project, explain how they can help prepare their files for conversion, and show them how they will be able to maintain their pages after the conversion. Written instructions that explain updating will be available for them after the conversion is complete. (see draft)
  4. WebOps arranges a group training session for the Implementation Team to provide instructions on how to convert existing pages to the new template/CSS format. Written instructions will also be available (see draft).
  5. WebOps needs to make sure that all web maintainers have Dreamweaver MX on their computers and that their Dreamweaver preferences have been set for XHTML.
  6. Web maintainers prepare files for conversion:
    [Note: Many of the points outlined below are currently being handled by David Smith as he validates documents to XHTML 1.0 Transitional and ensures that pages are accessible. So much of the preparation work is underway.]
    1. Clean up orphan files.
      The easiest way to convert a directory is to just start at the top and work through it. Converting orphan files wastes valuable time. Therefore, it is important to clean out orphan files from current directories
    2. Identify the document structure
      The document's structure needs to be clearly marked. This means that headings should be enclosed in heading tags (e.g., <h1>, <h2>). Instead of using <b> for bold and <i> for italics, we now use <strong> and <em> which communicate that the item or concept is more important or needs to be empasized.
    3. Remove document formatting
      Any formatting on pages should be removed, especially blockquotes (for indent) and font tags, if possible. Appearance of the page will be handled by the new templates/CSS prepared by WebOps. The main tags that should remain are the headings, <strong>, and <em> tags.
    4. Ensure all internal links are relative links
      Conversions will be carried out in a copy of the original directory. If relative links are used, then the converted directory can simply be renamed to replace the original directory without creating internal broken links.
    5. Validate pages to XHTML 1.0 Transistional
      By starting the conversion with valid XHTML documents, the process is quicker because less work is then required to produce a valid page based on a template.
    6. Check the page for accessibility
      All of these steps move the page toward a more accessible page. In addition ensure that all images have meaningful alt texts.
  7. An Implementation Team handles the conversion of all pages to use CSS and templates. The team works through the site on a directory by directory basis. Conversion on an individual directory can begin after the web maintainer has completed the preparation outlined in step 6. It is expected that directories will be at different stages of development.While a directory is being converted, a freeze on editing changes is made on the current directory.
  8. WebOps ensures the CSS-based navigation bar is applied to pages on lap2, webdev, Google, OpenText, etc. The CSS-based navigation bar is part of the new templates and will be applied to pages in htdocs as they are converted to the new format.
  9. When the conversion is complete, the web maintainer checks all pages to ensure all is in order. If the pages are working properly, they then notify the Implementation Team member who makes the converted pages live and deletes the old pages from remote site. If web maintainers wish to keep the old files, they can save them on their local Dreamweaver site.
  10. Esther will continue to run Linkbot throughout the process to ensure that internal broken links can be identified and corrected.

Implementation Team

Conversion of the Library Web will be handled by an expert group of maintainers: Marian Davies, Ted Harms, Linda Hastings, Val Huggan, Cheryl Kieswetter, Rose Koebel, Esther Millar, Marina Wan

Timeframe

To begin as soon as possible and to finish by the end of the summer.

Members:

Esther Millar, David Smith

If you have any queries or concerns about this page, please contact .

November 2, 2006