Skip to content

Student profile pages: generate a title and description per student #70

Description

@geetxnshgoyal

Problem

app/students/[slug]/page.tsx is a client component, so every student profile has the same generic tab title and no description. It's the page a student would share on LinkedIn.

Done when

  • Add app/students/[slug]/layout.tsx with generateMetadata({ params }) that looks up the student in data/students.ts and returns title: "<Name> | DevForge", a one-line description, alternates.canonical, and openGraph.images set to their photo.
  • An unknown slug still 404s.
  • Share-preview check: paste a profile URL into https://www.opengraph.xyz (or view source) and see the right name and photo.
  • npm run build passes.

Size: ~25 lines. params is a Promise in this Next version, so await it.


Taking this? Comment /assign and the bot assigns you if it's free. One issue per person at a time; comment /unassign to hand it back. That's milestone 2 of the 10 PR Journey. Setup, the checks CI runs, and how to open the PR from your fork are in CONTRIBUTING.md. Put Fixes #<this issue> in your PR description.

Activity

  1. piushisharma commented on Oct 4, 2026

    @piushisharma

    /assign

  2. github-actions commented on Oct 4, 2026

    @github-actions

    @piushisharma it's yours! 🎉

    1. Fork the repo and create a branch: see CONTRIBUTING.md.
    2. Open your PR from your fork into main, with Fixes #70 in the description.
    3. Make sure CI (Lint, Test, Type-check & build) is green.

    Can't finish it? Comment /unassign so someone else can pick it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

seoMetadata, sitemap, search

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions