/* articles family - /news/:slug/ /guides/:slug/ /careers/:slug/ /services/:slug/
 * and the four legal documents (/privacy/ /terms/ /cookies/ /accessibility/).
 *
 * Only what site.css does not already carry. Every rule below closes a gap
 * between the approved preview's markup and this build's, and there are
 * exactly three kinds:
 *
 *   1. the preview writes an inline style attribute where a real page wants a
 *      class - .asidenote, .asidenext;
 *   2. the preview draws a CONTROL (a <button> with data-view) where a real
 *      page draws a LINK, and site.css styles only the control - .artnav a,
 *      .asidebox a.btn, .ibread a, and the .backlink. Every one of these is
 *      the same failure: site.css names some of the font's properties on the
 *      selector and leaves the rest to the UA's button defaults, which an <a>
 *      does not get - it inherits the body's instead. Three have been found
 *      so far (line-height, text-align, font-weight), so when a new one of
 *      these appears, check the whole computed font, not the one property
 *      that looks wrong;
 *   3. site.css's global `a{color:var(--gold)}` therefore paints gold what the
 *      preview painted with the text around it - the breadcrumb's home and
 *      last segment, and the aside's list.
 *
 * Plus one box the preview fills with placeholder art and this build fills
 * with a photograph, or - when there is no photograph yet - with the state
 * that says so (.arthero img, .arthero--none), and the one heading whose
 * spacing the preview writes differently from the shared kickhead macro
 * (.steplist).
 */

/* ---- 1. the preview's inline style attributes, as classes ---------------- */

/* the aside's explanatory line on a role page */
.asidebox .asidenote {
  font-size: 14px;
  line-height: 1.7;
  font-weight: 300;
  color: var(--muted);
}

/* the aside's second heading, above the other-roles list */
.asidebox h4.asidenext {
  margin-top: 8px;
}

/* ---- 2. controls the preview draws as buttons, drawn here as links ------- */

/* "Back to all X". site.css's `.backlink` covers both element types, but it
   sets no line-height, and that is the whole difference: a <button> takes the
   UA's `line-height:normal` and sits flush at the top of its line box, while
   an <a> inherits the body's 1.6 and is baseline-aligned, which drops it 5px
   and adds 1.6px of height. Everything after it in the column inherits the
   shift - measured at +6 to +7px on every element below, which was the entire
   geometry difference on the service and role pages. Restoring the button's
   two values puts the anchor back on the preview's pixel. */
.backlink {
  line-height: normal;
  vertical-align: top;
  /* And the UA's font-weight, for exactly the same reason. site.css sets
     `.backlink`'s family, size, letter-spacing and case but NOT its weight, so
     the preview's <button> keeps the UA's 400 while an <a> inherits the body's
     300. It shows up as width, not position: measured per character with a
     Range on /services/ at 1440, the arrow (12.77px) and both spaces (5.08px)
     match to the hundredth - they come from the fallback face - and every
     LETTER is narrower, "A" 8.77 against 9.03, "i" 4.19 against 4.48, so the
     whole label came out 2.28px short (2.21px on /careers/). Neither the flex
     split nor the separator character was the cause: both markups measured
     104.94px against the preview's 107.22 until the weight was restored. */
  font-weight: 400;
  /* site.css sets `gap:9px` on .backlink, which in the preview separates
     NOTHING: the button's content is one text run ("<- All news"), a single
     anonymous flex item, so the arrow and the label are held apart by the
     ordinary space between them. This build draws the arrow in its own
     aria-hidden span so a screen reader does not announce it, which makes two
     flex items - and the 9px gap suddenly applies on top of that space.
     Measured: 12px of clear pixels between arrow and label against the
     preview's 8px, and the label displaced ~4px right on every route that
     carries a backlink. The span carries a non-breaking space of its own
     instead (same character metrics as the preview's ordinary space, and not
     collapsible), so the separation is the preview's and the gap is not
     applied twice. */
  gap: 0;
}

/* The aside's call to action. On a policy page it goes to /contact/, so it is
   an anchor where the preview draws `<button data-view="contact">` - and
   site.css's `.btn` sets neither text-align nor line-height, leaving the
   button on the UA's `center`/`normal` and the anchor on the container's
   `text-align:left` and the body's 1.6. Measured on /privacy/ at 1440 light
   before this rule: the label sat hard against the left padding of the gold
   plate, the plate was 36.8px tall against the preview's 35.0, and the 1.8px
   carried up through .asidebox and, at 390 where the aside is the taller
   column, through .artwrap. The two UA values, restated for the anchor.
   Scoped to .asidebox on purpose: base.html's FAQ and office call-to-action
   are the same substitution in a SHARED file, and correcting them here would
   move this family's chrome away from every other family's. */
