Idea
For grids whose squares have an inherent order, add sparse orientation labels directly on selected squares.
Example: Workflow Runs are chronological. If the grid spans multiple days, label only the first run for each day (Jun 6, Jun 7, etc.) so the viewer can orient without every square becoming text-heavy.
Shape
- Treat ordering as grid metadata, not a universal square feature.
- Only apply labels when the collection has a meaningful ordered axis.
- Use group-boundary labels, not labels on every square.
- Chronological grids might label day/month boundaries.
- Other ordered grids might label rank/threshold boundaries if the ordering is by balance, count, severity, activity, etc.
Notes
This could generalize beyond GitHub:
- GitHub Workflow Runs: chronological labels.
- GHL sessions: chronological labels.
- Therapists: maybe unordered, so no labels.
- Patients/clients: maybe ordered by open balance, sessions had, follow-up urgency, etc.; labels depend on the chosen ordering.
The key is that some grids are ordered and some are not. The component should know the difference.
Idea
For grids whose squares have an inherent order, add sparse orientation labels directly on selected squares.
Example: Workflow Runs are chronological. If the grid spans multiple days, label only the first run for each day (
Jun 6,Jun 7, etc.) so the viewer can orient without every square becoming text-heavy.Shape
Notes
This could generalize beyond GitHub:
The key is that some grids are ordered and some are not. The component should know the difference.