ProjectTech4DevAI / ProjectTech4DevAI/kaapi-frontend

UI: Enhancements on the layout, wordings, etc

Abierto
#26 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

enhancement sub-parent
Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Merge medio
10 h 40 min
PR fusionados (30 d)
4

Descripción

Describe the current behavior
Currently the frontend has been built with keeping only one thing in mind that it is clear enough to run evaluations, config management etc. UI-wise our frontend may not be the best, we connected with noopur during sprint and these are the things she pointed out that we can take care of to make the UI better, More things can be added to this list also

Describe the enhancement you'd like

  • Naming can be clearer, that users can understand
  • Back button on Configuration bucket, also browse library may not be the best idea
  • Laundry list of old evals that have been run can be a good addition
  • using specific colour codes when showing scores to show bad or good score
  • evaluation page layout can be - the first thing we see is a list of old evals, and then we have a button to create a new eval, and we click on it and we select which evaluation to run
  • eval metric overview can be smaller, does not have to take much space, the detailed results part deserves more space to take
  • lots of texts in score reasoning, maybe turn them to points/takeaways
  • markdown should not show up in texts in answers/ground truth
  • question and ground truth column should be kept together, and then answer column comes, also these columns can be shown in a better way noopur will come back to us for this
  • evaluation score comparision, with particular filters
  • for evaluation, dont show the timestamp it took but if you have to show the amount of time it took
  • change configuration library name?
  • "datasets" can come under evaluation
  • the word configuration by itself does not mean much
  • when we compress the menu, there still should be smth we can see is there
  • under configurations, maybe it should not be called "prompt editor", it should be called "config editor"

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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.

Línea de trabajo

No se nombran archivos, pruebas ni puntos de entrada. Empieza revisando las pantallas existentes de evaluación y configuración en relación con los elementos sin marcar de este issue y acuerda un subconjunto bien delimitado y los criterios de finalización antes de realizar cambios.

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

Evaluación

Stack tecnológico
typescript
Área
design, frontend
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
20/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.