Skip to content

feat(ui): clarify service hierarchy and mobile status overview - #9

Open
Adiker wants to merge 1 commit into
mainfrom
feature/service-hierarchy
Open

Adiker wants to merge 1 commit into
mainfrom
feature/service-hierarchy

Conversation

@Adiker

@Adiker Adiker commented Oct 22, 2026

Copy link
Copy Markdown
Owner

Summary

Service navigation was separated from the panel it controls, client diagnostics occupied the header, and small text made the status overview difficult to scan. Place tabs immediately above the active service, move client diagnostics into collapsed technical information at the bottom, and use consistent 16px names/body copy and 14px status/secondary text.

Replace individually bordered dashboard tiles with aligned desktop columns and compact mobile rows. Keep status text alongside its dot, reserve space for changing measurements, and provide a visible open-service label with a whole-card hit area. Retain the three themes and bilingual UI; darken light-theme secondary/status colors for contrast. Update EN/PL documentation and asset versions.

At 390px in Polish with identical controlled states, the dashboard is 520px tall versus 972px in PR #8 (46% shorter). The service section ends at 1039px versus 1058px on main. Desktop service content does not extend further down than main or PR #8 across the checked panels, languages, and themes.

Validation

  • JavaScript syntax, whitespace, static hosting/assets/custom-domain checks, and all 8 existing Muse status tests passed.
  • Isolated headless Brave: 450 layout/state combinations across 160–1440 CSS pixels, EN/PL, and Dark/Light/OLED; no page overflow, clipped checked text, unstable dashboard row heights, or JavaScript errors. Narrow CSS widths exercise reflow equivalent to 200% zoom; this is not physical-device testing.
  • 60 panel checks plus language/theme persistence, keyboard arrow navigation and wrapping, horizontal tab scrolling, skip link, visible focus, history/technical disclosures, ARIA references, and whole-card links passed.
  • Controlled HTTP 200/503 responses verified status, count, timestamp, and latency updates. Rendered-text contrast sampling across all three themes: minimum 4.84:1.
  • 240 desktop comparisons against main and PR fix(ui): improve service dashboard readability #8 passed. Reviewed desktop/mobile screenshots and the local page with live service polling.

Risk and rollback

Markup and CSS relocate existing controls and change responsive sizing. Existing service URLs, polling logic, storage keys, and DOM IDs are preserved. Revert this commit to restore the previous layout; no data migration is required.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant