GitHub user xuang7 edited a discussion: Proposal: Improve the dataset dashboard 
with a more visual card-view layout

Hi everyone,

After the hackathon, we saw several creative interface ideas related to 
workspace discovery. I think this is a good opportunity for us to discuss a 
broader improvement to the current dataset/dashboard page.

### Proposed direction
For the dataset dashboard, there are two directions worth exploring (some of 
these ideas may also apply to the workflow dashboard):
- Card-view layout: add a card view alongside the current line-by-line list, 
making it easier to browse and quickly understand what datasets are available.
- Richer metadata display: surface key fields at a glance on each card, such as 
dataset name, short description, owner, visibility, tags, last updated time, 
and an optional preview or cover image.

The goal is not necessarily to replace the current list view immediately, but 
to explore whether a card-based dashboard could make dataset browsing more 
intuitive and visually clear.

Related references:
- Dataset Bank hackathon project [(PR 
#5097)](https://github.com/apache/texera/pull/5097)
- Workflow dashboard card-view [(PR 
#4216)](https://github.com/apache/texera/pull/4216)

Current dashboard (today):
<img width="1474" height="853" alt="dashboard" 
src="https://github.com/user-attachments/assets/7e589896-9744-4941-a555-490c9f67ea5c";
 />

Reference: Dataset Bank (PR 5097) from the hackathon:
<img width="1932" height="1146" alt="dataset bank" 
src="https://github.com/user-attachments/assets/8493ac91-04be-4720-9e64-52e2c4e57869";
 />

Reference: AI-generated sample layout (for discussion only):
<img width="809" height="457" alt="dashboard" 
src="https://github.com/user-attachments/assets/c3557b01-a3ee-4e4b-86c4-988c7cef7da6";
 />

Please feel free to share any thoughts, concerns, or suggestions. Thank you.

GitHub link: https://github.com/apache/texera/discussions/5130

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to