/* The second sheet, and the only one this repo edits.
 *
 * css/site.css is a byte-for-byte copy of the marketing site's, kept identical
 * so it can be re-copied and diffed rather than merged:
 *
 *     diff ../website/public/css/site.css public/css/site.css   # prints nothing
 *
 * Everything this page needs that the design system does not already have goes
 * here, and this sheet loads second so a plain rule here beats a plain rule
 * there. That ordering has a trap in it worth naming even though nothing here
 * springs it today: a plain rule in this sheet beats a media query in that one,
 * whatever the viewport is, so anything responsive copied down here has to
 * bring its own media query with it. The two-column footer rule was the one
 * example, and it went out with the footer on 6 September 2026.
 */

/* ---------- the form's frame ----------
   Tally draws the form inside their own iframe, and their embed script
   measures the content and writes the height onto the element as an inline
   style, which beats this rule and is meant to: the box then grows with the
   form instead of scrolling inside a fixed one.

   The 1200 here is what the page looks like when that script is blocked or
   fails, which is the same number the markup carries as a height attribute.
   It is deliberately taller than the form measures at desktop width (about
   1030px on the day it was written), because the failure to avoid is a form
   scrolling inside its own box: blank space under the last field costs
   nothing, a hidden submit button costs a signup. Remeasure it if fields are
   added, with the resizer disabled. The min-height stops a frame that has not
   loaded yet from collapsing the panel to nothing. */
.tally {
  display: block;
  width: 100%;
  height: 1200px;
  min-height: 520px;
  border: 0;
  background: transparent;
  color-scheme: light;
}
.panel-b > .tally + noscript { display: block; margin-top: var(--s2); }

/* ---------- the form's band ---------- */
.join-lede { max-width: 52ch; }

/* The panel is capped rather than filling the wrap, and centered inside it.
   Tally draw their inputs at a fixed narrow width and stretch only the text
   boxes, so a 1200px panel puts a 260px field in the corner of an acre of
   cream and reads as a broken layout. 760px is about the measure of the lede
   above it. Centred rather than left-aligned because the form is what the
   page is for: it is the one object here that does not line up with the type,
   which is what makes it read as the destination rather than another
   paragraph. Below 760px the cap does nothing, the auto margins collapse and
   the panel is the wrap. */
.join .panel { margin: var(--s4) auto 0; max-width: 760px; }

/* ---------- the cheer ----------
   site.css scopes the squash to .closing-mascot, which was the front page's
   waitlist band and does not exist on this site. The keyframe and the easing
   are still in that sheet; this points them at the drawing this page has. */
html.motion .hero-louie.is-cheering { animation: squash 0.62s var(--pop); }

/* ---------- the headings, given room to breathe ----------
   site.css caps a .head at 20ch, which is right on the marketing site where a
   band heading sits beside other things. Here the bands are wide and empty to
   the right of the text, so 20ch wraps a three-word line and leaves half the
   row blank. 34ch is two full lines at desktop, and balance stops the last
   line being one orphaned word. Both fall back to the site default on a phone,
   where the measure is the viewport rather than either number. */
.wrap > .head { max-width: 34ch; text-wrap: balance; }

/* ---------- the cards' heading, five pixels up ----------
   Taken out of the flow rather than out of the margin, so the cards below do
   not move with it. The band's padding is site.css's and is left alone. */
#what .head { position: relative; top: -5px; }

/* ---------- the one red word in the H1 ----------
   site.css paints it --crimson-deep, which is the darker red it uses for text
   on cream where a body-sized word has to hold contrast. Nothing else on this
   page is that red: the band, the button and the footer rule are all
   --crimson. At display size the lighter one holds up, so the page has one
   red rather than two that look like a mistake. */
.hero .d1 em { color: var(--crimson); }

/* ---------- the corner Louié ----------
   Fixed to the bottom right of the WINDOW, at every width, from the moment the
   page loads. There is no big drawing in the hero any more and no flight from
   one to the other: js/ride.js measured the hero stage, took it out of the
   flow, left a slot the same size behind and flew it down here on the page's
   own scroll. That whole file went on 6 September 2026 with the drawing it
   carried, and the classes it wrote (.hero-slot, .is-riding) went with it.

   .hero-stage is kept on the element for what site.css hangs off it: the bob,
   and the squash on .is-poked. The selector below is compound on purpose. That
   sheet sizes .hero-stage inside a max-width: 1080px query, and a media query
   over there beats a plain rule over here (see the header of this file), so a
   plain .corner-louie would lose its width on every laptop.

   Sized off the viewport so he is a corner ornament rather than a passenger:
   168px at the top of the range, 96px at the bottom of it.

   z-index 40 is the ride's old number, and it is the same job: over the bands,
   under nothing else on this page.

   He comes off below 1181px, which is the same width and the same reason as
   the marketing site's own corner companion: measured at 500px on 6 September
   2026 he stands 96px wide over a 410px form, so a quarter of every field is
   behind him for the length of the band a reader is meant to be typing into.
   Below that width there is no corner to spare. The three cards still carry a
   drawing each, so the character does not leave the page on a phone, he just
   stops standing on the form. */
.hero-stage.corner-louie {
  position: fixed;
  right: clamp(12px, 2.2vw, 32px);
  bottom: clamp(12px, 2.2vw, 32px);
  z-index: 40;
  width: clamp(96px, 12vw, 168px);
}
@media (max-width: 1180px) {
  .hero-stage.corner-louie { display: none; }
}

