DEV Community

Abhishek Gupta
Abhishek Gupta

Posted on

GDG Ranchi DevFest Game 2026

Participant & Game Management System

1. Overview

This system will manage participants, games, game registrations, game submissions, scores, and the leaderboard for GDG Ranchi DevFest 2026.

The system will have only two roles:

  1. Super Admin
  2. Participant

The system will be independent of Commudle. Participants can register themselves through the website, while the Super Admin manages participants, games, and scores.

The main goal is to keep the system simple, reliable, and easy to operate during the event.

2. Main System Flow 

                    GDG Ranchi Game System
                             │
              ┌──────────────┴──────────────┐
              │                             │
         SUPER ADMIN                   PARTICIPANT
              │                             │
      Manage Participants             Register Account
      Manage Games                     View Games
      Manage Registrations             Register for Game
      Manage Submissions               Submit Game
      Update Scores                    View Own Results
      View Leaderboard                 View Leaderboard
              │                             │
              └──────────────┬──────────────┘
                             │
                         LEADERBOARD
Enter fullscreen mode Exit fullscreen mode

3. Roles

3.1 Super Admin

The Super Admin has complete control over the game management system.

Super Admin can:

  • Login to admin dashboard
  • View all participants
  • Search participants
  • Edit participants
  • Disable participants
  • Enable participants
  • Create games
  • Edit games
  • Activate games
  • Close games
  • View game registrations
  • View game submissions
  • Update participant scores
  • View participant game history
  • View leaderboard
  • Manage final event data

4. Participant

Participants use the public website/dashboard.

Participant can:

  • Register their account
  • Enter personal information
  • View their participant profile
  • View available games
  • Register for games
  • Submit completed games
  • View their registered games
  • View submitted games
  • View scores
  • View total points
  • View leaderboard
  • View their current rank

Participants cannot:

  • Edit their game score
  • Create games
  • Edit other participants
  • Disable participants
  • Manage the leaderboard
  • Manage other users

5. Participant Registration

Participants can register themselves through a public registration form.

Registration form 

Name *
Email *
Mobile Number *
Organization
City
Profile Photo
Other required information
Password *
Confirm Password *
Enter fullscreen mode Exit fullscreen mode

After successful registration:

Registration
     ↓
Create Participant Account
     ↓
Generate Participant ID
     ↓
Participant Dashboard
Enter fullscreen mode Exit fullscreen mode

6. Participant ID

Every participant should receive a unique Participant ID.

Example:

GDG26-0001
GDG26-0002
GDG26-0003
Enter fullscreen mode Exit fullscreen mode

The Participant ID can be used internally to identify a participant.

It should be:

  • Unique
  • Easy to read
  • Stable
  • Never reused

Example:

Participant ID: GDG26-0042
Name: Abhishek Kumar
Email: abhishek@example.com
Enter fullscreen mode Exit fullscreen mode

7. Participant Status

Participants should not be permanently deleted by default.

Instead, use a status.

ACTIVE
DISABLED
Enter fullscreen mode Exit fullscreen mode

Active

The participant can:

  • Login
  • Register for games
  • Submit games
  • View results

Disabled

The participant cannot:

  • Login
  • Register for new games
  • Submit games

However, their previous registrations and scores remain stored.

This protects historical event data.

8. Participant Dashboard

After login, the participant sees a simple dashboard.

┌─────────────────────────────────────┐
│ Welcome, Abhishek                   │
│ Participant ID: GDG26-0042          │
├─────────────────────────────────────┤
│ Total Games       5                 │
│ Completed Games   3                 │
│ Total Points      240               │
│ Current Rank      #12               │
└─────────────────────────────────────┘
Enter fullscreen mode Exit fullscreen mode

Dashboard sections

  • Profile
  • Available Games
  • My Games
  • My Results
  • Leaderboard

9. Games

The Super Admin creates and manages games.

A game can contain:

Game Name
Description
Maximum Score
Start Time
End Time
Status
Enter fullscreen mode Exit fullscreen mode

