Final Project - E-sports Betting Platform

You are a young student in your third year of computer engineering school!
A client comes to see you, accompanied by one of your best friends!
(or female friend, as you wish 😉)

This person presents you with their REVOLUTIONARY project!

The idea of the century!

An online sports betting platform! But not just any platform: an E-sports betting platform!
After a few hours of discussions and explanations, you accept this mission.
A VC from the United Arab Emirates is behind it and needs a killer POC!
Otherwise, they won't finance the project, and you can say goodbye to any possibility of working with this client.

The idea is therefore to create a first functional version, as simple as possible.
Each added feature will be rewarded, and each creative element or original idea will be as well.

You have at your disposal an SQL export of the data that we could have in this kind of application.
You are completely free on the choice of technologies (only condition: it must be JS/TS in the ecosystem).
Everything else is free: the design, the artistic direction, and the teams you want to pit against each other.

The data provided is not mandatory: you can, if you wish, add, delete, or modify it as you see fit.
You can request a specific data format depending on what you have in mind.

I also provide you with a moodboard, a graphic charter, and links to all the resources you can use.
YOU HAVE THE POSSIBILITY TO TOTALLY IGNORE THIS PART, and you are free to choose the graphic charter you want

You are asked for the following features:

• Landing: quick presentation of the idea

• Admin: page for creating a new team

  • ability to create a new team
  • ability to upload a profile picture for this team
  • ability to modify this team
  • ability to delete a team

• Admin: page for creating a match

  • ability to add a new match
  • ability to modify an ongoing match
  • ability to delete a match

• Visitor: page for betting on open matches

  • possibility to place a new offer

• Visitor: see the results

• Visitor: be able to see their gains and losses

I am not specifically asking you to set up an authentication and login system, but you are free to do so.
For example, if you have chosen to move your backend to a CMS or a third-party solution, you can implement it: it will be taken into account in the evaluation.
But if you don't feel capable, it may represent too great a waste of time.

(I emphasize that in a real professional project, this would be one of the first building blocks to put in place.)