Changed a lot of the UI to make use of bootstrap and just have it be like the sample screens. The ui should folder should contain a file called things-to-do.md that just lists out all the things that I felt we still needed to do for the frontend.I'm actually pasting the contents of that file below for convenience:
Header.js:
Does it render the things that it should - test that out (especially with backend integration)
Test the login popup
Home.js
Are we doing upcoming events? If we are then implement it on the frontend.
We should sort the favorited events by start date and time and have the 4 earliest ones displayed on the home page.
Org.js and Event.js (common stuff):
How to know if some user is a club admin so that we can decide which buttons to display? Also, we will only need to display the org specific buttons (edit, delete) for the org that the user is a club admin of - can't display those buttons for all orgs when user is club admin.
Handling favorite and delete for an org/event.
How to handle the case of a club admin adding a new org or adding a new event? Might need a new component or could somehow integrate it using the edit “components”.
What to do for the org and event images? Right now both are auto-generated but we could change that if we want.
Event.js:
Location is not a field in the database - we need to have that.
Edit pages:
Need to send new state to the backend api when submitting the form
Do we need a cancel button? If so, implement that event handler.
Search.js
Bugs that need to be fixed - don't know whether it's the backend or the frontend.
Settings.js:
Again, only display the 4 earliest favorited events.
Should we even display the orgs? If we do, then we should only display a limited number of them.
Might have to remove the change button if we don't have functionality to change email.
General stuff:
Should change how date and time is displayed - should be displayed separately. Because it doesn't look good right now.
Do some form validation for all the inputs. Not sure if we need this for any form though.
Changed a lot of the UI to make use of bootstrap and just have it be like the sample screens. The ui should folder should contain a file called things-to-do.md that just lists out all the things that I felt we still needed to do for the frontend.I'm actually pasting the contents of that file below for convenience:
Header.js:
Home.js
Org.js and Event.js (common stuff):
Event.js:
Edit pages:
Search.js
Settings.js:
General stuff: