Written independently by Ritesh Koushik (Web Co-Head)

This is being written on 8th January, 2026. The ideas and constraints are subjective to my timeline after co-heading the web-team of Anokha ‘26 and contributing in building infrastructure for this edition. The opinions are my own and not reflective of any group or entity.

  1. The website has always followed a standard pattern over the last 3 editions. It does not currently innovate with newer designs and animations. It operates with tried and tested ideas.

A solution could be to experiment with newer animation libraries and 3D elements and make the website a playful experience. After all, the website is built by and for 20 year olds. Demographic-driven design is imperative instead of striving to satisfy upper management.

  1. Custom forms for different events can be supported at a wider scale now. This year, we were able to support custom form for one particular event - AI Verse. But in the forth coming editions of Anokha, the idea can be proliferated across the organizers that they can come up with new and innovative events instead of the standard workshops and events.
  2. Data dispatch has been a breeze with Termite (our in-house data delivery service). We can power more events to have their independent internal tooling for managing participants and dispatch all the data that they need.
  3. There’s an urgent need to coalesce the multiple portals that have been built as part of internal tooling into a single unified portal - Anokha Mission Control. This needs to have a built-from-scratch role-based access control system for different stake holders in the the hierarchical pyramid to have access (students and faculties).
    1. Hospitality Panel
    2. Admin Panel
    3. Organizers Panel
    4. Others .. ? (in the future)

Better Data, Better Analytics

  1. As everyone seems to seek different kinds of data and some people need reports too. It is a good idea to include a data panel with analytical data that refreshes every 10 minutes. As analytics data requires aggregations, it is a good idea to run a background job that computes and presents this data. Somewhere we understand that no one really needs LIVE analytics data.
  2. Additionally, there may be authorities which require a complete report each data. (perhaps the registrar ?), a pipeline can be built to create a report in LateX and dispatch via mail as an attachment. The pipeline can expand to all folks who wish to have reports dispatched to them as they may or may not be tech savvy and are happy with receiving an end-of-day report.

The idea here is to reduce the number of calls people make to each other and to WMD for different data and analytics. Data for everyone, without calling anyone!

New Communication System

  1. We need a better communication system. This requirement comes in because of the following observations:
    1. Departments produce ideas which are critiqued and shot-down by TCW. All the communication happens back and forth and the tracking is done through excel with no trail of the communication thread. We need an event proposals system with option to comment on events and give reasons for discarding for the following stake holders:

      1. Department events - suggested by heads / co-heads
      2. Club event - suggested by presidents / chairs
      3. Other events - suggested by the students which were shot down by the first two but could be a good opportunity.

      While the third stakeholder may create more work for TCW and they might have to expand their headcount. Overall, it’s a good idea to get ideas for the crowd with complete visibility and appreciation from higher-ups. Creates interest and prompts more students to be involved in Anokha’s organizing space. The emails can still be involved for official documentation purposes in a programmatic way where all the changes suggested for an event are propagated via email in parallel. We already send OTP to participants so we have the infrastructure in place for sending out programmatic mails, all it needs doing is to scale up.

Work Submission + Notification System

There’s no tracking of the contributions made by different team members. While this cannot be fully solved, we should have a way to see who made what changes.

  1. Create a portal for managing all the personnel involved in Anokha. Every hire across every team needs to be listed there along with their phone numbers and emails.
  2. The programmatic mail ideas can involve the team, say “[email protected]” along with the heads and co-heads college emails in Cc so as to reduce the number of missed emails.
  3. Media team can upload their posters and other media elements in the submission system for review and the reviewing authorities can be notified.
  4. All posters reflect automatically on the main website without us having to scram around for aspect ratios and file-size complaints.