The official frontend web application for IEEE YESS'25 (Yearly Engineering Students Summit), the largest engineering students summit organized by IEEE India Council and IEEE Kerala Section.
IEEE YESS'25 is the largest engineering students summit by IEEE, a collaborative initiative of IEEE LINK and IEEE Kerala Section. Scheduled for September 20th, 2025 at NIT Calicut, Kerala, this summit will bring together over 5,000 participants from across India, creating a platform for students to connect with industry professionals and enhance their professional development.
- Event Landing Page - Comprehensive information about YESS'25
- Ticket Registration - Seamless ticket booking with Razorpay integration
- Payment Processing - Secure payment handling with automatic verification
- Ticket Status Check - Real-time registration and payment status tracking
- Event Gallery - Highlights from previous YESS events
- Responsive Design - Optimized for all devices and screen sizes
- Admin Authentication - Secure login system with JWT tokens
- Ticket Management - Comprehensive ticket management system
- Add individual tickets with full validation
- Bulk upload via CSV with progress tracking
- Edit existing tickets - Complete ticket editing with form validation
- Real-time ticket filtering and search
- IEEE Verification - Bulk IEEE membership verification system
- Event Management - Create, update, and delete events with image upload
- Updates Management - Manage announcements and news
- Payment Resolution - Handle webhook failures and payment issues
- Invoice Generation - Send ticket invoices via email
- Data Analytics - Comprehensive ticket and registration analytics
- Environment-based Configuration - Automatic switching between development and production
- Real-time Updates - Live status updates and notifications
- File Upload Support - CSV processing for bulk operations
- Image Management - Integration with ImgBB for image hosting
- Progressive Web App - PWA capabilities with offline support
- SEO Optimized - Complete meta tags and Open Graph support
- React 19 - Latest React with modern hooks and features
- Vite - Fast build tool and development server
- React Router DOM - Client-side routing
- Tailwind CSS 4 - Utility-first CSS framework
- Framer Motion - Animation library for smooth interactions
- React Icons - Comprehensive icon library
- Lottie React - Lightweight animations
- AOS (Animate On Scroll) - Scroll-based animations
- React Slick - Carousel/slider components
- Swiper - Modern touch slider
- React Hook Form - Performant forms with easy validation
- Yup - Schema validation library
- @hookform/resolvers - Form validation resolvers
- Axios - HTTP client for API requests
- React Intersection Observer - Intersection Observer API wrapper
- PayU WebSDK - Payment gateway integration
- Razorpay - Primary payment processor
- Three.js - 3D graphics library
- Vanta.js - Animated backgrounds
- Three-stdlib - Three.js utilities
frontend/
βββ public/ # Static assets
β βββ images/ # Image gallery and media files
β βββ favicon files # PWA icons and favicons
β βββ manifest files # PWA configuration
βββ src/
β βββ components/ # Reusable UI components
β β βββ BgAnimation.jsx # Background animations
β β βββ TicketForm.jsx # Registration form
β β βββ UpdateTicketForm.jsx # Ticket editing form
β β βββ Header2.jsx # Navigation header
β β βββ LandingSection.jsx # Hero section
β β βββ AboutSection.jsx # About YESS section
β β βββ HighlightsSection.jsx # Event highlights
β β βββ ExploreEventsSection.jsx # Events showcase
β β βββ UpdatesSection.jsx # News and updates
β β βββ PartnersSection.jsx # Partner logos
β β βββ NewFooter.jsx # Site footer
β βββ pages/ # Page components
β β βββ Home2.jsx # Main landing page
β β βββ AdminLogin.jsx # Admin authentication
β β βββ TicketDetails.jsx # Admin ticket management
β β βββ AddTicket.jsx # Add single ticket
β β βββ AddBulkTickets.jsx # Bulk ticket upload
β β βββ BulkIEEEVerification.jsx # IEEE verification
β β βββ EventDetails.jsx # Event management
β β βββ AddEvent.jsx # Create events
β β βββ Updates.jsx # Updates management
β β βββ CheckStatus.jsx # Status checker
β β βββ PaymentCallback.jsx # Payment success handler
β β βββ PaymentCancelled.jsx # Payment failure handler
β β βββ About.jsx # About page
β β βββ Contact.jsx # Contact page
β β βββ Privacy.jsx # Privacy policy
β β βββ ToS.jsx # Terms of service
β β βββ NotFound.jsx # 404 error page
β βββ config/
β β βββ api.js # API endpoints configuration
β βββ assets/ # Static assets used by components
β βββ App.jsx # Main application component
β βββ main.jsx # Application entry point
β βββ index.css # Global styles
βββ package.json # Dependencies and scripts
βββ vite.config.js # Vite configuration
βββ tailwind.config.js # Tailwind CSS configuration
βββ vercel.json # Vercel deployment configuration
βββ README.md # Project documentation
- Node.js (version 18 or higher)
- npm or yarn package manager
- Backend API running (see backend repository)
-
Clone the repository
git clone https://github.com/ieeelink/yess25-webapp.git cd yess25-webapp/frontend -
Install dependencies
npm install
-
Environment Setup
# Copy environment template cp .env.development.example .env.development # Edit the environment file with your configuration # See ENVIRONMENT_SETUP.md for detailed instructions
-
Environment Variables Create
.env.developmentfile:VITE_API_BASE_URL=http://localhost:5000/api VITE_RAZORPAY_KEY_ID=your_razorpay_test_key VITE_IMGBB_API_KEY=your_imgbb_api_key
-
Start development server
npm run dev
-
Open your browser Navigate to
http://localhost:3000
# Development
npm run dev # Start development server
npm run dev:prod # Start development server in production mode
# Building
npm run build # Build for production
npm run build:dev # Build for development
# Other
npm run lint # Run ESLint
npm run preview # Preview production build locallyThe application uses environment-based configuration:
- Development:
.env.development - Production: Environment variables set in deployment platform
API endpoints are centrally managed in src/config/api.js:
- Automatic environment detection
- Configurable base URLs
- Comprehensive endpoint definitions
- Support for all CRUD operations
- Authentication-aware requests
- React plugin enabled
- Tailwind CSS integration
- Custom host and port settings
- Production optimizations
- Color Palette: Dark theme with red accents (#fe4a56)
- Typography: Nunito Sans font family
- Layout: Mobile-first responsive design
- Components: Reusable UI components with consistent styling
- Utility-first CSS framework
- Custom configuration for YESS'25 brand colors
- Responsive design utilities
- Dark mode optimized
- AOS: Scroll-based animations
- Framer Motion: Page transitions and interactions
- Lottie: Lightweight animations
- Custom CSS: Hover effects and transitions
- Secure payment processing
- Real-time payment verification
- Automatic callback handling
- Payment retry functionality
- Multiple payment methods support
- Automatic invoice generation
- Payment status tracking
- Failed payment recovery
- JWT-based authentication
- Secure admin routes
- Automatic token validation
- Session management
- Individual ticket creation - Add single tickets with comprehensive form validation
- Bulk CSV upload - Upload multiple registrations with progress tracking
- Ticket editing - Full-featured editing system with:
- React Hook Form with Yup validation
- Dynamic dropdown menus for institutions and courses
- "Other" option support with custom input fields
- Real-time form validation and error handling
- API integration with MongoDB ObjectId support
- IEEE membership verification - Bulk verification processing
- Payment status management - Track and update payment states
- Advanced filtering - Search by name, email, status, institution, IEEE membership
- Create and manage events
- Image upload with ImgBB integration
- Event categorization
- Real-time updates
- Invoice email system - Send ticket invoices directly to participants
- Automated email notifications
- Payment confirmation emails
- Bulk Tickets: Upload multiple registrations
- IEEE Verification: Bulk membership verification
- Webhook Resolution: Handle payment webhooks
- Template downloads available
- Tickets CSV: fullName, email, phone, gender, institution, course, yearOfStudy, foodPreference, isIEEEMember, ieeeMembershipNumber
- IEEE CSV: ieee_number, first_name, last_name, institution
- Images: JPEG, PNG, WebP for events and gallery
- Real-time validation during CSV upload
- Progress tracking for bulk operations
- Error reporting with detailed feedback
- Template downloads for proper formatting
- MongoDB integration with ObjectId support
The application is configured for Vercel deployment:
{
"rewrites": [
{
"source": "/(.*)",
"destination": "/index.html"
}
]
}npm run buildSet these in your deployment platform:
VITE_API_BASE_URL: Production API URLVITE_RAZORPAY_KEY_ID: Live Razorpay keyVITE_IMGBB_API_KEY: ImgBB API key
The frontend integrates with the following key API endpoints:
POST /api/admin/login- Admin login with JWTPOST /api/admin/changepassword- Change admin passwordGET /api/admin/data- Fetch all tickets and analytics
POST /api/admin/addticket- Create individual ticketPOST /api/admin/addbulktickets- Bulk ticket upload via CSVPUT /api/admin/update-ticket/:id- Update existing ticket (MongoDB ObjectId)POST /api/admin/generate-invoice/:id- Send invoice email
GET /api/colleges- Fetch institution/college listGET /api/updates- Fetch announcementsGET /api/events- Fetch events list
POST /api/admin/verifyieee/:id- Verify individual IEEE membershipPOST /api/admin/bulk-ieee-verify- Bulk IEEE verification
- MongoDB Integration: Full support for MongoDB ObjectIds
- JWT Authentication: Secure token-based authentication
- Error Handling: Comprehensive error responses with user-friendly messages
- Data Validation: Server-side validation with detailed error reporting
- Audit Trail: Change tracking for ticket modifications
-
β Advanced Ticket Editing System
- Complete ticket editing modal with React Hook Form
- Dynamic institution and course dropdowns with "Other" options
- Real-time form validation with Yup schema
- API integration with MongoDB ObjectId support
- Proper data mapping between display and server formats
-
β Enhanced Admin Dashboard
- Improved ticket filtering and search functionality
- Invoice email system with status tracking
- Better date formatting for timestamp display
- Responsive design optimizations
-
β API Integration Improvements
- Centralized API endpoint management
- Enhanced error handling and user feedback
- Authentication-aware requests with JWT tokens
- Support for CRUD operations on ticket data
-
β Form Enhancements
- Institution dropdown with searchable college list
- Course dropdown with predefined options
- Conditional field rendering for "Other" selections
- Improved validation messages and user experience
- Performance: Optimized form rendering and API calls
- Accessibility: Better form labels and error messaging
- Code Quality: Modular components with proper error boundaries
- Documentation: Updated with latest API endpoints and features
- ESLint configuration for consistent code style
- React hooks and modern JavaScript practices
- Component-based architecture
- Functional components with hooks
- Environment-based configuration
- Error boundary implementation
- Loading states and user feedback
- Responsive design principles
- SEO optimization
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
- Follow existing code style and patterns
- Test thoroughly on different devices and screen sizes
- Update documentation for new features
- Ensure responsive design compatibility
- Implement proper error handling and user feedback
- Use TypeScript-style JSDoc comments where applicable
- Follow React best practices with hooks and functional components
- Component Architecture: Modular, reusable components
- State Management: React hooks with proper dependency arrays
- Form Handling: React Hook Form with Yup validation
- API Integration: Centralized API configuration with error handling
- Styling: Tailwind CSS with consistent design tokens
- Performance: Optimized builds with lazy loading where applicable
This project is developed for IEEE YESS'25. All rights reserved by IEEE LINK and IEEE Kerala Section.
- Event Website: yess.ieee-link.org
- Email: yess@ieee-link.org
- Organization: IEEE LINK
- Event Partner: IEEE Kerala Section
- Event: IEEE YESS'25 (Yearly Engineering Students Summit)
- Date: September 20, 2025
- Venue: NIT Calicut, Kerala, India
- Expected Participants: 5,000+
- Organizers: IEEE India Council & IEEE Kerala Section
This project uses environment-based configuration to automatically switch between localhost and production backend URLs.
- Development: Uses
http://localhost:5000/apiwhen runningnpm run dev - Production: Uses
https://yess25-backend.up.railway.app/apiwhen building for production - Railway Deployment: Automatically uses production environment variables
- Copy
.env.development.exampleto.env.development - Update the values with your development keys
VITE_API_BASE_URL=http://localhost:5000/api
VITE_RAZORPAY_KEY_ID=rzp_test_xgawYkbdrfISRM
VITE_IMGBB_API_KEY=0e9cde7ae8a30c258f12071cc6a4ecedVITE_API_BASE_URL=https://yess25-backend.up.railway.app/api
VITE_RAZORPAY_KEY_ID=rzp_live_sTkXOTd2O2D904
VITE_IMGBB_API_KEY=0e9cde7ae8a30c258f12071cc6a4ecedContains production values as fallback
npm run dev
# Automatically uses localhost backendnpm run build
# Automatically uses production backendnpm run build:dev
# Uses localhost backend in buildRailway automatically detects the environment and uses the appropriate configuration:
- Set environment variables in Railway's project dashboard (not in files)
- Railway automatically sets
NODE_ENV=production - Fallback values in
api.jsensure the app works even without explicit env vars - No
.envfiles needed in the repository
- Go to your Railway project dashboard
- Navigate to Variables tab
- Add these variables:
VITE_API_BASE_URL:https://yess25-backend.up.railway.app/apiVITE_RAZORPAY_KEY_ID: Your live Razorpay keyVITE_IMGBB_API_KEY: Your ImgBB API key
All API endpoints are centralized in src/config/api.js:
- Import
API_ENDPOINTSfor predefined endpoints - Import
API_BASEfor custom endpoints - Environment info available via
getEnvironmentInfo()
- No more manual URL switching between development and production
- Environment-specific configuration (test vs live Razorpay keys)
- Centralized API endpoint management
- Railway-compatible - works seamlessly with Railway's deployment process
- Development logging - see current environment in browser console during development
The bulk IEEE verification feature processes CSV files containing IEEE membership data and matches them against registered tickets.
The uploaded CSV can have either format:
ieee_number,first_name,last_name,institution
99739023,ALEESHA,SHAMINS,College of Engineering-Perumon
100490042,Joshua,Bose,School Name,Member/Customer Number,Last Name,First Name
College of Engineering-Perumon,99739023,SHAMINS,ALEESHA
,100490042,Bose,Joshua- Method: POST
- Content-Type: multipart/form-data
- Field:
ieeeFile(the uploaded CSV/Excel file) - Headers: Authorization: Bearer {token}
{
"verified": 25,
"failed": 3,
"notFound": 15,
"total": 43,
"details": [
{
"ieee_number": "99739023",
"name": "ALEESHA SHAMINS",
"status": "verified",
"message": "IEEE membership verified and ticket updated"
},
{
"ieee_number": "100490042",
"name": "Joshua Bose",
"status": "not_found",
"message": "No matching ticket found for this IEEE member"
}
]
}// Parse CSV file (handle both formats)
const records = parseCsv(uploadedFile);
// Normalize to standard format
const normalizedRecords = records.map(record => ({
ieee_number: record['Member/Customer Number'] || record['ieee_number'],
first_name: record['First Name'] || record['first_name'],
last_name: record['Last Name'] || record['last_name'],
institution: record['School Name'] || record['institution']
}));const results = {
verified: 0,
failed: 0,
notFound: 0,
total: normalizedRecords.length,
details: []
};
for (const member of normalizedRecords) {
// Find matching ticket by IEEE number and name similarity
const ticket = await findMatchingTicket(member);
if (!ticket) {
results.notFound++;
results.details.push({
ieee_number: member.ieee_number,
name: `${member.first_name} ${member.last_name}`,
status: 'not_found',
message: 'No matching ticket found for this IEEE member'
});
continue;
}
// Verify IEEE number matches and update ticket
if (ticket.ieeeMembershipNumber === member.ieee_number) {
await updateTicketVerification(ticket._id, true);
results.verified++;
} else {
results.failed++;
}
}async function findMatchingTicket(member) {
// Strategy 1: Exact IEEE number match
let ticket = await Ticket.findOne({
ieeeMembershipNumber: member.ieee_number,
isIEEEMember: 'yes'
});
if (ticket) return ticket;
// Strategy 2: Name similarity + no IEEE number in ticket yet
const nameVariations = generateNameVariations(member.first_name, member.last_name);
ticket = await Ticket.findOne({
isIEEEMember: 'yes',
$or: nameVariations.map(name => ({
fullName: { $regex: name, $options: 'i' }
})),
$or: [
{ ieeeMembershipNumber: { $exists: false } },
{ ieeeMembershipNumber: '' },
{ ieeeMembershipNumber: null }
]
});
return ticket;
}- Flexible Format Support: Handles both template and official IEEE export formats
- Smart Matching: Uses IEEE number and name similarity for matching
- Detailed Results: Provides specific feedback for each record
- Bulk Processing: Efficiently handles large files
- Error Handling: Graceful handling of malformed data
- Validate file size (max 10MB)
- Sanitize CSV input
- Require admin authentication
- Log all verification activities
- Rate limiting for bulk operations
Complete documentation for the Mark Attendance feature with real-time Server-Sent Events (SSE) integration
The Mark Attendance feature allows administrators to mark attendance for multiple students in bulk by uploading a CSV file. The system uses Server-Sent Events (SSE) for real-time progress updates, providing instant feedback as each ticket is processed.
- β Bulk attendance marking via CSV upload
- π Real-time progress tracking with SSE
- π¨ Live visual feedback for each ticket
- π Statistics dashboard (success/skipped/failed)
- π Batch processing (20 tickets per batch)
- β‘ Instant status updates without page refresh
- Drag-and-drop or click-to-upload interface
- CSV file validation (must end with .csv)
- Automatic parsing of CSV data
- Preview of parsed data (first 5 entries)
- File removal option with reset functionality
- Format instructions displayed inline
- EventSource connection for live updates
- Sends CSV data as JSON to backend
- Listens for 8 different event types
- Handles connection errors gracefully
- Automatically closes connection on completion
- Progress bar with percentage and count
- π’ Green cards - Successfully marked attendance
- π‘ Yellow cards - Already marked (skipped)
- π΄ Red cards - Failed to process
- Batch indicator - Shows current batch being processed
- Live statistics - Updates in real-time
- Progress bar - Animated with smooth transitions
The backend sends 8 different event types:
{
"message": "Bulk attendance marking started",
"totalTickets": 100,
"timestamp": "2025-10-21T10:30:00.000Z"
}{
"batchNumber": 1,
"totalBatches": 5,
"batchSize": 20,
"startIndex": 1,
"endIndex": 20,
"timestamp": "2025-10-21T10:30:01.000Z"
}{
"ticketId": "YESS25001",
"index": 1,
"total": 100,
"status": "checking",
"timestamp": "2025-10-21T10:30:02.000Z"
}{
"ticketId": "YESS25001",
"yessTicketId": "YESS25001",
"fullName": "John Doe",
"email": "john@example.com",
"institution": "ABC College",
"index": 1,
"total": 100,
"status": "completed",
"attendanceMarked": true,
"attendanceMarkedAt": "2025-10-21T10:30:02.500Z",
"timestamp": "2025-10-21T10:30:02.500Z"
}{
"ticketId": "YESS25002",
"yessTicketId": "YESS25002",
"fullName": "Jane Smith",
"email": "jane@example.com",
"index": 2,
"total": 100,
"status": "already-marked",
"message": "Attendance already marked",
"timestamp": "2025-10-21T10:30:03.000Z"
}{
"ticketId": "YESS25003",
"index": 3,
"total": 100,
"status": "failed",
"error": "Ticket not found: YESS25003",
"timestamp": "2025-10-21T10:30:03.500Z"
}{
"batchNumber": 1,
"totalBatches": 5,
"completedTickets": 20,
"totalTickets": 100,
"successCount": 18,
"errorCount": 2,
"timestamp": "2025-10-21T10:30:05.000Z"
}{
"message": "Bulk attendance marking completed",
"totalTickets": 100,
"successCount": 95,
"errorCount": 3,
"skippedCount": 2,
"timestamp": "2025-10-21T10:30:30.000Z"
}-
Prepare CSV File: Create a CSV file with the following format:
ticketId YESS25001 YESS25002 YESS25003 -
Upload File: Navigate to "Mark Attendance" page from admin dashboard and upload your CSV file
-
Review Preview: Check the number of entries found and verify ticket IDs
-
Process Attendance: Click "Mark Attendance for X Entries" button and watch real-time progress
-
Review Results: After completion, review the summary with success/skipped/failed counts
Endpoint: POST /api/admin/mark-attendance-bulk
Headers:
Authorization: Bearer {token}
Content-Type: application/json
Request Body:
{
"tickets": [
{ "ticketId": "YESS25001" },
{ "ticketId": "YESS25002" }
]
}/src/pages/MarkAttendance.jsx- Complete implementation with CSV upload and SSE handling/src/config/api.js- AddedADMIN_MARK_ATTENDANCE_BULKendpoint/src/pages/TicketDetails.jsx- Added "Mark Attendance" navigation links/src/App.jsx- Added MarkAttendance route
- JWT authentication required for all operations
- Token validation on backend for SSE connection
- File type validation (only .csv accepted)
- XSS prevention (all user input sanitized)
- CORS configuration for SSE endpoints
Built with β€οΈ for the engineering student community by IEEE LINK