/*
 * Markdown Eye — web/landing.css
 *
 * The home page only. It shares nothing with the app: styles.css is 66 KB of
 * reader, editor and eight themes, and none of it is needed to read a page of
 * marketing copy. Keeping them apart means the first visit costs one small
 * stylesheet, and the app's bundle is still cold when someone only wanted to
 * know what this is.
 *
 * Hand-authored — tools/build-web.js does not generate or touch this file.
 *
 * Colours are the app's midnight theme, so the page and the thing it is
 * advertising look like the same product. No web fonts: the system UI stack
 * renders instantly and matches whatever device you are holding.
 */

:root {
  --bg: #0a0b0d;
  --bg-2: #0d0f13;
  --panel: #12141a;
  --panel-2: #171a21;
  --border: #23272f;
  --border-soft: #1b1e25;
  --text: #d7dce4;
  --text-strong: #f2f5f9;
  --muted: #99a2b0;
  --muted-2: #737c8b;
  --accent: #c6f432;
  --accent-strong: #d4fa52;
  --accent-ink: #10140a;
  --accent-soft: rgba(198, 244, 50, 0.11);
  --accent-line: rgba(198, 244, 50, 0.32);
  --cyan: #22d3ee;
  --violet: #a06bff;

  --radius: 14px;
  --radius-sm: 9px;
  --wrap: 1120px;
  --font-ui: system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue",
    Arial, sans-serif;
  --font-mono: ui-monospace, "Cascadia Code", "SF Mono", Menlo, Consolas,
    "Liberation Mono", monospace;
}

*,
*::before,
*::after {
  box-sizing: border-box;
}

html {
  -webkit-text-size-adjust: 100%;
  text-size-adjust: 100%;
  scroll-behavior: smooth;
}

body {
  margin: 0;
  background: var(--bg);
  color: var(--text);
  font-family: var(--font-ui);
  font-size: 16px;
  line-height: 1.65;
  -webkit-font-smoothing: antialiased;
  overflow-x: hidden;
}

/* Two soft washes of colour behind everything, fixed so they do not scroll
   away. Cheaper than an image and they cannot fail to load. */
body::before {
  content: "";
  position: fixed;
  inset: 0;
  z-index: -1;
  pointer-events: none;
  background: radial-gradient(
      70ch 60ch at 12% -8%,
      rgba(160, 107, 255, 0.14),
      transparent 70%
    ),
    radial-gradient(60ch 50ch at 92% 4%, rgba(34, 211, 238, 0.1), transparent 70%);
}

img,
svg {
  max-width: 100%;
}

a {
  color: var(--accent);
  text-decoration: none;
}
a:hover {
  color: var(--accent-strong);
  text-decoration: underline;
}

:focus-visible {
  outline: 2px solid var(--accent);
  outline-offset: 3px;
  border-radius: 4px;
}

/* Skip link: the nav is short, but the download list is the second thing on the
   page and a keyboard user should not have to walk the whole hero to reach it. */
.skip {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 100;
  padding: 10px 16px;
  background: var(--accent);
  color: var(--accent-ink);
  font-weight: 650;
  border-radius: 0 0 var(--radius-sm) 0;
}
.skip:focus {
  left: 0;
  text-decoration: none;
}

/* ==========================================================================
   Shared layout
   ========================================================================== */
.wrap {
  width: 100%;
  max-width: var(--wrap);
  margin: 0 auto;
  padding: 0 24px;
}
.section {
  padding: 84px 0;
}
.section + .section {
  border-top: 1px solid var(--border-soft);
}
.section-head {
  max-width: 62ch;
  margin: 0 0 44px;
}
.eyebrow {
  display: inline-block;
  margin: 0 0 14px;
  font-size: 12px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--accent);
}

h1,
h2,
h3 {
  color: var(--text-strong);
  letter-spacing: -0.025em;
  line-height: 1.15;
  margin: 0;
  font-weight: 750;
}
h2 {
  font-size: clamp(1.6rem, 1.15rem + 1.6vw, 2.3rem);
}
h3 {
  font-size: 1.05rem;
  letter-spacing: -0.01em;
  line-height: 1.35;
}
.lede {
  margin: 14px 0 0;
  font-size: 1.06rem;
  color: var(--muted);
}

/* ==========================================================================
   Buttons
   ========================================================================== */
.cta {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 10px;
  padding: 13px 22px;
  min-height: 48px;
  border: 1px solid var(--border);
  border-radius: 11px;
  background: var(--panel-2);
  color: var(--text-strong);
  font: inherit;
  font-weight: 600;
  text-decoration: none;
  cursor: pointer;
  transition: background 160ms ease, border-color 160ms ease, color 160ms ease,
    transform 160ms ease;
}
.cta:hover {
  border-color: var(--accent-line);
  color: var(--text-strong);
  text-decoration: none;
}
.cta:active {
  transform: translateY(1px);
}

.cta-primary {
  background: var(--accent);
  border-color: var(--accent);
  color: var(--accent-ink);
  font-weight: 700;
}
.cta-primary:hover {
  background: var(--accent-strong);
  border-color: var(--accent-strong);
  color: var(--accent-ink);
}
.cta-lg {
  padding: 16px 30px;
  min-height: 56px;
  font-size: 1.03rem;
}
.cta-block {
  width: 100%;
}
/* A button whose label needs a second line under it — the exact filename on a
   download, so nobody has to guess what lands in their Downloads folder. */
.cta-stack {
  flex-direction: column;
  gap: 2px;
  padding-top: 12px;
  padding-bottom: 12px;
}
.cta-sub {
  display: block;
  font-size: 11.5px;
  font-weight: 500;
  letter-spacing: 0.03em;
  opacity: 0.72;
}

/* ==========================================================================
   Top navigation
   ========================================================================== */
.nav {
  position: sticky;
  top: 0;
  z-index: 50;
  border-bottom: 1px solid var(--border-soft);
  background: rgba(10, 11, 13, 0.82);
  -webkit-backdrop-filter: saturate(1.3) blur(12px);
  backdrop-filter: saturate(1.3) blur(12px);
}
.nav-in {
  display: flex;
  align-items: center;
  gap: 20px;
  height: 64px;
}
.nav-brand {
  display: flex;
  align-items: center;
  gap: 10px;
  margin-right: auto;
  color: var(--text-strong);
  text-decoration: none;
}

.nav-brand:hover {
  text-decoration: none;
}
.nav-mark {
  display: block;
  flex: none;
  color: var(--text-strong);
}
.nav-word {
  font-size: 16px;
  font-weight: 750;
  letter-spacing: -0.015em;
}
.nav-word em {
  color: var(--accent);
  font-style: normal;
  margin-left: 3px;
}
.nav-links {
  display: flex;
  align-items: center;
  gap: 22px;
}
.nav-links a {
  color: var(--muted);
  font-size: 14.5px;
  font-weight: 550;
}
.nav-links a:hover {
  color: var(--text-strong);
  text-decoration: none;
}
.nav .cta {
  padding: 9px 17px;
  min-height: 40px;
  font-size: 14.5px;
}

/* ==========================================================================
   Hero
   ========================================================================== */
.hero {
  padding: 76px 0 40px;
  text-align: center;
}
.hero h1 {
  font-size: clamp(2.1rem, 1.15rem + 3.9vw, 3.9rem);
  max-width: 20ch;
  margin: 0 auto;
}
.hero h1 em {
  font-style: normal;
  background: linear-gradient(96deg, var(--accent) 12%, var(--cyan) 88%);
  -webkit-background-clip: text;
  background-clip: text;
  color: transparent;
}

.hero-lede {
  max-width: 58ch;
  margin: 20px auto 0;
  font-size: clamp(1rem, 0.94rem + 0.3vw, 1.16rem);
  color: var(--muted);
}
.hero-cta {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 14px;
  margin: 34px 0 0;
}
.hero-note {
  margin: 20px 0 0;
  font-size: 13.5px;
  color: var(--muted-2);
}

/* The badge row: three facts, not decoration. */
.badges {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 8px 10px;
  margin: 0 0 26px;
  padding: 0;
  list-style: none;
}
.badges li {
  display: inline-flex;
  align-items: center;
  gap: 7px;
  padding: 6px 13px;
  border: 1px solid var(--border);
  border-radius: 999px;
  background: var(--panel);
  font-size: 12.5px;
  font-weight: 600;
  color: var(--muted);
}
.badges b {
  color: var(--accent);
  font-weight: 700;
}

/* ==========================================================================
   The window under the hero — a real miniature, not a screenshot
   ==========================================================================
   Everything in it is live HTML at 11px, so it stays sharp on any screen, in
   dark or light, and weighs nothing. It is aria-hidden: it illustrates, it does
   not inform, and the features list below says all of it in words.
   ========================================================================== */

.shot {
  max-width: 1000px;
  margin: 52px auto 0;
  border: 1px solid var(--border);
  border-radius: var(--radius);
  background: var(--bg-2);
  box-shadow: 0 30px 80px -30px rgba(0, 0, 0, 0.9),
    0 0 0 1px rgba(255, 255, 255, 0.02) inset;
  overflow: hidden;
  text-align: left;
  font-size: 11px;
  line-height: 1.55;
}
.shot-bar {
  display: flex;
  align-items: center;
  gap: 10px;
  height: 38px;
  padding: 0 12px;
  background: var(--panel-2);
  border-bottom: 1px solid var(--border);
}
.shot-bar .shot-logo {
  color: var(--text-strong);
  flex: none;
  display: block;
}
.shot-seg {
  display: inline-flex;
  gap: 2px;
  margin-left: auto;
  padding: 2px;
  border: 1px solid var(--border);
  border-radius: 7px;
  background: var(--bg);
}
.shot-seg span {
  padding: 2px 9px;
  border-radius: 5px;
  color: var(--muted-2);
  font-weight: 600;
}
.shot-seg span.on {
  background: var(--accent);
  color: var(--accent-ink);
}
.shot-chip {
  padding: 3px 9px;
  border: 1px solid var(--border);
  border-radius: 6px;
  color: var(--muted-2);
}

