- a default margin (about
1em top/bottom); left unreset, it silently added extra space below
the last row, inside the colophon's own padding box, on top of the
card's own now-zeroed padding-bottom (Captain Review 2, order 4) --
found only by direct measurement, not by inspecting this rule. */
margin: 0;
display: grid;
grid-template-columns: minmax(0, max-content) minmax(0, 1fr);
column-gap: 1.25rem;
row-gap: 0.5rem;
}
.colophon dt {
color: var(--ink-light);
font-weight: 600;
}
.colophon dd {
margin: 0;
white-space: pre-wrap;
overflow-wrap: anywhere;
}
.colophon p.editorial {
margin: 0.75rem 0 0;
text-indent: 0;
white-space: pre-wrap;
color: var(--ink-mid);
font-size: 0.92em;
}
@media (max-width: 560px) {
.colophon dl {
display: block;
}
.colophon dt {
margin-top: 0.7rem;
}
.colophon dt:first-child {
margin-top: 0;
}
}
/* Captain Review 2, order 3 ("add the section line divider ... between
all major sections"), amended: "spacing, line divider, then spacing --
exactly as the Prototype's .document-section does it: the preceding
section's bottom padding (clamp(3.5rem, 8vw, 7rem)), then the 1px
--rule line, then the same top padding before the next section's
heading." The Prototype achieves the "before" half by giving every
`.document-section`-classed element ITS OWN bottom padding of that
same clamp() (`analects.css` ~524: `padding: clamp(...) var(
--source-rail) clamp(...) 0`) -- appendix-4 gets its divider border
only because it separately also carries the `.appendix` class: the
line itself never supplies the spacing.
This document's 15 divider elements sit after very different kinds of
preceding siblings (a boxed colophon card, the Contents table, a plain
front-matter div, or the last of a Book's own numbered-chapter divs),
so rather than hunt down and pad the trailing edge of each of those
different element types individually, the identical rendered gap is
produced by giving the DIVIDER element itself `margin-top:
clamp(3.5rem, 8vw, 7rem)` instead: none of this document's "before a
divider" elements ever declare a margin-bottom larger than the
clamp's own 3.5rem floor (colophon: 0; table.contents: 2rem; a plain
div.chapter: 0), so ordinary adjacent-sibling margin collapsing always
resolves to the larger value -- the clamp -- giving byte-for-byte the
same measured gap the Prototype's own padding-based mechanism
produces, without touching any element this order did not name.
`border-top` and the "before" margin are shared here; the "after"
padding is added per host element below, since `
- ` text, via `DIVIDER_GAP_JS`'s
TreeWalker), not to the card's border, so that 1.5rem lands directly
in the measured gap (confirmed: a live re-run showed the "hr(contents)"
boundary alone going out of tolerance by ~24px, exactly 1.5rem, after
the padding restore). Widened by that same 1.5rem here, the same
pattern as `div.chapter:has(> aside.note-box:last-child) +
.section-divider` above, so the measured "last glyph -> line" gap
still matched the Captain's own order-4 calibration.
Captain Review 2, order 14/15: both sides of this specific boundary
changed font -- the colophon's own font-size (0.86rem -> 0.9rem, order
14) shifts the release-date glyph the "above" side measures to, and
`main > h3`'s font-size/line-height (order 15, now `div.chapter h3`'s
own values) shifts the Contents heading glyph the "below" side (this
same `hr.section-divider`'s flat `padding-top`) measures to. The old
flat `0.734px` residual is stale for both reasons at once, so it was
thrown out and re-measured from scratch (Playwright, both sides
Range-measured, at 1280 and 420) rather than patched incrementally;
unlike order 11's own correction above, the new residual is NOT
width-independent -- fit as `Xpx + Yvw` from the two measured points,
the same technique `.section-divider`'s own base correction (below)
already uses. */
.colophon + .section-divider {
margin-top: calc(clamp(3.5rem, 8vw, 7rem) - 1.5rem - (2.2613px + 0.1163vw));
}
hr.section-divider {
margin-inline: auto;
margin-bottom: 0;
border: none;
border-top: 1px solid var(--rule);
padding-top: clamp(3.5rem, 8vw, 7rem);
}
/* Captain Review 2, order 8 ("add the section space/line divider like in
Analects" -- the About box selected): this hr's own "gap below" is
measured to another ELEMENT's border edge (the box's own top), not a
glyph the way every other divider's "below" is -- so, unlike those,
it is NOT naturally offset by font leading, but it DOES pick up this
hr's own 1px border-top (box-top = hr-top + border-width(1px) +
padding-top, so box-top minus hr-top over-counts padding-top by
about that 1px). Corrected here, found only by direct measurement
(1280: 103.38px below vs 101.44px above without this fix) -- the
1.15px figure (not a bare 1px) was solved from measurements at
three widths (1280/900/420) so all three land within 1px, not just
the two the Captain's own order names. Scoped with `#reference` so
it only affects this specific hr, not the Contents-section one
(whose own "below" measurement is to a heading's
glyph, already correct via the shared rule above). */
#reference hr.section-divider {
padding-top: calc(clamp(3.5rem, 8vw, 7rem) - 1.15px);
}
/* ---- "Contents" heading + the Contents table ---------------------------- */
/* Captain Review 2, order 1, "Fix the alignments of the listings": both
rules below used to fight `main > *` (the shared reading-measure rule
above) on the properties that matter for centring, even though neither
intended to.
- `main > h3` used to write `margin: 2rem 0 1rem` -- a 3-value
shorthand (top | left-right | bottom) that zeroes left/right
margin explicitly, at HIGHER specificity than `main > *`'s
`margin-inline: auto`, so the heading stayed flush against
's own left edge instead of centring on the 704px reading column div.chapter/#colophon share. Fixed: `auto` in the left-right slot keeps the heading's own vertical margins while leaving horizontal centring to `main > *`. - `table.contents` used to declare `width: 100%`, at higher specificity than `main > *`'s `width: min(100% - 2rem, 44rem)`, so the table filled the whole of (1024-1084px at 1280px wide, panel state dependent) rather than the 704px column -- "auto" margins on a 100%-wide box have no space left to centre into, which is why the table's own `margin: 0 auto 2rem` looked right but did nothing. Fixed: no `width` declared here at all, so `main > *`'s constrained width is the only one that applies, and this rule's own auto margins then actually centre it. */ /* Captain Review 2, order 4 ("all line divider spacing areas should be equal on both sides"): this heading's own top margin used to add on top of hr.section-divider's padding-top, making the gap BELOW the Contents-section line larger than the gap ABOVE it. Zeroed here (top only -- the horizontal `auto` centring and the bottom margin are unchanged); the divider's own padding-top alone now supplies the full, symmetric gap. See the `.section-divider`/`div.chapter.section-divider` comment further down for the matching fix on the "above" side. Captain Review 2, order 15 ("update the style of this header like the other Titles"): color/font-size/font-weight/line-height/margin-bottom now match `div.chapter h3` (below) exactly -- the same treatment every other section title in the document already has (INTRODUCTION, the Book headings, REFERENCE, ...). `margin: 0 auto ...` is untouched on the left-right ("auto") side -- those are Review 2 order 1's own fix, load-bearing for this heading's horizontal centring on the reading column, which this order does not touch. `font-family`/`text-align` already matched `div.chapter h3` before this order and stay as they were. No `letter-spacing`/`text-transform` is added -- `div.chapter h3` declares neither, so "normal tracking, no transform" is already the match. */ main > h3 { margin: 0 auto 1.25rem; color: var(--ink); font-family: var(--display); font-size: clamp(1.5rem, 3.4vw, 2.1rem); font-weight: 400; line-height: 1.25; text-align: center; } /* Captain Review 2, order 4: bottom margin zeroed -- was 2rem, which used to survive only because it happened to collapse with pref01's own (larger) margin-top; zeroing it here puts the ENTIRE gap above that line into pref01's margin-top explicitly, rather than relying on collapse behaviour that would silently break if either value ever changed independently. */ table.contents { margin: 0 auto; border-collapse: collapse; font-size: 0.92rem; } table.contents td { padding: 0.2rem 0.6rem; text-align: left; vertical-align: top; } table.contents a { color: var(--rust); text-decoration: none; } table.contents a:hover { text-decoration: underline; } table.contents tr.editorial td { padding-top: 1.5em; } /* ---- chapters (front matter / Book dividers / numbered chapters all share class "chapter"; REFERENCE additionally carries "editorial") ----- */ /* Captain's correction (relayed via the coordinator, following Review 2 order 3): chapters are "left as is" -- the Basic HTML had no rule between chapters, and the Prototype's own `.chapter`/`.book-divider` give no border either (confirmed: no such rule anywhere in analects.css). The old `border-bottom` this rule carried (this build's own PIPE 3 authoring, never vendored from anywhere) was removed outright, along with the `:last-of-type` exception that existed only to zero it on the very last chapter. Captain Review 2, order 5 ("these Chapters in Clausewitz are large blocks of text and paragraphs, and should get the space/line dividers between the Chapters"): extends order 3's divider from the 14 major-section blocks to EVERY one of the 142 chapter-like blocks (all 128 numbered chapters too) -- the generator now tags every div.chapter (and REFERENCE) with `section-divider`, so this base rule and that modifier collapse into one, applying uniformly: a top border, and the Prototype's own `.document-section` top-padding rhythm on every side that needs it, replacing the smaller flat `2.25rem` this build started with. A Book-division div (heading only, no body text) now sits between two divider lines like a part-title page -- the Captain's own stated, intended result of order 5, kept as-is. Captain Review 2, order 4 ("all line divider spacing areas should be equal on both sides"): the gap ABOVE a line must equal the gap BELOW it. Below is simple -- this rule's own `padding-top`, since a chapter's own heading margin-top is separately zeroed (see `div.chapter h3` below). Above used to be the SUM of the preceding block's own bottom padding (which never collapses with anything, unlike margin) plus this rule's `margin-top` -- always bigger than `padding-top` alone. Fixed by removing `padding-bottom` from this rule entirely (0 top-of-column padding contribution from what PRECEDES a line) and zeroing the actual last child's own trailing margin/padding too (see the `:last-child` rule below) -- every chapter's own "end of section" cost is 0, so the ENTIRE measured gap above any line is this rule's `margin-top` alone, the same `clamp(3.5rem, 8vw, 7rem)` magnitude as `padding-top` below. `border-top` and `margin-top` are shared with `hr.section-divider` via the `.section-divider` rule above; `padding-top` differs per host element since `
` and `div.chapter` start from different bases. */ div.chapter { padding-top: clamp(3.5rem, 8vw, 7rem); padding-bottom: 0; } /* The actual last child of ANY div.chapter -- ordinarily a `` (which has no padding to begin with), but a `
` wrapped in `
` and `div.chapter` start from different base rules. `--rule` is already a dark-mode-aware token (flips with the theme), so no separate dark-mode override is needed here. */ /* Captain Review 2, order 4 (continued): even with every trailing padding/margin zeroed (above), the Range-measured gap above a line still did not exactly equal the gap below it, because the two sides measure through DIFFERENT fonts/line-heights (this build's body text for whatever precedes a line vs. div.chapter h3's own display font for what follows one) -- a browser's own glyph-to-line-box "leading" is not identical for the two, so `margin-top == padding-top` in the CSS is not the same as "measured gap above == measured gap below." This was measured directly (Playwright, the same Range-based method the Captain's own check uses) for every DISTINCT kind of element that can be the "last thing before a line" in this document (found by inspecting all 143 boundaries' actual last child): a plain paragraph (126 of 143, `p`/`p.center`/`p.right` alike -- same font, so one correction covers all three), a footnote box (5, smaller font-size), a Book-division heading (8, the one case where a line follows another line directly -- see order 5's own "Book division sits between two lines" note), the Contents table (1, pref01's own boundary) and the colophon card (1, the hr boundary). Each gets its own small, measured correction, subtracted from the shared clamp() via `calc()`, so the final measured gap matches within 1px at both 1280 and 420 -- the two widths the Captain's check runs at; see the build report for the full 143-row table this was calibrated against. */ .section-divider { margin-top: calc(clamp(3.5rem, 8vw, 7rem) - (2.365px + 0.0988vw)); border-top: 1px solid var(--rule); } /* Book-division heading immediately followed by its Book's own first chapter (8 cases): this is a line directly after another line (no text in between -- the Book-division div's only child is its own h3), so the "leading" mismatch runs the other way; the correction is correspondingly a small ADDITION to margin-top rather than a subtraction (a negative correction value here). */ div.chapter.section-divider:has(> h3:only-child) + .section-divider { margin-top: calc(clamp(3.5rem, 8vw, 7rem) - (-1.4845px + 0.1153vw)); } /* A chapter whose very last paragraph carries a footnote (5 cases): the footnote's own smaller font-size (0.86em) leaves a different residual than a plain body paragraph. Captain Review 2, order 11 ("review all the boxes... correct similar errors"): `main > div.chapter > :last-child` (below) used to zero this note-box's own `padding-bottom` along with its `margin-bottom` -- the same reader-visible-padding-as-outer-spacing mistake the colophon had, confirmed by measurement (12px top, 0px bottom). Neither Analects nor Sunzi ever zero a note-box's own padding this way (both only zero its MARGIN at a section end -- analects.css ~640, sunzi-war.css ~1189). Fixed the same way `#reference > aside.source-note.editorial` (below) already restores the About box's own padding against this same generic rule: a more specific override, `main > div.chapter > aside.note-box:last-child { padding-bottom: 0.75rem }`. UNLIKE that box, this one still has a NEXT divider line depending on the old, zero-padding measurement, so this rule's own correction is widened by that same 0.75rem to keep the "last content -> line" gap exactly where the Captain's own order 4 already measured and approved it. */ div.chapter:has(> aside.note-box:last-child) + .section-divider { margin-top: calc(clamp(3.5rem, 8vw, 7rem) - 0.75rem - (1.323px + 0.1671vw)); } /* The Contents table, immediately before pref01's own line (1 case): table-row text leaves a larger residual than body prose. */ table.contents + .section-divider { margin-top: calc(clamp(3.5rem, 8vw, 7rem) - (4.952px + 0.1163vw)); } /* The colophon, immediately before the Contents-section hr (1 case). Captain Review 2, order 11: restoring the colophon's own padding- bottom (1.5rem, above) grows the card's own total height by that same 1.5rem, pushing this line 1.5rem further down the page -- and `verify_finished.py`'s own gap check measures "above" to the colophon's last GLYPH (the release-date `