/* The footer every page on balthazor.net shares.
 *
 * One file rather than four copies: the landing page, /syncsessions/support, /syncsessions/siri
 * and /syncsessions/User-Guide had drifted into three different footers and one page with none —
 * different type sizes, different content, and support carrying two date lines that disagreed.
 *
 * ⚠️ It lives at the SITE root, not under /syncsessions/, even though three of the four pages that
 * use it are published from the syncsessions-web repo. This is site furniture and the landing page
 * needs it too, so it must not depend on an app directory that the plan is eventually to move to
 * its own subdomain.
 *
 * ⚠️ Colors are inherited, never declared. Each page brings its own palette under its own names —
 * site.css says --text-muted, the landing page says --muted, the User Guide says --dim — so every
 * value here is a fallback chain ending in a literal. A footer that set its own colors would be
 * the one band of the wrong grey on three pages out of four, and would break the User Guide's
 * light mode outright.
 */

.site-footer {
  margin-top: 3.5rem;
  padding-top: 1.25rem;
  border-top: 1px solid var(--border, var(--line, var(--rule, #2a2a2c)));
  color: var(--text-muted, var(--muted, var(--dim, #86868b)));
  font-size: 0.875rem;
  line-height: 1.55;
}

.site-footer p {
  margin: 0 0 0.75rem;
}

.site-footer a {
  color: var(--link, #2997ff);
}

/* Page navigation or contact detail, where a page carries it. Sits above the notices so the
   legal text stays the last thing, which is the order every one of these pages already used. */
.site-footer__links {
  margin-bottom: 1.25rem;
}

/* The Apple notices and the copyright. Slightly quieter than the links above: it is required
   text rather than something a reader is meant to act on. */
.site-footer__legal p {
  font-size: 0.8125rem;
  opacity: 0.85;
}

/* ⚠️ Keep this class name. TWO workflows rewrite the date by matching on it — deploy.yml in
   syncsessions-web substitutes __PUBLISHED_DATE__ for the syncsessions pages, and
   published-date.yml in this repo sed-replaces the landing page's line in place. Renaming it
   silently strands whichever page the regex no longer matches, and neither workflow fails:
   deploy.yml only checks the pages it is told about, and the sed simply matches nothing.
   Centred and last, so it reads as the page's vintage rather than as part of the notices. */
.site-footer .page-published {
  margin: 1.25rem 0 0;
  text-align: center;
  font-size: 0.8125rem;
  opacity: 0.75;
}

/* ---------------------------------------------------------------------------
 * The page shell.
 *
 * Two widths, named, because there are two kinds of page here and previously there were three
 * unrelated numbers in three files — 820px, 42rem and 640px — with nothing to say which of them
 * was a decision. 820 was: support and siri carry tables and code. 640 was not; it was 42rem with
 * a different round number picked on a different day, and no reader will ever perceive the 32px
 * between them as intent.
 *
 * ⚠️ PADDING STAYS WITH THE PAGE. Only the measure is shared. The landing page opens on 12vh of
 * air, the User Guide on 3rem, support on none — those are compositional choices about how each
 * page begins, not a convention anyone is failing to follow.
 */

/* Prose: the landing page and the User Guide. ~75 characters at 17px, which is where a line
   stops being comfortable to read. */
.wrap {
  max-width: 42rem;
  margin: 0 auto;
}

/* Documents: support and siri. Wider because they hold tables and code blocks, which a prose
   measure squeezes — not because the prose on them wants the room.
   If this ever narrows to match, the tables should break out instead, the way the User Guide's
   screenshot rows already do. */
.wrap--document {
  max-width: 820px;
}