.shot-main {
  display: grid;
  grid-template-columns: 150px 1fr;
  min-height: 300px;
}
.shot-toc {
  padding: 12px 10px;
  border-right: 1px solid var(--border);
  background: var(--panel);
}
.shot-toc b {
  display: block;
  margin: 0 0 8px 8px;
  font-size: 9px;
  font-weight: 700;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--muted-2);
}
.shot-toc span {
  display: block;
  padding: 3px 8px;
  border-left: 2px solid var(--border);
  color: var(--muted);
}
.shot-toc span.on {
  border-left-color: var(--accent);
  background: var(--accent-soft);
  color: var(--text-strong);
  font-weight: 600;
}
.shot-doc {
  margin: 14px;
  padding: 18px 20px 24px;
  border: 1px solid var(--border);
  border-radius: 10px;
  background: var(--panel);
  color: var(--text);
  /* A grid item's implicit min-width is `auto`, which means "never narrower than
     my widest unbreakable child". The <pre> below is `white-space: pre`, so that
     floor is the longest line of code — about 385px, which is wider than a phone.
     Without this the frame would refuse to shrink and .shot would quietly clip
     the right-hand third of the document off. */
  min-width: 0;
}
/* Not an <h4>: the miniature is aria-hidden decoration, and a real heading here
   would put an h1 → h4 jump in the document outline for no reader's benefit. */
.shot-doc .shot-h {
  margin: 0 0 10px;
  padding-bottom: 8px;
  border-bottom: 1px solid var(--border);
  font-size: 17px;
  font-weight: 750;
  letter-spacing: -0.02em;
  color: var(--text-strong);
}
.shot-doc p {
  margin: 0 0 10px;
}

.shot-doc strong {
  color: var(--text-strong);
}
.shot-doc pre {
  margin: 0 0 10px;
  padding: 9px 11px;
  border: 1px solid var(--border);
  border-radius: 7px;
  background: var(--bg);
  font-family: var(--font-mono);
  font-size: 10.5px;
  line-height: 1.7;
  /* Clipped, not scrollable. The miniature is aria-hidden illustration; a
     scrollbar here would read as a real control on something nobody is meant to
     operate. On a narrow screen the line simply runs off the edge, which is what
     a code block in a too-narrow window looks like anyway. */
  overflow: hidden;
}
.shot-doc code {
  font-family: var(--font-mono);
}
.shot-doc :not(pre) > code {
  padding: 1px 5px;
  border-radius: 4px;
  background: var(--bg);
  color: var(--accent);
  font-size: 10px;
}
/* Stand-ins for the highlighter's three commonest tokens. */
.k {
  color: var(--violet);
}
.s {
  color: var(--accent);
}
.c {
  color: var(--muted-2);
}
.shot-doc table {
  width: 100%;
  /* `fixed` so the two columns divide whatever width there is instead of asking
     their content how wide they would like to be — the Key column's `Ctrl+Shift+S`
     would otherwise hold the table above 380px on a phone. */
  table-layout: fixed;
  border-collapse: collapse;
  border: 1px solid var(--border);
  border-radius: 6px;
  overflow: hidden;
  font-size: 10.5px;
}
.shot-doc th,
.shot-doc td {
  border: 1px solid var(--border);
  padding: 4px 8px;
  text-align: left;
  /* With table-layout: fixed a long cell would spill past its column, so let it
     break. These are key names, not prose; a break mid-token is fine here. */
  overflow-wrap: anywhere;
}
.shot-doc th {
  background: var(--panel-2);
  color: var(--text-strong);
}

/* ==========================================================================
   Features
   ========================================================================== */
.grid {
  display: grid;
  /* min() keeps auto-fit from insisting on 268px inside a 288px phone and
     pushing a scrollbar onto the page. */
  grid-template-columns: repeat(auto-fit, minmax(min(268px, 100%), 1fr));
  gap: 18px;
}
.card {
  padding: 24px 22px;
  border: 1px solid var(--border);
  border-radius: var(--radius);
  background: linear-gradient(180deg, var(--panel-2), var(--panel));
  transition: border-color 160ms ease, transform 160ms ease;
}
.card:hover {
  border-color: var(--accent-line);
  transform: translateY(-2px);
}
.card-ico {
  display: grid;
  place-items: center;
  width: 38px;
  height: 38px;
  margin: 0 0 15px;
  border: 1px solid var(--border);
  border-radius: 10px;
  background: var(--bg);
  color: var(--accent);
}
.card h3 {
  margin: 0 0 7px;
}
.card p {
  margin: 0;
  font-size: 14.2px;
  line-height: 1.6;
  color: var(--muted);
}
/* A card's body is muted on purpose; the few words it emphasises have to climb
   back out of that, or the emphasis is only weight and gets lost at 14px. */
.card p strong {
  color: var(--text-strong);
  font-weight: 650;
}

/* ==========================================================================
   Privacy band — the one claim worth its own section
   ========================================================================== */
.band {
  padding: 42px 34px;
  border: 1px solid var(--accent-line);
  border-radius: 18px;
  background: linear-gradient(140deg, var(--accent-soft), transparent 62%),
    var(--panel);
  text-align: center;
}

.band p {
  max-width: 66ch;
  margin: 14px auto 0;
  color: var(--muted);
}

/* ==========================================================================
   Download
   ========================================================================== */
.dl-grid {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(300px, 100%), 1fr));
  gap: 18px;
  align-items: stretch;
}
.dl {
  display: flex;
  flex-direction: column;
  padding: 28px 26px;
  border: 1px solid var(--border);
  border-radius: var(--radius);
  background: var(--panel);
}
.dl-best {
  border-color: var(--accent-line);
  background: linear-gradient(170deg, var(--accent-soft), transparent 55%),
    var(--panel);
}
.dl-tag {
  align-self: flex-start;
  margin: 0 0 14px;
  padding: 3px 10px;
  border-radius: 999px;
  background: var(--accent);
  color: var(--accent-ink);
  font-size: 11px;
  font-weight: 750;
  letter-spacing: 0.08em;
  text-transform: uppercase;
}
.dl-tag-quiet {
  background: var(--panel-2);
  border: 1px solid var(--border);
  color: var(--muted);
}
.dl h3 {
  font-size: 1.2rem;
}
.dl-meta {
  margin: 6px 0 0;
  font-size: 12.5px;
  color: var(--muted-2);
  font-variant-numeric: tabular-nums;
}

.dl-list {
  margin: 16px 0 22px;
  padding: 0;
  list-style: none;
  font-size: 14px;
  color: var(--muted);
}
.dl-list li {
  display: flex;
  gap: 9px;
  padding: 4px 0;
}
.dl-list li::before {
  content: "";
  flex: none;
  width: 6px;
  height: 6px;
  margin-top: 9px;
  border-radius: 50%;
  background: var(--accent);
}
.dl .cta {
  margin-top: auto;
}

/* The Windows warning. Someone downloading an unsigned installer will meet it,
   so it is on the page rather than buried in a readme they will not open. */
.notice {
  margin: 26px 0 0;
  padding: 20px 22px;
  border: 1px solid var(--border);
  border-left: 3px solid var(--accent);
  border-radius: var(--radius-sm);
  background: var(--panel);
}
.notice h3 {
  margin: 0 0 8px;
}
.notice p {
  margin: 0 0 10px;
  font-size: 14.2px;
  color: var(--muted);
}
.notice p:last-child {
  margin-bottom: 0;
}
.notice p strong {
  color: var(--text-strong);
  font-weight: 650;
}
/* Inline code, wherever prose needs to name a key, a file or a fence. One rule
   so `.md` looks the same in a card, a note, an answer, the hero and a guide.
   A new prose container has to be added here or its <code> renders unstyled —
   .doc covers both guide pages, including the syntax column of every table. */
.notice code,
.faq code,
.hero-note code,
.dl-list code,
.card p code,
.band p code,
.doc code {
  padding: 2px 6px;
  border: 1px solid var(--border);
  border-radius: 5px;
  background: var(--bg);
  color: var(--accent);
  font-family: var(--font-mono);
  font-size: 0.86em;
}

/* ==========================================================================
   FAQ — <details>, so it opens without a line of JavaScript
   ==========================================================================
   The page ships no script at all (_headers sets script-src 'self' and there is
   nothing to serve), and an accordion is the one place a marketing page usually
   reaches for one. <details>/<summary> is the browser's own, keyboard-operable
   and findable by Ctrl+F even while closed.
   ========================================================================== */

.faq {
  display: grid;
  gap: 10px;
  max-width: 78ch;
}
.faq details {
  border: 1px solid var(--border);
  border-radius: var(--radius-sm);
  background: var(--panel);
  overflow: hidden;
}
.faq details[open] {
  border-color: var(--accent-line);
}
.faq summary {
  display: flex;
  align-items: center;
  gap: 12px;
  padding: 15px 18px;
  color: var(--text-strong);
  font-weight: 600;
  cursor: pointer;
  list-style: none; /* Firefox */
}
.faq summary::-webkit-details-marker {
  display: none; /* Safari's own triangle, replaced below */
}
/* A plus that becomes a minus. Drawn from two borders so it needs no glyph and
   cannot pick up a font the system does not have. */
.faq summary::after {
  content: "+";
  margin-left: auto;
  flex: none;
  width: 22px;
  height: 22px;
  display: grid;
  place-items: center;
  border: 1px solid var(--border);
  border-radius: 6px;
  color: var(--accent);
  font-size: 15px;
  line-height: 1;
}
.faq details[open] summary::after {
  content: "\2212"; /* minus sign, not a hyphen */
}
.faq summary:hover {
  background: var(--panel-2);
}
.faq p {
  margin: 0;
  padding: 0 18px 17px;
  font-size: 14.4px;
  color: var(--muted);
}
.faq p + p {
  padding-top: 0;
  margin-top: -6px;
}

/* ==========================================================================
   Footer
   ========================================================================== */
.foot {
  padding: 40px 0 46px;
  border-top: 1px solid var(--border-soft);
  background: var(--bg-2);
}
.foot-in {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 14px 26px;
}
.foot-brand {
  display: flex;
  align-items: center;
  gap: 9px;
  color: var(--text-strong);
  font-weight: 700;
}
.foot-links {
  display: flex;
  flex-wrap: wrap;
  /* The row gap is small because each link now carries its own vertical padding
     for the tap target; 8px of it would stack on top of that. */
  gap: 2px 20px;
  margin-left: auto;
  font-size: 14px;
}
.foot-links a {
  /* A bare 14px line is 23px tall, one pixel under the 24px floor WCAG 2.5.8
     asks of a pointer target. These are the smallest targets on the page and the
     ones a thumb reaches for last, so they get the padding rather than the
     benefit of the doubt. */
  display: inline-flex;
  align-items: center;
  min-height: 24px;
  padding: 3px 0;
  color: var(--muted);
}
.foot-links a:hover {
  color: var(--accent);
  text-decoration: none;
}
.foot-note {
  flex: 1 1 100%;
  margin: 4px 0 0;
  font-size: 12.5px;
  color: var(--muted-2);
}

/* Developer credit.
   Its own row below the legal note, with a hairline above it so it reads as a
   signature rather than one more clause of the boilerplate. The studio name is
   full-strength text and the URL beside it is muted mono, so the pair scans as
   one credit instead of two links competing for the same click — they do in fact
   go to the same place, which is why they share a single anchor. */
.foot-credit {
  flex: 1 1 100%;
  margin: 20px 0 0;
  padding-top: 16px;
  border-top: 1px solid var(--border-soft);
  font-size: 13px;
  color: var(--muted-2);
}
.foot-credit a {
  /* inline-flex for the same 24px tap-target floor the nav links get. */
  display: inline-flex;
  align-items: baseline;
  flex-wrap: wrap;
  min-height: 24px;
  color: var(--text-strong);
  font-weight: 600;
}
.foot-credit a:hover {
  color: var(--accent);
  text-decoration: none;
}
.credit-sep {
  margin: 0 8px;
  color: var(--border);
}
.credit-url {
  color: var(--muted);
  font-family: var(--font-mono);
  font-size: 12px;
  font-weight: 500;
}
.foot-credit a:hover .credit-url,
.foot-credit a:hover .credit-sep {
  color: var(--accent);
}

/* ==========================================================================
   Responsive — 320px phone up
   ==========================================================================
   Everything above is fluid already: the grids are auto-fit, the headings are
   clamp(), and .wrap is a max-width. These three blocks only handle the things
   fluidity cannot decide on its own — what to drop, what to stack, and where
   the miniature stops being readable.
   ========================================================================== */

@media (max-width: 900px) {
  .section {
    padding: 64px 0;
  }
  .hero {
    padding: 56px 0 30px;
  }
  .shot {
    margin-top: 40px;
  }
  .band {
    padding: 34px 24px;
  }
}

/* The miniature's contents column is 150px of a 700px window; below that the
   document beside it stops looking like a document and starts looking like a
   column of broken lines. The panel is the first thing to go, and the toolbar's
   filename chip follows it — the window is an illustration, and neither is what
   it illustrates. */
@media (max-width: 760px) {
  .nav-links {
    display: none;
  }
  .shot-main {
    grid-template-columns: 1fr;
    min-height: 0;
  }
  .shot-toc,
  .shot-chip {
    display: none;
  }
  .shot-doc {
    margin: 12px;
    padding: 16px 16px 20px;
  }
  .dl {
    padding: 24px 20px;
  }
  .notice {
    padding: 18px 18px;
  }
}

/* Phones. Two buttons side by side at 360px are two buttons nobody can read the
   label of, so the hero's calls to action become full-width rows — which is also
   the easiest thing to hit with a thumb. */
@media (max-width: 560px) {
  .wrap {
    padding: 0 16px;
  }
  .section {
    padding: 52px 0;
  }
  .section-head {
    margin-bottom: 32px;
  }
  .hero {
    padding: 40px 0 24px;
  }
  .hero-cta {
    flex-direction: column;
    align-items: stretch;
    gap: 11px;
    margin-top: 28px;
  }
  .hero-cta .cta {
    width: 100%;
  }
  .cta-lg {
    padding: 14px 22px;
    min-height: 52px;
  }
  .badges {
    gap: 7px;
  }
  .badges li {
    padding: 5px 11px;
    font-size: 12px;
  }
  .shot {
    margin-top: 32px;
    border-radius: 11px;
  }
  .shot-bar {
    height: 34px;
    padding: 0 9px;
  }
  .card {
    padding: 21px 18px;
  }
  .band {
    padding: 28px 18px;
    border-radius: 14px;
  }
  .faq summary {
    padding: 14px 15px;
  }
  .faq p {
    padding: 0 15px 15px;
  }
  .foot-links {
    margin-left: 0;
  }
}

/* 320px, the narrowest screen still worth supporting. The nav is down to a
   wordmark and one button by here, and they have to share 288px. */
