Elijah Kasujja

Case study · 09

Cassia Lodge

A Kampala lodge's Framer site rebuilt in Next.js, with direct booking requests, live room availability and a back office staff use to confirm stays and close rooms.

Year
2026
Role
Next.js rebuild of a Framer design, booking system, staff back office
Stack
Next.js · Hospitality · Bookings · Uganda
Live
cassialodge.com

Up close · The parts that move

Booking, without the back-and-forth. Full nights grey out as rooms fill, and the price follows the dates a guest picks.

Book a roomSingleDoubleTwinTriple1 left
MarchMTWTFSS1234567891011121314
Double · nightEstimated total$Request booking
One live calendar for roomsacross four room types, opened and closed by staff from the back office.

Confirmed in a click. The guest hears back either way.

GGrace NambiDouble · 9–12 MarchPending
DeclineConfirm

Every way in, one calendar. Desk staff enter the rest by hand.

WebsiteBooking.comPhoneWalk-in
Availability
Checked twice.Every request is checked against availability again on the server, so a page left open can't overbook a room.

01 · The brief

What the client needed.

Cassia Lodge already had a design in Framer. The rebuild had to keep that design and add what it couldn't do on its own: direct booking requests against real room availability, and one place for staff to confirm, decline or record stays that arrive by phone, email, walk-in or Booking.com.

02 · Discovery & IA

Structure, audience and sitemap.

The public structure stayed close to the Framer original: rooms, services, gallery and contact, with three service pages for the restaurant, meetings and events, and weddings. The new work was behind it. Four room types with 28 rooms between them became the basis of an availability model, and a back office grew around how staff actually take bookings.

Sitemap · cassialodge.com

07 public routes · 03 staff surfaces

Home //rooms/service/gallery/contact/facilitiesrestauranteventsweddings/SERVICE-DETAILS/[SLUG] · MENUS AS PDFSTAFF · NOINDEX/admin/bookingsPending · Confirmed · Past · Declined/adminClose rooms · set thresholds/staff-guidePractice copies on made-up dataAPIbooking · availability · contactBOOKING LIFECYCLEGuest request → staff confirm or decline → guest emailed → deleted a year after check-outPhone, email, walk-in and Booking.com stays are entered by hand into the same calendar.
  • ·Four room types and 28 rooms make up the availability model. Fully booked nights grey out in the calendar, and 'Only N left' appears once a room type falls below a threshold staff set.
  • ·Every public page is prerendered. Only the booking, contact and availability endpoints run on the server, and the booking endpoint checks availability again, so a stale page can't overbook.
  • ·Guest-facing availability is cached for 30 seconds and never exposes who booked.

03 · Wireframes & UX

From wireframes to prototype.

I wireframed the booking request before any other page, because every page ends in it. The questions were what a guest sees when a room type is nearly full, how a fully booked night shows in the calendar, and how to show a likely total without promising a confirmed price.

Booking request wireframe

Mid-fi · closes every page

Photograph · Book your stayRoom typeSingleDoubleTwinTriple · 1 leftDates1234fullfull7891011full131415161718192021Guest detailsMessageSummaryDouble · 3 nightsEstimated totalRequest booking0102030405
  1. 01Room type first, so the calendar can show that type's availability
  2. 02'Only N left' appears once a type falls below the threshold staff set
  3. 03Fully booked nights are greyed out, never hidden
  4. 04Estimated total (rate × nights), framed as an estimate, not a price
  5. 05A request, not a payment: staff confirm and the guest is emailed

04 · Outcome

What changed after launch.

The rebuild went live at cassialodge.com. Every public page is prerendered, and only the booking, contact and availability endpoints run on the server, which checks availability again before accepting a request so a stale page can't overbook. Staff confirm or decline from the back office, the guest gets an email either way, and bookings are deleted automatically a year after check-out. A staff guide with practice copies of the admin pages lets new staff learn the system on made-up data.