Current State: A Web Development Framework is Needed 

UCSC s first generation web pages, developed in the mid 1990s, and provided a satisfactory, if not 

always excellent, roadmap from the top of the site to a variety of UCSC web pages. A redesign of the 

upper level pages enhanced the first generation site. A second generation redesign of the upper level 

web pages, indexing and categorizing sites by audience type, was accomplished almost three years 

ago. In that same period, a few units' web sites were enhanced, providing a third generation level of 

interactivity between web authors and site visitors. 

UCSC s web presence, particularly at the deeper levels, is inconsistent in terms of the quality of the 

pages, the accuracy of the content provided, and the maintenance of that content. In addition, it s 

becoming increasing important that UCSC develop a portal option that will enable the campus to 

"push" information to many audiences, including current students, potential students, alumni, faculty 

and staff, and others AND enable those users to receive content that is based on their relationship to 

UCSC. In the fourth generation phase, we envision relationship based content delivery portals to 

manage the quality of info that UCSC pushes to potential students, alumni, current students, faculty 

and staff.  

Some of UCSC s web sites are of a very high quality. They provide users with up to date information, 

have a professional and consistent appearance, and are maintained by units that care about providing 

their audiences with interesting, informative content. 

Others are not of that quality. They provide users with sketchy information; they are not designed 

with the audience in mind, look unprofessional, and are sporadically maintained.  Moreover, a rapid 

rate of staff turnover, a need for specialized training, and a high degree of disparity among web 

authoring tools can make it difficult for departments to conform to campus wide standards. 

In addition, UCSC s web presence suffers from a lack of coordination regarding baseline information 

that should appear on certain sites. For example, shouldn t ALL academic departments have standard 

links that appear on their sites, even if the web developer chooses not to use a template? Sites at 

UCSC are created by individual units/departments, with no (or little) regard to how the individual sites 

fit into the overall UCSC web presence. One important tool for web application developers is a 

community where they can share ideas, algorithms, code and resources.  A critical need here is that 

web application developers need the time to be able to participate in this community.   

The Public Information Office has published UCSC Web Policies and Guidelines, including site 

standards and templates at 

http://www.ucsc.edu/resources/policy.html

 However, these polices are 

not well known or frequently referenced, perhaps because those who have taken on web development 

responsibilities are somewhat isolated in their respective departments. Web sites are often developed 

and maintained within the margins of existing responsibilities and resources. In many departments, 

administrative assistants develop and post web pages in addition to their busy jobs. Web site support 

has been carved from small percentages of existing positions, with little new funding. Consequently, 

web developers and authors may be untrained or insufficiently trained, may not have appropriate 

support or resources to perform their duties, or receive the oversight and guidance for Web site 

quality and compliance. In short, we need to  build community  and an organizational framework for 

optimal web development. Defining the components of a web development framework is the main 

focus of the committee.  

_________________________________________________________________________________

Web Services Committee 

Page 5 

May 28, 2002