Ciissite Implementation Specification

CIISSite Implementation Specification

CIIS Site Implementation Specification

Version History

Access Information

How To Read This Document

Definitions

Schema Mapping Example

Schema – Detail Page

Site Implementation Overview

Site Essentials

Ingeniux Campus News Module

Ingeniux Campus Events Calendar Module

Site Wide Conventions

Site Navigation Conventions

Site Functional Requirements

XHTML Compliance and Cross-Browser Compatibility

Application Functionality

Search Engine Optimization

Metadata

Page Title

URLs

Site Tree

Site Elements

Forms

Page Elements

Page Functional Links

Page Types

Home

Design or Wireframe

Notes & Requirements

Schema – Home

Schema – Footer Drawer Component

Schema – Footer Item Component

Portal Page (Audience Gateway)

Design

(with global navigation without video)

Notes & Requirements

Schema – Portal Page

Schema – Right Column Link Component

Clone Page

Design – no design

Notes & Requirements

Schema – Clone Page

Section Front (Topical Second Tier)

Design

Notes & Requirements

Library Homepage

Design

Notes & Requirements

Schema – Library Homepage

Taxonomy Contact Component

Schema – Taxonomy Contact Component

Version History

4/15/09Initial Draft reviewed with CIIS

4/17/09Version with comments incorporated from the initial specification review with CIIS

4/22/09Version with Ingeniux updates from initial specification review with CIIS

4/23/09Version with updates from the specification review with CIIS on 4/23/09

5/7/09Version incorporating CIIS and EM2 deliverables, News Submission Module specifics and general updates

5/15/09Version incorporating email notes from EM2 and CIIS from 5/13/09 – 5/15/09

5/18/09Final Specification

Access Information

Design Templates: currently stored in CIIS FTP

Site Implementation Project site:

User:

Pass:

How To Read This Document

Definitions

Template:See Page Type below.

Page Type:Page Types are the functional equivalent of templates in the Ingeniux CMS. They define the various content types that can be displayed on any given page in your site. Because Ingeniux is an XML-based system, the content itself is separate from the display, and any given content type has the potential to be displayed in multiple ways – on a web browser, a mobile device, or even rendered as a PDF file. Because of this, page types in Ingeniux CMS are very flexible, and one page type can often handle a number of different display requirements.

Component:Components are pieces of reusable content that are inserted into pages. For example, making an advertisement a component and inserting it into various pages designed for it will allow that same ad to appear throughout the site. This allows you to change content in one place, and have the result broadcast throughout the rest of your site where it is used.

Schema:A schema defines what elements on a defined page type or component are exposed in the CMS so they can be modified by the user. Each field described will be rendered on the Edit Form in the Ingeniux CMS.

Yellow Highlights: Items highlighted in yellow are open questions addressed to you (the customer) that need to be answered as we proceed.

Teal Highlights: Items highlighted in teal are comments addressed internally for Ingeniux developers, usually referring to specific ways to implement the features of the site. These will be removed from the final draft of the specification.

Schema Mapping Example

The example below shows how a schema for a Page Type or Component in this specification will map to the Edit Form of the Ingeniux CMS. Each row in the table defines each field in the page. The columns are defined as follows:

Label: Lists what the title of the field is on the Edit Form.

Element Type: Lists which element type will be used to store the content.

Notes: Any extra information about the element and its function.

Req’d: Notes whether the field is required or not.

H/RO: This notes whether the field is Hidden and Read Only. If a field is Hidden, only Administrators can see the element on the Edit Form. If a field is Read Only, the field will be visible, but grayed out and unable to be modified.

The table below is how the schema is defined in this specification:

Schema – Detail Page

Label / Element Type / Notes / Help Text / Req’d / H / RO
Title / Text / Y
SubTitle / Text
Abstract / Text / Y
Main Content Area / XHTML / Optional body copy content
Image / Component
Ancestor Nav / Navigation / H/RO
Site Control / Component / Banner and Footer / H/RO

Which will look like this in the Ingeniux CMS:

Site Implementation Overview

This section defines the site implementation scope of work and requirements for CIIS. Site implementation will consist of:

Creation of up to 14 Standard Page Types in Ingeniux CMS, up to 4 Page Types in the Ingeniux Campus News Module, up to 3 Page Types in Ingeniux Campus Events Calendar Module.The initial scope of work defined the following page requirements:

