In January 2018, we will be starting the transition of moving from the old templates to the new templates for all sites on www.wku.edu. For most sites, this will be an easy transition; however, if you have a lot of snippets or custom development, the transition could be a little more time consuming. Other than the fantastic new look and feel of these templates, we have tried to address ease of use and template flexibility with new features. Below is a brief list of those new features.
The hero image is the large image above the content on the Funny Monkeys homepage. This is unique per page and can be added through each page's properties.
All sites have top navigation enabled, and it cannot be disabled. There is just one top navigation file (_topnav.pcf) per site, to promote a consistant navigation throughout the site and WKU's website as a whole. Seprate top navigations per nested folder is no longer supported.
Side navigation can be enabled on either the left column, or right coulmn of a page, and its content is controled via the _sidenav.pcf file. Side navigation can be enabled or disabled per page, through each page's properties. By default, the _sidenav.pcf file at the root of your site is used, however, multiple side navigation files per site are supported, meaning you can have unique side navigation content on pages grouped under the same folder.
When enabling side navigation for a page, you must also enable the appropriate side column, depending on your chosen settings.
Page footer content can be added and enabled per page, controlled via the _footer.pcf file. Footer content inclusion can be enabled or disabled per page, through each page's properties. By default, the _footer.pcf file at the root of your site is used, however, multiple footer files per site are supported, meaning you can have unique footer content on pages grouped under the same folder.
Sliders (i.e., carousel styled image galleries) can be added to the top of each page, just above the page's title and content. Page sliders can be enabled or disabled per page, through each page's properties. In junction with enabling the page slider in the page properties, an image gallery asset must also be created and then added to the page using the WYSIWYG's edit view.
Additionally, image galleries are supported anywhere the asset can be added to your pages. Checkout the gallery examples on our Funny Monkeys site for more information.
Notifcation messages can be added globally, across all pages of your site. This is useful when conveying a message to people regardless of what page they are on. Notification messages are controled via the _notification.pcf file at the root of your site; multiple _notifcation.pcf files per site are not supported. The alert level for the message, as well as its enabled or disabled state, are both controlled via its page properties; the content of the message is editable via the WYSIWYG.
For more information on the different alert levels, or if a page specific message is needed, take a look at the Alert Snippet page on our Funny Monkeys site.
Snippets are inserted into the page using the WYSIWYG Editor and become a part of the page. They provide an easier, standardized way to insert design and content elements. Snippets give users without HTML experience the ability to create more complex elements. For more information on the snippets available, check out the Snipptes page on our Funny Monkeys site.
Most of the time, adding content to a page is fairly simple and straightforward, utilizing snippets or other tools that have been made available. There are, however, a few cases where a little more is involved to make things look the way you want them. For example, while adding responsive tables or creating buttons as a call to action are easier than before, the process is still a little more involved than normal - hence the "advanced edits" classification. To see more on the available advanced edits and features available, checkout the Advance Edits page on our Funny Monkeys site.
The available snippets have under gone some major overhauls to make them more flexible and offer new features; some of the less commonly used features have been removed. For these reasons, existing snippets are not included included in the page transformations to the new template styles; they will need to be manually migrated to the snippets available under the new page templates.
Breadcrumbs have been drastically overhauled to make them consistantly easier to use and edit. Because of this, content from the old breadcrumb.inc file will need to be manually recreated in the new page templates' _breadcrumb.pcf file.
The new _breadcrumb.pcf file is now maintained as a list of links. When published, formatting, such as link/breadcrumb separators are added automatically for you, as well as a root breadcrumb link back to WKU's homepage.
Multiple breadcrumb files per site are still supported under nested folders.
The slider.pcf file is no longer used in the new templates. To add a slider gallery to your page, you must now create an image gallery asset and add it to your page. This allows different and unique slider galleries to be added per page, instead of per folder as was the case under the old templates.
Checkout Sliders under the New Features section of this page for more information.
After migration any galleries on your site will need to be modified slightly. Under gallery options there is an advanced edit section that will need extra settings to determine gallery style, number of columns, and thumbnail style. It is also likely that you will need to resize your images and thumbnails. About Galleries
Sites using the new page templates, or sites that have been migrated to use the new page templates, will no longer use different access roles (Content Coordinator and Site Manager). All users that have access to the site in OU Campus will have the same access level.
Each site will still require a Main Site Contact (MSC) be associated to it. The MSC is the person considered to be in charge of the site, he/she is responsible for administrative requests regarding the site, such as adding/removing users from the site access lists; they are the person IT and Web Services will contact with any questions, should anything come up.
After a site has been migrated to the new page templates, before it has been published to production, updating your live site in production will become more difficult.
In order to make changes and keep the old page templates, you will have to revert the applicable page to a version prior to the migration. You should then be able to make the desired changes, save, and publish the page. Once done, the edited page will need to be reverted again, to a version created after it was migrated to the new templates. Do not publish.
If you have made any changes to your pages after they have been migrated to the new templates, you may want to save a version of those unpublished changes before performing the intial revert; otherwise those changes will be lost during this process.
Additionally, any changes made to the old template version of a page, will not be carried forward when reverting back to the migrated version of the page; those changes will need to be duplicated after the page has been reverted back to its initial migrated page template state.
Because of these complexities, we strongly suggest that you take the time to migrate your site as quickly as possible - fixing layout descrepencies, etc. Once you are ready to go live with the new page templates, let IT know, and they will publish the site all at once and finalize the migration process (cleanup legacy files, etc.).
Under the old page templates you had the ability to request a header.txt file be added to your site, so that content could be included between the <head> tags of the page. While this is still available under the new templates, the naming has been changed from header.txt to _header.inc, and you no longer have to request this feature to be enabled for your site. By default, if a _header.inc file exists at the root of your site, it will be included on all your site's pages.