While waiting for a decision on the delivery approach (and maybe to inform this, if not yet decided) I have started mapping out the chunks of work, key questions and noting critical path (or high importance areas).
Amusing that CSP proceeds as core data, this component of the (current) Faculty and School HLS area can be though of as only loosely coupled to the rest of the F&S work, which in turn can be though of as comprising activity in the following areas:
- High level IA and site structure: Changing this is always easier before a major project rather than during or after. As such we urgently need direction or answers in this area. I think it sits with Nathan (and 'Tash for a few more days) to advance but I can not see a delivery date for a new IA. I am encouraged by the feedback of workshop participants with the direction of "audiences and their needs first", a pillar of how we think about the website and how we approach our work (but the devil might yet be in the detail).
- Lower level site structure and content plans: Well advanced by Anne, but potentially requiring rework depending on the high level IA work. Needs socialising with stakeholders, as it is currently a straw man or proposal. Workshops to date indicate an acceptance from half the faculties and a willingness to discuss from the others (but please do not mistake this for an agreement or willingness to implement). I suggest we have follow-up conversations with an faculty that does not seem onside with the "folding of school sites into the faculty site", meaning VBS and Science so far.
- Navigation: From simple (page sections, hyper-links, etc) to more complex (contextual search widgets). Can we identify some more complex ones early, with sufficient knowledge of their importance that work can start on them now?
- Functionality: I am thinking about this category (as tagged by Sam in Reframer for workshop observations) in terms of:
- Engagement: The more simple, one-way functionality that allows the user to do stuff he/she wants with our content. Client-side, not restricted (much) by Squiz, generic/modular (in that it could be placed on any/all pages as required). Examples include share, print, book mark, download, etc. Can we identify some more complex ones early, with sufficient knowledge of their importance that work can start on them now?; and
- Online Services: More complex, two-way, transaction-based functionality that allows the University to deliver a service to an audience online. Examples include buy, ask a question, subscribe, rate, register, change my details, etc. Can we identify some more complex ones early, with sufficient knowledge of their importance that work can start on them now?