³Ô¹ÏºÚÁÏ

³Ô¹ÏºÚÁÏ websites should be developed to operate within ³Ô¹ÏºÚÁÏ's visual standards, templates and infrastructure and using standard applications. This includes sites created within the t4 content management system and use of other standard ³Ô¹ÏºÚÁÏ-wide applications such as ³Ô¹ÏºÚÁÏ Profiles.

There are sometimes situations where these standard applications may not be appropriate, for instance a collaborative initiative requiring non-³Ô¹ÏºÚÁÏ branding and a non-³Ô¹ÏºÚÁÏ URL, or a custom application key to the research activities of a unit. In such instances alternative hosting solutions can be requested via ICT.

Non-standard hosting 

It may not always be appropriate to use standard ³Ô¹ÏºÚÁÏ-wide applications. Typical reasons for this include: 

• requirement to use non-³Ô¹ÏºÚÁÏ URLs 
• hosting web servers outside the ³Ô¹ÏºÚÁÏ web server farm 
• divergence from the standard ³Ô¹ÏºÚÁÏ web page templates due to a branding requirement 
• technical requirements cannot be met by use of standard applications 
• catering for interactive and transactional sites, specifically where persistent connections are required.

Applying for a non-standard website, domain, URL or hosting space 

In order to cater for these  hosting requests the following process has been implemented: 

1. The originator of the request needs to document the rationale in the online website domain and hosting request form on ASK.  By completing this form the Web Officer for the Faculty (FWO) or organisational unit will be asked to approve it.  
2. If approved by the Faculty Web Officer, the exception request will be submitted to the relevant team in ICT to process the application. If additional information is required this will be requested from the Faculty Web Officers or ICT. The requester will be notified of progress.   

Note: Because technologies change, the rationales for non-standard hosting will also change over time.  Therefore there will be a review period for each request to decide whether the requirement still stands. This includes the use of shorter or vanity URLs.

Criteria which may justify an exception

Read the following for further information on the reasons where deviation from the ³Ô¹ÏºÚÁÏ’s visual standards, templates and infrastructure is appropriate: 

Exception to URL policy - the URL is not within the imperial.ac.uk domain 

• A research or collaborative project or association, where ³Ô¹ÏºÚÁÏ members collaborate with other universities or academics from other institutions. 
• A ³Ô¹ÏºÚÁÏ spin-off, or licensed sub-brand 
• A ³Ô¹ÏºÚÁÏ commercial venture (eg. ³Ô¹ÏºÚÁÏshop) 

Where a site is an exception to the URL policy but is hosted on ³Ô¹ÏºÚÁÏ web servers, then ³Ô¹ÏºÚÁÏ web content management policies apply. 

Exception to URL policy - the URL is within the imperial.ac.uk domain. 

• The urls of websites stored and managed within the ³Ô¹ÏºÚÁÏ Content Management System are of the format www.imperial.ac.uk/sitename with suffix qualifiers added for each level within the site. Sometimes, a shortcut may be desired for easy access to information which is stored at a low level within the website. Each such request must be supported by the Faculty Web Officer and will be evaluated on its own merits. 
• Subdomains of the imperial.ac.uk domain i.e. subdomain-name.imperial.ac.uk. Please refer to the  Policy for subdomain requests for imperial.ac.uk before requesting an imperial.ac.uk subdomain. 

Exception to the use of ³Ô¹ÏºÚÁÏ branded templates 

Normally, sites which qualify for URL exception under the first bullet point above, will also be exempt from the requirement to be presented in ³Ô¹ÏºÚÁÏ branded templates. However, in the majority of cases, they will carry the ³Ô¹ÏºÚÁÏ ³Ô¹ÏºÚÁÏ logo to recognise that the site has an association with ³Ô¹ÏºÚÁÏ ³Ô¹ÏºÚÁÏ London. The correct format artwork for the logo will be provided by the Communications Division once they have approved its use. 

Exception to hosting of the website or server on the central ³Ô¹ÏºÚÁÏ web server farm

• A web server may qualify for registration outside the ³Ô¹ÏºÚÁÏ central web hosting environment if: 
• The site is commercial in its operation and hosting it on a JANET connected server would breach UKERNA conditions of use 
• The website is developed as part of the core business processes of a unit 
• The system is a 'sandbox' learning or experimental environment 
• Technology constraints limit the ability of the site to be compliant, eg: 
• incompatibility with ³Ô¹ÏºÚÁÏ standard software or hardware 
• the application requires persistent connections, either technical or in terms of usability. 

Where an exception is approved, then a 'system custodian' must be appointed who will ensure compliance with ³Ô¹ÏºÚÁÏ's Information Systems Security Policy. 

General exception criteria

• Time criticality - the site needs to be implemented by a deadline, eg. the start of a new academic year, and cannot be made compliant by that date 
• Resource prohibition- the cost or effort required to make the site compliant would outweigh the business benefits, thereby destroying the business case for the initiative. 

Examples of some common requests for exception to web policy 

• Assignment of a shortcut or level 1 url in the imperial.ac.uk domain. 
• A non-branded website for a collaborative project, hosted on ³Ô¹ÏºÚÁÏ webfarm servers (Windows or LINUX). 
• A non-branded website for a collaborative project, to be hosted on the project's own hardware, managed in the ICT datacentre. 
• A non-branded website to be hosted on departmental hardware. 
• Access is required, via the ³Ô¹ÏºÚÁÏ firewall to a departmentally hosted site. 
• A hostname is required in the imperial.ac.uk domain for an application (custom built or package based). 

Apply for domain and/or hosting 

Providing you have read and understand the details above, you can .