Feature description
The sidebar currently hosts four distinct file lists, several of which include type-specific primary actions:
- Recordings (Action: "New recording")
- Generators (Action: "New generator")
- Scripts
- Data files (Action: "Import data file")
As the number of resources grows (particularly within Recordings and Scripts), these flat lists are becoming increasingly difficult to parse and navigate. With the upcoming introduction of a new file type for browser tests (in scope of #1043), continuing to append standalone file trees is no longer sustainable.
Instead of adding another tree, we should reconsider the sidebar’s information architecture. We need a unified approach to grouping and managing resources that can scale as the project's complexity increases.
Suggested solution (optional)
One option is to stick with our current layout and simply add the new file tree. Alternatively, we could group browser tests and generator tests together. If we go this route, we’ll need to add file-type icons or badges so users can tell the difference between them:
Another approach is to move toward vertical tabs for each resource or task type. This solves the crowding problem and opens up space for task-specific features in the sidebar, such as a search filter for recording hosts or a list of recently visited URLs.
Already existing or connected issues / PRs (optional)
No response
Feature description
The sidebar currently hosts four distinct file lists, several of which include type-specific primary actions:
As the number of resources grows (particularly within Recordings and Scripts), these flat lists are becoming increasingly difficult to parse and navigate. With the upcoming introduction of a new file type for browser tests (in scope of #1043), continuing to append standalone file trees is no longer sustainable.
Instead of adding another tree, we should reconsider the sidebar’s information architecture. We need a unified approach to grouping and managing resources that can scale as the project's complexity increases.
Suggested solution (optional)
One option is to stick with our current layout and simply add the new file tree. Alternatively, we could group browser tests and generator tests together. If we go this route, we’ll need to add file-type icons or badges so users can tell the difference between them:
Another approach is to move toward vertical tabs for each resource or task type. This solves the crowding problem and opens up space for task-specific features in the sidebar, such as a search filter for recording hosts or a list of recently visited URLs.
Already existing or connected issues / PRs (optional)
No response