Repository navigation
Use table view for all non-Dashboard pages #19
Description
For 0.1.0, I suggest we keep cards only on the Dashboard and adopt a table layout on all other pages that display lists of entities (for example, the Mining or Energy pages).
Those pages are primarily for management and configuration (add, edit, activate/deactivate, delete), not for high-level monitoring. In these contexts, users usually work with many items at once and need to quickly scan and compare them.
With a card layout this becomes harder as soon as the list grows: it is difficult to see at a glance which miners are online/offline, running/not running, or which ones require attention.
A table view would improve usability by:
- showing key fields in columns (status, running state, controller, hash rate, power, actions, etc.)
- allowing sorting by column and filtering by attributes
- making row-level actions more consistent and discoverable
In short
Dashboard = cards (overview)
all other list pages = tables (operational management).
Activity