/* The landing page only. Loaded by core/landing.html and nowhere else, so the
   rest of the product does not carry the weight of a page it never renders.
   Tokens come from main.css, which is loaded first. */

.lede { font-size: 1.08rem; color: var(--ink-muted); max-width: 54ch; }

.landing-actions { display: flex; flex-wrap: wrap; gap: 10px; margin: 26px 0 14px; }
.landing-actions.center { justify-content: center; }
.landing-actions .btn { min-height: 46px; }
.btn-lg { --btn-py: 12px; --btn-px: 22px; --btn-panel-w: calc(1em + 30px); font-size: 0.96rem; }
/* A step up from 1em, which looked lost in a panel this size. The panel's width
   is resolved in the icon's em, now 1.15 of the button's, so it is restated in
   the button's: otherwise the panel outgrows the room the label leaves it. */
.btn-lg > .icon:first-child { font-size: 1.15em; --btn-panel-w: calc(1em / 1.15 + 30px); }
.landing-actions .btn .icon,
.landing-actions .btn-primary .icon,
.landing-actions .btn .svg-icon,
.landing-actions .btn-primary .svg-icon { color: var(--btn-panel-ink); }

.landing-section { padding: 62px 28px; }
.landing-tinted { background: var(--surface); border-block: 1px solid var(--line); }
.landing-inner { max-width: 1120px; margin: 0 auto; }
.landing-inner.center { text-align: center; }

.landing-head { margin-bottom: 30px; }
.landing-head h2 { font-size: 1.7rem; letter-spacing: -0.01em; margin-bottom: 8px; }
.landing-inner.center .lede { margin-inline: auto; }

.landing-steps {
  display: grid; grid-template-columns: repeat(3, minmax(0, 1fr));
  gap: var(--gap); list-style: none; margin: 0; padding: 0; counter-reset: step;
}
.landing-steps li {
  position: relative;
  background: var(--surface); border: 1px solid var(--line);
  border-radius: var(--radius); padding: 22px; box-shadow: var(--shadow);
}
/* The number, the icon and the title on one line, for the same reason. */
.landing-step-head { display: flex; align-items: center; gap: 10px; margin-bottom: 8px; }
.landing-steps h3 { display: flex; align-items: center; gap: 9px; margin: 0; }
.landing-steps h3 .icon { color: var(--brand); }
.landing-step-num {
  display: inline-flex; align-items: center; justify-content: center;
  width: 30px; height: 30px; border-radius: 50%;
  background: var(--brand); color: var(--on-brand); font-weight: 700; font-size: 0.9rem;
}

.landing-features {
  display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: var(--gap);
}
.landing-feature {
  background: var(--canvas); border: 1px solid var(--line);
  border-radius: var(--radius); padding: 22px;
}
/* The mark and the headline on one line. Stacked, each card spent a row on a
   40px square and pushed the sentence that does the work further down the page;
   inline, the eye reads mark-then-title as one thing. */
.landing-feature-head { display: flex; align-items: center; gap: 12px; }
.landing-feature h3 { font-size: 1rem; margin: 0; }
.landing-feature p { margin: 10px 0 0; }
.landing-feature-mark {
  display: inline-flex; align-items: center; justify-content: center; flex: none;
  width: 40px; height: 40px; border-radius: var(--radius-sm);
  background: var(--brand-light); color: var(--brand); font-size: 1.2rem;
}

/* The menu's features: the same cards, smaller, because there are fifteen of
   them and the reader is looking for one. In two groups, each under a heading
   that says who the group is for. Three to a row, from `.landing-features` and
   its breakpoints: nine and six divide by three, and four to a row left one
   card alone under the first group and two under the second. */
.landing-menu-features .landing-head { margin-bottom: 8px; }
.landing-group-title {
  display: flex; align-items: center; gap: 9px;
  margin: 30px 0 14px; font-size: 1.05rem;
}
.landing-group-title .icon { color: var(--brand); }
.landing-features.is-compact { gap: 12px; list-style: none; margin: 0; padding: 0; }
.landing-features.is-compact .landing-feature { padding: 16px 18px; }
.landing-features.is-compact .landing-feature-head { gap: 10px; }
.landing-features.is-compact h4 { font-size: 0.96rem; margin: 0; }
.landing-features.is-compact p { margin-top: 8px; font-size: 0.92rem; line-height: 1.5; }
.landing-features.is-compact .landing-feature-mark { width: 34px; height: 34px; font-size: 1.05rem; }

