You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
I am very familiar with MaterialUI and want to be able to maintain the web app later.
The tasks
First of all, thank you that you are reading this.
For me it is important to have a good communication and speak about ideas and issues.
In the past I had bad experiences with other devs who created one huge pull request which was impossible to review. Please show me some of your work and speak about your ideas.
If you work on this task, please create small pull requests.
Match page:/match?platformId=euw1&matchId=123&summonerId=123
Redesign our current matches page. It is extracted from the app and has fixed width and height. For the web it should be responsive. You are free to suggest or remove ideas from the page. https://www.loltrophyhunter.com/match/EUW1/3885740024/24688273
Second step (not important right now -> only to get a feeling what we want to do later):
We hired a designer to create a new design for this project which includes Adobe XD specs for
the landing, profile and match results pages.
In the meantime I prepare the use of our api in #96.
After the design is done, it should be easy to convert it to React components.
TL;DR
Create a web app based on our API, Next.js and maybe MaterialUI.
The problem
We have a very limited web app which only shows matches and ranking.
https://www.loltrophyhunter.com/match/EUW1/3863024196/24688273
It is the same like in the app and doesn't look good in the browser.
The technology
Our new api makes it possible to read from our database and fetch data from the Riot API.
Example: https://www.th.gl/api/trophies?platformId=euw1&matchId=3795861223&summonerId=30118891
I prepared the setup based on Next.js and serverless deployment.
See https://github.com/lmachens/trophy-hunter/tree/master/src/www
Why Next.js?
It fits perfectly into our serverless architecture and allows easy scaling and developing.
Details:
Design-wise I am open for ideas.
It could get inspired by https://play.overwolf.com/trophy-hunter/ or our app https://www.overwolf.com/app/trophy_hunter-trophy_hunter.
I am very familiar with MaterialUI and want to be able to maintain the web app later.
The tasks
First of all, thank you that you are reading this.
For me it is important to have a good communication and speak about ideas and issues.
In the past I had bad experiences with other devs who created one huge pull request which was impossible to review. Please show me some of your work and speak about your ideas.
If you work on this task, please create small pull requests.
First step:
/
/match?platformId=euw1&matchId=123&summonerId=123
Second step (not important right now -> only to get a feeling what we want to do later):
/
/summoner/:summonerName
summonerName
,icon
andrank
(data from our api)Live
,Matches
,Trees
andTrophies
.The text was updated successfully, but these errors were encountered: