Catcher Nelly — Athlete Recruiting Website and Client-Managed Content System

A young catcher needed a professional recruiting presence communicating identity, skills, achievements, schedule, media, and contact information to coaches — and it had to stay maintainable as her profile changed. A static page would be out of date within a season.

Designer and developer of the full site and its admin system — from creative direction through build, deployment, and family handoff.

• The athlete — her identity and achievements presented professionally to coaches
• Her family — the owners of the content, updating it as her profile evolves
• College coaches and recruiters — the audience the site must serve clearly

1. 01Discovery — what coaches need to see and what the family needs to change over time
2. 02Creative direction — “Built Behind the Plate”
3. 03Content structure — profile, statistics, highlights, schedule, gallery, contact
4. 04Build — public site plus admin system
5. 05Accessibility, structured data, and social-sharing pass
6. 06Deployment and family handoff

• Public recruiting site with centralized data so profile, statistics, schedule, and media stay consistent everywhere they appear
• Supabase-backed admin controlling schedules, instructor fields, athlete email, and profile content
• Schedule manager supporting image upload or manual entry
• Vercel deployment for the live site

• “Built Behind the Plate” — a cinematic direction built around the catcher's position rather than a generic sports template
• Content modeled around what changes (schedule, statistics, instructors, media) so updates never require a developer
• Accessibility improvements and mobile-responsive layout as requirements, not afterthoughts
• Structured data and social sharing so the profile presents well when coaches share it

Tools

• Modern front end
• Supabase-backed admin
• Vercel deployment
• Centralized data

Human Checkpoints

• Creative direction and content reviewed with the family before build
• Admin workflows tested against how the family actually updates content
• Every published change owned by the client, not the developer

• Modern front end with centralized data feeding every section
• Admin system with client-controlled updates: schedule manager, instructor fields, editable athlete email and profile
• Performance work to keep the media-heavy site fast
• Deployment on Vercel with a documented handoff

• Designing an admin system a non-technical family can own — resolved by modeling the admin around their real update tasks rather than raw database fields
• Presenting a young athlete professionally while keeping the family in control of every detail that appears publicly

• The site became more than a static athlete page. It became a system the family can update as schedules, instructors, statistics, media, and recruiting information change.

Live site

catchernelly.com

Additional evidence is pending verification and will be published once confirmed.

“The family owns the content system: schedules, instructors, statistics, media, and recruiting information are all client-controlled through the admin, with the update workflows built around how they actually work.”

Collect verified performance scores and a client testimonial, and keep expanding the admin system around how the family actually uses it.