ProjectTech4DevAI / ProjectTech4DevAI/kaapi-frontend
UI: Enhancements on the layout, wordings, etc
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 4
Description
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"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing evaluation and configuration screens against the unchecked items in this issue, then agree on a focused subset and completion criteria before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100