Embed
Email

Logo here…NKU, IT or prism

Document Sample
Logo here…NKU, IT or prism
Shared by: RyanTannehill
Stats
views:
62
posted:
8/21/2009
language:
English
pages:
5
1. Introduction

A. CMS Queue

i. Due to limited UCit CMS Development resources, Web Communications has developed a CMS

queue. This listing consists of all clients interested in CMS and projected timelines for

conversions.

ii. Request a Web Site: requests can be made directly to TJ Iaciofano tj.iaciofano@uc.edu, Ass’t.

Director, Web Communications. A preliminary assessment will be conducted to determine the

complexity and priority compared with other Web sites in the official CMS queue.

iii. All university sites must comply with the university’s Web Policy and Branding Standards

(PDF).

2. Phased Approach

A. Planning

i. Web Communications will coordinate meetings and

brainstorming sessions to review existing Web site

content, explore current needs and determine the best

course of action.

B. Information Architecture and Design

i. Information Architecture: Web Communications can

assist you in identifying your audiences’ unique needs

(e.g. navigation terms, tasks performed on the site,

forms, outside applications) and then determining the

best organization of your content and navigation so your

site is user-friendly for your audiences.

ii. Complete Redesign: A complete redesign requires the

generation of CMS compliant designs. UC Creative

Services has the expertise and ability to create designs that work freely CMS. Web

Communications will coordinate this process with Creative Services.

iii. Convert Existing Web site: Web Communications will work with Creative Services to develop an

appropriate CMS-compliant design based on your existing site.

C. Development

i. For UCit to meet your expectations, a detailed Technical Requirements Checklist will be prepared

by Web Communications. This Checklist will then be submitted to UCit as an Application

Programming Request. Enhancements to your CMS Web site are also handled this way.

a) UCit Development Quote: an itemized quote detailing add-ons and estimated time

spent for each component will be generated and sent to you for review and approval. The

quote will include the cost of training and training resources.

ii. Once the quote is accepted, development work will begin on your CMS Project.

iii. As soon as development has been completed, training for your designated personnel will be

scheduled. Training materials will also be provided for future reference.

D. Content







For CMS emergencies, training, and support please contact:

UCit HelpDesk, or call 513-556-HELP (513-556-4357)

Page 1

i. Starting Out: This phase begins once CMS access has been granted to you and your staff and

training has been completed. At this point, you are encouraged to audit your content and retire

old and unnecessary content.

ii. Content Development: Using what you have been taught in CMS training, you will convert

existing content or author new content inside CMS.

iii. Problems: List and send any known issues directly to UCit.

E. Launch

i. “Going Live” or “Launch”: Once the new CMS Web site has met all your expectations, the

content has been perfected, approved and you are comfortable within CMS, we will schedule a

date to “Go Live”, your Web site must be backed up and removed, at that point you are ready for

a production launch

a) Note: UCit and Web Communications should be notified as soon as possible once your

Web site is ready for launch. Donna.Law@uc.edu

ii. Warranty: after launch ensure that all items are delivered as requested, a 5 day warranty period

for problems will begin at launch, see UCit for details

iii. Future Enhancements: List and send to UCit. These will be treated like new development,

typically will incur a charge and will be completed as time and priorities allow. Requests for

enhancements are placed using an UCit Application Programming Request. Web

Communications can assist with this request. See Instructions

3. Features:

A. Project Setup: Base Project Setup, Roles Setup, Account Setup, Web site Hosting,

Deployment Setup

i. Roles: The CMS has the ability to allow multiple editors and approvers. Authentication is based

on the UC Active Directory system to ensure proper credentials.

ii. Accounts: You will provide a list of those who should have access your CMS Web site and

whether they will be able to edit all or selected content/pages and/or approve all or selected

content/pages. Those only able to edit are called content contributors. Those allowed to approve

are called Approvers.

iii. Hosting: CMS Web sites are typically hosted on the main UCit Production Web Server Cluster.

This service is offered free of charge. Your site may be hosted on your own server, but an

additional fee will be charged for setting up deployment.

iv. Deployment: A CMS deployment automatically sends the appropriate approved assets to the

production Web site server. Deployments are scheduled based on each project’s needs (e.g. 2x

daily).

v. Fluid Design or Liquid Design: This web concept ensures that your Web site is visible in as many

browsers as possible. As the screen grows for larger monitors, the Web site corrects itself by

stretching to meet the desired width.

B. Navigation: The links that allow a user to move

through your site. Links are typically repeated

for consistency.

i. Standard Primary Navigation: Standard Left-side;

text based; will follow UC Branding pre-approved

style over white background

ii. Background colors (options): navigation text can

be placed over solid UC red or solid black (e.g.

www.uc.edu/ucwc/). Note: dark text on a light

background provides maximum visibility for most

users.

iii. Standard Secondary Navigation (option):

a) Right-side Sidebar area or