Example:

Game Name: Tech Quiz

Description:
Test your knowledge of technology and programming.

Maximum Score: 100

Start Time: 10:00 AM
End Time: 11:00 AM

Status: ACTIVE
Enter fullscreen mode Exit fullscreen mode

10. Game Status

Every game should have a status.

UPCOMING
ACTIVE
CLOSED
Enter fullscreen mode Exit fullscreen mode

UPCOMING

The game has not started yet.

Participants can see the game but cannot submit it.

ACTIVE

The game is currently available.

Participants can register and submit the game.

CLOSED

The game has ended.

New registrations/submissions should not be allowed.

11. Create Game

Only the Super Admin can create games.

Example:

Create Game

Game Name: Coding Challenge

Description:
Solve the given programming challenges.

Maximum Score: 100

Start Time: 2:00 PM
End Time: 3:00 PM

Status: UPCOMING
Enter fullscreen mode Exit fullscreen mode

After creation:

Game
 ↓
UPCOMING
 ↓
ACTIVE
 ↓
CLOSED
Enter fullscreen mode Exit fullscreen mode

12. Manage Games

The Super Admin can:

  • Create game
  • Edit game
  • Change game status
  • View registrations
  • View submissions
  • View results
  • Close game

Example admin table:

Game Max Score Registrations Submissions Status
Tech Quiz 100 450 430 Closed
Coding Challenge 100 320 300 Active
Memory Game 50 280 0 Upcoming

13. Game Registration

A participant can register for an available game.

Participant Dashboard
        ↓
Available Games
        ↓
Select Game
        ↓
Register
        ↓
Registration Successful
Enter fullscreen mode Exit fullscreen mode

Example:

Tech Quiz

Maximum Score: 100
Status: ACTIVE

[ Register for Game ]
Enter fullscreen mode Exit fullscreen mode

14. Duplicate Registration Protection

A participant must not be able to register for the same game twice.

For example:

Abhishek → Tech Quiz → Registered
Enter fullscreen mode Exit fullscreen mode

If Abhishek tries again:

Already Registered
Enter fullscreen mode Exit fullscreen mode

The backend must enforce this rule.

15. Game Submission

After registering and playing the game, the participant submits the game.

Example:

Tech Quiz
     ↓
Start Game
     ↓
Complete Game
     ↓
Submit Game
Enter fullscreen mode Exit fullscreen mode

After submission:

Status: SUBMITTED
Score: 0
Points: 0
Enter fullscreen mode Exit fullscreen mode

The initial score should be 0 by default.

The Super Admin can later update the actual score.

16. Score Management

Only the Super Admin can change scores.

Example:

Participant: Abhishek Kumar
Game: Tech Quiz

Current Score: 0

Maximum Score: 100

New Score: 85

[Update Score]
Enter fullscreen mode Exit fullscreen mode

After update:

Score: 85
Points: 85
Enter fullscreen mode Exit fullscreen mode

17. Score Validation

The backend must validate the score.

If:

Maximum Score = 100
Enter fullscreen mode Exit fullscreen mode

Then:

0 ≤ Score ≤ 100
Enter fullscreen mode Exit fullscreen mode

Invalid:

Score = 120
Enter fullscreen mode Exit fullscreen mode

The backend should reject it.

The score should never be trusted only from the frontend.

18. Score and Points

The system should store both score and points.

For a simple implementation:

Score = 85
Points = 85
Enter fullscreen mode Exit fullscreen mode

This gives flexibility if the event later wants different scoring rules.

For example:

Game Score = 80
Leaderboard Points = 100
Enter fullscreen mode Exit fullscreen mode

The current implementation can simply use:

Points = Score
Enter fullscreen mode Exit fullscreen mode

unless a different game-specific rule is required.

19. Participant Game History

Every participant should be able to see their game history.

Example:

My Games

