Repository navigation
homepage: implement the outcome-first catalog and product-page rollout #2
Description
Interaction review — 2026-10-23
P2 · 主站的产品发现方向保留，展示权重应跟随真实可用性。
Observed evidence and scope
The current source already separates product categories and developer libraries, provides language/theme controls, focus outlines and reduced-motion handling. It is a catalog, not the native app evidence. A polished card must not be read as proof that the underlying product flow is complete.
Source snapshot: d32f8400264c3b6dddd613d207331934e2d7694e. Central policy read: d32f8400264c3b6dddd613d207331934e2d7694e; Rivet interaction guide read at 1ced9e9e898173d9b95a9fdd0e746ef822b6c51a.
Product decision
- Use at most a few qualified products as featured stories, each with a real packaged-product screenshot and a proven first task; keep experiments/maintenance clearly labelled.
- Keep internal review/price hypotheses outside customer navigation. Product-page improvements follow the corrected primary workflow, not a shared marketing template alone.
Acceptance before closing
- A visitor can find a relevant usable product, its actual platform/readiness, guide and feedback without reading architecture or a pricing plan.
- Featured download/screenshot claims cite the exact release evidence; bilingual and narrow-window navigation retain current accessibility behavior.
Handoff boundary
This is an architect review and implementation contract, not a runtime fix. Refresh the repository, relevant open PRs and current policies before taking one bounded slice; record starting SHA, owned files and native evidence. Preserve active writers and existing release/security gates. A paused product is not automatically restarted. Source findings and required failure-injection scenarios above are not claimed as three-platform runtime validation. Use synthetic data; do not access real keys, publish content or operate real hardware for this review.
Shared baseline: product experience contract.
Earlier issue context (retained)
Latest rollout verification (2026-10-23)
The redesigned homepage is now visible at https://jrtx.site/ in a fresh browser check: outcome-led hero, task categories, separate builder section and public product/pricing link. Pages run 39880685922 for source 311fea24c51f9049eb06c4c2f870a0cabccd7cf6 succeeded. Later adoption-only documentation is queued separately; it does not change the verified HTML. A default-branch readback confirms delivery/language/portfolio links in all 25 audited AGENTS files. Taskly/Payback still hand off full pricing through their own PR gates; product-site/native acceptance is not inferred from the main-site screenshot.
本轮实施进度（2026-10-23）
主站结果导向 hero、19 项产品用途分类、写作/开发者分层及统一反馈/许可/方案入口已提交。16 个应用各有明确收费/免费设计；Taskly PR #60 和 Payback PR #21 以文档 PR 交接。旧 Pro 月订阅/终身托管文案已在 Fulcrum/HackDigest 源码中撤下。静态结构、内联脚本及本地浏览器预览已检；GitHub Pages 仍排队，线上当前仍可能为旧页，未宣称部署完成。
目标
执行 治理与主页规划 PR #1 的 HOME-PAGE-PLAN。保留现有静态零构建、双语和自托管字体；不新增前端框架。
切片顺序
- 用户已确认 Keepsake / Moonbeam 等找不到的仓库已删除。先清理主站对应残留卡片、进度CTA、导航和双语文案；从当前组合移除，不再安排来源补齐或恢复开发。再核对真实可下载版本与主站/产品页/README/GitHub About：纠正 gptp GTK3/WebKit 旧栈、Payback 桌面Pro预告及授权语义矛盾。
- 主站先呈现任务结果与最多三个已验收产品故事，再提供完整目录、汽车专业工具、实验区、写作/社区和builder区。技术栈标签降为次要信息；Alpha不显示下载按钮。
- 按 gptp→Fulcrum→Taskly/Booklight/PodLens 的就绪顺序改产品页，不同时重写全部站点。每页统一任务截图、安装/更新矩阵、隐私/AI、实际收费与支持/反馈。
验收
320/375/768/1440px、200%缩放、亮暗色、中英文、键盘焦点/语义标题/减少动效；逐卡检查HTML闭合和全部CTA。展示真实截图、真实可用资产和明确许可，未开售不放数字预告/Buy按钮。Pages部署后比对预期source SHA与实际HTML；保留上一部署提交可回滚。每次认领一个有边界切片，更新对应产品issue，不抢活动共享层文件。
Activity