sitecore - confluence - tufts university

Tufts University Sackler School of Graduate Biomedical Sciences

Tufts University School of Medicine

REQUEST FOR PROPOSAL

WEB CONTENT MANAGEMENT SYSTEM

Request for Proposal

Sitecore USA, Inc. &

ISITE Designs Due: March 4th, 2008

Prepared by: Joe Henriques, Regional Director Phone 415-444-0600 Fax 415-444-0730 Email [email protected]

mailto:[email protected]

- 2 -

1 EXECUTIVE SUMMARY

Sitecore, along with the interactive agency ISITE Designs, provides higher education customers

such as Tufts Medical School the ability to implement the best and easiest to use editorial tools

for business users to edit, create and manage content, assets, and internal CMS functionality.

The Sitecore CMS provides an extremely flexible and easy to use Workflow engine that will

completely support any Tufts Medical School specific requirements to the path by which content,

assets, customizations, etc get published to the web or other publishing targets. Sitecore

provides the most flexible framework for the management of multiple web sites, portals, and

applications all under the same CMS hood. It provides the ability to share, secure, import and

export content, data, and assets from the multiple sites, while providing site administrators one

interface to manage all web properties under management.

With Sitecore and ISITE Designs, Tufts Medical School with have the ability to categorize and

archive all existing and new content to the exact specifications or requirements determined

through the discovery process of your web infrastructure redesign. There are no limitations on

how Sitecore handles or stores content, assets, or other related items. This would provide Tufts

Medical School, with working with ISITE Designs, the ability to implement the CMS without

any restrictions.

The Sitecore platform will completely satisfy any and all integration needs of Tufts Medical

School. Sitecore is built for integration, whether it be through the completely documents

Sitecore APIs or through XML web services, there is no limits to the applications and tools that

can be integrated to accomplish any web challenge.

With Sitecore, Tufts Medical School will have the ability to create truly compelling web

experiences.

2 SITECORE AND ISITE DESIGNS

2.1 COMPANY INFORMATION

Sitecore is the worldwide technology and functionality leader in pure .NET web content

management and portal software. Sitecore provides content management and portal software to

mid-market and large commercial, non-profit and government organizations that require

enterprise-class functionality, scalability, integration and flexibility.

Sitecore is a privately held, multi-national company headquartered in Copenhagen, Denmark

with sales, marketing, engineering and support offices in the United States, United Kingdom,

Sweden, Australia, Netherlands and Germany.

Sitecore began in the mid-nineties with strong software development team implementing

contemporary web content management solutions for customers throughout Denmark. In 1998,

Sitecore became an independent software vendor (ISV), forgoing any implementation services

and solely focusing on the development of Sitecore‘s content management platform.

- 3 -

Sitecore is the leader in developing and maintaining the most advanced pure .NET web content

management and portal platform in the industry. Sitecore V5, the company‘s current flagship

product, is the fifth generation of Sitecore‘s web content management and portal platform and

technology. Since the company‘s beginning, Sitecore‘s team has focused on leveraging

Microsoft‘s technology platforms and in 2002 they introduced the first pure .NET web content

management and portal platform. Today, Sitecore continues its leadership with Sitecore V5 and

the aggressive, ongoing product roadmap.

The Sitecore platform is used by over 1400 hundred companies worldwide to manage over 5500

websites, intranets and extranet portals. A sample of Sitecore‘s customers include Ball State

University, the Newspaper Association of America, CA, Microsoft, Newspaper Association of

America, The Knot, the Atlanta Falcons, Population Reference Bureau, Webtrends, Dollar /

Thrifty Rent-A-Car, Sara Lee, USC, University of California, University of Texas, Baypath

College, Widner Law School, and Siemens.

Managing all of these customers are the over 100 employees of the Sitecore Global Corporation.

Of those 100, 25% are responsible for product development functions as Sitecore Developers /

Engineers. Sitecore is positioned to see a 50% increase in staff over the next year, while looking

at the same for profits.

2.1.1 Product Introduction

Sitecore CMS is a content management system (CMS) and portal platform. Sitecore enables

organizations to build, deploy and manage business solutions, such as web applications, public

websites and secure portals which require enterprise-class CMS functionality, integration options

and scalability.

Sitecore‘s open architecture and approach is optimized for the management and delivery of a

wide variety of web-based content. This optimization enables organizations to build and manage

web based solutions with less time and effort than competing platforms, thereby reducing the

total cost of ownership (TCO) for both Sitecore and the resulting business solution.

In addition, Sitecore provides organizations with the ability to ―single-source‖ content. Single

sourcing is the ability to create, edit and workflow content in a single repository, while

publishing the content to a variety of formats, such as web, MS-Word, PDF and RSS formats.

Sitecore provides a single user environment for users to work with content and the ability to

transform content on-demand to whatever format is required by the requestor.

Sitecore provides a broad-range of standard content management features. Sitecore differentiates

itself by providing enterprise-level functionality in a flexible, robust and scalable solution that

embraces a best-practices approach to content management. The following are key highlights of

the content management features Sitecore provides:

- 4 -

Cross-browser role-based user environment—Supporting both PC and Macintosh

environments with Microsoft IE and Firefox browser support. The user experiences an

environment that is specific to their role and security privileges.

In-context WYSIWYG content editing—Content editing occurs in the context of a web

page, where users navigate to and click on the content they want to edit to invoke a

structured content editor.

Built-in content staging (preview) environment—Content is initially managed within a

built-in staging environment where users can edit, review and approve content prior to

publishing for external consumption.

Content scheduling, expiration and archiving—Content stakeholders have full control

over the scheduled publishing, expiration and archiving of content.

Content reuse, aggregation and syndication—Based on XML content repository,

Sitecore enables easy reuse of content across multiple documents or web pages. In

addition, facilities to aggregate content form various external data sources, such as

Document Management Systems, enable the production of documents and web pages that

share content form a variety of sources.

Content permissions, versioning and workflow—Structured and document-based

content use the same permission, versioning and workflow functionality.

Multi-language content support with translation—Content can be maintain in any

number of languages, providing the dynamic creation of a document of web page in any

language on demand. Sitecore provides Web Services integration with external

translation houses that can provide machine translation of content.

Multi-device support and output—Dynamically assembled content can be transformed

to conform to virtually any output format, such as small device pages (i.e. PDA or

phone), web, PDF or RSS for example.

2.1.2 Technical Introduction

Sitecore is platform to deliver business-specific content management solutions. More like a box

of content management Lego® blocks than an out-of-the-box solution, Sitecore enables

customers working along side certified Sitecore Solution Partners, such as ISITE Designs, to

configure solutions that meet their needs without compromise.

This ability to provide solutions that seamlessly integrate into the customer‘s business processes

and way of working is enabled by the flexible, well-architected platform Sitecore provides. The

following highlights the key technology functionality:

Microsoft ASP.NET-based technology—Sitecore is pure ASP.NET managed-code

application running on Microsoft IIS (Internet Information Server). Sitecore takes full

advantage of the Microsoft .NET 2.0 framework.

Standards-based platform—Outside the fact that Sitecore relies on .NET as technology

platform, Sitecore embraces common (W3C) technology standards for web design and

development, such as XML, XSL, XHTML, DTHML, CSS, AJAX, XAML and

Javascript.

- 5 -

Strong development platform—5000+ documented .NET, JavaScript and Web Service

APIs with exposed event model and pipeline architecture. As an open development

platform, Sitecore provides many integration opportunities with enterprise systems and

enables organizations to easily extend Sitecore with business-specific functionality.

Enterprise integration layer—Enables data form enterprise systems (i.e. Document

Management Systems, Enterprise applications, etc.) to appear within the Sitecore

repository as though they are native Sitecore content. This enables external content to

inherit all the functionality, such as workflow and security, which native content does.

Multi-database architecture—Sitecore manage multiple content and security databases

to enable the federation of individual databases across multiple servers for both

scalability and security purposes.

XML content repository—Content is stored and managed within a single, unified XML

content tree. Sitecore provide both an interactive visual interface for non-technical

content stakeholder, while programmatic access to the content is provided to the

development community.

Dynamic content output—Content is presented dynamically to address the specific

format requirements of the requesting user. Content may take on virtually any form, such

a rich web page, text-only web page, PDF document or MS-Word document for example.

Flexible output definition—Flexible, layered approach to presentation templates

significantly reduces the effort required to both define and maintain them.

Multi-server server publishing—Publishing can occur to any number of web servers

within a server farm, including geographically disparate server farms. Sitecore provides

that ability publish content via variety of transport mechanisms, such database

replication, FTP and Web Services.

Universal security model—Sitecore security applies to structured content items (XML

objects), file-based items and functionality within the system. All security is managed

within a domain, group and user model that may be populated with various directory

systems, such as Active Directory or proprietary stores

2.1.3 References:

Below please find 3 Sitecore Higher Education clients who have stated that they would be happy

to discuss their Sitecore implementation and their decision making process with Tufts Medical

School.

Name of client:

Kyle Parker

Ball State University

3401 North Tillotson

Muncie IN 47306

765-748-7493

[email protected]

Number of sites implemented at install:

http://www.bsu.edu


http://www.bsu.edu/

- 6 -

*********************

Name of client:

Andy McHargue

Annenberg School for Communication

University of Southern California

3502 Watt Way

Los Angeles, CA 90089-0281

213.740.1290

[email protected]


http://annenberg.usc.edu

*********************

Name of client:

Michael Anderson, Assistant Director

Course Development and Technology

The University of Texas System - TeleCampus

702 Colorado Street - CLB 4.100

Austin, TX 78701

Voice: 512-499-4262

[email protected]


http://www.telecampus.utsystem.edu/


http://annenberg.usc.edu/


http://www.telecampus.utsystem.edu/

- 7 -

2.2 RESPONSE MATRIX

Number Requirement/Feature Does your product

provide this? Describe. Standard feature,

add-on, or custom?

If not custom, what is the price to buy or

build?

2.2 Content Sources and Migration

External Content Sources

2.2.1 CMS provides the ability to import content from any database – specifically: • Microsoft SQL 2000 and 2005 • MySQL 5.x • Oracle 11.x

YES - Sitecore provides developers with the ability to integrate the CMS with external databases (database agonist). The data being imported into Sitecore will need to have mapping performed to Sitecore content data structures which in turn map to XML tagged fields in the Sitecore data repositories.

Sitecore integration with external databases and having them mapped to Sitecore content items would be custom work performed by a Certified Sitecore Developers.

2.2.2 CMS provides the ability to import content stored on file systems.

YES - Sitecore provides the ability to import files stored on the file system as a standard feature. These files will be stored in the Sitecore Media Library as file based assets to be acted upon by content authors.

This is a standard feature.

- 8 -

2.2.3 CMS provides the ability to import content from RSS, ATOM and SOAP feeds.

YES - Sitecore content items, once mapped to these feeds can received imported content and create content items on fly to be stored in the hierarchical store format of the Sitecore database

Sitecore provides the ability to map feeds to Sitecore content items but the action by which to set the mapping would be considered a customization based on requirements and can be easily handled by a skilled certified Sitecore developer.

2.2.4 CMS provides the ability to import content from proprietary web services.

YES - Sitecore completely supports the importing of content into Sitecore via web services.

Sitecore provides the ability to receive data and file based assets via web services but the action by which to web service would be written would be considered a customization based on requirements and can be easily handled by a skilled certified Sitecore developer.

2.2.5 CMS provides the ability to import content from Atlassian Confluence Wiki.

This functionality is possible through the use of the API provided with the Sitecore CMS.

This would require some custom programming but is eminently do-able.

2.2.6 CMS provides the ability to import content from Six Apart Movable Type Blogs

Yes, this is supported. See 2.2.5

2.2.7 CMS provides the ability to import content and digital assets from Microsoft Sharepoint.

YES - Sitecore provides this requirement as a standard feature through the pre-built Sitecore SharePoint Module.


- 9 -

2.2.8 CMS allows metadata to be associated with the external sources.

YES - Sitecore provides the ability to have specific fields in content items have separate sources such as from Sitecore (metadata tagging) or from external sources.

The ability to separate content item's field’s source of content is a standard feature.

2.2.9 CMS allows external and internal content sources to be integrated in one content entry form, and applies presentation standards to both content sources.

YES - Noted above a single content item can have separate content sources. Both have a complete separate from presentation and both can have the same presentation layer applied.


2.2.10 CMS provides the ability to import content from existing web sites.

YES - Depending on structured the content exists on the existing websites, Sitecore can have the content imported.