Game                Score    Points    Status
------------------------------------------------
Tech Quiz             85       85      Submitted
Memory Game            70       70      Submitted
Coding Challenge       0        0       Registered
Puzzle Game            95       95      Submitted
Enter fullscreen mode Exit fullscreen mode

At the bottom:

Total Games: 4
Completed Games: 3
Total Points: 250
Enter fullscreen mode Exit fullscreen mode

20. Search Participant

The Super Admin should be able to search participants.

Search using:

  • Participant ID
  • Name
  • Email
  • Mobile number

Example:

Search: GDG26-0042
Enter fullscreen mode Exit fullscreen mode

Result:

Abhishek Kumar
GDG26-0042
abhishek@example.com
9876543210
Enter fullscreen mode Exit fullscreen mode

21. Participant Details Page

The Super Admin should be able to open a participant profile.

Participant Details
────────────────────────────

Name: Abhishek Kumar
Participant ID: GDG26-0042
Email: abhishek@example.com
Mobile: 9876543210
Organization: NexGen Studio
City: Ranchi

Status: ACTIVE

Game History
────────────────────────────

Game              Score    Points
Tech Quiz           85       85
Memory Game         70       70
Coding Challenge     0        0

Total Points: 155
Enter fullscreen mode Exit fullscreen mode

The participant's profile image can also be displayed.

22. Manage Participants

The Super Admin can view all participants.

Example:

Participant ID Name Email Mobile Games Points Status
GDG26-0001 Rahul rahul@example.com 98xxxxxx 4 280 Active
GDG26-0002 Priya priya@example.com 97xxxxxx 3 210 Active
GDG26-0003 Amit amit@example.com 96xxxxxx 2 120 Disabled

Actions:

View
Edit
Disable
Enable
Enter fullscreen mode Exit fullscreen mode

23. Leaderboard

The leaderboard shows participants ranked by total points.

Example:

Rank Participant Games Total Points
1 Rahul 5 450
2 Priya 5 420
3 Amit 5 390
4 Abhishek 4 350

The leaderboard should automatically update when scores change.

24. Ranking Calculation

The basic ranking rule:

Total Points =
Game 1 Points
+ Game 2 Points
+ Game 3 Points
+ ...
Enter fullscreen mode Exit fullscreen mode

Example:

Tech Quiz          80
Memory Game        70
Coding Challenge   90
Puzzle Game        60
----------------------
Total Points      300
Enter fullscreen mode Exit fullscreen mode

Leaderboard:

ORDER BY total_points DESC
Enter fullscreen mode Exit fullscreen mode

25. Tie-Breaker

Tie-breaking should be decided before the event.

Recommended order:

1. Higher Total Points
2. Higher Highest Game Score
3. More Completed Games
4. Earlier Final Submission
Enter fullscreen mode Exit fullscreen mode

For example:

Rahul       300 points
Abhishek    300 points
Enter fullscreen mode Exit fullscreen mode

Then compare the next tie-breaker.

This avoids confusion when deciding the top 3 winners.

26. Top 3 Winners

The final leaderboard determines the winners.

🥇 Rank 1 → Winner
🥈 Rank 2 → Runner-up
🥉 Rank 3 → Third Place
Enter fullscreen mode Exit fullscreen mode

The Super Admin should have a final leaderboard view for announcing winners and distributing goodies.

27. Admin Dashboard

The Super Admin dashboard should provide a quick overview.

┌────────────────────────────────────────────┐
│              ADMIN DASHBOARD               │
├────────────┬────────────┬──────────────────┤
│ Participants│ Games      │ Registrations    │
│     900     │     10     │      4,500       │
├────────────┼────────────┼──────────────────┤
│ Submissions│ Completed  │ Total Points     │
│    4,100    │    4,100   │     350,000      │
└────────────┴────────────┴──────────────────┘
Enter fullscreen mode Exit fullscreen mode

Below that:

  • Recent registrations
  • Recent submissions
  • Top participants
  • Active games
  • Games requiring attention

28. Recommended Pages

Public Pages 

