New UI reaches feature parity of old UI

_Update (Oct. 29, 2025)_: The import is done, and you can run this locally to test or develop it (see https://github.com/kubernetes-sigs/testgrid/tree/main/web for instructions). (It's not deployed anywhere yet though; that's tracked in https://github.com/kubernetes-sigs/testgrid/issues/31).

tl;dr: Listing the work remaining to get the TestGrid UI MVP (this repo) to have equivalent functionality to the existing closed-source UI (at https://testgrid.k8s.io/).

~~(Needs the import to be done first, ref #2).~~

The UI is basically a collection of web components that read data from the [TestGrid API](https://github.com/GoogleCloudPlatform/testgrid/tree/main/cmd/api#api) and handle specific functions within the UI. The main ones are navigation (to move between pages), the index (list of dashboard groups and dashboards), summary (display recorded summary data), and the grid component (the main logic; displays recorded test history in an interactive grid).

Most of this should require some familiarity with (or willingness to learn) frontend tech (TypeScript, web components, Lit, CSS, etc.). This is not currently deployed anywhere, but once the import is complete you should be able to run it locally.

It may help to have familiarity with (or willingness to learn) Golang as well so you can work with the API.

Note: This list is a work-in-progress and is expected to update with missing items as we come across them.
All the work below should come with sufficient testing (unit and manual tests).

- [ ] Navigation component
- [ ] (Is there any remaining work?)
- [ ] Index page
- [ ] (Is there any remaining work?)
- [ ] Summary component
- [ ] (Is there any remaining work?)
- [ ] Grid component
- [ ] Update component for performance (should handle 1 million elements easily)
- [ ] Ensure all statuses (color, icon, message) are handled
- [ ] Properly handle grouped/nested rows
- [ ] Properly handle all column and row headers (e.g. frozen to top and left sides, and scroll appropriately)
- [ ] Handle right-click context menu on cells (e.g. can file a bug and open test results)
- [ ] Add code-search link on failing rows
- [ ] Add tooltips (on cells and column headers)
- [ ] Accessibility: Verify that components are accessible
- [ ] Style: Unify styles across all components / pages
- [ ] Documentation: Update documentation for all components