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

Phase 4: Community submissions + moderation queue

Abierto
#35 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
supabase, typescript

Línea de trabajo

Start with src/app/submit/actions.ts and src/app/submit/submit-form.tsx, then inspect isUrlListed() in src/lib/resources.ts and the existing /submit submission view. Confirm the action validates the required fields, rejects duplicate URLs, records the signed-in user with approved=false, and refreshes the user's status view. Done means a submission appears under review and remains available to the admin queue.

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

Descripción

enhancement

Description

Implement community submissions and moderation queue as specified in PRD §8.10. This is a P2 requirement for Phase 4.

Acceptance Criteria (from PRD §8.10)

  • Logged-in users can submit a resource (approved = false until admin review)
  • Design the resources table's submittedBy/approved columns now (already in schema)

Current State

  • Database schema already has submittedBy (text) and approved (boolean, default true) columns on resources
  • /submit page exists with Supabase Auth sign-in
  • /submit page has SubmitForm component but it's not fully wired to backend
  • Admin dashboard already has review queue for approved = false resources
  • Admin can approve/reject submissions

What's Missing

  1. SubmitForm backend: The form submission action needs to insert into resources with approved = false
  2. User submission tracking: Show user their submissions with status (already partially in /submit page)
  3. Submission validation: Validate URL, required fields, duplicate detection
  4. Email notification: Notify admin of new submission (optional, Phase 5)

Implementation Plan

  1. Complete SubmitForm action:
    • src/app/submit/actions.ts - insert resource with approved = false, submittedBy = user.id
    • Validate form data (Zod schema)
    • Check for duplicate URL
    • Redirect to /submit with success message
  2. Enhance user submission view:
    • /submit page already shows user's submissions with status
    • Ensure real-time updates after submission
  3. Admin review queue: Already working in /admin dashboard
  4. Duplicate detection: Use existing isUrlListed() in src/lib/resources.ts

Files to Modify

  • src/app/submit/actions.ts - complete the submission Server Action
  • src/app/submit/submit-form.tsx - ensure proper form handling
  • src/lib/resources.ts - verify isUrlListed() works for duplicate check

Database Schema (already exists)

resources: {
  submittedBy: text('submitted_by'), // user id
  approved: boolean('approved').notNull().default(true), // false for submissions
  // ... other fields
}

UX Notes

  • Submission form: name, URL, category, cost type, description (required), tags/region/deadline (optional)
  • After submit: "Thanks! Your submission is under review." + show in user's submission list
  • Admin sees in review queue with "Approve" / "Reject" / "Edit before approving"
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.