Full-Stack Developer — Backend for Christian Discipleship Platform (Detailed Prototype Provided)

You can view and interact with the live prototype here: (link removed) You can view the public marketing site here: (link removed) I'm building Setting Captives Free Academy, a Christian discipleship platform. There are two pieces already built: A public marketing site — homepage, course pages, and an "Apply" page where a prospective student would enroll. The course app itself — fully prototyped and working. A complete front-end with student lessons, mentor review tools, and a "Living Margin" feature where mentors can annotate specific parts of a student's response. Right now these two are not connected, and neither one has a real backend. Everything runs in the browser with no accounts, no database, and no payments. What I need: a developer to build the real backend this needs, and to connect the marketing site's "Apply" flow through to the course app, so this goes from two disconnected prototypes to one real, multi-user, paid platform. What's already done for you: I'm providing two documents up front — a full Developer Handoff Package (architecture, exact build priorities, a known-issues list, file-by-file breakdown) and a Design Decisions Register (33 documented decisions explaining why the platform works the way it does). Please review both before submitting a proposal — they'll answer most of your early questions and should make scoping this fast and accurate. Scope, roughly in priority order: Connect the marketing site to the course app — a student who applies and is accepted on the marketing site should end up with a real account in the course app, not two disconnected systems. User accounts & authentication (students and mentors) Real database (replacing the prototype's browser-only storage) Payment processing (Stripe and/or PayPal) — each course is a $40 enrollment; payment should gate a student's access to their course Gender-matched, round-robin mentor assignment logic Two-way email notifications (every mentor/student exchange, not just first contact) Admin tools for reassigning students The prototype currently supports 5 lessons of a 40-day course, with more being written and added on an ongoing basis — your backend needs to accommodate that growth, not assume a fixed content set. Please review the attached documents and reference specific sections in your proposal — that tells me you've actually read them.