Adjust settings that influence how the page is displayed or used within the UBCMS. In most cases, the changes are immediate.
Last reviewed: September 22, 2021
Please be careful when adjusting these settings. Some changes may have unexpected results, including affecting pages on other sites.
Properties has seven tabs: Basic, Advanced, Scheduling, Image, Background, Stewardship and Social.
These settings can be accessed while editing a page in the Edit Console (click the Equalizer icon then select Open Properties), or from the Sites Console (select the page then click Properties in the Command Menu).
This tab controls the main settings for the page. The Title should reflect what you entered when you created the page. You can then make additional adjustments as noted below, although no further changes are required.
When viewed in the browser tab, search results, or bookmarks, UBCMS page titles will always end with ' - University at Buffalo'.
This area allows modification of additional settings and is mostly intended for developers.
Please be careful with these options. Some, such as Vanity URL, can impact other websites if not set carefully.
Without extra provisions such as server-level redirects, the Alias setting will cause every page under it to have two URLs. This can be bad for SEO and can greatly complicate Google analytics.
Jumbo Top Nav settings only work when Jumbo Top Navigation is turned on in the site header's Top Navigation component, and only if this page has child pages.
> Read more about Jumbo Top Navigation.
No one is permitted to set a Vanity URL outside their own site. For authorization, contact us.
Analytics codes should be placed in your site's home page Properties, where they will then apply to your entire site. As an alternative, they can instead be placed in your site's header or footer (in an HTML Snippet), but this is less recommended and more likely to cause confusion later.
Please be careful with Google Analytics. Adding a second GTM code to your site may result in duplicate form submissions or reCAPTCHA errors.
A Flush Trigger is used to ensure the Emergency Alert Banner component displays simultaneously on all applicable sites.
In effect, these make https:// required to navigate your site, but the UBCMS does not ensure your site will function properly in https:// mode. You could brake your site using this setting. > Learn more about requiring https
To use the Require SSL setting, the site must be covered by a SSL certificate. Everything under www.buffalo.edu (/content/www) is covered but not all other virtual hosts on the UBCMS have a certificate.
This option is only available to those with Publisher permissions. For others, it will be grayed out.
Using these settings, Publishers can control when content displays in a list, and schedule page activation and deactivation (compare to Publish/Unpublish Later).
If either of the On/Off times is in the past, you must activate the page to push the modifications over to the live site.
Images changes are saved immediately, regardless of whether you choose 'OK' or 'Cancel' for the dialog box.
Alt Text is generally required under state and federal accessibility laws. Read more about Alternative Text.
This is an experimental Flex UI feature which will be made available to all users Fall 2021
Adjust these optional settings to guide future authors in maintaining this page. These details will be visible in Page Reports.
When UBCMS pages are shared to social media, the resulting post pulls the page's title, descriptive text plus an image. These will be pulled from the current page but can be set specially in the Properties Social tab. The image is defined by the 'Social image from' setting.
If the 'Social image from' setting is not defined for the current page, the social image is determined using the Selection Rules below. (Regular pages and Shared Content are treated slightly differently.)
* Alt text is required by New York State policy for most images and is always required if the image has a link or if the zoom feature is enabled, otherwise a caption can serve instead. See webaim.org for tips on writing alt text. A period and space are added to the end of any text that does not already end with punctuation (not visible in the dialog box) to increase clarity when a screen reader reads the page. Adding just blanks or a carriage return will be blocked.
To meet accessibility requirements, every page must have an H1 heading (e.g. using the Title component).
Sometimes it is preferable for stylistic reasons not to show the main heading, especially on a home page. In such cases, a Properties setting allows the Header container to instead supply the 'Heading 1' title, and be visible to assistive technology such as screen readers.
Best practice: only a developer should modify the standard UBCMS code or styling, and any adjustments should be made thoughtfully, with regard for accessibility and long term maintenance.
Alternative text ('Alt text') is a best practice for all your UBCMS images and is often required for accessibility so screen readers can tell visually disabled users what they are not seeing.
Purely decorative images can be flagged "This image does not require Alt text" (when available), which nullifies any Alt text that was already entered, and some components (e.g. Photo) supports a nested Caption which can serve in place of Alt text, with these exceptions:
Alt text can also be added to images in Assets. This is required for images that are then used in the Photo Gallery, while it can also be used as an alternate source for Alt text in some components (e.g. the Photo setting 'Get Alt text from Assets').
Best practice, Alt text should be added whenever an image is uploaded into Assets.