Customize your site-wide header and footer elements.
This information refers to the Classic version of the UBCMS.
Only those with a Specialist role in the UBCMS can edit these files.
Header and footer elements are stored in your site's special Site-Wide Configuration folder.
Each area can hold several special components, which will be listed in the Sidekick when you are viewing the header or footer page.
Please be very carefully making your changes. They will be reflected throughout your site.
You can delete any -oldbrand header or footer files left over from the 2017-18 brand transition.
Open the Header page (double-click or right click). You will now see just your site's header elements, and the Sidekick will show any applicable components.
Here you can modify the elements in your site's header to reflect your organizational identity and affilliations, as well as provide navigation links for tasking, audience and social media.
Headers can have several components, although not all will occur on every site. From top to bottom:
It is possible to create custom headers, but this step requires great care to follow UB brand and accessibility rules and you will need to get special permission for an exception to a traditional lockup.
This is for experts only, please contact the DCT Help Desk if you are considering developing your own custom header.
Google Analytics codes can be placed in an HTML Snippet on the header (or footer), or in the Page Properties of your site's home page, not in the header or footer's Page Properties.
Open the Footer page (double-click or right click). You will now see just the footer elements, and the Sidekick will show any applicable components.
Here you can modify the elements in your site's footer, including the main unit title, parent affiliation(s), as well as additional navigational links for tasking, special audiences, and your social media channels.
All of these features are housed in the Fat Footer Container.
There are several layout options, each with additional space for links and content.
Sites will have a 'simple' or 'enhanced footer,' plus an optional 'fat footer,' with the fat footer displayed on top.
The 'simple footer' holds identity and contact details, while the 'enhanced footer' holds those same identify and contact details, plus some additional elements (usually links). Pages can also have a 'fat footer' with multple columns that usually contains links and social media buttons. All are built from the same component, the Footer (formerly 'Fat Footer') Container.
Jakob Nielsen's post "Footers 101" provides a handy overview including tips and shortfalls.
Authors are responsible for any custom coding and the use of third party content that is hosted in their UBCMS pages. This includes applications such as Formstack forms that have their own UBCMS component. If you have concerns that external vendor content is not accessible, please contact Mark Greenfield.
Best practice: for Formstack forms, avoid the date picker and use of 'other' in dropdowns.
To meet accessibility requirements, every page must have an H1 Title (using the Title component).
Sometimes it is preferable for stylistic reasons not to show an H1 on a page. In such cases, a setting in Page Properties allows the Header container to serve in stead of the 'Heading 1' title, and will be visible to assistive technology.