cedar-eventhub

byDrashti Solanki

# EventHub — Event Management & Booking Platform Build a responsive web application called **EventHub**, an event discovery and ticket booking platform. ## User Roles The application must support three roles: ### 1. Customer Customers can: * Register and login. * Browse events. * Search events. * Filter events. * View event details. * Book tickets. * View booking history. * Cancel eligible bookings. * Manage their profile. * Receive notifications. ### 2. Organizer Organizers can: * Register and login. * Create events. * Edit their own events. * Publish events. * Cancel their own events. * Create ticket types. * Manage ticket availability. * View bookings for their events. * View attendees. * View event statistics. ### 3. Admin Admins can: * Access the admin dashboard. * Manage customers. * Manage organizers. * Manage events. * Manage bookings. * Manage event categories. * Manage support requests. * Manage FAQs. * View platform statistics. ## Authentication Implement: * Registration. * Login. * Logout. * Protected routes. * Role-based access. * Session persistence. Customer registration fields: * Full Name * Email * Phone * Password * Confirm Password Organizer registration fields: * Organization Name * Contact Person * Email * Phone * Password * Confirm Password Validation must handle: * Required fields. * Invalid email. * Duplicate email. * Weak password. * Password mismatch. * Invalid phone number. ## Authorization Customers must only access their own: * Profile. * Bookings. * Notifications. Organizers must only manage their own: * Events. * Ticket types. * Bookings. * Attendees. Admins can access platform-wide data. Do not rely only on hiding frontend buttons. Backend/API authorization must also prevent unauthorized access. ## Customer Dashboard Create a customer dashboard containing: * Upcoming bookings. * Recent bookings. * Favorite events. * Notifications. * Total bookings. * Confirmed bookings. * Cancelled bookings. Provide proper: * Loading states. * Empty states. * Error states. ## Event Discovery Create a public event listing page. Each event card should display: * Event image. * Event name. * Category. * Date. * Time. * Location. * Starting ticket price. * Organizer name. Users can: * Search by event name. * Search by organizer. * Filter by category. * Filter by location. * Filter by date. * Filter by price. * Sort by date. * Sort by price. Search and filters must work together. ## Event Details The event detail page must display: * Event image. * Event name. * Description. * Category. * Organizer. * Date. * Start time. * End time. * Location. * Address. * Available ticket types. * Ticket availability. * Event rules. * Cancellation policy. Provide a prominent **Book Now** action. ## UI Requirements The application must be responsive for: * Desktop. * Tablet. * Mobile. Use a consistent design system for: * Buttons. * Forms. * Cards. * Tables. * Modals. * Dropdowns. * Alerts. * Loading states. * Empty states. Do not allow horizontal overflow on normal mobile screens. ## Important Build the application with realistic relationships between: User → Organizer → Event → Ticket Type → Booking → Customer. Use realistic sample data so the complete workflow can be tested immediately. The implementation should prioritize functional correctness, data consistency, role-based permissions, validation, responsive behavior, and error handling rather than only visual design.