/
├── Home
├── Register
├── Login
└── Leaderboard
Enter fullscreen mode Exit fullscreen mode

Participant Pages 

/dashboard
/profile
/games
/my-games
/my-results
/leaderboard
Enter fullscreen mode Exit fullscreen mode

Super Admin Pages 

/admin
/admin/participants
/admin/participants/:id
/admin/games
/admin/games/create
/admin/games/:id
/admin/registrations
/admin/submissions
/admin/scores
/admin/leaderboard
Enter fullscreen mode Exit fullscreen mode

29. Database

For this system, PostgreSQL is a good choice.

The expected workload is small.

Even with:

900 participants
10 games
Enter fullscreen mode Exit fullscreen mode

The maximum game registrations would roughly be:

900 × 10 = 9,000 registrations
Enter fullscreen mode Exit fullscreen mode

This is very small for PostgreSQL.

There is no need to introduce Redis, RabbitMQ, Elasticsearch, microservices, or Kubernetes just for this system.

30. Main Database Tables

The system can start with these tables:

users
participants
games
game_registrations
game_results
score_update_logs
Enter fullscreen mode Exit fullscreen mode

Optional:

activity_logs
email_logs
Enter fullscreen mode Exit fullscreen mode

31. Users Table

Used for authentication.

users

id
name
email
password_hash
role
status
created_at
updated_at
Enter fullscreen mode Exit fullscreen mode

Role:

SUPER_ADMIN
PARTICIPANT
Enter fullscreen mode Exit fullscreen mode

32. Participants Table

Stores participant information.

participants

id
participant_id
user_id
name
email
mobile
image_url
organization
city
status
created_at
updated_at
Enter fullscreen mode Exit fullscreen mode

Example:

id: UUID
participant_id: GDG26-0042
name: Abhishek Kumar
email: abhishek@example.com
mobile: 9876543210
status: ACTIVE
Enter fullscreen mode Exit fullscreen mode

33. Games Table 

games

id
name
description
max_score
status
start_time
end_time
created_at
updated_at
Enter fullscreen mode Exit fullscreen mode

Example:

name: Tech Quiz
max_score: 100
status: ACTIVE
Enter fullscreen mode Exit fullscreen mode

34. Game Registrations Table

This connects participants with games.

game_registrations

id
participant_id
game_id
status
registered_at
created_at
updated_at
Enter fullscreen mode Exit fullscreen mode

Important database rule:

UNIQUE(participant_id, game_id)
Enter fullscreen mode Exit fullscreen mode

This prevents duplicate registration.

35. Game Results Table

Stores the result of a game.

game_results

id
participant_id
game_id
score
points
status
submitted_at
updated_at
created_at
Enter fullscreen mode Exit fullscreen mode

Default:

score = 0
points = 0
Enter fullscreen mode Exit fullscreen mode

36. Score Update Logs

Whenever an admin changes a score, the system should keep a record.

score_update_logs

id
participant_id
game_id
old_score
new_score
old_points
new_points
updated_by
reason
created_at
Enter fullscreen mode Exit fullscreen mode

Example:

Old Score: 70
New Score: 80

Updated By: Admin
Reason: Manual evaluation correction
Time: 2026-10-04 15:30
Enter fullscreen mode Exit fullscreen mode

This is useful if a score is accidentally changed.

37. Database Relationship 

USER
 │
 └──── PARTICIPANT
          │
          ├──────── GAME REGISTRATION
          │                 │
          │                 └──── GAME
          │
          └──────── GAME RESULT
                            │
                            └──── GAME
Enter fullscreen mode Exit fullscreen mode

Simplified:

Participants
     │
     ├────< Game Registrations >──── Games
     │
     └────< Game Results >────────── Games
Enter fullscreen mode Exit fullscreen mode

38. Backend Architecture

Recommended stack:

Frontend
React / Next.js

        ↓

Backend
Node.js
TypeScript
Express

        ↓

ORM
Prisma

        ↓

Database
PostgreSQL
Enter fullscreen mode Exit fullscreen mode

External services:

Participant Image
       ↓
Cloudinary

Email
       ↓
Email Provider
Enter fullscreen mode Exit fullscreen mode

39. Backend Structure

A simple structure is enough.

src/
│
├── modules/
│   ├── auth/
│   ├── participants/
│   ├── games/
│   ├── registrations/
│   ├── results/
│   └── leaderboard/
│
├── middleware/
│   ├── auth.ts
│   └── role.ts
│
├── database/
│
├── utils/
│
├── routes/
│
├── app.ts
└── server.ts
Enter fullscreen mode Exit fullscreen mode

Keep modules separated by responsibility.

40. Authentication

Participants and Super Admin both need authentication.

Recommended:

Email
+
Password
Enter fullscreen mode Exit fullscreen mode

Passwords must never be stored directly.

Store:

password_hash
Enter fullscreen mode Exit fullscreen mode

Use a secure password hashing algorithm such as Argon2 or bcrypt.

41. Authorization

Authentication answers:

Who are you?

Authorization answers:

What are you allowed to do?

Example:

Participant
    ↓
GET /games
    ✓

Participant
    ↓
POST /games
    ✗

Super Admin
    ↓
POST /games
    ✓
Enter fullscreen mode Exit fullscreen mode

Every protected backend operation should check the user's role.

42. Important Backend Rules

The backend should enforce:

Rule 1

Disabled participants cannot perform game actions.

Rule 2

Participant cannot register twice for the same game.

Rule 3

Participant cannot update their own score.

Rule 4

Only Super Admin can update scores.

Rule 5

Score cannot exceed maximum score.

Rule 6

Closed games cannot accept new submissions.

Rule 7

Leaderboard must use server-side data.

Rule 8

Participant can only view their own private profile/results.

Rule 9

Participant ID must be unique.

Rule 10

Important admin changes should be logged.

43. API Plan

Authentication 

POST /auth/register
POST /auth/login
POST /auth/logout
GET  /auth/me
Enter fullscreen mode Exit fullscreen mode

Participant 

GET    /participants/me
PATCH  /participants/me
GET    /participants/me/games
GET    /participants/me/results
Enter fullscreen mode Exit fullscreen mode

Admin Participants 

GET    /admin/participants
GET    /admin/participants/:id
PATCH  /admin/participants/:id
PATCH  /admin/participants/:id/status
Enter fullscreen mode Exit fullscreen mode

Games 

GET    /games
GET    /games/:id
Enter fullscreen mode Exit fullscreen mode

Admin Games 

POST   /admin/games
PATCH  /admin/games/:id
PATCH  /admin/games/:id/status
DELETE /admin/games/:id
Enter fullscreen mode Exit fullscreen mode

Instead of physically deleting an important game, it may be safer to close/archive it.

Game Registration 

POST /games/:gameId/register
GET  /my-games
Enter fullscreen mode Exit fullscreen mode

Game Submission 

POST /games/:gameId/submit
Enter fullscreen mode Exit fullscreen mode

Admin Results 

GET   /admin/results
GET   /admin/results/:id
PATCH /admin/results/:id/score
Enter fullscreen mode Exit fullscreen mode

Leaderboard 

GET /leaderboard
Enter fullscreen mode Exit fullscreen mode

44. Game Lifecycle

A game follows this lifecycle:

CREATE
  ↓
UPCOMING
  ↓
ACTIVE
  ↓
CLOSED
Enter fullscreen mode Exit fullscreen mode

Participant:

Available
    ↓
Registered
    ↓
Playing
    ↓
Submitted
    ↓
Score Updated
    ↓
Completed
Enter fullscreen mode Exit fullscreen mode

45. Complete Participant Flow 

