Whitefield Hotel

The Idea

Explore what a full-service luxury hotel's digital operations could actually look like as one system — guest-facing booking alongside the admin tools that run it, not two disconnected products.

The Problem

Most hotel websites are static brochures. The operational reality — room availability, restaurant reservations, gym and pool scheduling, admin oversight — usually lives in separate, disconnected systems (or a phone call).

The Solution

A single Next.js application covering the guest side (rooms, restaurant, gym, pool, events, gallery, booking flow) and the admin side (bookings, rooms, gym/pool/restaurant management, analytics, CMS, role-gated users), backed by Supabase for data and auth, Paystack for payment, and Resend for transactional email.

My Role

Solo — designed the Supabase schema (rooms, bookings, admin roles), built the guest booking flow (room selection → guest details → payment → confirmation) and the restaurant reservation flow, and built the admin dashboard (analytics charts, CMS editing, booking/room/user management).

Challenges

Wiring a booking flow that behaves correctly end-to-end — selection, guest details, payment, confirmation — while keeping every screen fully usable on demo/mock data before real payment credentials exist, and designing one admin data layer general enough to cover five different hotel domains without duplicating logic per section.

Status