Responsive Migration & Conversion Tool
Digital Publishing has created a tool that migrates your legacy website and converts it to a responsive website, one that uses responsive templates and components. The converted site is placed in the CQ development environment where you can make changes and update it before replacing your existing live site.
What you need to know about converted sites
Digital Publishing does not troubleshoot migrated/converted content. Always refer to your production (live) site for comparison while working in your development site. If content is missing from DEV, please get a copy from production.
Your content is now governed by the rules of the responsive templates. Certain features, functionality and code are not permitted in responsive templates (see differences between legacy and responsive templates). Please familiarize yourself with the responsive templates and components before submitting issues about converted content.
News & Event page components are now News & Event templates
All news and event components are migrated to responsive news and event templates during our conversion process; however, the files are MOVED to new file locations. This may result in broken links for external sites linking to news and event content on your site.
If a page has multiple news or event components, each news/event component will be split and migrated to a new, unique page. Responsive news/event pages can only contain ONE news item or one event.
News & Event require Archives
In the responsive templates, archive templates must be created to 'house' news and event templates. News and event templates can only be created in the MONTH archive (01, 02, 03...January, February, March...) of a YEARLY archive (2017, 2018, etc.).
e.g. In the following URL, 2017 is a year archive; 11 is the month archive
During the migration process, yearly and monthly archives are automatically generated based on the date of your news or event. Then, your news or event pages are moved to the corresponding year and month archive. Any news or event lists, or calendars in your site need to be manually updated to point to the new file locations. This is a simple process of changing the path to the new archive location.
For more information, please visit the following pages:
Many pages in CQ were created in our old CMS (Collage) and migrated into CQ over six years ago while other pages have been built using non-standard and unsupported practices. We cannot guarantee that all Collage pages or non-standard content will be converted in a usable format. If you don't like the way the converted page looks, simply delete the components and rebuild the page using layout and content components.
No index files will be present in your converted site. Content from an index file gets moved to its parent during the conversion process.
Content in this index file -> ryerson.ca/water/index.html
gets moved to -> ryerson.ca/water.html
All of the following URLs will work and resolve to the same page:
ryerson.ca/water = ryerson.ca/water.html = ryerson.ca/water/index.html
What happens if both files have content?
If the parent (i.e. water) contains content, the index file's content will get ADDED below the original content.
The name of your site, or the title of your site, is not autogenerated. There is no header file. The site name is added in the inheritedContent template. Do the following to add your site name:
- Open the inheritedContent template
- Locate the Local Header component in the
- Right click to edit
- Add site title
- Click OK
- Activate inheritedContent template
Each converted webpage will automatically display a mandatory Heading 1 (H1) at the top of the page. This H1 is derived from the Title on the page (added when new files are created). If another heading is present, this will create duplicate headings on pages. Simply remove the duplicate heading from your page by deleting the component.
Please review the Ryerson Web Style Guide to determine the appropriate colour palette for your website.
Images will be mapped to the most appropriate responsive image component (Image component with optional text or slideshow); however, the display options may have to be modified and most images will need to be replaced with images of the correct scale (1200 pixels X 900 pixels).
- Learn more about responsive image specifications
Legacy 'Image and text components' are mapped to the responsive 'Image + optional text component'. In most cases, the display will be a 50:50 split. Modify this as necessary.
Most images will need to be replaced with higher resolution, responsive-ready images.
Layouts are unlikely to look the same post-conversion.
If something doesn't look right, start over with new components.
Empty image components:
Some image components will appear blank but in edit mode show an image. These components should be deleted as images are not retrievable. This resulted from a time when images could be added directly to the component instead of the DAM.
Delete empty components from pages where they appear empty. Check the live site for missing content.
Biography components are converted to responsive biography templates and existing fields are mapped to the new template. A person’s full name (first and last) will appear in the first name field. Separate the first and last names into the appropriate fields in the new bio template.
Legacy gallery components will be converted to responsive slideshows, not the responsive gallery grid. Due to the updated configuration of the responsive gallery grid, it is not possible to map legacy galleries to the responsive gallery grid.
If you wish to replace the converted slideshow to a gallery, delete the slideshow, drag in the new gallery grid, and configure the path to the DAM folder location of your images.
To address layout issues, use responsive components and layout components to improve the interface and layout.
- Reduce the manual effort required to build a site in the responsive templates.
- Develop a tool to convert content in legacy templates to responsive templates.
- Move content to responsive templates and components while maintaining existing file structure.
- Retain text content and relative paths i.e. links, where possible.
- Maintain basic HTML tags such as H2-H6, <b>, <em>, <p>, <br>, <a href=> and mailto tags, only.
- Map 750 template navigation to responsive template navigation.
Capture navigation information from 960 legacy templates in a single file (NavInHeader.html).
- Convert legacy components such as news, events and bios to respective responsive templates.
- Maintain relationships between structured content and lists (news, events and bios).
- Maintain tagging structure and references.