Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[UI] Footer social links overflow out of container on small and desktop/tablet screens

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

@AliRana30 is already working on this.

Since Oct 4, 2026.

  • #19 by @AliRana30 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
scss
Domain
frontend

Research direction

Start by locating the footer styles and reproducing the overflow at tablet or narrow desktop widths. Check how the footer columns are sized and whether they can wrap within the container. Done when all four columns, including Socials, stay inside the footer at the affected widths.

Written by the indexing model from the issue text.

Description

kind/bug
URL

https://discuss.meshery.io/u/[username]/activity/replies

Current Behavior

On small and intermediate/narrow desktop viewports, the footer columns do not wrap into a secondary row. As a result, the 4th column (Socials) overflows horizontally beyond the right boundary of the footer container and spills onto the background.

Expected Behavior

Footer columns should wrap responsively (e.g., into a 2x2 grid or column stack) using flex-wrap: wrap and appropriate max-width sizing so that all sections, including Socials, remain fully within the footer container.

Steps to Reproduce
  1. Navigate to https://discuss.meshery.io/u/[username]/activity/replies (or any discuss page).
  2. Resize the browser window to a tablet or narrower desktop width (or inspect with responsive view).
  3. Scroll down to the footer.
  4. Notice the Socials column overflowing past the right edge of the dark footer container.
ScreenRecording

https://github.com/user-attachments/assets/a6769af6-9e9b-47b3-bfcf-5da96a427afa

Dominant language
SCSS
Stars
17
Forks
16
Avg merge
3h 12m
Merged PRs (30d)
2

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 layer5io/discuss-theme

All issues in layer5io/discuss-theme

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.