This repository was archived by the owner on Jan 9, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
This repository was archived by the owner on Jan 9, 2026. It is now read-only.
Refactoring Frontend #15
Copy link
Copy link
Open
Labels
LSTMlstm worklstm workbackendThis is all backend work for the projectThis is all backend work for the projectdocumentationImprovements or additions to documentationImprovements or additions to documentationfrontendPertains to all frontend design, logic, or planning.Pertains to all frontend design, logic, or planning.project
Description
Objective
This part of the project will bring everything together into making the game. This will allow the users to actually use the site and be able to track their scores and compete with other users to outperform them. There will be multiple parts for the project which I will be presenting, like the higher or lower game and also how all of the scores are calculated.
Frontend Design
Components
Dashboard
- gives the stats of the user and general info about their stocks and ratings
Market
- this will let them explore the market and buy/sell stocks
- add in variables in the backend for tracking stocks/stockObj (stock name, shares, price, sold/buy)
- create frontend form component
- style to match the frontend
Purchase History
- this would let the user see what they have purchased and their history of what earned them money and what didn't
- create table display in the frontend
- pull the data into the frontend from the backend per user basis
Higher or Lower Game:
- the user will pick whether their stock of choice will either increase or decrease within that day
- this will give the user a rating that will basically give them a score based on how accurate they are at predicting the stocks
- the user input will be compared to the LSTM predictions and then that will create a score
- create frontend element that allows the users to make their predictions on the stocks for their future prices
- the rating will be given for each individual stock
- each individual rating will then be averaged out into one big rating that will be sent to the backend after the guesses are completed
- this will also be placed into the leaderboards and give the players a score
- the ratings can also give the users money to trade with
Performance
- this gives the user a rating that would let them see how they are doing with their trades and with their predictions from the higher or lower game
- this would also let the users compare themselves with other users in their classes and globally
- pull in the user ratings and the user account growths/total money in the account
- display in a table
Sessions
- this will let you manage which classes you joined and your rankings briefly shown in those classes
- connect this with the game codes that will allow the users to join games created by the teachers
- this will allow them to compete with their friends
Support
- this will let users submit complaints and recommendations to the website through google forms
- google form created and linked to the FE
Schedule
Monday
- refactoring the frontend to create the general layouts for pages
- start working on the Higher or Lower game
Tuesday
- finishing the Higher or Lower game
- formatting leaderboard and pulling in data from the backend
Wednesday
- continue formatting and finishing up the formatting for the site and begin debug
- make sure everything works coherently and as intended
Thursday
- debugging project and making sure everything works
- checking over the backend and connections to the databases
Friday
- finalize the debugging and start whole site debugging
- making sure the home server works as intended
Metadata
Metadata
Assignees
Labels
LSTMlstm worklstm workbackendThis is all backend work for the projectThis is all backend work for the projectdocumentationImprovements or additions to documentationImprovements or additions to documentationfrontendPertains to all frontend design, logic, or planning.Pertains to all frontend design, logic, or planning.project
Type
Projects
Status
Done
