Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Epic: Phase 3 — User Accounts, Bookmarks, Deadlines, Personalization

Abierto
  • ¿Algo no está bien?
#42 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
supabase, typescript
Área
authentication, database, full-stack

Línea de trabajo

This is a Phase 3 tracking issue rather than a self-contained task; begin with PRD §13 and the linked issues #32, #33, and #34. Review src/lib/supabase/{server,client}.ts and src/proxy.ts, then inspect the listed auth, RLS, migration, and role-based-admin concerns. Done means the three scoped issues and cross-cutting requirements are completed and the Phase 3 success metrics can be evaluated.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Description

Tracking issue for Phase 3 implementation per PRD §13. Phase 3 extends the existing Supabase Auth setup rather than introducing a new one.

Phase 3 Scope (PRD §13)

Feature PRD Section Priority Issue
Auth + Bookmarks + Application Tracker §8.7 P1 #33
Deadline View §8.4 P0 #32
Personalization Signals §8.8 P1 #34

Prerequisites (Already Done ✅)

  • Supabase Auth plumbing: src/lib/supabase/{server,client}.ts, src/proxy.ts
  • Database schema: bookmarks, reviews, clickEvents, profiles (to be added), resources.deadline
  • /submit page with Google + email-link sign-in working
  • Admin single-email gate (will need to become role-based for real users)

Phase 3 Implementation Order

1. Deadline View (/deadlines) — P0, Independent
  • No auth required
  • Uses existing deadline column
  • Need to seed deadline data for scholarships/internships
  • Issue: #32
2. Bookmarks + Application Tracker (/my-list) — P1, Requires Auth
  • Extends existing auth
  • Uses existing bookmarks table
  • ResourceCard bookmark button already exists (non-functional)
  • Issue: #33
3. Personalization (Branch/Year Onboarding + Ranking) — P1, Requires Auth + Bookmarks
  • New profiles table
  • Onboarding flow after first sign-in
  • Ranking boost in directory sort
  • Issue: #34

Cross-Cutting Concerns

  • Auth protection for /my-list and /onboarding: Update src/proxy.ts matcher
  • Role-based admin: verifyAdmin() currently checks email === ADMIN_EMAIL — needs to support real admin roles when multiple users exist
  • RLS Policies: Enable and test RLS on bookmarks, reviews, clickEvents, profiles
  • Migration: drizzle-kit generate + migrate for new profiles table

Success Metrics (PRD §11)

  • 7-day return rate > 25% (G3)
  • % of scholarship/internship clicks >3 days before deadline > 60% (G4)

Related Issues

  • #32: Deadline View
  • #33: Bookmarks/Tracker
  • #34: Personalization
  • #26: Click Tracking (feeds analytics)
  • #38: Weekly Digest Email (Phase 5, but uses same auth)
Lenguaje dominante
TypeScript
Estrellas
1
Forks
6
Merge medio
11 h 16 min
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Your-Voldemort/StudentStack

Todos los issues de Your-Voldemort/StudentStack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.