Web Services

Campus Web 3.0 Migration

In summer 2017, Web Services began migrating nearly 400 campus websites into the Campus Web 3.0 web framework for the csuchico.edu domain. Along with looking great, 3.0 sites are responsive, mobile-optimized, secure, and more customizable. They are regularly scanned for accessibility, broken links, and other quality control issues. You can see examples of how this new framework looks at the following sites:

University Publication Guide

Presidential Inauguration

College of Behavioral & Social Sciences

Is 3.0 a redesign?

No. It is a modular upgrade to our web framework that is more flexible and easier to maintain over time. It will continue to evolve, changing in response to audience needs, new accessibility and security requirements, and University goals.

How do I get a 3.0 site?

Request your site upgrade through our New Campus Web 3.0 website service ticket. Web Services will contact you about a timeline and schedule a meeting. We have many clients on the waiting list and are currently prioritizing high-traffic sites such as college and division sites. Find more information about how we prioritize requests on our 3.0 Migration Pipeline page.

Will my new site still be in the Cascade web content management system?

Yes. While 3.0 sites are on a new campus server, they are still in Cascade. To update them, you will go to a new URL (wcms.csuchico.edu) and use Hannon Hill’s latest version of Cascade (8). The changes in 3.0 and Cascade 8 give content maintainers much more power to customize their sites--and the system is structured differently, so you will need to take another Cascade training course to make updates.

How much does it cost?

Web Services provides a basic site migration no charge to most campus departments. If you'll want us to begin working on your site by jumping in front of the line there is a charge.

How long will it take?

We can build your site in several hours! A full site can be built within several hours! However, each site must go through a pipeline to determine when your site migration will begin.

Clients who provide a clear site structure to us and choose to migrate their site content themselves can have a 3.0 website within several weeks of their initial meeting with Web Services.

Clients newly added to the waiting list who prefer Web Services to do the work of migration will be in the queue for several months before we can start work.

Custom sites typically take a year and cost $5,000-8,000.

Find more information about how we prioritize requests on our 3.0 Migration Pipeline page.

What is the process, and how can I make it go smoothly?

A site migration is a lot of work! Getting your site ready now will make your migration go much more quickly when we are ready to build.

1. Before we meet

Clean up your existing 2.0 site

When we think about user experience, we need to address more than just how it looks. Take some time to analyze how easy your site is to use and how easily visitors can find the information they are looking for. Look at your site with fresh eyes, with help from our Site Self Maintenance page.

All PDFs that will be published in 3.0 must be submitted to OATS for accessibility remediation. Please plan ahead since this process may take a couple of weeks. Begin to select the PDFs that you will need migrated and identify PDFs with content better suited as a webpage (generally anything that doesn't need to be printed or filled out).

For guidance in writing and editing, refer to the University Standards and Guidelines.

Feel free to make a site map, outline, or wireframe if that helps—it may help us too!

2. Meet with Web Services

A Web Services staff member will contact you or respond to your ticket request to set a meeting date. At the meeting, we will review your current 2.0 content and site structure and make notes about any navigation or content edits that need to be made.

3. Site build from Web Services

Web Services will work from your 2.0 content and site structure notes to build the 3.0 pages. We will use our new template and its available features to migrate your 2.0 content, at that point your current 2.0 site will be frozen from new updates. There is a 10-hour labor cap on 3.0 basic migrations, so you will need to have a clear idea of what you want before we start work. After that 10-hour cap has been reached, you can submit a CAF for additional assistance or attend Cascade Training for 3.0 Site Editors to complete the process yourself.

Please note that if you choose to get trained in Cascade 3.0 and migrate your content yourself, you will move up to the top of the waiting list. Find more information about how we prioritize requests on our 3.0 Migration Pipeline page.

4. Proofing of draft site by you

We will give you the link to the draft site we have created on our development server. You will be provided a list of tips and things to check before the site is published, and you may request fixes for errors and bugs in two revision periods. You’ll get a final proof to sign off on before the site goes live.

5. Site goes live to 3.0!

Web Services will help you plan for a site launch during a low-traffic time. Don't launch your site before an important date or deadline! You should plan for some broken link and other fixes associated with your site going live.

6. Site maintenance

You are responsible for your site content and the requirements in our Campus Web Site-Maintainers Agreement.

For ongoing maintenance of 3.0 sites, your department site maintainer(s) must take Cascade 3.0 training to access and edit your website. Wait until after the 3.0 site has been published to do your training, unless you are opting to migrate your content yourself. Log in with your campus credentials and select “Schedule” in the Development & Training System.

Alternatively, you may use Web Services’ fee-based update service. Updates are typically completed within two business days.

You will receive monthly reports from Siteimprove on your site's quality, accessibility, and analytics to guide your efforts in keeping your site up to date.