University Event Management Application
Eventity is developed to provide a centralized system for managing university events, vendor participation, gym sessions, court reservations, workshop approvals, conference management, trip registrations, loyalty programs, and communication among students, staff, professors, vendors, and the Events Office.
The goal of this system is to streamline event operations, automate approval cycles, ensure accurate role verification, provide structured registration workflows, and enhance the overall event participation experience for the university community.
The system is functional on both frontend and backend with full connectivity to MongoDB.
The following components are fully operational:
- User authentication (registration, login, logout)
- Verification emails for students, staff, TAs, and professors
- Vendor registration and document upload
- Event listing, filtering, searching, sorting
- Event registration and payment using Stripe
- Workshop, trip, bazaar, and conference creation
- Workshop approval cycle between Professors and Events Office
- Rating and commenting system
- Favorites feature
- Notifications and reminders
- Wallet refund logic
- Vendor participation workflows
- Court reservation system
- Gym schedule viewing and session registration
- Poll creation and voting
- Vendor loyalty program
- Reporting for total attendees and sales
- Document viewing and downloads
Known Issues / Limitations:
- Some frontend flows depend on manual refresh after backend operations
- Stripe webhook handling requires deployment for production reliability
- Some administrative views may require further UI refinement
- Form validations could be expanded
- File upload size and type restrictions can be enhanced
- Some asynchronous operations lack error boundary handling on the frontend
- Naming convention: camelCase for variables and functions.
- Models use PascalCase.
- Controllers organized by functional modules.
- Routes separated by domain (auth, events, vendors, admin).
- Folder structure follows Node.js MVC methodology.
Screenshots located in:
/assets/screenshots/
Backend:
- Node.js
- Express.js
- MongoDB (Mongoose ORM)
- Nodemailer
- Stripe
- JWT
- Multer
Frontend:
- ReactJS
- Axios
- React Router
- Context API
- Spline
Other:
- Stripe CLI
The system supports all major user groups. Features include:
- Role-based authentication
- Email verification
- Vendor onboarding
- Event browsing, filtering, sorting
- Rating and commenting
- Favorites
- Event creation and approvals
- Vendor participation workflows
- Payments via Stripe
- Wallet refunds
- Notifications
- Court reservations
- Gym session registration
- Voting polls
- Loyalty program
- Reporting
exports.registerUser = async (req, res) => {
try {
const { email, password, firstName, lastName, role, idNumber } = req.body;
const existingUser = await User.findOne({ email });
if (existingUser) return res.status(400).json({ message: "Email already registered" });
const hashedPassword = await bcrypt.hash(password, 10);
const user = new User({
email,
password: hashedPassword,
firstName,
lastName,
role,
idNumber,
isVerified: false
});
await user.save();
await sendVerificationEmail(user.email, user._id);
res.status(201).json({ message: "Registration successful. Verification email sent." });
} catch (error) {
res.status(500).json({ error: error.message });
}
};exports.loginUser = async (req, res) => {
const { email, password } = req.body;
const user = await User.findOne({ email });
if (!user) return res.status(400).json({ message: "Invalid credentials" });
if (!user.isVerified)
return res.status(403).json({ message: "Please verify your email before logging in." });
const passwordMatch = await bcrypt.compare(password, user.password);
if (!passwordMatch) return res.status(400).json({ message: "Invalid credentials" });
const token = jwt.sign({ id: user._id, role: user.role }, process.env.JWT_SECRET, {
expiresIn: "7d"
});
res.status(200).json({ token, user });
};exports.createWorkshop = async (req, res) => {
try {
const workshop = new Workshop({
...req.body,
professorId: req.user.id,
status: "Pending"
});
await workshop.save();
res.status(201).json(workshop);
} catch (error) {
res.status(500).json({ error: error.message });
}
};exports.payForEvent = async (req, res) => {
try {
const { amount, eventId } = req.body;
const paymentIntent = await stripe.paymentIntents.create({
amount: amount * 100,
currency: "egp",
metadata: { eventId, userId: req.user.id }
});
res.send({ clientSecret: paymentIntent.client_secret });
} catch (error) {
res.status(500).json({ error: error.message });
}
};exports.sendNotification = async (userId, message) => {
const notification = new Notification({
userId,
message,
createdAt: new Date()
});
await notification.save();
};cd server
npm install
npm run dev
cd client
npm install
npm start
PORT=3000
MONGO_URI=YOUR_MONGO_URI
JWT_SECRET=YOUR_JWT_SECRET
EMAIL_USER=YOUR_EMAIL
EMAIL_PASS=YOUR_EMAIL_APP_PASSWORD
STRIPE_SECRET_KEY=YOUR_STRIPE_SECRET_KEY
STRIPE_WEBHOOK_SECRET=YOUR_WEBHOOK_SECRET
CLIENT_URL=http://localhost:3001
POST /api/auth/signup
POST /api/auth/login
POST /api/auth/logout
GET /api/auth/me
GET /api/all
GET /api/events/:eventId
POST /api/events/:eventId/register
POST /api/workshops/create
GET /api/workshops/my-workshops
POST /api/vendor/apply
GET /api/vendor/my-requests
POST /api/payments/create-session
POST /api/payments/pay-event
POST /api/payments/refund-event
POST /api/payments/confirm
POST /api/payments/confirm-event-payment
POST /api/payments/confirm-event-payment-and-email
GET /api/reports/attendance
GET /api/reports/sales
POST /auth/register
POST /auth/login
GET /auth/verify/:id
GET /events
POST /events/register
GET /events/:id
POST /payment/pay
POST /payment/webhook
POST /vendor/apply
GET /vendor/my-requests
POST /workshops/create
GET /workshops/my-workshops
Postman was used for testing.
Screenshots stored under /assets/screenshots/.
Contributions are welcome and encouraged to help improve Eventity.
Please follow the contribution guidelines below to maintain code quality and consistency across the project.
Start by creating your own copy of the project:
- Click Fork on GitHub
- Clone your fork locally
git clone https://github.com//Eventity.git
All new work must be done on a dedicated feature branch.
This keeps the main branch clean and stable.
git checkout -b feature/
Examples:
feature/vendor-qr-generationfeature/enhanced-event-filteringfeature/fix-stripe-webhooks
To maintain code consistency:
- Use camelCase for variables & functions
- Use PascalCase for models & components
- Keep controllers modular and clean
- Separate logic into controllers, routes, and services
- Avoid bulky functions; break into helpers where needed
- Remove unused imports and commented-out code before submitting
Write meaningful commit messages describing what you changed.
Examples: git commit -m "Add: new event sorting by popularity" git commit -m "Fix: vendor application validation error" git commit -m "Update: improved email template for workshop approval"
Ensure that:
- Server runs without errors
- All major flows still work (login, signup, event creation, vendor apply, payments)
- Postman tests succeed
- App builds & loads properly
- UI updates reflect new features
- No console errors
Once your feature is ready:
-
Push your branch: git push origin feature/
-
Open a Pull Request describing:
- The feature or fix
- Screenshots if UI-related
- Postman tests if backend-related
- Any issues resolved
The maintainers will review your PR before merging.
- Do NOT commit
.envfiles or secrets - Do NOT commit to the
mainbranch directly - Avoid adding large images or binaries outside
/assets/ - Ensure your branch is up to date with main before submitting a PR
- Adding additional event filters or sorting
- Improving UI responsiveness
- Enhancing vendor workflows
- Expanding Postman test coverage
- Fixing validation or form errors
- Improving Stripe payment flow reliability
If you follow these guidelines, your contribution will be reviewed and merged efficiently.
- Stripe Documentation : Stripe documentation
- Nodemailer Documentation : Nodemailer Documentation
- MongoDB Documentation : Mongodb documentation
- YouTube tutorials related to Node.js and React : -Node.js -Express -Naming Conventions
- This project uses a modified version of a template created by [milicodes] on the Spline Community. Original template: https://link-to-template Created/edited using Spline (https://spline.design).
This project is licensed under the Apache 2.0 License.