/* --- The comparison ----------------------------------------------------------
   A table, because the reader is comparing, and a table is what lets the eye
   run down one column and across one row. What it is not is bare: our column
   is lifted out of the grid - its header in the brand colour, its cells washed
   with it - so the answer is visible before a word is read, and every cell has
   a mark that differs in shape as well as colour, so the three states still
   differ to somebody who cannot tell green from amber. */
.compare {
  width: 100%; border-collapse: separate; border-spacing: 0;
  background: var(--canvas); border: 1px solid var(--line);
  border-radius: var(--radius); box-shadow: var(--shadow);
  table-layout: fixed; font-size: 0.93rem; line-height: 1.45;
}
.compare th, .compare td { padding: 14px 16px; text-align: left; vertical-align: top; }
.compare thead td, .compare thead th { border-bottom: 1px solid var(--line); }
.compare tbody tr + tr > * { border-top: 1px solid var(--line-soft); }
.compare thead tr > :first-child { width: 22%; }
/* `.compare thead` rather than the class alone, which loses to the `top` two
   rules up - and a name on one line sat at the top of a header row made tall
   by a name on two. The mark and the name are a flex row for the same reason
   a cell is: a name's second line starts under the name, not under the mark. */
.compare thead > tr > * { vertical-align: bottom; }
.compare-col { font-size: 0.9rem; font-weight: 650; }
.compare-col-say { display: flex; align-items: center; gap: 9px; }
.compare-col-mark {
  display: inline-flex; align-items: center; justify-content: center; flex: none;
  width: 30px; height: 30px;
  border-radius: var(--radius-sm); background: var(--line-soft); color: var(--ink-muted);
}
.compare-col.is-ours { background: var(--brand); color: var(--on-brand); border-top-left-radius: var(--radius-sm); border-top-right-radius: var(--radius-sm); }
.compare-col.is-ours .compare-col-mark { background: color-mix(in srgb, var(--on-brand) 18%, transparent); color: var(--on-brand); }
.compare-row { font-weight: 650; }
.compare-cell { color: var(--ink-muted); }
.compare-cell.is-ours { background: var(--brand-wash); color: var(--ink); }
.compare-say { display: flex; align-items: flex-start; gap: 9px; overflow-wrap: anywhere; hyphens: auto; }
.compare-mark {
  display: inline-flex; align-items: center; justify-content: center; flex: none;
  width: 22px; height: 22px; border-radius: 50%; font-size: 0.8rem; margin-top: -1px;
}
.compare-cell.is-yes .compare-mark { background: var(--ok-bg); color: var(--ok); border: 1px solid var(--ok-line); }
.compare-cell.is-partly .compare-mark { background: var(--warn-bg); color: var(--warn-ink); border: 1px solid var(--warn-line); }
.compare-cell.is-no .compare-mark { background: var(--line-soft); color: var(--ink-faint); border: 1px solid var(--line); }
.compare-cell.is-ours.is-yes .compare-mark { background: var(--ok); color: var(--surface); border-color: var(--ok); }
/* The column's name inside each cell is for the narrow layout only, where the
   header row is gone. */
.compare-label { display: none; }

/* --- The menus section ------------------------------------------------------
   Copy on the left, the photograph on the right, and the two swap to one column
   on a narrow screen with the picture underneath - a phone showing a picture of
   a phone above the sentence explaining it is a riddle. */
.landing-menus { background: var(--surface); }
.landing-menus-inner {
  display: grid; grid-template-columns: minmax(0, 1.05fr) minmax(0, 0.95fr);
  gap: 48px; align-items: center;
}
/* What an owner can track: each half of it beside its picture, the second the
   other way round so the two read as a pair. A picture of a light editor on
   either theme, so it carries its own edge and is never tinted. */
.landing-analytics {
  display: grid; grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 36px; align-items: start;
}
.landing-analytics + .landing-analytics { margin-top: 44px; }
.landing-analytics.is-flipped .landing-shot { order: -1; }
/* The ranking is far taller than the words about it, so they stay in view
   beside it, clear of the sticky header, until the picture has gone by. */
.landing-analytics.is-flipped > div { position: sticky; top: 96px; }
.landing-analytics .landing-group-title { margin-top: 0; }
.landing-tracked { display: grid; gap: 12px; list-style: none; margin: 0 0 16px; padding: 0; }
.landing-tracked strong { display: block; margin-bottom: 2px; }
.landing-shot { margin: 0; }
.landing-shot img {
  display: block; width: 100%; height: auto;
  border: 1px solid var(--line); border-radius: var(--radius); box-shadow: var(--shadow);
}
.landing-shot figcaption { margin-top: 8px; font-size: 0.76rem; color: var(--ink-faint); }
.landing-menus { padding-top: 72px; }
.landing-menus h1 {
  font-size: 2.6rem; line-height: 1.1; letter-spacing: -0.02em;
  margin: 6px 0 14px;
}
.landing-eyebrow {
  margin: 0; font-size: 0.76rem; font-weight: 700; letter-spacing: 0.09em;
  text-transform: uppercase; color: var(--brand);
}
/* Three reasons to put the menu on a phone at all, each a card with its mark,
   so they read as the section's argument rather than as the first three lines
   of a feature list. The third is green: it is the one a venue does not think
   to ask about, and the colour is the product's word for "good" already. */
.landing-pillars { list-style: none; margin: 22px 0 26px; padding: 0; display: grid; gap: 10px; }
.landing-pillar {
  display: flex; align-items: flex-start; gap: 14px; line-height: 1.5;
  padding: 14px 16px; border-radius: var(--radius);
  background: var(--brand-wash); border: 1px solid var(--brand-edge);
}
.landing-pillar strong { display: block; margin-bottom: 2px; }
.landing-pillar-mark {
  display: inline-flex; align-items: center; justify-content: center; flex: none;
  width: 38px; height: 38px; border-radius: var(--radius-sm);
  background: var(--brand); color: var(--on-brand); font-size: 1.15rem;
}
.landing-pillar.is-green { background: var(--ok-bg); border-color: var(--ok-line); }
.landing-pillar.is-green .landing-pillar-mark { background: var(--ok); }
/* The picture, and under each phone in it a way to open that menu for real: a
   code to scan, the venue's name and the address. Under the phone rather than in
   the column of copy beside it, because the phone is what makes somebody want
   to open it - the card belongs to the picture it is about.

   A container, so `cqw` below is a percentage of the *picture's* width. The
   handsets sit at fixed proportions of it - `tools/build_showcase.py` draws two
   430px phones 22px apart, trimmed to 52px of shadow either side, in a 986px
   sheet, the right one 54px higher - so the columns are padded and spaced by
   those same proportions and stay under their phones at every width. Change the
   geometry there and these four numbers have to be measured again. */
.landing-menus-shot { margin: 0; container-type: inline-size; }
.landing-menus-shot > img { display: block; width: 100%; height: auto; }
.landing-shot-demos {
  display: grid; grid-template-columns: 1fr 1fr; align-items: start;
  padding-inline: 5.27cqw; column-gap: 2.23cqw;
  /* Up into the strip of shadow under the lower phone, which is empty space. */
  margin-top: -2cqw;
}
/* The right-hand phone ends 54px higher, so its card does too: each hangs the
   same distance under its own handset, and the pair repeats the picture's
   stagger rather than squaring it off. */
.landing-shot-demos > :nth-child(2) { margin-top: -5.48cqw; }
.landing-shot-note { margin: 12px 0 0; text-align: center; text-wrap: balance; }

/* Each one is a link end to end, so the tap target is the whole card rather
   than the code. No box until it is pointed at: under a picture a pair of
   bordered cards read as two more things on the page, where a code and a name
   read as the phone's caption. The hover is the box, a lift and the arrow, and
   it presses when clicked and takes the same focus ring as the buttons. */
.landing-demo {
  display: flex; flex-direction: column; align-items: center; gap: 8px;
  padding: 10px 8px 12px; text-align: center;
  border: 1px solid transparent; border-radius: var(--radius);
  color: inherit; text-decoration: none; cursor: pointer;
  transition: transform 0.18s ease, background-color 0.18s ease, border-color 0.18s ease;
}
.landing-demo:hover {
  text-decoration: none; transform: translateY(-2px);
  background: var(--brand-tint); border-color: var(--line-strong);
}
/* Pressed, not lifted. Without this the card springs *up* under a finger that
   is pushing down on it, which is the one moment a link stops feeling like a
   button. */
.landing-demo:active { transform: translateY(0); }
.landing-demo:focus-visible { outline: 2px solid var(--brand); outline-offset: 2px; }
/* `--paper`, and it is not themed - see the paper tokens in main.css. A QR code
   is thresholded into light and dark before anything reads it, so the quiet
   zone around it has to be light whatever the rest of the page is doing. This
   is the one rule on the page that a dark theme must not touch.

   As wide as the phone allows up to 148px: on a phone-width page the picture is
   ~360px and each handset under 160, and a code that keeps its full size there
   pushes the card wider than the phone it is meant to sit under. Nobody scans a
   code on the screen they are holding; they tap it. */
.landing-demo-code {
  display: block; width: min(148px, 100%); height: auto; aspect-ratio: 1;
  border-radius: 10px; border: 1px solid var(--line);
  background: var(--paper); padding: 8px;
  box-shadow: 0 6px 16px rgb(var(--shadow-rgb) / 0.08);
}
/* The name carries the brand colour and the arrow, so the card says which part
   of it is the thing being followed - the address under it is ink. */
.landing-demo-name { display: flex; align-items: center; gap: 6px; color: var(--brand); }
.landing-demo-name .icon { width: 14px; height: 14px; transition: transform 0.18s ease; }
.landing-demo-url { color: var(--ink-muted); line-height: 1.4; overflow-wrap: anywhere; }
/* The arrow leans out of the card on hover: the whole card is the link, and this
   is the cheapest way to say which direction following it goes. */
.landing-demo:hover .icon { transform: translate(2px, -2px); }

/* --- Prices, on the public page ----------------------------------------------
   Four compact cards. Deliberately lighter than the signed-in plan page's: that
   one is a decision between tiers, this one is an answer to "what does it
   cost", and it is passed on the way down the page rather than studied. */
/* `.landing-inner.center` centres a lede by giving it auto margins; this head
   is centred without the whole column being, so it needs the same rule. */
.landing-head.center { margin-bottom: 24px; }
.landing-head.center .lede { margin-inline: auto; }

/* The switch is a column above the grid so it centres over it. Same shape the
   plan page uses; the rule is repeated here because that one is scoped to
   `.plan-page`, which is a class on the signed-in shell's content column. */
.landing-tinted .plan-periods { display: flex; flex-direction: column; align-items: center; }
.landing-tinted .plan-periods > .pricing-grid { width: 100%; }

.pricing-grid {
  display: grid;
  grid-template-columns: repeat(4, minmax(0, 1fr));
  gap: 14px;
  align-items: stretch;
}

.price-card {
  display: flex;
  flex-direction: column;
  gap: 10px;
  padding: 20px;
  background: var(--canvas);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  transition: transform 0.18s ease, box-shadow 0.18s ease, border-color 0.18s ease;
}
/* Each card is a tier with its own button, so it answers to the pointer the way
   `.plan-card` does on the signed-in plan page - same lift, same shadow, same
   easing. The two pricing tables are already held to the same *contents* by
   `_plan_features.html`; behaving differently under the pointer was the last
   way they still read as two different tables.

   Note this is not in tension with the ring below it. A momentary lift is what
   the pointer is over right now; the recommended card's mark is permanent, and
   permanently raising one card in a row of four is what would break the line
   the four bottoms sit on. */
