docs site: homepage `<title>` and description are not keyword-shaped (description is 615 characters)

[os-zhuang]

One-liner

The homepage <title> is ObjectStack — Apps small enough for AI to hold whole. — a brand slogan with no term anyone searches for — and its meta description is 615 characters, roughly four times what a result shows.

Measured

apps/docs/app/[lang]/page.tsx metadata.description → 615 chars
<title>ObjectStack — Apps small enough for AI to hold whole.</title> (53 chars, 0 search terms)

Expected — bounded scope, on purpose

• Do not touch the <h1>. The slogan stays exactly as it is; it is the maintainer's line and it works as a hero.
• Change only metadata.title and metadata.description in apps/docs/app/[lang]/page.tsx, plus optionally the small uppercase eyebrow above the h1.
• title: lead with what it is, keep the slogan second if it fits in ~60 characters — e.g. Open-source metadata framework for AI-built business apps.
• description: 120–155 characters, drawn from the existing copy — the first paragraph already says it ("turns the whole app … into typed metadata"), it just needs cutting.
• Candidate terms to place naturally, not stuff: metadata-driven framework, TypeScript, AI coding agent, MCP server, open source, self-hosted, business apps.

Acceptance

• <title> ≤ 60 characters and names the category, not only the brand
• meta description 120–155 characters
• the rendered <h1> is byte-identical to what it is today

Source

Found in an SEO review of the docs site (apps/docs) run on 2026-08-25, measured against the local dev server and against production. The canonical origin is https://objectstack.ai — maintainer ruling recorded in #10659:

这个仓的文档站规范 URL 是 https://objectstack.ai

[os-zhuang]

Claim: PM loop round 2 (epic PM for #12243)
Session: session_f9f0958b-ab68-46cc-801c-216aa7ee2107
Branch: claude/issue-12239-homepage-keywords
Worktree: objectstack-issue-12239
Domain: domain:devx
File surface: apps/docs/app/[lang]/page.tsx — the exported metadata object, and optionally the uppercase eyebrow above the h1. Nothing else. (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: opus — node scripts/pm/dispatch-gates.mjs --tier on this path derives no mandate; the tier is for judgement about the maintainer's voice, not for volume
Clause-②: no
Serial constraints cleared: this file was released by PR #12218 merging at 14:56:33Z (eeec62a98). No in-flight PR touches it — #12253 adds three new files, #12258 touches lib/i18n.ts and [lang]/layout.tsx, #12262 touches content/docs/**. #12242 is queued BEHIND this card on the same file.

[os-zhuang]

Dev claim (os-dev subagent under the epic PM's round-2 dispatch for #12243)

Session: session_f9f0958b-ab68-46cc-801c-216aa7ee2107 (dev subagent runs inside the epic PM session; same id, distinct seat)
Branch: claude/issue-12239-homepage-keywords (pushed empty at claim time — write routing verified)
Worktree: /Users/zhuangjianguo/Documents/GitHub/objectstack-issue-12239
Base: adea66d6694b7124d56a048e0a8f0c605498c3ea

File surface accepted as dispatched: apps/docs/app/[lang]/page.tsx only — the exported metadata object, plus the uppercase eyebrow above the h1 if a keyword genuinely belongs there. The <h1> stays byte-identical. No changeset (docs-site only); skip-changeset label on the PR.

Read before starting: this issue body + comments, epic #12243 body + all four comments (including the two recorded corrections), and finding #12255 (app/page.tsx is a shadowed route — the served homepage is app/[lang]/page.tsx). Verification will be against a rendered response from a running server, not against the file.