-
-
my working tree
-
my product was a template for note-taking. It could be peer-reviewed just with a link.
-
my hard work that details the firebase calls that was used in my code.
-
our values. A big problem is taking so many notes just to use the text-book for study. Its essential we learn to write better notes.
-
Front page.
Inspiration
I will always find a problem to be addressed in every hackathon I do, to provide me another reason and purpose to give the hackathon my all. In this case: I wanted to address the problem of inefficient notes, which I experienced a lot, often using the textbook instead of the notes I use in class.
What it does
I researched the different note-taking methods, like the Cornell note taking method, and integrated strict templates to help disorganized students like me follow them. There also is very easy collaboration as if one wants to peer review a note, all they have to do is share a link to access the document. I believe security is a minor concern because notes aren’t exactly sensitive data….
How we built it
I used tons of react JS, firebase, and git branching to create this technology . Learning them all in this hackathon!! I found myself staring at documentation and scouting Stack overflow to no avail. At least I know how to commit to Github on the ide now. Trying to work with and integrate the backend to my front end took a lot but what I learned was invaluable
Challenges we ran into
I started as a team. Which was a challenge. I spent hours learning git and GitHub to learn how to properly contribute code, expecting someone to cover my backend side. But due to understandable circumstances we parted ways, and being left with the backend , although it was challenging, It felt like another opportunity to learn invaluable skills. A notable challenge was trying to figure out how to organize my data. Although saving pages and docs looks easy it was tedious in the backend. In addition, my goal of posting this website to GitHub pages cut me off to server side databases like MySQL due to their nature . Still Firebase was still very fun to learn and I appreciate the challenge .
Accomplishments that we're proud of
I was really proud of myself for being able to integrate backend to front end. It was surprising I was able to create such technology and I am excited for how much more I can create!
What we learned
3 things that I learned through hard work was react js, I never used it as much as I did in the project. I never used routing before, and am amazed how instanteous the loading times are. Interacting with a database . I went for firebase because I want to host my project on GitHub pages which provides no servers. Finally I learned and got experienced with collaboration. Although my team ended up splitting, spending hours to learn git and using GitHub will serve me for years to come.
What's next for Lemnsicate ( Infinity )
I came in this hackathon wanting to create a project that will last for more than just a 2 day project and something that I can contribute for years. I believe Lemnsicate will help guide and improve my skills as I steadily add more and more features to it. It would be a waste to abandon something that I believe can help people like me. My code may be up for GH pages, though I have to do something about the missing API keys from my .env file.
Log in or sign up for Devpost to join the conversation.