The ability to import content from an existing site weighs solely on how structured the content resides. Sitecore wants extremely structured content, as it makes it extremely easy to reuse content across multiple sites and locations within a site. Custom work and a deeper dive into the current site by Sitecore certified developers would need to be performed.

2.2.11 Imported content is definable based on content type (e.g., image, PDF, text, etc.).

YES - Sitecore provides the ability to import content to specific defined content types.


- 10 -

2.2.12 Imported content can be mapped to custom content types.

YES- Sitecore would need to map the imported content to custom content types.


2.2.13 CMS allows the filtering of imported content based on custom rules.

YES - Sitecore provides the ability to create custom rules or criteria

The creation of custom rules would need to be performed by certified Sitecore Developers.

2.2.14 Users can create custom rules. Please explain.

This is completely dependent on the rules being defined. Sitecore users with the ability to define validation rules or rules by which content items can be created. Custom logic rules will need to be created by Developers.

Custom logic is created by developers, while common rules such as validation or content creation can be applied by standard users, using the standard features of Sitecore.

2.2.15 CMS provides the ability to import related tables.

YES - But it would make more sense to create the items in Sitecore and migrate the content. Sitecore completely separates content from presentation and is a database driven CMS.


2.2.16 CMS provides the ability to import HTML/XML documents.

YES - Sitecore provides XML importing and exporting.


2.2.17 CMS imports XML documents based on any XML Document Type Definitions (DTD) or XML Schema Definitions (XSD).



2.2.18 CMS allows XML DTD or XSD to be directly mapped to CMS content types.


This would be part of the implementation process, as well as, the XML document would need to be consistent with the fields of the content item types.

- 11 -

2.2.19 CMS supports batch import of multiple HTML/XML files.

YES - Batch import of XML is supported.


Content Migration

2.2.20 Who performs content migration from the existing site?

Content migration can be handled in multiple ways: The client can collaborate with the implementation partner to conduct a site audit; determine which content will port over to the new CMS, and create a migration work-plan that is supported either by the client, the partner, or both. This is a recommended best practice, in that the migration process becomes a de facto training phase for content owners/managers who can learn the system while also accomplishing the migration activities.

2.2.21 CMS provides content migration tool. Partial - Sitecore provides some mapping tools for the migration of well structure content.

This would be considered a customization. If the pages are static HTML pages, a script would need to be written by .NET developers to migrate the content to the well structured data structures of Sitecore.

2.2.22 Content migration tool can be run manually.

YES - Sitecore provides the ability to create and run manual migration tools.

Some custom work will need to be performed to synchronize the migration tool with Sitecore content items.

2.2.23 Content migration tool can be run based on a schedule.

YES - Sitecore provides all tasks within the application to be run as scheduled tasks.


- 12 -

2.2.24 Content migration tool can continually synchronize content between the source pages and the CMS.

YES - Sitecore provides all tasks within the application to be run as scheduled tasks.


2.2.25 Migrated site can look exactly like the "pre-migrated" site

YES - Sitecore provides complete flexibility on look and feel.

The look and feel would need to be created by web developers. Sitecore does not limit any design decisions.

2.3 Content Authoring

WYSIWYG Editor

2.3.1 CMS provides WYSIWYG editor. Yes - Provided as core component


2.3.2 Editor is XML-compliant and browser independent.

Yes - Sitecore editor is XML compliant and is completely supported in IE and Firefox.


2.3.3 Editor allows editing in both XHTML/XML and WYSIWYG views.

Yes- Sitecore provides a permission based toggle between both views.


2.3.4 Editor provides split code and live preview view.

Yes - Sitecore provides the ability to see the code and to preview how the code will render items in the Sitecore Developer Center application.


2.3.5 Editor is customizable based on branding standards (e.g., fonts, colors, etc.).

Yes -Each function in the editor is security permission based.


2.3.6 Editor formatting features can be "turned off" for different users.

Yes - This is completely permission based features that are turned off and on through the non-technical Sitecore security interfaces.


- 13 -

2.3.7 Multiple files can be edited at a time. Yes - Sitecore does not store content as files. All content is stored as tagged XML in the database. Each separate item in Sitecore can be checked out by users all at the same time.


2.3.8 Editor supports the insertion of in-line images.

Yes - The Sitecore editor provides the ability to insert in-line images by the simple selection of the image from the Media Library.


2.3.9 Editor supports the creation of in-line links to other content.

Yes - Sitecore provides the ability to link to other content items managed by Sitecore via the Sitecore Link Manager application.


2.3.10 Links created to other CMS content are stored as dependencies in the CMS.

Yes - Sitecore stores links as dependencies.


2.3.11 HTML/XML view has color-coded syntax highlighting.

No - Sitecore does not provide this out of the box, but provides seamless integration with Visual Studio 2005 & 2008 which provides this feature.

Sitecore's seamless integration with Visual Studio 2005 & 2008 is a standard feature.

2.3.12 Editor accommodates special characters.

Yes - Sitecore provides the ability of users to use special characters


2.3.13 Editor has advanced table creation palette.

Yes - Sitecore completely supports the ability to create tables with in the HTML Editor.


- 14 -

2.3.14 Editor supports uploading of variant file types: Word documents, PDF files, etc.

Yes - Sitecore provides users with the ability to upload file based assets to the Sitecore Media Library. Sitecore also provides the ability to apply approval processes for the uploading process of assets.


2.3.15 Page length is unrestricted. Yes - Sitecore does not limit the length of pages.


2.3.16 Editor provides option to clean HTML/XML code and strip out extraneous Word coding.

Yes - Sitecore provides a customizable code stripper for cleaning code when being copy and pasted from Word. The end result is clean complaint (X)HTML.


2.3.17 Editor validates code for W3C compliance. What is the level of compliance?

Yes - Sitecore is shipped with a w3c Him validator. The settings of which are set by each customer's specific requirements.


2.3.18 Editor identifies code violations visually. Yes- This is provided through the w3c HTML validator. Sitecore can also show code violations through the Sitecore Preview Mode.


2.3.19 Editor has spell-check. Yes - The Sitecore editor comes shipped with a Spell Checker, as well as a Spell Checker for all field types that can be used to make up content items.


- 15 -

2.3.20 Content can be saved without exiting editor, regardless of view.

Yes - Sitecore provides the ability to save draft content at anytime in all editing UIs.


2.3.21 Content can be saved to multiple locations.

Yes - Sitecore provides the ability to single source content and have it rendered on a web site in multiple locations, as well as, multiple web sites under Sitecore management.

The ability to have content saved in multiple locations would be part of the implementation process of Sitecore and the creation of the Sitecore content tree based on specific requirements.

2.3.22 Content is auto-saved while editing to allow for recovery if user inadvertently navigates away from editor.

Out of the box, Sitecore prompts users when navigating from the editor that if they continue they will lose your changes and also asks do you want to save.

Sitecore can be customized to auto save. This is a customization that can be achieved by a Sitecore Certified Developer.

Ability to author content from within browser-based customized forms

2.3.23 Content input forms are completely configurable based on customer requirements (e.g., input forms for Physician bios with multiple fields such as Name, Education, Publications, etc.; input forms for health articles with custom fields such as Title, SubTitle, Author).

YES - Sitecore provides the same ability to create public facing forms to CMS users in the same way that content items used by content authors are created.


2.3.24 Content created from these forms are edited within the same forms.

YES - Just like Content Items are edited by Content Authors logged into the CMS, Public visitors can edit content in Web Forms (which correlate with Sitecore Content Items).


- 16 -

2.3.25 Forms support standard form controls including dropdowns, text areas, WYSIWYG/HTML formatting, radio buttons, and check boxes.

YES - Sitecore is shipped with these field types


2.3.26 Forms have a calendar feature. YES - Sitecore is shipped with this field type.


2.3.27 Forms are accessible from anywhere depending on security/firewalls, etc.

YES - Access to the forms would be completely dependent on security requirements but the application is completely accessible in a browser.


2.3.28 Forms are restricted based on users' access rights.

YES - Access to the forms would be completely dependent on security permission set by the customer


2.3.29 Forms are configurable based on the workflow state of content being edited.

YES - All actions in forms are security driven and can have workflow applied.


2.3.30 Forms are supported on Internet Explorer 6+, Firefox 1.5+ and Safari 2+ browser versions on both Windows and OS X platforms as appropriate.

YES - Sitecore web forms are supported in all browsers for visitors of the site.


2.3.31 Forms support the creation and use of related content (i.e., content stored in related tables).

YES - Sitecore can be implemented to integrate with external data repositories for the rendering of content and data from those tables in Sitecore web forms.

Sitecore is built for integration. Some minor coding will need to be performed to integrate Sitecore with external data repositories.

Form Creation

2.3.32 CMS has a wizard for creating email forms.

YES - Sitecore provides this functionality through the Sitecore Forms module

This is an add-on module that has an additional cost.

- 17 -

2.3.33 CMS has templates for form creation. YES - Sitecore provides this functionality through the Sitecore Forms module

This is an add-on module that has an additional cost.

2.3.34 Forms wizard can create forms that are directed to one of multiple email recipients.


This is an add-on module that has an additional cost; some minor coding on the module is needed but would be considered part of the standard implementation.

2.3.35 Forms wizard can create forms to sort directories (i.e., physician directory search form).


The custom field control will need to be developed by a .Net developer if the directory is outside of Sitecore.

2.3.36 Forms wizard can create forms that have fields that populate based on the selection of a previous field (i.e., subspecialties based on choice of specialty).

YES - Sitecore provides the dynamic generation of content in fields based on other fields in an item.

The custom field control will need to be developed by a .Net / Sitecore developer.

Special Features

2.3.37 CMS supports use of server-side includes (SSI), or some way to handle content reuse.

YES - Sitecore stores all content as tagged XML. Content is completely separated from presentation which provides for complete content reuse across the site or across multiple sites.


- 18 -

2.4 Design

2.4.1 CMS has template creation wizard. Sitecore provides the Developer Center application for browser based development tasks. Most Sitecore developers prefer using MS Visual Studio fro coding and aspx template creation / manipulation. Sitecore also supports the use of applications like Dreamweaver, etc. for the main layout creation.

Most of the look and feel of Sitecore sites is performed by standard .Net web development tasks and applications.

2.4.2 CMS accepts templates created in external programs such as Dreamweaver, BBEdit or Visual Studio.

YES - Most developers work in Visual Studio, but layouts can be created in applications such as Dreamweaver. The objects and .NET controls dropped on to the layout are most likely created in Visual Studio.

Most of the look and feel of Sitecore sites is performed by standard .Net web development tasks and applications.

2.4.3 Coding from external programs can be copied as code or as WYSIWYG.

YES - Coding for external applications or programs can be placed on Sitecore managed aspx and run independent of the CMS.


- 19 -

2.4.4 All tags remain intact when copied into the CMS.

Sitecore completely separates content from presentation. The tags of the content will be stored in the database (XML tags). Current content will need to be migrated to CMS structured XML hierarchy.

IF code is copied and placed on the layout managed by Sitecore but the items referenced in the code are outside of CMS then the tags will remain.

2.4.5 All Javascript elements remain intact when copied into the CMS.

The Javascript would need to be rewritten as the content now resides in a database as tagged XML.

The creation of Javascript would be performed by a developer.

2.4.6 CMS provides validation of Javascript code.

Once the Java Script is on managed Sitecore pages, then validation can occur.

The creation of Javascript would be performed by a developer.

2.4.7 All form elements remain intact when copied into the CMS.

Sitecore would most likely require that new forms are created, as Sitecore completely separates content from presentation. If Tufts required a completely separate .Net web form and having the data entered not be stored in the CMS then this would be correct.

The creation of the form would need to be performed by a developer or the Sitecore Forms module (add-on)

2.4.8 Changes to the templates can be made within the CMS.

Yes - Through the Sitecore Template Manager and the Developer Center.


2.4.9 Changes to the templates reflect immediately.

YES - the changes can take immediate effect.


- 20 -

2.4.10 Different templates can be applied to pages without re-entering content.

YES - Sitecore completely separates content from presentation, thus making it very easy to set separate presentation layers to the same content item.


2.4.11 Server-side code can be included in the template.

YES - Sitecore provides the ability to have server side code placed on all design / presentation layers.


2.4.12 The templating engine inserts code or comments not included in the template.

YES - Sitecore pages are made up of controls or objects, which are all independent code or renderings which render content or design aspects based on the object itself.


2.4.13 Describe the skill set and training necessary to develop templates in the CMS.

Development of presentation components requires knowledge of HTML and Sitecore's templating infrastructure. HTML developers can easily learn XSL with Sitecore. Advanced developers use .NET.

Sitecore also offers training to developers.

- 21 -

2.4.14 Describe how the CMS would handle a re-design of the site.

Typically, all content pages combine a single master layout with some number of sublayouts and renderings. Rebranding can often be accomplished by updating the master layout, or the CSS file it references, but in other cases, the settings controlling which presentation components are used for each content type may be updated.


Cascading Style Sheets

2.4.15 CMS supports uploading of cascading style sheets (CSS).

YES - This is a standard practice


2.4.16 CMS provides a way to link to CSS from individual pages, groups of pages, or from the entire site.

YES - Typically, all pages within a section inherit a CSS file referenced by the section item, but much more complex scenarios are supported.


2.4.17 CMS supports multiple style sheets. Yes - This is completely supported. There is no limit.


2.4.18 CMS supports editing of CSS. YES - This can be accomplished in eh same manner by which CSS is being edited today.


- 22 -

2.4.19 CSS attribute tags are color-coded to prevent errors.

Sitecore does not provide this in the browser based UI of the developer center but does provide seamless integration with other development tools such as Visual Studio to assist in this requirement.

The integration with Visual Studio requires no customization. It is built in.

2.4.20 CMS validates CSS and identifies code-violations visually.

Sitecore does not provide this in the browser based UI of the developer center but does provide seamless integration with other development tools such as Visual Studio to assist in this requirement.

The integration with Visual Studio requires no customization. It is built in.

2.5 Version Control & Workflow

Version Control

2.5.1 CMS maintains revisions of all content. YES - Sitecore stores all past versions of content and assets


2.5.2 CMS allows rollback of revisions. YES - Sitecore provides easy roll back of all past versions and revisions.


2.5.3 CMS provides reporting of revision history.

YES - Sitecore provides version history on all content items.


2.5.4 CMS allows for comparison of two revisions of content.

YES - Sitecore provides the compare function of past versions.


2.5.5 CMS allows versions of content to be created.

YES - Sitecore provides the ability to current new versions of content.


- 23 -

2.5.6 CMS provides reporting of version history.

YES - Sitecore provides version history on all content items.


2.5.7 CMS enables check-out and check-in of documents, pages, content and digital assets as they are edited and saved.

YES - Sitecore provides checking in & checking out of content, data, assets, etc.


2.5.8 Users can see and use, but not edit, checked-out content.

YES - Users can see items that are checked out and see who has checked them out.


2.5.9 Content checkout locks can be overridden by a manager in the event of situations requiring urgent edits.

YES - higher level users can check items back in on lower users behalf.


2.5.10 CMS supports the notion of a promotable version (i.e., a cloned version of content that can be changed and then promoted to take the place of the previous version at a certain point in the workflow).

YES - This action is completely support through standard Sitecore workflow.


Workflow

2.5.11 Workflow processes can be configurable based on existing business processes.

YES - Sitecore provides completely workflow freedom / flexibility. Customers create workflows that make sense to each item.


2.5.12 CMS can workflow Web content, documents, images and digital assets.

YES - Anything in Sitecore can have a workflow applied.


2.5.13 CMS provides one workflow engine to manage all types of content (e.g., Web content, documents, digital assets, etc.).

YES - Sitecore provides the internal Sitecore workflow engine for all actions.


2.5.14 CMS allows many workflow processes to be created, with no restriction on the number of states.

YES - Sitecore does not limit the number of workflows or steps and branches in each workflow process.


- 24 -

2.5.15 Workflow processes can be modified after creation while content is in process.

YES - Workflow is handled in the same way as content. They can be edited and managed anytime.


2.5.16 Workflow supports aging. YES - This is completely supported as part of the configuration of the workflow process.


2.5.17 Workflow processes are flexible, supporting ad-hoc assignment of content to users.

YES - Sitecore provides the most flexible workflow engine in the market today. Ad-hoc assignments of content to users on the fly is completely supported.


2.5.18 Workflow can require a minimum number of approvers.

YES - Sitecore provides the ability to set the number of approvers for each stage of a workflow action.

This would require some minimal development to create the rule to support more than one approver to have to approve a piece of content prior to being moved along to the next step of the workflow.

2.5.19 Workflow integrates with our current email system for notifications (IMAP and SMTP) and potential future email systems (e.g. Microsoft Exchange server).

YES - All e-mail systems can be used with Sitecore workflow.


2.5.20 Each workflow can have a custom email message associated with it.

YES - Sitecore provides the ability for CMS workflow created to customize the message for each workflow state.


2.5.21 CMS allows all content (regardless of entry point to the CMS) to be automatically allocated to a workflow step.

YES - All content derived from any entry point can have a workflow applied.


- 25 -

2.5.22 Content editing can be restricted on a field-by-field basis by workflow state.

YES - Sitecore security gets as granular as to each field of an item.


2.5.23 Content viewing can be restricted on a field-by-field basis by workflow state.



2.5.24 Content usage/reuse can be restricted on a field-by-field basis by workflow state.



User Groups & Roles

2.5.25 Users can be allocated to one or many user groups.

YES - Sitecore provides the ability to apply a user to multiple roles.


2.5.26 CMS provide access or restriction to CMS functionality based on user groups.

YES - Core component of Sitecore security


2.5.27 Content types can be restricted based on user groups.

YES - Sitecore provides the ability to apply all security permission tasks through roles, including access to Content types.


2.5.28 Templates can be restricted based on user groups.

YES - Sitecore provides the ability to apply all security permission tasks through roles, including access to Templates or Layouts.


2.5.29 Users can be added at any time. YES - Sitecore provides the ability to add new users through the easy to use User Manager application, or Sitecore can be integrated with MS AD and new users can be added through AD.


- 26 -

2.5.30 User names can be changed at any time.

YES - Performed through the User Manager by default. Can be also accessed through each user's Control Panel on the Desktop interface.


2.5.31 Roles can be added at any time. YES - Sitecore provides this ability to create to roles through the User Manager.


2.5.32 Role names can be changed at any time.

YES - Performed through the User Manager application.


2.5.33 Users can be assigned to one or many roles.

YES - There is no limit on how many roles each users can take part in.


2.5.34 CMS supports access control lists. YES - This is provided through the Security Editor interface provided to Sitecore Admins.


2.5.35 CMS does not restrict the number of roles or type of roles.

YES - There is no limit on how many roles can be defined.


2.5.36 User groups and roles can be automatically assigned based on Microsoft Active Directory groups.

YES - Sitecore provides complete integration with MS Active Directory through the Sitecore LDAP module

The Sitecore LDAP module is an add-on module sold by Sitecore.

2.5.37 User groups and roles can be automatically assigned based on a web service.

YES - Sitecore completely supports the use of web services for the communication of actions from 3rd party or external applications.

The support of web services is an out of the box function of Sitecore. The creation of the web service would be performed by developers.

2.6 Content Management

User Interface

- 27 -

2.6.1 CMS provides multiple interfaces (e.g., advanced vs. simple).

YES - Sitecore provides several interfaces which can be accessed to users based on their comfort level, very non-technical to technical.


2.6.2 Content is organized visually using a familiar paradigm such as folders or hierarchical trees.

YES - Sitecore stores all content in a hierarchy. Content is organized and access in this content tree format.


2.6.3 CMS supports drag and drop movement of content, pages, documents and digital assets.

YES - Completely supports drag and drop of all items.


2.6.4 CMS provides ability to delete single or multiple content records (e.g., HTML, PDF, image, and others) permanently, only after agreeing to caution message.

YES - Deletion rights is a security permission, but if one has access to the function, he or she can delete one or a several items after receiving a warning.


2.6.5 CMS alerts users that a page, content, document or digital asset they are attempting to remove is linked to from other pages within the system.

YES - Sitecore provides on the fly link management.


2.6.6 CMS allows content to be copied resulting in the creation of new content.

YES - Sitecore provides copy and paste of content items and assets, as well as the ability to duplicate.


2.6.7 Content can be moved or relocated. YES - Sitecore allows the movement of all items under management.


Content Organization

- 28 -

2.6.8 CMS supports sorting of content records (i.e., by date modified, name, author, or custom).

YES - Sitecore provides customers with the ability to organize content in a manner which makes the most since for abstracting the items to be rendered on the dynamic web pages of Sitecore but also to be located in the content tree by web editors.


2.6.9 Content can be used and exist in more than one organizational location without requiring copies to be made.

YES - Sitecore provides the ability for content items to live in several locations in the content tree, and providing single source editing from one location or editing points at each location.


2.6.10 CMS supports multiple organizational hierarchies simultaneously.

YES - Sitecore provides customers with the ability to organize content in a manner which makes the most since for abstracting the items to be rendered on the dynamic web pages of Sitecore but also to be located in the content tree by web editors.


2.6.11 Organizational hierarchy reflects site structure.

YES - Customers can have their content tree directly reflect site structure.


- 29 -

2.6.12 Organizational hierarchy reflects physical folder structure.

Sitecore stores content in a database as tagged XML. The Sitecore content tree reflects a visual representation of the XML repository of the database. Sitecore does provide the ability to organize content in folders, but the content is not stored as files. The content tree can reflect a physical file folder.


2.6.13 Organizational hierarchy represents different views of content (e.g., based on metadata).

YES - The Sitecore content tree can be organized based on metadata tagging fields on each item created (i.e. news story tagged political will be stored in the Political News folder in the content tree once created).

Sitecore completely supports dynamic content tree creation based on tags. The logic to dynamic organize items in a tree would need to be implemented through some coding by a developer.

2.6.14 Organizational unit (e.g. folder) content can be secured based on user group.

YES - All items in the Sitecore content tree can be secured based on roles.


2.6.15 Organizational unit content can be secured based on role.

YES - All items in the Sitecore content tree can be secured based on roles.


2.6.16 Organizational unit content can be secured based on user.

YES - All items in the Sitecore content tree can be secured based on roles or even on the user level.


- 30 -

2.6.17 CMS provides the ability to view content currently checked out to a user.

YES - Users can view content that has been checked out to other users. Power users can check in back in.


2.6.18 CMS provides the ability to view content recently viewed based on date.

YES - Sitecore provides the ability to see the last version modified or viewed.


2.6.19 CMS provides the ability to search for content in the file repository.

Content is not stored as files with Sitecore. Content is stored as tagged XML in the database. Sitecore does provide the ability to search for file based assets that reside in a file system to be used or referenced in a Sitecore item.

The ability to integrate Sitecore with an external file repository is easily performed by a developer with some minimal documented coding.

2.6.20 CMS provides the ability to search for content in the image repository.

YES - Sitecore provides the Media Library for the storage, search, and management of all file based assets, including images.


Relationship Management

2.6.21 Content can be related to other content based on customized rules.

YES - relationship of content can be applied based on custom rules.

Sitecore supports the creation and use of custom rules. The creation of the rules would be considered a customization that would be applied during the implementation process.

- 31 -

2.6.22 CMS provides ability to manage and maintain all relationships (i.e., dependencies) among content.

YES - all relationships between content, whether they are created by tagging or through another field property, can be managed by Sitecore.


2.6.23 CMS creates relationships automatically when content is copied.

YES - This would be dependent on how the relationship rules were created during the implementation process but Sitecore can completely support the relationships of content during the copy and pasting process.

This is dependent on the implementation of the relationship rules, but once the rules are implemented this requirement can be completely supported.

2.6.24 CMS creates relationships automatically when content is versioned.

YES - If the rules are based on tagging or other custom fields, the relationships will not be affected or will be created based upon those fields being edited.


2.6.25 CMS creates relationships automatically when content is translated.

YES - The same relationship that exists for the original language in which the content was created in will be applied to the other subsequent language versions.


2.6.26 CMS creates relationships automatically when content is moved.

YES - With Sitecore relationships can be defined based on location in the content tree.

The rules for the relationships would need to be defined and created by developers.

- 32 -

2.6.27 CMS creates relationships automatically when content is linked.

YES - When content is linked to other managed items in Sitecore, relationships are created.


2.6.28 CMS creates relationships automatically when content is viewed by site visitors.

Sitecore can be implemented to create specific relationships based on web statistics, i.e. most viewed news articles to be rendered on the home page.

Sitecore completely supports the automatic generation of relationships based on web statistics. The implementation of the rules or controls that create the rules would need to be created by developers.

2.6.29 Relationships are viewable to assess the impact of changes to content.

YES - Sitecore provides the Carousel interface to view all relationships within the CMS.


2.6.30 CMS supports the creation of new relationship types to meet custom requirements.

YES - Sitecore is extremely flexible and provides a developer framework to create custom relationships and provides an application that can meet any requirement from very simple to extremely complex.

All custom relationship types and the ability to meet custom requirements would be part of the strategy, implementation, and custom development work required based on specific requirements detailed.

2.6.31 CMS uses relationships to enforce no redundant copies of content.

YES - Sitecore provides the single sourcing of content to provide customers with the ability to have only one content item used in several locations on one or several sites, and in several ways.


- 33 -

2.6.32 CMS uses relationships to enforce custom rules (e.g., all content related to a page get published together).

YES - Sitecore can be implemented to enforce all custom rules developed at time of development.

Specific enforcement of rules would need to be coded by developers.

2.6.33 CMS uses relationships to suggest relevant related content to content authors and editors as well as site visitors.

YES - Sitecore can be implemented to provide relevant content in dynamic fields based on other fields such as tagging fields. Related content rendered on the public facing site can be achieved through similar tagging attributes.

The creation of the rules and custom fields will need to be developed by Sitecore developers. Minimal coding will need to be performed. The creation of custom controls to render related content would be part of a standard implementation requirement / process.

2.6.34 Relationships can be defined as "strong" or "weak," invoking appropriate workflow, or delivery actions.

YES - Sitecore provides the ability to create custom field properties that define specific workflows for the content item to flow through.

The creation of the custom field property would need to be accomplished by a .NET developer.

2.6.35 CMS invokes appropriate delivery actions when relationships among content are changed.

YES - Sitecore will publish accordingly based on relationship changes occurring.


Link Checking

2.6.36 CMS maintains and maps all links to images.

YES - Sitecore manages all links to assets through the link management application.


2.6.37 CMS maintains and maps all links to binaries (e.g., PDFs, Flash, etc.).

YES - Sitecore manages all links to assets through the link management application.


- 34 -

2.6.38 CMS maintains and maps all links to other pages.

YES - Sitecore manages all links to content items through the link management application.


2.6.39 CMS provides reporting on all content interdependencies.

YES - This is provided through the Carousel interface, which provides a graphic representation of all interdependencies.


2.6.40 CMS enforces no broken links. YES - Sitecore provides broken link reports, as well as, on the fly notification when a user is about to create a broken link when continuing an action.


2.6.41 CMS provides reporting on broken links. YES - Sitecore provides the broken link report through the Desktop interface.


2.6.42 CMS provides the ability to find and replace text strings globally, with the ability to see where changes are made.

Partial - Sitecore provides the ability to have developers globally find and replace. Sitecore does not offer this out of the box out of fear of errors in replacing content that did not want to be replaced.

A customization or can be achieved by developers or internal IT.

2.6.43 CMS provides ability to find and replace within a specified section of the site.

YES - Sitecore provides the ability to find and replace content with in fields.


- 35 -

2.6.44 CMS provides pre-built (out-of-the-box) content types for the homepage.

No - Sitecore does not provide pre-built content types, but provides an interface to build your own. The standard building time of a content item in Sitecore is 2 minutes.

All content item types will need to be created in the template manager.

2.6.45 CMS provides pre-built (out-of-the-box) content types for press releases.



2.6.46 CMS provides pre-built (out-of-the-box) content types for events.



2.6.47 CMS provides pre-built (out-of-the-box) content types for calendars.

YES - Through the Sitecore Calendar Module pre-built calendar items are provided.

The Sitecore Calendar module is an add-on in which Sitecore sells.

2.6.48 CMS provides pre-built (out-of-the-box) content types for directories.



- 36 -

2.6.49 CMS provides pre-built (out-of-the-box) content types for indices.



2.6.50 CMS provides the ability to manage navigation.

Yes - Sitecore provides the ability to create navigation on the fly based on the content tree and the navigation controls dropped onto the Sitecore presentation layers.

The Navigation controls can be downloaded from the Sitecore Developer Portal and / or create by developers.

2.6.51 CMS provides the ability to manage site maps.

YES - Sitecore provides the ability to create Site maps as a web control.

Sitecore provides the Site Map web control at no cost. It is a standard feature.

2.6.52 CMS provides the ability to manage breadcrumbs based on either organizational hierarchy or navigational history.

YES - The Sitecore breadcrumb control is rendered based on the organizational hierarchy or navigation history.

The configuration of this standard feature can be provided easily by a Sitecore developer.

- 37 -

2.6.53 CMS provides the ability to manage pieces of content that can easily be reused (e.g., contacts on press releases).

YES - All items in Sitecore can easily be reused.

The ability to have items reused across sites or across one site is a standard feature of Sitecore, as Sitecore completely separates content from presentation, and a dynamic web rendering engine. The rendering that calls on that specific item can be dropped on any aspx template in which it is needed, thus resulting in several web pages calling on the same item in the content tree.

Navigation

2.6.54 Users can indicate which items should be included in the navigation menus and which should be excluded.

YES - A field property can be created to state if the item should be represented in specific navigation elements, where the item is created in the content tree can also directly reflect the navigation elements it will be rendered in, and lastly, tagging fields can dynamic change navigation.

All rules to change navigation settings would be part of the standard implementation process of the Sitecore CMS.

- 38 -

2.6.55 CMS provides the ability to change navigation without requiring changes to templates.

YES - Navigation is a .Net control that is dropped on aspx templates. The navigation can be changed on the content item. With Sitecore templates are only access dif design changes are required.


2.6.56 CMS provides the ability to customize navigation based on the current section/page.

YES - Navigation can be dependent on the hierarchy of the content tree, i.e. the hierarchy of the section of page that is being accessed.


Error Handling

2.6.57 CMS offers appropriate "Are you sure?" messages to ensure a minimum of deletion errors.

YES - Sitecore provides a warning before deletion


2.6.58 CMS provides the ability to establish shortened "vanity" URLs.

YES - This is provided through the Sitecore Alias URL interface.


2.6.59 URLs are not case-sensitive. YES - Specific URL rules can be created for each customer.

Sitecore is shipped with non case sensitive URLs, but rules can be applied to provide validation on the create of URL keywords.

2.6.60 CMS automatically redirects moved URLs to the new location.

YES - All links and URLs are redirected automatically by the Sitecore link manager.


2.6.61 CMS allows for custom redirects from any URL within the site, including URLs not actually ever associated to a page or digital asset, to any other URL including outside of the site’s structure.

YES - Sitecore completely supports the redirecting of URLs for none Sitecore managed pages or assets.


- 39 -

2.6.62 CMS allows files with the same name to exist in different sections or folders within the system (i.e., two different "newsletter.pdf" can reside in both /news/may05/ and /news/june05).

YES - Sitecore provides the ability to have the same named items stored in the CMS as Sitecore is GUID driven.


2.6.63 CMS does not create multiple versions of a static URL (such as "Default2446.html" for a file named "about.html").

YES - Sitecore's URLs are dynamic not static. They are also not file based but represent the content storage hierarchy.


2.6.64 CMS allows users and/or automated policies to determine naming for each page.

YES - the naming for each page can be a field value on the content item, or it can be dynamically created based on policies or rules.


Metadata

2.6.65 CMS prompts for the input of metadata elements.

YES - Sitecore can have validation rules set for any fields.


2.6.66 CMS requires metadata when specified. YES - Sitecore can have validation rules set for any fields.


2.6.67 CMS records date of content creation. YES - Sitecore by default stores the date of content creation.


2.6.68 CMS enables time-stamping ("page last updated on mm-dd-yyyy").

YES - Sitecore date / time stamps each event with in the CMS for admins to view.


2.6.69 CMS records date of an event or deadline contained in the content.

YES - Sitecore can store any attribute of a content item including a date or deadline.


- 40 -

2.6.70 CMS records date for future publication. YES - Sitecore provides the ability to set publication dates in the future through the Change Publishing Settings wizard.


2.6.71 CMS records date on which the content creator should be prompted to review.

YES - Sitecore can have a field created on an item for review submission

The creation of the rule to delay workflow submission to approver would need to be created by a developer. This would require minimal coding.

2.6.72 CMS records date of content obsolescence.

YES - Sitecore stores the date in which content is unpublished.


2.6.73 CMS provides option to override required date information, in essence making some content "evergreen".

YES - This would be an optional rule that can be created.

This requirement would be considered a custom development task but would be achieved with minimal coding.

2.6.74 CMS uses date-related metadata elements to remove or change links to content from compiled pages without intervention by content editors (with notification via workflow, as needed).

YES - This is completely supported by Sitecore if content is unpublished. They will also change when tags are changed if the hierarchy is being rendered by tags.


2.6.75 CMS uses date-related metadata elements to: • create compiled pages of date-sensitive event pages. • publish pages at a specified future date. • prompt content editors to renew or remove content. • delete content if no action is taken to retain it. • move content to an off-site archive.

YES - Date metadata can be used for these actions.

Rules will need to be created for some of these items by Developers (i.e. Prompt editors to renew or remove content and move content to an off-site archive). All other functions are standard.

- 41 -

2.6.76 CMS records content author. YES - Every action with a content item is stamped by the user who carries out the action.


2.6.77 User-identifying metadata elements can be applied automatically to all content created by a user.

YES - Global content can be syndicated to specific users based on the content they touch. This is performed by having dynamic rendering of field values.

Some coding would need to be performed to create the dynamic field property.

2.6.78 CMS records content subject. YES - Content subject would be a field on the item. The field value can be stored and used for any purpose.


2.6.79 Subject-identifying metadata elements can be applied automatically for specified content, with the ability to override when necessary.

YES - Sitecore provides the ability to have default values for fields and have the ability to override those values during the editing process or through another stage in the workflow.


2.6.80 CMS accommodates custom-defined taxonomy and prompts content editors to select approved subject-identifying metadata elements.

YES - This is completely supported as Sitecore provides sources for fields of content items. Custom taxonomies can be set as field source and be used as the taxonomy structures for the item.


- 42 -

2.6.81 CMS can record a free-form description of the content.

YES - Free form description would be a field on the item. The field value can be stored and used for any purpose.


2.6.82 CMS can record keywords. YES - The keyword values can be stored in Sitecore and those keywords can be used as field source data to be accessed in fields in content items.


2.6.83 CMS provides the ability to create and maintain a non-displaying "notes".

YES - This would be another field in Sitecore. Not all fields are displayed. Fields can be used for tagging, URLs, or even notes.


Multisite Management

2.6.84 CMS allows the creation and management of multiple domain names.

YES - Sitecore is built for multisite management


2.6.85 CMS provides the ability to create and maintain directory names and file names.

YES - Sitecore provides the ability to create separate content tree nodes for each site (Sitecore does not store content as files).


2.6.86 CMS provides the ability to clone entire content items, including all metadata elements, not just textual content.

YES - Sitecore provides the ability to create / clone entire content items (all).


- 43 -

2.6.87 CMS allows content to be reused in two or more places on the same site without making a copy of the content (i.e., single sourcing).

YES - Content can be reused limitlessly in Sitecore. This is because Sitecore completely separates content from presentation. Content is rendered on the site based on controls or objects calling on the data base or Sitecore APIs for specific fields on content item(s).


2.6.88 CMS allows different templates (look and feel) to be applied to the same content.

YES - Sitecore completely separates content from presentation, thus providing the ability to set separate look and feels to the same content.


2.6.89 CMS automatically manages the dependencies and relationships between content across multiple sites (e.g., A press release appears on two sites - when one is unpublished, the other must also be unpublished automatically).

YES - Sitecore automatically manages dependencies of content b/c content is single sourced. If unpublished all dependencies and relationships across of sites will be handled seamlessly.


2.7 Digital Assessment Management

Digital Assessment Management

2.7.1 CMS can import multiple digital assets in an automated way.

YES - Sitecore provides bulk upload of assets


2.7.2 CMS can automatically extract digital asset metadata upon import.

YES - Sitecore can import metadata values once uploaded.


2.7.3 CMS can index multiple types of digital assets.

YES - Sitecore has no limits to what assets can be indexed.


- 44 -

2.7.4 CMS provides search capabilities for multiple types of digital assets.

YES - internal search can index any type of assets.


2.7.5 Digital assets can be manipulated via a Web interface.

YES - Images can be manipulated, as well as, asset attributes.


2.7.6 Digital assets can be manipulated in the CMS with the same UI as all other types of assets.

YES - All Sitecore UIs are based off of the same look and feel.


2.7.7 Users can email shortcuts to digital assets residing in the CMS.

YES - Digital Assets stored in eh CMS have url paths that can be e-mailed to other users.


2.7.8 Users can group digital assets into projects for easy collaboration.

Sitecore provides the ability to create security permission folders that only specific users or roles have access to. The ability to build items in a collaborative manner is not an out of the box function of Sitecore.

The ability to create security permission based folders of assets is a standard feature.

Other applications, such as SharePoint, can be integrated with Sitecore for collaborative digital asset creation.

