[Di-vyansh]

What

Add a server layout for /journey with its own title, one-sentence description, and canonical URL. The browser title becomes Our Journey | DevForge using the root title template; the client page continues to render unchanged.

Fixes #64

How I tested it

• Node 24: installed the locked dependencies with npm ci.
• npm run lint: passed (0 errors; 36 existing warnings elsewhere).
• npm test: passed, 121 tests across 13 files.
• npm run build: passed, including TypeScript checks and static generation.
• Opened /journey from the production build and verified the page renders, the title is Our Journey | DevForge, the description matches the new metadata, and the canonical URL is https://www.devforge.club/journey.

Checklist

• I was assigned the issue before I started
• npm run lint and npm run build pass locally
• The diff only touches what the issue asked for

Screenshot

[vercel]

@Di-vyansh is attempting to deploy a commit to the Geetansh Goyal's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

📸 How this looks

Built from this PR, so you can see the change without checking it out.

/

Desktop (1280px), top 3000px

Mobile (390px), top 3000px

/learn/open-source

Desktop (1280px), top 3000px

Mobile (390px), top 3000px

_{Screenshots are taken from a production build of this PR, signed out. Pages behind sign-in show the signed-out view. Build log}

[garv-sanveria]

Review type: Read-only

Great addition to improve the SEO of the Journey page!

Actionable Suggestion: Since this is a metadata object, you might want to consider adding openGraph properties (like og:title and og:description) so that the link unfurls nicely when shared on Discord or Twitter.

Question: By the way, did you check how the canonical URL behaves? Does Next.js automatically prepend the base domain to /journey, or do we need to provide the absolute URL (https://...) for canonical to work properly in production?