zsty.us

Before / After · Case Study

OC Singles — a scattered social-media community given its own front door

  • Events & Entertainment

Itzi runs real singles events across Orange County — 1,100+ followers and a 630-member group — but seeing what's on and booking it meant hopping across three different platforms she didn't own. Now every event, photo, and testimonial lives on one warm, sunset-toned site at her own web address, and when a legal scare hit mid-build, the events never went offline.

“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

At a glance

What this rebuild covers.

  • Design

    Every photo and testimonial on the site is the real community from real events — no stock models pretending to mingle, so a visitor sees exactly who they'd actually meet.

  • Theme & color

    A golden-hour look built on sunset gradients, with the hero sky shifting as you scroll, event photos assembling into a wall, and a gently pulsing book button — all safe for visitors who prefer reduced motion.

  • Search visibility

    With a web address the brand owns, searches for Orange County singles events can finally land on Itzi's own site instead of a ticketing aggregator's listing.

  • Security

    When a trademark complaint arrived over an event name, the name was scrubbed the same day, the event stayed live, and an automatic check now blocks that name from ever slipping back onto the 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
  • 3 platforms → 1 site
  • 1,100+ followers, one home
  • 630-member group behind it
  • Legal scare survived — zero downtime

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.

For the technically curiousHow it was done
  1. 01

    Where it started

    The brand's entire web presence was rented: an Instagram profile with 1,100+ followers, event listings on Eventbrite, and a 630-member Facebook group. Seeing what's on and booking it meant hopping IG bio → Eventbrite → Facebook, nothing ranked in search, and the brand's warmth was flattened by three platforms' chrome.

  2. 02

    The content rip

    Instead of lorem ipsum and stock couples, the build started with a rip of the brand's own public channels: events and pricing pulled from the live Eventbrite listings, the photo wall sourced from the brand's actual Instagram, and testimonials carried over verbatim from public posts. The community on the site is the community a visitor would meet.

  3. 03

    The rebuild

    An events platform on the brand's own domain, running on our hosting platform with a managed database behind it. The design is a golden-hour system with three named motion pieces — SunsetScroll (the hero sky shifts as you scroll), PhotoMosaic (real event photos assembling into a wall), and a Heartbeat call-to-action that pulses on the book button — all reduced-motion safe.

  4. 04

    The cease-and-desist interrupt

    Mid-build, a trademark cease-and-desist arrived over an event name. The response was a same-day surgical scrub of the mark across code, copy, assets, and metadata — the event itself stayed live under a placeholder name with no dead links and no cancelled listing — plus a guard in the build pipeline that fails any future change containing the banned mark. Legal risk became a build gate.

  5. 05

    What runs now

    The platform is live on the brand's own domain with the real community on the page, and the funnel that used to cross three platforms now resolves to one owned site. Next phase: the owner's printed brochures, remaining domain tidy-up, and an email pipeline for event communications.

Architecture

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

What changed, with evidence

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 scattered social-media community given its own front door — zsty.us