docs: document the shipped ordered column flow - #86
Merged
thejustinwalsh merged 1 commit intoAug 20, 2026
Conversation
`columns: { count, gap }` is public API on the paragraph content box
(`text-properties.ts:50`) and ships in the canary, but it appeared zero
times in `README.md` and zero times in `docs/packages/glyph.md`. A tester
had no way to discover it.
Worse, the docs denied it. `editorial-flow-layout.md` stated the engine
"does not represent columns", and `roadmap.md` marked 11.18 not started
even though the ordered-column slice merged in 7feda80 alongside the
solid-decoration slice already noted in that row.
The denial is now scoped to what is genuinely absent: column balancing,
holes, floats, contours, and multiple usable intervals on a baseline.
Ordered flow inside the content box is described where readers meet the
content box -- the README example section and the retained frame
transaction in the package concept -- including the two constraints that
bite in practice: columns fill in order without balancing, so the last
column may run short, and an exact `width` is required because the column
advance derives from it.
Roadmap 11.18 moves to in progress and records the landed slice inline,
matching how the same row already records decorations. It is not complete:
balancing and the drop-cap exclusion surface remain.
size-limit report 📦
|
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
1 participant
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.
columns: { count, gap }is public API on the paragraph content box(
text-properties.ts:50) and ships in the canary, but it appeared zerotimes in
README.mdand zero times indocs/packages/glyph.md. A testerhad no way to discover it.
Worse, the docs denied it.
editorial-flow-layout.mdstated the engine"does not represent columns", and
roadmap.mdmarked 11.18 not startedeven though the ordered-column slice merged in 7feda80 alongside the
solid-decoration slice already noted in that row.
The denial is now scoped to what is genuinely absent: column balancing,
holes, floats, contours, and multiple usable intervals on a baseline.
Ordered flow inside the content box is described where readers meet the
content box -- the README example section and the retained frame
transaction in the package concept -- including the two constraints that
bite in practice: columns fill in order without balancing, so the last
column may run short, and an exact
widthis required because the columnadvance derives from it.
Roadmap 11.18 moves to in progress and records the landed slice inline,
matching how the same row already records decorations. It is not complete:
balancing and the drop-cap exclusion surface remain.
Stack created with GitHub Stacks CLI • Give Feedback 💬