.price-card:hover {
  transform: translateY(-3px);
  border-color: var(--brand);
  box-shadow: 0 10px 24px rgb(var(--shadow-rgb) / 0.09);
}
/* The one the table steers towards. A ring rather than a scale transform, for
   the reason above. It keeps the ring while hovered and takes the lift's shadow
   under it - without restating it here the ring's own `box-shadow` wins and the
   one card the table argues for is the one that does not respond. */
.price-card.is-recommended {
  background: var(--surface);
  border-color: var(--brand);
  box-shadow: 0 0 0 1px var(--brand), 0 6px 18px color-mix(in srgb, var(--brand) 10%, transparent);
}
.price-card.is-recommended:hover {
  box-shadow: 0 0 0 1px var(--brand), 0 10px 24px rgb(var(--shadow-rgb) / 0.09);
}

.price-head { display: flex; align-items: center; justify-content: space-between; gap: 8px; flex-wrap: wrap; }
.price-head h3 { font-size: 0.95rem; margin: 0; }

.price { font-size: 1.5rem; font-weight: 650; line-height: 1.2; }
.price-per { font-size: 0.78rem; font-weight: 500; color: var(--ink-muted); margin-left: 3px; }
/* The euro restatement, under the figure rather than beside it: the mark price
   is what is charged and has to stay the largest thing in the card. */
/* `min-height`, because two of the four tiers have no euro figure - Free is
   priced at nothing and Enterprise says "contact us" - and without the slot
   being held open their feature lists started a line above the other two. */
.price-eur {
  font-size: 0.76rem; font-weight: 500; color: var(--ink-faint);
  margin-top: -8px; min-height: 1.15em;
}

/* The shared feature list (core/_plan_features.html) inside a price card.
   `flex: 1` so the four lists absorb the slack in a short card and the button
   below them lands on the same line in all four. The rows are unruled here -
   the plan page draws a line between them, which is right in a wide table and
   too busy in a 260px card. */
.price-card .plan-features {
  margin: 4px 0 0; flex: 1;
  display: grid; gap: 0; align-content: start;
  font-size: 0.84rem;
}
.price-card .plan-features li { padding: 5px 0; border-bottom: none; }

/* The pay-terms block is `core/_pay_terms.html` and styles itself in main.css,
   which both pages load. Here it sits on the tinted band, so the two grounds
   swap: the block takes the same grey as the price cards above it, and the
   callout inside it goes white. Left as it is elsewhere, brand-tint on canvas
   is barely a shade apart and the callout showed as a left rule and nothing
   else. */
.landing-tinted .pay-terms { margin-top: 30px; }

@media (max-width: 900px) {
  .pricing-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}
@media (max-width: 560px) {
  .pricing-grid { grid-template-columns: minmax(0, 1fr); }
}

.landing-closing { background: var(--brand-tint); }
.landing-closing h2 { font-size: 1.9rem; margin-bottom: 10px; }

/* --- Published policies ------------------------------------------------------
   The four documents a card acquirer requires. One readable column - these are
   read start to finish, or jumped into at an anchor from the merchant
   application, and neither is helped by a page-wide measure. */
.legal { max-width: 780px; margin: 0 auto; padding: 48px 24px 64px; }

.legal-head { margin-bottom: 34px; }
.legal-head h1 { font-size: 2.1rem; letter-spacing: -0.02em; }
.legal-head .lede { font-size: 1.05rem; color: var(--ink-muted); margin-bottom: 12px; }

.legal-updated {
  display: inline-flex; align-items: center; gap: 7px; margin: 0;
  font-size: 0.82rem; color: var(--ink-faint);
}

/* Each section is a landmark somebody may have been sent straight to, so it
   gets a rule above it and enough room that an anchored jump does not leave the
   heading against the very top of the window. */
.legal-section {
  padding-top: 26px; margin-top: 26px;
  border-top: 1px solid var(--line);
  scroll-margin-top: 24px;
}
.legal-section:first-of-type { border-top: none; margin-top: 0; padding-top: 0; }
.legal-section h2 { font-size: 1.25rem; margin-bottom: 10px; }
.legal-section p { color: var(--ink-muted); line-height: 1.65; }
.legal-section p strong { color: var(--ink); }

.legal-list, .legal-steps { margin: 12px 0 14px; padding: 0; }
.legal-list { list-style: none; display: grid; gap: 8px; }
.legal-list li {
  display: flex; align-items: flex-start; gap: 10px;
  color: var(--ink-muted); line-height: 1.55;
}
.legal-list .icon { flex: none; margin-top: 0.25em; color: var(--brand); }

/* The steps of a card payment, numbered because the order is the point. */
.legal-steps { padding-left: 22px; display: grid; gap: 8px; color: var(--ink-muted); }
.legal-steps li { line-height: 1.55; padding-left: 4px; }

.legal .detail-meta { margin: 14px 0; }
.legal .table-wrap { margin: 16px 0; }
.legal .card-marks { margin: 14px 0; }

/* The other three documents, at the foot of whichever one is open. */
.legal-more { margin-top: 44px; padding-top: 24px; border-top: 1px solid var(--line); }
.legal-more h2 {
  font-size: 0.78rem; letter-spacing: 0.08em; text-transform: uppercase;
  color: var(--ink-faint); margin-bottom: 12px;
}

/* `.footer-nav` is the Resources column and rides along with these rules rather
   than copying them: it is the same row of icon-and-label links, and the two
   lists sit side by side in the footer where any drift between them shows. */
.legal-nav, .footer-nav {
  list-style: none; margin: 0; padding: 0;
  display: flex; flex-wrap: wrap; gap: 8px 20px; font-size: 0.88rem;
}
.legal-nav li, .footer-nav li { display: inline-flex; }
.legal-nav a, .legal-nav .is-current,
.footer-nav a { display: inline-flex; align-items: center; gap: 7px; }
.legal-nav .icon, .footer-nav .icon { color: var(--ink-faint); flex: none; }
/* The one being read is not a link to itself. */
.legal-nav .is-current { color: var(--ink); font-weight: 600; }
.legal-nav .is-current .icon { color: var(--brand); }

/* The merchant's own contact routes, as three targets rather than a paragraph
   of small print - a customer looking for a phone number should find it at a
   glance, which is the whole reason it is on the checklist. */
.contact-cards {
  display: grid; grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
  gap: 14px; margin: 18px 0;
}
.contact-card {
  display: grid; gap: 3px; padding: 16px;
  border: 1px solid var(--line); border-radius: var(--radius);
  background: var(--surface); color: var(--ink);
}
a.contact-card:hover { border-color: var(--brand); text-decoration: none; }
.contact-icon {
  display: inline-flex; align-items: center; justify-content: center;
  width: 30px; height: 30px; margin-bottom: 4px;
  border-radius: 9px; background: var(--brand-light); color: var(--brand);
}
.contact-label {
  font-size: 0.72rem; text-transform: uppercase; letter-spacing: 0.07em;
  color: var(--ink-faint); font-weight: 650;
}
.contact-card strong { word-break: break-word; }

/* --- The merchant footer -----------------------------------------------------
   Four columns above the copyright line: who we are, what we publish, what we
   have written, how to reach us. The first, second and fourth are checklist
   items, and a footer is where a customer looks for them without being told
   to. Resources is the third because it is the one column that is ours rather
   than the acquirer's, and it must not push the other three around. */
.landing-footer { background: var(--surface); border-top: 1px solid var(--line); }

.footer-main {
  max-width: 1120px; margin: 0 auto; padding: 40px 28px 8px;
  display: grid; grid-template-columns: 1.4fr 1fr 1.2fr; gap: 32px;
}

.footer-col h2 {
  font-size: 0.78rem; letter-spacing: 0.08em; text-transform: uppercase;
  color: var(--ink-faint); margin-bottom: 12px;
}
.footer-col .legal-nav { flex-direction: column; gap: 9px; }
/* The brand mark only. Written as a bare `img` this also caught the three card
   acceptance marks in the column beside it and drew each of them 150px wide,
   which is both wrong and, for a scheme mark, not permitted. */
.footer-brand .brand-logo { width: 150px; height: auto; opacity: 0.85; margin-bottom: 10px; }
.footer-brand p { color: var(--ink-muted); margin-bottom: 14px; max-width: 34ch; }

