Why a new CMS?
One of the initial reasons for forming the Web Advisory Committee in June 2012 was to help ensure a smooth transition into a new content-management system (CMS). This page includes information about the upcoming migration, but if you have any questions that are not answered here, please reach out to the WAC.
Why is Dickinson migrating to a new CMS?
The simple answers are "opportunity" and "integration." Two years ago, the college's enterprise systems team began looking for a software replacement for our current Ellucian Luminus-based Gateway portal. They chose Jadu (pronounced JAR-du). One of the benefits of Jadu is that it is also a very powerful and flexible content-management system (CMS) and mobile-application development tool.
Currently, we have one product supporting the Gateway portal (Ellucian Luminus), another (Ektron) supporting the public Web site, and a third product (Boopsie) supporting our mobile app. Jadu allows us to bring these three disparate areas—which are currently maintained by separate staff in marketing & communications (MarComm) and Library & Information Services (LIS)—together into one system.
That's a huge step forward for Dickinson from a support standpoint, and it also means a more seamless Web experience for users who need to navigate between the public and private areas of the Web site, or for content producers who will be able to create and edit portal and public content using the same product.
Finally, there's the financial benefit: Integrating our CMS, portal and mobile development in one system will help Dickinson save money on an annual basis.
When will migration finish?
The Web Advisory Committee and the MarComm and LIS teams are committed to keeping the community informed about the migration process and will provide opportunities for feedback and training in the new system. Regardless of its CMS, Dickinson's Web site can only be as successful as the people who are maintaining and contributing to it want it to be, so collaboration between MarComm, LIS and the campus community is a priority throughout the process.
We are projecting content migration from Ektron to Jadu, which began in spring 2013, to conclude by early Nov. 2013. As of September 1, 2013, the college had migrated 47% of site content.
Can I continue to update my site in Ektron during migration to Jadu?
Yes! It's important that all departments and offices keep their content current. Just remember that once you've started the migration process, you'll need to replicate any changes you make in Ektron on the same pages in Jadu.
Have more questions?
You can learn more about Jadu on the company's Web site. Questions about the migration can be directed to the Web Advisory Committee by e-mailing firstname.lastname@example.org.