The website is part of the system, not a side project.
The venue website, e-commerce, and member sign-up — on the same system as everything behind the bar. When an event changes, the public page changes with it; no web developer in the loop.
The venue website
A public venue site built on the same spine as the register — the storefront and the point of sale are one system, not two vendors kept in sync by hand.
Self-serve account deletion with a cascade-correct member deletion, so a guest can remove their record cleanly.
Calendar feeds (ICS) for events the public can subscribe to.
Events & tickets, public-facing
Event pages update themselves — create an event and pricing, tiers, tickets, and tables render on the public page automatically.
An inline ticket panel with quantity caps and sold-out states, and a deep-link that autofills the reservation form.
Ticket purchase runs through a server-authoritative path; a guest can self-pay from the pass page. See Reservations & tables for the event and ticket engine.
Member sign-up
Public join straight from the site, and guest-to-member upgrade that preserves the guest's history.
A self-service member area with wallet passes, bookings, and a notification inbox. See Memberships & loyalty.
Galleries
Photo galleries with per-photo metadata and scoped public or private access behind signed URLs.
Built to be found
Canonical URLs, a scoped sitemap, and inline structured data — SEO discipline is part of the build, not an afterthought.
A dependency-free CSS build and build-time hardening keep the public pages fast and self-contained.