The Beta Alpha Psi Beta Tau Chapter web platform is a full-stack, member-facing application built to serve three distinct audiences: active chapter members, executive board officers, and corporate sponsors. It provides authenticated dashboards, a chapter-wide networking directory, event management with RSVP and check-in flows, an announcement system, a shared resource library, and an administrative control panel — all unified under a single React SPA deployed to Vercel. The frontend communicates with a separate backend API (referenced viaDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/asubap/website/llms.txt
Use this file to discover all available pages before exploring further.
VITE_BACKEND_URL) that owns the database and business logic, while Supabase handles identity via Google OAuth and session persistence in localStorage.
Who This Documentation Is For
Chapter Developers
Engineers contributing to the platform who need to understand the project structure, auth system, routing conventions, and how to spin up a local environment.
E-Board Officers
Technical officers who need to understand how roles, permissions, and protected routes work — and what the admin dashboard can and cannot do without a backend change.
New Contributors
Anyone onboarding to the codebase for the first time. Start with the local setup guide, then read the architecture overview.
Sponsor Contacts
Technical stakeholders at sponsor companies who want to understand how sponsor accounts are provisioned and what the sponsor portal exposes.
Tech Stack at a Glance
| Layer | Technology | Version |
|---|---|---|
| UI Framework | React | 19.0 |
| Language | TypeScript | ~5.7.2 |
| Build Tool | Vite | 6.2 |
| Styling | Tailwind CSS | 3.4 |
| Routing | React Router DOM | 7.5 |
| Auth & DB Client | Supabase JS | 2.49 |
| HTTP Client | Axios | 1.8 |
| Maps | Leaflet + react-leaflet | 1.9 / 5.0 |
| Rich Text | TinyMCE React | 6.3 |
| Fuzzy Search | Fuse.js | 7.1 |
| Icons | Lucide React + react-icons | 0.479 / 5.5 |
| Toasts | react-hot-toast | 2.5 |
| Hosting | Vercel | — |
Project Folder Structure
The frontend lives entirely insideFrontend/ within the monorepo. The src/ directory follows a feature-aware layout where pages own their top-level view components and components/ is further split by domain.
Quick Navigation
Local Setup
Clone the repo, install dependencies, configure your
.env, and start the dev server in minutes.Environment Variables
Every environment variable the frontend needs, where to find the values, and what happens if one is missing.
Architecture Overview
Deep-dive into the full dependency list, the
src/ directory conventions, and how the app is wired together at a high level.