2015-10-23 Dev Planning Meeting notes

• Jane Young (Unlicensed) to confirm that topics and programmes is signed off 30 Oct 2015 

• Andrew Bredenkamp to record in Confluence why we are not recommending that Squiz is used for building the topic or programme pages

Disadvantages of Squiz

• testing suggests that the final solution will be brittle
• to get it to work we are effectively creating a unique solution which could be complex to maintain.

Advantages of third party system

• can choose a solution which fits the problem
• could be used as a way of trialling a new system
• potentially the new system could also be used for COO.

Disadvantages of third party system

• another system to be learnt and maintained by core web team - the core team will be managing the topic pages.
• if web publishers in the faculties are maintaining programme pages this would mean them learning a new system.
• potentially delays in getting approach approved

Nathan would like the designs to be coded directly into the system rather than being first developed in photoshop. He feels overall this will reduce

Joe feels this would stifle the design process as it would be slower to do and can make you more reluctant to adjust the design. He feels by coding the design once the final result will be cleaner as there won't be reworking.

Nathan would like Joe to do the front end design for both COO and Topic pages. Nathan would then take on developing the SASS for both.

This is a more efficient way to work as it will help keep the development work consistent. The additional WIPII time spent on COO would be balanced by not needing to develop the SASS.

Jane Young (Unlicensed) agreed to approach.