Repository navigation
docs: add What's new page, seeded with the October 19 update - #12
Open
yanboishere wants to merge 3 commits into
Open
yanboishere wants to merge 3 commits into
yanboishere wants to merge 3 commits into
Conversation
Release announcements (such as the October 19 post on X) are curated,
user-facing highlights, so they get a What's new page modeled on Codex's.
The exhaustive per-version changelog stays in GitHub Releases, which each
section links to; the docs keep no changelog of their own.
- docs/whats-new.md in en/zh/ja/ru: one dated section per announcement,
verb-led entries with explicit ASCII anchors shared across locales,
the announcement card image, and a link to the v0.22.0 release notes
- Top-nav item and a sidebar entry under References in every locale;
two-level outline so readers can jump to individual entries
- Agents / ACP documents Grok Build (sign-in options, permission modes,
no adapter needed), with a {#grok-build} anchor; it previously said
only Codex and Claude Code ship
- CONTRIBUTING records what belongs in What's new versus release notes
and the entry format; READMEs list the page
Keep the entry to the four highlights from the announcement; the section still ends with the link to the full v0.22.0 release notes.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
发版公告放在哪里
参考 Codex 文档的做法，更新内容分成两个页面：
我们 10 月 19 日在 X 上发的公告挑了 4 个亮点，其余用一句「Plus dozens of bug fixes and visual polish across the app」带过，配一张宣传卡片，没有版本号，属于 What's new。它对应的 changelog 已经存在：同一天发布的 v0.22.0 GitHub Release，约 20 项功能、70 项修复，其中修复大多是内部改动。产品「关于」页里的更新日志读的也是这份 Release。所以本 PR 只新增 What's new 页面，changelog 继续由 GitHub Releases 承担，What's new 的每一节都链接到对应的 Release。
本 PR 的改动
docs/whats-new.md，并在 zh/ja/ru 下镜像（最新动态 / 新着情報 / Что нового）。顶栏和侧边栏「参考文档」分组下都有入口。###标题以动词开头，带显式 ASCII 锚点（如{#2026-10-19-grok-build}），各语言的深链保持一致。大纲显示两级标题，可以直接跳到单条更新。检查
vitepress build通过。acp#grok-build都存在。