Family Shapes
Family Shapes is a multi-surface relationship platform for donor-conceived family ecosystems, spanning family, donor, clinic, and community experiences.
Narrative
Why it matters
Family Shapes tackles a messy and emotionally sensitive problem space: donor-conceived family ecosystems. The product is trying to hold together relationship discovery, privacy and consent, donor health stewardship, communication boundaries, and institutional workflows for clinics or cryobanks in one connected system. The live Supabase schema confirms that this is not just a landing-page story: the repo has real relationship, donor, organization, community, and media structures behind it.
What the product is
Family Shapes is a multi-surface relationship platform, not a single-purpose family-tree app. It spans family-facing tools, a dedicated donor experience, a clinic or cryobank SaaS layer, and a broader community surface for stories, forums, and resources. The linked Supabase schema shows those layers connect through family trees, donor profiles, organizations, memberships, invitations, forums, posts, and media tables rather than existing as disconnected marketing ideas.
System surfaces
Recipient or family platform
Family-facing onboarding, dashboards, family trees, people, and donor-relative connection management under privacy constraints.
Donor platform
A distinct donor experience for profile management, privacy controls, health updates, and communication settings.
Clinic or cryobank SaaS platform
Professional onboarding, organization dashboards, member management, and operational oversight for institutions.
Community layer
Stories, forums, resources, and broader community support around donor-conceived family experiences.
Implementation stack
Frontend
- • React 18
- • TypeScript
- • Vite
- • Tailwind CSS
- • Radix / shadcn-style UI primitives
Backend and data
- • Supabase Auth
- • Postgres
- • Edge Functions
- • Row-level security
- • Migration-first schema workflow
- • Linked remote type generation
Visualization
- • XYFlow / React Flow
- • Dagre
- • ELK
- • D3
Quality and operations
- • Playwright end-to-end coverage
- • Docs-first project governance
- • Permissions and privacy hardening
Evidence
24 artifacts grouped by type so each kind of proof can be scanned on its own.
Data models
7 artifactsCommunity Content And Media Model
Donor Boundary and Health Model
Donor Profile And Connection Model
Organization and Oversight Model
Organization Membership And Oversight Model
Relationship Graph And Access Model
Relationship Graph Core
Workflows
3 artifactsImages
7 artifacts
imageClinic or cryobank surface for professional donor oversight.
imageCommunity surface for stories, forums, and resources.
imageDonor surface focused on privacy, transparency, and control.
imagePublic home or umbrella entry point for the overall Family Shapes product.
imageSigned-in clinic or organization dashboard (`Rainbow Family Clinic`) showing organization metrics and operational overview.
imageSigned-in donor dashboard showing donor profile completeness, privacy level, and health-update status.
imageSigned-in family dashboard showing family-tree stats, privacy settings, and linked organizations.
Chats
1 artifactNotes
6 artifactsConnected references
Key dates
Initial repo setup established Family Shapes as an active product build rather than a concept stub.
Family-tree visualization, people, connections, Supabase, and RLS gave the project its core relationship-graph shape.
Interactive tree builder, organization maturity, donor portal, onboarding, and end-to-end testing made the product feel like a real ecosystem platform.
The collaborator and invitation model became a first-class concern, showing how central privacy and access control are to the product.
The roadmap and changelog show explicit movement toward clearer family, donor, and SaaS boundaries plus continued RLS hardening.