Marriage & Family Bible Institute
Marriage & Family Bible Institute brings its public programme, enrollment journey, learning environment, commerce workflows, and operational administration into one production platform. I built the system across its public experience, protected portals, backend automation, data model, and deployment.
- Role
- Product architecture · Fullstack engineering · Platform delivery
- Stack
- React 18 · TypeScript · Vite · Tailwind CSS · Firebase Auth · Firestore · Cloud Functions · Stripe · Resend · TanStack Query · Zustand · PWA · Vitest

Context
The institute needed more than a public course website: enrollment, payment, protected learning, downloadable resources, support, and administration all had to operate as one coherent product.
Individual, couple, organization-student, organization-admin, and platform-admin journeys required distinct capabilities without weakening subscription, course, progress, or data boundaries.
Response
A pnpm monorepo separates the React application, Firebase Cloud Functions, and shared TypeScript contracts while keeping frontend and backend models aligned.
The public experience leads into Stripe-backed enrollment and resource purchases, while protected portals coordinate course chapters, reading and video completion, quizzes, progress, certificates, resources, invitations, and reporting.
Firebase Authentication, Firestore and Storage rules, callable functions, webhook processing, scheduled retries, and transactional email automation keep privileged operations behind explicit server and data boundaries.
Contribution
- Architected and built the responsive public site and the student, platform-admin, and organization-admin applications.
- Designed the course-management workflow for structured chapters, rich text, video, quizzes, exercises, media, faculty, and downloadable resources.
- Implemented authentication, subscription gates, role capabilities, organization membership, couple-account invitations, and protected data access.
- Built Stripe enrollment and resource-purchase flows, webhook reconciliation, purchase records, subscription lifecycle handling, and failure states.
- Delivered automated certificates, transactional Resend email, scheduled retries and reports, PWA behavior, deployment recovery, Firebase configuration, and production delivery.
Engineering challenges
- Enforcing role, ownership, organization, couple, purchase, and active-subscription rules consistently across navigation, Firestore, Storage, and Cloud Functions.
- Keeping Stripe payment intents, recurring subscription events, user entitlements, purchases, and webhook-processing records synchronized through asynchronous callbacks.
- Calculating dependable course completion across reading, video, and quiz pages while preserving resumable progress and issuing a certificate only when completion requirements are met.
- Supporting a large set of public and protected routes with theme parity, responsive layouts, lazy loading, recoverable deployments, and useful loading, empty, and failure states.
Delivered evidence
- Delivered a deployed end-to-end platform spanning discovery, enrollment, payment, learning, completion, certification, resources, support, and administration.
- Created dedicated student, platform-admin, and organization-admin experiences over shared course, user, progress, certificate, and resource data.
- Automated subscription activation, resource access, invitations, transactional email, certificate issuance, retries, cleanup, and scheduled reporting through Firebase Functions.
- Added focused tests for course UX, reading and quiz progress, invitation and email behavior, deployment safeguards, and source-policy boundaries.







Evidence and publication note
Technical scope verified from the clean local MFBI monorepo, Firebase configuration, security rules, deployment documentation, and the live service on 11 August 2026. Public screenshots were captured from mfbinstitute.org; the authenticated student dashboard was supplied by the project owner and uses demonstration identities. The private source repository is intentionally omitted, and no adoption or commercial-impact metrics are claimed.