/* The /integrations ingestion-methods section.
 *
 * Plain CSS, not Tailwind: public/assets/css/app.css is a frozen build, so a
 * NEW arbitrary utility (grid-cols-[1fr_2fr], w-[47%]) in this view renders as
 * nothing at all.
 *
 * The shape is the one the rest of the site now uses, lifted from
 * public/css/site-home.css: ONE plate cut into cells by hairlines rather than a
 * wall of free-standing cards, bordered medallions floated LEFT of the copy
 * they label, and a dot field on the tinted band. Three plates, because there
 * are three KINDS of answer here and eighteen identical cards would read as a
 * list rather than as a system.
 *
 * --brand-rgb is COMMA separated: rgba(var(--brand-rgb), .4). The slash form is
 * invalid for it and the whole declaration is dropped silently. The numbered
 * tokens (--brand-400-rgb) are space separated and want the slash form.
 *
 * The `ing-` prefix was grepped across public/css before it was used; nothing
 * else in the global class namespace claims it.
 */

.ing {
    --ing-line: #eef2f7;        /* the hairlines INSIDE a plate */
    --ing-edge: #e2e8f0;        /* the plate's own edge */
    position: relative;
}

/* The tinted band carries the dot field the marketing sections use, at the
   same 22px pitch. No mask-image on this layer: a radial fade erased every dot
   past the first few rows once, so the fade is done with the dot color. */
.ing-dots {
    position: absolute;
    inset: 0;
    pointer-events: none;
    background-image: radial-gradient(rgba(var(--brand-rgb), 0.16) 1.2px, transparent 1.2px);
    background-size: 22px 22px;
}

.ing-wrap { position: relative; z-index: 1; }

/* ---------------------------------------------------------------------------
 * The group rail. Three plates need three labels, and a second full
 * section-head over each one would be three headings in one section. A ruled
 * line with a number, a name and a count is the lighter form, and the numbers
 * are what make the section read in order.
 */
/* Wraps rather than overflows. At 375px "Provider And Host Guides" plus
   "Twelve Walkthroughs" is 491px of unbreakable content in a 343px column, and
   the count chip is the half that can take a second line: both labels stay on
   ONE line each, they just stop sharing a row. */
.ing-rail {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 8px 13px;
    margin-top: 26px;
}
.ing-rail:first-of-type { margin-top: 20px; }

.ing-n {
    font-family: inherit;
    font-size: 12.5px;
    font-weight: 800;
    letter-spacing: .1em;
    color: rgba(var(--brand-rgb), .5);
    white-space: nowrap;
}
.ing-rt {
    margin: 0;
    font-size: 12.5px;
    font-weight: 800;
    letter-spacing: .16em;
    text-transform: uppercase;
    color: #0b1220;
    white-space: nowrap;
}
.ing-rule {
    flex: 1;
    min-width: 12px;
    height: 1px;
    background: linear-gradient(90deg, rgba(var(--brand-rgb), .35), rgba(var(--brand-rgb), .06));
}
.ing-rc {
    flex: 0 0 auto;
    border: 1px solid rgba(var(--brand-rgb), .22);
    border-radius: 999px;
    background: #fff;
    padding: 4px 11px;
    font-size: 11px;
    font-weight: 700;
    letter-spacing: .04em;
    color: var(--brand);
    white-space: nowrap;
}

/* ---------------------------------------------------------------------------
 * The plate. One border, one radius, one shadow; the cells inside it carry no
 * ground of their own, which is what lets the plate's corners stay round
 * without overflow: hidden anywhere on the page.
 */
.ing-plate {
    margin-top: 10px;
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    border: 1px solid var(--ing-edge);
    border-radius: 20px;
    background: #fff;
    box-shadow: 0 20px 44px -34px rgb(15 23 42 / .5);
}

/* ---- Plate 1 + 2: the methods. Medallion left, copy right. ---------------- */
/* align-items: stretch, NOT flex-start. The copy column has to fill the cell
   for the link to be anchorable to its floor; left at flex-start, a three-line
   cell beside a four-line one left ~40px of empty plate under the shorter one,
   which is the short-column hole rather than spacing. */
.ing-cell {
    display: flex;
    align-items: stretch;
    gap: 16px;
    border-top: 1px solid var(--ing-line);
    padding: 18px 20px;
}
.ing-cell:first-child { border-top: 0; }

@media (min-width: 768px) {
    .ing-core, .ing-pair { grid-template-columns: repeat(2, minmax(0, 1fr)); }
    .ing-core > .ing-cell:nth-child(-n+2),
    .ing-pair > .ing-cell:nth-child(-n+2) { border-top: 0; }
    .ing-core > .ing-cell:nth-child(2n),
    .ing-pair > .ing-cell:nth-child(2n) { border-left: 1px solid var(--ing-line); }
}

/* R25: bordered on a light ground, every time, and floated LEFT of its copy.
   No bottom margin on it - a margin-bottom here would mean the card is a
   column and the medallion is sitting on top of its own heading. */
.ing-ic {
    display: inline-flex;
    flex: 0 0 46px;
    width: 46px;
    height: 46px;
    align-items: center;
    justify-content: center;
    align-self: flex-start;
    border: 1px solid var(--brand-100, #dbeafe);
    border-radius: 14px;
    background: var(--brand-50, #eff6ff);
    font-size: 17px;
    color: var(--brand);
    transition: background .2s, color .2s, border-color .2s;
}
.ing-cell:hover .ing-ic {
    border-color: var(--brand);
    background: var(--brand);
    color: #fff;
}

.ing-b { display: flex; flex-direction: column; min-width: 0; flex: 1; }

/* The pill wraps onto its own line before anything overflows. nowrap on the
   title alone put 259px of unbreakable content into a 235px cell at 375px and
   pushed 132px of horizontal scroll onto the whole page: nowrap ALONE just
   converts a wrap into an overflow, which is the worse failure. */
.ing-head {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 6px 10px;
}
.ing-ct {
    margin: 0;
    min-width: 0;
    font-size: 15.5px;
    font-weight: 700;
    color: #0b1220;
    white-space: nowrap;
}
/* One column, so the cell is narrow and the title is the longest thing in it.
   It is a card heading rather than a control label, so it may take two lines
   here; the badge beside it never does. */
@media (max-width: 767px) {
    .ing-ct { white-space: normal; }
}
/* It sits against the cell's right edge only at the widths where it CANNOT
   wrap. Pinned there at every width, the moment it took a line of its own it
   sat alone against the right margin under its title, which reads as a stray
   rather than as a badge. Below 1024 it follows the title instead. */
.ing-meta {
    flex: 0 0 auto;
    border: 1px solid var(--ing-edge);
    border-radius: 999px;
    background: #f8fafc;
    padding: 3px 10px;
    font-size: 11px;
    font-weight: 700;
    letter-spacing: .05em;
    text-transform: uppercase;
    color: #475569;
    white-space: nowrap;
}
@media (min-width: 1024px) {
    .ing-meta { margin-left: auto; }
}
.ing-cd {
    margin: 5px 0 0;
    font-size: 13.5px;
    line-height: 1.55;
    color: #475569;
}

/* Visible at rest. A "Learn More" that appears only under the pointer hides a
   link from everybody not already hovering the cell it is in. R15 case 1: an
   inline text link changes color, never gains a box. */
.ing-more {
    display: inline-flex;
    align-items: center;
    gap: 6px;
    /* Anchored to the cell's floor, so the slack in a short cell lands between
       the paragraph and the link where it reads as room, instead of pooling
       under the link as a hole in the plate. */
    margin-top: auto;
    /* A flex item blockifies, so without this the anchor box spans the whole
       copy column and the link's hit area is far wider than its words. */
    align-self: flex-start;
    padding-top: 10px;
    font-size: 12.5px;
    font-weight: 700;
    color: var(--brand);
    text-decoration: none;
    white-space: nowrap;
    transition: gap .2s, color .2s;
}
.ing-more i { font-size: 10px; }
.ing-more:hover, .ing-cell:hover .ing-more { gap: 10px; color: var(--brand-700, #1d4ed8); }
.ing-more:focus-visible {
    outline: 2px solid var(--brand);
    outline-offset: 3px;
    border-radius: 6px;
}

/* ---- Plate 3: the provider and host walkthroughs. ------------------------ *
 *
 * Twelve of them, so the count divides cleanly at every column count the page
 * resolves to: 1 at phone width, 2 from 640, 4 from 1024. No part-filled last
 * row at any width, which is the whole reason the generic IMAP walkthrough
 * sits in the grid rather than in a sentence underneath it.
 *
 * The hairlines are done by removing the first row's top edge and the first
 * column's left edge per breakpoint. Each block re-asserts both edges on every
 * chip first (:nth-child(n), same specificity, earlier in the block) so the
 * previous breakpoint's exemptions cannot leak into the next one.
 */
.ing-chip {
    display: flex;
    align-items: center;
    gap: 13px;
    padding: 13px 15px;
}
.ing-grid > .ing-chip { border-top: 1px solid var(--ing-line); border-left: 1px solid var(--ing-line); }
.ing-grid > .ing-chip:nth-child(-n+1) { border-top: 0; }
.ing-grid > .ing-chip:nth-child(1n+1) { border-left: 0; }

@media (min-width: 640px) {
    .ing-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
    .ing-grid > .ing-chip:nth-child(n) { border-top: 1px solid var(--ing-line); border-left: 1px solid var(--ing-line); }
    .ing-grid > .ing-chip:nth-child(-n+2) { border-top: 0; }
    .ing-grid > .ing-chip:nth-child(2n+1) { border-left: 0; }
}
@media (min-width: 1024px) {
    .ing-grid { grid-template-columns: repeat(4, minmax(0, 1fr)); }
    .ing-grid > .ing-chip:nth-child(n) { border-top: 1px solid var(--ing-line); border-left: 1px solid var(--ing-line); }
    .ing-grid > .ing-chip:nth-child(-n+4) { border-top: 0; }
    .ing-grid > .ing-chip:nth-child(4n+1) { border-left: 0; }
}

.ing-cic {
    display: inline-flex;
    flex: 0 0 38px;
    width: 38px;
    height: 38px;
    align-items: center;
    justify-content: center;
    border: 1px solid var(--brand-100, #dbeafe);
    border-radius: 14px;
    background: var(--brand-50, #eff6ff);
    font-size: 15px;
    color: var(--brand);
}
.ing-cb { min-width: 0; }
.ing-name {
    margin: 0;
    font-size: 13.5px;
    font-weight: 700;
    line-height: 1.25;
    color: #0b1220;
    white-space: nowrap;
}
.ing-tag {
    margin: 2px 0 0;
    font-size: 11.5px;
    font-weight: 600;
    line-height: 1.3;
    color: #64748b;
    white-space: nowrap;
}

/* The one honest line about where these walkthroughs live. They are in-product
   pages behind a login (routes/portal.php, the `verified` group), so nothing
   here links to one: a public page pointing at them would land a prospect on
   the sign-in screen. */
.ing-note {
    display: flex;
    align-items: flex-start;
    gap: 9px;
    margin: 12px 0 0;
    font-size: 12.5px;
    line-height: 1.6;
    color: #475569;
}
.ing-note i { margin-top: 3px; flex: 0 0 auto; color: var(--brand); font-size: 12px; }


/* R32: 12px type floor on a phone. The three small labels sit at 11 and 11.5
   on desktop, which is the scale the rest of the site uses; below that floor
   they trigger Safari's own text inflation, which then changes the layout that
   was measured. They step up rather than the whole scale moving. */
@media (max-width: 767px) {
    .ing-rc, .ing-meta, .ing-tag { font-size: 12px; }
}