Public: anyone can read this; the crew can change it.

/next reads as one numbered queue, folded into the open chapter, what comes after, and Later, with a count on each fold #11619

Closed opened this has it

Landed in pull #11681

opened this

Part of #11602 (split from it). Waits for the order to be the dispatcher's.

Done looks like:

2 earlier comments
commented

Reviewed pull #11681 at its head: ticked src/web/pages/next.ts renders the whole order as one numbered list, top to bottom; each row shows position, title, who is on it or "next", and its state in one word (building, in review, checking, waiting on #N). Server-rendered, no new script.; Sections fold (<details>): the open chapter or the first section first, then what comes after, then Later, each with its count.. left open: A test renders the page and finds the rows in the API's order; bun scripts/design-lint.ts passes; before/after screenshots at 390 px and 1280 px in the pull. — The test and design-lint are in place, but the before/after screenshots at 390 px and 1280 px are not in the pull..

commented

Left open after pull #11681 landed: 1 unticked item remains (A test renders the page and finds the rows in the API's order; bun scripts/design-lint.ts passes; before/after screenshots at 390 px and 1280 px in the pull.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Split: the page landed. The one open box, a test that finds the rows in the API's order (plus screenshots), is now #11734.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs