Travel platform + operations dashboard
Morocco Immersion
My role
Full-stack engineer · product architecture · interface implementation
2026
A connected travel platform that gives guests a clear path from destination discovery to enquiry while giving the operations team one structured place to publish and manage the catalogue.
public experience routes
public API routes
admin API routes
01 · The problem
What needed to change
Trip, destination, departure, media, and enquiry content had to remain consistent across a public travel experience and a protected internal dashboard. The public site also needed to keep working while database-backed content was being prepared and reviewed.
02 · The constraint
The hard part
The difficult part was the boundary between editorial flexibility and reliable public data. Draft or archived records could not leak into selectors or public pages, and raw database records did not match the existing frontend contracts.
03 · Decisions
How I approached it
- 01
Kept the public interface behind typed DTOs and a dedicated API layer instead of coupling pages directly to Prisma records.
- 02
Used a controlled mock-to-API switch so the team could validate real endpoints without destabilizing the public catalogue.
- 03
Defined Published as the only public and selectable state, while preserving Draft and Archived references as admin repair warnings.
- 04
Built media, activity, reporting, and publishing workflows as connected operational concerns rather than isolated screens.
Technology