The Web Technologies team is responsible for the technical end of enterprise websites in the University System, including the myCampus intranet portal and public websites for most campuses and the University System. Our primary responsibilities include application-tier web technologies, front-end design, extending CMS themes and plugins, training site administrators, and helping business owners define their needs and determine how to meet them. We also assist as needed with web server administration, web development, and other back-end tasks.
Services We Provide
- The Liferay CMS that runs the myCampus portal, mycampus.maine.edu
- WordPress CMS websites at a one-per-campus/UMS level, specifically:
- UMA (www.uma.edu)
- UMM (machias.edu)
- UMF (www.umf.maine.edu)
- UM (umaine.edu)
- USM (usm.maine.edu)
- UMPI (www.umpi.edu)
- Maine Law (mainelaw.maine.edu)
- University of Maine System (www.maine.edu and related subdomains such as learn.maine.edu, peoplesearch.maine.edu, together.maine.edu, etc.)
- Services we don’t provide:
- Sites for individual people or courses
- Supporting or providing editing access to users other than campus site administrators
- Other content work, such as adding/modifying web content, web analytics, etc.
- For more information about these and other business side processes, see our Website Roles and Responsibilities page
Who We Are
- Tom O’Donnell (Team Lead)
- Robin McGlauflin
- David Rosen
- Zachary Sylvester
- Daniel Tyger
- Eric Brissette
How to Contact Us
The best way for anyone to reach us, even other IT departments or campus site administrators, is through Jira Service Desk. The whole team is notified by email when a ticket is escalated to us, and we internally triage to determine which of us will be best to respond. Directly contacting or assigning tickets to individual team members is more likely to slow down the process, as that person may be busy with other tasks, out on vacation, or just not the right person for the task.
We do have non-Service Desk projects in Jira, but they’re more for our own development tracking, so keeping all requests in Service Desk lets us track and respond to them more efficiently in one place.
Support or content requests from individual users or departments are usually better directed to the campus site administrators instead. If these tickets come to us, we will generally forward them to the campus site administrator.