Website Content Management Services

The vendor is required to provide website content management services (CMS) for include:
a. Creation and publishing
1. Content creation
• Allow full and flexible control over all pages where allowed (have permission). 
• The web CMS must not constrain design.
• Template driven – allowing template creation by designated internal staff
• Control of style (using style sheets) through CMS admin e.g., changes to colors across sections.
• Ability to include web programmer created style sheets.
• Allow flexibility in design of lower-level pages while maintaining corporate identity and global navigation. 
• Provide a system for content creation that requires minimal training and can be used by nontechnical users. 
• Ability to accurately preview pages in a browser and ensure the preview pages are not exposed to external search engines.
• Ability to edit content items independently of the published work. 
• Ability to perform spell checking of content. 
• the spell check dictionary should be customizable at user and organizational level. 
• Ability to add content using a WYSIWYG editor. 
• Editor should work in a variety of browsers including i.e., Firefox, chrome and safari and on both pc and mac platforms. code produced by editor should be XHTML compliant. 
• Ability to easily customize the editor’s features/buttons. different levels of authoring options should be available, or features be hidden based on that user’s permissions.
• Ability to easily integrate rich media (e.g., video, audio etc.) where appropriate. 
• Add additional documents to pages (e.g., pdf, hi-res images etc.). 
• Creation and integration of multiple sites (or micro sites) - provide tools to support deployment of multiple sites. 
• Support for online forms, data collection and analysis – e.g., PG applications, open day bookings, prospectus requests, email, surveys, etc. 
• Provide a comprehensive ‘undo’ function in the content editor.
• Ability to insert content that uses cold fusion. 
• Code should be executable in a production/preview environment. 
• Ability to insert content that uses server-side scripting (e.g., asp, php, JSP).
2. Content publishing and quality control
• Users do not need web technical skills in order to publish content. 
• Publication of content can be controlled by start date, review date, expiry date settings. 
• Ability to automatically set or change dates for review and expiry of a content item (e.g., author, content item type or site standard/policy for review dates). 
• System should be capable of sending reminder emails based on review and expiry dates. 
• System should incorporate an escalation procedure for reminder emails. 
• Ability to publish a single item of content to multiple delivery environments with the option of selecting different delivery requirements/templates depending on publishing location. 
• Ability to publish multiple variations of a single content source to a variety of web page contexts on the same website or to different websites (e.g., for different audiences, languages, summary or full version of the content item) 
• Publish content to multiple sites depending on audience (e.g., external / internal-facing websites). 
• Support delivery of content items based on completion of review/approval workflow processes. 
• Ability to manually override automatically generated review and expiry dates for content items based on hierarchy of role. 
• Ability to maintain integrity of internal links within the web CMS. 
• Ability to detect, notify, manage and allow maintenance of broken web links. 
• Roll-back and audit trail – ability to view and re-instate previous versions of specific pages and view full history of content changes across the site. 
• Ability to publish/unpublish content items to more than one website generated by the web CMS.
• Ability to publish/unpublish content items to more than one website generated by the web CMS on a scheduled date and time. 
• Ability to publish and unpublish content items in bulk. 
• Ability to search, preview and replace a content item across the site or sites managed by the web. functionality restricted by role. 
• Support delivery of content items to a range of delivery channels and technologies, covering both on-line and offline (e.g., mobile phones, handheld devices, interactive television and print). 
• Ability to provide notification of details of links that will be affected by removal of an expired content item.
• Ability to apply mandatory validation processes (e.g., for accessibility compliance, page size (and speed) and broken links). 
• Ability to restrict access to content by specific groups of users. (e.g., for publishing content to internal audiences and applicants etc.)
3. Workflow processes
• Ability to establish a variety of steps within a workflow process that is part of the CMS and doesn’t require external tools. 
• Ability to assign workflow to classes of content items as well as roles and individuals. 
• Ability to grant or withhold specific permission based on role, type of content item and other criteria. 
• provide a workflow process that supports sequential approval steps. 
• Provide a workflow process that supports parallel approval steps. 
• Provide a workflow process that is configurable to support varying content item status during the authoring process (e.g., draft, awaiting approval, approved, published, archived etc.). 
• Provide a workflow that is configurable to allow different approval processes based on the type of content being created.
• Provide a workflow that is configurable to allow different approval processes based on where the content is being published. 
• Provide a workflow that is configurable to allow different approval processes for different groups within the university.
- Questions/Inquires Deadline: July 10, 2025