Equitask
Equitask is a full-stack web app for university group assignments that prioritizes fair workload distribution, task effort voting, availability-aware assignment, accountability, and team analytics.
The app now uses Supabase authentication for normal access. Earlier demo-login entry points have
been removed, so users sign up or sign in with a real Supabase-backed account.
Project Overview
Equitask solves group-project imbalance by making effort estimation and assignment transparent:
- Story point voting happens before assignment
- Official effort is based on team average votes
- Workload fairness is continuously measured
- Overload and overdue risk are surfaced early
- Analytics shows contribution and progress trends
Key Features
- Landing page with product positioning and CTA flow
- Supabase sign-up and sign-in (email/password)
- Team Hub for creating teams, joining by team code, and switching active team
- Dashboard with summary cards, fairness score, activity feed, notifications, progress chart, and member cards
- Scrum board with status updates, assignment updates, and task creation panel
- Task detail page with voting, comments, assignment recommendations, and activity log
- Dedicated voting center for planning-poker style estimation
- Member profile page with timetable-style weekly availability
- Analytics page with Recharts visualizations
- Settings page for session and account visibility
Tech Stack
- Next.js (App Router)
- TypeScript
- Tailwind CSS
- Next.js server routes (
/api/...) for backend logic
- Recharts for analytics
- Supabase integration via service/provider layer
- Vercel-compatible structure (no custom server)
Local Development
- Install dependencies:
npm install
- Start development server:
npm run dev
- Open:
http://localhost:3000
Supabase Auth Required
The public demo login flow has been removed. To use the workspace, configure Supabase and sign in
through the normal email/password flow.
The codebase still contains seeded data and a provider abstraction for development history and safe
fallback testing, but the website no longer exposes a demo login button, settings switch, sidebar
switch, or any demo workspace controls in the UI.
Environment Variables You Must Add Manually
Do not hardcode credentials. Add these yourself in local/Vercel:
NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEY
No filled .env file is generated by this project.
Supabase Setup
1. Create a Supabase Project
Create a project in Supabase and wait for it to initialize.
2. Enable Email/Password Auth
In Supabase Dashboard:
- Go to
Authentication -> Providers
- Enable
Email
- Enable
Email + Password sign-in
- Optional: disable email confirmation for faster dev testing
3. Add Environment Variables
Add these to your local environment and Vercel project settings:
NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEY
4. Run SQL in Supabase
- Go to
Supabase Dashboard -> SQL Editor
- Create a new query
- Paste the full SQL from the section SQL to Run in Supabase
- Run it
5. Start App and Test Auth
- Start app:
npm run dev
- Open
/sign-up and create an account
- During sign-up, either create a new team or join with a team code
- Then sign in at
/sign-in
- If the user has a team membership, login redirects to
/dashboard
- If no team membership exists, login redirects to
/teams (Team Hub)
- Workspace, board, voting, and analytics all load from the active team in session
6. Supabase Session Behaviour
- Supabase mode is used when env vars are configured and the user signs in through the Supabase form.
- Team context is saved in session (
teamId) so users return to their team workspace directly.
- Demo login and demo switching are no longer exposed in the website.
SQL to Run in Supabase
Paste this entire SQL block into Supabase SQL Editor:
This is the beginning of the README. Read the rest at the original. Read the full README ↗
