hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Harden dashboard responsive layout #38

New Issue
Closed
opened 2026-05-21 14:35:26 +02:00 by parkel · 0 comments
parkel commented 2026-05-21 14:35:26 +02:00
Owner
Copy Link

Goal

Make the dashboard layout robust across desktop, laptop, tablet, and mobile widths while keeping the current control-panel direction.

Scope

  • Fix cramped and overlapping dashboard content, especially long hostnames and recent activity cards.
  • Rework the top dashboard grid so panels do not force awkward empty height or narrow columns.
  • Ensure host cards, storage pressure, required action, schedules, and activity blocks wrap predictably.
  • Add responsive breakpoints for medium and small screens.
  • Preserve the current information architecture unless a small layout change clearly improves scanability.

Acceptance Criteria

  • Long hostnames and snapshot IDs never overlap adjacent content.
  • Dashboard cards remain readable at common laptop widths and stack cleanly on mobile.
  • Empty/low-content panels do not create excessive whitespace.
  • Existing dashboard tests remain green, with targeted test coverage where template behavior changes.
## Goal Make the dashboard layout robust across desktop, laptop, tablet, and mobile widths while keeping the current control-panel direction. ## Scope - Fix cramped and overlapping dashboard content, especially long hostnames and recent activity cards. - Rework the top dashboard grid so panels do not force awkward empty height or narrow columns. - Ensure host cards, storage pressure, required action, schedules, and activity blocks wrap predictably. - Add responsive breakpoints for medium and small screens. - Preserve the current information architecture unless a small layout change clearly improves scanability. ## Acceptance Criteria - Long hostnames and snapshot IDs never overlap adjacent content. - Dashboard cards remain readable at common laptop widths and stack cleanly on mobile. - Empty/low-content panels do not create excessive whitespace. - Existing dashboard tests remain green, with targeted test coverage where template behavior changes.
parkel added this to the 1.1 milestone 2026-05-21 14:35:26 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label
Milestone
No items
No Milestone 1.1
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#38
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?