@media (max-width: 380px) {
  .nav-in {
    gap: 10px;
  }
  .nav .cta {
    padding: 8px 12px;
    font-size: 13.5px;
  }
  .hero h1 {
    letter-spacing: -0.02em;
  }
  .shot {
    font-size: 10.5px;
  }
  .shot-doc {
    margin: 10px;
    padding: 14px 13px 18px;
  }
  .shot-doc .shot-h {
    font-size: 15px;
  }
  .dl,
  .card {
    padding: 20px 16px;
  }
}

/* ==========================================================================
   Long-form pages — the guides
   ==========================================================================

   markdown-cheatsheet.html and open-md-file.html are prose: paragraphs,
   tables, code fences, lists and steps, none of which anything above styles.
   The home page is components; a guide is text, and text needs its own
   typography.

   Every rule is scoped to .doc so none of it can reach index.html, and the
   page furniture — .wrap, .section, .eyebrow, .cta, .notice, .card — is reused
   rather than restated. Both guides are scriptless like the home page, so
   there is no syntax highlighting in here: a cheat sheet's code fences are
   four-line examples of Markdown, and colouring them would cost a bundle to
   say nothing.

   .doc is a reading column, not the full 1120px .wrap. A line of prose becomes
   hard to track back long before a grid of cards looks too wide. */

.doc {
  max-width: 74ch;
}
.doc > :first-child {
  margin-top: 0;
}
.doc p {
  margin: 0 0 16px;
}
.doc p:last-child {
  margin-bottom: 0;
}
.doc strong {
  color: var(--text-strong);
  font-weight: 650;
}

/* The nav is sticky and 64px tall, so an in-page jump has to stop short of it
   or the heading it landed on is hidden underneath.

   The sizes are set here rather than inherited. The global h2 is a landing-page
   section heading — 36.8px, built to be read once from across the room — and at
   that size twelve of them in a 74ch column sit almost level with the page's own
   h1 and stop reading as subordinate to it. A document needs the steps between
   h1, h2 and h3 to be obvious at a glance, so each one gets its own. */
.doc h2 {
  scroll-margin-top: 84px;
  margin: 46px 0 14px;
  padding-top: 26px;
  border-top: 1px solid var(--border-soft);
  font-size: clamp(1.35rem, 1.18rem + 0.7vw, 1.62rem);
  line-height: 1.25;
  letter-spacing: -0.015em;
  color: var(--text-strong);
}
.doc h3 {
  scroll-margin-top: 84px;
  margin: 30px 0 10px;
  font-size: 1.06rem;
  line-height: 1.35;
  letter-spacing: -0.01em;
  color: var(--text-strong);
}

.doc ul,
.doc ol {
  margin: 0 0 16px;
  padding-left: 22px;
}
.doc li {
  margin: 0 0 7px;
}
.doc li > ul,
.doc li > ol {
  margin: 7px 0 0;
}
.doc li::marker {
  color: var(--muted-2);
}

.doc blockquote {
  margin: 0 0 18px;
  padding: 2px 0 2px 16px;
  border-left: 3px solid var(--accent-line);
  color: var(--muted);
}
.doc blockquote p:last-child {
  margin-bottom: 0;
}

.doc hr {
  height: 1px;
  margin: 24px 0;
  border: 0;
  background: var(--border);
}

.doc pre {
  margin: 0 0 18px;
  padding: 14px 16px;
  overflow-x: auto;
  border: 1px solid var(--border);
  border-radius: var(--radius-sm);
  background: var(--bg-2);
  font-family: var(--font-mono);
  font-size: 13.2px;
  line-height: 1.6;
  -webkit-overflow-scrolling: touch;
}
/* Block code is already a bordered box in a monospace face; the inline pill
   would put a second border and a lime foreground inside it. */
.doc pre code {
  padding: 0;
  border: 0;
  border-radius: 0;
  background: none;
  color: inherit;
  font-size: inherit;
}

/* Tables carry most of the cheat sheet. The scroll lives on a wrapper rather
   than the table so the rounded border stays put while the columns move, and so
   a phone gets a swipe instead of a page-wide horizontal scrollbar. */
.doc-table {
  margin: 0 0 20px;
  overflow-x: auto;
  border: 1px solid var(--border);
  border-radius: var(--radius-sm);
  background: var(--panel);
  -webkit-overflow-scrolling: touch;
}
.doc table {
  width: 100%;
  border-collapse: collapse;
  font-size: 14.4px;
}
.doc th,
.doc td {
  padding: 11px 14px;
  text-align: left;
  vertical-align: top;
  border-bottom: 1px solid var(--border-soft);
}
.doc tr:last-child th,
.doc tr:last-child td {
  border-bottom: 0;
}
.doc thead th {
  background: var(--panel-2);
  color: var(--text-strong);
  font-size: 12px;
  font-weight: 700;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  white-space: nowrap;
}
/* pre-wrap, not pre: the two trailing spaces that make a line break, and the
   indentation that nests a list, are the point of several of these cells and
   normal white-space collapsing would delete them — but a long example still
   has to be allowed to wrap rather than widen the table. */