.asidebox a.btn {
  text-align: center;
  line-height: normal;
}

/* site.css styles `.artnav button`; these are the same declarations for the
   anchor this build uses, so the pair reads identically in both themes. */
.artnav a {
  display: inline-block;
  border: 1px solid var(--line);
  padding: 14px 20px;
  text-align: left;
  font-family: var(--sans);
  font-size: 14px;
  font-weight: 300;
  /* The button's UA line-height, for the same reason as .backlink above: an
     <a> would inherit the body's 1.6. It is invisible at 1440, where the
     label fits one line, and compounds once `max-width:46%` wraps it - the
     card grew 3.6px at 820 and 8.4px at 390, and since the two columns are
     grid siblings the whole asidebox came down with it. */
  line-height: normal;
  color: var(--text);
  max-width: 46%;
  transition: all .2s ease;
}

.artnav a:hover {
  border-color: var(--gold);
  color: var(--gold);
}

.artnav a:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* ---- 3. links the preview drew as plain text ---------------------------- */

/* "Home" in the breadcrumb is a <span> in the preview and takes the crumb's
   own muted colour; it is a real link here, so the global anchor rule would
   paint it gold. It still turns gold on hover, from site.css. */
.crumb .cr-home {
  color: var(--muted);
}

/* The preview marks the PARENT segment of a detail page's breadcrumb, not the
   last one: "Home > Services > Property sales & purchases" has "Services" in
   gold. The shared pagehead macro marks the last segment instead, and the
   parent is already gold because it is a link - so the segment to quiet down
   is the <b> that follows a linked segment. A document page, whose only
   segment is its own title and carries no link, keeps its gold.

   `.crumb b` also carries `font-weight:400` (site.css), and the mark is on the
   wrong segment for weight exactly as it is for colour: the preview's parent
   is a <b> at 400 and its last segment is plain text at the crumb's 300, while
   this build has an <a> at 300 and a <b> at 400. Both are restated below.
   `.pagehead .wrap` is centred, so the two errors did not cancel - they made
   the whole crumb 3.30px wide of the preview's on /services/ and started it
   1.66px left of it (0.95px on /careers/, 0.28px on /news/, and 0.00px on a
   policy page, which has no parent segment and was therefore right all
   along). Measured per segment with a Range: "Services" 55.64px against the
   preview's 57.41px. */
.crumb a:not(.cr-home) ~ b {
  color: var(--muted);
  font-weight: 300;
}

.crumb a:not(.cr-home) {
  font-weight: 400;
}

/* the aside's list items carry the body colour and turn gold on hover
   (site.css, `.asidebox ul li`); the link inside follows the item */
.asidebox ul li a {
  color: inherit;
}

/* the legal pages' in-body breadcrumb: site.css styles `.ibread button`, and
   like `.backlink` it sets the family, the size, the letter-spacing and the
   case but not the weight - so the preview's <button> keeps the UA's 400 and
   this anchor would inherit the body's 300. Same substitution, same restated
   value; only the linked "Home" segment needs it, because the current page's
   segment is a <span> on both sides. */
.ibread a {
  font-weight: 400;
  /* and the UA's line-height, the third property of the same shorthand: ours
     computed to 17.6px against the button's `normal` (16px). It does not move
     the row - `.ibread` is a flex line whose <span> separators are 17.6px on
     both sides, and `align-items:center` put the shorter button back on the
     same glyph centre to within 0.01px - so this is restated for the case
     where the crumb wraps, and because a computed font that differs in one
     property is how the previous two were missed. */
  line-height: normal;
}

.ibread a:hover {
  color: var(--gold-hi);
}

/* ---- the article cover ------------------------------------------------- */

/* site.css absolutely positions `.arthero svg` - the preview's placeholder
   art. A photograph fills the same box. */
.arthero img {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
}

/* A news post with no photograph yet. The box is NOT dropped: it carries the
   category plate, and the reference's column is measured from its height -
   358.0px at 1440, which is what the whole article moved by while the box was
   conditional. site.css already gives `.arthero` the logo ground, the height
   clamp and `position:relative`; this is the same no-photograph state the
   listing family draws in `.gal--none`, in this box's proportions. */
.arthero--none {
  display: flex;
  align-items: center;
  justify-content: center;
}

.artnone {
  position: relative;
  z-index: 2;
  font-size: 13px;
  letter-spacing: .1em;
  text-transform: uppercase;
  color: var(--muted);
  font-weight: 300;
  text-align: center;
  padding: 0 20px;
}

/* ---- the "How it works" heading --------------------------------------- */

/* Every other kicker heading in this family sits 4px above what follows it,
   which is what macros/shared.html's kickhead writes. The preview gives this
   one 18px; the margins collapse, so the larger of the two wins. */
.steplist {
  margin-top: 18px;
}
