| Item | Who | To discuss | Notes |
|---|
| Sprint planning | Jane | Sprint planning | |
| Content mangement system | Andrew | Discuss as the team next steps for a content management system Links for Andrew: https://victoria.gathercontent.com/item/2420053 https://gathercontent.com/developers/items/get-items/ WIP-756 | - Andrew took us through the extra coding that would be needed in order for content to be loaded automatically. Feedback:
- the approach will be hard for SMEs to understand
- headings won't be formatted which takes away from the advantage of using Gather Content.
- each different block of content needs the code and this could make for very rigid templates which are hard to follow
- adding the code after SME sign off would be time consuming and could lead to hard to spot errors with heading wording etc.
- If we go for the new delivery approach there won't be as much content loading as quite a bit of the content will be migrated.
|
| New dev approach to F&S | Jane | Work in a different way to get F&S sites | - Will need a different approach for the two newly merged sites - Engineering and Education
- By the time the templates are ready there will be some new content so this may affect how clean the migration process is
- I have put notes from my meeting on the following page under delivery approach
Faculty & School Sites: New Design before New Content - Next steps:
- how many different templates/patterns will need to cover current content
- what can we do to reduce content ahead of migration e.g. ask schools and faculties to review, get solution underway for FHSS course outlines etc.
- all pages will need to be checked post migration - could this be done by students? could we involve the Faculties and Schools themselves?
|
| RAID log | Jane | WIP II RAID - review of risks, actions, issues and decisions | |
| Blockers | All | team to raise any blockers not already covered from RAID review | |
| WIPII Wish List | Jane | WIP II Wish List - review of wish list | |
