
Glendale Community CollegeWebDev 2000 Home New! Follow-ups in 2001 Past WebDev Conferences (DSSC Site) About the GCC Web |
More Commentary on Web Management Authority
These opinions were contributed by WebDev 2000 attendees and readers in addition to the live debate on Centralized Web Management vs. Distributed Web Management to introduce the Web Management Authority topic:
For Centralized Web Management:
|
- [NEW 11/24/00] While I understand the need for innovation and
diversity, the main campus web site is not the place for it. Faculty are not web designers... See entire comment
- Some centralized management is necessary to ensure legal standards are
maintained.
- Maintaining a web site (different [from] maintaining a web page or pages)
takes an expertise that most people do not have.
- There are areas where a person can play, such as their "home" individual
web pages.
- Brand, institutional identity, one brand, ease of use.
- More sophisticated users look for Internet standards in order to
recognize the structure of a site and determine where to find the info
they need; without standard structure / organization the user will become
frustrated and leave the site.
- There needs to be a structure [and a] main idea to maintain a web site
that is not confusing.
- Marketing model consistency.
- Consideration of user (student).
- Key people should be responsible for look.
- Identity needs to be maintained.
- Good point: inequity in distributed module.
- Centralized does not remove the curve of education, because staff
can enroll in classes to further education. Taxpayers are benefited by centralized based on training costs and salaries.
|
For Distributed Web Management:
|
- My opinion is everyone has the insight to choose what is on their own
web page.
- In academia, distributed web development is better.
Centralized development is censorship.
- More diversity of ideas.
- Under control of single person -- not good.
- Is representative of institutional differences.
- There needs to be freedom of expression in the classroom.
- Distribution among many departments.
- Rigid [if only] controlled by one or two people.
- Diversity of ideas always of value from staff.
- Concern that the technical person will act as a gatekeeper to control
what is put on the web instead of the person who knows the information.
- Downfall of centralized: maintenance of the individual departments.
Who becomes responsible for maintenance? Who makes priority when
changes need to be made?
|
General Commentary:
|
- Web techs need to support staff to allow them to contribute. Takes
collaboration, not autonomous process.
- Need a balance between control freaks and anarchists; a continuous
dialog without power grabbing.
- Too much confusion when there is a lot of diverse information that
is squeezed into one page.
|
Links for learning more about this topic:
- Some Maricopa campuses have already published information explaining aspects of their web management:
Provide additional commentary
Proceed to:
Web Management Authority: 1. What Do We Need To Learn?
Return to:
Introduction to Web Management Authority
Danger in the Construction Zone Contents
WebDev 2000 Contents
|
|