Content areas for delivery (draft)

Proposed order/priority	Project phase	Content area	Current location(s) Where it currently lives on the web channel, stating multiple locations if they exist	Proposed new location(s) Note if its a central source, but also if we have plans to pull into other areas on the site	Delivery approach Document how we move from its current location to the new one. e.g. current content removed, new content goes live etc.	Implications e.g. would have to create redirects in....	Dependencies e.g. would want to release topics and programmes together courses	Risks Any risks e.g. identifying where current content is linked across the site is an obvious one to me that would probably impact most things. We may want to document that on the risk register
1	Phase 2	Topics (and associated subjects)	Subjects exist on faculty sites, school sites, Future Students and Victoria International (VI). They are likely to be the same page/content, with "one asset ID". .	Future Students (until renamed Study at Victoria). Will pull through the VI	Either 'Remove' subject pages from school/faculty sites when topic pages go live; or 'Move' the asset for subject pages from school/faculty sites to VI and then 'remove' subject pages from school/faculty sites when topic pages go live; or (Is there an option to publish new topic and programme pages but leave the old ones (on at least some sites) live until all topic-programmes are up and then turn off all the old ones?)	Remap Future Students and VI to the new topic pages in the same "batches" as we plan to use for go-live on Future Students; or Work in moving old content to a new location, but it would allow us to bundle up all the batches on Future Students to one release for Victoria International.	Enabling new topic pages with the matching UG programme page seems to be the most sensible approach, in that it delivers returns early, minimises the risk of a big go-live and allows us to learn and tailor our approach as we go Subjects that are PG only could be mapped to existing programme pages, until we are able to rewrite them.	(No matter how much we try) We will fail to identify all the links that we break when turning old pages off. So long as we fix them promptly when we find them (ideally via a pro-active tool search but at least when reported) it should be okay. Reputation/image during the transition period: Some subjects are covered by new topic pages while others are still on old subject pages. Faculties willingness to have the new-old version split live at the same time. Easier to manage when a faculty has a tight offering but difficult for the broad ones.
2	Phase 2	Undergraduate degree pages	UG degrees exist on faculty sites, school sites, Future Students and VI. They are likely to be the same page/content, with "one asset ID".	Future Students (until renamed Study at Victoria). Will pull through the VI.	'Remove' UG programme pages when new UG degree pages go live, which in turn is best linked to then the feeder topic pages go live (see row 1 above)	See above	See above Further, it is unlikely that we can "remove" old subject pages until we have enabled the new programme pages, as the subject page currently has the appropriate major rules. So, our rewrite of the programme page is not only to "refresh" the content but also to integrate all the major rules that are currently on the subject pages but will not make it through to the new topic pages. Ideally, all courses would have outlines published via COO. We should map to the course finder result, even knowing that it is only a subset of attributes available on an outline.
3
4
5
6
7
8
9