UF colleges, departments, centers, institutes, offices, and other campus units will be able to use pre-built templates that align with the updated UF brand. The templates will be flexible, and each editor can use use/hide modules within the template that are/are not applicable to them.

Templates will be available in multiple formats, so campus units can choose whether to use Terminal Four, WordPress multisite, or HTML to build their website.

These templates will be available to colleges, departments, centers, institutes, offices, and other campus units. While the use of the templates is not mandated, their implementation is encouraged to protect the integrity of the UF brand.

Note: If the templates are implemented, each party will be responsible for the set-up, content creation / migration, launch, and maintenance of their own website.

Using the new templates is not required but strongly encouraged to retain brand continuity. The templates are also meet current accessibility standards.

Colleges or departments that do not use a CMS will still be able to leverage the base tech stack (HTML, CSS, and JS) developed for the project templates.

No – however, units may incur additional costs if they have an outside vendor implement the template for them or work on website assets such as copy, videos, images, etc.

Each college, department, center, institute, and administrative unit is responsible for installing their own template, migrating their content, setting up analytics and launching their own site.

SCM will work with the marketing agency to develop documentation that outlines:

• How the template should be installed and used
• Issues and bug fixes
• Specs for images, character limits, etc.
• Specs for each content module and how to update it

When it comes to the website builds and features, Tiers 2 and 3 are functionally the same; everyone will be able to access the same components. Tiers 2 and 3 are use cases, where Tier 2 refers to college websites and Tier 3 are websites of departments, administrative units, centers, institutes, etc.

Templates for Tier 2 & 3 will be held in a GitLab Repository, which can be accessed via the Brand Center. A GatorLink login will be needed to access the repository.

If a marketing agency/vendor is setting up the template for a UF client, the UF client is responsible for downloading the template files and documentation and sending that to the vendor.

Visit the GitLab Repository via the Brand Center to download template files and access documentation. For brand questions, please contact SCM. For technical questions, please contact UFIT Web Services.

Note: Each unit is responsible for setting up their own instance of the template – this particularly applies to those who opt to use the HTML files only or for those who opt to use WordPress in a single site instance.

If a marketing agency/vendor is setting up the template for a UF client, the UF client is responsible for downloading the template files and documentation and sending that to the vendor.

It is not encouraged to modify templates so as not to disrupt brand continuity.

Modifying the look of the templates or components with the intent of positioning them as the official UF templates or distributing them is prohibited. Templates or components cannot be modified in a way that misrepresents the UF brand identity or violates the UF Accessibility Policy. Agencies or vendors assisting any unit with setting up their official UF template are prohibited from using Copyright or Designed By [Vendor’s Name] language on the site or claiming the design as theirs in their portfolios.

It is not encouraged to modify templates so as not to disrupt brand continuity.

Modifying the look of the templates or components with the intent of positioning them as the official UF templates or distributing them is prohibited. Templates or components cannot be modified in a way that misrepresents the UF brand identity or violates the UF Accessibility Policy. Agencies or vendors assisting any unit with setting up their official UF template are prohibited from using Copyright or Designed By [Vendor’s Name] language on the site or claiming the design as theirs in their portfolios.

The self service option is for those on campus who have internal technical support from their own development staff or an agency, and who will not need ongoing support from UFIT Web Services. Self service clients will be able to have access to the Base Code Bundle (HTML, CSS and JavaScript files) and the WordPress templates for single site installation.

The UFIT hosted web content management option is for those on campus who would like to receive support from UFIT Web Services to set up their template instance. UFIT Web Services will only be supporting the TerminalFour and WordPress Multisite templates.