Components as required to complete the specified Page Types.

Structuring of permissions and workflow rules for site contributors.

Page Types required for this site implementation include:

Standard Page Types

1)Homepage

2)Portal (audience gateway)

3)Topical Second-Tier Page/Section Front

4)Library Homepage

5)Directory

6)A- Z Index

7)Alumni Page

8)Contact Us/Thank You

9)Search Results

10)Make a Gift Form

11)Academic Program/Academic Department

Note: these two page types will be the same yet will have different page names for user friendliness

12)Third Tier Information Detail Page

13)Profile/Featured Story

14)Counseling Center

15)Clone Page

Note: this is one standard page type over the initial scope of work proposal but Ingeniux will include this in the current page type budget free of charge

Additional Page Types through 360

16)Photo Gallery

17)Video Gallery

18)News Submission Form

Ingeniux Campus News Module

19)News Section Front

20)News Index

21)News Archive

22)News Detail

Ingeniux Campus Events Calendar Module

23)Event/Calendar Page

24)Event Detail

25)Event/Filter View

Site Functionality

26)Print Friendly

Site Wide Conventions

Site Navigation Conventions

Header Navigation:The header navigation will be consistent on every page in the site and be managed in the Site Control Component

Topical Navigation: The topical navigation will appear on top of every page and will be managed as images.

Footer Navigation: The footer navigation will be consistent on every page in the site and be managed in the Site Control Component

Footer Drawer: The footer drawer will live on the bottom of each page and hold content directed towards the audience of each page. The footer drawer will be managed in components (defined at the end of this document) and will be programmatically inherited by the decedents of Section pages but will also have the ability to be manually managed. The Footer Bar will rotate through all selected components on page reload. The Footerdrawer component will consist of an image, a headline text field, a sub-headline text field,and a link. The link will link internally within the CMS environment and open in new window that will lie over the page.

Breadcrumb Navigation:

Breadcrumb navigation will exist and begin at the second tier level in the site tree. Portal pages will also use breadcrumb navigation and incorporate “Cloned Pages” in order to incorporate bread crumbing that interacts with the site.

Left Column Navigation: The Left Column Navigation begins on the second tier level in the upper image treatment and will display the children of each the given page. Various pages throughout the site will use the child navigation within the left column area. Each page type’s specifics regarding the left column navigation are defined per page in the document specifics below.

Site Functional Requirements

XHTML Compliance and Cross-Browser Compatibility

Ingeniux will use W3C-standard XHTML that meets accessibility compliance requirements.
Ingeniux will provide cross-browser display for Firefox PC and Mac, IE 6 Windows, IE 7 Windows and Safari.
Alt-text shall be used for all images throughout the site.

Application Functionality

Ingeniux Site Essentials includes the following Application Functionality:

Search integration or Ingeniux Search functionality
Print-this-Page
Image Rotation

Ingeniux Campus News Module includes the following Application Functionality:

RSS Feed Output
RSS Feed Input
News Classification
News Components for integration of news content in other site pages

Ingeniux Campus Events Module includes the following Application Functionality:

RSS Feed Output
Events Classification
Events Components for integration of events content in other site pages

Search Engine Optimization

Abstract fields will be used to capture Meta data for each page. Structured URLs, Alt-text and Page Titles are also included as a standard offering, all of which are meant to enhance page rankings. Additionally, Ingeniux recommends the creation of a Google Site Map.

Metadata

Metadata descriptions for search engines are typically taken from the “Abstract” field in the page schema. This can be modified to conform to general site-wide standards for population of search engine metadata fields.

Page Title

The “Page Title” field will be used by default to populate the browser window / tab title

Search

Site search will use the Google Mini application. Integration with Google Mini will be done by Ingeniux.

URLs

Published pages will use Structured URLs.

Redirects

Ingeniux can implement up to ten (10) redirects for the CIIS site implementation. Additional redirects can be configured if requested by CIIS but will require additional scope.

CIIS to provide a list of the redirects they would like Ingeniux to configure for site delivery

Site Tree

This section is to be defined by CIIS

Page NamePage Type

Home(Home)

Section 1(Section Front)

Sub-Section 1 (Sub-Section Front)

Site Elements

Forms

There is currently one (1) form, Make a Gift, which will be managed in the CMS. Specifics on this form are defined in the page type specifics below.

Page Elements

