Steven Powers is overseeing web migrations until Web Com Manager role is filled. Information about the migration process and request form is available online at https://publicrelations.ucmerced.edu/web/responsive-templates
Migrations are recorded on Google Sheets -
As new request arrive, record on the: In Migration tab and move over to the Migrated tab when completed.
https://docs.google.com/spreadsheets/d/15J6RAhjbia_DeplKH0_HsOaTTBbkftwgShgcLoRyKqQ/edit?usp=sharing
- After receiving migration request and having logged it on Google Doc, build the migration request in Jira and use the following subject line to create filters for tracking:
Subject line: Responsive Template Migration: sitename.ucmerced.edu
Include details of the migration form on how they want it set up.
Ex: 3/4 pano slider with blank sidebox or full slider
Newsfeed (send client form for news feed request on PR site)
Events feed (send client form for events feed request on PR site)
etc
Most clients are requesting same front-page layout and the sliders will need to be recreated. If client staff availability is an issue I have been recreating the sliders for them to speed up the initial process.
If they check Need consultation for layout, email client and suggest they sketch layout ideas and refine for them before implementaion.
- Once you have set up the migrated site, fix any formatting issues, such as:
- Tables
Upon migration, they turn very ugly with borders and bad formatting, there might even be span tags. If you see span tags I have been scrubbing the entire page first using http://word2cleanhtml.com/
Set table to 100%
Set the first row of cells to percentages for scaling purposes. Ex: Two column table, the table is set to 100%, first and second cell properties set to 50%.
This allows for responsive scaling.
- Images
Make sure they're Alt Text set - send back to client to update with direction to provide brief description of photo.
- Filtered HTML
Older sites have pages set to Filtered HTML, set to full and you might encounter span formatting. Scrub page to rid format issues using the Word2HTML site.
- UC Merced logo
Update logo to point to gateway. Under Configuration > Appearance > scroll to bottom of page.
- Once fine tuned, send the updated site to the client with log in so they can complete any last minute changes or updates. Ask them to review and let you know when they are ready to launch. We’ve set a 48-hour work week turnaround time.
- When client approves and is ready for launch:
Submit the Go Live!! Ticket in Jira. By default it goes to Derek and he will handle the move from dev to prod.
To make launches easy to track in Jira, use the following subject line:
Go Live!! Sitename.ucmerced.edu.672elmp01.blackmesh.com - Once site is live, do a quick run through to make sure there are no hardcoded links left behind pointing to dev.
If requested, turn on GA module and enter tracking ID
Add site to SiteImprove and end user to receive reports if site is not already on SI. - Notify site owner the site is live and they can proceed to edit at the production addres.
