IEInclusiveEd ConnectSpecial education network Prepare accounts

Production roadmap

Make InclusiveEd Connect public, paid, and editable after launch

This page tracks launch tasks for the public website: domain, educator registration, protected profiles, uploaded materials, blogs, Zoom booking, and paid sessions.

Recommended production stack

What each service will do

The platform now has server storage, secure sign-in, file hosting, and payment processing; remaining work focuses on operations, review, and growth.

Code

GitHub

Keeps the site source safe, tracks edits, and lets future updates be published without rebuilding from zero.

Hosting

Vercel or Cloudflare

Makes the site public, connects the domain, protects environment keys, and publishes updates.

Database

Supabase or Neon

Stores users, educator profiles, materials, blog posts, bookings, reviews, and payment records.

Payments

Stripe

Processes paid sessions, receipts, refunds, platform fees, and provider payouts in production.

Files

Storage bucket

Stores diplomas, certificates, covers, lesson files, PDFs, DOCX files, and preview images.

Meetings

Zoom links

Connects booking requests to online consultations and stores confirmation status.

Live platform workflow

How the real site should work

  1. Account createdParent, student, or educator registers with secure authentication.
  2. Educator verifiedSpecialists add education, experience, and documents before their profile becomes public.
  3. Content publishedEducators upload materials, write blog posts, and manage their own public page.
  4. Family books supportParents choose a specialist, select Zoom time, and pay if the session is not free.
  5. Payment recordedStripe stores the payment, platform fee, provider payout, receipt, and booking status.
  6. Admin edits laterThe site owner can update pages, approve specialists, moderate content, and publish new versions.

Database structure

Core tables for the real platform

These records replace local browser storage when the site becomes public.

usersRole, name, email, account status, created date.
educator_profilesSpecialty, education, experience, languages, price, availability, Zoom link.
credential_documentsUploaded diplomas, certificates, licenses, and review status.
author_materialsTitle, description, file, cover, category, grades, visibility, paid/free.
blog_postsTitle, excerpt, full text, cover, category, published/draft status.
appointmentsParent request, specialist, time, Zoom status, lesson status.
paymentsStripe checkout, payment intent, total, platform fee, payout, receipt, refund status.
stripe_connect_accountsEducator payout account, onboarding status, charges enabled, payouts enabled.
payment_eventsVerified Stripe webhook events that update appointments, receipts, refunds, and payouts.
reviewsParent comments, rating, moderation status.

Payment readiness

What changes when Stripe is connected

Stripe Checkout is connected. The next production work is testing one paid booking, completing payout tasks, and finalizing legal/business payment policies.

Before payment

The family sees specialist price, platform fee, cancellation note, and total.

Checkout

Stripe Checkout securely collects card, Apple Pay, Google Pay, or other supported methods.

After payment

The booking becomes paid, the receipt is saved, and the specialist sees a confirmed request.

Provider payout

Stripe Connect pays verified specialists after completed sessions and platform review rules.

Refunds

Cancellations and refunds must update payment status, appointment status, and family receipts.

Security

Webhook signatures must be verified before changing any booking, payment, or payout record.

Launch checklist

Next steps before the site becomes public

Open admin review center