Participant visits website
          ↓
      Register
          ↓
    Account created
          ↓
 Participant ID generated
          ↓
       Login
          ↓
 Participant Dashboard
          ↓
     View Games
          ↓
 Select available game
          ↓
     Register Game
          ↓
       Play Game
          ↓
    Submit Game
          ↓
 Score = 0 initially
          ↓
 Super Admin evaluates
          ↓
 Score updated
          ↓
 Points calculated
          ↓
 Leaderboard updated
          ↓
 Participant sees result
Enter fullscreen mode Exit fullscreen mode

46. Complete Admin Flow 

Super Admin Login
       ↓
Admin Dashboard
       ↓
Manage Participants
       ↓
Manage Games
       ↓
Participants Register
       ↓
Participants Submit Games
       ↓
Admin Views Submissions
       ↓
Admin Updates Scores
       ↓
Points Updated
       ↓
Leaderboard Updated
       ↓
Final Top 3
Enter fullscreen mode Exit fullscreen mode

47. Event-Day Workflow

The system should be designed for fast operation during the event.

Before Event 

Create games
Configure maximum scores
Check participant registration
Test admin dashboard
Test game registration
Test score updates
Take database backup
Enter fullscreen mode Exit fullscreen mode

During Event 

Participant registers
        ↓
Participant joins game
        ↓
Participant submits game
        ↓
Admin checks submission
        ↓
Admin updates score
        ↓
Leaderboard updates
Enter fullscreen mode Exit fullscreen mode

After Event 

Close games
     ↓
Verify scores
     ↓
Verify leaderboard
     ↓
Confirm Top 3
     ↓
Distribute goodies
     ↓
Final database backup
Enter fullscreen mode Exit fullscreen mode

48. Dashboard Statistics

Super Admin should see:

Total Participants
Active Participants
Disabled Participants

Total Games
Active Games
Closed Games

Total Registrations
Total Submissions

Total Points
Top 3 Participants
Enter fullscreen mode Exit fullscreen mode

49. Performance Requirements

The system does not require complicated infrastructure.

Expected scale:

Participants: ~900
Games: ~10
Registrations: ~9,000 maximum
Results: ~9,000 maximum
Enter fullscreen mode Exit fullscreen mode

A small PostgreSQL instance can easily handle this workload.

The bigger concern is not database performance.

The important things are:

  • Correct database constraints
  • Good validation
  • Reliable authentication
  • Backups
  • Stable hosting
  • Simple admin UI

50. Recommended Infrastructure

Simple production setup:

                Internet
                   │
                   ↓
             Web Application
                   │
                   ↓
             Node.js API
                   │
                   ↓
              PostgreSQL
Enter fullscreen mode Exit fullscreen mode

Optional:

Participant Photo
       ↓
Cloudinary

Email
       ↓
Email Provider
Enter fullscreen mode Exit fullscreen mode

For this event, avoid unnecessary services such as:

RabbitMQ       ❌
Redis          ❌
Kafka          ❌
Microservices  ❌
Kubernetes     ❌
Elasticsearch  ❌
Enter fullscreen mode Exit fullscreen mode

A simple application is easier to maintain and safer during an event.

51. Backup Strategy

Because this system contains participant and game results, backups are important.

Recommended:

Before Event
     ↓
Database Backup
     ↓
During Event
     ↓
Periodic Backup
     ↓
After Event
     ↓
Final Backup
Enter fullscreen mode Exit fullscreen mode

At minimum, keep a reliable database backup before the event begins.

52. Security

The system should include:

  • HTTPS
  • Password hashing
  • Secure authentication tokens/cookies
  • Role-based authorization
  • Input validation
  • Rate limiting for authentication
  • Server-side score validation
  • Unique database constraints
  • Secure environment variables
  • Database backups
  • Protection against unauthorized admin access

Never put:

DATABASE_URL
JWT_SECRET
EMAIL_PASSWORD
CLOUDINARY_SECRET
Enter fullscreen mode Exit fullscreen mode

inside frontend code.

53. What Participants Can See

Participants should have a clean experience.

Dashboard
│
├── My Profile
│
├── Available Games
│
├── My Games
│
├── My Results
│
└── Leaderboard
Enter fullscreen mode Exit fullscreen mode

