Inspiration
Syncing a calendar from school to personal usually includes a bunch of junk we wanted to prioritize our class work as well as be able to filter junk.
What it does
Users can add as many ical URLs to their accounts which which is saved to the database. it then has configurable settings on the right to manipulate the data of their calendar allows for basic crossing off tasks as well
How we built it
we used react for the front end and flask for the back end as this was the first hackathon for all members involved we did not know what to expect or had any project ideas for a bit, so we jumped on this idea
Challenges we ran into
CORS errors. Lots of them CORS is Cross-Origin Resource Sharing, and well Canvas does not like when u request a student's calendar without being a proper service we fixed this by putting the calendar getting/reading onto the backend this does create a more stressful environment for the backend however other then that the back end is very simple just the link to mongo db.
Accomplishments that we're proud of
The front end. Mainly have been more of script developers instead of website builders but we wanted to try something new for this, so we went with a full stack project. getting to use Auth0 was also really cool once you read enough of the docs to understand it.
What we learned
We learned how to better use CSS, and that inline CSS is good for the short term but not good for the long term as you keep wanting to add to the website. we learned valuable skills in React and css as well as connecting a flask back end to a react front end.
What's next for Priority Tracker
We want to allow users to give different point values based on the keyword and allow for tags to be created and auto-assigned we think it could help bring it to be a better overall project. However, the front end would probably have to be redone if anyone was going to use this project as all the inline css can be hard to work with especially if you change the positioning of something it all may crumble into something else but for 24 hours as well as a first hackathon we think this was a success.
Log in or sign up for Devpost to join the conversation.