Skip to content

Platform

Rotaract District 3292 Platform

Public website and member platform for 6,000+ Rotaractors in 198 clubs across Nepal and Bhutan.

Role
Developed and deployed
Organisation
Rotaract District 3292 (Nepal & Bhutan)
Timeline
2026
Status
Live
  • React
  • TypeScript
  • Vite
  • Tailwind CSS
  • Mobile app
  • Node.js API
  • Docker
  • nginx
members
6,000+members
clubs in 20 zones
198clubs in 20 zones
countries
2countries

Context

Rotaract District 3292 covers Nepal and Bhutan: 198 clubs, 20 zones and more than 6,000 members aged 18–30. The district needed one public face for anyone curious about Rotaract, and one place to run itself: clubs, members, events, officers and finance.

Stakeholders and needs

Who uses the platform, and what they can do
RoleNeedsAccess
Public visitorFind a club, see projects and events, register interestPublic site
MemberDirectory, events, own billsMember portal
Club officerManage their own club's board, members and eventsOwn club only
District adminRun the whole district: clubs, officers, finance, meetingsEverything

Requirements

Requirements
IDTypeRequirement
FR-01FunctionalSearchable club directory by name, place and zone, with each club's board.
FR-02FunctionalProjects and events filterable by cause, with upcoming events and interest registration.
FR-03FunctionalDistrict team listing for the current Rotary year.
FR-04FunctionalRole-based portal for members, club officers and district admins, including finance and meetings.
FR-05FunctionalMobile app with push notifications.
NFR-01Non-functionalEach role sees only what it should: club officers are limited to their own club.
NFR-02Non-functionalA typed contract between frontend and API, so either side can change without breaking the other.

Architecture

One codebase, three apps
  1. Clients
    • Public website
    • Member portal
    • Mobile app
  2. Shared
    • Typed contract
    • Types & validation
  3. Server
    • API
    • Database
    • Push notifications
Hosting
  • Docker
  • nginx
  • rotaract3292.org.np

What I built

  • The public website: hero, district statistics, projects and events with cause filters, upcoming events, district team, and a club finder across all 20 zones.
  • The member portal with three roles and their permissions, written first against a typed contract so the real API slotted in without a rewrite.
  • Migration of the district's club and member records into the new system.
  • Production deployment with Docker and nginx on the district's own domain.

Outcome

Rotaractors served
6,000+Rotaractors served
clubs listed with their boards
198clubs listed with their boards
one district, one platform
Nepal & Bhutanone district, one platform

Artefacts I produced

  • Project plan and requirements
  • Role and permission model
  • Typed API contract
  • Data migration of clubs and members
  • Deployment (Docker, nginx)