The Web Communications team must approve all website changes before they go live. This is to ensure consistency across all pages, reduce the amount of typos and make sure the pages are correctly formatted and linked.
Tasks generally go live within 24 to 48 hours after they have been received by the Web Communications team. Occasionally, a task may take longer if it has issues that need to be resolved or if it is complicated (ie: many new pages that need to be added to the navigation). If you need an urgent approval please see below.
Sometimes, Web Communications approvers may have to reject tasks if there is missing information, information that belongs on another site or if the page is formatted incorrectly.
If you want to be notified when your task has been approved, please indicate so in your task notifications and or send an email requesting to be notified to firstname.lastname@example.org.
In the case of a major error on a page or time-sensitive material, please follow-up with an email or phone call to the web content staff at email@example.com or by calling 978-934-3875. It is the responsibility of the department editor to submit tasks allowing for adequate time for the task to be approved before the content goes live.
An alias automatically brings users to the right place in a website by typing a shortened URL (www.uml.edu/anyname) instead of the full URL path. Aliases can be set up for sites at the discretion of Web Services in collaboration with Information Technology.
Recommended uses for aliases are in print publications or advertising.
Aliases should be intuitive and follow the traditional format, www.uml.edu/anyname/. Web Services staff can help you determine the best alias for your project. Please alert Web Services prior to referencing an alias in print materials or advertising to ensure that the alias is working and doesn't already point to a different location.
To request an alias for a site, email firstname.lastname@example.org or call 978-934-3875 or on campus: 4-3875.
Web Services does not recommend subdomains (anyname.uml.edu). To maintain a clear presence in print publications and maximize search engine results, Web Services recommends using aliases. Best practices indicate that subdomains provide no benefit from a marketing perspective, require more work on the back-end to make them functional and have the potential to dilute search engine rankings. Additionally, using both subdomains and aliases is confusing to users as they navigate throughout the UMass Lowell website.