The booking website for Amapas 353 and how it works underneath — every service in the stack, how a booking, a price and an email travel through them, how admin is guarded, and how a change goes live.
The stack at a glanceWhat amapas353.com is built from — every service, what it does for the site, what lives inside it, and where its console is.
A booking, end to endWhat each service does, in order, from a guest picking dates to the arrival emails — for a request from the website and for a booking made in the ChatGPT app.
Prices and availabilityHow the Worker turns the Rates page into the price a guest sees, where the open dates come from, and what the pricing agent adds.
Email in and outHow the site sends every email through Resend, and how mail to the domain is routed — guests' replies filed against their booking, platform emails screened, everything else forwarded.
The admin area, keys and recordsHow the admin area is guarded, where every key lives, what is written down when anyone changes something, and how to see what is switched on.
How a change reaches the live siteFrom a commit to the live Worker — the repository's layout, what runs on every push, the checks a change must pass, and where the reasons for each decision are written down.