Tech Stack¶
The rubric rewards a fully listed and motivated stack — don't just name a tool, say why you picked it over the alternatives you considered.
| Layer | Choice | Why |
|---|---|---|
| Front-end | e.g. React + Vite | reason |
| Back-end | e.g. Express / Fastify | reason |
| Database | e.g. PostgreSQL | reason |
| Auth | e.g. Auth0 / Clerk / Supabase Auth (auth only) | must be an established library/service — see brief |
| Hosting (client) | e.g. Vercel / Netlify | reason |
| Hosting (server) | e.g. Railway / Render / Fly.io | reason |
| CI/CD | e.g. GitHub Actions | reason |
| External integration | e.g. timetable/calendar API | reason |
| Docs | MkDocs + Material, deployed via GitHub Pages | Markdown-based, free static hosting, satisfies the "no account-gated platform" requirement |
Third-party libraries¶
Track any significant third-party code here as you add it (the rubric explicitly marks on "Third-Party Code Documentation").
| Library | Purpose | Version |
|---|---|---|