Here’s what happens when you make a request.

Top Level Page Change Process Summary

change request diagram

Top Level Page Change Process Detail

  1. User submits online form to a single central contact (irwebmaster@csuchico.edu)
    1. Communications sent to other parties will be directed to irwebmaster
    2. The irwebmaster will direct all communication to the appropriate channel. This simplifies the user experience since they are unlikely to understand which kind of request should go to what body.
    3. All requests, no matter what type, will receive a response from irwebmaster. The appropriate bodies handling requests will also respond.
    4. There are four categories of requests:
      • Report bug/broken link/typo
      • Request for link/change/addition to top level pages
      • Requests to have story in Big Picture/Highlight/News/Events
      • Other
    5. The irwebmaster will enter all communications into JIRA, a web application that is used for issue tracking
      • JIRA is a good resource for managing issues and directing them to the appropriate groups
      • IRwebmaster will forward communication directly to appropriate groups to expedite the process
  2. Each type of issue will have its own process.
    1. Report bug/broken link/typo
      • Issue will be forwarded to a Web Content Management System (WCMS) administrator who either:
        • Corrects the problem and responds to the requestor
        • Forwards it to appropriate body if there is any further consideration needed before making the change
        • Forwards to departmental contact if problem is with departmental site and not top level pages
    2. Request for link/change/addition to top level pages
      • Issue will be forwarded to Web Content subcommittee chair or chair designee
        • Web Content subcommittee is appointed by the Web Content Committee Chair
      • Web Content subcommittee reviews requests via e-mail to address requests for links, changes, or additions to top level pages
        • Members have 1 week to respond before decisions are made
        • The Subcommittee will meet in person as needed
      • Web Content subcommittee uses a standard set of criteria to evaluate requests:
        • Does the change entail a major structural or design change to pages or the site as a whole?
        • Does the change entail major structural or organizational changes within the WCMS?
        • Does the change positively or negatively affect the end user experience?
        • Is the change consistent with standard web best practices with regard to coding, usability, and accessibility?
        • Does the change meet with campus web editorial standards?
        • Does the change fit with the overall branding, message, and tone (visually and editorially) of the current site?
        • Does the change affect multiple units or departments?
      • Web Content subcommittee responds to requester with decision, or forwards request to full WCC if they feel that the request requires wider consideration.
        • If approved, WCMS admin (or other appropriate user) makes change.
        • If denied, appeals can be made to the full WCC at their regular meeting, if a hearing of such an appeal is approved by the chair of the WCC.
          1. The WCC chair must approve the hearing of appeals. This should be done only in cases where input from a greater range of the campus community is required or the proposed change has a significant potential impact.
        • If forwarded to the full Web Content Committee, the chair convenes the WCC for consideration of the request, using the same standard criteria (above).
        • Requestor is notified of final decision and action (if any).
        • Decisions of the WCC may be appealed to the Web Management Committee at their regular meeting, if a hearing of such an appeal is approved by the chair of the WMC.
          1. The WMC chair must approve the hearing of appeals. This should be done only in cases where input from campus administrators is required or the proposed change has a significant overarching campus impact.
          2. Decisions of the WMC are final.
        • A summary of the actions of the Web Content subcommittee will be presented at each meeting of the full WCC.
    3. Requests to have story in Big Picture/Highlight
      • Issue forwarded to Public Affairs Office
        • Decision of PA is final.
        • If approved, PA creates story/highlight and works with Web Services (big picture/highlights).
    4. Other (including requests/issues with pages that are not included in the top level)
      • Issue is forwarded to most appropriate body.

Web Change Request form