...
- This approach won't work where we are making changes to structure
- Engineering Faculty and School is being merged
- Education Faculty and School is being merged
- NZSM is on a very distinct site - do we include this in the project at all. Originally it wasn't part of the project as the school was staying independent.
- New content will be being developed at the same time the templates are being built. We need to decide how and when to approach integrating the new content - before, during or after migration
How it would work
...
| Month | Development | Loading and Migration | Content |
|---|---|---|---|
| January | UG Topics and programme - develop front end and build template | n/a | UG Topics and programmes content development |
| February | UG T&P content loading | ||
| March | UG Topics and programmes - finalise back-end | PG Topics and programmes content development | |
| April | PG Topics and programmes - design and build template(s) | ||
| May | PG T&P content loading | Faculty & Schools content | |
| June | Staff profiles design and build | ||
| July | Staff profiles migration | ||
| August | Faculty and School templates including homepages, news and events functionality | n/a | |
| September | F&S content migration | ||
| October | Post-graduate hub and/or continuous improvement. | F&S content loading | |
| November | Postgrad hub or continue with F&S content | ||
| December |