MedBank

MedBank is a hosted browser app for medical students. The website is static on GitHub Pages, and the live hosted Supabase project is the single source of truth for auth, courses, questions, progress, enrollments, and admin data.

Live App

Open the deployed site:

• https://youssef256d.github.io/Medbank-Website/

The app does not need a local Supabase instance, local database, or your laptop to stay running. Once GitHub Pages and the hosted Supabase project are available, students and admins can use the app from the web.

Included MVP flows

• Public pages: Home, Features, Pricing, About, Contact + support form
• Auth: Sign up, Login, Forgot password via hosted Supabase Auth
• Create a test: choose assigned course + topic, set count, mode (timed/tutor), source (all/unused/incorrect/flagged), and randomization
• Attempt interface: select answers, flag, strike-through, notes, navigator, autosave, pause/resume timer
• Review: score summary, per-question explanation, add to incorrect queue
• Analytics: overall performance + topic breakdown + weak areas
• Profile: update account/email/password and view incorrect queue size
• Admin portal: assign courses to accounts, create/edit/delete/publish questions, and bulk import by course/topic

Legal content

Canonical legal-page copy lives in /Users/youssefayoub/Documents/Apps/MCQs Website/docs/legal/:

• privacy.md — Privacy Policy
• terms.md — Terms of Service
• support.md — Support Policy
• deletion.md — Data Deletion Instructions

The public Privacy Policy URL for Apple App Store Connect and Google Play Console is:

• https://youssef256d.github.io/Medbank-Website/privacy.html

The public account-deletion URL for Google Play Console is:

• https://youssef256d.github.io/Medbank-Website/deletion.html

These files are source copy for generated/public legal pages. Keep them in sync when privacy, retention, support, account deletion, or platform behavior changes.

Data/storage

Hosted Supabase is the database for the project. Browser storage is only used for session state, route memory, theme preference, and offline/cache safety; it is not the source of truth.

Supabase is wired through:

• /Users/youssefayoub/Documents/Apps/MCQs Website/supabase.config.js
• hosted project URL: https://fzjzjzdamehxbgikiskt.supabase.co
• browser-safe publishable key in supabase.config.js
• SQL migrations in /Users/youssefayoub/Documents/Apps/MCQs Website/supabase/migrations

Notes:

• The frontend uses only the hosted Supabase URL + publishable/anon key.
• Do not put SUPABASE_SERVICE_ROLE_KEY in frontend files.
• Supabase Auth is used for sign up/login/reset email.
• Primary sync path: relational tables (profiles, courses, course_topics, questions, test_blocks, etc.).
• Legacy app_state sync path is now limited to non-relational settings/queues only (to avoid duplicate heavy writes and improve responsiveness).
• Sync keys now support scale-safe namespacing:
  • global keys: g:<storage_key>
  • user-scoped keys: u:<auth.uid>:<storage_key>

Supabase connection method for this project

This repo now follows an online-only Supabase connection model:

• Browser frontend (index.html + bootstrap.js + main.js):
  • use Supabase Data APIs through supabase-js
  • configured by /Users/youssefayoub/Documents/Apps/MCQs Website/supabase.config.js
  • required values: hosted Supabase URL and publishable/anon key
  • do not use Postgres connection strings in the browser
• Server-side admin endpoints (/api/*.js and supabase/functions/*):
  • current implementation uses Supabase Auth/Admin HTTP APIs with SUPABASE_SERVICE_ROLE_KEY
  • no direct Postgres socket connection is opened by the current code
• Schema changes are applied to the remote Supabase project through migrations; do not start or depend on local Supabase.

Supabase Auth setup checklist

In Supabase Dashboard:

1. Authentication -> Providers:
   • Email: enable Email provider.
   • Google: enable Google provider and set authorized redirect/client settings in Supabase.
2. Authentication -> URL Configuration:
   • Site URL: your deployed URL
   • Redirect URLs: add your deployed URL and the mobile deep link medbank://auth/callback
3. Enable leaked-password protection (recommended for production).
4. (Optional) Disable "Confirm email" during testing if you want instant login after sign-up.

Supabase dashboard tasks still required

You still need to confirm these values in the Supabase project UI:

1. Project dashboard -> Connect
   • confirm the project URL
   • confirm the browser-safe publishable/anon key
2. Authentication -> URL Configuration
   • set Site URL to your deployed frontend URL
   • add all valid redirect URLs used by this app
3. Authentication -> Providers
   • enable Email
   • enable Google only if you intend to keep Google sign-in active
4. Database migrations
   • apply migrations to the hosted Supabase project only
   • do not use local Supabase as part of the runtime or release flow
5. Storage
   • create the question-images bucket if you want image upload to work
6. Edge Functions or hosting UI
   • if you deploy the canonical admin Edge Functions, set:
     • SUPABASE_SERVICE_ROLE_KEY
     • ALLOWED_ORIGIN
   • if you host your own /api backend instead, set the same server env vars there

Recommended connection selection:

• Use the hosted Project URL + publishable/anon key for this website frontend.
• Use the hosted Supabase Dashboard/CLI remote connection for migrations.
• Do not run local Supabase for production or student/admin usage.

Publish to web

This project is static (index.html + main.js + styles.css), so GitHub Pages works.

Release workflow

1. Push to main.
2. The Validate Changes GitHub Action runs automatically.
3. GitHub Pages deploys the static app from the repository.
4. The deployed app talks directly to the hosted Supabase project.

Quick GitHub Pages steps:

This is the beginning of the README. Read the rest at the original. Read the full README ↗