PCM Family Reunion 2026

The challenge

A large family reunion spanning four days, multiple venues, and dozens of attendees runs on coordination, and coordination usually means a tangle of group texts, scattered spreadsheets, and “did everyone see that?” The PCM Family Reunion needed a single source of truth: one place where every family member could see the schedule, find the venues, sign up, settle event costs, and flag dietary needs.

The site had to handle several distinct jobs at once:

• Register each family member individually, capturing structured details (age bracket, t-shirt size)
• Coordinate payment for optional events and merchandise, with a way to track who paid for what
• Collect food preferences and allergy information so nobody got left out or put at risk
• Present a four-day itinerary, venue locations, and lodging clearly enough that no one needed to ask

The approach

This was the inverse of a static brochure site. Where a simple practice site needs to load fast and stay out of the way, this build needed to do things: capture data through multiple forms, manage interactive state, and organize a lot of information without overwhelming the visitor.

I built it as a single-page application with anchor navigation across eight sections, using an AI-assisted development workflow to move from requirements to working build efficiently. The complexity here wasn't visual polish. It was the number of moving, stateful pieces working together in one coherent interface.

What I built

• A single-page app with eight anchored sections and a fully responsive mobile menu
• A tabbed four-day itinerary, with each day's events and cost notes revealed on selection
• Three independent data-capture forms, each with its own schema:
  • Registration: per-person, with age-bracket and t-shirt-size selection (youth and adult ranges)
  • Payment confirmation: structured capture of name, amount, method, and what was paid for
  • Food & allergies: multi-select preference and allergy capture with an open notes field
• A manual payment-coordination flow (CashApp / Zelle) paired with the structured confirmation form, so organizers could reconcile who paid for what
• Three embedded Google Maps for the primary venues
• External booking integrations: deep links into Hilton and IHG reservation systems for the room blocks
• A built-in feedback form for issue reports and suggestions
• A full FAQ section reducing repeat organizer questions

Stack: React / Next.js, deployed on Vercel. The framework choice was driven by the build's needs: multiple forms, interactive state, and conditional content benefit from a component-based architecture in a way a static brochure site does not.

The outcome

The reunion went from “coordinate it across group chats” to a single web destination handling registration, payment tracking, dietary capture, and logistics in one place, and it did so without the performance penalty that usually comes with that much functionality on one page.

A 96 performance score on a single page carrying three data-capture forms and three embedded maps is the headline number here. Interactive, integration-heavy builds typically pay for that complexity in load time, and this one didn't.

The build demonstrates capability that transfers directly to client work: managing multiple form schemas and their data, handling interactive UI state, embedding third-party services, and organizing dense information into a clean, navigable, mobile-first experience, all delivered solo, end to end.

Why it matters for client work

SteadyPath showed a fast, polished, credibility-first build. PCM shows the other half of the range: a stateful, multi-form, integration-heavy site that captures and organizes real data. Between them, the pattern is consistent: custom-coded, modern-stack sites built to fit the job, whether the job is a clean professional presence or a complex coordination tool.