.doc td code {
  white-space: pre-wrap;
}
.doc .col-syntax {
  width: 42%;
}

/* The right-hand column of the cheat sheet shows what the syntax produces, so
   it has to *look* rendered without being it. Forty real headings inside a
   table would wreck the document outline and compete with the one heading on
   the page that should be ranking, so these are spans that borrow the sizes. */
.doc .r {
  display: block;
  color: var(--text-strong);
  font-weight: 750;
  letter-spacing: -0.02em;
  line-height: 1.3;
}
.doc .r-1 {
  font-size: 1.5rem;
}
.doc .r-2 {
  font-size: 1.22rem;
}
.doc .r-3 {
  font-size: 1.05rem;
}
.doc .r-4 {
  font-size: 0.95rem;
}
/* A rule, a checkbox and a swatch, drawn rather than typed, for the rows that
   demonstrate them. */
.doc .r-hr {
  display: block;
  height: 1px;
  margin: 9px 0;
  background: var(--border);
}
.doc .r-box {
  display: inline-block;
  width: 13px;
  height: 13px;
  margin-right: 7px;
  vertical-align: -2px;
  border: 1px solid var(--muted-2);
  border-radius: 3px;
}
.doc .r-box-on {
  border-color: var(--accent);
  background: var(--accent);
  color: var(--accent-ink);
  font-size: 10px;
  font-weight: 800;
  line-height: 11px;
  text-align: center;
}

/* Numbered steps for "open a .md file". A counter rather than an <ol> marker,
   because the number wants to be a lime disc and a ::marker cannot be one. */
.doc .steps {
  counter-reset: step;
  margin: 0 0 20px;
  padding: 0;
  list-style: none;
}
.doc .steps > li {
  position: relative;
  margin: 0 0 15px;
  padding: 0 0 0 44px;
  counter-increment: step;
}
.doc .steps > li::before {
  content: counter(step);
  position: absolute;
  left: 0;
  top: 1px;
  width: 28px;
  height: 28px;
  display: grid;
  place-items: center;
  border: 1px solid var(--accent-line);
  border-radius: 50%;
  background: var(--accent-soft);
  color: var(--accent);
  font-size: 13px;
  font-weight: 700;
  font-variant-numeric: tabular-nums;
}
.doc .steps > li > strong:first-child {
  display: block;
}

/* Keys and menu items, for the ones the reader has to find on their own
   machine. Deliberately the UI face, not the mono one — Windows does not label
   that button in Consolas. */
.doc kbd {
  padding: 2px 7px;
  border: 1px solid var(--border);
  border-bottom-width: 2px;
  border-radius: 6px;
  background: var(--panel-2);
  color: var(--text-strong);
  font-family: var(--font-ui);
  font-size: 0.82em;
  font-weight: 600;
  white-space: nowrap;
}

/* The contents list. A <nav> with a plain paragraph for a label rather than a
   heading: it is navigation, aria-label already says what it is, and a real
   <h2> here would be the first heading on the page after the h1 and would say
   "On this page" to anything reading the outline. */
.toc {
  margin: 30px 0 0;
  padding: 18px 22px;
  border: 1px solid var(--border);
  border-radius: var(--radius-sm);
  background: var(--panel);
}
.toc-t {
  margin: 0 0 12px;
  color: var(--muted-2);
  font-size: 12px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}
/* Scoped to .toc, not .doc .toc: the contents box sits in .doc-head, above the
   article, so a .doc-prefixed selector never matches it. .toc only exists on the
   guide pages anyway, so it is specific enough on its own. */
.toc ol {
  columns: 2;
  column-gap: 30px;
  margin: 0;
  padding: 0 0 0 20px;
  font-size: 14.4px;
}
.toc li {
  margin: 0 0 6px;
  break-inside: avoid;
}

/* The masthead of a guide: eyebrow, h1, standfirst. .hero is the home page's
   and is much taller than a guide wants. */
.doc-head {
  padding: 46px 0 8px;
}
.doc-head h1 {
  margin: 0;
  font-size: clamp(1.9rem, 1.4rem + 2vw, 2.7rem);
  line-height: 1.14;
  color: var(--text-strong);
}
.doc-head .lede {
  max-width: 68ch;
  margin-top: 16px;
  font-size: 1.09rem;
}
.doc-updated {
  margin: 18px 0 0;
  color: var(--muted-2);
  font-size: 13.4px;
}

/* A whole .card as one link, for the guides block on the home page. Without
   the first rule every word in the card would be lime, because a { color:
   var(--accent) } at the top of this file catches all of it. */
a.card-link {
  display: block;
  color: inherit;
  text-decoration: none;
}
a.card-link:hover {
  text-decoration: none;
}
.card-go {
  display: inline-block;
  margin-top: 13px;
  color: var(--accent);
  font-size: 14px;
  font-weight: 650;
}
a.card-link:hover .card-go {
  color: var(--accent-strong);
  text-decoration: underline;
}

/* The in-article call to action reuses .notice, which is already a bordered
   panel with a lime edge; all it needs is room for the button. */
.notice .cta {
  margin-top: 6px;
}