2.7.9 Users can easily find out where and how specific digital assets are being reused across multiple Web sites, documents etc.

YES - This is provided through the Carousel interface.


2.7.10 Digital Asset Management capabilities are fully integrated into CMS.

YES - Depending on specific requirements, Sitecore can fulfill even medium level DAM objectives set by each customer.

Sitecore provides an integration framework to integrate robust DAM systems, such as Cumulus or North Plains, if needed.

Graphics/Images

2.7.11 CMS accommodates fast, uncomplicated image uploading, without tedious approvals.

YES - Sitecore allows each customer with eh ability to set upload security permissions.


2.7.12 Images can be uploaded independently of the WYSIWYG editor.

YES - Images can be uploaded within the Sitecore Media Library.


- 45 -

2.7.13 CMS supports batch upload of multiple images.

YES - Sitecore completely supports batch upload.


2.7.14 Users can overwrite images (i.e., replace graphics with the same file name) and PDF files.

YES - Sitecore completely supports overwriting of the same file.


2.7.15 Users can delete graphics and PDFs. YES - Deletion is a security permission based task of any item in Sitecore, including assets.


2.7.16 CMS supports drag and drop of images. YES - Dragging and dropping assets in the Media Library folder hierarchy is completely supported.


2.7.17 CMS provides rendering capabilities. YES - Sitecore provides a dynamic rendering engine.


2.7.18 CMS provides thumbnail views of images in database.

Sitecore stores one image in the media library. The creation of different sizes of the image in several locations is provided by the presentation layer of Sitecore. Sitecore saves the image to disk each place it is being rendered but before that resizes it.


2.7.19 CMS provides image editing capabilities – resize, crop, orientation, and other basic features.

YES - Sitecore is shipped with an Image Editor


Special Formats

2.7.20 CMS supports uploading of multiple media types (e.g., MOV, EPS, PDF, Powerpoint, DHTML, MPEG, streaming video, Real, Quicktime, .ZIP, etc.)

YES - There is no restriction of files under management.


- 46 -

2.7.21 CMS supports Flash presentations. YES - There is no design restrictions with Sitecore. Sitecore currently has several flash intensive sites as clients.


2.8 Special Features

Newsletter

2.8.1 CMS provides the ability to create and distribute newsletters. If not, please describe how this could be accomplished.

YES - Sitecore provides Newsletter functionality through the Newsletter Module. Sitecore can also be integrated with E-marketing leaders such as Exacttarget, etc.

The Sitecore Newsletter module is an add-on that Sitecore sells. Integration with external 3rd party applications would take development resources.

2.8.2 CMS provides the ability for visitors to sign-up for newsletters.

YES - This is provided through the module.


2.8.3 CMS provides the ability to manage the newsletter subscribers.

YES - This is provided through the module.


Constituent Relationship

2.8.4 CMS provides ability to personalize content to the activities and interest of registered users.

YES - Sitecore completely supports personalization because of its dynamic page generation engine and its object oriented pages.

The creation of the controls that are dropped on to the aspx templates that render specific content based on registered users profile would require a .Net web / Sitecore developer.

2.8.5 CMS provides the ability to password protect specific sections of the site.

YES - This is provided through the Sitecore Extranet Domain


2.8.6 Please describe how this could be accomplished if not built into the CMS.

Built in to the CMS This is a standard feature.

Surveys

- 47 -

2.8.7 CMS provides the ability to create surveys and quizzes.

YES - This is provided through the Sitecore Polls / Survey module. It could also be accomplished by creating data structures for the quizzes or surveys using core Sitecore development.

Sitecore does not charge for the Polls / Survey module, which is an additional component to Sitecore.

2.8.8 CMS provides the ability to score the surveys and/or quizzes and display the results.

YES - The quiz or survey results will be stored in Sitecore just like all other content. Once in Sitecore it can be manipulated in any way.

The controls to render the results would be created by developers.

Calendar

2.8.9 CMS provides an online calendar function for visitors.

YES - This is provided through the Sitecore Calendar module.


2.8.10 Users can customize the online calendar.

YES - Users can have extranet calendars, calendars that only rendered specific tagged events, and can change the look and feel of the calendar.


2.9 Content Delivery

Content Preview

2.9.1 CMS provides content staging functionality.

YES - Sitecore is shipped with the Preview Mode for staging purposes


- 48 -

2.9.2 CMS provides ability to show unpublished work in progress to outside groups, and restrict their access based on established criteria or permissions.

YES - This is can occur using the Preview Mode and using Workflow processes. A Workflow process can be create to display preview snapshots or access to the preview mode to show unpublished work to others.


2.9.3 CMS automatically refreshes preview screen based on modifications.

YES - The Preview mode is a dynamic page generation system that dynamically renders pages based on the saved changes to the item. It also uses Sitecore's single source of content ability to show how the changes to the item will affect the entire site (s).


2.9.4 How will the CMS manage uploaded content between the staging server(s) and the live server(s)?

Sitecore does not upload files as content is not stored as files, content is stored in a database. Sitecore publishes from one database repository to another (Master DB to the Web DB). This is a large advantage to other database driven CMSs as Sitecore who just replicate the database. Sitecore does an actually publish of the latest version of data.


Publishing

- 49 -

2.9.5 Publishing results in immediate visibility of the new content.

YES - Sitecore publishes to the web database and clears the cache on the web servers through the add-on staging module.

The Sitecore staging module is an add on module sold by Sitecore.

2.9.6 Dynamic pages update immediately upon publishing.

YES - Sitecore publishes to the web database and clears the cache on the web servers through the add-on staging module.

The Sitecore staging module is an add on module sold by Sitecore.

2.9.7 Publication can be scheduled. YES - Sitecore provides the option to have live publishing or to have publishing conducted as a scheduled task.


2.9.8 CMS provides ability to specify a "copyright date" (persistent yet modifiable, in case of error) for all pages. The copyright date will not change on republication.

YES - Sitecore provides the ability to hard code data such as copyright date on the presentation layers themselves. Copyright date can also be part of a content item that is referenced in a web control that is un editable.


- 50 -

2.9.9 CMS allows content to be published to new sites or new delivery destinations (not planned) without requiring any additional coding.

YES - Sitecore provides the ability to create new publishing targets without any coding. If an item was create in Site A and you want that item to be rendered in Site B, this can be accomplished through Sitecore UIs by Admins. This is assuming Site A and B are managed Sitecore web properties.


2.9.10 CMS allows publishing to be based on folder structure.

Sitecore does not store content has files. Sitecore does support the use of folders in eh content tree for the organization of content items. Sitecore also supports publishing static versions to the site to a file folder hierarchy if needed.

More information would need to be obtained by Sitecore to dig into how Sitecore would handle this requirement, but it seems it would be part of the implementation process.

2.9.11 Users can specify portion of site to be published.

YES - Sitecore provides incremental publishing options to publish one item, one section , or one sub section of the site.


2.9.12 Users can specify portions of pages to be published.

YES - Sitecore pages are broken up into separate objects or controls. Each control can be separately published based on eh content that it is rendering.


- 51 -

2.9.13 CMS allows publishing to be based on queries to filter content based on business rules (e.g., all content that has been archived in the last 3 months except for press releases).

YES - Sitecore page objects or controls can easily have business rules to only render specific content from the Sitecore content tree.


2.9.14 CMS allows editions (for publishing) to be based on • sites. • sub-sites. • Special version of the site (e.g., a monthly online publication). • Future versions of the site (e.g., to prepare for a product launch).

YES - Sitecore provides the ability to version pieces of content, sections of sites, or sites themselves. Sitecore also provides the ability to set publication dates and times for all items discussed above.


2.9.15 If the CMS is disabled, the supported site will still run.

YES - With Sitecore customers have the option to separate the Content Authoring environment from the Content Delivery environment (separate servers). If the CMS server went down the CSM delivery server will still be rendering web pages and visitors would not know of the CMS server issues.


Archiving

2.9.16 CMS provides ability to temporarily flag content as "unavailable" to the public.

YES - Sitecore provides the ability to tag content as unpublished, to make it temp unavailable to the public.


- 52 -

2.9.17 CMS provides ability to inactivate content.

YES - Sitecore provides a separate database called the archive database for the storing of archived content and assets that customers no longer want to make available to content authors.


2.9.18 Inactivation can be scheduled. YES - Sitecore provides the ability to archive or even unpublished content to assets by setting specific dates and times.


2.10 Search, Categorization and Reporting

Repository Search

2.10.1 CMS provides a repository search engine.

YES - Sitecore is shipped with the Lucene Search engine for internal CMS search.


2.10.2 CMS search engine provides the capability of acting (editing, deleting) on specific items within the result set.

YES - CMS users have the ability to act on each item in the search results.


2.10.3 CMS search engine can search all metadata.

YES - The Lucene search engine provides the ability to search metadata values


2.10.4 CMS search engine provides field and combined-field searching using logical operators.

YES - Lucene provides field and combine field searching.


- 53 -

2.10.5 Content Search for Visitors NO - Sitecore is not shipped with an external search product. Sitecore currently has several Enterprise Search Partners and also integrated with search leaders such as MS or Google.

External Search applications would be an additional purchase and professional services would be required to implement the search on the public facing site.

Sitecore offers Coveo search at a 50% discount on the product based on Sitecore's partnership.

2.10.6 CMS includes a content search capability.

YES - This is included with Lucene.


2.10.7 CMS provides both full-text search and native RDBMS search.

YES - This is included with Lucene.


2.10.8 Search is fully integrated. YES - Search is fully integrated for internal CMS search. For external search, a 3rd party product will need to be integrated.

Internal search is integrated as standard feature. External search would be additional professional services.

2.10.9 Searches respect the underlying permissions of repositories and content.

YES - All permissions and access to items is respected with the internal search of the CMS


2.10.10 Search results format can be customized.

YES - Lucene is an open source search product that can easily be customized by web developers.

Customization of the search results and search functionality can be accomplished through professional services or internal web development.

2.10.11 Visitors can search all standard and custom content and metadata properties.

YES - Lucene provides search to all fields with in a content item.


2.10.12 Boolean searches are supported. YES - This is supported by the enterprise level search products that can be integrated with Sitecore.

A 3rd party search product will need to be purchased.

- 54 -

2.10.13 Pattern searches are supported. YES - This is supported by the enterprise level search products that can be integrated with Sitecore.


2.10.14 Search engine accounts for misspellings in queries.

YES - This is supported by the enterprise level search products that can be integrated with Sitecore.


2.10.15 Search engine supports searching in multiple languages.

YES - all languages in Sitecore can have search allocated.


2.10.16 Advanced search is supported. Sitecore would need to know what types of requirements are being referenced to regarding advanced search. Most advanced search can be achieved by customizing Lucene or by adding a 3rd party application.

For advanced search requirements, customization to the lucene search engine or adding a 3rd party module would be required.

2.10.17 Users can specify filter properties to appear in search dialog.

YES - The Lucene and the 3rd party search tools on the market today provide the ability to customize filter properties for users search the CMS.

The added of filter properties would be considered a customization that would require some minimal coding.

2.10.18 Interactive capabilities are available for building query-based searches.

This is provided by 3rd party search tools that Sitecore has been integrated with, such as Coveo.

This would be a 3rd party application that would need to be purchased.

Categorization

2.10.19 Content can be categorized manually. YES - Sitecore provides the Uis to categorize all content manually.


- 55 -

2.10.20 Content can be categorized automatically.

YES - Sitecore provides the ability to create rules by which specific content types can be created only in designated areas of the content tree.


2.10.21 Taxonomies are supported. YES - Sitecore supports the simpler to the most robust taxonomy structures.


2.10.22 Taxonomies can be created based on user needs.

YES - Sitecore provides complete freedom in creating taxonomy structures.


2.10.23 Content can be categorized to target it to specific sites or sections of sites.

YES - The categorization of content in Sitecore can directly reflect the sites and sections in which that content will be rendered on the web pages.


Reporting

2.10.24 CMS provide reporting capabilities. YES - Sitecore provides a framework to have developers create custom reports for each customer's specific needs.

The framework to create custom reports is a standard feature.

2.10.25 Reporting is browser-based. YES - Everything in Sitecore is browser based.


2.10.26 CMS includes standard reports. Please describe.

Sitecore is shipped with a broken link report, content / asset repository report, database usage reports, as well as complete access to the log files to create your own reports.


- 56 -

2.10.27 Custom reports can be created. YES - Sitecore leans heavily on the fact that customers want to create custom reports, and provides the framework to do so.


2.10.28 Access to reports can be restricted based on user, role, etc.

YES - Everything in Sitecore can be restricted by user or role.


