, so there is nothing to click and nothing for a crawler to follow.
⛔ Quieted with the dashed --alt treatment the greyed series shelf uses, NOT with
opacity: opacity would blend the copy toward the card and drop it under 4.5:1, and this
card's whole job is to say clearly that the world is coming. --muted on --alt = 4.92:1. */
.wcard.off{background:var(--alt);border-style:dashed;cursor:default}
.wcard.off:hover{border-color:var(--border);transform:none}
/* four worlds, four peers: 2x2, not a 3-across row with one orphan underneath.
Must stay ABOVE the 760px rule below, which collapses every .wgrid to one column. */
.wchoose{grid-template-columns:repeat(2,1fr)}
/* --- portraits: an enhancement layered on the card, never a slot (28 Jul 2026) -------
⛔ ONE ENTITY IN SEVENTY-ONE HAS ART. So the design problem is not "how does the picture
look" — it is "how do the seventy cards WITHOUT one look standing beside it". Two rules
follow, and they are the whole of this block:
1. FLOAT, never grid. A float occupies space only when the element exists, so a card
with no portrait is byte-for-byte and pixel-for-pixel the card the site already
renders. There is no reserved box, no placeholder, no grey hole to explain.
2. SMALL AND ROUND. At 56px it reads as an avatar decorating a text card, not as the
card's hero image. A large portrait would make the row it sits in look like a grid
of missing pictures with one filled; an avatar looks like a card that happens to
have a face on it — which is exactly the truth.
The text wraps around it, so nothing shifts and no min-height is needed. */
.wcard .wthumb{float:right;width:56px;height:56px;border-radius:50%;object-fit:cover;
/* the master is a 2:3 headshot with the face high in frame; a centred square crop would
cut the chin. 22% from the top puts the eyes just above the circle's centre. */
object-position:center 22%;margin:2px 0 6px 14px;
border:1px solid var(--border);box-shadow:0 2px 8px rgba(30,22,10,.14)}
/* the entity's own page: the portrait sits ABOVE the entry, not floated beside it.
⛔ MEASURED, not preferred. Floated right at 200px it took 226px out of the .prose column's
570px reading measure and left the text at 32–38 characters a line — visibly ragged, and well
under the ~45ch floor for comfortable reading. The picture is not worth breaking the one thing
the page is for. As a block above the prose the entry keeps its full 58ch measure, the portrait
still reads at a proper size, and it needs no responsive exception because it never competes
with the text for width. An entity with no portrait gets the page it has today, unchanged. */
.wportrait{display:block;width:190px;aspect-ratio:2/3;object-fit:cover;object-position:center 22%;
border-radius:4px;margin:6px 0 24px;box-shadow:0 6px 22px rgba(30,22,10,.16)}
/* --- family sections on the People page (29 Jul 2026) --------------------------------
⛔ THE BOX IS --alt, NOT A SECOND BORDERED CARD. The cards inside are --card (#fcfaf4) on a
--bg (#f5efe3) page; a bordered white box around bordered white cards reads as a table, and
the page stops looking like a shelf. Dropping the group to --alt (#efe7d6) instead puts the
cards a step LIGHTER than their container, so the family reads as a tray the cards sit in
and the eye still lands on the people, not on the joinery.
The heading is the small-caps meta treatment the site already uses for shelf labels, so a
family name never competes with the character names it is introducing. --muted on --alt is
the pairing measured at 4.64:1 in rushlight.css — the one contrast this block relies on. */
.wfam{background:var(--alt);border:1px solid var(--border);border-radius:8px;
padding:20px 22px 22px;margin-bottom:20px}
.wfam:last-child{margin-bottom:0}
/* ⛔ MUST BE `.wfam .wfam-h`, NOT `.wfam-h`. `.sec h2` (0,1,1) is a page-section title — serif,
30px, centred, 34px below — and it out-specifies a bare class (0,1,0). On the first build the
family label inherited all three and rendered as a second page heading competing with