Skip to content

feat: split the README into a landing page and topic pages - #51

Merged
firejune merged 2 commits into
mainfrom
jinni/48-readme-split
Nov 1, 2026
Merged

firejune merged 2 commits into
mainfrom
jinni/48-readme-split

Conversation

@firejune

@firejune firejune commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Closes #48.

README goes from 6,877 to 2,451 words, cap 2,700. The commit message carries the argument, including why the runner had to move with the prose.

Page Words
README.md 2,451
docs/guide/motion.md 1,118
docs/guide/depth-turn.md 480
docs/guide/use-what-you-made.md 689
docs/guide/make-your-own-character.md 1,612
docs/guide/troubleshooting.md 696
Command Exit Figures
Fence comparison against origin/main, by sha256 0 20 before, 20 after, 0 missing, 0 added, 0 duplicated
bun scripts/check-readme.ts 0 2,451 of 2,700
bun test scripts/check-readme.test.ts scripts/try-it.test.ts scripts/link-reader.test.ts 0 0 fail, 405 expects

Contradicted in the card: step 10 depends on 9b and 9c too, not only 9d; check-adapters.ts also read the README directly; the site's src/external-links.test.ts has no getting-started pin, and no other repository links an anchor outside the stubs kept here. The section table summed to 6,801 because it left out the 76 words above the first heading.

The walkthrough on CI is the bar this PR waits for.

🤖 Generated with Claude Code

The README had reached 6,877 words under a cap of 7,550, set in #43, so
the cap permitted the size that was the problem. It is now 2,451 words
under a cap of 2,700 (post-cut words × 1.10, rounded up to 50). Five
topic pages under docs/guide/ hold motion, the depth turn, using the
result, your own character and troubleshooting.

The move changed what CI runs unless the runner moved with it. try-it
read fences only from `## Try it first` in README, and step 10 needs 9b
and 9c as well as 9d: the primary URL plays hello, the breeze needs the
physics, and the menu needs turn. check-adapters.ts also read steps and
the PixiJS snippet straight from README. So:

- try-it follows the README's stubs into the topic pages, in the order
  1..9, 9b, 9c, 9d, 10. A removed stub is refused naming the page and
  step, and a numbered step left unlinked on any page is refused.
- guide_sha256 hashes README plus all five pages, so a change on a topic
  page triggers a run and stops a stale publish.

Measured by HQ against origin/main: 20 fences before, 20 after, none
missing, added or duplicated, compared by sha256. All 26 changed prose
lines differ only in link paths. New prose is limited to the stubs, a
title on two pages, and a Next line that carries a reader onward from 9c
and back to step 10.

Rejected: a second copy of any fence on a landing page, because the
commands have one source; hashing README alone, because moved steps
would stop triggering a run.

Closes #48

Co-Authored-By: Jinni <342598851+fj-jinni[bot]@users.noreply.github.com>
Co-Authored-By: Roa <342598975+fj-roa[bot]@users.noreply.github.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-01T05:07:42.384362Z e7ac70d PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

…ommands

rig-c/.github#13 replaced the profile's numbered table with a repository
table that names packages and carries no install commands. This check
read its three install lines from that row, so it failed on `PROFILE:
adapters row missing` for every run after that merge, on main as well as
here. It would fail the same way without this branch.

The install lines now live in the check, which is what runs them. The
profile row is held to naming the three packages, and the guide's own
line must be one of those tested.

Co-Authored-By: Roa <342598975+fj-roa[bot]@users.noreply.github.com>
@firejune
firejune merged commit 9dae774 into main Nov 1, 2026
7 of 8 checks passed
@firejune
firejune deleted the jinni/48-readme-split branch November 1, 2026 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Split the README into a landing page and topic pages

1 participant