Update on CMS migration project; action may be required
Update on CMS migration (web guidelines and standardization) project, review of deadlines and action items needed.
On August 28, 2008, Information Technology (IT) and Communications & Marketing (OCM) held a public forum to announce a new strategy for university websites and departmental business applications, including a move to the Plone content management system (CMS) for all static sites and a move to Java or APEX for all departmental business applications. In addition, you may have received e-mails related to each phase of the project over the course of the fall semester. Today, we would like to update you on the status of the project milestones and request action from you if any of the action items apply to you or your unit’s website or business applications.
The guidelines, presentation and video from the Aug. 28 forum are available for review.
Each phase of the project is listed below along with its deadline and action items. Please read all phases and take action when needed according to the instructions listed.
1. Reduce security risks by moving to a more secure web environment in the fall
Deadlines:
- Dec. 19, 2008: School, department, center, institute and other non-personal websites moved from athena
- Dec. 31, 2008: Personal websites on athena (louisville.edu/~USERID) discontinued
Description: In this phase, IT and OCM are moving all static, non-CMS sites from athena to a more secure server. To further enhance security, we are discontinuing the use of FTP and SSH for file transfers. After the deadlines above, we will be using WebDAV for file transfers to static, non-CMS sites.
Action item: If you have not yet moved to the Plone CMS and need access to maintain your department’s non-CMS site after Dec. 19 while you are moving your site to the Plone CMS, please request access via WebDAV. You will receive a response with details you will need to use WebDAV to maintain your non-CMS site. We will also provide documentation.
Action item: If you still have website files on your personal site (louisville.edu/~USERID) or if you store any files on your Athena account, you must retrieve them by Dec. 31, 2008. If you are a faculty member and would like to create a site in the CMS, please request a Plone CMS site.
2. Introduce enhanced features and design templates by upgrading CMS to latest version of Plone
Deadline: Jan. 30, 2009
Description: We are upgrading our Plone CMS software to the latest version. We will also be implementing new template designs that will incorporate the university’s “It’s Happening Here” branding elements.
Action item: During the two-week period of Jan. 12-24, 2008, we will provide testing at two locations: Miller Information Technology Center room 117 on Belknap campus and K-WING (School of Nursing) room 3008 on the HSC campus. If you currently maintain a Plone CMS site, please mark those dates on your calendar and go to either location to test your site in the lastest version of the Plone CMS. Documentation will be provided at both locations.
3. Migrate all remaining static, non-CMS sites to the university’s Plone CMS
Deadline: June 30, 2009
Description: All static, non-CMS sites for schools, departments, centers, institutse and any other non-personal websites must be moved to the Plone CMS by June 30, 2009.
Action item: To ensure that you have ample time to move your site, please request your Plone CMS site by February 28, 2009 at https://louisville.edu/web/tools/site-requests
Action item: After you have built your new site in the Plone CMS, you must submit the site for content and web accessibility approvals by April 30, 2009 to ensure that all possible changes can be complete by June 30, 2009. Additionally, the IT Applications Development team will be available to help move your site to the Plone CMS on a charge-back basis. If you would like assistance from IT, please request it using our secure form.
4. Standardize departmental application development by converting all applications to JAVA or APEX
Deadline: March 31, 2010
Description: All departmental business applications written in non-Java languages (php, perl, cold fusion, etc.) must be rewritten in Java or APEX by March 31, 2010.
Action item: To begin the process, please contact the IT Applications Development.
If you have any questions about any of the information above, please contact us.
Thank you.
Update on CMS migration project; action may be required
