/
Meeting #13

Meeting #13

Date

12/10/2020, 1600-1700HRS

Participants

  • @Tommy Truong (Unlicensed)

  • @Paula Tennent (Unlicensed)

  • @Abiram Nadarajah (Unlicensed)

  • @Jarvis W. (Unlicensed)

  • @Sergio Mercado Ruiz (Unlicensed)

Goals

  • Pivoting

  • Open Discussion about direction

Please add any discussion points that you would like to talk about below. Make sure to include as much context as you can, as well as an indication for how long you expect the discussion to last. Most discussion points won’t take more than 5-15 minutes.

Discussion topics

Discussion Point

Presenter

Duration

Context

Notes

Discussion Point

Presenter

Duration

Context

Notes

Follow up on action items from previous meeting

Everyone

2 mins

 

Meeting #12

Updates

Everyone

5 mins

  • What have you been working on?

  • Do you have anything blocking you?

  • What do you plan to work on?

  • Tommy: Opened a PR for the responsive landing page. Blockers: Prog challenges. 

  • Jarvis: Blocked still since Friday.

  • Sergio: Started working on the DB at least the first part: shutting down properly to save persistent data. Blockers: Blocked disabling adoption of another ticket.

  • Abiram: Fixed the event issue. Blockers: 2521

  • Paula: Busy all of last week so no tickets completed. Blocker: Assignment on sunday night, catch up for 4418 lectures + prog challenges

CMS Pivot

Tommy

2 mins

 

  • Authentication groundwork in place to move to developing some of the backend for CMS.

  • Database needs to be restructured to handle information that is intended for the website.

  • All information that needs to be updated by the CMS should be fetched by API -> this needs to happen for data props on the landing page. Tickets for this week.

  • Pages needed to be created for the wireframes currently designed

  • Menu and Footer need to be designed and coded for smaller screen sizes. -> Review.

  • Breakdown of what needs to be addressed first out of the CMS tickets currently tagged.

Open Discussion

Everyone

30 mins

 

Notes:

  • Grab stuff from the API -> top priority -> Sergio

  • Wanted to have one fetch per page to make the page as responsive as possible -> content of a page to be in a single document -> con:  find data hard to find and locate -> pro: sending it off. Classifying things by data points. -> Tommy will tag data types.

  • Using native vuetify to code up and design will create clear functionality for the CMS - Jarvis

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Feedback

 

 

  • Questions?

  • Comments?

  • Concerns?

 

Action items

@Tommy. Write up tickets for this week. 12/10/2020
@Tommy. Review PR. 12/10/2020
@Tommy. Catalog and write up a list of data types.

Decisions

  1. Keep the CMS design simple by using native vuetify design.