fix: prevent footer overlap on tablet viewports

[karthikvemula23]

Description

Summary

Fixes footer layout overlap on tablet-sized and narrow viewport widths.

Changes Made

• Updated the newsletter form width from sm:w-80 to lg:w-80
• Allows the newsletter input to remain responsive on tablet and reduced viewport widths
• Prevents the Updates and Community sections from overlapping with the Navigation section
• Preserves the original desktop appearance by applying the fixed width only on large screens

Result

The footer now maintains proper spacing and alignment across desktop, tablet, and narrow window sizes without content collisions.

Related Issue

Fixes #1594

Type of Contribution

• Bug fix
• New feature
• Documentation update
• Refactor
• GSSoC contribution

Participant Info

• GitHub username: karthikvemula23
• Contribution level (Beginner/Intermediate/Advanced): Intermediate

Screenshots

Before

After

## Checklist

• I have read the contribution guidelines
• My changes follow the project structure
• [x ] I have tested my changes in Edge, Chrome, Firefox, and Safari
• [ x] bun run lint passes (no ESLint errors)
• [x ] bunx tsc --noEmit passes (no TypeScript errors)
• New interactive elements have aria-label / accessible names
• No console.log statements left in
• This PR is related to a valid issue
• Screenshots attached above

[vercel]

@karthikvemula23 is attempting to deploy a commit to the magic-peach1's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

✅ PR Format Check Passed — @karthikvemula23

Basic format checks passed. A maintainer will review your code changes.

This does not mean the PR is approved — it just means the format is correct.

[github-actions]

👋 Thanks for your PR, @karthikvemula23!

Welcome to Reframe — a browser-based video editor built for everyone 🎬

🟠 GSSoC'26 PR detected — thanks for contributing under GirlScript Summer of Code 2026!

What happens next

1. 🤖 Automated checks — build & TypeScript typecheck will run automatically
2. ✅ Vercel preview — a preview deployment will be created (requires maintainer authorization for fork PRs)
3. 👀 Code review — a maintainer will review your changes
4. 🚀 Merge — once approved, your PR will be merged!

Quick checklist

• PR title follows Conventional Commits (e.g. feat: add dark mode)
• Linked the issue this PR closes (e.g. Closes #123)
• Tested the changes locally (bun run dev)
• Build passes (bun run build)

Useful links

• 📖 CONTRIBUTING.md
• 🐛 Open Issues
• ⭐ Star the repo to support the project!

Happy coding! 🎉