2.10.29 Reports are viewable through different report formats.

YES - Sitecore can export reports to MS office applications as well have it viewable via the browser based interfaces of the CMS


2.10.30 CMS supports the creation of custom report formats.

YES - Sitecore provides the framework to build reports and report formats.

Sitecore Developers would need to assist in setting up custom report formats.

2.11 Multi-lingual Support

Content Translation

2.11.1 CMS supports the process of translating content into many languages. Please describe.

YES- Sitecore provides side by side translation user interfaces to compare different language versions of an item and to perform translation actions.


2.11.2 Relationships between translated content are maintained and reported.

YES - All relationships are maintained with in Sitecore for translated content.


- 57 -

2.11.3 Workflow triggers are available to synchronize content translation efforts.

YES - Sitecore relies on workflow triggers to mandate translation. With Sitecore items have independent versioning based on the languages the site is supported. Where a mandate would occur to keep all versions consistent would be through workflow.


2.11.4 Workflow triggers are available to inform translators of updates to translated content.

YES - Sitecore provides notification through e-mail, and command buttons for translators to open the translation interfaces for that item.


2.11.5 Publishing of content can be limited to language (e.g., only publish Spanish version).

YES - Sitecore provides the ability to select specific languages during the publishing process.


2.12 Product Architecture, Standards, Technology and Security

Architecture

2.12.1 Describe the proposed hardware architecture.

One production Sitecore content management server on 32-bit or 64-bit Windows supported by a remote SQL Server of equal or greater hardware. One production Sitecore content delivery servers.

This will provide separation of authoring and delivery. Additional servers may need to be added if requirements suggest that a separate development or QA server is required.

- 58 -

2.12.2 Describe the communications and network protocols.

All Sitecore servers communicate with the database server over TCP/IP port 1433 by default. Production content management server communicates with content delivery servers over port 80 (SOAP/HTTP).


2.12.3 Describe the procedures used to detect and identify communications failures.

Sitecore logs all exceptions. Monitor logs, or configure logging to generate email notification.


2.12.4 CMS is able to operate in a heterogeneous environment, leveraging existing: • databases. • application servers. • dynamic delivery systems.

Sitecore leverages the ASP.NET application server supporting integration with any external systems exposing web services or APIs for consumption by .NET.


2.12.5 CMS integrates with existing email systems.

Sitecore sends email messages using the SMTP protocol.


2.12.6 Describe the database architecture. Sitecore provides a middleware layer providing caching and abstracting relational tables as a hierarchy of objects for use by .NET, which is also represented as XML for consumption by XSL. The internal database schema is proprietary - developers work with high level abstractions rather than SQL queries.


- 59 -

2.12.7 Describe the underlying databases that can be used for the CMS repository.

Sitecore supports all editions of Microsoft SQL Server 2000 and 2005, as well as Oracle 9i and higher, and MySQL 5.0.22 or higher. Components developed using the abstraction layers work with any of the supported databases.


2.12.8 CMS repository stores both content and metadata.

Sitecore stores all content, metadata and relations in a single repository. Metadata taxonomies are defined in the same way as content trees. Users manipulate all data through consistent browser-based user interfaces.


2.12.9 Where (in relation to the web server) will the CMS be installed?

Sitecore is typically installed on multiple development and QA web servers, and one production content management web server inside the firewall, as well as multiple content delivery web servers behind a firewall in the DMZ. Content delivery server configuration and/or licensing prevent access to content management user interfaces.


- 60 -

Standards

2.12.10 CMS leverages all standard database systems used within the organization (e.g. SQL). Please describe.

Sitecore communicates with database servers using SQL. Components on the published site can interact with Sitecore APIs or its XML model, or directly with any database or other external system.


2.12.11 CMS provides the capability to pull content from external databases via standard JDBC/ODBC drivers.

ODBC (JDBC is specific to Java).


2.12.12 Describe the database connectivity method.

Sitecore uses standard .NET connection pooling.


2.12.13 CMS does not dictate the use of proprietary adaptations of standard technologies for delivery or templating structures.

Sitecore does not dictate the use of proprietary technology.


2.12.14 CMS is built on an application server platform.

Sitecore leverages the ASP.NET application server.


2.12.15 The .NET platform is supported. Sitecore is a pure ASP.NET solution.


2.12.16 UNICODE is supported. Sitecore stores all data using UTF-8.


Technology

- 61 -

2.12.17 Describe how it is possible to integrate custom-built applications with the CMS.

Sitecore is designed for this purpose. Sitecore treats application pages and content pages in the same manner. Each is an item in the repository and hence the information architecture. Each item containing data and presentation settings controlling which layout, sublayouts and renderings (applications) to invoke when that item is requested on different types of devices (browser, printers, PDAs, RSS readers, etc.).


2.12.18 Do you provide code support with access to the source code for the CMS.

Sitecore is a licensed, closed-source product, but much of the source code is not obfuscated and can be seen using .NET Reflector. Shared source components are available on the Sitecore Developer Network with full source code.

2.12.19 APIs / Web services are provided for specific applications.

YES - Sitecore provides well document APIs, as well as, the ability to use web services that are provided or even the ability for developers to write their own.


- 62 -

2.12.20 Other applications can be launched from within the CMS. Please list.

Any browser-based application can be launched as a popup window or embedded within the CMS user interface. Desktop applications such as PDF readers can also be invoked.


2.12.21 CMS has import/export capability from external sources/applications for both content and metadata.

YES - Sitecore provides the ability to import or export content or data via several methods, such as RSS or standard Sitecore publishing of XML files.


2.12.22 CMS can integrate with third-party tools (e.g., shopping cart).

YES - Sitecore has been integrated with several e-commerce applications such as Commerce Server, MediaChase, AbleCommerce, Digital River, etc.

The ability to integrate is a standard feature of Sitecore. The integration process would requirement development effort.

2.12.23 List the portal products with which the CMS can integrate (e.g., SAP).

Sitecore can integrate with any application that uses web services or has well documented APIs. Sitecore currently has customers who have integrated with SharePoint and SAP.

The ability to integrate is a standard feature of Sitecore. The integration process would requirement development effort.

2.12.24 CMS supports the IIS Web server. YES - Sitecore is a pure ASP.NET application running under IIS.


- 63 -

2.12.25 Content caching is supported. Please describe.

YES - Sitecore provides standard .NET caching as well as, has layers a much more robust Sitecore caching layer for even more caching options.


Security

2.12.26 CMS integrates with LDAP (JNDI) connections.

YES - Sitecore integration with LDAP through the Sitecore LDAP module.

The LDAP module is an add-on sold by Sitecore.

2.12.27 CMS integrates with standard Windows authentication mechanisms.

YES - This is achieved through the Sitecore LDAP module.


2.12.28 CMS provides mechanisms to integrate with any backend database user authentication mechanism.

YES - Sitecore provides the ability to integrate with backend authentication mechanisms through the LDAP module, as well as, Sitecore use of virtual roles in the security database.

The LDAP module is an add-on sold by Sitecore. Depending on the external membership database, some development effort will need to occur.

2.12.29 CMS supports connection over HTTPS. Yes - This is completely supported.


2.12.30 CMS allows the reading of LDAP attributes such as email address.

YES - This is achieved through the Sitecore LDAP module.


- 64 -

2.12.31 Describe patch management and release schedule.

Sitecore release all patches through the Sitecore Developer Network. Certified Developers, as well as Customers are notified of Sitecore patches via announcements and have the ability to download the patches as long as they are subscribing to the maintenance program of Sitecore. The Sitecore release schedule is taken very seriously. Sitecore goes through a very rigor beta testing program internally first. Second releases the application of closed beta testing to selected partners, and third provides it to internal tech and sales individuals for final testing. The release management of a new product from step 1 to completion usually takes 6 months.

A roadmap can be provided if necessary.

2.13 Deployment of the CMS

Product Support and Installation

2.13.1 Indicate the location of your service offices.

Sitecore supports service offerings out of locations in San Rafael, CA, the Ukraine, Copenhagen Denmark and London England.

2.13.2 Describe hardware and software support options.

Sitecore supports its CMS software according to the attached Customer Care documentation. Support of the CMS software is provided for the first year at no additional cost.

- 65 -

2.13.3 Describe your problem escalation policies.

Sitecore supports a tiered escalation process that starts with issue submittal and tracking number designation and then progresses based on a severity ranking association. Software support challenges creating production outages are considered most sever and receive the full attention of the engineering, q/a and support staff; globally.

2.13.4 Can develop its own separate systems that could access, but not modify, data contained in your system (i.e., extracts for interface engine).

Sitecore fully documents API and supports a concept of "triggers" on all CMS functions should applications need to be integrated or synchronized. Sitecore also provides a technology identified as the Data Provider to ease the sharing of content between applications and data sources.

2.13.5 Describe how application documentation will be updated (i.e., memo, revised manuals).

Sitecore maintains a full documentation team that synchronizes the updating and management of documentation, training materials and Developer Network content with each version release.

2.13.6 Describe the last three software releases/upgrades. Include date of release and a summary of its major features.

The last 3 releases of the Sitecore application were labeled Sitecore CMS 5.3, Sitecore CMS 5.2 and Sitecore CMS 5.1.1, over the course of these 3 releases Sitecore continuously improved its application in the areas of performance, scalability and usability. 1 of the major "changes" was the adoption of the Office 2007 UI design for editing and management UI's. Additionally improvements in the form of SEO analytics as well as caching and performing improvements were made. For a full and detailed description of all product versions and improvements Sitecore makes its Developers Network available.

2.13.7 What is your pricing structure? Sitecore's pricing structure is built on 2 primary elements, per server cost for each environment it is installed on and by concurrent user count. Sitecore has no limitation on named/permission based users.

2.13.8 Are there consulting fees? Consulting fees are not required for Sitecore. Training and service offerings are provided and have set pricing associated with them.

2.13.9 Are upgrades automatic with product support/maintenance?

Yes, access to software upgrades, new features and support and maintenance are all available with a current maintenance program.

2.13.10 Are major releases covered or just maintenance upgrades?

All major and minor releases are covered by the maintenance program.

- 66 -

2.13.11 In which timeframe should we expect to recoup our investment into your system?

Sitecore customers typically recoup investment within the first year of ownership. With the reduction in IT/development time as well as the ability of marketing communication to own many elements they formerly outsourced the gains are typically evident quickly.

2.13.12 What is your current installation load? 1400 customers worldwide.

2.13.13 Are your resources able to handle an implementation in the next 3 months?

Yes, Sitecore's effective use of its Partner channel allows it the freedom to manage many more CMS implementations than CMS applications that rely solely on internal deployment teams.

2.13.14 Have any customers canceled a contract before, during, or after an installation? If yes, why?

This has happened once in North America. The client cancelled the contract and sought a refund of the CMS solution due to being purchased by another company and all funding of the project was terminated. This happened within 2 weeks of project kick off.

Deployment Details

2.13.15 Provide a preliminary implementation work plan and proposed phasing. Include your approach to data migration.

See attached Appendix: ISITE Appendix A

2.13.16 Specify the client and vendor resources needed during system implementation.

Client resources: internal project owner to interface with implementation partner; to varying degrees: internal dev staff, database admins, server admins, department/site subject matter experts. Vendor resources vary, but see 2.13.19

2.13.17 Describe the proposed approach to acceptance testing.

ISITE Design has a complete and rigorous process for QA and acceptance testing. We have a dedicated QA department responsible for reviewing code prior to client delivery. We would be glad to detail our methods based on the specific project that ISITE would be engaged to perform.

- 67 -

2.13.18 Describe the extent of services provided during the implementation process.

Implementation services as described by ISITE Design: As a full-service interactive agency with deep Sitecore expertise, our implementation skill is complemented by a strategic layer (if desired) to help scope and define technical, functional and usability requirements. ISITE's approach considers CMS implementation in the larger context of what are today's goals, and tomorrow's, with the organizations web plans. If necessary, this also includes information architecture, wireframes, sitemapping, as well as creative modifications as required by the client. Beyond implementation, we also look at the equally critical issues of CMS governance (including the client's desires for how sites are managed -- centrally? distributed? how are new sites provisioned and by whom?) and architect the CMS environment according to these requirements.

2.13.19 What personnel are typically required to implement the product?

Implementation in most cases, regardless of CMS, takes a team of several skill-sets, which usually means a number of skilled people. Looking specifically at the technical implementation: a project manager to plan and manage steps and resources; front-end developer for CSS, XHTML and templates; a .NET web developer for core CMS implementation, customization; quality assurance engineer to test the site and identify areas that need fixing. Beyond that, many such projects also include (to some degree) a web strategist, a business strategist, an SEO specialist; an analytics specialist; and a database administrator.

