Layout should look good in a vertical (portrait / narrow) window

Open
#98 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
54/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
playwright, typescript

Research direction

Start by locating the dashboard layout, top bar, side panel, and modal components, then review the existing Playwright viewport tests. Check the dashboard at widths from roughly 768px to 1366px and at a portrait viewport such as 900x1400. Done means the layout and main modals meet the listed acceptance criteria and Playwright covers a portrait viewport.

Written by the indexing model from the issue text.

Description

enhancement

The dashboard is laid out for a wide landscape window. On a vertical monitor, a narrow browser window, or a window snapped to half the screen, it gets cramped:

  • Top bar buttons wrap onto two lines (e.g. "Add Instance"), and the version label wraps. The CPU/RAM totals added in #38 are hidden below 1366px for this reason.
  • The fixed-width side panel uses up a large share of a narrow window, leaving little room for the server grid.
  • Modals (edit instance, settings, add instance) should be checked at narrow widths.

Acceptance criteria

  • Usable and tidy from roughly 768px to 1366px wide, at portrait heights too
  • Top bar never wraps button labels; it collapses (icons only, overflow menu, or similar) when space runs out
  • Overall CPU/RAM totals from #38 visible at narrow widths in some form
  • Side panel adapts (narrower, collapsible, or moved below the grid)
  • Main modals fit without horizontal scrolling
  • Playwright coverage at a portrait viewport (e.g. 900x1400)

Phone-sized screens are tracked separately in #99.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.