They should not see admin functionality.

54. What Super Admin Can See 

Admin Dashboard
│
├── Participants
│
├── Games
│
├── Registrations
│
├── Submissions
│
├── Scores
│
└── Leaderboard
Enter fullscreen mode Exit fullscreen mode

55. Important UX Rules

Because this will be used during a live event:

Keep registration fast

Avoid unnecessary fields.

Show clear status

For example:

Registered ✓
Submitted ✓
Score Pending
Score: 85
Enter fullscreen mode Exit fullscreen mode

Prevent accidental actions

For example:

Are you sure you want to disable this participant?
Enter fullscreen mode Exit fullscreen mode

Make scores obvious 

Current Score: 85 / 100
Enter fullscreen mode Exit fullscreen mode

Make leaderboard easy to understand 

Rank | Name | Games | Points
Enter fullscreen mode Exit fullscreen mode

56. Error Handling

The system should show simple messages.

Instead of:

UNIQUE_CONSTRAINT_VIOLATION
Enter fullscreen mode Exit fullscreen mode

Show:

You are already registered for this game.
Enter fullscreen mode Exit fullscreen mode

Instead of:

FORBIDDEN
Enter fullscreen mode Exit fullscreen mode

Show:

You don't have permission to perform this action.
Enter fullscreen mode Exit fullscreen mode

Instead of:

BAD_REQUEST
Enter fullscreen mode Exit fullscreen mode

Show the actual problem.

57. Development Plan

Phase 1 — Project Setup 

Frontend
Backend
PostgreSQL
Prisma
Environment configuration
Enter fullscreen mode Exit fullscreen mode

Phase 2 — Authentication 

Register
Login
Logout
Role management
Protected routes
Enter fullscreen mode Exit fullscreen mode

Phase 3 — Participants 

Participant profile
Participant ID
Admin participant management
Enable/disable participant
Search
Enter fullscreen mode Exit fullscreen mode

Phase 4 — Games 

Create game
Edit game
Game status
Maximum score
Game listing
Enter fullscreen mode Exit fullscreen mode

Phase 5 — Game Registration 

Register for game
Duplicate protection
My games
Registration status
Enter fullscreen mode Exit fullscreen mode

Phase 6 — Game Submission 

Submit game
Submission status
Default score = 0
Admin submission list
Enter fullscreen mode Exit fullscreen mode

Phase 7 — Scores 

Admin score update
Score validation
Points calculation
Score update history
Enter fullscreen mode Exit fullscreen mode

Phase 8 — Leaderboard 

Total points
Ranking
Tie-breaker
Top 3
Enter fullscreen mode Exit fullscreen mode

Phase 9 — Dashboard 

Admin statistics
Participant dashboard
Game statistics
Recent activity
Enter fullscreen mode Exit fullscreen mode

Phase 10 — Testing

Test:

Registration
Login
Participant permissions
Admin permissions
Game registration
Duplicate registration
Game submission
Score update
Invalid score
Leaderboard
Disabled participant
Enter fullscreen mode Exit fullscreen mode

Phase 11 — Deployment 

Production database
Production backend
Production frontend
HTTPS
Environment variables
Backups
Monitoring
Enter fullscreen mode Exit fullscreen mode

58. Final Architecture 

                    ┌───────────────────────┐
                    │       WEBSITE         │
                    │   React / Next.js     │
                    └───────────┬───────────┘
                                │
                                │ HTTPS
                                ↓
                    ┌───────────────────────┐
                    │       BACKEND         │
                    │ Node.js + TypeScript  │
                    │       Express         │
                    └───────────┬───────────┘
                                │
                                ↓
                    ┌───────────────────────┐
                    │      PostgreSQL       │
                    │                       │
                    │ Users                 │
                    │ Participants          │
                    │ Games                 │
                    │ Registrations         │
                    │ Results               │
                    │ Score Logs             │
                    └───────────────────────┘
                         │             │
                         │             │
                         ↓             ↓
                    Cloudinary       Email
