Fix logo/graphic fitting within its container on mobile viewports
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- css, javascript
- Domain
- frontend
Research direction
Search the repo for the HPE case study section component (likely a Gatsby/React file under src/). Inspect its CSS for the logo container and add responsive scaling rules for widths like 360px and 546px. Done means the logo fits proportionally, centered, with no overflow in responsive mode.
Written by the indexing model from the issue text.
Description
Description
The logo/graphic in the HPE case study section does not appear to scale and fit correctly within its container on smaller mobile viewports.
When testing the page using responsive mode, the layout appears inconsistent across different mobile screen widths.
Page: https://layer5.io
Steps to Reproduce
- Visit the HPE case study page.
- Open browser developer tools and enable responsive design mode.
- Test the layout at different mobile viewport widths (e.g., 546px and 360px).
- Observe how the logo/graphic is rendered inside its container.
Expected Behavior
- The logo/graphic should scale proportionally to fit within its parent container.
- It should remain properly centered and maintain its aspect ratio.
- No clipping, overflow, or unwanted spacing should occur at smaller viewport widths.
Actual Behavior
The logo/graphic does not scale consistently across mobile viewport widths. Its sizing and alignment within the container appear inconsistent, resulting in a layout that does not adapt cleanly to smaller screens.
Environment
- Browser: Firefox
- Testing mode: Responsive Design Mode
- Viewports: 546px and 360px
- Device emulation: Android
Screenshots
Screenshots demonstrating the behavior at different viewport widths are attached.
Anyone can work on this issue
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 1.7k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 69
Getting set up
- No 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 layer5io/layer5
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Fix inconsistent visibility and clipping of Slick carousel navigation arrows on mobilePossibly taken @AP24110011695 claimed this 14 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
layer5io/layer5#8275 · 4 comments ·
Maintainers usually reply within 1 day
-
[UI] Typography token Heading 1 overflows on mobile viewportsPossibly taken @tanav29 claimed this 4 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
layer5io/layer5#8267 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
[UI] Theme Provider Props table overflows on mobile viewportsPossibly taken @SajanBisht claimed this 15 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
layer5io/layer5#8264 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
[Pricing] Plan cards reference non-existent "Free" and "Team" tiersPossibly taken @sameerkrdev claimed this 14 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
layer5io/layer5#8258 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
good first issue help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dlq/synthpopcan#58 ·
Maintainers usually reply within 2 days
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
osmlab/name-suggestion-index#13104 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fjaeckel/seriesoftubes#376 ·
Maintainers usually reply within 1 day
-
0. Needs triage 35-feedback bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day