WebDev 2000

Glendale
Community
College

WebDev
2000
Home

New!
Follow-ups
in 2001

Past
WebDev
Conferences
(DSSC Site)

About the
GCC Web


Web Management Authority:
2. What Do We Need To Do?

After a debate on Centralized Web Management vs. Distributed Web Management, teams of conference attendees provided the contents of this report beginning with Web Management Authority: 1. What Do We Need To Learn?.

The attendees were also invited to add to their notes More Commentary about Web Management Authority, which is reported separately from the outline of this page. The lists below focus only on responses to the second half of the Danger in the Construction Zone instructions.


  1. To achieve resolution or greater understanding of Web Management Authority,
    WHAT DO WE NEED TO DO IN THE SPACE OF ONE YEAR?

    Summary:

    • (Mutually exclusive initiatives)
      • We need to create a central department or team of web development experts who make all web design and organization decisions to promote marketing values, while departments responsible for separate areas of information maintain (or deliver to the central web managers) the information content only.
      • We need to establish web experts as sources of support and advisement -- especially in specialized areas such as legal questions, technological innovations, elective template designs, and general training -- while the authority to publish web sites is held by individuals or teams representing diversified interests.
      • We need to establish a "hybrid" of centralized and distributed web publishing models, in which certain parts of the colleges' web sites adhere to common standards which might include shared design templates and some kind of centralized control of information, while other more diversified web sites continue to be published.
    • We need to establish and clearly communicate standards and guidelines for web sites to follow (regardless of centralized or distributed publishing authority) that may address legal, aesthetic, navigational, and functional issues affecting the organization.
    • We need to foster competitive design and technical skills of our web developers (regardless of centralized or distributed publishing authority) via education and training.

    Transcriptions of Conference Notes:

    • [Multiple] Balance centralization/decentralization in separate areas of Web.
    • [Multiple] We have to change our philosophy; create a web department / team made up of graphic people, techs, and managers who maintain basic college standards.
    • [Multiple] Set site standards / determine priorities and procedures.
    • [Multiple] Provide a template or set of templates.
    • [Multiple] Build web sites around student interests.
    • Provide some ground rules, but not so many that creativity is stifled. Use web staff wisely as advisors and consultants.
    • There should be a set of guidelines/rules from district level for web individuals to work from.
    • Incorporate both centralization and distributed management techniques -- concepts of webdev- technical/programming, web interface usability (format/template features), and content organization standards.
    • If structure is needed maybe it should be for the delivery system.
    • Maintain skills: be competitive with other educational institutions; provide most up to date information; common sites throughout for students.
    • Distributive web management with source standard for navigation and look and feel of each page.
    • Articulate the purpose of the web in words!
    • More hands-on training with district supporting training and education in this area, more so than the individual seeking educational knowledge alone.
    • In even less than one year, we should try to have a districtwide, ADA compliant set of websites.
    • Call each campus to develop its own model of #1 so that the "flavor" of each campus is retained.
    • Make progress (recognizable) toward changing.
    • College administration needs to commit resources to meet needs whether it is centralized or spread out to different individuals.
    • Better site map of organization.
    • Combination of both: managed for main page and more diversified for links.
    • Decentralized page created by experts with standard navigation.
    • Need to establish a uniform revised look for our department page.
    • Keep lines of communication open.
    • Develop campus template.
    • Develop training on web design concepts, ground rules, and web architecture, even basic computer file management, shared work environment.
    • Figure out a way to "brand" Maricopa and link all coverages.
    • Idea for developing web sites: Individuals contribute content, suggestions, do updates. Central management provides guidance in legal issues, ADA compliance, marketing standards, design and new ideas, navigation.
    • We thought a combination of distributed and centralized web management would work best. Managed creativity and ownership. District needs to support web training for employees expected to be involved in web development (on each campus). Funding an issue. Training an issue.
    • Lack of experience, but ... Have central webmaster, but feedback from individuals allowing individual areas to edit their info on the web using an editor.
    • Value of input from technological savvy people.
    • We decided that it would be wise to have a combination of both theories. Creating a template, issuing basic guidelines, and allowing creative freedom would give a better representation of our campus.
    • Keep pages current.
    • [Obtain] software to test links.
    • Diversity can be maintained through unified pages: team-webmastering with several webmasters reporting to the primary webmaster.
    • Division Chairs need to be aware through the Dean of Instruction how important the website is to marketing their programs.
    • A hybrid: Internal web consultant to serve as a "guide". Page standards -- template. But the content is put in by the content experts.
    • Would suggest a module that is centrified to [the] extent of providing standard multiple templates, but hold source/originator responsible for content, e.g., online college catalog.
    • Can become centralized.
    • Combination: Centralized control for main campus department. Diversified, individualized at lower levels.
    • Convince DI, Department Chairs to establish control.
    • All main pages should have search engines.
    • Not centralized; there should be input by each department. This allows for more creativity, but uniformity!
    • Centralized with information coming from those involved.
    • Student drives should be managed. Employee drives should be diversified.
    • General templates for marketing purposes, but freedom to create general information.
Proceed to:
Next Topic: ADA Compliance Issues

Return to:
Introduction to Web Management Authority
Danger in the Construction Zone Contents
WebDev 2000 Contents


http://www.gc.maricopa.edu/webdev2000/danger1a.htm
Last revised: Thursday November 30 2000
Original conference date: Friday November 3 2000
Maintained by: Bobby Sample. Photography by Patrick Lovings. See Legal Disclaimer.