|
Activity...
|
Responsible Party?
|
| Determine template design. See examples from other web sites at http://itd.memphis.edu/webdev/resources/cms/lcmssites.htm |
customer
|
| Choose workflow, whether client wants to submit for approval or immediate launch |
customer
|
| Assign users and roles. User determines who will need access as site manager, content
manager or content editor |
customer
|
| AATECH creates subsite. |
customer
|
| ITD creates initial template for client. |
ITD
|
| ITD adds users for the new site. |
ITD
|
| Determine if a cname is needed. A cname is an alias or web site link. Example: gradschool.memphis.edu is a unique identifier |
AATECH & customer
|
| Register cname if needed with ITD |
AATECH
|
| Assign user roles |
AATECH
|
| Client determines menu options (left nav) |
customer
|
| Any backend programming needed like PHP or any special contents on web page |
AATECH
|
| Coordination of moving websites into LCMS, client creates page and gets ready for
LCMS |
AATECH & customer
|
| Coordinate redirection of old site to new LCMS site for go live |
AATECH
|
| Zip old site and archive |
AATECH
|