{"id":9983,"date":"2024-01-12T14:49:47","date_gmt":"2024-01-12T19:49:47","guid":{"rendered":"https:\/\/www.eng.ufl.edu\/marcom-dev\/?page_id=9983"},"modified":"2025-09-25T09:17:14","modified_gmt":"2025-09-25T14:17:14","slug":"migrating-from-hwcoe-2019-to-hwcoe-mercury","status":"publish","type":"page","link":"https:\/\/www.eng.ufl.edu\/marcom\/resources\/web-services-standards\/wordpress-help-and-how-to\/mercury\/migrating-from-hwcoe-2019-to-hwcoe-mercury\/","title":{"rendered":"Migrating from HWCOE 2019 to HWCOE Mercury"},"content":{"rendered":"\n

The HWCOE 2019 and HWCOE Mercury themes work quite differently. While 2019 content is mostly edited in WordPress’s older Classic Editor<\/a>, Mercury makes extensive use of the Block Editor<\/a> and is much more modular in its approach to content. While this makes it easier to create attractive layouts without coding, it means that migrating from 2019 to Mercury is not an instant process, though we’ve developed page and post templates that do not require rebuilding your content with Mercury blocks in order to be readable.<\/p>\n\n\n\n

The instructions below are for units whose sites reside on WordPress installations administered by Herbert Wertheim College of Engineering Marcom.<\/strong><\/p>\n\n\n\n

Step 0: Assess your current site<\/h2>\n\n\n\n

Updating to a new theme is an excellent time to audit your site content. Do you have old images or posts you no longer use, or content that is out of date or duplicated on another UF site (or even on another section of yours)? A content audit can help you discover these issues.<\/p>\n\n\n\n

Sample content audit process with template<\/a><\/p>\n\n\n\n

Before switching to Mercury, you will also need to go through your site and note any pages that use page templates other than the default<\/a>, as these will all be converted to use the Default page template in Mercury when the theme is switched. Any content in the custom fields within those templates will no longer display and will need to be moved into the main edit window or put into Mercury blocks<\/a>.<\/p>\n\n\n\n

\n
\n
\"In\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n\n
\n
\"In\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n<\/div>\n\n\n\n

Step 1: Request a development site<\/h2>\n\n\n\n

If your site is hosted on our WordPress infrastructure, submit a Web Related request<\/a> to have a development site created. We will create the site as https:\/\/domain.ufl.edu\/yoursite-dev\/ and import your existing content. <\/p>\n\n\n\n

If your instance of WordPress is self-hosted, you can create this site yourself or have your network administrator do it.<\/p>\n\n\n\n

Step 2: Convert or build your content<\/h2>\n\n\n\n

You will notice when you first view your development site that the content doesn’t look very readable; this is normal! You’ll need to convert your pages and posts to Classic Editor-friendly templates or rebuild them in the Block Editor<\/a> using Mercury blocks<\/a>.<\/p>\n\n\n\n

If you do not have time or personnel to rebuild your content, HWCOE Mercury has two page templates and three post templates<\/a> that can display old Classic Editor content.<\/p>\n\n\n\n

To bulk change the templates of multiple pages or posts: <\/p>\n\n\n\n