There are four types of pages in Sitefinity. Top level pages and child pages are standard options and are used to decipher page location. Group pages and redirect pages are used as placeholders in the navigation to divert site visitors to content on other pages. Standard top level or child pages can be converted to group and redirect pages by site builders in the page properties.
They are also known as parent pages. These pages should be created first. Top level pages usually consist of the homepage and the pages that are listed in the top navigation.
Navigation and all page properties should be set on these pages. These settings will be inherited properly by child pages.
These pages automatically inherit properties from the parent page unless otherwise specified in their page properties. If you break inheritance, the new properties trickle down to any new page built under it.
These pages are mainly used for site organization. These pages have no content of their own so there is no landing page when site visitors click on them.
Users can think of these pages essentially as folders to group pages with similar content. Again, there is no content on a “group page”. Content only exist on pages that are in the “group” or folder. For this reason,
when site visitors click on group pages, they are directed to the first subpage that exists in the group.
These pages also have no content of their own so there is no landing page. When clicked, these pages will redirect site visitors to another page immediately. Pages can be internal to the site or external.
Certain sections within page properties inherits all its properties to child pages. These sections only need be setup on top level pages but can be setup on a specific child page in needed. Below are the properties you'll find in this area and how to use them.
Navigation is like a table of content for the website. Navigation can live at the top or side of every page, as well as the bottom of every page, which is called a footer. Navigation offers the user a list of all the sections within a website. Learn more about navigation.
For increases user experience and accessibility, a back to top button will be automatically applied to all pages longer than four screens and will hover on the bottom right of user’s screens. This is turned on by default. It is our recommendation that every page has this option. You can uncheck it if you need to disable the function.
The local footer is located right above the global footer, which is the same university wide. The local footer is customizable for site builders. It can consist of a parent breadcrumb, a physical address, social media icons, and up to four columns of helpful links for site visitors. Learn more about local footers.
Site builders can select their homepage breadcrumb here which will allow users to click back to the homepage from the local footer. To use this feature:
Site builders can select their address here and should submit a ticket if the information is not here or correct. This information is displayed in the local footer. To use this feature:
Social media icons can be displayed in the local footer. This is a reusable content type and should only need to be created once. User can create the content type in this area by hitting select and “Create a new item”. They can also create it in the content tab area on the dashboard. This content type can be maintained/edited in both places. To use this feature:
Please note: you only have to create this group one time as it is reusable content. Site builders can reuse the same item on all other pages.
This is also a reusable content type. Link groups can be created here as well as in the content tab on the dashboard in the same way as the social media icons. There can be up to four columns.
NOTE: You can select the groups (link groups) you’ve already created at this time. If you choose not to create link groups in the content area first, you can create them at this time. This will allow you to create the groups only; users cannot add links here. This is more of a place holder. The groups created can be maintained and links can be added in the “Content” area in the dashboard. This is helpful if the users would like to setup their page footer properly but are unsure of the specific links at that time. They can setup the appropriate groups and maintain the links in the dashboard without the added stress of going into individual pages to make changes once they have the links figured out.
To use setup the groups in your page properties:
Please note: you only have to create these groups one time as it is reusable content. Site builders can reuse the same item on all other pages.
Later when you are ready to add additional links to your Link groups. You will be able to do so in the Content area of the dashboard.
This is usually the name of the department, division or website. Logos are no longer accepted in the top of webpages so this is a good way for site builders to let their audience know what site they are looking at. This name is inherited to all child pages unless specifically changed on a webpage’s properties.
Builders have the option to make the website name clickable to their site’s homepage. To use this feature:
If nothing is selected, the website name is not clickable. Again, this is inherited throughout child pages and should be completed on all top level pages.
A second line can be displayed below the website/unit name to show hierarchy or an approved partnership. This text is limited to a single parent unit or partner affiliation. This is also inherited. No taglines, promotional copy or other text may be used.
This allows site visitors to click to a parent unit’s homepage. To use this feature, insert your parent unit's URL in this area. If nothing inserted, the website name is not clickable. This is inherited throughout child pages.
Examples with images below: Center for Midwifery, second line College of Nursing; Accounting Services, second line Finance Office.
This option allows site builders to display pertinent information to site visitors across the top of webpages. You can find additional details, an example and instructions here: https://www.ucdenver.edu/atweb/learnsitefinity/widgets/sitewide-banner.
Builders should select all appropriate campus tags.
Site builders have the option to include an action button in the local header area, which will display on the far right. To utilize this feature:
The header CTA button inherit downwards, so if a Header CTA button is set on a top level page, any child pages will also display the button, unless selected otherwise on specific pages.
The header CTA button is visible at the top of a page on desktop screen sizes. On mobile screen sizes, it will be combined with certain top navigation templates. Desktop example is below.
This is the university logo chosen to meet brand standards. It is assigned base on campus affiliation. There is no logo currently for CU Anschutz or Dual units. CU Denver’s logo is “CU in the City”. Site builders cannot change this.
This is usually Webmail, UCDAccess and Canvas. This cannot be changed by site builders but they can request this to be changed based on their audience needs via Cherwell ticket.
The global header links appear in the top right-hand corner of university sites next to quick links and search. By default these links focus on internal audiences but you have the option to request that these links be customized specifically for your site's audience. Send an email to firstname.lastname@example.org to make a request to change your site’s global header links in Sitefinity.
Desktop view shown below and mobile view is to the right. Click on the images to expand.
Enter in a sentence to describe the type of content present on the page. It should be 150 characters or less.
Enter in words related to the content of the page. Separate keywords with a comma and space. It should be 450 characters or less.
These descriptions and keywords are duplicates. Please use the "Description" and "Keywords" section at the top only
All domains and subdomains will receive their own analytics properties and Google Tag Manager event tracking. Site Builders should add the proper Google Tag Manager container ID to all top level pages in page properties using the “Google Tag Manager container id” field. This can be accessed through the “Title & Properties” on any page. If the value is left blank, analytics will be tracked by the default CU Denver container.
This option allows site builders to preselect information that they would like to display when someone shares the page on social media. To use this feature, fill in the applicable fields.
Builders will not have access to this section in page properties. You should work with Web Services to find solutions for their website needs instead of trying custom solutions. If you a looking for new functionality submit a feature request.