Stories of Service

A phone-friendly site where veterans record their story, add a few details, and submit it. Every story waits in a review queue until a reviewer approves it for the public wall.

How it works

• index.html: pick branch (Active/Guard/Reserve) and eras, record a short intro video plus any number of separate story videos, fill in a bio, give consent, send. Shows approved profiles on the wall.
• bio.html: each veteran's profile page: intro video, each story with its transcript, and their bio: with the veteran's photo, service details, life after service and an "about me". Filled in as step 3 of the submit form.
• admin.html: reviewers sign in with a code texted to their phone (or an emailed link), then approve, hide or delete stories.
• Branch and era colors live in common.js. Branch colors follow each service's official colors; era colors follow each era's service-medal ribbon.
• Supabase (project "Veterans") stores the veterans and videos tables and the private story-videos bucket (8 GB per file, about 30 minutes of video). Uploads are resumable, so a dropped signal picks up where it left off.
• Plain static files, no build step. Hosted on Vercel.

Security rules (enforced in the database)

• Anyone can submit; new stories are always pending.
• The public can only read approved stories and their videos. Contact emails are never public.
• Only phones or emails listed in the admins table can review. Add a reviewer in the Supabase SQL editor (phone is digits only, with the country code):

insert into public.admins (phone) values ('15551234567');
insert into public.admins (email) values ('[email protected]');

• A "Before User Created" auth hook (private.only_reviewers_sign_up) refuses anyone not on that list, so strangers can't trigger texts.

One-time setup in Supabase

Authentication → URL Configuration:

• Site URL: the live site address
• Redirect URLs: add https://<your-site>/admin

Authentication → Sign In / Providers → Phone: turn on, choose Twilio, and enter the Account SID, Auth Token and Messaging Service SID.

Authentication → Hooks → Before User Created: choose Postgres, function private.only_reviewers_sign_up.

Storage → Settings → Upload file size limit: at least 8 GB (the project-wide cap; the bucket limit cannot exceed it).

Database changes live in supabase/migrations/.