/* =====================================================================
 * Forum Borealis — one heading scale, applied consistently, 2026-11-21
 *
 * Al 2026-11-21: "Everything is huge... can things be made smaller? Can
 * we also try to make symmetry, such as justify text."
 * Ricky, replying: "I will justify text and improve symmetry." Size is a
 * SEPARATE promise he deliberately gated — "this largely depends on your
 * screen size... if you could send me screenshots." So this file does not
 * shrink the site. It removes the places where the same heading is a
 * different size depending on where it sits, which is the symmetry half,
 * and the side effect is that the outliers come down.
 *
 * MEASURED before writing anything, at 1440px, from the live markup.
 * Headings on four pages ran to ELEVEN distinct sizes with no scale:
 *
 *   12.0  .fb-comments-head              "3 comments"
 *   12.48 .fb-about-h                    "The show"
 *   16.32 .fb-section-head h2            "Latest from the discussion"
 *   20.8  .fb-update-body h2             "The whole archive is here"
 *   21.6  .fb-signup h2                  "Get new episodes by email"
 *   21.6  .fb-members h2                 "Subscribers hear everything"
 *   25.6  .fb-update-title               "Welcome to the new Forum Borealis!"
 *   29.6  .fb-hero-title                 "Game of Initiates — …"
 *   30.0  h1.entry-title  (post)         "Welcome to the new Forum Borealis!"
 *   32.0  .post-content h2 (post page)   "The whole archive is here"   <-- same heading as 20.8
 *   32.0  .fb-follow h2                  "Follow us"                   <-- beside a 21.6 one
 *
 * Two of those are the complaint in miniature:
 *
 *  1. "The whole archive is here" is ONE heading in ONE post. On the front
 *     page, where the post is published in full, it renders at 20.8px. On
 *     the post's own page it renders at 32px — 54% larger. A reader who
 *     clicks through from the front page watches the type jump.
 *  2. "Follow us" (32px) sits directly beside "Get new episodes by email"
 *     (21.6px), same panel treatment, same <h2>, 28px apart. That is the
 *     asymmetry Al can see without knowing why.
 *
 * ROOT CAUSE, and why it is not a list of unrelated mistakes. Avada's
 * dynamic CSS loads AFTER the child theme and carries
 * `.post-content h2, …, h2 { font-size: var(--h2_typography-font-size) }`
 * at specificity 0,1,1. Every heading we wrote a two-class rule for got
 * our size; every heading we didn't fell through to Avada's default of
 * h1 44 / h2 32 / h3 22 against 16px body text. So the scale is not
 * "ours" with a few errors — it is ours wherever we remembered, and
 * Avada's wherever we didn't, interleaved.
 *
 * WHAT THIS FILE PICKS. Where the two disagree, our deliberate value wins,
 * because that is the one somebody chose. Nothing is invented and nothing
 * already-deliberate is changed:
 *
 *   content h2   32px -> 1.3rem  (20.8px)  = the value already live on the
 *                                            front page for the same markup
 *   content h3   22px -> 1.12rem (17.9px)  = the value already in 28-home-hero
 *   content h4   18px -> 1rem    (16px)
 *   panel h2     32px -> 1.35rem (21.6px)  = the value already on .fb-signup
 *
 * The small end (12.48 and 16.32) is deliberately LEFT ALONE. Raising it
 * would make the page bigger, which is the wrong direction this week, and
 * those two are doing eyebrow-label work rather than heading work. Worth
 * revisiting with Al once the size question is settled.
 *
 * IF AL'S SCREENSHOTS SAY THE WHOLE SITE IS STILL TOO BIG, the lever is
 * four values in Avada's own typography options (h1 44 / h2 32 / h3 22 /
 * body 16), not this file. Changing them there moves every heading at
 * once and keeps this scale's proportions. ⚠ Avada caches dynamic CSS in
 * OPTIONS — the change does nothing until those are deleted, and emptying
 * uploads/fusion-styles/ alone regenerates the same stale file.
 *
 * SPECIFICITY. Avada's rule is 0,1,1, so a bare `.post-content h2` (0,1,1)
 * ties it and loses on source order, which is exactly how we got here.
 * Everything below leads with `body` to reach 0,1,2 and win on
 * specificity rather than on load order, so none of it needs !important
 * and none of it breaks if the enqueue order ever changes.
 * ===================================================================== */

/* ---- headings inside running content -------------------------------- */

body .post-content h2,
body .fb-update-body h2 {
	font-size: 1.3rem;
	line-height: 1.3;
}
body .post-content h3,
body .fb-update-body h3 {
	font-size: 1.12rem;
	line-height: 1.35;
}
body .post-content h4,
body .fb-update-body h4 {
	font-size: 1rem;
	line-height: 1.4;
}

/* The post's own title, and the title it carries when the front page
   publishes it in full, are a different role from a heading inside the
   body -- they stay larger, and stay as they already were. Restated here
   only so the rules above cannot reach them. */
body .post-content .fb-update-title {
	font-size: clamp(1.2rem, 2vw, 1.6rem);
	line-height: 1.22;
}

/* ---- the two widget panels, side by side ---------------------------- */

/* .fb-signup already had a winning rule and .fb-follow did not, which is
   the whole of the 21.6-vs-32 split. Both are named here so neither can
   drift again, and .fb-members joins them because it is the same panel
   treatment one section above. */
body .fb-signup h2,
body .fb-follow h2,
body .fb-members h2 {
	font-size: 1.35rem;
	line-height: 1.25;
}

/* ---- the Follow panel's dead space ---------------------------------- */

/* Measured at 1440px: both panels are 418.2px tall because .fb-widget-row
   is `align-items: stretch`, but Follow's content stopped at 159.6px --
   258.6px of empty panel, against Newsletter's 391.2px of content. It
   reads as an unfinished box beside a full one.

   The obvious fixes both cost something: `align-items: start` leaves the
   two panels different heights, and centring Follow's whole content block
   pushes its heading out of line with the Newsletter heading beside it.
   Neither is acceptable when the complaint is specifically about symmetry.

   So the heading and lede stay pinned to the top, in line with the panel
   beside them, and only the icon row takes the slack -- it grows into
   whatever is left and centres its icons in it. Headings align, panels
   match, and the empty space is gone. */
.fb-follow {
	display: flex;
	flex-direction: column;
}
.fb-follow > .fusion-social-networks,
.fb-follow > .fb-social-links,
.fb-follow > div:last-child {
	flex: 1 1 auto;
	display: flex;
	align-items: center;
	flex-wrap: wrap;
}

/* ---- page titles: LEFT ALONE, deliberately --------------------------
 * /about/'s title measures 41.6px, the largest text on the site, against
 * 29.6px for the home hero title and 30px for a post title. It looks like
 * the same outlier as the ones above and it is not: 21-about.css sets
 * `.fb-about-title { font-size: 2.6rem !important }`, so somebody chose
 * it, as a display wordmark rather than as a page heading. The rule in
 * this file is that a deliberate value stands and only Avada's leaked
 * defaults get overridden, so it stands. It is a good candidate for the
 * size conversation once Al's screenshots arrive -- flagged there, not
 * pre-empted here. (It already steps down to 2rem under 900px.)
 * ------------------------------------------------------------------- */
