Athena Team Meeting 3-31-2022
- David Launikitis
Agenda:
Discussion on deadlines moving forward
Finalized branding?
Review of the past week and shoutouts
Documentation on Confluence
Notes:
Goal : beta by end of semester and full release by next fall
Names to vote on
UTD Trends
UTD Info
UTD Stats
Design - flat logo vs current
___________________________________________________________________________
Start
Writing better documentation
Frequent pull requests, diversity in code reviews (Prof Cole’s lesson on code reviews soon)
Feedback for design, team and public
Assemble list of resources for project - useful for new teammates
Comminicate with API team
Hiring designers/ team members
Stop
Code cramming
Avoiding asking for help
Switching the graphs
Sleep deprivation
Doing this instead of homework
Continue
Having fun
Being productive and writing good code
Weekly team communication
___________________________________________________________________________
Confluence:
Can create our own internal wikis
Has built in support for Figma, easy to put it into the documentation, can get feedback and start a wiki page on it.
Good for starting documentation and tracking evolution of the project.
Storybook - documentation for front end components, has independent component testing to avoid mess of testing on pages
Dynamic adjusting of attributes in the documentation
Action Items:
Play around with confluence- do documentation for a component you’ve done and talk about what you’ve learned Eric,William,Taya
Figma and confluence interaction - Shuaib
Learn Golang - Taya
Storybook build issues - Eric / volunteers
Look at storybook docs - front end
Decide which testing suites to look out - Jest, Mocha, Cypress
Cypress - 1 page product brief - Danny
Mocha and Jest recommendation report - William