Eagle
Portland

A recurring night is stored once — an anchor date plus a rule — and expanded server-side into a rolling 90-day window of real occurrences. Biweekly nights re-align to the anchor event's own week, so a night created on a Tuesday stays locked to that Tuesday's cadence instead of drifting. Every date resolves against the venue's own timezone, not whatever server happens to render the page.

// Sanity's date field is timezone-less — this pins every
// occurrence to 835 N Lombard, not the server's clock.
const VENUE_TIMEZONE = 'America/Los_Angeles'
export function dateKey(d: Date): string {
  return new Intl.DateTimeFormat('en-CA', {
    timeZone: VENUE_TIMEZONE,
  }).format(d)
}

Ships correctly across DST, timezones, and legacy recurrence rules.

A single template field switches the entire page layout: Default for a standard night, Poster for a full-bleed hero with a configurable overlay, Timeline for a multi-round tournament, Custom for a one-off page that needs its own shape entirely. One CMS, four genuinely different page shapes, zero custom code per event.

One field decides the entire call to action per event: informational only, a free in-house guest list, an external ticket link, or both at once.

Capacity is staff-editable, but the submit path doesn't yet stop RSVPs once a night is full — a wired field, not yet an enforced cutoff.

Every client's ID is a deterministic hash of their email — not an auto-incrementing number. An RSVP, a contact form and a bulk spreadsheet import from the same person all resolve to the same record automatically. For the harder case — same person, different email — the system doesn't guess: a name-and-phone match only flags a possible duplicate for a human to confirm.

Zero-duplicate identity for the common case, human judgment kept for the ambiguous one.

Every unsubscribe link is signed with HMAC-SHA256 and verified with a timing-safe comparison, not a plain equality check that can leak the correct signature to an attacker one character at a time. No token table to maintain — the link verifies itself against a server secret.

Any staff member can flag a guest as barred; only an admin can lift it. Every action is designed to create its own incident record — who did it, when — not a boolean that silently flips.

The underlying client dataset is being rebuilt following a security-driven reset, and the door check-in flow is mid-migration to the new data layer — this system is designed and shipped, not yet back in daily use.

A custom, admin-gated tool lets staff drag in a legacy spreadsheet and import it as real client records — reusing the same identity logic as the live site, so a bulk import can't fragment the directory the way a naive CSV import would.

A single boolean governs the sitemap's disallow rules and every page's indexing behavior at once. Launch readiness is a content decision, not a code deploy — the exact mechanism behind the site's current pre-launch state, ahead of the Fall 2026 public launch.

Every page ships real schema.org JSON-LD — venue details, individual events with parsed pricing and cancellation status, breadcrumbs — generated server-side from the same content editors already fill in. Everything is escaped before injection so a pasted character can't break out of its own script tag.

Social preview images generate at request time — page-specific image first, then a site default, then a branded fallback rendered live at the edge. Nothing on the site can be shared with an empty gray box where the image should be.