Category Archives: advanced functions


Footer Call to Action Buttons

You can choose to add call to action buttons at the top of the footer on your website. You can choose to add just the Give button linked to a page of your choice, just the recruitment buttons with preset links, or all four. The default is no buttons. This is only available in the _props.pcf file within the root folder for your site or the folder where navigation is restarted.

Example footer showing all buttons.

Continue reading


Research Projects

Academic departments have the option to automatically pull in research project information to their CMS website. The information comes from a database of projects that are approved for public knowledge by the Research Office. The standard information that is pulled in is:

  • Principal Investigator
  • Co-PI
  • College/School
  • Department(s)
  • Sponsor
  • Center/Institute

The PI and Co-PI fields will automatically link names to their faculty page if one is set up in the CMS.

Example of research projects listed on a website.

Departments can be given the ability to override this information (as viewed on your departmental website only) or manually add projects that are not listed. If you have never used this function before, you must contact cmshelp@mtu.edu to get set up. Departments currently set up are Mechanical Engineering-Engineering Mechanics, Electrical and Computer Engineering, and Computer Science. Continue reading



Approval Workflow

The Approval Workflow in OU Campus is an optional function that a department can use when creating or editing content that needs approval from someone else before being published. This process allows the item to remain checked out to a user throughout the process until it has been completed—either published or reverted back to the previous version. Keeping content checked out is important so that the item is not published unintentionally before it should be.

  • The item goes from being checked out to the editor to being checked out by the approver and possibly back to the editor depending on what the approver selects.
  • The approver can deny the changes or publish/approve them.
    • The approver must have CMS access, but could have view-only access or edit access. An approver with edit access could publish the changes if approved, with view-only access the approver can only approve the content and return the item to the first person for publishing if approved.
  • OU Campus will send an email notification to the approver letting them know you have sent them something. This email can include a custom message from you.

Continue reading


Department Publications

Departments who produce regular newsletters or magazines are able to use the Michigan Tech Magazine template to digitally display their publications on their departmental website. You can refer to the Biological Sciences Newsletters as an example. Interested departments should contact cmshelp@mtu.edu to get setup. Once your site has been set up and your CMS users given access, you can follow these instructions to add future publications. Continue reading



Versions

A unique version of a page is saved through the automatic version control system every time a page is published. A backup version of a page can also be created manually with the use of the Save Version button.

All versions of the page are kept in the system until the page is deleted. There is no limit to the number of versions that are stored in the system for an individual page or across all pages in the site. If a file is moved to the Recycle Bin and then restored, versions will still be preserved.

Continue reading


Navigation

Navigation on CMS websites is located at the top of every page as tabs with dropdown lists for subnavigation links and along the left side of the content area on pages other than the homepage or where the left navigation is manually turned off. The top and left navigation will always match.

Example webpage with top and left navigation circled.

Navigation is controlled through the _nav.shtml files automatically created with a new section or additional _nav.shtml files that are created manually. New pages are automatically added to the correct navigation files depending on your choice for “Add Navigation Item” when creating them. These files must be published in order for changes to appear on the live site.

Each nav file controls the navigation for the section below it. If you are in the main root folder for a site, the _nav.shtml file will include the tab navigation links only. If you are in the first folder beneath the root folder the _nav.shtml file will have the subnavigation for the tab represented by that folder. Navigation on the live site can include one additional level beneath this subnavigation, however these links will not appear until the user goes to the parent subnavigation page. Any nav files below that level would not be used on the site. If you are in the most interior page’s folder the _nav.shtml file will only contain the page you are on.

Continue reading


Section’s Extra Left Sidebar Content

Content can be added below the left sidebar in several ways. If you only want it to be visible on a single page, use the Left Sidebar Content Editable Region on that page. To display content on multiple pages, the content will be added to a _props.pcf file. Remember, any settings made in a _props.pcf file will carry through to all files and folders within that folder. Add it to the file in the root folder to carry through to the whole site. This field is available on all _props.pcf files.

Continue reading