feat(frontend): Add SEO meta tags and Open Graph cards for all pages

[KuchiMercy]

Description

The root layout.tsx metadata export (lines 13-16) only sets a generic title and description. There are no Open Graph, Twitter Card, canonical URL, or robots directives. Links shared on Slack, Discord, or Twitter show no preview card. Every page (homepage, dashboard, escrow detail) shares the same generic title.

File: apps/frontend/app/layout.tsx (metadata export), all page files

Acceptance Criteria

• Add openGraph metadata to root layout: og:title, og:description, og:image, og:url, og:type
• Add twitter card metadata: card type, site handle, creator
• Add alternates.canonical URL pointing to production domain
• Add per-page metadata overrides:
  • Homepage: compelling title + description for sharing
  • Dashboard: "My Escrows — Vaultix" (no sensitive data in meta)
  • Escrow detail: "Escrow #xxx — Vaultix" (status, no amounts)
  • Admin pages: robots: { index: false, follow: false } to prevent indexing
• Create a branded OG image (1200x630) stored in public/
• Add manifest.json link for PWA basics
• Test with Facebook Sharing Debugger, Twitter Card Validator, and LinkedIn Post Inspector
• Ensure no sensitive data (amounts, addresses) leaks in meta tags

Points: 100 | Difficulty: Trivial

[midenotch]

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

I can take this on. I've gone through the details and will provide a well-tested solution aligned with the project standards.

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

[NnamdiCyber]

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

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[drips-wave]

Congratulations, @midenotch! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @midenotch: 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 🌊

[drips-wave]

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

Moderator's reason: [Auto-assessed] The PR is open with no maintainer response or objections across any of the four channels, and the changes thoroughly and correctly implement all requirements specified in Issue #601, including root layout metadata, OpenGraph cards, Twitter cards, per-page overrides, admin robots directives, manifest.json, and the SVG open graph image.

😎 @midenotch: You earned 100 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.