| |
Web Publishing Policies, Procedures
and Guidelines
Policies
Procedures
Guidelines
Policies
- Policy
and procedures must be reviewed annually by the CLDH.
- Guidelines
must be reviewed every six months by WETWG due to rapid change
in web publishing technology.
- All pages
must be in compliance with the WKU policies and applicable state and
federal laws, including copyright.
- All pages
must be in compliance with the WKU World Wide Web Publishing Policy.
- Content
must be consistent with and in support of WKU and University Libraries
mission statements.
- WKU logo
must appear on the UL home page as a link to the university home page.
- UL banner
must appear on top of the UL home page.
Go
to top
Procedures
- All page
proposals must be submitted to the Special Assistant to the Dean for Web & Emerging Technologies.
Major projects must be reviewed by the CLDH before they are sent to
the WETWG for discussion about its design and development.
- Department
heads are responsible for the content of their department home page
and area librarians are responsible for the content of their area pages.
- UL Web
Site is to be designed and maintained by the Web & Emerging Technologies Working Group (hereafter WETWG) with the
Special Assistant to the Dean for Web & Emerging Technologies (hereafter Special Assistant) overseeing
the integrity of its directory tree. WETWG members and the Special Assistant must maintain good communication when managing files in
the web servers to prevent irreparable damage to the files and the file
system.
Go
to top
Guidelines
General
- Each
topic must be stored in a separate directory
- Directory
and file names must be meaningful and easy to type and remember.
- Information
must be kept as accurate and current as possible
- Content
must be grammatically correct with no spelling errors
- Do not
activate a link unless it leads to a document that is available. Links
that need to be in the code as a reminder must be commented out to hide
from the users' view.
- "Under
construction" or "Not available" must be used sparingly where there
is an ABSOLUTE need. "No link, no show."
- Include
a warning if a link will lead to an extremely large file, such as the
library tour movie
- Outside
links must be checked periodically to make sure that they remain active
- Color
scheme of UL pages shall adapt to that of the university homepage
- All-capital
headings are to be prohibited
- Footer
of UL homepage must include:
- Date
that the page was last modified
- WETWG
as maintainer of the page with link to the team's web page
- Email,
Phone, Fax, Snail mail address of UL
- Copyright,
WKU
- Site
URL
- Counter
- All UL
Web pages except the home page must use the dlts.dwt template
- All UL
Web pages except the home page that do not belong to a specific department
or unit must use the library_nomenu.dwt template
- Faculty/Staff
pages must use the faculty_bio.dwt template
- Sub area
pages must use sub area libraries, a template-like file ending with
extention .lbi, such as dlps.lbi for the Department of Library Public
Services
- For quality
control, individual WETWG member's name must be inserted as comment within
the <head> </head> tags of the page he/she last maintained
it
- Authors
other than the WETWG must appear either on top or at the bottom of the
pages they created, with WETWG as maintainer in the footer
Go
to top
Technical
- Consistent
Navigation
- To
guarantee consistency, use of template and library files are enforced
- Each
page must explicitly tell the users their current location by giving
its URL in the footer
- Browser
and Accessibility
- Pages
must be checked on Netscape Version 4.0+ and Internet Explorer 5.0+
browsers
- Text
only alternative must be provided to the UL home page
- UL
Web site must be ADA compliant
- Screen
Size & Space
- Screen
size must not exceed 760 pixel wide to avoid horizontal scrolling
- Generally,
Page length must not exceed 3 screen heights. Where a long page
is required such as the Web Index, Site Map and Glossary of Library
Terms, an Index and/or navigation to the top of the page must be
provided at the interval of about a screen length.
- HTML
Authoring
- Mark-up
must be in compliance with the prevalent HTML standards. New standards
are still evolving and not necessarily to be adopted.
- Adopt
browser specific extensions supported by the most popular browsers
- Frame
shall be used sparingly
- Visual
Graphic Editors that force non-standard HTML codes must be avoided
Files created on Mac machines must be saved as "DOS with Line Break"
format.
- Mark-up
must be made readable by other authors:
- There
must be vertical stack up
- Tag
case must be consistent
- Isolate
key elements must be on separate lines
- Comment
wherever it is necessary with plain, descriptive language
- Page
formatting
- Use
invisible tables and transparent gif spacers to maximize the
layout of a page
- Width
of tables must be set to a percentage whenever it is possible
- Pre-formatted
<pre> </pre> tags are to be avoided. Use line breaks
or tables instead.
- Title
must be short and meaningful
-
Meta tags must be used to facilitate search engine indexing
- Use
white color background and dark color text for all pages. The reverse
is prohibited. Use default blue for hyper links with hover texts
set as red
- Content
text:
- Header:
default font with size 5
- Text
area: venada with size -1
- Colors
must be web-safe, as are available in the Dreamweaver color pallet
- Image
- Images
must provide useful, visual clues about the content. Create original
graphics. If borrowing a graphic is necessary, credit must be given
in the Mark-up.
- Depth:
72 dpi
- Graphics
must meaningful, their numbers necessarily miminal and sizes reasonablly
small. Use thumbnails to lead to larger pictures
- Correct
size dimension must be provided in the <img> tags
- Animation
must be used sparingly. There shall be no loops unless absolutely
necessary
-
Pictures introducing a page must be activated with invisible borders.
- Images
must include "alt" in the tag to provide alternative text for non-graphic
browsers or users of graphic browsers who tend to turn graphics
off.
- Interlace
the graphics if possible
- Use
transparent gifs instead of blocks of images when necessary
- File
formats
- jpg
for photos
- gif
for inline pictures
- png
for graphics that need revising constantly
- New
Technology
- JavaScript
JavaScript can be used to add functionality to a web site and aid
with navigation
- Java
Applets
Java applets must be prohibited in any of the UL pages.
- Plug-ins
Flash movies, Shockwave, MP3, RealPlayer, etc. must be used judiciouly.
If one is required by the content as in some special event pages,
a link to download the necessary plug-in must be provided. An alternative
page that does not require C
|