Special Delivery Presents

Research and architecture plan for a nightlife promoter site: event calendar, venues, ticket links and VIP capture.

Research
Next.js
Sanity
SEO

A pre-build teardown and plan for an events brand that needs a public calendar with detail pages, venue and recurring-series pages, private-event lead capture and a VIP list. No code yet by design: the open questions belong to the owner, so the work so far is research that makes the build cheap once they answer.

Problem

The problem

Event pages are the long-tail search surface for a promoter, so the site has to be discoverable per event, keep up with ticketing platforms, and still be simple enough for a promoter to run. Picking the wrong ingestion strategy up front would mean maintaining scrapers forever.

Solution

The solution

A competitive teardown of a comparable promoter site, fingerprinted from response headers and asset URLs to identify Next.js with ISR on Vercel and Sanity as the CMS. From that, a proposed architecture: CMS-managed events first, a scheduled ingestion sync only if the brand sells on more than one platform, and server routes for VIP and contact forms.

Highlights

Interesting details

Identified the reference site's stack from prerender and stale-time headers, DNS, and CDN image URLs, without access to its source.
Captured a concrete event data model from the reference feed that maps cleanly onto Event JSON-LD, a JSON feed and an ICS feed.
Documented and then argued against the reference's hourly multi-source scraper pipeline for a brand that likely uses one ticketing platform.
Planned SEO surface: JSON-LD on every page, generated Open Graph images, llms.txt, and JSON plus ICS alternate feeds.
Recorded design direction: dark-only, flyer-forward card grid with brand and venue filter chips.

Tech stack

Built with

Next.js App Router (proposed)
Tailwind CSS v4 (proposed)
Sanity CMS (proposed)
Vercel ISR (proposed)