Mobile responsiveness issue on landing page

Open Beginner friendly
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend, web-dev

Research direction

Open the landing page and inspect the section headed “Integrate in Minutes, Not Months” at a mobile viewport, then trace the code snippet container and the call-to-action before the footer. Verify the layout at multiple narrow widths and confirm that horizontal scrolling, right-side blank space, and the oversized mobile button are gone.

Written by the indexing model from the issue text.

Description

The mobile version of the landing page is not fully responsive in the section with the heading:
“Integrate in Minutes, Not Months”
The code snippet container in this section appears to overflow horizontally on smaller screen sizes, causing:

  • horizontal scrolling,
  • layout overflow,
  • and extra blank space on the right side of the mobile viewport.

Actual behavior
On mobile devices:

  • the code snippet box extends beyond the viewport width,
  • the page can be dragged/slid horizontally,
  • and a blank area appears on the right side of the screen.

Steps to reproduce

  1. Open the landing page on a mobile device or browser dev tools.
  2. Navigate to the section titled:
“Integrate in Minutes, Not Months
  3. Attempt horizontal scrolling.
  4. Notice the extra whitespace/overflow on the right side.

Environment

  • Mobile viewport
  • Reproduced in browser responsive mode
  • Likely affects multiple mobile screen sizes
Image Image Also the call to action button before the footer is too big on the mobile too: Image

@roncodes @shivthakker

Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
23h 4m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.