Customer pages
Present the restaurant, food highlights, private events, visit information, and booking-data notice.
Community / App case study
Yaelitos
A mobile-first restaurant website with a Supabase booking-request pipeline, Turnstile checks, private staff and owner tools, request-status updates, audit activity, CSV export, and customer-data anonymization.
Restaurant website and booking-request workflow
- HTML
- CSS
- JavaScript
- Supabase
- Turnstile
01 / Overview
What it’s built for.
Let customers send complete booking requests while staff review and track them through a private dashboard.
Who it serves
Restaurant customers, invited staff, and the business owner.
02 / Features
Inside the app.
Booking requests
Validate the request, check Turnstile, store a Pending record, and show a reference with optional contact fallbacks.
Staff handoff
Invited staff update statuses; owners manage access, export CSV, inspect activity, and anonymize customer details.
03 / Workflow
From task to outcome.
A customer completes the on-page request and Turnstile check.
The Edge Function validates, rate-limits, and stores the Pending request.
The customer receives a request reference.
Staff review and update the request; owners oversee access and retained data.
04 / Technical layers
How the pieces work.
HTML · CSS · JavaScript
Static customer pages and the staff dashboard use approved restaurant content and assets.
Supabase Edge Functions
Submission, staff management, and exports use validation, origin checks, and authorization.
Supabase · Staff profiles
Pending requests and audit activity are stored behind private staff/owner access; anonymous direct table access is excluded.
Turnstile · Quotas · Retention job
Idempotency and per-IP limits protect submissions; the documented workflow includes retention and anonymization.
05 / Limitations
What to keep in mind.
- Requests require staff review and do not automatically confirm a booking.
- Online ordering, payments, automatic capacity decisions, and automated customer notifications are outside the documented scope.
- End-to-end business acceptance requires the configured backend and staff walkthrough.
06 / Evidence
Follow the source.
These descriptions were reviewed against the linked source snapshot on October 12, 2026. Repository code and documentation may evolve after this review.