[UI] Typography token Heading 1 overflows on mobile viewports
Maintainers usually reply within 1 day
@tanav29 is already working on this.
Since Nov 10, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, javascript
Research direction
The affected page is the Sistent Design Tokens documentation (Getting Started → Design Tokens), so start by locating the typography tokens section and the Heading 1 preview component that renders it, and read the width and font-size rules applied there. Reproduce at 414px and 360px in responsive design mode, then adjust responsive font sizing or width constraints so Heading 1 stays on one line. Done means no horizontal clipping at 360px and the typography hierarchy still reads correctly at desktop widths.
Written by the indexing model from the issue text.
Description
Description
The Heading 1 typography preview in the Sistent Design Tokens documentation does not adapt properly to smaller mobile viewports.
At narrower screen widths, the heading exceeds the available content width, resulting in awkward text wrapping and horizontal clipping.
Affected page: Sistent → Getting Started → Design Tokens
Steps to Reproduce
- Open the Sistent Design Tokens page.
- Open the browser's responsive design mode.
- Set the viewport width to approximately 414px.
- Scroll to the Typography Tokens section.
- Observe the Heading 1 typography preview.
- Repeat with a viewport width of approximately 360px.
Actual Behavior
- At 414px, the Heading 1 text wraps awkwardly, separating the word "Heading" from the number "1".
- At 360px, the heading extends beyond the available content width and gets clipped.
- The typography preview does not scale or adapt appropriately to smaller screens.
Expected Behavior
The typography preview should adapt to smaller viewport widths without causing horizontal overflow or clipping.
Heading samples should remain fully visible and maintain an appropriate responsive layout while preserving the intended typography hierarchy.
Environment
- Page: Sistent Design Tokens — Typography
- Viewports: 414 × 846 and 360 × 760 pixels
- Browser: Firefox
- Issue type: UI / Responsive Design
Suggested Investigation
Inspect the responsive styles and width constraints applied to typography preview components, particularly the Heading 1 sample.
Consider using responsive font sizing or appropriate width constraints to ensure typography samples remain readable on smaller screens.
Evidence
Attached screenshots demonstrate the issue at two different mobile viewport widths.
Contribution
Anyone can work on this...
- 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
-
Fix logo/graphic fitting within its container on mobile viewportsPossibly taken @AP24110011695 claimed this 14 days ago. Openframework/gatsby good first issue help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
layer5io/layer5#8272 · 4 comments ·
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