The problem Nescii solves

There is already Linkedin to share our achievements, information, and any other activities There are already societies pages on other social media sites like Facebook and Instagram There is already WhatsApp for sharing circulars, notices, etc. Then Why Nescii?

The answer is pretty simple
It is very often that we wouldn't be able to connect with every student of our college. So many times we would not be able to meet some like-minded peers to collaborate and work together. Won't be able to know the different domains in which our mates are working on. So to reduce that gap we have created Nescii. Here every post is in public view means you just need to login into the website with the college ID. And you will be able to see every post made by your peers.
It is very often that some students are not very active on social media sites or there is a significant possibility that we wouldn't get the upcoming events to notice, important meet-ups, fun activities and some other society related stuff at the right moment because we need to see every page individually. So to decrease these problems we have created Nescii. In this, there are separate page "societies" where all societies are listed. And you can navigate to any one of them to see the posts, upcoming events made by that particular society and Fun fact is in order to switch to a different society, all you need to do is nothing. Just click another society tab and within nanoseconds, you will be directed to that society and get the details.
It will also be a tiring job for the societies admin to post on multiple social media sites. So with Nescii, they can post their stuff at the same location.
It is also very common to share circulars, notices, etc on WhatsApp in multiple groups. At Nescii they can post at a single place and students will infer from here.

Challenges we ran into

1. The uploading and rendering of multiple media was an issue that we stumbled upon. It was solved using synchronous calls to Firebase Storage. Rendering was done by the ReactPlayer library.
2. Developing the mobile view was a bit time-consuming and it was solved by good old Bootstrap.
3. Rendering carousels was done by SwiperJS.
4. Web Scraping for Notices was resolved by CheerioJS.
5. Automatic emailing the college society presidents was done by EmailJS API. It was time-consuming to go through the documentation.
6. Stylizing the website and improving the UI involved going through many CSS frameworks. Finally, we settled for Material-UI.