/* Our own changes on top of the Webflow export.
 *
 * Kept separate from inkara.css (the Webflow export's site stylesheet) so that re-exporting the site from
 * Webflow cannot silently drop them, and so "what have we changed since we left
 * Webflow" stays answerable by reading one short file.
 *
 * Loaded after the Webflow stylesheet on every page.
 */

/* Ink Press masthead.
 *
 * The exported <img> carries Webflow's default sizes="100vw". With w-descriptor
 * srcset that makes the browser lay the image out at the viewport width and
 * upscale to fill it — so a 512x193 file was being drawn at ~900px and looked
 * soft. Capping at the file's real width keeps it sharp.
 *
 * Replace this with a larger source image if the masthead should be bigger;
 * the constraint is the asset, not the layout.
 *
 * Desktop only. Below 992px the export sizes it as a percentage of the
 * container, which already lands at or under the file's real width — capping
 * there as well would override a deliberate responsive choice for no gain. */
@media screen and (min-width: 992px) {
  .image-6 {
    max-width: 512px;
  }
}

/* "Read more" hover.
 *
 * The export hovers these to #32343a, a dark grey that appears nowhere else in
 * the palette. Hovering to the same navy as the Contact button ties the two
 * together and keeps the page to its own colours.
 *
 * Uses the brand token rather than the literal #0b0d63 so the two buttons cannot
 * drift apart: .button-primary is background-color: var(--_colours---navy), and
 * this is the same value by reference, not by coincidence.
 *
 * The border matches the fill so the button reads as one solid navy shape —
 * left at #d3d3d3 it haloes the dark fill with a pale outline. */
.button-blog:hover {
  background-color: var(--_colours---navy);
  border-color: var(--_colours---navy);
  color: #fff;
}

/* Ink Press: even spacing around the featured article.
 *
 * The intro block sat 80px above the featured article while the featured article
 * sat 60px above the grid below it, so the page stepped unevenly down. The intro
 * carries 60px of its own padding plus the closing paragraph's 20px margin;
 * trimming the padding to 40px makes both gaps 60px, which is the separation the
 * rest of the page already uses.
 *
 * Scoped to this page. `.intro-div` is shared with the home, ISBN Emporium and
 * Marketing Studio pages, where the spacing is not in question —
 * `.blog-landing-section` appears on Ink Press alone. */
.blog-landing-section .intro-div {
  padding-bottom: 40px;
}

/* Pull quotes in Ink Press articles.
 *
 * The blockquote button in the dashboard's Ink Press editor writes a plain
 * <blockquote>, and Webflow's stylesheet renders that as its stock treatment: a
 * grey left border at 18px, SMALLER than the 22px body text around it. That is
 * the opposite of a pull quote — a sentence marked as worth lifting out would
 * have shrunk into the page.
 *
 * Restyled as an actual pull quote: larger, in navy, with a ruby quotation mark.
 * The mark is CSS rather than characters in the text, so the stored HTML stays
 * clean and the writer never has to type or delete it — the quotation is
 * presentation, and the sentence is the content.
 *
 * Scoped to the rich-text containers the post template uses, so it cannot reach
 * a blockquote on a hand-written page elsewhere on the site. */
.w-richtext blockquote,
.rich-text-block blockquote {
  position: relative;
  border-left: 0;
  margin: 32px 0;
  padding: 4px 0 4px 56px;
  font-family: 'EB Garamond', serif;
  font-size: 28px;
  line-height: 38px;
  font-style: italic;
  color: var(--_colours---navy);
}

.w-richtext blockquote::before,
.rich-text-block blockquote::before {
  content: "\201C";
  position: absolute;
  left: 0;
  top: 6px;
  font-family: 'EB Garamond', serif;
  font-size: 72px;
  line-height: 1;
  color: var(--_colours---ruby);
}

/* Closing mark. Inline after the last word rather than absolutely placed like
 * the opening one: the quote is any number of lines long, so the only reliable
 * place for it is wherever the text actually ends. line-height:0 keeps it from
 * stretching that final line, and the vertical-align sets it on the baseline
 * instead of floating it up. */
.w-richtext blockquote::after,
.rich-text-block blockquote::after {
  content: "\201D";
  font-family: 'EB Garamond', serif;
  font-size: 72px;
  line-height: 0;
  vertical-align: -0.38em;
  margin-left: 4px;
  color: var(--_colours---ruby);
}

/* One column below tablet: 56px of indent is a lot of a phone's width, and the
 * mark scales down with it. */
@media screen and (max-width: 767px) {
  .w-richtext blockquote,
  .rich-text-block blockquote {
    padding-left: 36px;
    font-size: 24px;
    line-height: 32px;
  }
  .w-richtext blockquote::before,
  .rich-text-block blockquote::before,
  .w-richtext blockquote::after,
  .rich-text-block blockquote::after {
    font-size: 54px;
  }
}

