[BUG] : Footer content overlaps on tablet and reduced window sizes

[karthikvemula23]

Bug description

The footer layout breaks on tablet-sized and narrow viewport widths. When the browser window is reduced, the right-side footer content (Updates and Community sections) overlaps with the Navigation section.

This causes:

• The UPDATES heading to collide with the NAVIGATION heading.
• The newsletter input field to overlap Navigation content.
• The COMMUNITY heading to overlap the Privacy Policy link.

This creates visual layout issues and reduces readability in the footer.

---

Steps to reproduce

1. Open the application.
2. Scroll to the footer section.
3. Gradually reduce the browser window width to a tablet-sized viewport.
4. Observe the positioning of the Navigation, Updates, and Community sections.
5. Notice that the right-side footer content overlaps with the Navigation section.

---

Expected behavior

The footer sections should maintain proper spacing and alignment across all viewport sizes. The Updates and Community sections should remain visually separated from the Navigation section without any overlapping content.

---

Actual behavior

When the viewport width is reduced, the right-side footer content shifts into the Navigation section, causing headings, form elements, and links to overlap and creating layout inconsistencies.

---

Browser and OS info

• OS: Windows 11
• Browser: Microsoft Edge (Chromium)
• Version: Latest

---

Screenshots/screen recording

[github-actions]

👋 Thanks for opening an issue, @karthikvemula23!

Our maintainers will review this shortly 🚀

Before you start working

• 📖 Read the CONTRIBUTING.md guide
• 💬 Wait for a maintainer to assign you the issue before starting work
• 🔍 Search for existing issues to avoid duplicates

For GSSoC'26 contributors

If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:

"I'd like to work on this — contributing under GSSoC'26"

Architecture notes

Reframe is a static Next.js app with output: "export". Key points:

• All video processing uses FFmpeg.wasm (client-side, no server)
• headers() in next.config.ts won't work — use vercel.json instead
• not-found.tsx requires public/404.html + vercel.json routes config

Happy contributing! ⭐ Star the repo if you find it useful!

[karthikvemula23]

/assign

I'd like to work on this issue under GSSoC'26.

[github-actions]

Hey @karthikvemula23, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.