2.13.20 What technical skills are required? Sitecore developers should have knowledge of .NET programming.

2.13.21 How many people are typically required to support the CMS once in place?

This is highly variable. Certainly, at a minimum, if the CMS is to be supported even minimally by internal staff resources, a developer with .NET web programming experience who can train on Sitecore CMS to carry out the daily maintenance tasks that inevitably appear is essential. Beyond the technical, a CMS administrator who can take a global (cross-campus) view of the Web at Tufts and administer at a high level the planning and hands-on provisioning of user roles and rights, workflows, new sites, basic functionality, etc., is advisable. And, as with any CMS, one or more content "owners" whose role is to be subject matter experts or know where to source the subject matter within Tufts. On this last role, it is likely that it would follow the same staffing structure/requirements as is currently in place at Tufts, at least where existing legacy sites are concerned.

2.13.22 Who provides these resources - vendor, customer, consultant, SI?

The resources detailed about can be provided by the customer or can be provided by ISITE Designs (development resource).

- 68 -

2.13.23 What is the average time for implementation?

This is highly variable depending on level of customization, 3rd party integrations, functional and technical req's etc. It is common for the development phase for such a project to last 14-24 weeks. This, of course, can be better targeted with complete requirements and specifications.

2.13.24 Describe the on-site, dedicated personnel that you would provide during the initial implementation of your system.

Scenario of ISITE Design providing the initial implementation service: the initiative would be Project Managed and Account Managed from our Cambridge, MA, office. The project would be a mix of onsite meetings during project initiation phase (discovery, knowledge transfer, requirements gathering, etc.) with as-needed onsite meetings and coordination. If required ISITE would make personnel available on-site at Tufts during essential/required portions of the project. That said, ISITE has in place rigorous project management tools and processes for frictionless, off-site development. CMS integration projects are handled by ISITE Design staff in our Portland, OR, development center.

2.13.25 What are the associated costs of implementation?

This is highly variable. ISITE Design would be pleased to provide a cost estimate based on a specified scope.

2.13.26 Can the product be deployed using a modular approach?

Yes, Sitecore CMS can be deployed in this way. The core product is supported by a large number of additional, optional functional modules created by Sitecore.

2.13.27 What levels of training are required? Sitecore offers training in a 3 tier format, User Training, Admin Training, and Developer Training. The decision to go through any of the Sitecore trainings would be completely up to what is anticipated by each customer. If development tasks will be conducted by the school, then it is suggested to go through developer training. It is suggested to go through admin and user training just prior to launch of the new site.

2.13.28 How is this provided (e.g., CBT, classroom, on-site, Web-based)?

Sitecore provides either onsite training, web training, or has fully equipped training facilities in San Rafael, CA.

2.13.29 How is ongoing support provided? Sitecore provides completely technical support to all customers who have continued their support agreement with Sitecore. Support is conducted through the Sitecore Developer Portal, Support Portal, Online Help Desk, Telephone support during office hours, etc. Ongoing support can also be provided in the form of a maintenance contract from ISITE Design. The terms of the contract (hours per month; nature of the support requirements; service levels, etc.) are customized to the specific requirements of the client.

- 69 -

2.13.30 Is the product dependent on other products from the company's portfolio or on any third-party products?

There is no actual "dependence" on 3rd party applications or products. Sitecore does utilize a 3rd party wysiwyg editor that can be replaced. Sitecore also ships with the Lucene search tool by default, but has been architected to allow this to be replaced with additional search applications should a client project dictate this.

2.13.31 Please list any required products and relevant vendors. On which (operating system) platforms does the product run?

Sitecore does require IIS web servers to run as well as integration with a database solution. Please see the attached Hardware/Software requirements document attached.

2.13.32 Will business procedures need to change to support this product, if so why, and to what benefit?

Sitecore believes firmly that business procedures should not be altered to meet the needs of a CMS solution, but that CMS solutions should be deployed to support business procedures.

System Performance

2.13.33 Describe the anticipated downtime for monthly, weekly and daily processing.

Sitecore as a web based CMS solution does not require "downtime" but as in all applications routine maintenance should be followed. For clients, there are multiple options for performing this maintenance without compromising up-time. In the reviews of enterprise class CMS solutions there should be no expectation for "downtime".

2.13.34 Discuss data storage and data access issues and state the recommended disk space for data storage.

Sitecore stores all web based content within approved databases. It is recommended that at least 2 gigabytes be available for disk storage, with a minimum of 500 megabytes to run the application and basic processes.

2.13.35 Describe any performance monitoring inherent in the system.

Sitecore ships with multiple performance monitoring capabilities. Within the Developer Center, the "debug" tool allows real time evaluation of all code running within each aspx template allowing extremely granular review and control. Sitecore also allows action to be taken on poorly performing code, with the ability to fine tune caching to maximize live site performance.

2.13.36 Describe in detail how the recovery procedure works.

Sitecore's CMS solution supports multiple disaster recovery scenarios and configurations. Dependent on architecture Sitecore can provide extremely detailed responses to this question based on your actual environments.

- 70 -

2.13.37 Describe data file backup procedures and provisions, including features of the system that minimizes the impact of scheduled and unscheduled downtime.

Sitecore inherently decouples the CMS production environments from the live web presentation environments. In addition, many customers load balance presentation environments allowing for the load balancer to divert traffic to the "up" production environment when scheduled and non-scheduled maintenance occurs. In addition, when the primary CMS instance is being upgraded or having routine maintenance performed the web presentation environments are not affected in any way.

2.14 Training & Support

2.14.1 Discuss training requirements to utilize the product for: • Non-technical (content editors & approvers) • Semi-technical to technical (developers & administrators)

Attached please find the Training document which details all Sitecore training Services.

2.14.2 Discuss training requirements to utilize the product for: • Non-technical (content editors & approvers) • Semi-technical to technical (developers & administrators)

Attached please find the Training document which details all Sitecore training Services.

2.14.3 Describe how training courses are conducted (e.g., a series of presentations by vendor to end users or a “train the trainers” approach, etc.).

Attached please find the Training Agendas which details all Sitecore training Services.

2.14.4 Provide detailed syllabus for training courses

Attached please find the Training Agendas which details all Sitecore training Services.

2.14.5 Is there any continuing education or training provided to support new releases and/or upgrades?

YES - Sitecore has regularly scheduled training classes that any customer can sign up for continuing education on the Sitecore platform.

- 71 -

2.14.6 Discuss if the following items are included in the annual support maintenance fee. • All hot fixes and service packs • All version upgrades • Administrative technical support hotline • E-mail/online support • Installation support • Online access to documentation • Online access to software

Sitecore provides all functions listed below with the exception of the telephone hotline. Sitecore provides telephone support via 8 AM to 8 PM EST. Sitecore also suggest the installation of the product be conducted by trained Sitecore developers.

2.14.7 Provide average support response time (please detail by category – email, phone)

Sitecore provides a guaranteed 8 office hour response time for all support issues.

2.14.8 What standard options are there for support (e.g., is there a call center or email, etc.)

Sitecore provides both a call center and an online support portal for the creation of support tickets for Sitecore's support offices to act on.

2.14.9 Discuss any online training and documentation materials

Sitecore provides Admin and User training via the web. Please see attached training descriptions and agendas for each. All Sitecore documentation is placed on the web based Developer Portal. Access to the portal can be provided to Tufts for review of any and all Sitecore documentation.

2.14.10 Provide details on any online user groups, forums, or conventions

Sitecore has online forums in the Developer Portal for certified developers to discuss Sitecore. Sitecore also hosts a Yahoo forum for the discussion of Sitecore Development tasks. Sitecore will plan on having its first user group convention in 2009.

- 72 -

3 Special Cases

3.1 Master Calendar

3.1.1 Challenge

To gather calendar data from a large number of users and sources, and to display that data in a

customizable, attractive format that supports web standards.

3.1.2 Proposed Solution

To solve the challenge of calendar requirements, Sitecore provides the Sitecore Calendar

Module. The Sitecore Calendar module is an add-on feature supported by Sitecore for the

building and management of content intensive web based calendars.

Sitecore provides the same very intuitive editing interfaces to add new events and to add new

data to the Calendar events being displayed by the module. The real strength of the Calendar

module is the ability to store and create content in the same fashion as standard content items, as

tagged XML fields stored in the database.

Because customers develop the same content items for the events that they create for all other

content, the same rules apply. Customers can create tagging fields or keyword description field

on events that can be used for the rendering logic of events. For example, those events tagged as

Board of Directors will only render to users authenticated when logged into the site as part of the

Board of Directors role in the extranet security domain.

The tags can also be used for filtering calendar events. Filter options can be provided on the web

page to only show those events that are tagged ―PHPD program.‖ Because Sitecore provides a

dynamic web page generation engine and completely separates content from presentation it is

quite easily to implement this type of logic on your calendar.

Lastly, at the end of the day, the event content is stored in the same manner in which all other

content is stored. This provides customers with the ability to render the data not only as events

in a calendar but also content on separates pages. For example, TUSM can have the event of the

day rendered on the homepage based on a tag on the event content item. That event can be

rendered on the global calendar, as well as, in a list of the month‘s events.

Please feel free to check out a The Sitecore Calendar in action: http://www.wolftrap.org/

http://www.wolftrap.org/

- 73 -

3.2 Sackler and TUSM News

3.2.1 Challenge

Create automated news feeds from three main sources and allow editors to filter, select and

display select news effectively throughout the Sackler and TUSM websites. Also, build and

publish RSS feeds (and other standard web syndication formats) containing TUSM and Sackler

news.


The solution to this problem can be addressed in several different architected solutions and the

actual solution will be addressed at the time of the strategy and requirements gathering phase

lead by ISITE Designs. Below are two methods / features provided by Sitecore:

1. The use of the Sitecore RSS Module. Sitecore provides the ability for CMS users to

create RSS Feeds for specific sections / subsections of the site for visitors to sign up for.

The RSS Module will completely support TUSM need for the syndication of content via

RSS and the ability for users to sign up for RSS feeds to be delivered from the Sitecore

managed sites.

2. Sitecore can be implemented to create content items on the fly from incoming RSS feed

from external sites, such as Google Alerts. A content data structure will need to be

created for the RSS feed content to be received and added to. Upon receiving a new RSS

feed from a pre set subscribed RSS, Sitecore will create content items on the fly and

provide the ability to have content reviewers review the items via the Sitecore workflow

processes and edit, reject or publish the items to the web. Sitecore provides the ability for

the RSS feed to be the content author and the editor will only need to review and edit the

content feed from the other sites, and lastly publish it or reject it.

An example of a Sitecore site that receives more than half of its content through RSS feeds:

http://www.chcf.org/

3.3 Sackler Faculty Research Pages

3.3.1 Challenge

Support updated faculty and research pages that rely heavily on internal and external search

functionality.

http://www.chcf.org/

- 74 -


A key to accomplishing the types of things described in this case revolve around the use of

formal taxonomy, a set of generally accepted keywords that describe or categorize the content,

making it searchable easily based on common understanding of terms and keyword usage at the

