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

🗺️ Roadmap

Abierto
  • ¿Algo no está bien?
#21 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
12/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
docker-compose, eslint, express, github-actions, javascript, mongodb, nodejs, playwright, react, tailwindcss, vite
Área
full-stack

Línea de trabajo

This is a tracking issue, not a single task: it links open issues #5 to #20 and lists unfiled ideas. Read CONTRIBUTING.md first, then open a linked issue to pick a concrete item. Ideas without an issue need a discussion before any work starts. The only file the list names is server/src/app.js, which the controller-tests item would need split out.

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

Descripción

This is where TaskFlow is heading. It's a living list: it changes as issues are finished and new ideas come up. Everything here is open to contributors, including first-timers! 🙌

💡 Have an idea that would make TaskFlow better? Suggest it with a feature request. Good ideas become issues here, and you're welcome to build yours.

How to help

  • Items with an issue number are ready to work on: open the issue, comment to claim it, and follow CONTRIBUTING.md.
  • Bigger features are split into small steps. Each step is its own issue, so several people can work on one feature. Please pick the next open step, since later steps build on earlier ones.
  • Items without an issue are ideas, not promises. If you'd like to work on one, comment here or start a thread in Discussions first, so we can agree on the approach and turn it into an issue.

🟢 Short term: polish and fixes (open issues)

Bugs

  • #5
  • #11
  • #13
  • #17
  • #18
  • #42
  • #43
  • #49
  • #63
  • #66

User experience

  • #6
  • #7
  • #8
  • #9
  • #10
  • #16
  • #24
  • #37
  • #38
  • #40
  • #41
  • #59
  • #61
  • #62
  • #67

Backend and security

  • #14
  • #15
  • #64
  • #65

Testing, docs and tooling

  • #19
  • #20
  • #28
  • #44 (continuous integration: tests and the client build run on every pull request)
  • #78
  • #79

🟣 Bigger features, step by step

Due dates

  • #68
  • #69
  • #70

Light theme

  • #71
  • #72
  • #73

Tags

  • #74
  • #75

Board view (Kanban)

  • #76
  • #77

🟡 Medium term: next improvements (ideas, no issues yet)

  • Automatic formatting with Prettier, after ESLint (#78) is in. It needs one planned reformat of the whole project at a quiet moment, so it doesn't conflict with open pull requests.

🔵 Long term: bigger ideas

  • Safer sessions: short-lived access tokens with refresh tokens stored in httpOnly cookies instead of localStorage.
  • One-command local setup with Docker Compose (API, app and MongoDB together).
  • End-to-end tests that click through the real app in a browser (for example with Playwright).

This roadmap is updated as work lands. Last updated: 21 October 2026.

Lenguaje dominante
JavaScript
Estrellas
3
Forks
2
Merge medio
13 h 10 min
PR fusionados (30 d)
42

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 KEX-03/taskflow

Todos los issues de KEX-03/taskflow

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.