StudentNET Content

This paper describes how student content could be treated once removed from the external web. Its purpose is to start a discussion.

Option 1 - Full content integration into StudentNET V2

Similar to content administered by the i-zone content would be surfaced using the 'app area' in StudentNET V2.

i-zone content surfaced through StudentNET V2

The advantage of this approach is that it is in keeping with existing design and functionality.

Option 2 - Layered content integration into StudentNET V2

Following the original StudentNET vision, content would be surfaced using a conventional, layered web structure.

This layered content would be accessed through an 'A-Z app widget' from StudentNET V2. It could also be accessible through direct URLs.

E.G.: https://secure.canterbury.ac.uk/student/subject1/

The advantage with this approach is that it appears to be more scalable. It allows for more flexibility when having to cater for all CCCU's departments' needs.

Content structure

With either option the content structure needs to be carefully designed to allow for content to be reused in different areas of the web and in different media.

Content would be packaged up in logical subject sections. These subject sections may be informed by the more detailed content audit.

Content administration

With either option Contensis CMS would be used to administer content and support workflow rules.

Content rules will be important because content will be edited from staff across departments.