time of content creation. (Example: tag Tufts-created content and information by topic, faculty

name, keywords in bios, research keywords, and related photos by keyword, and more. For

externally sourced content (PUBMED and CRISP), the use of these services‘ content feeds (e.g.

XML data) via an automated subscription to feed the Tufts‘ sites based on specific criteria can

accomplish the goal and extend the reach of relevant research information and data from leading

professors and publications into the relevant Tufts websites, right down to the page of an

individual researcher or professor.

We would like the CMS to pull in keyword-based PubMed database searches in the form

of abstracts for an internal user to select and tag appropriately.

o Leverage the XML output of PubMed and similar sites according to stipulated

keywords wanted by Tufts, and leverage the CMS‘s ability to consume XML;

automate the pull of data and deposit it into a CMS folder that can be triaged and

approved by content managers before going live.

We would need to build a searchable database of faculty bios (and possible grad student

bios) with spaces for CVs, descriptions of research, photos and publications.

o A common and effective approach to this is creating Personal URLs (PURLs),

one page for each individual, whether professor or student. This would be a

structured page with extensive ability to add/edit bios, CVs, research info, photos

and articles, within limits: The structure of the page would be created and

formalized by website administrators without the ability for individuals (staff,

students) to alter the overall page layout. This affords consistency and

searchability, as well as presents a consistent user experience for people

traversing the website. Content for each PURL could be added by the individual

whose bio page it is (with CMS access, mild training and oversight) or via a

content administrator/editor (who would be gatekeeper to the PURL section of the

site.) This is a choice within the purview of Tufts web administrators.

These pages should also pull in any research-related news and events, both internal and

external to Tufts, such as news of a Nobel Prize winner in specific scientific field.

o This would be accomplished through the use of an XML news feed (source: TBD)

in an automated way. To address this in a manual fashion would create an

extensive workload just to manage the inbound articles.

3.4 Advanced Search and Taxonomy

3.4.1 Challenge

- 75 -

Build an integrated search engine or search functionality that supports internal taxonomy to

maximize results and makes it easier for internal and external website users to find what they‘re

looking for.


Sitecore has the ability to add in additional fields into a Sitecore item. In this instance, items are

created with a built in field for keyword metadata. It is very easy for a user who is creating

content to put in whatever metadata or keywords into this field(s) at the time of the item creation.

This allows for specialty keywords to be placed on the page that relate this material to a certain

keyword that may not be related to the content in a meaningful way. These fields can also be

added in through a number of different ways with either freehand text or even as existing data

from other parts of the site (referenced fields). This can be predetermined at the time of

architecture or added in at a later time. At such time that the page is then rendered out, this

metadata can then be loaded into the page to be indexed by the Google search appliance.

Having it as a part of the item architecture also makes it feasible to search for the item internally.

Customized search views could then also to be configured by parsing the Google results and

sorting through the meta data associated with the specific item.

Internal searching can be handled entirely within the Sitecore user interface. From inside of the

Sitecore interface, there is a search box. Any search term can be entered into this and it returns a

listing for all the content items containing that term. Results are then shown in such a way that it

shows a few fields (i.e. Title and Description) and then clicking the result will take the user into a

content editor for that specific item.

3.5 Social Networking

3.5.1 Challenge

Offer original tools or easily integrate external tools for social collaboration, including blogs,

wikis, forums and online chat.


The Sitecore CMS natively supports its own Sitecore modules for blogs and forums, and

supports the integration with third party products for blogs, forums, wikis, if a third-party/best-

of-breed solution is preferred by users. The good news is the Sitecore CMS will easily support

external products.

The social networking aspects can go a number of different ways. There are custom, third-party

social platforms that provide the ―cool‖ yet highly capable social networking tools and widgets.

The Sitecore CMS also supports a number of these natively; a CMS partner/integrator would be

able to define what specific functionality and capability would need to be built into the site;

- 76 -

which of those are Sitecore-specific; and which third party (if any) tools are required to support a

private social network.

How these tools are applied is a strategic discussion for Tufts staff and administrators. But given

the evolution of the web as a platform for social communication, there are vital and significant

ways that social networking could be established and fostered on one or more Tufts websites.

Specific to the challenge of Admissions using social collaboration tools to attract and engage

potential students, here are two visions from ISITE Design web strategists for using social tools

in the Admissions environment:

1. Social platform to encourage students to apply to Tufts: Every university-bound

ungergrad/grad/postgrad goes through their own process to determine whether a given

school would be a good fit for them. Their decision-making can be highly formal and

structured, or it can be informal – assessing whether the school passes the ―gut-check‖

test according to the metrics that matter most to them. That gut-check often happens on

the school‘s website and it can be the place where a relationship with a prospect can end

as quickly as it begins.

Decisions to short-list a school and to apply come down to perceptions and real-world

experiences and evidence that indicate how well a school will serve them: academic

tracks and academic rigor, social opportunities, campus life, religious life, sports & clubs,

overall campus environment, and other decision factors.

To facilitate this process and to ensure that students have a positive ―gut check‖ a social

microsite can facilitate this process and enable prospects to see for themselves how Tufts

can meet their requirements. Such a site would employ common social media formats

such as web video, audio, images and text (supplied/provided by officials campus

sources; user-generated content at your discretion) as well as interaction points using

blogs, forums, and ―groups‖ defined by common interests or objectives (―I am interested

in applying to Tufts undergrad.‖

This would be an offshoot of the main Admissions area on the website(s) and exist to

provide interaction among potential and current students and faculty/professors able and

willing to articulate their vision/perceptions for the University.

2. Social networking site to encourage “accepted students” to attend Tufts: This can be

a key differentiator for any University that does it right. The concept is powered by CMS

and is elemental to a strategic Admissions program. The execution involves creating a

microsite open to a relatively small audience: Students who have been accepted to Tufts

for Fall enrollment, some of whom are still on the fence about whether or not to attend.

With this ‗Tufts Freshmen‘ social website, each student who receives an acceptance letter

also receives a personal login to the private website. Once there, each student can create a

profile which contains a mix of personal, academic, social, music and other topics which

they can identify as relevant to them. The site becomes a gathering place for incoming

- 77 -

students, who can find one another, converse and meet one another, and generally build

via the website a set of friends and peers with whom they are already familiar the day

they set foot on campus. This is also where roommates can be matched based on

personality or special interest, and Admissions counselors can provide ongoing

commentary/feedback about why students should attend Tufts.

3.6 Password Protected or Semi-Private Areas

3.6.1 Challenge

Build a semi-private area within the public website for specific audiences, such as members of

the media, accepted students, alumni and others.

3.6.2 Proposed Solution:

Sitecore provides password protected areas of the site, password protected pages, or entire

password protected sites all via the Sitecore Extranet Security domain. The Extranet Security

Domain is shipped with the Sitecore product and provides Sitecore customers with the ability to

have member only password protected areas by using extranet security roles and applying named

visitors to those roles.

Site admins simply log into the CMS and navigate to the security editor interface. Once in the

Security Editor, admins need to switch to the Extranet Security Domain and find the role in the

extranet membership database they would like to grant or restrict access to. Upon locating the

role, the admin just simply denies Read access to those pages or sections that he / she wants to

restrict access to and the process is complete,. When a visitor logs into the site, he / she is placed

as a member of the role in the Extranet Database that admins have delineated and their access to

specific pages will be rendered based on the security permissions set.

- 78 -

4 Cost Analysis

4.1 Software Licensing

Tufts Medical School is being quoted for the Sitecore Professional Edition in 1 primary CMS

installation on one content authoring server with unlimited CPUs for an unlimited number of

domains. This license would allow 5 concurrent editors on that server and permit unlimited

content item management.

Based on the current and expected web traffic, Sitecore is recommending that this license allow

the installation on one additional server which can be used as production servers for the single

purpose of content delivery.

Qty Product Name

Higher Ed Retail

Discount Price Total

1 Sitecore CMS Professional Edition 10% 29,700.00 26,730.00

1 Extra Servers (Content Delivery) 10% 7,560.00 6,804.00

Total US$ 33,534.00

4.2 Sitecore Implementation

As a longtime Sitecore integrator, ISITE Design is proficient at estimating the development costs

and timeline for specific, scoped implementations. In the case of Tufts, we would be glad to

focus on a specific scope of work around the implementation of the Sitecore CMS and provide a

cost and time estimate for the project. That said, we would be pleased to have a phone

conversation with someone at Tufts to discuss our overall approach and provide you with a

scoped example with related price and time estimates

4.3 Sitecore Training

Sitecore training courses are managed and delivered by Sitecore. All of the Sitecore course

offerings occur on a regular and scheduled basis at the Sitecore training facility in San Rafael,

California with published dates available on the Sitecore web site. On-site training can be

arranged and is offered for each of the below course offerings with a requested 3 week

notification period. Exceptions may be accommodated based on trainer availability.

4.3.1 Sitecore Certified Level 1 Developer

Level 1 is Sitecore‘s primary developer training course for those web developers with no

previous experience with the Sitecore CMS solution. This two day course will fully equip the

attendee with the knowledge and skills necessary to build a Sitecore managed web property upon

passing this level‘s evaluation. For a full description of this course and understanding of required

skill sets please see –

- 79 -

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Developer%20level%20one

.aspx

Cost - $1,200.00 per attendee or $4,800.00 plus travel expenses for on-site

4.3.2 Sitecore Certified Level 2 Developer

This training is offered to Sitecore Certified Developers who have a solid understanding of the

Sitecore CMS solution in place. This course offering delves into leveraging the full Sitecore API

at a deeper level and more advanced web development challenges. For more information -

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Developer%20level%20tw

o.aspx

Cost - $810.00 per attendee or $2,400.00 plus travel for on-site

4.3.3 Sitecore Certified Administrator

This one day administrator focused training is aimed at providing the team the level of

understanding and confidence to manage security, workflow and advanced editorial features

efficiently and productively with the Sitecore CMS solution. For more information -

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Administrator.aspx\


4.3.4 Sitecore Certified User

This course is designed to introduce site end users to Sitecore‘s CMS solution. This training

describes how to use the various web based user interfaces an author and publish content. This

training is often delivered by the solution architect who builds the end solution, but Sitecore can

provide this level of training directly. For more information -

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/User.aspx


4.4 Maintenance / Support Costs

Provided at no cost to Tufts Medical School is the required first year Sitecore Annual Upgrade

and Support cost of $6,706.80. This Annual Upgrade and Support cost at the stable price of

$6,706.80 will be charged annually for the next 5 years, or until Tufts Medical School has

decided to discontinue annual upgrade and support service.

4.5 Optional Sitecore Costs

In addition to the recommended licensing detailed above, which would be required by Tufts

Medical School to run their planned web infrastructure, Sitecore offers several other optional

modules to add increased functionality to the Sitecore web CMS.

Forms Pro – Provides the ability for the building and management of web based forms

($2,430)

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Developer%20level%20one.aspx

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Developer%20level%20one.aspx

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Developer%20level%20two.aspx

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Developer%20level%20two.aspx

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/Administrator.aspx/

http://www.sitecore.com/Training/Sitecore%20Training%20Courses/User.aspx

- 80 -

StatsCenter Pro – Provides the ability to view web statistics / analytics via the CMS

interface ($2,970)

SEO Module – Provides users to evaluate their content with regards to preset search

engine criteria. Provides users with the ability to optimize their content for better search

engine rankings ($1,485)

Calendar Module – Provides the ability to render and manage events in a calendar

interface on the site as well has rendered the content in different locations and

presentation layers ($2,160)

Newsletter Module – Provides the ability to manage subscribers for specific separate

mailing list roles with in all of your newsletters. Also provides the ability to create and

manage specific newsletter messages, whether they be URL, HTML, or Text driven

($2,160)

MS SharePoint Connector – Provides completely / seamless integration with MS

SharePoint and Sitecore ($4,320)

- 81 -

Appendix – ISITE Design’s CMS Development Approach

ISITE Design, a full-service interactive agency and experienced Sitecore CMS integrator,

follows a standard development process that begins with an initial alpha delivery which is made

available for review by our clients. The alpha release will have the initial framework of the new

site populated with a majority of the content. Feedback is captured via our online issue tracking

system. This feedback is combined with known issues to guide the effort required for a beta

release. Once a beta level of quality and functionality has been reached, we will initiate

deployment and launch activities as described below.

Objectives

Develop the templates according to the Information Architecture

Configure templates and CSS to support the site map and creative design

Populate the site with starter content

Integrate and/or develop the features and functionality specified in documentation

Train Tufts staff on the management of the new site including content entry and page creation

Key Activities

Template Creation

Meta and Analytics Tagging

Graphics & CSS Production

Integration & Feature Development

Content Migration & Import

Quality Assurance

Training

Launch of the new website(s)

Delivery of all project documentation and deliverables

- 82 -

Appendix II – ISITE Design Case Study

Oregon Health & Science University

OHSU is Oregon‘s only health and research University and is Portland‘s largest single employer

– an absolute force in the state of Oregon from the perspective of higher education, medical and

scientific research, and complete healthcare services.

In 2001, ISITE Design was chosen as a preferred OHSU vendor and since then we‘ve supported

a wide variety and large number of web strategy, design, web development and CMS-specific

integration projects. In that time, ISITE has developed more than 30 CMS-driven OHSU

websites for departments, research labs, the medical school, the hospital and healthcare system,

and more. ISITE‘s role is far more than a web development agency. In fact, ISITE has been and

continues to be OHSU‘s strategic web partner, advising the organization on nearly all things

related to their online strategy, from architecture to website governance to CMS integration.

ISITE is currently engaged in a multi-year, cross-organization project to unify OHSU‘s many,

far flung websites. The goal is to create a unified technical architecture for managing a vast,

dispersed web environment and presenting their brand, and the web user experience, in the best

possible way. The current www.OHSU.edu home page is a first step in this direction – a user-

centered design that helps visitors determine more easily the online path they need. The result of

ISITE‘s efforts is an engaging interface and site architecture which will allow users to easily

access accurate and comprehensive information – regardless of the purpose of their site visit.

http://www.ohsu.edu/

sitecore - confluence - tufts university

Documents