Skip to content

Conversation

@wanyingz-dis
Copy link
Contributor

What I did

  1. Moved project selector to the top, just below the Alphatrion logo
  2. Sidebar now shows Experiments/Trials/Runs instead of Projects
  3. Added Overview and List tabs to each page
  4. Implemented Runs page
  5. Run ID is clickable and jumps to run detail page

Additional UI improvements

  • Added icons to sidebar navigation
  • Added some effects to sidebar
  • Redesigned Overview tab with metric cards instead of plain table
  • Added "Recent Experiments" section in Overview
  • Version number now reads from package.json

- Move project selector to sidebar header (below logo)
- Sidebar now shows Experiments, Trials, Runs
- Trials and Runs links disabled until parent is selected
- Add TrialsPage component with Overview + List tabs
- Overview shows stats: total, completed, running, failed, avg duration
- Store selected experimentId and trialId in context for navigation
- Store selected experimentId and trialId in context
- Sidebar Trials link enabled after selecting experiment
- Sidebar Runs link enabled after selecting trial
- ExperimentDetail sets experimentId in context
- TrialDetail sets experimentId and trialId in context
- Run IDs now clickable in TrialDetail page
- RunsPage with Overview + List tabs
- Overview shows total, completed, running, pending, failed counts
- List shows all runs with clickable IDs
- RunDetail shows run info, status, and metadata
@InftyAI-Agent InftyAI-Agent added needs-triage Indicates an issue or PR lacks a label and requires one. needs-priority Indicates a PR lacks a label and requires one. do-not-merge/needs-kind Indicates a PR lacks a label and requires one. labels Dec 4, 2025
@kerthcet
Copy link
Member

kerthcet commented Dec 4, 2025

Some advices here:

  1. delete them, we should only have one item for experiment-related in the sidebar, because in the future, we'll have more like prompts, models, evaluations in the sidebar.
image
  1. let's also add the id here, id is always one of the most important information for table list.
image
  1. let's keep the style consistent across pages, only keep the arrow here. Right now, sometimes we have arrow, sometimes we have view ->, sometimes nothing there.
image
  1. Another thing I would like to discuss with you is the tables, in the experiment home page, we have tables, but in other pages, like trials list page, no tables, also the run list page. The main concern here is if we combine the list page and the overview page together, would that lead to performance issue in the future, because the overview page will have several curves usually have lots of data points. That's the main reason why we need to have two different tables. What's you opinion on this since you designed the page loading process.
image

@@ -0,0 +1,219 @@
import { useState } from "react";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you use lowercase for the folders and file names?

@wanyingz-dis
Copy link
Contributor Author

For 1, understood, will change and only “Experiments” will remain in the sidebar.
Then Trials and Runs will be accessible by navigating through the experiment hierarchy, with breadcrumbs/tabs for going back.
For 2: sounds good, will update.
For 3: agreed, I can make action column consistent across all list pages and use only the arrow icon (so no “View”). Right now the styling for Trials and Runs pages haven't been updated, can update that to match the Experiment list style.
For 4: yes that's a really good point, Thanks! Combining the overview and list could get heavy once added more charts and data. I can separate them into two pages, so the overview can load its heavier components without affecting the list view. This should also make the Experiment -- Trial -- Run flow clearer. What do you think?

@kerthcet
Copy link
Member

kerthcet commented Dec 4, 2025

I can separate them into two pages

Here I guess you mean two tables, or other better layouts if you have. I'm fine with either options.

@wanyingz-dis
Copy link
Contributor Author

I’ve cleaned up and unified some of the dashboard UI in this update:

  1. Converted all component folders and files to lowercase.
  2. Sidebar update
  3. ID added for recent experiments
  4. Replaced the separate tab implementations on Experiments Page, Experiment Detail, Trial Detail, and Run Detail with a single reusable component under components/ui/. Tabs now should have a consistent design
  5. Separating content areas such as metrics, overview info, and list tables.

Note: I haven’t yet created the reusable arrow/row action component, that can be done as a refinement in the future.

@kerthcet
Copy link
Member

kerthcet commented Dec 4, 2025

Several comments, then let's merge it.

  1. be consistent with other pages
image
  1. Combine Metrics with Overview
image
  1. remove the projects, if you click the projects, it' a blank page.
image
  1. Better to make sure the id is also clickable for quick navigation.
image
image

@wanyingz-dis
Copy link
Contributor Author

please see latest clean up

@kerthcet
Copy link
Member

kerthcet commented Dec 4, 2025

I don't want to be too mean on this, but I think we should still optimize it a bit:

  1. The position of the Experiments is different from other pages if we click any experiment item, it's very obvious.
image
  1. we don't have metrics page anymore
image
  1. The format is not very common, let's use Prefix 6 + … + Suffix 4, then it should look like Experiments/df0b18...d19e/Trials/88be24...a9a26/
image

Also they're other parts not very good, like at some pages the font is highlighted, while other pages not, but I'm fine with the first minor version. These three are the main concerns I have now, they're more obvious.

@kerthcet
Copy link
Member

kerthcet commented Dec 5, 2025

One more thing, we have logo here: https://github.com/InftyAI/alphatrion/blob/main/site/images/logo.png

Let's replace the default one in the dashboard.

@wanyingz-dis
Copy link
Contributor Author

@kerthcet
Thanks for the feedback, they are quite helpful for me and all make sense.
After looking back at the changes, I think overall, the root cause is that I hadn’t yet abstracted enough repeated UI patterns such as ID formatting into shared components, which caused some visual drift between pages.
I can fix all items this afternoon and update the branch with a consistent version.

@kerthcet
Copy link
Member

kerthcet commented Dec 5, 2025

Kindly remind: Alphatrion should be AlphaTrion.

@kerthcet
Copy link
Member

kerthcet commented Dec 5, 2025

Is this ready for another review? @wanyingz-dis

@wanyingz-dis
Copy link
Contributor Author

Is this ready for another review? @wanyingz-dis
Yes. Everything should now be updated, so it’s ready for another review.

@kerthcet
Copy link
Member

kerthcet commented Dec 5, 2025

/lgtm
/approve
/kind feature

Thanks @wanyingz-dis

@InftyAI-Agent InftyAI-Agent added lgtm Looks good to me, indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. feature Categorizes issue or PR as related to a new feature. labels Dec 5, 2025
@kerthcet
Copy link
Member

kerthcet commented Dec 5, 2025

fix #102

@InftyAI-Agent InftyAI-Agent removed the do-not-merge/needs-kind Indicates a PR lacks a label and requires one. label Dec 5, 2025
@InftyAI-Agent InftyAI-Agent merged commit 8e1e7c2 into InftyAI:main Dec 5, 2025
25 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. feature Categorizes issue or PR as related to a new feature. lgtm Looks good to me, indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a label and requires one. needs-triage Indicates an issue or PR lacks a label and requires one.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants