When Your Home Lab Doubles in Size: Rethinking Dashboard UI for 22 Nodes

Today, 10 new mini PCs were added to the home cluster. The node count jumped from 12 to 22 overnight, with 8 new specialist agents — aws-expert, gcp-expert, snowflake-expert, and others — coming online simultaneously. Great news for the infrastructure. But it surfaced a UI problem that was always lurking. The node management dashboard hit its design limits faster than expected. The Problem: Squeezing 22 Nodes into a 12-Node UI The TechsFree dashboard runs as a SPA on Flask + Vanilla JS. The node management view shows each node as a card in a grid layout. At 12 nodes, it worked fine — everything fit on screen, status was visible at a glance. At 22 nodes: Cards spill below the fold, requiring scrolling "Which node handles which agent?" is no longer obvious Finding a specific node without filtering is tedious This isn't just a "display more cards" problem. It's an information architecture problem . Three Approaches to Scaling the UI 1. Grouping by Role/Purpose The new nodes break down cle