Close
 
 

Standard Operating Procedure

Create a Web site in the Content Management System

Purpose

The goal of this procedure is to describe the steps necessary to create a web site in the Content Management System.

Scope

This procedure is intended for all current staff members of Internet Services.

Prerequisites

A valid and active UTPA account must be in existence (in order to be able to access University resources). Also, staff must be given publish privileges in the Content Management System.

Responsibilities

Internet Services team members

Procedure

  1. Meet department or university entity in order to fully understand the requirements of their particular project.
  2. Understand what content they want to display on the site and who the target audience is. Based on this recommend best practices to the customer. Create the information architecture, site navigation, color scheme etc. for the website using the approved UTPA branding template and provide a wire frame and/or a design mockup to the customer.
  3. Once the design has been approved by the customer start converting it to code in the CMS.
  4. Identify who will be a content contributor and who all will need access to edit the website. All users who need access to edit the website must submit a Web Services Request Form. This serves as documentation that the access for the user was granted on approval from the Project Manager.
  5. Create web site structure (pages) within the Content Management System. This should include all the pages that will be navigable by general audience and pages that will be used to house files associated with the web site.
  6. Create an HTML skin that will give the web site its general appearance. HTML skin should include links to supporting files (CSS, JavaScript, etc).
  7. Create a Portal Template that will give the structure within the HTML Skin. Define all the regions that will have content and specify whether they will be editable by an end user. Assign permissions to the template based on information gathered and once Request Access to a Website procedure is complete.
  8. Assign the HTML Skin you created earlier to the Portal Template you just created.
  9. Assign the Portal Template you created earlier to all the pages you created for the web site except the document repository page.
  10. Run the web site against accessibility checkers to ensure Section 508 compliance.
  11. Check to make sure no copyrighted materials are used on the site and there are no direct links to business websites that are selling products or services.
  12. Inform customer that the template has been completed and the content provided has been put up on the site.
  13. Once the customer provides approval for making the website Live, go through the Go Live checklist before making the site public. Save the filled out Go Live checklist in the team share folder for documentation.
  14. If the website is a transition from the old webserver into the CMS then the content on the web server will be compressed into a zip file for archiving, the content deleted and a redirect file to the new location will be put in place.
  15. Provide training to the customer in editing or adding content to the web site using the CMS.
  16. If we need to back out of the Live website, the website access in the CMS will be changed to make it non public by putting it behind a username and password. If it is redesigned website then the new site will be made non-public and the old site will be activated again.

References

Definitions

N/A

Current Alerts

IT Help Desk