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

[Labs] Design the lab details page

Abierto
  • ¿Algo no está bien?
#2,168 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 5 días

@alanpeixinho ya está trabajando en esto.

Desde el 14/10/2026.

  • #2172 de @alanpeixinho — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Área
design

Línea de trabajo

Start by opening the /labs listing to see which build, boot and test counts each row shows for the selected origin and interval. Sketch a lab details page for one lab that carries those same filters and summaries forward, with a way back to the listing and an empty state. Done when a Figma link or in-dashboard mock labeled as a proposal covers all the acceptance criteria. No API or production page is needed.

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

Descripción

Frontend q4-plan

The labs listing (/labs) shows one row per lab: name, and build, boot, and test status counts for the selected origin and time window. Clicking a row does nothing. There is no lab details route.

Propose the page a user lands on after clicking a lab. A Figma (or equivalent) design is enough to collect feedback. A mocked page in the dashboard is also fine, as long as it is clearly a proposal and not wired to real data.

The proposal should show one specific lab, carrying over the listing's origin and interval. Start from what the listing already implies (that lab's builds, boots, and tests) and show how those summaries expand. Include the way back to the listing, and the empty state when that lab has no results in the window.

The kind of information the page will show is open to discussion.

Acceptance criteria

  • A design artifact (Figma or an in-dashboard mock) of the lab details page.
  • The entry point is a click on a lab in the listing, and the page is clearly about that one lab.
  • Build, boot, and test results for that lab are shown in more detail than the listing row.
  • Empty state and a way back to the listing are included.
  • The artifact is labeled as a proposal. No API or production page is required.
Lenguaje dominante
Python
Estrellas
10
Forks
32
Merge medio
5 d 8 h
PR fusionados (30 d)
22

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 kernelci/dashboard

Todos los issues de kernelci/dashboard

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.