Remix

Make your own version of StudyHub LMS

Get an exact, working copy in your account, then change anything with chat.

Original by Bomor Samuel

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

Build StudyHub, a production-oriented, multi-tenant school learning management SaaS platform for thousands of schools. Use React, TypeScript, a responsive accessible UI, Supabase Auth, PostgreSQL, Supabase Storage and server-side Edge Functions. Use a clean premium blue-and-white design. Build a real working application, not just a landing page or static mockup.

MULTI-TENANCY: Every school is a tenant with its own branding, school code, administrators, teachers, students, parents, academic sessions, terms, classes, subjects, assignments, exams, documents, attendance, grades, announcements, billing and settings. Enforce school isolation at the database level using tenant_id and tested Row Level Security policies. Never trust a client-provided tenant ID or role. Check membership and authorization on the server for every protected operation. Keep service-role keys and AI secrets server-side.

ROLES: Platform super administrator; school administrator; teacher; student; parent/guardian. Implement role-specific dashboards and permissions. School administrators create classes, subjects, users and academic sessions. Teachers only manage assigned classes and subjects. Students only access their own enrolled classes and records. Parents only access linked children. Create unique usernames and school codes, bulk import users using CSV, issue secure activation links or temporary passwords, require password change on first login, and support secure resets. Never store or display plaintext passwords.

CLASSROOMS: Each class and subject has its own private workspace containing announcements, lesson materials, homework, assignments, discussion, StudyHub Docs, online meetings, attendance, CBT exams, grades, feedback and progress analytics. Support deadlines, file attachments, individual or group assignments, submission history, late submission settings, notifications and teacher feedback.

DOCUMENTS: Build an internal document editor with rich-text formatting, autosave, comments, version history, teacher templates, student submissions and export to PDF/DOCX. Protect documents by tenant, class and ownership. Support accessible reading and low-bandwidth usage.

GOOGLE MEET: Integrate the official Google Meet API using secure server-side OAuth and authorized accounts. Allow teachers to schedule lessons, create meeting spaces, save meeting URLs, set start/end times and send reminders. Display Join Meeting inside the correct classroom. Handle missing authorization and API errors gracefully. Never pretend a meeting was created if the API call failed. Provide a manual meeting-link option if API integration is not configured.

CBT: Build a secure examination engine with multiple choice, multiple select, true/false, short answer, fill in the blank and essay questions; question banks; randomization; shuffled options; timers; scheduling; autosave; resume after temporary disconnection; attempt limits; submission receipts; objective marking; accommodations; and configurable grading. Protect answer keys and unpublished exams from students. Enforce exam start/end rules server-side. Record audit events. Make reasonable best-effort anti-cheating controls without claiming a normal browser can prevent all cheating.

AI: Create an AI provider abstraction using server-side secrets and configurable models. Provide an AI study tutor, topic explanations, lesson summaries, revision notes, quiz generation, assignment drafting, question generation and rubric-based essay marking. Teachers must review generated questions before publishing. Automatically score objective answers deterministically. AI may suggest essay marks with rubric evidence, confidence and feedback; route uncertain or high-stakes marking to teachers. Preserve original submissions, model/version metadata, rubric, suggested mark and teacher overrides. Do not let AI silently finalize uncertain high-stakes results. Add rate limits, per-school quotas, cost tracking, abuse protection and graceful handling when no AI key is configured. Do not expose API keys to the browser.

RESULTS AUTOMATION: Calculate totals, weighted scores, percentages, configurable grades, subject averages, term summaries and report cards using deterministic, tested code. Each school configures its grading scale, academic calendar, subject weights and promotion rules. Generate draft teacher comments and class analytics. Detect missing marks and unusual results. Publish results only according to school approval settings. Maintain audit history for all changes and allow authorized corrections.

ADMIN AND BILLING: Build a platform-wide admin console to approve schools, configure subscription tiers, manage subscription status, view aggregate system health and usage, and suspend or reactivate accounts with audit logs. Each school admin sees only their school's billing, users, usage and settings. Add monthly/annual subscription workflows, invoices, renewal states, grace periods and payment-provider integration through verified server-side webhooks. Keep development billing in sandbox mode until configured. Never mark a payment successful based only on a browser redirect.

PARENT PORTAL: Allow authorized guardians to view linked children's homework, attendance, published results, report cards, announcements and teacher feedback. Require explicit verified school-controlled linking. Do not expose another student's information.

NOTIFICATIONS: In-app notifications and configurable email reminders for assignments, upcoming exams, missed deadlines, published results, announcements and online lessons. Queue background jobs, deduplicate notifications and retry failures safely.

DESIGN: Premium, modern, polished educational SaaS interface with blue-and-white branding, responsive side navigation, dashboards, cards, charts, tables, search, filters, empty states, skeleton loading, clear errors, accessibility and mobile navigation. Add school logos, accent colors and optional custom subdomains/domains. Provide realistic demo data clearly marked as demo. Never confuse demo data with real records.

DATA MODEL: Create normalized migrations and constraints for schools, memberships, profiles, classes, class enrollments, subjects, teacher assignments, academic sessions, terms, announcements, lessons, documents, assignments, submissions, question banks, questions, exams, attempts, answers, marking rubrics, grades, report cards, attendance, guardians, notifications, audit logs, subscription plans, school subscriptions, payments and AI usage. Include tenant_id on tenant-owned records and enforce consistent foreign-key relationships. Index common school/class/student queries. Use private storage buckets and signed URLs where appropriate.

SECURITY AND RELIABILITY: Use Supabase Auth, secure server-side role checks, RLS on every exposed tenant-owned table, least-privilege grants, validation, rate limits, upload restrictions, safe error messages, audit logging and tested tenant-isolation policies. Do not store secrets in frontend code. Do not log passwords or private exam answers unnecessarily. Provide data export, backups, retention settings and school data deletion workflows. Test cross-tenant read/write denial, role permissions, result calculations and payment webhooks. Make clear that production readiness requires real deployment, security testing, load testing and legal/privacy review.

BUILD STRATEGY: First inspect the project and create a phased implementation plan. Then build a functional MVP with authentication, tenant isolation, school setup, teacher/student accounts, class dashboards, assignments, document submissions, objective CBT and deterministic results. Next implement AI-assisted marking and tutoring, Google Meet API integration, parent portal, notifications, billing and analytics. Use real Supabase persistence, migrations and working forms. Do not fake backend features with buttons that do nothing. If credentials are missing, provide an explicit configuration checklist and a clearly labeled demo mode. Run available checks, fix errors and document setup, environment variables, deployment, backup and testing steps. Prioritize secure working features over superficial feature count. The product name is StudyHub. The target is a web-only platform that can grow to serve thousands of schools, with paid school subscriptions and independently isolated school environments.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.