team-05-team-kk

WIAL’s global chapter platform: one admin, one template, AI-powered coach search, and one-click chapter launches.

Comment

Inspiration

WIAL operates as a global nonprofit, but its digital infrastructure did not reflect that reality. Each chapter needed local autonomy, but WIAL Global also needed consistent branding, shared tooling, and a way to launch and support chapters without rebuilding the same website and workflows over and over.

What stood out to us was that this was not just a website problem. It was an operations problem, a payments problem, a content problem, and a discovery problem. A coach in one country could be invisible to a client in another simply because their profile was written in a different language. We wanted to build something that made the network feel truly global.

What it does

WIAL ChapterHub is a multi-tenant platform for running WIAL’s global chapter network.

It gives WIAL:

  • A centralized admin dashboard for Global admins and chapter leads
  • Static chapter websites generated from one shared Astro template
  • One-click chapter provisioning with automatic GitHub and Cloudflare setup
  • AI-assisted site editing with branch previews and human approval before publish
  • Cross-lingual coach discovery powered by embeddings and vector search
  • Stripe Connect payments for enrollment, certification, dues, and events
  • Email campaigns, reminders, and analytics for ongoing chapter operations

In practice, that means WIAL can launch a new chapter faster, keep its global brand consistent, let chapters manage their own content, and help clients find the right coach even across language boundaries.

How we built it

We built the platform as a Turborepo monorepo with a clear separation of concerns:

  • apps/admin: a Next.js admin dashboard for WIAL Global and chapter leads
  • apps/chapter-{slug}: per-chapter Astro sites deployed to Cloudflare Pages
  • packages/template-core: the shared site template, layouts, and components
  • Supabase: PostgreSQL, Auth, Row Level Security, Edge Functions, Realtime
  • Gemini + pgvector: embeddings, semantic search, reranking, and AI content/edit workflows
  • Stripe Connect: chapter-level payments
  • Resend: campaigns and transactional email

The deployment architecture was a major part of the project:

  • Provisioning a chapter triggers backend automation that scaffolds a new chapter folder in GitHub
  • The system creates a dedicated Cloudflare Pages project, configures watch paths, and sets up the domain/DNS flow
  • Future redeploys happen by pushing a scoped deploy trigger commit, which Cloudflare rebuilds automatically

For AI editing, we built a safer review-based flow:

  • Start an editing session
  • Create a dedicated GitHub branch
  • Dispatch a GitHub Actions workflow that runs AI edits only inside that chapter folder
  • Generate a Cloudflare preview deployment
  • Let the user approve or reject before anything reaches production

For coach discovery, we embedded coach profiles into vector space and used semantic retrieval plus Gemini reranking so multilingual queries can still find relevant experts.

Challenges we ran into

One of the biggest challenges was that this was not a single feature build. It was a full platform with moving parts across frontend, backend, infrastructure, CI/CD, AI, payments, and database security.

Some of the hardest parts were:

  • Designing a chapter architecture that was reusable but still customizable
  • Automating provisioning across GitHub, Cloudflare Pages, and DNS without making the flow brittle
  • Building AI editing in a way that was useful but still safe enough for production content
  • Keeping chapter data isolated correctly with role checks and Row Level Security
  • Making semantic search actually valuable instead of just technically impressive
  • Connecting payments, receipts, reminders, and reporting into one coherent workflow

A recurring challenge was resisting the temptation to build disconnected demo features. We had to keep turning separate capabilities into one operational system.

Accomplishments that we're proud of

We are most proud that the project feels like a real platform, not just a hackathon prototype.

Highlights:

  • One-click chapter provisioning that handles repo scaffolding, Cloudflare setup, and deployment
  • AI editing with branch isolation, preview deployments, and explicit human approval
  • Cross-lingual coach matching powered by embeddings, vector search, and reranking
  • A shared chapter template that allows global consistency with chapter-level ownership
  • A payments system that maps cleanly to WIAL’s operational model
  • Real backend security with RLS, role-aware APIs, and protected server-side workflows
  • A static-site architecture that keeps public chapter sites fast and lightweight

What we learned

We learned that the hard part of multi-tenant systems is not just building features. It is defining boundaries clearly:

  • who can do what
  • what belongs in shared infrastructure vs chapter-owned content
  • when automation should act immediately vs when approval is required

We also learned a lot about integrating platform services in a practical way:

  • using GitHub as an automation surface, not just a code host
  • using Cloudflare Pages watch paths to make template propagation scalable
  • combining AI with strong constraints instead of treating AI as a black box
  • treating database policies and backend authorization as product features, not just backend details

Most importantly, we learned that a good nonprofit tool has to reduce operational burden, not add another dashboard with more work.

What's next for WIAL ChapterHub

Next, we would focus on making the platform even more useful in day-to-day chapter operations:

  • Integrate Cloudflare Analytics API for real per-chapter traffic reporting
  • Expand payment options beyond Stripe Connect
  • Improve AI content generation with stronger chapter context and reusable brand voice controls
  • Build a richer knowledge layer around WIAL resources, journals, and certification content
  • Continue strengthening accessibility, multilingual support, and chapter onboarding flows
  • Support more automation for chapter operations without removing human approval where it matters

The long-term goal is for WIAL ChapterHub to become the operating system for WIAL’s global chapter network.

Built With

Share this project:

Updates