Add integration test for marketing page community links having correct href values

[Chucks1093]

Summary

The marketing page has GitHub and Telegram community links. These need a test confirming the href values point to the correct URLs so a refactor cannot silently break them.

Scope

• Render the MarketingPage component in the test environment
• Assert the GitHub link href is https://github.com/accesslayerorg
• Assert the Telegram link href is the correct Telegram URL
• Assert both links have target="_blank" and rel="noopener noreferrer"

Acceptance Criteria

• GitHub link href is correct
• Telegram link href is correct
• Both links open in a new tab with correct rel attribute

ETA: 12 hours

---

Coordinate on Telegram

[Benedict315]

@Benedict315 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello please assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Benedict315 to this issue.

[samjay8]

@samjay8 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Boss, please kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @samjay8 to this issue.

[yunus-dev-codecrafter]

Hi! I've carefully reviewed the entire task description and fully understand the requirements and expected outcome.
I have experience working on similar tasks and I'm confident I can complete this within about an hour. I'd be happy to take ownership of this issue and submit a clean, well-tested solution promptly.
If it's available, please assign it to me. Thank you!

[drips-wave]

Congratulations, @samjay8! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @samjay8: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @samjay8 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 #428)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@samjay8's PR #432 was approved and merged by @Chucks1093.

🏆 @samjay8: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (366 total points). Track your full progress on GrantFox.

👏 Great work, @samjay8! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @samjay8 as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully implemented the required integration tests for the marketing page links. Although PR #431 was closed due to targeting the wrong base branch, the maintainer's activity logs confirm that the contributor's subsequent PR #432 was approved and merged to complete the issue.

😎 @samjay8: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.