/* Text alignment in Ink Press articles.
 *
 * Quill records alignment as a class on the block — ql-align-center,
 * ql-align-right — and the API's sanitiser keeps `class` on p, h1-h5 and li
 * precisely so it survives. But those classes are defined in Quill's own
 * stylesheet, which is loaded by the DASHBOARD and not by the site, so without
 * these rules a centred heading saves correctly, previews correctly in the
 * editor, and publishes flush left with nothing to explain why.
 *
 * ql-align-justify is styled although the editor does not offer it: pasted
 * content can carry it, and a class the page ignores is the same silent
 * mismatch in a different direction.
 *
 * Left needs no rule — Quill writes no class for it, which is why '' is the
 * first option in the toolbar's align list. */
.w-richtext .ql-align-center,
.rich-text-block .ql-align-center { text-align: center; }

.w-richtext .ql-align-right,
.rich-text-block .ql-align-right { text-align: right; }

.w-richtext .ql-align-justify,
.rich-text-block .ql-align-justify { text-align: justify; }

/* The date at the foot of an Ink Press article.
 *
 * New: the Webflow template never printed one, and the date existed only to order
 * the index. It closes the article rather than heading it — provenance, not a
 * headline — so it sits below the body.
 *
 * Grey rather than the body's charcoal, because it is a fact about the article
 * rather than part of it. #6b6b6b holds 4.91:1 against the stone background, so
 * it still passes AA at this size; the obvious greys one shade lighter (#767676,
 * #8a8a8a) drop to 4.18 and 3.18 and fail. Not a palette token because the
 * palette has no grey — charcoal, navy, ruby, stone and white are all of it.
 */
.post-date {
  margin-top: 40px;
  /* PADDING, not margin. .blog-post-section has padding-bottom: 0 and the footer
   * begins immediately after it — measured gap before this: 0px — so a bottom
   * margin on the last child would collapse straight out of the section and
   * produce nothing. Padding cannot collapse.
   *
   * On .post-date rather than on the section so the two travel together: if the
   * date is ever dropped, the space it needed goes with it instead of leaving a
   * gap nobody can account for. */
  padding-bottom: 64px;
  font-family: 'EB Garamond', serif;
  font-size: 16px;
  color: #6b6b6b;
}

/* GEO questions and answers closing an Ink Press article (build-ink-press.py:
 * faq_html). Set apart from the body by a rule, since it is a summary of the
 * article rather than more of it; the headings and paragraphs inside keep the
 * article's own .w-richtext styles. */
.ink-faq {
  margin-top: 48px;
  padding-top: 32px;
  border-top: 1px solid rgba(0, 0, 0, 0.12);
}
.ink-faq h3 {
  margin-bottom: 6px;
}

/* About page: the image overlapped the footer divider.
 *
 * The export fixes .about-section at height: 80vh on desktop. The image column is
 * 50% of a container up to 1400px wide, so on a wide screen the image (~700px
 * square) is taller than 80vh and spills out of the section over the gradient
 * rule that opens the footer. min-height keeps the 80vh look on short content
 * and lets the section grow to fit the image; the padding gives it the same
 * breathing room below as above.
 *
 * Desktop only — below 992px the export already sets height: auto with its own
 * padding. */
@media screen and (min-width: 992px) {
  .about-section {
    height: auto;
    min-height: 80vh;
    padding-top: 60px;
    padding-bottom: 60px;
  }

  /* And the image itself is capped at 550px square (Mark, 2026-11-05). At 50% of a
   * 1400px container it reached ~680px and outweighed the copy beside it; 550 sits
   * level with the text block. The file is 1000x1000, so it stays sharp at 2x.
   * sizes matches, so the browser fetches the 800w/1000w files, not a 100vw guess. */
  /* Two equal columns with one 60px gap between them (Mark, 2026-11-05). The export
   * sized them 40% + 50% with space-between, so the spare 10% plus a 41px gap all
   * landed between the text and the image — ~120px of white at 1050px wide. Now the
   * columns split the row evenly, the text column drops its right padding so the gap
   * is exactly the gap, and on wide screens the capped pair is centred. */
  .about-section .about-flex-div {
    justify-content: center;
    column-gap: 60px;
  }
  .about-section .div-block-2 {
    flex: 1 1 0;
    width: auto;
    max-width: 620px;
    padding-right: 0;
  }
  .about-section .div-block-3 {
    flex: 1 1 0;
    width: auto;
    max-width: 550px;
  }
  /* min-width: 0 or a flex item will not shrink below its content — the image's
   * natural 550px — and the text column gets only what is left over. */
  .about-section .div-block-2,
  .about-section .div-block-3 {
    min-width: 0;
  }
  .about-section .div-block-3 img {
    display: block;
    width: 100%;
    max-width: 550px;
  }
}
