Request for Proposal: Web Content Management System
Upcoming SlideShare
Loading in...5
×
 

Request for Proposal: Web Content Management System

on

  • 6,136 views

 

Statistics

Views

Total Views
6,136
Views on SlideShare
6,136
Embed Views
0

Actions

Likes
0
Downloads
141
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Request for Proposal: Web Content Management System Request for Proposal: Web Content Management System Document Transcript

  • Request for Proposal: Web Content Management System Project Timeline: November 14, 2008 – Proposal Due Date, 3 print copies and an electronic version in Microsoft Word November 17, 2008 -- H-SC begins review November 21, 2008 -- Invitations to campus extended December 11, 2008 -- Presentations to Web Oversight Committee January 2, 2009 -- Decision made by Web Oversight Committee, Budget Request made for 2009-10 year July 1, 2009 -- Purchase of CMS Summer 2009 -- Installation, training Spring/Summer 2010 -- Launch new website Send all Proposals to: Hampden-Sydney College Web Oversight Committee ATT: Cheryle Dixon Box 37, Hampden-Sydney, VA 23943 (434) 223-6856 cdixon@hsc.edu Web Oversight Committee Members: • Dr. Paul Baker, Vice-President for College Relations and Administration, Chairman • Mladen Cvijanovic, Director of Intercultural Affairs and New Student Orientation • Cheryle Dixon, Webmaster • Richard Epperson, Director of Development • Anita Garland, Dean of Admissions • Chandra Gigliotti-Guridi, Instructional Technologist & Assistant Director of Library • Richard McClintock, Director of Publications • Dr. Dan Mossler, Professor of Psychology, Faculty Representative • Bob Murray, Director of Computing • Tommy Shomo, Director of Public Relations • Matt Green, Sports Information Director
  • Hampden-Sydney College About Hampden-Sydney College: • General Description of College o Founded: 1775 (10th oldest college in the United States) o Control: Private (affiliated with the Presbyterian Church) o Description: Four-year, independent liberal arts college for men o Calendar Plan: Semester o Standards: Selective o Accredited by: Commission on Colleges of the Southern Association of Colleges and Schools • Location and Campus o 1340-acre wooded campus 60 miles southwest of Richmond, Virginia. o Thirty-two major buildings in the Federal style. o Much of the campus has been designated a National Historic Preservation Zone. • Enrollment o Total: 1120 Freshmen: 315 o Student/Faculty Ratio: 11:1 Existing College Web: • The College’s web server currently runs on a Dell PowerEdge 6800 with 8Gb memory and 8 hard drives with 1,168Gb space with Microsoft Windows 2003 Server and IIS 6. • Client computers use Microsoft Windows XP, Vista, or Macintosh OSX with a variety of web browsers including Internet Explorer 6, 7, 8; Firefox 2, 3; and Safari. • Data is currently stored in static html files, MySQL and PostgreSQL databases, XML, and plain text files • Daily backups are done on all web files and databases • PHP (currently version 5.0.3) is the predominant programming language used for interactive content although a few PERL scripts exist. Student Administrative data is pulled to the web from a Jenazabar database using ODBC and PHP. The Blackboard Learning System is used by the Library and Academic departments but does not interface with the College’s website. • Traffic on the site from January to October 9, 2008 was 3,903,418 pages served averaging 430,000 pages per month or 14,500 pages per day (AWStats, 2008). • The website has over 50,000 pages stored. Regular archiving is not done. • About 35 content editors across campus currently use the College supplied FrontPage to edit files directly on the web server. They use template files with the College’s banner and menu navigation system built in. Other than the banner, navigation menu and College colors, they are free to edit page content as they wish. • Content editors also upload images directly to the web server and insert them into web pages. Often these images are not resized before uploading to the server. Each editor has permissions (NTFS and IIS basic authentication) set for access to only the directory in which they edit content. They may read other directory content but have no permissions to edit. • The webmaster uses Dreamweaver, Photoshop, Sothink DHTML Menu 8, PHP, and MySQL to build the template files, write new applications, and maintain the javascript menus for the site. The College Events calendar is also done in PERL and PostgreSQL. News, Athletics, Alumni Profiles, and Alumni Class Notes are all maintained in MySQL databases. 2 RFP: Web Content Management System
  • Hampden-Sydney College Identified Problems with Current Web: • Out-dated template design done in tables optimized for 800x600 screen resolution • Out-dated content with no tools to continually expire or archive content with link checking • Repurposing content is very time-consuming when done manually • Out-dated FrontPage editor provides no CSS support, stripping of Microsoft Office formatting code • Image editing may only be done through FrontPage and files may remain large • Very difficult to measure marketing initiatives Project Goals and Objectives: • Redesign H-SC website o Create standards compliant website for viewing on various devices including web browsers and PDA/Cell phones o Create a liquid layout to fit viewing window o Automate a print version of all pages o Include more new media content across website • Better manage content on website o Begin and expire content by date o Archive selected content o Check for out-dated links on expired and archived content o Automate notification of expired content o Repurpose content across site Use approval process on large publications like Academic Catalogue and publish print version to Adobe InDesign o Automate menu system o Automate site map • Replace FrontPage editor with browser-based CMS that will create standards compliant output • Improve image access and editing o Provide image repository with access by content editors o Provide image resizing for thumbnails and automatic sizing for showing on web page along with mass upload of images • Improve measurability of marketing initiatives o Gather statistics on content tied to marketing initiatives with start/expire dates and products like Google Analytics 3 RFP: Web Content Management System
  • Hampden-Sydney College Terms and Conditions: • Each respondent should answer the Vendor Questionnaire and complete the Functionality Checklist. • The respondent should offer contractual terms for 1-year, 3-year, and 5-year terms. The length of time included in the initial contractual agreement will be negotiated with the finalist. • The respondent is responsible for all associated costs incurred in responding to this Request for Proposal, including on-campus presentations, document support, and implementation and on-campus training. • The College reserves the right to enter into an agreement with the company that it feels is in the best interest of the College. The College also reserves the right to request clarification and/or further information from one or more respondents after closing without becoming obligated to offer the same opportunity to all respondents. • A respondent requiring clarification or interpretation of this RFP must make a written request. All questions and responses will be shared with all bidding vendors to ensure fairness. Questions should be sent to: Hampden-Sydney College Web Oversight Committee ATT: Cheryle Dixon Box 37, Hampden-Sydney, VA 23943 (434) 223-6856 cdixon@hsc.edu • Prices quoted are important to selecting a CMS. In this process, the quoted price will be submitted in the spring semester budget process. Actual purchase will not occur until July 1, 2009. Indicate how long quoted price is good for and project to July 1, 2009. • Proposals will be evaluated on the following criteria (not necessarily in order) o Experience o Pricing aspects including purchase price, maintenance costs and other long-term expenses associated with the product o Functional capability o Timeliness of project implementation o Company resources and project staffing assignments o Support and product implementation o Vendor evaluation including past performance, long-term stability and customer references o Closed system (no partner, advertiser, or business associate of vendor will be allowed to access our web site, data or registered user information for any reason not approved by the Web Oversight Committee Chair. o Visual appeal of product • Three (3) print copies of your response to this RFP must be received by the College by 5 p.m. on November 14, 2008. An e-mail attachment version in Microsoft Word is also requested for distribution to the Committee members. • Proposal documents must be completed in accordance with the requirements of the Request for Proposal specifications and no amendment or change to proposals will be accepted after the closing date and time. • Vendors may be required to provide proof of financial stability. • All contractual instruments, to be officially recognized, must be agreed upon and signed by the Vice President for Business and Finance for Hampden-Sydney College. 4 RFP: Web Content Management System
  • Hampden-Sydney College Vendor Questionnaire Technology Architecture System Requirements 1. Describe your technology architecture 2. What server Operating Systems are supported? 3. What client Operating Systems are supported? 4. Is the client browser-based? 5. What Databases are supported? 6. What Web servers are supported? 7. Does your technology architecture include a RunTime application server for processing real time queries and content transformations? 8. Does your technology architecture include a replication service for replicating content to multiple servers? 9. What are the recommended hardware requirements for running your CMS software? 10. What programming languages can be used with your CMS? 11. How is your CMS licensed, by server, by user? Technology Infrastructure 12. Describe the base data model for your product. 13. Outline the Open Standards (e.g. LDAP, XML, XSLT, etc) that are supported by your product. Describe how your product uses them. 14. Describe the future directions for your product? For example, if there are plans for new features, integration with other products or modules, a shift in technologies and the like, please describe them. 15. Identify proprietary and non-standard components of your product. Scalability Describe the performance characteristics of your product. 16. Describe the scalability of your product. What limits, if any, are there on the numbers of objects supported? On the number of uses supported? What is the limiting factor in scaling your product to increasing numbers of objects and users? 17. Does your product support load balanced servers and clustered servers? Technology Upgrades 1. When is the next scheduled major release of your product? What is your maintenance release schedule? 2. Describe your release notification and delivery process. 3. How are customer feature requests incorporated into your product development process? 5 RFP: Web Content Management System
  • Hampden-Sydney College Content Management The Hampden-Sydney College Web initiatives require a robust content management environment that is easily accessible to front-line staff and other content contributors with no knowledge of HTML markup language. Content will be created in the system and derived from external applications and content repositories. All content will be stored or referenced within the Content Management System. Content can be from other Web pages (html), XML content, MSWord documents, PDF documents, entered or copied text, existing PC files of various types, and multimedia objects (graphics, audio, video, etc). The CMS must be able to track content and support action dates (begin date, review date, archive date, end date, etc). The CMS must provide a content “review and approval” workflow for some areas but not all. The CMS must be able to support multiple methods of content entry from a decentralized environment. Creating Content 1. Describe how content is entered or submitted using your product. 2. Describe the necessary skill set to add content to your product 3. Does your product make creating pages with the correct template and placement into the proper directory self-evident? Describe how. 4. What text formatting tools are available in your product? Is there a WYSIWYG option that is familiar to word- processor users? 5. Does your product allow users to edit preview their content for multiple display formats, e.g., for a web browser, PDA and kiosk? 6. Does your product have a built-in spell checker? Can custom or third-party dictionaries be added to the spell checker? 7. Does your product allow copy and pasting from Microsoft Word, Excel and other office productivity applications? Does your product offer the option of stripping-out Microsoft formatting? 8. Describe how your product accommodates various content types, such as. text, HTML, PDF, MS-Word, XML, graphics, audio, rich media, etc) in terms of storage & management, and types natively supported. 9. Can your product import content from HTML editors and recognize HTML formatting tags within text content type? Explain. 10. Does your product allow for direct editing of the HTML in the edit environment? 11. Does your product have a code validator for catching errors in HTML, XHTML, XML, etc. 12. Does your product provide any tools for creating and managing forms? Managing the Content Lifecycle 1. How is access to content and functionality controlled or restricted through user permissions? 2. Does your product support workflow for editorial and approval processes? Describe. 3. Can the workflow be extended through scripted events or through the product API? Describe. 4. How are users notified of workflow assignments? Are notifications customizable? How do users track their tasks and assignments within the CMS? 5. We would like the ability to attach notes to content items within the workflow, and for these notes to remain until final submission. How does your product support reviewers’ comments or notes? 6. Does the product support content versioning and roll-back? 7. Does the product offer “red-lining” to view content changes and approve or reject previous drafts? 8. We would like robust inbox capabilities for each workflow recipient to organize and prioritize the items in the work queue while providing status on each work item. How does your product support this? 6 RFP: Web Content Management System
  • Hampden-Sydney College 9. Does your product support a workflow for out-of-date and expired content? 10. Can e-mail notification be automated for certain types of content that are nearing their expiration dates. 11. Does your product support multiple workflows based on content type? Parallel workflows? It is possible to create an ad-hoc workflow for specific content. 12. Can Site administrators and editors search for pages that have not been updated in "x" number of days, weeks, months, or years. Managing Content Assets 1. Does your system allow for associating metadata with content assets? Explain. 2. Describe how your product supports content indexing and cross-referencing through metadata, content keyword attributes or explicit content identifiers. 3. Can content classifications, such as metadata, keywords or explicit content identifiers be used to search for content, build content listings, build content navigations and optimize content for search engines? 4. Can metadata and meta-tags be defined and entered by content contributors? 5. How are images and other multimedia objects stored and managed in your system? Can users associate metadata with images and multimedia objects? Explain. 6. Does your product apply metadata to images and other multimedia objects when they are uploaded? 7. Does your system make uploading images, PDFs, MSOffice docs, and media to the proper directories self- evident? Explain. 8. Are there easy-to-use methods to add directories and manage documents within them (adding, renaming, moving, deleting, archiving). 9. Can your system automatically format images and other rich media based on pre-defined standards for resolution, size and number of copies? Managing Site… 1. Can menus and navigations be automatically generated based on directory content and rearranged to any order, if user is given permission to do so. 2. Does your product have the ability to export content elements from one page for use on another page or in another site? 3. Are links in the system maintained when content is moved? 4. Is there a utility or tool for checking and repairing broken internal and external links. 5. Does your product include pre-built functionality for querying databases? If so, what databases are supported? Is there an easy way for non-technical content contributors to include database queries on their pages? If so, describe. 6. Does your product have pre-built functionality for inserting data from third party applications commonly used in the government? If so, explain. 7. Does your product have the ability to import feeds from third party content providers? If so, what data feeds are supported? Is there an easy way for content contributors and site administrators to manage these feeds? 8. What other pre-build modules or functional components does your product ship with? 9. Does your product have the ability to easily import legacy Web content (HTML)? 10. Does your product have the ability to easily import XML based content? 11. Is there is a way to set-up permanent, descriptive URLs (whether dynamically generated or static)? 7 RFP: Web Content Management System
  • Hampden-Sydney College 12. Does your product have the ability to archive content in a separate data repository? Can archived content that is no longer on the production Web site be searched and retrieved for display on the live Web site? Content Storage and Re-Use 1. How is content stored in the system? 2. Does the system provide a clear separation of form and content? How is this done? Is content stored with any HTML or XHTML formatting? 3. Does the system support storage of content as XML data? 4. Does the system support content transformation using W3C standard XML and XSLT? How is content re-used in the system? For instance, can content be updated in multiple places by modifying a single content instance? Can multiple instances of a single piece of content appear differently in different places (such as the words in a text block can be changed where it appears in one place without changing it everywhere else)? 5. Is re-usable content functionality “plug-and-play” or does it require template coding? 6. How is external data integrated into the system? Does it require template coding? 7. How are Web Services integrated into the system? Search 1. What search functionality does your product have for searching content on the published site? How is this implemented? 2. Does your product integrate with any of the large-scale Internet search engines for searching content on the published site? If so, which do you recommend? 3. How does your product support or facilitate indexing or spidering of published content by Internet search engines such as Google, Yahoo, Altavista, etc. 4. What search capabilities are available for finding content within the CMS? 5. We need the flexibility to include or exclude content for search capability by various criteria. For example, we need the ability to tag content as available, or not available, to each search function on the site. How does your product support this? 6. Does your product provide search functionality for archived content? Content Syndication and Co-Branding 1. The Hampden-Sydney College may want to plan for future delivery of Web content in other formats, styles, and media. For example, we may want to provide for distribution of content by email, fax, print, phone, browser, PDA, wireless, kiosk, ATM, Video Displays, etc. How does your product support this? 2. Is your product capable of supporting multiple page templates that take advantage of various browser capabilities to display content? 3. Is your product capable of automatically selecting the appropriate content format and stylesheet based on requesting device type or URL or cookie? If so, please explain. 4. Does your product support output to RSS? Explain. 5. Does your product support templates that let site visitors choose alternate style sheets, such as for large print, aural readers or print friendly versions? 6. Is it easy to build sites that are compatible with U.S. Government Section 508 accessibility standards. Explain how this would be done with your system. 7. Is multi-lingual support built into your product? How are multi-lingual sites implemented in your system? How is multi-lingual content managed through the translation cycle? 8 RFP: Web Content Management System
  • Hampden-Sydney College 8. Does your product include translation memory? Do you integrate with or provide any translation services? 9. Is your product capable of exporting content to be reused in other systems? What other systems are supported? 10. Does your product allow site visitors to render any given page as a PDF document? If so, please explain. 11. The Hampden-Sydney College would like to provide co-branded content to other organizations and agencies. Please describe the capabilities of your products for supporting these initiatives. Publishing and Replication 1. Describe your product’s publishing and content replication capabilities, i.e., how is content published and how is content moved from the CMS server to the Web production server? 2. Does your product support publishing multiple sub-sets of the same site? Multiple sites? 3. Can publishes be scheduled? Can instances of a single piece of content be scheduled to appear for different lengths of time in different places. 4. Can content be scheduled for state and expiration dates and times? 5. Does your product support content replication? If so, describe how it supports replication and provide an example of an implementation. 6. Can content be published into portals or into other Web sites? Application Integration The Hampden-Sydney College has numerous central Web-based systems that deliver business information to the community. Additional functionality is envisioned by integrating these services and services of other external processes into or through the portal site. We must be able to integrate with or provide access to these services directly through the portal site. 1. What HTTP servers does your product support? Outline how each supported server is integrated with your product. 2. Does your product have an open API? 3. Does your product integrate with other servers, applications, and tools (e.g. credit card authorization, email, Cold Fusion-based environments, etc)? Explain the process for doing so. 4. Does your product have the ability to easily import content from databases and administrative systems. Customization 1. Can your data model be customized to meet Hampden-Sydney College needs? If so, explain. How is the customization carried forward in product upgrades? 2. Can your CMS handle customized applications in PHP and Perl? System Administration 1. Describe the typical software installation and configuration process, the amount of time required, and the skill sets and training required for system administrators to perform a system installation. 2. Describe the number of applications and separate systems required for installation and configuration. 3. Describe the process for site back-ups and restores. What redundant strategies for emergencies (e.g. when site is down, etc.) are supported? 4. Describe how accounts and privileges are created and managed for use within the CMS. 9 RFP: Web Content Management System
  • Hampden-Sydney College 5. Can users be authenticated to an existing LDAP store? Which LDAP stores or user management systems are supported? 6. Describe the capabilities for accessing the system using secure methods, i.e., SSL or SFTP. Is secure remote access available for users outside the internal network? Explain. 7. What skill set and monthly work load is required for system administrators to manage database modifications and other system additions? 8. Describe system administrator reporting capabilities. 9. Does your product provide for automated archiving? Is so, describe how your product handles archiving of old / expired content and what tools or features you provide to manage content whose expiration date has passed? Do you offer a hosted solution for your product? If so, describe. Tracking and Reporting The Hampden-Sydney College needs to monitor usage of the site to assist in enhancing and refining its Web content offerings and insure that the system is properly sized and designed. Detailed tracking and reporting of web site traffic and usage will be necessary to ensure that the system is properly sized and that user designed and . 1. Describe the reporting and tracking capabilities of your product. 2. Does your product leverage 3rd-party tracking tools 3. Does your product integrate with any of the major analysis tools? Explain. Site Implementation 1. If your product uses templates to place content, describe the steps in creating a template. 2. Describe the skill set needed to create or maintain these templates. 3. Describe how your product applies or enforces style restrictions and constraints on text or graphic contents. For example, if the text content is longer than the area allotted for placement, or the graphic content is smaller or larger than the allotted space. 4. Does your product support a staging or test server for development work? Please provide details. 5. Is there an option to preview content prior to staging? 6. Does your product support templates that allow content to be dynamically queried from the RunTime server? Explain in detail how this is accomplished and how non-technical uses can create these queries on their pages. 7. Does your product allow the presentation of dynamic pages (from the CMS) in conjunction with static pages created as html files external to the CMS? Explain how. 8. Does your product allow the bulk import of existing web pages and assets into the CMS? 9. Does it allow the Hampden-Sydney College to transition in stages to the CMS or does all content have to be in the CMS when launched. 10. The Hampden-Sydney College would like to utilize the CMS to manage the Hampden-Sydney College’s internet site, Intranet site and sites for its CUSO’s, please describe how templates would be created to accomplish this. What additional licensing fees would be incurred to achieve this objective? Product Support and Training 1. Describe your standard product support offering and its cost. 10 RFP: Web Content Management System
  • Hampden-Sydney College 2. Are there any limitations to the number or type of technical support calls that a customer can make each year? 3. Do you provide 24/7 technical support? If so, is there an additional cost for this? 4. How are technical support issues escalated and resolved? Describe the typical resolution process. 5. Describe your training program. Include class schedule, length and indicate whether training is offered at your site or at customer's site. Indicate whether or not any training materials are provided. 6. Describe the different roles and skill sets required to support the product. 7. Describe the professional services offered to facilitate installation and customization? What are the rates for such services? Vendor Information Company Information Please provide the following information about your company 1. Short history of the company 2. Description of the company’s products and services 3. Years In Business Technology Information 1. What is the origin of the core technology offering covered by this RFP? If the technology was acquired from a third party, provide a complete history of previous technology owners and code changes or integration that has taken place since acquiring the technology. 2. Length of time the product you are bidding has been available for licensing by your company? 3. What programming languages are used to develop the technology covered by this RFP? 4. List all third party applications used in the technology offering covered by this RFP. Vendor Experience and References The successful vendor must demonstrate proven ability to successfully perform tasks, and to complete and deliver web site features, as described in this RFP. The Hampden-Sydney College will determine vendor’s stability, adequacy of resources, staffing, products and experience on the basis of bidder’s proposal, and based on checks of references provided by bidder. 1. Please provide at least three customer references. 2. Provide at least three site reference (provide URLs) showcasing the use of your product. 11 RFP: Web Content Management System
  • Hampden-Sydney College RFP Functionality Checklist: ITEM DESCRIPTION CMS System Requirements Will run on Dell PowerEdge 6800 with 8Gb Application Server required for memory and 8 hard drives with 1,168Gb CMS server installation space running Microsoft Windows 2003 Approximate Cost Supported databases Will run on MySQL, PostgreSQL or XML License Per Server with unlimited users Operating System Microsoft Windows 2003 Support for server-side scripting languages Server Side Scripting Language including ASP, PHP, Perl, SSI, and Python Full functionality from web browser without Browser-based plug-ins or downloads Supported browsers(input) Internet Explorer, Mozilla/Firefox, Safari Standards compliant for operability across all Supported browsers(output) browsers Security All changes to content are logged to specific Audit Trail user Captcha Available for form input Content Approval Provides various levels of approval Email Verification System checks for valid email addresses System allows read and write privileges on a Granular Privileges per page or per content item basis LDAP Authentication Supports Microsoft Active Directory Tracks login/logout of users by browser and Login History ip numbers Problem Notification System notifies administrators of problems Users can test new content without affecting Sandbox rest of site Passwords encrypted in database to prevent Encrypted user passwords in access to CMS through a compromised database database User Authenication outside of If sessions/cookies are used, no private Active Directory information is stored in the cookie Can switch between secure SSL mode (128- SSL Compatible bit encryption) and regular HTTP SSL Logins Login is done through SSL Versioning System creates retrievable backups Support There are certtification programs for the Certification Program CMS System provide code templates for Code Skeletons developers to write plugins Commercial Manuals Books or oline manuals are available Commercial Support Support is included or available 12 RFP: Web Content Management System
  • Hampden-Sydney College Commercial Training Training is included or available Pluggable API System can be expanded with APIs An open community of users is available for Public Forum or mailing list sharing Users may attend conferences with larger Users Conference community of users Ease of Use Content from exisitng websites can be Capture or import content imported with tools provided by CMS System notifies administrators of expired Content Expiration notice content Drag-N-Drop Content Users can easily position content URLs are human-readable and search Friendly URLs engine friendly Users may resize images through CMS Image Resizing without using an external editor Users may upload images and other files all Mass Upload at once Spell checker of all content with users able to Spell Checker add custom words to dictionary Link Checker Check for broken links and notify user Set specific start and expiration dates for Schedule Content content Style Wizard All formatting is done through CSS Templates allow definition of areas on a Template Language page UI Levels Different levels of users are allowed Users can undo operations when a mistake Undo is made Inline browser-based word processor for WYSIWYG Editor content input Management Advertising Management Ability to set goals and measure results A central repository of uploading images to Asset Management be used throughout the site Can cut and paste content from one area of Clipboard site to another Content may be added or removed from site Content Scheduling by date Inline Administration Content is edited directly in page Online Administration Content is edited through a web browser Can run more than one web through CMS, Sub-sites / Roots for example, public site, intranet, faculty/staff site Themes / Skins Templates can be shared between sites Administrators can recover content that was Trash deleted Usage statistics are available for an entire Web Statistics site and by subsection like Athletics, Alumni, Admissions for example 13 RFP: Web Content Management System
  • Hampden-Sydney College Web-based Style/Template Styles and templates are managed through a Management web-based interface Web-based Translation Language translation is included Management Some areas may have workflow approval Workflow Engine process and others may not use this Interoperability All content can be exported through Content Syndication (RSS) RSS/XML iCal Calendaring system supports iCal standard Supports UTF-8 character encoding for UTF-8 Support multi-lingual sites System is compliant with Web Accessibility WAI Compliant Initiative (WAI) System follows W3C specification for XHTML Compliant XHTML compliance Flexibility Content Reuse Content can be reused across site Content can be exported to print process in Content Repurposing Adobe InDesign Content objects can have metadata Metadata properties System can host multiple sites from one Multi-Site Deployment software deployment System is capable of rewriting URLs or can URL Rewriting use ISAPI Rewrite for Windows Viewable in multiple display Content can be viewed in web browser, formats PDA, and kiosk Built-in Applications Blogs can be set for public or private Blog comments Chat Real-time chat can be included on a site Discussion / Forum Message board Document Management Documents can be stored within system Includes calendar for overall site and smaller calendars for site specific, for example, Events Calendar College Calendar holds all public events, but Wilson Center wants a department specific calendar. Events Management Registration process for events Users can create forms with content Form generator validation and output to email, text file, or database Graphs and charts can be generated from Graphs and Charts data in system Groupware Like group calendaring Guest Book Guest book or grafitti application Help Desk / Bug Reporting Application to report problems in system Link Management Application to manage links across site My Page / Dashboard Portal application for faculty/staff/students 14 RFP: Web Content Management System
  • Hampden-Sydney College Users can subscribe to receive news on Newsletter various topics Application for creating thumbnail and Photo Gallery resized image repositories Application to run simple question polls and Polls show results Ability to do full-text search of content and Search Engine metadata in system Site Map Automatic generation of site map Surveys Support for multi-question surveys Syndicated Content (RSS) Can retrieve and display RSS/XML content User community can contribute stories and User Contributions other content Can use other web services like Google API, Web Services Front End maps and analytics, for example Wiki Supports wiki functionality 15 RFP: Web Content Management System