Go to www.utc.edu
Visit Us Request Info

Division, Department, and Content Type Changes

Home » Division, Department, and Content Type Changes

Directions on moving a department, creating a new department or division, or moving existing content to a new content type

Areas of Attention:

  • Sidebar menus on child pages (Layout mode)
  • Menu assignment of child pages (Edit mode)
  • Footers (only applies if you’re moving from one department to another or creating a new department)
  • Workbench Section (only applies if you’re moving from one department to another or creating a new department)

Steps:

Skip step 1 and go to step 2 if this is just a content type change, not a department move or new departmental/division creation.

* Indicates that this step is a necessary preliminary step to a new homepage creation.

    1. NEW DEPARTMENT, DIVISION, OR MOVE FROM ONE ORGANIZATION TO ANOTHER.
      1. If it is a new department or division, a developer must do the following first*:
        1. Create new taxonomy in the UTC organization chart for the new department.
/admin/structure/taxonomy/manage/utc_organizational_chart/add
        2. Create a new departmental information block (used in the footer) with contact information. Be sure to note the number in parentheses under “UTC ORGANIZATION SECTION”. You will need this for the next step. /block/add/utc_department_info_block
          • Easiest way: Find a similar footer and in the “Edit” dropdown, select “Duplicate”.
          • Change the necessary info:
            • Label
            • Descriptions
            • Under “Conditions” > “Content Type”, enter the UTC Organization Section number you retrieved from step 1b above.
            • Scroll down to “Content” under “Reactions”. Remove the duplicated block and add the new block you created in step 1b above.
            • Save and Exit.
        3. Export the new configuration to be put into your local and PRed. 
/admin/config/development/configuration
This will include context.context.NEW_DEPT_INFO_FOOTER and may also include taxonomy configuration (not sure).
          • Make note of the files changed.
          • Go to the Export tab, select the configuration type, then the configuration name.
          • Highlight all of the configuration information and copy it to your clipboard.
        4. Import the new configuration into your local environment.
          • Under utccloud > config > default on your local, create a new file using the EXACT name of the one in the production configuration.
          • Paste your configuration from your clipboard and save.
        5. DEVELOPER: Create an issue in UTCCloud repo and then follow normal procedures for creating a pull request for the new configuration.

      2. If it is a move from one department to another, a developer must do the following first*:
        1. Drag and drop department taxonomy from the old division to the new one /admin/structure/taxonomy/manage/utc_organizational_chart/overview
        2. Go to its departmental information block (used in the footer) and update the contact information to reflect the change, INCLUDING the new UTC Organization. Be sure to note the number in parentheses under “UTC ORGANIZATION SECTION”. You will need this for the next step.
        3. Use the filter to find the dept info block on this page: /admin/structure/block/block-content
        4. Change the context for Dept. Info Footers. /admin/structure/context
          1. Find your department’s footer and select “Edit” in the dropdown.
          2. Change any necessary info:
            • Label
            • Descriptions
            • Under “Conditions” > “Content Type”, enter the UTC Organization Section number you retrieved from step 1b above.
            • Scroll down to “Content” under “Reactions”. Remove the existing block and add back the block you changed in step 1b above.
            • Save and Exit.
          3. Developer will need to follow Steps 1d-f above.
      3. Create your new homepage
        1. In “Draft” mode, create the new page with the new content type. Ex., an interior landing page needs to become the department’s homepage using a homepage content type.
        2. Go through the show and tell and approval process with the appropriate stakeholders.
        3. Once the approval process is complete, the next step will need to be done VERY quickly as these changes are taking place live. Recruit help if the pages are too numerous to accomplish in one sitting.
        4. Publish the newly created parent page/node.
          • URL designation: Chose one of two ways to update the URL of the homepage.
          • Redirect both the URL of the old homepage as well as its node ID to the new homepage (/admin/config/search/redirect ) OR
        5. Under the “Edit” tab of the node, rename the old homepage URL alias and unpublish that page, then apply the old URL alias to the new page/node. Got to /admin/config/search/redirect to redirect the node ID as well.
        6. Update/add the parent to the menu. /admin/structure/menu
        7. If it is a new department or division, you may need to create new child pages. Add those as you would any new page with the correct workbench/organization and menu assignments.
        8. If it is a move from one department to another, you will need to move existing pages to the new workbench/organization. This is more involved.
          • Retrieve the sitemap of the existing content to be moved from SiteImprove. This will aid in the migration of subpages to the new parent page.
          • Child page changes: Each child page will need to be reviewed and changed.
            • Edit tab: Change the “Menu” location if necessary to the new homepage.
            • Layout tab: Begin the process of reattaching parent menus to child pages. NOTE: if the child page did not use the parent menu, but rather a child of the parent menu, then the sidebar menus should still be there.
NOTE: If there are more than 50 pages, you may want to enlist another web content editor to help the process as these pages are live updates and must be made quickly. Communicate clearly how the work will be divided.
            • When you have completed reconnecting menus on all the child pages, double check your work.
        9. You will need notify Google of all the changes. You must have account permissions to do this task.
        10. CHECK YOUR WORK and notify stakeholders to check it as well.
    1. CREATE THE NEW HOMEPAGE WITH A NEW CONTENT TYPE ONLY. NO CHANGE IN DIVISION OR DEPARTMENT ASSIGNMENT.
      1. In “Draft” mode, create the new page with the new content type. Ex., an interior landing page needs to become the department’s homepage using a homepage content type. 
      2. Be sure to assign the appropriate (new?) Workbench/Organization to the page. 
      3. Go through the show and tell and approval process with the appropriate stakeholders. 
      4. Once the approval process is complete, the next step will need to be done VERY quickly as these changes are taking place live.  
      5. Go to your new page to the “Edit” tab. 
        1. Retrieve the node number in the URL during publishing: /node/###### 
        2. Publish the newly created parent page/node. 
        3. Save. 
      6. Go to /admin/structure/menu and navigate to the menu in which the parent is being placed or replaced. If it is a replacement, there is likely a disabled button with the link to the old page as well as an enabled child button with the same link. The link will need to be changed in both places. 
        1. Click on the parent button’s edit button (under “Operations”) first.  
        2. In the “Link*” field, paste or type the node and number: /node/###### 
        3. Save 
        4. If applicable, do the same to the child button with the same homepage link. 
        5. Check both those links. (Use right click to “Open Link in a New Tab” to keep the menu page open.) 
        6. On the open menu page, select any of the other children to verify that the submenu in the sidebar exists. 
        7. Click on numerous other pages to check as well. 
      7. URL reassignment:  
        1. Under the “Edit” tab of the node, rename the old homepage URL alias (or change the name in the SEO title field. 
        2. Get the node ID of that old homepage and copy to your clipboard.
        3. Unpublish that page and save. 
        4. Redirect both the old URL alias AND its node/ID to the new page/node. 
      8. Child page changes: Each child page will need to be reviewed. 
        1. Check the breadcrumbs. 
        2. Check the sidebar menu. 
      9. If it is a new department or division, or a move from one division to another, that probably changes or adds URL paths which must be revised for Google Search and Silktide QA/Analytics.
        1. Ask a Google admin to request removal the old URL path + subpaths in Google Search Console, then request reindexing of the new URL path + subpaths.
        2. Ask a Silktide admin to modify or create the URL rule(s) for the section’s Domain Group, and assign or create a user account to have access and reporting for the group.
      10. CHECK YOUR WORK and notify stakeholders to check it as well.