Page Functional Links

To appear in the center towards the bottom of the page. These include:

Print This Page

Social Bookmarking

Font Size

Page Types

Home

Design or Wireframe

Notes & Requirements

The Main image area will be managed in the CMS as flash as Home Flash Component. This will be managed in a component with the option to add an image (up to 6) , logo, link, and text field for the text that overlays the image

Scrolling navigation in the bottom left will be handled outside the CMS through the flash

The flash presentation will need a backup image for browsers that do not support flash this will include an alt image and alt link

Ingeniux will create the homepage flash (this will use 360 hours)

Emergency bar will appear on the homepage under the top image area and will push the content area down. Check box to enable, will default to not display. The emergency notification will be managed by an include text file. This will allow CIIS to manage emergency messages outside the CMS through accessing a URL with a status notification to select on/off and an alert field to manage the text notification for the given emergency.
All Pages will have a link list at the bottom of the content areas which will display links to facebook, RSS feeds, Blog Spot, and YouTube.
Social Bookmarking will also need to be a part of each page. This will be a dropdown list of all Ingeniux standard Social Bookmarking and will hardcoded
Left Column will have the Portals as a navigation to a portal page folder pulling all children of the folder and automatically updating the left column list
The Promo Component (Explore CIIS) will be managed in a Component List so there is the ability to add more if necessary. The Component will consist of an image and a link.

If there is a link to an internal page it will open in a new page, if there is a link to an external area it will open in a new window

The right column will consist of News & Events tab and a Calendar tab which fill function with a dojo toggle.

The News and Events Tab and the Calendar Tab will be editorial selected through a Multi Select by a taxonomy navigation (the News tab will only be news. If there needs to be an event CIIS can create a news story for that event.The Calendar tab will only be events). The Multi Select will limit the user’s choices to only three items per area.

Below the Link List will be a link to all News and all Events

The bottom footer drawer will use the following components: “Drawer Content Component” to manage the footer content andwill be placed in the “Left Side Footer Drawer Components”, “Middle Footer Drawer Components”, or “Right Side Footer Drawer Components” Lists whichmanage the placement and rotation of each “Footer Drawer Component”. Which will be placed in the Footer Drawer Component per designated page. This Footer Drawer will be inherited by all of the given sections descendents

The components will rotate on page refresh

Each component will consist of a image and link field.

These will all be internal links and use a pop-up window that overlays the page. This will be managed in an i-frame

Schema – Home

Label / Element Type / Notes / Help Text / Req'd / H/RO
Main Flash / component / Flash displayed at the top of the page. / H
Title / Text / X
Abstract / Text / X
Body Copy / Xhtml
Left Column / group start
Portal Pages / navigation / Navigation Type: Children
Promo Components / List
group end
Right Column / group start
News and Events / multiselect
News Front Link / Link / X
Calendar / multiselect
Calendar Front Link / Link / X
group end
Footer Drawer / component
SEO Group / group start
Browser Bar Title / Text / Populates the title at the top of the browser.
Meta Description / Text / Populates the description of the page for search engine results.
No Follow / checkbox / Tells search engine spiders not to crawl the links on this page.
No Index / checkbox / Tells search engine spiders not index this page.
No ODP / checkbox / Tells search engine spiders not add this page to the Online Directory Project.
group end
Emergency Alert / Insert
Site Control / component

Schema – Footer Drawer Component

Label / Element Type / Notes / Help Text / Req'd / H/RO
Text Color Class / Enumeration / The color class options are defined below / X
Left Side Footer Drawer Components / list / List of components that will cycle on refresh on left side of the bottom of the page. / X
Middle Footer Drawer Components / list / List of components that will cycle on refresh in the middle of the bottom of the page. / X
Right Side Footer Drawer Components / List / List of components that will cycle on refresh on right side of the bottom of the page. / X

Footer Drawer Text Color Class Options:

Schema – Footer Item Component

Label / Element Type / Notes / Help Text / Req’d / H / RO
Image / Image / Y
Headline / Text
Sub-Headline / Text
Link / Link / Link will pull title and abstract from page its linking to

Schema – Main Flash Component

Label / Element Type / Notes / Help Text / Req'd / H/RO
Flash Promo / Media
Flash Alternate Image / image
Flash Alternate link / Link / The link will be used if the image is displayed and not the flash

Portal Page (Audience Gateway)

Design