b) Top banner area (e.g.

http://www.uc.edu/sas/ )

C. Content Web Page Layouts: formatting Web

pages

i. 1 Column: Fixed content width





For CMS emergencies, training, and support please contact:

UCit HelpDesk, or call 513-556-HELP (513-556-4357)

Page 2

ii. 1 Column Wide: 100% wide content

iii. 1 Column Sidebar: 100% wide content in main content area, plus right-hand sidebar area for

secondary information or navigation, if needed

iv. 1 Column Pic_annc_below: 100% wide main content area, plus right-hand sidebar area for

announcements

D. Banner: Repeated graphic at the top of every

Web page within a Web site

i. Randomized Banners (option): multiple graphic

banners from a group of images can randomly

display (e.g. http://www.uc.edu/kingsgate/ )

ii. Independent Banners (option): a unique

banner can be associated with a sub-folder or

independent site within the same project (e.g.

www.uc.edu/sas/ and

www.uc.edu/sas/disability/









E. Footer: Repeated on every page, consists of

basic contact information, physical address,

linked e-mail address

i. Independent Footer (option): a unique footer

can be associated with a sub-folder or

independent site within the same project (e.g.

www.uc.edu/sas/ )









F. Print-Friendly Pages: all pages can be available in a print-friendly format and turned

on through meta-data options

G. Announcements: this module give you the ability to control time-sensitive information

i. Use the built-in Announcements feature for announcements requiring start and end dates and

times.

H. News (option):

i. This module pulls directly from the UC E-News system using RSS technology which updates

automatically without human intervention. To use this option, your area must be an identified unit

within the E-News system.

I. Web Site Analytics (option): measuring Web site traffic and trends can be useful in

understanding your audience and how they use your Web site.

i. Statistics: $50 setup fee; $10/month and billed automatically. These statistics are not retroactive.

J. Events (option): this module automatically displays department, college campus or unit

events from the university’s calendaring system.

i. Events Module automatically populates “Events” and “More Events” sections of your CMS Web

site.

ii. Events Module can be pulled and displayed based on a variety of variables.

iii. Entering events into the University Calendaring System. If your area is not currently entering

events into the system, contact Brian Warner brian.warner@uc.edu, Web Communications









For CMS emergencies, training, and support please contact:

UCit HelpDesk, or call 513-556-HELP (513-556-4357)

Page 3

Manager. A preliminary assessment will be conducted to determine the complexity and priority of

your request.

A. MetaData: used to give search engines consistent and correct information to index and

display your site in pertinent search requests. MetaData can be set with the same

information for the entire CMS Web site (includes MetaTitle, MetaDescription,

MetaKeywords), or you can add unique, specific information for each and every page in

your site.

4. Support

A. Training: hands-on and interactive, training is included within setup fee for up to 6

people

i. Serena Collage Basics: spend 1 hour learning the features of UC’s CMS

ii. Web site: spend 1 hour training specifically on your Web site

iii. Refresher: courses can be revisited if necessary for additional fees

B. Phone & E-mail: UCit & Web Communications 2-Tiered Support

i. Help Desk Support: available during UC’s HelpDesk hours, trained HelpDesk staff can assist with

basic CMS issues

ii. CMS Team Support: should HelpDesk be unable to service your needs, the inquiry will be

escalated to the CMS Team.

C. Web site: Online Help & FAQ

i. www.uc.edu/web/cms/

5. Terminology

A. Approval: Last step in contribution workflow. No assets will be published until approved. This capability is

only given to the Editor/Approver role.

B. Asset: all pieces of content in CMS are considered assets; all assets, including images must be

approved before they will be published.

C. CMS Project: a logical grouping of CMS Web sites determined during the Planning Phase.

D. Content: substance of your Web site, including images, text, graphics, animations, videos

E. Information Architecture: the practice of structuring information for a purpose usually based on user

interactions with the site.

F. MetaData: associated with an asset/page and also used in CMS to change from one option to another

G. Serena Collage: UC’s supported core application for Web content management









For CMS emergencies, training, and support please contact:

UCit HelpDesk, or call 513-556-HELP (513-556-4357)

Page 4

Reference: Standard 100% Layout









For CMS emergencies, training, and support please contact:

UCit HelpDesk, or call 513-556-HELP (513-556-4357)

Page 5


Related docs
Other docs by RyanTannehill
SkyTeam Transatlantic Routes
Views: 9  |  Downloads: 0
Jan
Views: 41  |  Downloads: 0
SME Banking (Transitional)
Views: 55  |  Downloads: 3
Sustainable Transportation Working Group
Views: 5  |  Downloads: 0
SLP Skill Competency Evaluation
Views: 206  |  Downloads: 4
esb08301
Views: 2  |  Downloads: 0
ARTS ON EDGE
Views: 11  |  Downloads: 0
By registering with docstoc.com you agree to our
privacy policy

You are almost ready to download!

You are almost ready to download!