Elevate Events
From discovering a venue to planning an event.
- Role
- Frontend and backend implementation
- Timeline
- 2026
- Type
- Web platform, hospitality
- Stack
- React, Vite, Flask, SQLAlchemy
The problem
An event website needs to present its venues clearly and connect discovery to booking and membership workflows.
What we built
The public frontend contains venue, gallery, booking and membership components. The Flask backend separates event, booking, membership and user routes and models.
My role
Web developer and media manager at Elevate Events GmbH from February to August 2026: feature work, troubleshooting and performance on the React and Flask/PostgreSQL platform, plus digital content and campaigns. The frontend and backend repositories are on my GitHub.
How it fits together
- React + Vite frontend
- Flask route blueprints
- SQLAlchemy domain models
- Environment-configured database
The hard part
Keeping presentation and domain workflows separate, so venue content can change without touching booking logic.
Where it stands
The site is live at elevate-eventsgmbh.de in English and German, and the frontend and backend code are in public repositories.
What I took from it
Documentation should describe the implementation a reviewer can actually inspect. Framework names alone are not evidence of architecture quality.
Sources and scope
Sources: the live site, and the public repository trees, package.json, requirements.txt and api/main.py, inspected September 2026.
Screens
