fix: add page titles and meta tags for all major routes [nsoc26]

[Ananya-CM]

Summary

Added page-specific titles and global meta tags to
FlowForge. Previously all pages showed a blank or
generic browser tab title.

Changes Made

Modified Files

1. frontend/app/layout.tsx
   • Added global Metadata export with title template
   • Default title: "FlowForge"
   • Template: "%s — FlowForge" for all pages
   • Added meta description for SEO

New Files Created

2. frontend/app/dashboard/layout.tsx

   • Title: "Dashboard — FlowForge"

3. frontend/app/projects/layout.tsx

   • Title: "Projects — FlowForge"

4. frontend/app/login/layout.tsx

   • Title: "Sign In — FlowForge"

5. frontend/app/signup/layout.tsx

   • Title: "Create Account — FlowForge"

Why Route Layouts Instead of Page Metadata?

All page components (dashboard, projects, login, signup)
use "use client" directive which prevents direct metadata
exports. Route-level layout.tsx files are server components
by default, making them the correct Next.js approach for
adding metadata to client component pages.

Before

• All pages showed blank or "localhost:3000" in browser tab
• No meta description for any route

After

• localhost:3000 → "FlowForge"
• localhost:3000/dashboard → "Dashboard — FlowForge"
• localhost:3000/projects → "Projects — FlowForge"
• localhost:3000/login → "Sign In — FlowForge"
• localhost:3000/signup → "Create Account — FlowForge"

Screenshots

Files Changed

• frontend/app/layout.tsx ← modified
• frontend/app/dashboard/layout.tsx ← new
• frontend/app/projects/layout.tsx ← new
• frontend/app/login/layout.tsx ← new
• frontend/app/signup/layout.tsx ← new

Issue

Closes #89

nsoc26

[vercel]

@Ananya-CM is attempting to deploy a commit to the shreemp194-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thank you for opening this pull request! I will review your changes and assist you soon.