onewinkip7-prog/afya-connect-web

Afya Connect Kenya - marketing site, operations dashboard, Supabase schema # Afya Connect Kenya — website Two static pages: - `index.html` — the public marketing site (services, how it works, facilities, partner/apply CTAs) - `operations.html` — the live operations dashboard (facilities A–D, department shift targets, overtime, ratings) `schema/` contains the Postgres migrations for the underlying data model (billing, staff attendance, commissions, overtime, patient ratings, cadres). These are written for Supabase's Postgres instance and can be run in order via the Supabase SQL editor or the Supabase CLI. ## Deploying on Vercel 1. Push this repo to GitHub (see below). 2. In Vercel: **Add New → Project → Import Git Repository**, select this repo. 3. Framework preset: **Other** (this is a plain static site, no build step needed). 4. Deploy. `index.html` and `operations.html` will be served as-is. ## Connecting Supabase (when you're ready to wire in real data) 1. Create a project at supabase.com. 2. In the Supabase SQL editor, run the three files in `schema/` in order (001, then 002, then 003). 3. Copy `.env.example` to `.env.local`, fill in your project's URL and anon key from Supabase's project settings — **do not commit `.env.local`**. 4. In Vercel, add the same variables under **Project Settings → Environment Variables** so the deployed site can read them. 5. Both HTML pages currently use hardcoded sample data in their ` ` blocks. Swapping that for live Supabase queries is the next step once you want real numbers instead of illustrative ones. ## Pushing this repo to GitHub From inside this folder: ```bash git init git add . git commit -m "Initial Afya Connect website" git branch -M main git remote add origin github.com git push -u origin main ``` If the repo doesn't exist yet on GitHub, create it first (empty, no README) at github.com, then run the commands above.