When your site is ready to go-live

Once you have finished building your site and you are ready to go live, use the following checklist to ensure that your site will look and behave as well on other people’s devices and browsers as it does on yours. 

Test Your Site

This is a very important step that should always be done prior to going live with your site. While YaleSites Templates are tested to work on most modern browsers and devices (see list below) if you have made style changes to the template with CSS injector or have a custom theme, you should check the browsers and devices.

a) Browser/Device Compatibility Requirements

The following list represents the platforms and devices that should be supported by all websites built on the YaleSites platform. Effective: 9/30/14

Internet Explorer




Desktop/Laptop Computers

MAC OS X 10.8, 10.9




Windows 7, 8.1

8, 11



Phones/Tablet Devices

iPad/iPhone iOS 6, 7

Mobile Safari

Windows Phone 8.0 - i.e. HTC

Latest version

Android – i.e. Samsung S5


b) Check Permissions

In addition, if you have enabled Modules that adjust or allow permissions to functionality for specific groups or roles, you should be sure to test the access by assigning the role to a fellow staff member and having them login to the site and access the content you have available only for that role. Make sure to check that they ONLY have access to the functionality you want!

c) Check Links

Make sure you do not add links with “dev” in the URL

When you are creating links to pages within your site, use the Internal Path feature found in the link tool of your WYSIWYG toolbar. The problem occurs when links pointed to pages within the site used absolute links including dev. as part of the URL (http://dev.yoursitename.yale.edu/pagename). Otherwise, when the site goes live, the links open the dev version of the site. The Internal Path feature also prevents broken links if the name of the page is changed (hence, changing the URL).


Making your site available to the public

Your site it is not available to the public either because it is in the development environment (dev) or it is in maintenance mode in the production environment. The following instructions will help you to get your site ready for the public to see.

  • If your site is in Production - If your site is in Production and the URL is the one you want when the site is available to the public (yoursite.yale.edu), just disable Maintenance Mode and your site is live.

  • If your site is in Development (dev) - Your site is in development if there is a dev in the URL (yoursite-dev.yale.edu D6 or dev.yoursite.yale.edu D7). 

    • ​Complete the Go-Live request form to request your site is moved to the production (“live”) environment. These deployments happen on Tuesday and Thursday evenings*.

    • Transition URLs - Please indicate that you want to maintain the same URL as the dev instance OR if you want a new URL when you complete the Go-Live request form. Complete the Redirect fields to redirect the old URL to the new URL - yale.edu/yoursitename to yoursitename.yale.edu.

  • Websites migrated to cloud work on weekly schedule, please refer to YaleSites Cloud Q/A.

Deployment Schedule*

Request is made
Ticket is created
(YaleSites Team)
Site is provisioned
Site is available
By Monday afternoon Tuesday morning Tuesday evening Wednesday morning
By Wednesday afternoon Thursday morning Thursday evening Friday morning