Notice: lots of issues and pull requests that have not yet been resolved at time of review. Also, there are lots of branches that should be cleaned up since their purpose has been served (There are like 20 branches at the time of review). Lastly, there are some sprint files that are not fully filled out that are from sprints 1 and 2.
Overall: The current product seems to have a nice frontend but there does not seem to be a backend or testing software. The repository seems to be a bit disorganized but we do expect that it can be cleaned up relatively quickly with some documentation, branch cleanup, etc.
1 Strength: What the team is doing well (be specific)
The frontend has a nice dark and light mode and the repo protections for merging are solid.
2 Improvements: Concrete suggestions for what could be improved
1 Question: A thoughtful question about design, implementation, or direction
Where are the designs from? Did you just AI generate the layout or is there a wireframe?
1 Suggestion: A practical next step or idea they could implement “
Try making the front end responsive to a simple backend setup in localhost
What we learned:
Repo organization is important for knowing the purpose of things. For example, we initially could not find the ADR for cloudflare so we did not really know what the purpose was. In an attempt to understand the repository, it was difficult to understand what was happening without the proper documentation filled out.