@media (max-width: 700px) {
  .doc-head {
    padding: 30px 0 4px;
  }
  .doc h2 {
    margin-top: 34px;
    padding-top: 20px;
  }
  .doc table {
    font-size: 13.6px;
  }
  .doc th,
  .doc td {
    padding: 9px 11px;
  }
  .doc .col-syntax {
    width: auto;
  }
  .toc ol {
    columns: 1;
  }
}

/* A cheat sheet is the one page here somebody genuinely might print. The
   general print block below handles the colours; this handles the parts of a
   guide that block has never seen. */
@media print {
  .doc,
  .doc-head .lede {
    max-width: none;
  }
  .doc h2 {
    border-top-color: #ccc;
    break-after: avoid;
  }
  .doc h3 {
    break-after: avoid;
  }
  .doc pre,
  .doc-table,
  .toc {
    border-color: #bbb;
    background: none;
    break-inside: avoid;
  }
  .doc th,
  .doc td {
    border-bottom-color: #ddd;
  }
  .doc thead th {
    background: none;
    color: #000;
  }
  .doc blockquote {
    border-left-color: #bbb;
    color: #333;
  }
  .doc .r,
  .doc kbd {
    color: #000;
  }
  .doc kbd {
    background: none;
    border-color: #999;
  }
  .doc .steps > li::before {
    border-color: #999;
    background: none;
    color: #000;
  }
  .doc .r-hr {
    background: #999;
  }
  .doc-updated {
    color: #555;
  }
}

/* ==========================================================================
   Motion and print
   ========================================================================== */

/* The card lift and the button nudge are the only motion here, and the smooth
   scroll on html is the one that matters — a jump to #download should be
   instant for anyone who asked for that. */
@media (prefers-reduced-motion: reduce) {
  html {
    scroll-behavior: auto;
  }
  *,
  *::before,
  *::after {
    animation-duration: 0.001ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.001ms !important;
  }
  .card:hover {
    transform: none;
  }
  .cta:active {
    transform: none;
  }
}

/* ---- the not-found page ---------------------------------------------------
   404.html borrows this whole stylesheet and adds nothing of its own — its nav,
   hero, buttons and footer are all the landing page's. The one thing it needs
   is this: it is the only page short enough that the footer would otherwise
   stop halfway down a tall screen with bare background below it. Pushing the
   footer to the bottom is a two-rule job, so it lives here rather than in a
   second stylesheet.

   100vh first for anything that predates the dynamic viewport units; browsers
   that understand 100dvh take the second and get the right answer when a phone
   toolbar slides away. */
.short-page {
  min-height: 100vh;
  min-height: 100dvh;
  display: flex;
  flex-direction: column;
}
.short-page main {
  flex: 1 0 auto;
}

/* Printing a landing page is unusual, but it happens — somebody sends the URL
   to whoever approves software on a work machine. Keep the words and the
   download URLs, drop the theatre. */
@media print {
  html {
    scroll-behavior: auto;
  }
  body {
    background: #fff;
    color: #000;
  }
  body::before,
  .nav,
  .skip,
  .shot,
  .badges,
  .hero-cta,
  .foot-links {
    display: none !important;
  }
  .section {
    padding: 18pt 0;
    border: 0;
  }
  .section + .section {
    border-top: 1px solid #ccc;
  }
  h1,
  h2,
  h3,
  .hero h1 em,
  .band h2,
  .dl h3,
  .shot-doc strong {
    color: #000;
    -webkit-text-fill-color: #000;
    background: none;
  }
  .lede,
  .hero-lede,
  .card p,
  .band p,
  .dl-list,
  .dl-meta,
  .notice p,
  .faq p,
  .foot-note,
  .foot-credit {
    color: #333;
  }
  /* The credit is worth keeping on paper, but its hairline and its two muted
     greys are tuned for a dark screen and would come out as near-white on white. */
  .foot-credit {
    border-top-color: #ccc;
  }
  .foot-credit a,
  .credit-url {
    color: #000;
  }
  .credit-sep {
    color: #999;
  }
  .card,
  .dl,
  .band,
  .notice,
  .faq details {
    border: 1px solid #bbb;
    background: none;
    break-inside: avoid;
  }
  .eyebrow,
  .dl-tag,
  .badges b {
    color: #000;
    background: none;
  }
  /* Lime on white is unreadable; on paper inline code is just monospace. */
  code {
    color: #000;
    background: none;
    border-color: #bbb;
  }
  /* A closed <details> cannot be forced open from CSS — the collapsed part
     lives in a slot the author cannot select, and opening it needs the one line
     of JavaScript this page does not have. So a printout carries the questions
     and whichever answer the reader had open, which is the part they were
     looking at anyway. The download URLs and the Windows note, which are what a
     printed page is actually for, are not in a <details> at all. */
  .faq details {
    break-inside: avoid;
  }
  /* Where the download buttons went, print where they pointed. */
  .dl .cta[href]::after {
    content: " (" attr(href) ")";
    font-size: 9pt;
    font-weight: 400;
    word-break: break-all;
  }
}