Full Stack MERN Meeting & Event Scheduler
Budget: ₹4,000 – ₹8,000 INR
Problem Statement: Build a Meeting & Event Scheduling Platform
This platform allows users to schedule, manage, and customize their meetings and events. It includes features like event creation, scheduling availability, participant management, and conflict resolution.
1. Landing Page
A public-facing landing page.
Ensure it is responsive for all devices.
2. Signup and Login Page
Signup:
Input fields for email, password, and username.
Basic validations (e.g., unique email, password strength).
Secure password hashing (e.g., using bcrypt).
Login:
Input fields for email and password.
Login authentication using JWT or session-based authentication.
3. Event & Meeting Management
Create & Manage Meetings
Users can schedule meetings.
Ability to edit, delete, activate, and deactivate meetings.
Users can view meeting schedules categorized as:
Upcoming Meetings
Pending Meetings
Canceled Meetings
4. Users can set their availability (like Calendly), specifying when they are available or unavailable & Conflict Handling
Users can configure availability settings for meetings and events.
Real-time conflict detection:
If an event is already scheduled for a time slot, the system prevents overlapping meetings.
Conflict alerts appear when a user tries to schedule an event at the same time as an existing one.
5. Event Creation & Customization
Events require essential details such as:
Event title, description, and date/time.
Manually added event link (Google Meet, Zoom, etc.).
Banner image and background color customization.
Password protection for events:
Users can set a password for an event.
Participants must enter the password to join.
6. Event Participation & Approval
Users can share event links with attendees.
6. Settings Page
Options for users to manage their account:
Update basic information (e.g., name, email, password).
On email and password updation the user should be logged out
7. Logout Feature
Provide a Logout button to securely end the user session.
8. Mobile Responsive Public Link Page
The public-facing sharable event/meeting page should
Be fully responsive, optimized for mobile viewing.
Use adaptive designs for different screen sizes.
Two display views
Add availability view: User can add there availability for the entire day
Calendar View: Similar to Google Calendar, showing all scheduled meetings.
Tech Stack
Frontend:
React.
Vanilla CSS.
Backend:
Node.js with Express.
MongoDB for database storage.
Hosting:
Deploy the frontend using Vercel/Netlify.
Deploy the backend using Render/Heroku.
Submission Guidelines
GitHub Repository: Include a README with:
Setup instructions.
Features implemented.
Demo credentials.
Live Demo Link: Host the app and share the live link.
Do's:
Always use raw/vanilla css.
Always use modular css.
Always structure your project properly.
Always use proper naming for variables and functions.
Always use some kind of basic validations for forms.
Use jwt auth mechanism.
You can use any toast library for showing toast. Design can be flexible for toast.
Your password should always be stored in encrypted form, always prefer any encrypting library to do that. Also password comparison should be done use the same encryption library.
Proper error handling should be there on the backend and frontend. Your backend should return a proper response in case anything goes wrong.
Search and Pagination should be implemented in the backend.
Don'ts:
Don't use any css library or frameworks
Don't store your passwords as plain string, it must be encrypted
Don't implement filtering, sorting or searching on the frontend
If your code is found to be copied from anywhere then your solution will not be considered for the evaluation
below is the figma link of site https://help.figma.com/hc/en-us/articles/360041003114-Import-files-to-the-file-browser
This platform allows users to schedule, manage, and customize their meetings and events. It includes features like event creation, scheduling availability, participant management, and conflict resolution.
1. Landing Page
A public-facing landing page.
Ensure it is responsive for all devices.
2. Signup and Login Page
Signup:
Input fields for email, password, and username.
Basic validations (e.g., unique email, password strength).
Secure password hashing (e.g., using bcrypt).
Login:
Input fields for email and password.
Login authentication using JWT or session-based authentication.
3. Event & Meeting Management
Create & Manage Meetings
Users can schedule meetings.
Ability to edit, delete, activate, and deactivate meetings.
Users can view meeting schedules categorized as:
Upcoming Meetings
Pending Meetings
Canceled Meetings
4. Users can set their availability (like Calendly), specifying when they are available or unavailable & Conflict Handling
Users can configure availability settings for meetings and events.
Real-time conflict detection:
If an event is already scheduled for a time slot, the system prevents overlapping meetings.
Conflict alerts appear when a user tries to schedule an event at the same time as an existing one.
5. Event Creation & Customization
Events require essential details such as:
Event title, description, and date/time.
Manually added event link (Google Meet, Zoom, etc.).
Banner image and background color customization.
Password protection for events:
Users can set a password for an event.
Participants must enter the password to join.
6. Event Participation & Approval
Users can share event links with attendees.
6. Settings Page
Options for users to manage their account:
Update basic information (e.g., name, email, password).
On email and password updation the user should be logged out
7. Logout Feature
Provide a Logout button to securely end the user session.
8. Mobile Responsive Public Link Page
The public-facing sharable event/meeting page should
Be fully responsive, optimized for mobile viewing.
Use adaptive designs for different screen sizes.
Two display views
Add availability view: User can add there availability for the entire day
Calendar View: Similar to Google Calendar, showing all scheduled meetings.
Tech Stack
Frontend:
React.
Vanilla CSS.
Backend:
Node.js with Express.
MongoDB for database storage.
Hosting:
Deploy the frontend using Vercel/Netlify.
Deploy the backend using Render/Heroku.
Submission Guidelines
GitHub Repository: Include a README with:
Setup instructions.
Features implemented.
Demo credentials.
Live Demo Link: Host the app and share the live link.
Do's:
Always use raw/vanilla css.
Always use modular css.
Always structure your project properly.
Always use proper naming for variables and functions.
Always use some kind of basic validations for forms.
Use jwt auth mechanism.
You can use any toast library for showing toast. Design can be flexible for toast.
Your password should always be stored in encrypted form, always prefer any encrypting library to do that. Also password comparison should be done use the same encryption library.
Proper error handling should be there on the backend and frontend. Your backend should return a proper response in case anything goes wrong.
Search and Pagination should be implemented in the backend.
Don'ts:
Don't use any css library or frameworks
Don't store your passwords as plain string, it must be encrypted
Don't implement filtering, sorting or searching on the frontend
If your code is found to be copied from anywhere then your solution will not be considered for the evaluation
below is the figma link of site https://help.figma.com/hc/en-us/articles/360041003114-Import-files-to-the-file-browser