Event Frontend Implementation

A comprehensive map of every frontend file involved in the event system. Use this page to find where event features live in the bt-web-v2 codebase.

Page Files

Public Pages

Admin Pages

Companion Pages

Event Management Components

These components handle event CRUD, registration, and feedback forms.

FormComponents/ Reusable form primitives

Event Dashboard Components

These components make up the public event listing and the admin event dashboard.

Query Hooks

Both call getEvents() / getAll() which hit GET /events/.

Related hooks in src/queries/registrations.ts:

Event Form Schema

The admin event form validates through eventFormSchema:

Required Fields

Optional Fields

Custom Questions

customQuestions: z.array(
  z.object({
    id: z.string(),
    type: z.enum([
      'TEXT',
      'SELECT',
      'CHECKBOX',
      'UPLOAD',
      'WORKSHOP_SELECTION',
      'SKILLS',
    ]),
    question: z.string(),
    required: z.boolean(),
    options: z.array(z.string()),
    charLimit: z.number().optional(),
    questionImageUrl: z.string().optional(),
    participantCap: z.number().optional(),
    isSkillsQuestion: z.boolean().optional(),
  }),
).default([])

TypeScript Types

BiztechEvent

Core event type with 30+ fields:

• Identity: id, year, ename
• Display: description, partnerDescription, imageUrl
• Scheduling: startDate, endDate, deadline (all ISO 8601 strings)
• Config: capac, isPublished, isCompleted, isApplicationBased, nonBizTechAllowed
• Pricing: pricing: { members: number, nonMembers: number }
• Questions: registrationQuestions, partnerRegistrationQuestions
• Feedback: attendeeFeedbackQuestions, partnerFeedbackQuestions, attendeeFeedbackEnabled, partnerFeedbackEnabled
• Runtime: counts (populated by ?count=true query)

RegistrationQuestion

{
  label: string;
  questionId: string;
  type: string;        // TEXT | SELECT | CHECKBOX | UPLOAD | WORKSHOP_SELECTION | SKILLS
  required: boolean;
  choices?: string[];
  charLimit?: number;
  questionImageUrl?: string;
  participantCap?: number;
  isSkillsQuestion?: boolean;
}

FeedbackQuestion

{
  label: string;
  questionId: string;
  type: "SHORT_TEXT" | "LONG_TEXT" | "MULTIPLE_CHOICE" | "CHECKBOXES" | "LINEAR_SCALE";
  required: boolean;
  choices?: string[];
  scaleMin?: number;
  scaleMax?: number;
  scaleMinLabel?: string;
  scaleMaxLabel?: string;
}

DBRegistrationStatus

enum DBRegistrationStatus {
  WAITLISTED,
  REGISTERED,
  CHECKED_IN,
  CANCELLED,
  INCOMPLETE,
  ACCEPTED,
  ACCEPTED_PENDING,
  ACCEPTED_COMPLETE,
}

Constants

src/constants/questionTypes.ts

Registration question types:

enum QuestionTypes {
  TEXT,
  CHECKBOX,
  SELECT,
  UPLOAD,
  WORKSHOP_SELECTION,
  SKILLS,
}

src/constants/feedbackQuestionTypes.ts

Feedback question types and defaults:

enum FeedbackQuestionTypes {
  SHORT_TEXT,
  LONG_TEXT,
  MULTIPLE_CHOICE,
  CHECKBOXES,
  LINEAR_SCALE,
}
FEEDBACK_FORM_TYPES = { attendee, partner }
DEFAULT_OVERALL_RATING_QUESTION // Linear scale 1–10

src/constants/registrations.ts

Registration status labels, QR scan stages, table types:

REGISTRATION_STATUS = {
  REGISTERED,
  CHECKED_IN,
  WAITLISTED,
  CANCELLED,
  INCOMPLETE,
  ACCEPTEDCOMPLETE,
}
QR_SCAN_STAGE = { SCANNING, FAILED, SUCCESS }
SCAN_CYCLE_DELAY = 5000 // ms
ATTENDEE_TABLE_TYPE, PARTNER_TABLE_TYPE, APPLICATION_TABLE_TYPE

src/constants/companion-events.ts

Companion app event definitions (4 events configured):

• Blueprint 2025 — basic companion
• ProductX 2025 — basic companion
• Kickstart 2025 — with team and invest sub-pages
• Blueprint 2026 — full companion with profile, partner-database, quests, companies, MBTI, discover, connections sub-pages

Each entry specifies eventID, year, ChildComponent, optional pages (sub-routes), and options (theming, headers, schedule config).

Data Flow Patterns

Event Listing

events.tsx → useEvents() → GET /events/ → EventDashboard → EventCard[]

Event Creation

new.tsx → EventForm → eventFormSchema.parse() → POST /events/ → redirect to dashboard

Event Edit

edit.tsx → useAllEvents() → EventForm (prefilled) → eventFormSchema.parse() → PATCH /events/{id}/{year}

Registration

register/index.tsx → GET /events/{id}/{year} → AttendeeEventRegistrationForm → POST /registrations/

Feedback

feedback/[formType].tsx → GET /events/{id}/{year}/feedback/{formType} → EventFeedbackForm → POST .../feedback/{formType}

Related Pages

• Events System Overview — architecture and system dependencies
• Event Creation Flow — frontend-to-backend trace
• Event Data Model — complete field reference
• Event Image Upload — thumbnail upload pipeline
• Events and Registrations — registration dependency on events
• Admin Event Management — admin dashboard
• Events Service — all backend endpoints