...
Item | Who | Notes |
---|---|---|
Topics and programmes approach approved |
| |
Using third party system | Andrew |
Advantages of using Squiz as a content API
Disadvantages of using Squiz as a content API
Advantages of third party system to provide content API
Disadvantages of third party system
|
Development process | Nathan | 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 time taken to delivery. 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. |
Division of labour | Nathan | 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. |