feat: add contact page and footer link

[KrutagyaKaneria]

Summary

• Added a new /contact page with a responsive contact form
• Implemented basic form validation and submission feedback states
• Added a visible "Contact" link in the footer
• Improved styling to match the existing DevTrack theme and design system
• Ensured responsive behavior across devices

Closes #1401

Please add the gssoc:approved label after review if everything looks good.

Screencast.From.2026-05-28.18-04-12.mp4

[vercel]

@KrutagyaKaneria is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[Priyanshu-byte-coder]

The contact form simulates submission with a setTimeout delay but doesn't actually send the message anywhere — the try block just waits 700ms and always succeeds. Please either:

1. Add a real API route (/api/contact) that sends the message (e.g. via Resend/email), OR
2. Replace the form with a redirect to GitHub Issues if no backend is intended.

The supabase.ts and LanguageBreakdown.tsx changes (remove ESLint comment + add role="img") are good — keep those.

Please fix the form submission before this can be merged.

[vercel]

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

[Priyanshu-byte-coder]

The contact page UI is well done, but the form submits to a /api/contact endpoint that doesn't exist in the codebase. Please either:

1. Add a /api/contact route that handles form submissions (e.g. sends an email via Resend/SendGrid, or saves to Supabase), OR
2. Use a third-party form service (Formspree, etc.) and update the form action accordingly.

Without a working backend, the form will 404 on submit. Please rebase on main after implementing the API route.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	JSON Web Token	c6e7fa1	.github/workflows/ci.yml	View secret
-	-	Generic High Entropy Secret	c6e7fa1	.github/workflows/ci.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}