dscnitrourkela / project-kiwi Goto Github PK

Is your feature request related to a problem? Please describe.

1. Create the Login Component.
2. Create a component that shows user profile in place of the Login Component (To be shown after login)

Describe the solution you'd like

• Create a component For the Login part. (Do keep in mind that this and the Leaderboard components are to be made using css grids)
• A basic component that showcases users' points and a list of events attended.

Is your feature request related to a problem? Please describe.
We are going to use google Oauth for login. Set that up using the firebase APIs

Describe the solution you'd like

1. Setup OAuth handlers and integrate them with the app.
2. Setup a global state to determine the auth state of the application

Additional context

• We plan to use Context API along with useReducer hook.
• Use the OAuth popup option instead of redirect.

Is your feature request related to a problem? Please describe.

• As per the design, the header and the footer for the project are going to be the same. Research for any possible way through which we can use those components here without having an explicit code. (I am not really sure if this is even possible or not, hence the research)
• If no possible way, then recreate those components here. (You can literally get the entire marginals directory here itself.)

NOTE: BEWARE that you were planning to use Material UI here and the oregano project uses tailwind.

Is your feature request related to a problem? Please describe.
The leaderboard component is similar to the material-table components. Create the component.

Describe the solution you'd like

• Material table provides a component that has the search feature. Make sure to use the particular one and make the adjustments as required.
• It also has good provisions to update the styles of literally each and every part of the component. Go through the docs well and update the styles as designed.

Addition Note

• We are going to follow a pattern for this which is very standard. So the idea is to separate all the logic from the UI stuff.
• Since this component requires heavy integration with firebase, it makes sense that a wrapper component containing all the firebase logic is created and another component that has all the styles and JSX is created.
• As of now, in this PR, just create the style component but do keep in mind this architecture and code accordingly.