.footer-contact {
  list-style: none; margin: 0; padding: 0;
  display: grid; gap: 9px; font-size: 0.86rem; color: var(--ink-muted);
}
.footer-contact li { display: flex; align-items: flex-start; gap: 9px; }
.footer-contact .icon { flex: none; margin-top: 0.2em; color: var(--ink-faint); }

/* Ends apart on one line; both centred once they need two.

   `space-between` on a row that has wrapped leaves each line's single item hard
   against the left, which reads as two stray scraps rather than as a footer. So
   the fold is made explicit below the width where the two stop sharing a line -
   the currency notice is the longer of them in German, and it is what runs out
   of room first. */
.footer-base {
  max-width: 1120px; margin: 0 auto; padding: 24px 28px;
  border-top: 1px solid var(--line);
  display: flex; justify-content: space-between; align-items: center;
  gap: 12px 16px; flex-wrap: wrap;
  font-size: 0.86rem; color: var(--ink-muted);
}
.footer-base a { color: var(--ink-muted); }
.footer-base a:hover { color: var(--brand); }

@media (max-width: 860px) {
  .footer-main { grid-template-columns: 1fr 1fr; }
}
@media (max-width: 620px) {
  .footer-base { flex-direction: column; justify-content: center; text-align: center; }
}

/* The hero stacks first, because its two halves are the widest thing here;
   the card grids follow at the widths where their columns stop fitting. */
@media (max-width: 900px) {
  .landing-menus { padding-top: 48px; }
  .landing-menus h1 { font-size: 2.1rem; }
  .landing-menus-inner { grid-template-columns: minmax(0, 1fr); gap: 28px; }
  .landing-analytics { grid-template-columns: minmax(0, 1fr); gap: 20px; }
  .landing-analytics.is-flipped .landing-shot { order: 0; }
  .landing-analytics.is-flipped > div { position: static; }
  .landing-analytics .landing-shot { max-width: 600px; }
  .landing-features { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .landing-steps { grid-template-columns: minmax(0, 1fr); }
}
/* Five cells a row do not fit a phone, so each row becomes a card: its name as
   the card's title, then a line per column with that column's name above it.
   The header row goes, because each cell now says which column it is - and
   the ARIA roles in the markup keep a screen reader reading it as a table,
   which `display: block` alone would stop it doing in Safari.

   From 900px, with the page's other grids: at 760 the five columns held on
   down to 761px, and German ran to five lines a cell there with a word
   touching the table's edge. */
@media (max-width: 900px) {
  .compare, .compare tbody, .compare tr, .compare th, .compare td { display: block; }
  .compare { background: none; border: 0; box-shadow: none; }
  .compare thead { display: none; }
  .compare tbody { display: grid; gap: 12px; }
  .compare tbody tr {
    background: var(--canvas); border: 1px solid var(--line);
    border-radius: var(--radius); overflow: hidden; box-shadow: var(--shadow);
  }
  /* As specific as the desktop's rule between rows, which they replace: the
     cell's own line lost to its `border-top: 0`, and only the first card had
     its lines. */
  .compare tbody tr > .compare-row { padding: 14px 16px 10px; font-size: 1rem; border-top: 0; }
  .compare tbody tr > .compare-cell { padding: 10px 16px; border-top: 1px solid var(--line-soft); }
  .compare tbody tr > .compare-cell.is-ours { border-top-color: var(--brand-edge); }
  .compare-label {
    display: block; margin-bottom: 4px; font-size: 0.74rem; font-weight: 700;
    letter-spacing: 0.06em; text-transform: uppercase; color: var(--ink-faint);
  }
  .compare-cell.is-ours .compare-label { color: var(--brand); }
}
@media (max-width: 560px) {
  .landing-section { padding: 44px 20px; }
  .landing-features { grid-template-columns: minmax(0, 1fr); }
  .landing-actions { flex-direction: column; }
  .landing-actions .btn { width: 100%; justify-content: center; }
  .footer-main { grid-template-columns: 1fr; gap: 26px; padding: 32px 20px 8px; }
  .legal { padding: 32px 16px 48px; }
  .legal-head h1 { font-size: 1.7rem; }
}