Enter fullscreen mode Exit fullscreen mode

59. Final Role Structure

There are only two roles.

SUPER ADMIN
│
├── Manage Participants
│   ├── View
│   ├── Search
│   ├── Edit
│   ├── Disable
│   └── Enable
│
├── Manage Games
│   ├── Create
│   ├── Edit
│   ├── Activate
│   └── Close
│
├── Manage Registrations
│
├── Manage Submissions
│
├── Update Scores
│
└── View Leaderboard
Enter fullscreen mode Exit fullscreen mode 
PARTICIPANT
│
├── Register
├── Login
├── View Profile
├── View Games
├── Register for Games
├── Submit Games
├── View Own Games
├── View Own Scores
├── View Total Points
└── View Leaderboard
Enter fullscreen mode Exit fullscreen mode

60. Final Feature Checklist

Super Admin

  • [x] Login
  • [x] Dashboard
  • [x] Manage participants
  • [x] Edit participants
  • [x] Disable participants
  • [x] Enable participants
  • [x] Search participants
  • [x] Create games
  • [x] Manage games
  • [x] Activate/close games
  • [x] View registrations
  • [x] View submissions
  • [x] Update scores
  • [x] Score defaults to 0
  • [x] Score validation
  • [x] Score update history
  • [x] View leaderboard
  • [x] Final Top 3

Participant

  • [x] Self registration
  • [x] Login
  • [x] Participant ID
  • [x] Profile
  • [x] View available games
  • [x] Register for games
  • [x] Submit games
  • [x] View registered games
  • [x] View submitted games
  • [x] View individual scores
  • [x] View total games
  • [x] View total points
  • [x] View leaderboard
  • [x] View current rank

61. Final Recommended Stack 

Frontend
React / Next.js
TypeScript

Backend
Node.js
Express
TypeScript

Database
PostgreSQL

ORM
Prisma

Authentication
JWT / Secure Cookie
Argon2 or bcrypt

Images
Cloudinary

Email
Resend / Brevo / SMTP

Hosting
Small VPS / Render / Similar

Version Control
Git + GitHub
Enter fullscreen mode Exit fullscreen mode

The architecture should remain a single application initially.

62. Core Principle

The most important principle for this project is:

Keep the system simple enough that the GDG Ranchi team can operate it easily during the event.

We do not need a complicated distributed architecture for approximately 900 participants.

The core system is simply:

Participants
      ↓
Games
      ↓
Registrations
      ↓
Submissions
      ↓
Scores
      ↓
Points
      ↓
Leaderboard
      ↓
Top 3 Winners
Enter fullscreen mode Exit fullscreen mode

Everything else exists to make this flow secure, reliable, and easy to manage.

63. Final System Summary 

                GDG RANCHI DEVFEST 2026
                         │
              Participant Registration
                         │
                         ↓
                  Participant ID
                         │
                         ↓
                  Participant Login
                         │
              ┌──────────┴──────────┐
              ↓                     ↓
        View Available Games    View Leaderboard
              │
              ↓
        Register for Game
              │
              ↓
          Play Game
              │
              ↓
        Submit Game
              │
              ↓
        Score = 0 initially
              │
              ↓
         SUPER ADMIN
              │
              ↓
         Update Score
              │
              ↓
        Calculate Points
              │
              ↓
          Leaderboard
              │
              ↓
          ┌───┴───┐
          ↓       ↓
       Rank 1   Rank 2   Rank 3
          │       │       │
          └───────┴───────┘
                  ↓
             TOP 3 WINNERS
Enter fullscreen mode Exit fullscreen mode

Final Scope

2 roles

6 core database concepts

Users
Participants
Games
Registrations
Results
Score Logs
Enter fullscreen mode Exit fullscreen mode

1 backend

1 PostgreSQL database

1 participant flow

1 leaderboard

No unnecessary microservices.

Top comments (0)