WEB PLATFORM · HOSPITALITY · 2025—26
Elevate Events
From discovering a venue to planning an event.
01 / Context
The problem
An event website needs to present its venues clearly and connect discovery to booking and membership workflows.
02 / Response
The product response
The public frontend contains venue, gallery, booking, and membership components. The Flask backend separates event, booking, membership, and user routes and models.
03 / Contribution
My role
Public frontend and backend repositories are owned by Ubaida Dib. The CV separately records Web Developer & Media Manager at Elevate Events GmbH from February 2026, covering WordPress, React, JavaScript, and digital content.
04 / Architecture
How the pieces connect
- 01React + Vite frontend
- 02Flask route blueprints
- 03SQLAlchemy domain models
- 04Environment-configured database
05 / Execution
The engineering challenge
Keeping presentation and domain workflows separate. The public frontend README references Next.js, while package.json and the source use Vite; the case study follows the code.
06 / Result
Outcomes & perspective
An inspectable frontend/backend implementation. The repositories need hygiene and deployment review before they can substantiate a production-readiness claim.
07 / Reflection
A lesson from the work
Documentation should describe the implementation that a reviewer can actually inspect. Framework names alone are not evidence of architecture quality.
08 / Evidence
Evidence & scope
Source: public repository trees, package.json, requirements.txt, and api/main.py, inspected September 2026. The backend includes a SQLite fallback; a PostgreSQL production deployment was not independently verified.