Ecoza Hill Retreat

Booking platform — 20 screens for review · 15 Sep 2026

Every page here is a plain HTML file — open it directly, there is no build step. All of them run on one generated token set with no compatibility layer. npm only regenerates assets/css/tokens.css from the TypeScript source and typechecks.

Bookings

Availability Drag across a row to book. 10 units × 14 nights, conflicts shown New booking One screen, 14 fields, Ctrl+Enter confirms Bookings Daily/monthly/range, drawer, quick confirm, PDF Booking detail Payments, messages, activity, cancel dialog Day sheet One date: arrivals, in house, departures, kitchen

Resort

Cottages & tents 10 units, capacity, rates, line-art placeholders Guests Phone-first search, outstanding per guest Guest profile Stay history, ledger, carried preferences

Money

Finance Invoices · Payments · Expenses Invoice Editable amounts, attribution, print Reports Overview · Occupancy · Revenue · Source Owner view Read-only, contact details redacted Orders Guest add-ons — scope pending Q5

System

Today One hero row, needs-you queue, activity Messages Sent log · Templates · Bulk send Settings Property · Messaging · Staff · Audit Design system Every component, both registers, greyscale test

Entry & edges

Sign in Lobby register — cream, serif, hill rule Reset password Lobby register Not found Points at the merged screens

Merged

cottages.html now redirects to inventory.html
tents.html now redirects to inventory.html
financial-overview.html now redirects to reports.html

Three screens were folded into others rather than kept thin. Old links still work.