[Bug] Fix broken footer links pointing to "#" instead of real destinations

[grantfox-oss]

Getting Started

1. Fork the repository: https://github.com/JointSave-org/Joint_Save
2. Clone your fork:

   git clone https://github.com/<your-username>/Joint_Save.git
   cd Joint_Save

3. Create a new branch:

   git checkout -b fix/footer-placeholder-links

---

Overview

frontend/components/landing/footer.tsx has 5 links that currently point to href="#" — 3 likely social/community links and 2 legal page links ("Privacy Policy", "Terms of Service"). These are dead links that do nothing when clicked, which looks unfinished on a public-facing landing page.

Requirements

• For the 3 social/community-style links: confirm with the maintainer what they should actually point to (GitHub repo, Discord/Telegram if one exists, X/Twitter if one exists) and update accordingly
• For "Privacy Policy" and "Terms of Service": if these pages don't exist yet, either:
  • Create minimal placeholder pages at /privacy and /terms with a clear "Coming soon" notice, or
  • Link to a shared document (e.g. a Notion page or GitHub markdown file) if the maintainer has one in mind
• Do not leave any link as a bare href="#" — if a real destination genuinely doesn't exist yet, at minimum disable/style the link distinctly so it doesn't look broken

Acceptance Criteria

• No remaining href="#" links in footer.tsx
• Every link either goes to a real destination or is clearly styled/marked as "coming soon" rather than silently doing nothing
• Links open in a new tab where appropriate (external links) using target="_blank" rel="noopener noreferrer"

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[Yasir-TechGuy]

Hi Maintainer,

I'd like to work on this issue. I have experience with Next.js frontend development and polishing production-facing user experiences. I'll review the existing footer links, coordinate on the intended destinations where needed, and ensure there are no dead href="#" links by replacing them with valid targets, dedicated placeholder pages, or clearly marked disabled states.

ETA: 1–2 hours

Please assign this issue to me.

[felladaniel36-hash]

​Hi maintainer, I would love to work on this issue. I can get started on it right away. Could you please assign it to me?

[dolaoluwa574-source]

pls assign me

[ODbeke]

This task is a great match for my skillset.
Here is my plan to address the requirements:

1. Social/Community Links: I'll update these to point to the correct destination. I will confirm the correct URLs with the maintainer before making the final changes.
2. Legal Pages: If the Privacy Policy and Terms of Service documents aren't ready yet, I will create clean, minimal placeholder pages at /privacy and /terms with a polished "Coming soon" message. Alternatively, if maintainer have a shared Notion doc or markdown file, I can link to those.
3. UX & Security: I'll ensure all external links open securely in a new tab using target="_blank" rel="noopener noreferrer", and that no dead href="#" links remain.
   I can get started on this right away if assigned.

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.

[Justprotocol]

Hi maintainer! I'd love to work on this.

As someone with a background in Product Management and frontend HTML/CSS, I can ensure these footer links aren't just technically fixed, but have a polished UX.

My plan:

Check your repository settings/socials to find the correct links for X, GitHub, and Discord, and apply them using target="_blank" rel="noopener noreferrer".

For the Privacy/Terms links, I will create clean, minimal placeholder components with a sleek 'Coming Soon' state so the site looks fully professional, or link to a markdown file if you prefer.

I'm eady to jump in and submit a PR quickly.

[GBOYEE]

Approach

1. Audit — Identify all footer links currently pointing to # or empty hrefs
2. Map destinations — Determine correct URLs (Docs, GitHub, Discord, Twitter/X, Terms, Privacy, etc.)
3. Update component — Replace # hrefs with actual links in Footer component
4. External links — Add target="_blank" rel="noopener noreferrer" for external URLs
5. Verify — Click through every footer link to confirm they resolve correctly

Quick, clean fix. Ready now.

[grantfox-oss]

🦊 GrantFox — @Justprotocol has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #108)
2. Your PR will be reviewed by the JointSave-org maintainers

Good luck! Track your progress on GrantFox.

[Justprotocol]

Hey maintainer! I'm working on Issue #108 to update the broken footer links. Just to make sure everything points to the exact right places, could you share the official URLs you'd like me to use for the Twitter/X and Discord handles?

Once you drop those here, I'll get them updated right away. Thanks!