This is another collaborative project to which I contributed as a frontend developer. The “CS” in CSWebhook stands for Code Sapiens, a well-known online community of college students from various technical backgrounds. As a volunteer for an open-source event organized by the community, I worked alongside other members to develop an application that coordinated and monitored event activities.
The CS community was planning to host an event called “Oru Git-In Kadhai”, an open-source event aimed at spreading awareness about GitHub and encouraging open-source contributions among budding developers.
To monitor the activities of various teams and individuals in this event, we identified the need for a platform that allowed event coordinators to observe and analyze activities in real time. Hence, Project CSWebhook was born.
Our first step was to analyze the requirements:
After researching individually, we decided to build an application capable of displaying the following:
We also decided to implement a dashboard that displayed live updates. However, the development process was progressing slowly. Feeling that we were falling behind schedule, another community member and I took the initiative to complete the project efficiently.
Since only the two of us were working on the project, we decided to split the workload into two parts: frontend and backend. As expected, I chose to work on the frontend,while my collaborator handled the backend.
For this, I selected the following tech stack:
With the stack finalized, I began development by designing the landing page. Landing pages are crucial as they create the first impression for users visiting the platform. In this case, the goal was to design something relevant to the competition theme, so I ensured the design aligned with the event’s purpose.
For the main section, I drew inspiration from a stitch-generated design, and then added my own personal touch, refining and adapting it. I was quite satisfied with how it turned out.
The overall process went smoothly. Despite having only two contributors, we made steady progress within a short timeframe. After completing the landing page and main section, I moved on to designing the dashboard.
I stayed in close contact with my collaborator, discussing the content structure and how each component should be displayed. During this process, I also gained a better understanding of Git, which provided me with a new perspective on how version control works in collaborative environments.
Since the platform was intended for monitoring event activities, I designed the dashboard to ensure that organizers could view all information clearly and efficiently. Once both frontend and backend development were completed, we proceeded with final integration, ensuring smooth communication between both layers.
We completed the project within one week. The other volunteers were both surprised and impressed with the outcome. The organizing team was satisfied, and the event was conducted smoothly without major issues.
This project was a valuable experience for me, allowing me to strengthen my technical skills and receive constructive feedback. It was also fulfilling to contribute to a successful event using my skills, and I’m grateful for the opportunity.