Select Page

Personal Website

Your choices for creating a website at UCLA include, but not limited to, the following:

For Faculty Research/Lab Sites Only

Google Sites at g.ucla.edu

Eligibilities: UCLA employees, students, departments, student groups/organizations, alumni, and retirees

Pro: free

Cons:

  1. Not flexible and very limited in design
  2. Custom URLs are not supported for sites hosted at g.ucla.edu

Instructions:

  1. Activate your g.ucla.edu Google account at https://g.ucla.edu (if you’ve not done it already). A new faculty whose appointment has not begun will need his/her department to email help@it.ucla.edu.
  2. Sign to mail.g.ucla.edu with your UCLA Logon ID.
  3. Follow the instruction at https://gsuite.google.com/learning-center/products/sites/get-started

Notes:

GitHub Pages at github.com

Eligibilities: Anyone
Pro: free
Con: familiarity with HTML

Instructions:

  1. See https://pages.github.com
  •  

WordPress using Amazon Lightsail

WordPress using cPanel

Eligibilities: Valid UCLA’s FAU or CoA recharge account
Cost (subject to change): $29.75/month

Instructions:

  1. See https://ucla.service-now.com/support?id=its_browse_service&sys_id=bc62ef341b9c885038cec8415b4bcbab

Notes:

  • You need to be within UCLA network to logon to CPanel’s admin console with the admin account provisioned to you.
  • You are responsible for keeping WordPress/Drupal, Apache, MySQL/PostgreSQL, and etc. up-to-date with security updates.
  • You are responsible for responding to UCLA IT Security should any security vulnerability is discovered.
  • Although IT support is not included, there are some fee-based support available:

Drupal using full-service hosting

Eligibilities: Valid UCLA’s FAU or CoA recharge account
Cost (subject to change): $288.42/month (for 10k daily page view site), $250.00/month (optional 5 hours of consulting)

Instructions:

  1. See https://www.it.ucla.edu/services/web-development-hosting/web-cms

Notes:

  • As of April 2019, the version of Drupal is 7, with version 8 coming soon.
  • You will be provided with the default UCLA template for your Drupal site. Customization may be possible at additional cost.
  • Non-core Drupal module request is not supported (due to complexity in upgrades).
  • Content updates can be delegated UCLA IT Services with additional cost. Also, content update approval workflow setup can be requested.
  • UCLA IT Services is responsible for security updates.
  • Some examples of UCLA sites using this service: tickets.ucla.edu, it.ucla.edu