zsty.us

Before / After · Case Study

OC Singles — a singles-events brand given a golden-hour home (and a C&D survived)

  • Events & Entertainment

Itzi runs singles events across Orange County under Orange County Social Events — a real community (1,100+ Instagram followers, a 630-member Facebook group) whose web presence was scattered across IG, Eventbrite, and Facebook. The build is a Next.js 16 events platform live on the real domain, with every event, photo, and testimonial ripped from the brand's actual public channels — no lorem ipsum, no stock couples. The design is a golden-hour system with signature motion (SunsetScroll, PhotoMosaic, a Heartbeat CTA). Mid-build, a trademark C&D arrived; the response was a surgical scrub that kept the event live under a placeholder name and a CI trademark-guard workflow so the banned mark can never re-enter the codebase.

“A community this warm shouldn't route through three platforms' chrome. And when the C&D landed, the answer was a scrub and a CI guard — not a takedown.”
ocsingles.events↗Repo → og-gitclaw/ocsingles-events↗
🔒ocsingles.events
jackiej.events — modern site

Receipts — measured

Numbers that moved.

0
Instagram followers behind the brand
was 0
0
Facebook group members
was 0
3
Platforms a visitor crosses to see events + book
was 3
  • Scattered IG / Eventbrite / FB presence → one platform at ocsingles.events
  • Real content rip: events, photos, testimonials from the brand's own channels
  • Trademark C&D handled with a surgical scrub — event stayed live throughout
  • CI trademark-guard workflow blocks the banned mark from ever returning

The story

Problem · Insight · Build · Outcome.

  1. 01 · Problem

    A real community with no owned front door.

    1,100+ IG followers and a 630-member FB group — and a funnel that required hopping IG bio → Eventbrite → Facebook to see what's on and book it. Nothing ranked, nothing was owned, and the brand's warmth was flattened by three platforms' chrome.

  2. 02 · Insight

    The community is the product — show the real one.

    Singles events live or die on 'will people like me be there?'. Stock photos answer it wrong. Ripping the brand's real photos, real testimonials, and real event history answers it honestly — and an owned domain lets 'singles events orange county' finally resolve to Itzi instead of an aggregator.

  3. 03 · Build

    Golden-hour system + real-content rip + the C&D interrupt.

    Next.js 16 + Neon on the real domain. SunsetScroll / PhotoMosaic / Heartbeat motion, event pages with real listings, testimonials verbatim. Mid-build, the trademark C&D: surgical scrub, placeholder event name, CI trademark-guard workflow — shipped without dropping the event.

  4. 04 · Outcome

    Live at ocsingles.events; brochures + SES the next phase.

    The platform is live on the brand's own domain with the real community on the page. Awaiting Itzi's printed brochures, remaining DNS tidy-up, and SES sending for event comms.

Architecture

One chain replaced by another. Receipts above.

Old stack
  • IG bio link
  • Eventbrite
  • FB group
  • No owned surface
↓
New stack
  • ocsingles.events (owned domain)
  • Next.js 16 + Neon
  • Golden-hour motion system
  • Real-content event pages
  • CI trademark guard

What changed

Grouped by what kind of system shipped.

Each claim ships with concrete evidence — env vars, table names, cadence chips. No marketing fluff.

Design

A golden-hour design system with signature motion

The brand sells warm evenings with strangers who might not stay strangers — so the site is built on sunset gradients and three named motion pieces: SunsetScroll (the hero sky shifts as you scroll), PhotoMosaic (real event photos assembling into the wall), and a Heartbeat CTA that pulses on the book action. All reduced-motion safe.

Before
Brand warmth lived only in IG photos; every owned surface was platform chrome.
After
A coherent golden-hour system that feels like the events do.
Retention

Real content, ripped from the brand's own channels

Every event, photo, and testimonial on the site came from the brand's actual Instagram, Eventbrite, and Facebook presence. No stock photography of models pretending to mingle — the people on the site are the community a visitor would actually meet.

  • Events + pricing pulled from live Eventbrite listings
  • Photo wall sourced from the brand's own IG
  • Testimonials carried over verbatim from public posts
Agent backbone

A trademark C&D survived with a surgical scrub + a CI guard

Mid-engagement, a C&D arrived over an event name. The response: a same-day surgical scrub of the mark across code, copy, assets, and metadata — the event itself stayed live under a placeholder name — and a CI trademark-guard workflow that fails any future commit containing the banned mark. Legal risk turned into a build gate.

Before
One angry letter could have taken the whole calendar down.
After
The mark is unrepresentable in the repo; the calendar never blinked.
  • Mark scrubbed across code, content, and metadata in one pass
  • Event continuity preserved — no dead links, no cancelled listing
  • CI workflow greps every push for the banned mark

← All rebuilds

OC Singles — a singles-events brand given a golden-hour home (and a C&D survived) — zsty.us