feat: add responsive reusable footer component

[fabrohit03]

Summary

Added a responsive and reusable footer component to improve UI consistency and navigation.

Changes Made

• Added reusable Footer component
• Added quick navigation links
• Added icons and support section
• Added modern responsive UI styling
• Added hover effects and smooth interactions
• Added optional back-to-top button
• Improved footer spacing and overall appearance
• Added theme-compatible styling support

Testing

• Tested on Landing Page
• Tested responsiveness and footer layout
• Verified footer renders correctly across pages

[fabrohit03]

@suresh1319 Sir, I have implemented the responsive reusable footer component with navigation links, icons, support section, hover effects, and responsive styling. Sorry for the delay .Kindly review the PR. Thank you.

[entelligence-ai-pr-reviews]

---

Confidence Score: 3/5 - Review Recommended

Not safe to merge without changes — the PR introduces a reusable Footer component with good intent, but has correctness issues that will produce visible bugs in production. Placing <Footer /> globally in App.js outside <Routes> causes a duplicate footer on LandingPage where an inline footer already exists, and the use of plain <a href="/"> tags in Footer.jsx instead of React Router <Link> components will trigger full page reloads on every footer navigation click, undermining the SPA experience. The placeholder href="#" links also pollute browser history and scroll users to the top unexpectedly.

Key Findings:

• In App.js, rendering <Footer /> globally outside <Routes> results in a duplicate footer on LandingPage, which already contains its own inline footer — this is a visible UI regression that users will notice immediately.
• In Footer.jsx, using plain <a href="/"> and <a href="/join"> anchor tags instead of React Router <Link> components causes full browser page reloads on navigation, breaking the SPA model and losing React state.
• Placeholder href="#" links in Footer.jsx scroll the page to the top and push spurious entries into browser history on every click, which degrades UX and breaks the browser back button flow.
• The component itself is a reasonable foundation — responsive layout, semantic HTML, and a clear separation of concerns — but the integration and link implementation need to be corrected before it can be safely merged.

Files requiring special attention

• src/App.js
• src/components/Footer.jsx

[fabrohit03]

@suresh1319 Sir, I have addressed the review comments and updated the PR.

✅ Removed duplicate footer rendering
✅ Replaced internal anchor navigation with React Router Link components
✅ Improved footer UI with responsive layout, icons, hover effects, and cleaner styling
✅ Verified the application builds and runs successfully

Kindly review the updated PR. Thank you.

[entelligence-ai-pr-reviews]

EntelligenceAI PR Summary

This PR extracts and refactors the Footer into a reusable component, relocating it from the global router to LandingPage and improving semantic markup and styling.

• src/App.js: Removed global Footer component import and JSX usage
• src/pages/LandingPage.js: Imported and rendered shared <Footer /> component, removing hardcoded footer markup
• src/components/Footer.jsx: Migrated internal navigation links (Home, Join Room) to React Router <Link> with footer-link class; converted Support and Community placeholder anchors to <button> elements with footer-btn class
• src/components/Footer.css: Updated background color, top margin, and container alignment; added .footer-link and .footer-btn classes with hover/transition support; updated responsive breakpoint to target new selectors

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR cleanly extracts the Footer into a reusable component in src/components/Footer.jsx, relocates it from the global router in src/App.js to src/pages/LandingPage.js, and upgrades internal navigation to use React Router <Link> elements with appropriate footer-link styling. The refactor is well-scoped with no logic changes, no new dependencies beyond what React Router already provides, and no runtime risk introduced. All four changed files were reviewed with zero issues identified, making this a straightforward, low-risk component extraction.

Key Findings:

• The migration from hardcoded anchor tags to React Router <Link> components in Footer.jsx is semantically correct and avoids full-page reloads for client-side navigation, which is the expected pattern in a React Router app.
• Removing the global Footer import and JSX from src/App.js and scoping it to LandingPage.js is architecturally sound — it avoids rendering the footer on routes where it may not be appropriate.
• No new logic, state management, or data-fetching is introduced; the change is purely structural/presentational with zero runtime risk.
• Full 4/4 file coverage was achieved in the review with no comments generated, confirming the implementation is clean and consistent across all touched files.