Layout should look good in a vertical (portrait / narrow) window
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
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
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Isopod-Project/Isopod
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Isopod-Project/Isopod#220 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Isopod-Project/Isopod#200 ·
Maintainers usually reply within 1 day
-
Dashboard drives high GPU usage while a server starts or restartsPossibly taken @tacoz234 claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Isopod-Project/Isopod#191 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Isopod-Project/Isopod#134 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Isopod-Project/Isopod#113 ·
Maintainers usually reply within 1 day
All issues in Isopod-Project/Isopod
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·