Website Registration and Setup Requests
A process is in place to allow web developers to request a new site, register an existing site, or request a site be moved into Sitefinity, UTMB’s web content management system (Web CMS).
All the university’s web sites and the individuals that build and manage these resources are required to be registered in UTMB’s Site Inventory.
A web-based registration/site request process populates the information in the inventory. It also triggers other tasks in support of the developer and her/his program. The inventory creates a searchable list of UTMB web sites, associated contacts and developers, and technical details that support the creation and maintenance of UTMB's web infrastructure.
The Site Registration Process
The entire process begins with an online web form. The options on the form change depending on your selections; the form is divided into seven sections:
In this section you’ll select what you are interested in doing: set up a new site, register an existing site; or move a site into the new CMS.
- Site Details
This section collects essential information including site name and URL, and whether it’s internal or public. A document offers guidance on what’s being requested.
- Site Appearance
For new sites or sites moving into the CMS, this section helps the technical staff define and establish your initial site settings and look, navigation structure, and tools. A document offers guidance on what’s being requested.
- Site Ownership and Management
In this area, users define the department or area that "owns" a UTMB web site, and the people in those areas requesting and/or ultimately responsible for the site. A site owner may be a program director, departmental chair, area manager, VP, etc. She/he may or may not have any hands-on management of the pages in a site.
- Site Builders
These fields ensure that access to a site is enabled (and enabled at the appropriate level). Builders of a site are broken into three primary roles:
- Content author: The content author is in charge of the day-to-day edits the site needs to stay fresh. This is the primary and most common level of access. Every site needs someone designated as a content author.
- Developer: In our use of Sitefinity, a developer is an advanced role, a programmer function for someone who will be developing, testing and implementing code, and building special custom applications for sites. This is an optional role; we anticipate the built-in capabilities and templates of the CMS will meet or exceed most applications.
- Content Approval & Workflow
We plan to enable site builders to create workflows that will route page updates and changes to editors for approval. An editor can be a manager, colleague, the site owner or anyone designated by a department. The workflow process is optional and is not required.
- Comments or Special Instruction
A “catch all” for any other information not already part of the standard form. Have a URL that needs to be redirected? A blog? Special content you are concerned about? This is where you’ll mention it.
Requests made via the form are registered with the Internet Technology Committee and ultimately go to the same web services team in Information Services that has supported web hosting and server management in the past.
The information captured in the form also triggers the scheduled review for each web site, an annual (at the minimum) requirement beginning in 2016.
Did you know?
A similar registration requirement is being made for owners of UTMB-associated social media sites. The information collected there will be merged into UTMB’s Site Inventory.