/* ---------- the cooking card is a portrait drawing ----------
   The three card drawings are the same character at the same size, and the
   eye reads that before it reads anything else, so a card whose art is a
   different shape has to be sized to match the others' Louié rather than
   their box. louie-pot.svg is 458 by 650 where the rest are 518 by 463: it
   carries the pot below him as well as the hat above. 458 / 518.42 is the
   width that puts him on the same scale as his neighbours, which is 133px
   against their 150 and 106 against their 120 on a phone.

   The card grows taller for it. That is the honest way round: shrinking the
   drawing to the height of the others would shrink him, and three Louiés at
   two sizes looks like a mistake where one taller card looks like a drawing
   with more in it.

   The three drawings then sit in a box the tallest one needs, aligned on
   their bottom edge, so the shadows under all three Louiés line up and the
   three headings start at the same height. Without that the middle heading
   sits fifty pixels below its neighbours. */
.card .louie-pot { width: 133px; }
.card .louie-md { height: 189px; object-fit: contain; object-position: left bottom; }
@media (max-width: 620px) {
  .card .louie-pot { width: 106px; }
  .card .louie-md { height: 150px; }
}

/* ---------- the headline breaks where it is told to ----------
   Cook with your / hands, not / your phone. Three lines, and the second one
   carries the crimson word on its own so the eye lands on it.

   site.css sizes the headline off `.hero .d1 { max-width: 13ch }` and lets it
   wrap wherever that lands, which is four lines with "not your" alone on the
   third. Spans set to block are the whole mechanism: the browser is not being
   asked to guess, and there is no <br> in the markup, so with this sheet gone
   the words still read as one sentence with ordinary spaces between them.

   The 13ch has to go with it. It is narrower than the longest of the three
   lines (14 characters), so left in place it would wrap the line it is meant
   to hold.

   It holds on the phone too. The three lines are the shape of the headline,
   not a wide-screen luxury, and letting them fall back to natural wrapping put
   "not your" up on the second line there and nowhere else.

   "Cook with your" is the long one: 6.74 times the font size, so 304px at the
   42px floor site.css sets, against a column of 100% - 40px. That fits every
   phone down to 344px wide, which is under every iPhone in service. Below that
   the floor comes off and the headline is sized off the viewport instead, so
   the line stays inside the column at 320 and narrower rather than pushing the
   page sideways. */
.hero .d1 { max-width: none; }
.hero .d1 .ln { display: block; }
@media (max-width: 343px) {
  .hero .d1 { font-size: 11.5vw; }
}

/* ---------- one centered column, all the way down ----------
   The page used to be built on two shapes at once: a hero split into a text
   column and a drawing column, and every heading and paragraph hard against
   the left edge of a band up to 1180px wide. Both cost the same thing. The
   headline had 596px to say a 615px line in, so it broke where the column
   said rather than where the sentence does, and the paragraphs ran short
   measures against acres of empty ground on their right.

   Everything is centered instead, in one column, and nothing is asked to fit a
   width it was not written for. Louié moves under the words rather than beside
   them, which is also the order somebody reads them in.

   site.css caps the measures already (.head at 20ch, .lede at 46ch) and those
   caps are what stop a centered line from stretching. All this adds is the auto
   margin that puts the cap in the middle of the band instead of on its left. */
.hero-grid {
  grid-template-columns: 1fr;
  justify-items: center;
  align-items: start;
  text-align: center;
  gap: 0;   /* the gap was the space between the two columns; the rows below
               set their own, and s5 between every line reads as four things
               rather than one hero. */
}
/* The text column is not a column any more: contents makes the headline, the
   lede and the button grid items in their own right, so the grid centres each
   of them rather than centering one block that then holds them left.

   It is matched by its own class rather than by "every div in the grid", which
   is what it said until 6 September 2026 and is a trap worth keeping written
   down: js/ride.js used to insert a second div here, .hero-slot, holding the
   space the hero drawing left when it took off, and the wildcard gave that one
   display:contents too. A slot with no box holds no space, so the hero
   collapsed and Louié drew over the band below it. The class is the fence. */
.hero-say { display: contents; }
.hero .d1 { margin-inline: auto; }
.hero .lede { margin-inline: auto; }
.hero-do { display: flex; justify-content: center; margin-top: var(--s3); }

.head, .lede { margin-inline: auto; }
#what .wrap, #join .wrap { text-align: center; }

/* The card keeps its drawing on the bottom edge of a shared box (see the
   cooking card above); centering only moves it sideways. */
.card { text-align: center; justify-items: center; }
.card .louie-md { object-position: center bottom; }

/* The form itself stays left inside the panel: Tally draws it, the address bar
   in the markup carries alignLeft=1, and a column of centered input boxes with
   centered labels over them is harder to fill in than one with a left edge to
   run down. The panel it sits in is what gets centered, and it is held to the
   width the fields were drawn for rather than the full band. */
.join .panel { max-width: 760px; margin-inline: auto; }

/* The panel's header strip holds one sentence and nothing else. site.css builds
   .panel-h as a flex row for a label and a right-hand figure, so a lone child
   sits against the left edge; this centres it over the form under it, which is
   the only band on the page where everything else is centered too. */
.join .panel .panel-h { justify-content: center; }

/* ---------- the small print under the form ----------
   Sits under the panel, not in it, and is deliberately quiet: it is read once
   by the person who wants to know where their address goes and never again by
   anybody. Capped near the lede's measure so the four sentences do not run the
   full width of a 1200px wrap, and centered to sit under a centered panel.

   Not a .note. That widget paints itself sand, which is this band's own
   background, so it would draw an outline around nothing. Plain type in the
   secondary ink is what the rest of the design system uses for small print. */
.join .privacy {
  margin: var(--s3) auto 0;
  max-width: 62ch;
  font-size: 15px;
  line-height: 1.55;
  color: var(--ink-2);
  text-align: center;
}
.join .privacy a { color: inherit; }
