/* College Chambers — structural styling.
 *
 * BRAND VALUES ARE NOT IN THIS FILE. Colours, fonts, the type scale and the
 * container width live in the Theme Studio theme (CollegeChambersThemeSeeder).
 * Everything here reads them through var(), so changing the brand colour in the
 * admin moves the whole site. A literal brand hex here would be a bug: it makes
 * the studio decorative and turns "change our blue" into a developer job.
 *
 * What belongs here is the structural half: proportions, spacing rhythm, and the
 * few treatments the block set has no field for. Every measurement was read off
 * the rendered legacy site, never eyedropped from a screenshot.
 *
 * SELECTORS ARE TAKEN FROM THE EMITTED DOM, not from the block names in the
 * admin. The two do not match: the Quote block renders
 * `blockquote.builder-quote > .builder-quote__text` with a `footer.builder-quote__cite`,
 * so a rule written against `.builder-quote cite` attaches to nothing and the
 * page looks unstyled for no visible reason. Read
 * `resources/views/frontend/partials/builder-blocks.blade.php` before adding to
 * this file.
 */

/* ── Type rhythm ──────────────────────────────────────────────────────────────
 * The heading face and its weight-400 setting are tokens. Live's headings are
 * set at normal tracking (measured): any added tracking widens every serif line
 * by about 2% and is enough to break names like "Carol Davies" onto two lines
 * on the people cards. Bootstrap gives a heading 8px beneath it.
 */
.builder-block__heading {
    margin-bottom: 8px;
}

/* ── Type ladder ──────────────────────────────────────────────────────────────
 * Live steps every size at its own breakpoints rather than holding one size:
 * body 16 / 18 at 768 / 20 at 1400 / 22 at 1600; h2 32 / 38 at 768 / 42 at
 * 1200; h3 20 / 25 at 992 / 28 at 1200 / 34 at 1400 / 36 at 1600; the banner
 * title 42 / 50 at 992 / 60 at 1200 / 65 at 1400 / 82 at 1600; and any other
 * h1 (a barrister's name) 40 / 45 at 992 / 52 at 1200 / 56 at 1400 / 62 at
 * 1600, both off the h1 token. The theme tokens hold the 1400px banner
 * values, so each step is a ratio of its token and a size change in Theme
 * Studio still moves every width.
 *
 * The body step scales the ROOT, not body, because core sets body and most
 * block text in rem: stepping body alone would leave them at 20px on a phone.
 */
:root {
    --cc-step-body: 0.8;
    --cc-step-banner: 0.646;
    --cc-step-h1: 0.615;
    --cc-step-h2: 0.762;
    --cc-step-h3: 0.588;
}

@media (min-width: 768px)  { :root { --cc-step-body: 0.9; --cc-step-h2: 0.905; } }
@media (min-width: 992px)  { :root { --cc-step-banner: 0.769; --cc-step-h1: 0.692; --cc-step-h3: 0.735; } }
@media (min-width: 1200px) { :root { --cc-step-banner: 0.923; --cc-step-h1: 0.8; --cc-step-h2: 1; --cc-step-h3: 0.824; } }
@media (min-width: 1400px) { :root { --cc-step-body: 1; --cc-step-banner: 1; --cc-step-h1: 0.862; --cc-step-h3: 1; } }
@media (min-width: 1600px) { :root { --cc-step-body: 1.1; --cc-step-banner: 1.262; --cc-step-h1: 0.954; --cc-step-h3: 1.059; } }

html {
    font-size: calc(var(--font-size-base, 20px) * var(--cc-step-body));
}

h1 {
    font-size: calc(var(--font-size-h1, 65px) * var(--cc-step-h1));
}

h2,
.page-body .cms-content h2 {
    font-size: calc(var(--font-size-h2, 42px) * var(--cc-step-h2));
}

h3,
.page-body .cms-content h3 {
    font-size: calc(var(--font-size-h3, 34px) * var(--cc-step-h3));
}

.page-body-heading h1 {
    font-size: calc(var(--font-size-h1, 65px) * var(--cc-step-banner));
}

/* ── Container ────────────────────────────────────────────────────────────────
 * Live is Bootstrap: a 12px gutter and a column that steps at each breakpoint
 * instead of filling the screen, so at a 1366 laptop the copy is 1116px wide,
 * not 1316. --cc-col is that column, gutters excluded. The theme's container
 * width is the 1400px step (live 1316, within 4px); 1600 widens it by live's
 * 200px. Anything bled to the screen edge puts its content back on the page
 * with max(12px, calc(50% - var(--cc-col) / 2)), never with the theme token,
 * which is right at one width only.
 */
:root { --cc-col: 100vw; }

@media (min-width: 576px)  { :root { --cc-col: 516px; } }
@media (min-width: 768px)  { :root { --cc-col: 696px; } }
@media (min-width: 992px)  { :root { --cc-col: 936px; } }
@media (min-width: 1200px) { :root { --cc-col: 1116px; } }
@media (min-width: 1400px) { :root { --cc-col: var(--container-width, 1320px); } }
@media (min-width: 1600px) { :root { --cc-col: calc(var(--container-width, 1320px) + 200px); } }

.container {
    max-width: calc(var(--cc-col) + 24px);
    padding-inline: 12px;
}

/* ── Links in copy ────────────────────────────────────────────────────────────
 * Live underlines every link in running text and drops the underline on hover
 * (screen.css). Without it a link in navy copy is indistinguishable from the
 * words around it. Scoped to written content so nav, buttons, cards and the
 * gold-rule links keep their own treatment.
 */
/* :where() keeps this at the weight of `.cms-content a`, so any page or
 * component rule that takes the underline off (live's .noUnderline links on
 * the contact page) wins without an arms race of selectors. */
.cms-content a:where(:not(.btn):not([class*="button"])) {
    text-decoration: underline;
}

.cms-content a:where(:not(.btn):not([class*="button"])):hover {
    text-decoration: none;
}

/* ── Copy: line height and lists ──────────────────────────────────────────────
 * Core sets written content at 1.7; live's copy is the body's 1.636, which the
 * theme already carries as its body line height, and paragraphs are Bootstrap's
 * 16px apart at every width. Lists are Bootstrap's too: a 32px indent, no space
 * between items, 16px under the list, and a disc in the text colour. Only a
 * barrister's bio differs (.bio-caption-left on live): a 1em indent and the disc
 * in the secondary colour, the one touch of gold in a page of navy copy.
 */
.page-body .cms-content {
    line-height: var(--lh-body, 1.64);
}

.cms-content p {
    margin-bottom: 16px;
}

.page-body .cms-content ul,
.page-body .cms-content ol {
    margin: 0 0 16px;
    padding-left: 32px;
}

.page-body .cms-content li {
    margin-bottom: 0;
}

.page-body .cc-profile-lead__bio ul,
.page-body .cc-profile-lead__bio ol {
    padding-left: 1em;
}

.page-body .cc-profile-lead__bio li::marker {
    color: var(--color-secondary);
}

/* ── Dividers ─────────────────────────────────────────────────────────────────
 * Live's rule is Bootstrap's hr inside the copy: 1px of the text colour at 25%
 * opacity with 16px either side. Here it is a divider block between two text
 * blocks, so it inherits the block gap twice over plus its own inline margin,
 * about 70px a side. The gap is taken off both neighbours, and the margin
 * needs !important because the block writes it inline. The colour is replaced
 * only while it is the block's default grey, so a colour an editor picks wins.
 */
.builder-block:has(+ .builder-block--spacer > .builder-divider),
.builder-block--spacer:has(> .builder-divider) {
    margin-bottom: 0;
}

.builder-block--spacer > .builder-divider {
    margin: 16px 0 !important;
}

.builder-block--spacer > .builder-divider[style*="#dddddd"] {
    border-top-color: var(--color-text, var(--color-primary)) !important;
    opacity: 0.25;
}

/* Newer core prints no colour for a default divider and reads --divider-color
   instead, so the rule above stops matching it. This one covers that markup; an
   editor's own colour is written as --divider-color on the divider and is left
   alone. Both rules are load-bearing while core may still write `#dddddd`
   inline; delete the one above once it no longer does. */
.builder-block--spacer > .builder-divider:not([style*="--divider-color"]) {
    --divider-color: var(--color-text, var(--color-primary));
    opacity: 0.25;
}

/* The same rule where it sits inside written copy, as the policy pages carry
 * it, in place of the browser's grey inset line. */
.cms-content hr {
    height: 0;
    margin: 16px 0;
    border: 0;
    border-top: 1px solid var(--color-text, var(--color-primary));
    opacity: 0.25;
}

/* The wordmark is set noticeably wider than anything else, measured at roughly
 * 0.08em on the legacy header lockup. */
.site-header .site-name a {
    font-family: var(--font-h1, inherit);
    font-weight: 400;
    letter-spacing: 0.08em;
    text-transform: uppercase;
}

/* ── Quote treatment ──────────────────────────────────────────────────────────
 * Live draws every recommendation one way (.quote-text): a large serif mark in
 * the flow at the left, at full strength in the text colour, the quotation
 * beside it in the display face on the quotation ramp (--cc-quote-size, below)
 * and in straight double quotes, and the source under it in bold on a gold
 * rule. The default and centred styles both take it; core's card style keeps
 * its own. Core's centred style is unset rather than overridden piecemeal,
 * because a centred quotation is a different device, not a variant of this.
 */
.builder-quote--default,
.builder-quote--centred {
    display: grid;
    grid-template-columns: auto minmax(0, 1fr);
    align-content: start;
    margin: 0;
    padding: 0;
    border: 0;
    text-align: left;
    color: var(--color-h2, var(--color-primary));
}

.builder-quote--default::before,
.builder-quote--centred::before {
    content: "\201C";
    grid-column: 1;
    grid-row: 1 / span 2;
    font-family: var(--font-h1, Georgia, serif);
    font-size: 72px;
    line-height: 1;
    padding-right: 16px;
    margin-left: -0.1em;
}

@media (min-width: 992px) {
    .builder-quote--default::before,
    .builder-quote--centred::before { font-size: 102px; }
}

.builder-quote--default > *,
.builder-quote--centred > * {
    grid-column: 2;
}

/* The quotation is upright in the display face. Core italicises it; live does
 * not, and at this size italic serif reads as decorative rather than
 * authoritative. The straight quotes are live's own characters; the importer
 * strips them from the text, so they are drawn back here. */
.builder-quote__text {
    font-family: var(--font-h1, inherit);
    font-style: normal;
    font-weight: 400;
    font-size: var(--cc-quote-size);
    line-height: 1.556;
    margin: 0;
    padding-bottom: 20px;
    quotes: '"' '"';
}

.builder-quote__text::before { content: open-quote; }
.builder-quote__text::after { content: close-quote; }

/* live's .link: the gold rule under the source is the only place the
 * secondary colour appears at any real size on the legacy site. */
.builder-quote__cite {
    justify-self: start;
    color: inherit;
    font-size: 1rem;
}

.builder-quote__cite cite {
    display: inline-block;
    padding: 10px 0;
    border-bottom: 2px solid var(--color-secondary);
    color: inherit;
    font-weight: 700;
    letter-spacing: normal;
}

/* ── Lead quote ───────────────────────────────────────────────────────────────
 * The Legal 500 recommendation that opens the people index. A different figure
 * from the Quote block above: live sets the mark in the flow to the left of the
 * text, at full strength and much larger, so it is styled here rather than by
 * bending .builder-quote — the two want opposite ::before behaviour.
 *
 * Colour sits on the wrapper so the mark and the words cannot drift apart.
 *
 * Live's type ramp (.quote-text h4) is 24px, 28px at 576, 30px at 1200, 32px
 * at 1400 and 36px at 1600, held in --cc-quote-size because the quotation
 * beside a barrister's bio is the same element on live and steps the same way.
 * Stated per breakpoint rather than as a clamp: a clamp in rem drifts with the
 * root size, which itself steps. The mark's two sizes are literal, because
 * 72 → 102 is a step, not a ramp.
 */
:root { --cc-quote-size: 24px; }

@media (min-width: 576px)  { :root { --cc-quote-size: 28px; } }
@media (min-width: 1200px) { :root { --cc-quote-size: 30px; } }
@media (min-width: 1400px) { :root { --cc-quote-size: 32px; } }
@media (min-width: 1600px) { :root { --cc-quote-size: 36px; } }

/* 80px to the search row at every width, and 28px under the words (the h4's
 * 20px padding and the 8px its wrapper adds), both measured off live. */
.cc-lead-quote {
    display: flex;
    align-items: flex-start;
    margin: 0 0 80px;
    color: var(--color-h2, var(--color-primary));
}

.cc-lead-quote__mark {
    flex: none;
    font-family: var(--font-h1, Georgia, serif);
    font-size: 72px;
    line-height: 1;
    margin-left: -0.1em;
    padding-right: 16px;
}

@media (min-width: 992px) {
    .cc-lead-quote__mark {
        font-size: 102px;
    }
}

.cc-lead-quote__text {
    margin: 0;
    font-family: var(--font-h1, inherit);
    font-weight: 400;
    font-size: var(--cc-quote-size);
    line-height: 1.556;
    padding-bottom: 28px;
}

/* ── About page ───────────────────────────────────────────────────────────────
 * about.php is one Bootstrap row: History in col-md-4 beside a client's words
 * in col-md-8, then Services across the full width, then the Legal 500
 * recommendations two to a row (col-md-6). Here those are sibling blocks with
 * no wrapper, so the row is the page container itself, made a grid only where
 * it holds the History block. The first recommendation carries the set's
 * heading inside it, so that block alone is display: contents, which lets the
 * heading span the row while its quotation takes a cell like the rest. The
 * classes are the Design-tab ones chambers:import writes; clearing one puts
 * that block back in the ordinary column.
 */
@media (min-width: 768px) {
    .page-body > .container:has(> .cc-history) {
        display: grid;
        grid-template-columns: repeat(12, minmax(0, 1fr));
        column-gap: 24px;
        align-items: start;
    }

    .page-body > .container:has(> .cc-history) > * {
        grid-column: 1 / -1;
    }

    .page-body > .container:has(> .cc-history) > .cc-history {
        grid-column: span 4;
    }

    .page-body > .container:has(> .cc-history) > .cc-history-quote {
        grid-column: span 8;
    }

    .page-body > .container:has(> .cc-history) > .cc-recommendation {
        grid-column: span 6;
    }

    .page-body > .container:has(> .cc-history) > .cc-recommendation:has(> .builder-block__heading) {
        display: contents;
    }

    .cc-recommendation > .builder-block__heading {
        grid-column: 1 / -1;
    }

    .cc-recommendation > .builder-quote {
        grid-column: span 6;
    }
}

/* "Services" is live's .title-1, the h1 ladder rather than an h2, so it
 * stands larger than History above it. It is the page's one other text block. */
.page-body > .container:has(> .cc-history) > .builder-block--text:not(.cc-history) > .builder-block__heading {
    font-size: calc(var(--font-size-h1, 65px) * var(--cc-step-h1));
}

/* Live's col-md-6 pt-5 pb-lg-4 around each recommendation. On the quotation
 * rather than the block so the one inside the heading's block gets it too. */
.cc-recommendation {
    margin-bottom: 0;
}

.cc-recommendation > .builder-quote {
    padding-top: 48px;
}

@media (min-width: 992px) {
    .cc-recommendation > .builder-quote { padding-bottom: 24px; }
}

.cc-recommendation > .builder-block__heading {
    margin: 0;
}

/* The client's words beside History: the same quotation figure as above, on a
 * testimonial card instead of a Quote block, so the card's chrome comes off
 * and core's own curly quotes (bare text nodes, see the quote band) are
 * collapsed the same way. Live prints the words alone here, with no name, and
 * indents the column by Bootstrap's ps-xl-4 and ps-xxl-5. */
.cc-history-quote .content-section {
    border-top: 0;
    padding: 0;
}

.cc-history-quote .content-section > .container {
    max-width: none;
    padding: 0;
}

.cc-history-quote .testimonial-card {
    display: grid;
    grid-template-columns: auto minmax(0, 1fr);
    align-content: start;
    margin: 0;
    padding: 4px 0 0;
    border: 0;
    border-radius: 0;
    background: none;
    box-shadow: none;
    color: var(--color-h2, var(--color-primary));
}

.cc-history-quote .testimonial-card::before {
    content: "\201C";
    grid-column: 1;
    font-family: var(--font-h1, Georgia, serif);
    font-size: 72px;
    line-height: 1;
    padding-right: 16px;
    margin-left: -0.1em;
}

@media (min-width: 992px) { .cc-history-quote .testimonial-card::before { font-size: 102px; } }

.cc-history-quote .testimonial-card > * {
    grid-column: 2;
}

.cc-history-quote .quote {
    font-size: 0;
    font-style: normal;
    margin: 0;
    color: inherit;
}

.cc-history-quote .quote > * {
    font-family: var(--font-h1, inherit);
    font-size: var(--cc-quote-size);
    line-height: 1.556;
    color: inherit;
    margin: 0 0 20px;
}

.cc-history-quote .author {
    display: none;
}

@media (min-width: 1200px) { .cc-history-quote { padding-left: 24px; } }
@media (min-width: 1400px) { .cc-history-quote { padding-left: 48px; } }

/* ── Practice-area and ADR pages: one passage, several blocks ─────────────────
 * Live's "How we can help" is one passage: a sentence, a two-column list, a
 * closing line, spaced only by their own paragraph margins. The importer
 * builds it as a text block, a Two Column block (from the legacy row markup)
 * and another text block, and core puts its block gap between each, about
 * 50px apiece. The gaps close where a text and a two-column block meet, and
 * the two lists stack with no gap between them on a phone, as live's
 * col-md-6 pair does.
 */
body[data-path^="expertise/"] .builder-block--text:has(+ .builder-block--two_column),
body[data-path^="expertise/"] .builder-block--two_column:has(+ .builder-block--text),
body[data-path^="adr/"] .builder-block--text:has(+ .builder-block--two_column),
body[data-path^="adr/"] .builder-block--two_column:has(+ .builder-block--text) {
    margin-bottom: 0;
}

body[data-path^="expertise/"] .builder-block--two_column .content-row-grid,
body[data-path^="adr/"] .builder-block--two_column .content-row-grid {
    gap: 0 24px;
}

/* The same on the Private Dispute Resolution page, where the passage is copy
 * then two runs of questions: live's accordion follows the last paragraph's
 * own margin, and the heading between the runs carries the 30px it was given
 * inline in the legacy copy. */
body[data-path^="adr/"] .builder-block--text:has(+ .builder-block--accordion),
body[data-path^="adr/"] .builder-block--accordion:has(+ .builder-block--accordion) {
    margin-bottom: 0;
}

body[data-path^="adr/"] .builder-block--accordion + .builder-block--accordion > .builder-block__heading {
    margin-top: 30px;
}

/* ── Contact page ─────────────────────────────────────────────────────────────
 * Live's contact.php: col-md-5 for the details and col-md-7 for the directions,
 * a bold label over each, and the details set large (26px from 1200, 32px from
 * 1400) where every other page sets them at body size. The labels are a
 * two-column block an editor added on staging; it and the accordion take the
 * same 5/7 split so each label sits over its own column, and the labels are
 * drawn as live's bold body-face lines rather than as section headings.
 */
@media (min-width: 769px) {
    body[data-path="contact"] .builder-accordion-row,
    body[data-path="contact"] .builder-block--two_column .content-row-grid {
        grid-template-columns: minmax(0, 5fr) minmax(0, 7fr);
        gap: 24px;
    }
}

/* live's details are bold links with no underline (.noUnderline), and the
 * address block sits pt-5 under them. */
body[data-path="contact"] .builder-accordion__intro a {
    text-decoration: none;
}

/* Live's details open straight under the banner, with no section step above
 * them, and the labels sit pt-2 over their columns. */
body[data-path="contact"] .page-body-heading ~ .page-body {
    padding-top: 0;
}

body[data-path="contact"] .builder-block--two_column:first-child {
    margin-bottom: 24px;
}

/* Stacked on a phone, the label row would put "Directions" above the phone
 * numbers, two blocks away from the accordion it names. Live sets it just
 * above the accordion; a label row cannot follow it there, so on a phone the
 * row keeps only "Contact Us". */
@media (max-width: 768px) {
    body[data-path="contact"] .builder-block--two_column:first-child .content-row-grid > :last-child {
        display: none;
    }
}

body[data-path="contact"] .builder-accordion__intro > div + div {
    margin-top: 64px;
}

body[data-path="contact"] .builder-block--two_column h3 {
    margin: 0;
    font-family: var(--font-family, inherit);
    font-size: 1rem;
    font-weight: 700;
    letter-spacing: normal;
    line-height: var(--lh-body, 1.64);
}

@media (min-width: 1200px) {
    body[data-path="contact"] .builder-accordion__intro > div > div { font-size: 26px; }
}

@media (min-width: 1400px) {
    body[data-path="contact"] .builder-accordion__intro > div > div { font-size: 32px; }
}

/* ── Legacy grid classes in copy ──────────────────────────────────────────────
 * One piece of imported copy, the About page's services list, carries live's
 * own Bootstrap row and col-md-6 around its two lists. This site loads no
 * Bootstrap, so without these the lists stack into one long column. Only the
 * classes the import actually contains, at Bootstrap's own values.
 */
.cms-content .row {
    display: flex;
    flex-wrap: wrap;
    margin-inline: -12px;
}

.cms-content .row > [class*="col-"] {
    flex: 0 0 100%;
    max-width: 100%;
    padding-inline: 12px;
}

@media (min-width: 768px) {
    .cms-content .row > .col-md-6 { flex-basis: 50%; max-width: 50%; }
}

.cms-content .mt-3 { margin-top: 16px; }

@media (min-width: 992px) {
    .cms-content .mt-lg-4 { margin-top: 24px; }
}

/* ── Body copy in narrow columns ──────────────────────────────────────────────
 * The legacy site justifies text in narrow columns, which produces rivers at
 * this measure. Left-aligned deliberately. Recorded here rather than left
 * silent, because it IS a visible difference from the old site and someone will
 * eventually ask why.
 */
.builder-block--two_column p,
.builder-block--three_column p,
.builder-block--four_column p {
    text-align: left;
    hyphens: auto;
}

/* ── Focus visibility ─────────────────────────────────────────────────────────
 * The legacy site suppressed focus outlines. Not reproduced: it fails WCAG 2.4.7
 * and this is a public-facing professional-services site. Drawn in the brand
 * colour so it belongs, rather than reinstating the browser default.
 */
a:focus-visible,
button:focus-visible,
input:focus-visible,
select:focus-visible,
textarea:focus-visible,
summary:focus-visible {
    outline: 2px solid var(--color-primary);
    outline-offset: 2px;
}

/* ── Header ───────────────────────────────────────────────────────────────────
 * The live header, one row: logo lockup left (wordmark image over the
 * "Barristers - Mediators - Arbitrators" tags), the main nav right with the
 * clerks' number as its last item. The two wrap onto separate rows where they
 * do not fit side by side, which on live is everything under roughly 1700px:
 * at 1440 the nav sits on a second row under the logo, exactly as the capture
 * shows. Every step below (logo width, nav size, gaps, gutters) is the legacy
 * stylesheet's own breakpoint ladder: 992 / 1200 / 1400 / 1600.
 *
 * The header keeps its own fluid container (live: max 1758px with 24px
 * gutters) rather than the theme's content width, because on live the header
 * is wider than the copy beneath it and the logo sits nearer the viewport edge.
 *
 * Live positions the header absolutely over the banner. Here it stays in
 * normal flow and paints the same wash as the title band under it, so the two
 * read as one banner without every template having to reserve the header's
 * height (the first one that did not would render underneath it).
 *
 * The wash is the theme's alt background (Theme Studio "Alternate background",
 * measured off live's inner banner at its edge) lightened towards white at the
 * centre, which is how live draws it: a radial wash from #f5f8f8 in the middle
 * to #e9f8f8 at the edges. One token, so the tint stays the admin's to change.
 */
:root {
    --cc-banner-wash: radial-gradient(circle, color-mix(in srgb, var(--color-bg-alt, #e9f8f8) 45%, #fff) 0%, var(--color-bg-alt, #e9f8f8) 100%);
}

.cc-header {
    background: var(--cc-banner-wash);
    border-bottom: 0;
    padding: 24px 0 0;
}

@media (min-width: 1400px) { .cc-header { padding-top: 34px; } }
@media (min-width: 1600px) { .cc-header { padding-top: 48px; } }

.cc-header__inner {
    position: relative;
    width: 100%;
    max-width: 1758px;
    margin: 0 auto;
    padding: 0 12px;
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: space-between;
}

@media (min-width: 992px) { .cc-header__inner { padding: 0 24px; } }

/* The lockup: image over the tags, the whole thing the way home. It sits
 * above the phone menu overlay (z-index) so the wordmark stays visible while
 * the menu is open, as on live. */
.cc-header__brand {
    position: relative;
    z-index: 1001;
    padding: 12px 0;
    max-width: calc(100% - 60px);
}

.cc-header__logo {
    display: block;
    max-width: 260px;
    color: var(--color-primary);
    text-decoration: none;
}

@media (min-width: 1200px) { .cc-header__logo { max-width: 320px; } }
@media (min-width: 1400px) { .cc-header__logo { max-width: 420px; } }
@media (min-width: 1600px) { .cc-header__logo { max-width: 500px; } }

.cc-header__logo img {
    display: block;
    width: 100%;
    height: auto;
}

/* The tags, centred under the wordmark, a hyphen between each. Sized off the
 * body size token: 16px at the reference width is 0.8 of live's 20px body. */
.cc-header__tags {
    display: flex;
    justify-content: center;
    gap: 10px;
    font-size: calc(var(--font-size-base, 20px) * 0.6);
    line-height: 1.64;
}

@media (min-width: 1200px) { .cc-header__tags { font-size: calc(var(--font-size-base, 20px) * 0.7); } }
@media (min-width: 1400px) { .cc-header__tags { font-size: calc(var(--font-size-base, 20px) * 0.8); } }
@media (min-width: 1600px) { .cc-header__tags { font-size: calc(var(--font-size-base, 20px) * 0.9); } }

/* ── Nav ──────────────────────────────────────────────────────────────────────
 * Renders inside the header (overrides/header.blade.php). Plain navy text on
 * the wash, gold on hover, no bar and no boxes. Core's nav rules paint a dark
 * bar with padded, filled links, and each of those is unset here rather than
 * merely recoloured: the theme's white-on-white tokens only hide them until
 * someone changes a token.
 *
 * Every measurement is live's own: Lato (the theme's nav font), weight 400
 * with the phone at 900, sizes 16 / 18 / 20 / 22px up the ladder with 20px as
 * the token's reference value, 10px vertical padding, line-height 1.34, no
 * letter-spacing. The gaps are live's flex gaps LESS 10px: its links carry a
 * -5px side margin (screen.css) that the visible spacing on the capture
 * confirms, so 16 / 20 / 32 / 40 render as 6 / 10 / 22 / 30.
 */
.cc-nav {
    background: transparent;
}

.cc-nav .nav-main {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 0 6px;
    margin: 0;
    padding: 0;
    list-style: none;
}

@media (min-width: 1200px) { .cc-nav .nav-main { gap: 0 10px; } }
@media (min-width: 1400px) { .cc-nav .nav-main { gap: 0 22px; } }
@media (min-width: 1600px) { .cc-nav .nav-main { gap: 0 30px; } }

/* The second row is stated rather than left to the wrap. Live's nav is about
 * 30px wider than this one, so left to fit, this one squeezes beside the logo
 * from 1400 to 1599 where live's never does. Live joins the rows at 1700. */
@media (min-width: 769px) and (max-width: 1699.98px) {
    .cc-nav { flex-basis: 100%; }
}

.cc-nav .nav-item > a,
.cc-nav .nav-heading > .nav-label {
    padding: 10px 0;
    background: none;
    color: var(--nav-link-color, var(--color-primary));
    font-family: var(--font-nav, inherit);
    font-size: calc(var(--nav-link-size, 20px) * 0.8);
    font-weight: 400;
    letter-spacing: normal;
    line-height: 1.34;
    white-space: nowrap;
    transition: color 0.32s ease-in-out;
}

@media (min-width: 1200px) {
    .cc-nav .nav-item > a,
    .cc-nav .nav-heading > .nav-label { font-size: calc(var(--nav-link-size, 20px) * 0.9); }
}

@media (min-width: 1400px) {
    .cc-nav .nav-item > a,
    .cc-nav .nav-heading > .nav-label { font-size: var(--nav-link-size, 20px); }
}

@media (min-width: 1600px) {
    .cc-nav .nav-item > a,
    .cc-nav .nav-heading > .nav-label { font-size: calc(var(--nav-link-size, 20px) * 1.1); }
}

/* Live marks no current page (the theme's active colour is set to the link
 * colour to match); hover is the only state. Hover sits after active so a
 * hovered current item still goes gold. */
.cc-nav .nav-item.active > a {
    background: none;
    color: var(--nav-active-color, var(--nav-link-color, var(--color-primary)));
}

.cc-nav .nav-item > a:hover,
.cc-nav .nav-item > a:focus-visible,
.cc-nav .nav-item:focus-within > a,
.cc-nav .nav-heading:hover > .nav-label,
.cc-nav .nav-heading:focus-within > .nav-label {
    background: none;
    color: var(--nav-hover-color, var(--color-secondary));
}

/* The clerks' number, the nav's last item, is the one heavy weight on live. */
.cc-nav .cc-nav__phone > a {
    font-weight: 900;
}

/* Desktop dropdowns: live's 240px white card, 4px radius, 12px vertical
 * padding and a soft shadow; the links stacked at weight 400, line-height 1,
 * 10px vertical padding, with the side padding and size climbing the ladder
 * (10px / 15px, then 20px / 16px, then 30px / 18px). */
@media (min-width: 769px) {
    .cc-nav .nav-sub {
        top: 100%;
        left: 0;
        min-width: 100%;
        width: 240px;
        padding: 12px 0;
        background: var(--nav-dropdown-bg, #fff);
        border-radius: 4px;
        box-shadow: 0 6px 10px 0 rgba(0, 0, 0, 0.12);
    }

    .cc-nav .nav-sub a {
        display: block;
        padding: 10px;
        background: none;
        border: 0;
        color: var(--nav-dropdown-color, var(--color-primary));
        font-family: var(--font-nav, inherit);
        font-size: calc(var(--nav-link-size, 20px) * 0.75);
        font-weight: 400;
        letter-spacing: normal;
        line-height: 1;
        transition: color 0.32s ease-in-out;
    }

    .cc-nav .nav-sub a:hover,
    .cc-nav .nav-sub a:focus-visible {
        background: none;
        color: var(--nav-hover-color, var(--color-secondary));
    }
}

@media (min-width: 1200px) {
    .cc-nav .nav-sub a { padding: 10px 20px; font-size: calc(var(--nav-link-size, 20px) * 0.8); }
}

@media (min-width: 1400px) {
    .cc-nav .nav-sub a { padding: 10px 30px; font-size: calc(var(--nav-link-size, 20px) * 0.9); }
}

/* ── Nav: phones ──────────────────────────────────────────────────────────────
 * Live hides the menu behind a 32px hamburger at the right of the header and
 * opens it as a full-screen wash that scales up and fades in, the logo staying
 * put above it. Same here, driven entirely by core's toggle script: it flips
 * .open on the list and aria-expanded on the button, and those two are the
 * only hooks below. The breakpoint is core's 768px (its script and CSS both
 * key on it), not live's 992px: between the two the wrapped desktop row fits.
 */
@media (max-width: 768px) {
    .cc-nav {
        position: static;
    }

    .cc-nav .nav-toggle {
        display: block;
        position: absolute;
        top: 50%;
        right: 12px;
        z-index: 1002;
        width: 32px;
        height: 32px;
        margin-top: -16px;
        padding: 0;
        border: 0;
        background: none;
        cursor: pointer;
    }

    /* Three bars that fold into a cross: the middle bar fades, the outer two
     * swing to the centre. Timings are live's. */
    .cc-nav .nav-toggle span {
        position: absolute;
        left: 0;
        top: 50%;
        width: 100%;
        height: 3px;
        margin-top: -1.5px;
        background: var(--color-primary);
        transition: transform 0.3s 0s, top 0.3s 0.3s, opacity 0.3s 0.3s;
    }

    .cc-nav .nav-toggle span:nth-child(2) { top: calc(50% - 9px); }
    .cc-nav .nav-toggle span:nth-child(3) { top: calc(50% + 9px); width: 70%; }

    .cc-nav .nav-toggle[aria-expanded="true"] span { transition: transform 0.3s 0.3s, top 0.3s, opacity 0.3s; }
    .cc-nav .nav-toggle[aria-expanded="true"] span:nth-child(1) { opacity: 0; }
    .cc-nav .nav-toggle[aria-expanded="true"] span:nth-child(2) { top: 50%; transform: rotate(-45deg); }
    .cc-nav .nav-toggle[aria-expanded="true"] span:nth-child(3) { top: 50%; width: 100%; transform: rotate(45deg); }

    /* The overlay. Always laid out (display:flex) so it can animate; hidden
     * by visibility, which also keeps its links out of the tab order exactly
     * as core's display:none did. Core's own display toggles land on the same
     * value, so opacity/transform/visibility here are the single mechanism. */
    .cc-nav .nav-main {
        display: flex;
        flex-direction: column;
        /* nowrap is load-bearing: the desktop row wraps, and a wrapping column
         * in a fixed-height box breaks into a second column the moment an open
         * submenu makes the list taller than the screen. */
        flex-wrap: nowrap;
        align-items: stretch;
        gap: 0;
        position: fixed;
        inset: 0;
        z-index: 1000;
        margin: 0;
        padding: 130px 0 40px;
        background: var(--cc-banner-wash);
        overflow: auto;
        visibility: hidden;
        opacity: 0;
        transform: scale(0.8);
        transition: opacity 0.5s ease-in-out, transform 0.5s ease-in-out, visibility 0s linear 0.5s;
    }

    .cc-nav .nav-main.open {
        visibility: visible;
        opacity: 1;
        transform: none;
        transition: opacity 0.5s ease-in-out, transform 0.5s ease-in-out;
    }

    /* The rule across the top of the open menu, then the list centred under it. */
    .cc-nav .nav-main::before {
        content: "";
        display: block;
        border-top: 1px solid var(--color-primary);
        margin-bottom: 20px;
    }

    .cc-nav .nav-main > li {
        width: min(80%, 520px);
        margin: 0 auto;
    }

    body:has(.cc-nav .nav-main.open) {
        overflow: hidden;
    }

    /* Live's phone menu: 22px at weight 500 (Lato has no 500, so it renders
     * at 400 there too), submenu links 18px. */
    .cc-nav .nav-item > a,
    .cc-nav .nav-heading > .nav-label {
        font-size: calc(var(--nav-link-size, 20px) * 1.1);
        font-weight: 500;
        white-space: normal;
    }

    .cc-nav .nav-sub {
        position: static;
        min-width: 100%;
        padding: 0;
        background: none;
        box-shadow: none;
    }

    .cc-nav .nav-sub a {
        display: block;
        padding: 10px 0;
        border: 0;
        background: none;
        color: var(--nav-dropdown-color, var(--color-primary));
        font-family: var(--font-nav, inherit);
        font-size: calc(var(--nav-link-size, 20px) * 0.9);
        font-weight: 400;
        line-height: 1;
    }

    .cc-nav .nav-sub a:hover,
    .cc-nav .nav-sub a:focus-visible {
        background: none;
        color: var(--nav-hover-color, var(--color-secondary));
    }

    /* Live sets each parent's chevron right after its label (a flex row with
     * a 10px gap), not at the far edge of the row where core puts it. Same
     * signal as the desktop caret: aria-expanded is only ever on a parent. */
    .cc-nav .nav-item:has(> .nav-sub):not(.inactive) > a,
    .cc-nav .nav-heading:has(> .nav-sub) > .nav-label {
        padding-right: 0;
    }

    .cc-nav .nav-item > a[aria-expanded]::after,
    .cc-nav .nav-heading > button.nav-label[aria-expanded]::after {
        content: "";
        position: static;
        display: inline-block;
        width: 0.33em;
        height: 0.33em;
        margin: 0 0 0 10px;
        vertical-align: 0.15em;
        border-right: 1.5px solid currentColor;
        border-bottom: 1.5px solid currentColor;
        transform: rotate(45deg);
        transition: transform 0.2s ease;
    }

    .cc-nav .nav-item.sub-open > a[aria-expanded]::after,
    .cc-nav .nav-heading.sub-open > button.nav-label[aria-expanded]::after {
        margin-top: 0;
        transform: rotate(225deg);
    }

    /* A linked parent with core's chevron button (header override, CMS
     * 26.10.15+): the words open the page and the BUTTON opens the list, so
     * the button carries the arrow and the link draws none (two arrows on one
     * row otherwise; the link keeps aria-expanded for the desktop focus
     * mirror, which is why the rule above would still match it).
     *
     * Laid out to match the heading parents beside it: the arrow sits right
     * after the label, as live has it, not at the row's right edge where core
     * puts it. Core's edge position read as inconsistent next to Expertise and
     * ADR, whose arrows follow their words. The row becomes a wrapping flex
     * line: the link shrinks to its text, the button follows it on the same
     * baseline, and the submenu takes a line of its own beneath. The button is
     * wider than its glyph so the tap area runs on to the right of the arrow
     * rather than being the arrow alone, and its line box copies the link's
     * (font, size, line-height, 10px padding) so baseline alignment puts the
     * arrow exactly where the headings' ::after sits. */
    .cc-nav .nav-item:has(> .nav-sub-toggle) {
        display: flex;
        flex-wrap: wrap;
        align-items: baseline;
    }

    .cc-nav .nav-item:has(> .nav-sub-toggle) > a {
        flex: 0 1 auto;
    }

    .cc-nav .nav-item:has(> .nav-sub-toggle) > a[aria-expanded]::after {
        content: none;
    }

    .cc-nav .nav-item:has(> .nav-sub-toggle) > .nav-sub {
        flex: 0 0 100%;
    }

    .cc-nav .nav-item > .nav-sub-toggle {
        position: static;
        display: block;
        flex: 0 0 auto;
        width: 3rem;
        height: auto;
        padding: 10px 0 10px 10px;
        border: 0;
        background: none;
        color: var(--nav-link-color, var(--color-primary));
        font-family: var(--font-nav, inherit);
        font-size: calc(var(--nav-link-size, 20px) * 1.1);
        line-height: 1.34;
        text-align: left;
    }

    .cc-nav .nav-item > .nav-sub-toggle::after {
        position: static;
        display: inline-block;
        width: 0.33em;
        height: 0.33em;
        margin: 0;
        vertical-align: 0.15em;
        border-right-width: 1.5px;
        border-bottom-width: 1.5px;
    }

    .cc-nav .nav-item.sub-open > .nav-sub-toggle::after {
        margin-top: 0;
    }

    /* The clerks' number keeps its weight in the phone menu too: the 500
     * above would otherwise outrank it by source order. */
    .cc-nav .nav-item.cc-nav__phone > a {
        font-weight: 900;
    }
}

/* ── Page title band ──────────────────────────────────────────────────────────
 * Live's inner banner: the chambers' name set small above the page title,
 * both on the wash the header paints, so header and banner read as one block.
 * The eyebrow is generated content on core's .page-body-heading, reading its
 * text from --cc-eyebrow, which overrides/body-attributes.blade.php sets on
 * <body> from the company name. Generated rather than a block of its own for
 * one reason: the wash is a radial gradient, and two stacked boxes each
 * painting their own meet at a visible step. One box, one wash.
 *
 * The space above the eyebrow is --cc-banner-top, below; the 8px under the
 * title is live's h1 margin, which is all that sits between it and the wash's
 * bottom edge.
 * No eyebrow on the home page (live opens on its banner, no title band) nor
 * under a hero banner, which already carries the heading.
 */
.page-body-heading {
    background: var(--cc-banner-wash);
    padding: var(--cc-banner-top) 0 8px;
    margin-bottom: 0;
}

/* Live's body opens on its section step (pt-100) under the band. */
.page-body-heading ~ .page-body {
    padding-top: var(--cc-band, 100px);
}

/* Where the banner text starts. Live floats its header over the banner and
 * sets the text at 120 / 160 / 200 / 240px from the top of the page (768 /
 * 992 / 1200). This header is in flow, so each step is live's figure less this
 * header's own height at that width, which itself steps with the logo and with
 * the nav row it drops to below 1700. Measured, so re-measure if the header
 * changes height. The profile banner starts at the same line. */
:root { --cc-banner-top: 22px; }

@media (min-width: 768px)  { :root { --cc-banner-top: 62px; } }
@media (min-width: 992px)  { :root { --cc-banner-top: 61px; } }
@media (min-width: 1200px) { :root { --cc-banner-top: 88px; } }
@media (min-width: 1400px) { :root { --cc-banner-top: 60px; } }
@media (min-width: 1600px) { :root { --cc-banner-top: 31px; } }
@media (min-width: 1700px) { :root { --cc-banner-top: 80px; } }

.page-body-heading > .container::before,
.cc-page-banner__text::before {
    content: var(--cc-eyebrow, none);
    display: block;
    margin-bottom: 8px;
    font-family: var(--font-h3, var(--font-h1, inherit));
    font-size: calc(var(--font-size-h3, 34px) * var(--cc-step-h3));
    font-weight: 400;
    line-height: 1.2;
    color: var(--color-h3, var(--color-primary));
}

/* The banner below turns the container into a two-column grid, and a ::before
 * on it would be a third column. The eyebrow moves onto the text column there
 * (the rule above), so the container must stop drawing one. */
.cc-page-banner > .container::before {
    content: none;
}

body[data-path="/"] .page-body-heading > .container::before,
.page-hero ~ .page-body-heading > .container::before,
.slideshow-hero ~ .page-body-heading > .container::before {
    content: none;
}

.page-hero ~ .page-body-heading,
.slideshow-hero ~ .page-body-heading {
    padding-top: 0;
}

/* ── Page title band: the with-image banner ───────────────────────────────────
 * Live's includes/generalbanner.php in its other shape. Where a page carries an
 * image, the eyebrow and title drop to half width and the image sits beside
 * them, whole, on the same wash — never cropped into a background, which is
 * what core's hero would make of it.
 *
 * Two equal columns with a 24px gap, because legacy is Bootstrap: col-md-6
 * twice, and the gutter between them is 12px of column padding each side. The
 * columns are vertically centred (live: `.bg-banner-type .row {align-items:
 * center}`), so the title sits against the middle of the picture rather than
 * the top of the band.
 *
 * NO bottom padding, and that is live's measurement rather than a rounding:
 * `.inner-banner` sets padding-top only, so the wash ends exactly where the
 * image does. At 1440 that puts the band's edge at 608px on both sites.
 *
 * The image keeps its intrinsic ratio (Bootstrap `img-fluid` = max-width:100%,
 * height:auto) instead of being given one here, so a replacement of any shape
 * lands correctly. max-width rather than width for the same reason: an image
 * narrower than the column stays its own size on live rather than being
 * stretched, and ResponsiveImage emits width/height so the space is reserved
 * before it loads either way.
 *
 * 768px is the stack point because col-md-6 is: below it live gives each half
 * the full row, title first, image under it and still flush to the wash's
 * bottom edge.
 */
.cc-page-banner {
    padding-bottom: 0;
}

@media (min-width: 768px) {
    .cc-page-banner > .container {
        display: grid;
        grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
        gap: 24px;
        align-items: center;
    }
}

.cc-page-banner__image picture,
.cc-page-banner__image img {
    display: block;
}

.cc-page-banner__image img {
    max-width: 100%;
    height: auto;
}

/* Stacked, the image needs the gap the grid gives it at desktop. The title's
 * own bottom margin is all that separates them on live. */
@media (max-width: 767.98px) {
    .cc-page-banner__image {
        margin-top: 8px;
    }
}

/* ── Home page: the banner ────────────────────────────────────────────────────
 * Live's includes/homebanner.php, the one page it opens with a photograph
 * instead of the title band. The picture runs the full viewport at 100vh under
 * a white-to-transparent wash, and the chambers' line, its strapline and a
 * barrister search sit on the clear half. Markup:
 * frontend/chambers/partials/home-banner.blade.php.
 *
 * The header floats over it. That is live's arrangement on every page and this
 * site's on only this one — the Header section above says why the rest of the
 * site keeps its header in flow, and none of that reasoning applies to a page
 * whose banner is a full-bleed image.
 *
 * `position: absolute` with NO `top`, which is the point: the header keeps the
 * vertical position it would have had, so an announcement bar above it still
 * pushes it down, and the only thing that changes is that its height is given
 * back to the banner.
 *
 * The z-index is live's 99 and has to be a real value rather than auto. The
 * banner below is a positioned box later in the tree, so with both on auto the
 * picture paints over the nav. Everything the phone menu stacks against (its
 * own 1000, the brand's 1001) is INSIDE the header and keeps its order within
 * it; core's back-to-top at 60 stays underneath as before.
 */
body[data-path="/"] .cc-header {
    position: absolute;
    left: 0;
    right: 0;
    z-index: 99;
    background: none;
}

.cc-home-banner {
    position: relative;
    z-index: 0;
    display: flex;
    /* Live's strut, which is a zero-width box padded to 42% of the viewport
     * width and floored at the viewport height. The second declaration is the
     * same rule in small-viewport units and a browser that does not know them
     * drops it: on a phone 100vh is measured with the URL bar retracted, so the
     * search box lands below the fold and the first thing a visitor does is
     * scroll past the banner to find it. */
    min-height: max(42vw, 100vh);
    min-height: max(42vw, 100svh);
    overflow: hidden;
}

.cc-home-banner__image {
    position: absolute;
    inset: 0;
}

.cc-home-banner__image picture,
.cc-home-banner__image img {
    display: block;
    width: 100%;
    height: 100%;
    object-fit: cover;
    object-position: center;
}

/* The wash: flat at 50% on a phone, where the copy sits over the middle of the
 * picture, and a left-to-right gradient from 768px, where it clears the half
 * the copy is set on. White here is the page ground showing through rather than
 * a brand colour, so it is mixed from the page-background token.
 *
 * The far stop is the same colour at 0% rather than the `transparent` keyword,
 * which in several engines interpolates through transparent BLACK and greys the
 * middle of the gradient. */
.cc-home-banner::after {
    content: "";
    position: absolute;
    inset: 0;
    background: color-mix(in srgb, var(--color-page-bg, #fff) 50%, transparent);
}

@media (min-width: 768px) {
    .cc-home-banner::after {
        background: linear-gradient(
            90deg,
            var(--color-page-bg, #fff) 0%,
            color-mix(in srgb, var(--color-page-bg, #fff) 0%, transparent) 100%
        );
    }
}

/* The reserve clears the floating header. Live's .banner-content is a flat
 * 148px at every width and the content is vertically centred, so this only
 * decides the SHORT-viewport case, which is exactly the one that would
 * otherwise set the heading behind the nav. Stepping it up for the taller
 * header at 1400 and 1600 moves the centred heading down on every screen. */
.cc-home-banner__content {
    position: relative;
    z-index: 1;
    align-self: center;
    width: 100%;
    padding: 148px 0 48px;
}

/* col-lg-6 from 992px, the full width below it: half the row, which is the
 * column plus its 24px of gutter, less the column's own gutter. */
@media (min-width: 992px) {
    .cc-home-banner__text { max-width: calc((100% + 24px) / 2 - 24px); }
}

/* The home heading is off the theme's scale deliberately. The seeder's h1 is
 * the INNER-page size and says so; live sets this one larger at every step and
 * ends on a viewport-relative 5.1vw, so the lockup keeps its measure on a wide
 * screen instead of stranding "Proactive" on a line of its own. 1.137 is live's
 * line-height, tight enough that the three words read as one mark. */
.cc-home-banner h1 {
    font-size: 48px;
    line-height: 1.137;
    margin-bottom: 8px;
}

@media (min-width: 576px) { .cc-home-banner h1 { font-size: 62px; } }
@media (min-width: 992px) { .cc-home-banner h1 { font-size: 80px; } }
@media (min-width: 1400px) { .cc-home-banner h1 { font-size: 5.1vw; } }

/* Line-height 2, much looser than the body's 1.64: the strapline is set over
 * three lines under a very large heading and reads as display copy. */
.cc-home-banner__caption {
    font-size: 16px;
    line-height: 2;
    margin-bottom: 16px;
    color: var(--color-text, var(--color-primary));
}

@media (min-width: 768px) { .cc-home-banner__caption { font-size: 18px; } }
@media (min-width: 1200px) { .cc-home-banner__caption { font-size: 22px; } }
@media (min-width: 1400px) { .cc-home-banner__caption { font-size: 26px; } }

.cc-home-search {
    position: relative;
    max-width: 357px;
}

/* The left padding is what leaves room for the magnifier laid over the field.
 * appearance:none is load-bearing on a type=search: WebKit otherwise draws its
 * own rounded box and a clear button inside this one. */
.cc-home-search input {
    width: 100%;
    height: 42px;
    padding: 8px 20px 8px 72px;
    border: 2px solid var(--color-primary);
    border-radius: 32px;
    background: transparent;
    box-shadow: none;
    font-size: 18px;
    color: var(--color-primary);
    appearance: none;
    -webkit-appearance: none;
}

.cc-home-search input::-webkit-search-decoration,
.cc-home-search input::-webkit-search-cancel-button {
    -webkit-appearance: none;
}

@media (min-width: 768px) {
    .cc-home-search input { height: 52px; font-size: 20px; }
}

@media (min-width: 1200px) {
    .cc-home-search input { height: 64px; font-size: 24px; border-width: 3px; }
}

/* The placeholder IS the label on live: set in the heading face, at full navy
 * rather than the browser's grey, which is why it reads as a word in the design
 * and not as a hint. The real label is the screen-reader one in the markup. */
.cc-home-search input::placeholder {
    opacity: 1;
    color: var(--color-primary);
    font-family: var(--font-h1, inherit);
}

/* Live draws an inert icon at this position. Same mark, made into the form's
 * submit: a single-field form does submit on Enter, but nothing on screen says
 * so and a pointer user has nothing to press. */
.cc-home-search__submit {
    position: absolute;
    left: 30px;
    top: 0;
    height: 100%;
    display: flex;
    align-items: center;
    padding: 0;
    border: 0;
    background: none;
    color: var(--color-primary);
    cursor: pointer;
}

.cc-home-search__submit:hover { color: var(--color-secondary); }

/* ── Home page: section rhythm ────────────────────────────────────────────────
 * Under the banner live runs four bands — the intro, the expertise carousel,
 * the quote band, the services list — then the site-wide accreditation strip.
 * Their rhythm is the legacy `.pt-100` step, not core's 2.5rem block gap.
 *
 * KEYED OFF EACH BLOCK'S OWN CLASS, which chambers:import writes to the Design
 * tab. That is the intended way back out: clear the class and the section falls
 * to core's default styling, no deploy involved. `body[data-path="/"]` is used
 * only where the rule is genuinely about the page rather than the block.
 */
:root {
    --cc-band: 56px;
}

@media (min-width: 768px) { :root { --cc-band: 72px; } }
@media (min-width: 1200px) { :root { --cc-band: 100px; } }

/* The banner sets the page's top edge and the accreditation strip carries its
 * own 80px, so the body contributes neither. */
body[data-path="/"] .page-body {
    padding: 0;
}

.builder-block.cc-intro,
.builder-block.cc-expertise,
.builder-block.cc-services-list {
    margin-top: var(--cc-band);
    margin-bottom: 0;
}

/* The quote band is the exception: live's testimonials section opens straight
 * off whatever precedes it, its own padding being all the space there is (22px
 * from an Expertise page's last line, the carousel's 72px on the home page). So
 * it states no top edge, and the block before it gives up its gap too. */
.builder-block.cc-quote-band {
    margin-top: 0;
}

.builder-block:has(+ .builder-block.cc-quote-band) {
    margin-bottom: 0;
}

/* The rhythm above is four bands in a row, so each one states its top edge and
 * the band below supplies the next gap. The quote band also lands on inner
 * pages, where what follows is an ordinary block with no --cc-band margin of
 * its own and the band would butt straight into it. So it states its bottom
 * edge too: adjacent margins collapse, so the home page still steps by one
 * --cc-band and not two. Live measures the same 100px, from the `pt-100` on the
 * section under the testimonials include.
 *
 * Not on a last block, where the gap belongs to whatever comes after .page-body
 * — on an Expertise page that is the barristers' band and its own 80px. */
.builder-block.cc-quote-band:not(:last-child) {
    margin-bottom: var(--cc-band);
}

/* Live's `.link`: bold, no underline, a gold rule under it that swaps to navy
 * on hover as the text goes gold. It arrives as a class inside the rich text
 * (the legacy editor's own markup), so it is styled site-wide rather than on
 * the home block — only the intro carries one today, but an editor pasting the
 * same markup elsewhere should get the same link. */
.cms-content .link {
    margin-top: 24px;
}

.cms-content .link a {
    display: inline-block;
    padding: 10px 0;
    font-weight: 700;
    text-decoration: none;
    color: var(--color-primary);
    border-bottom: 2px solid var(--color-secondary);
}

.cms-content .link a:hover,
.cms-content .link a:focus {
    color: var(--color-secondary);
    border-bottom-color: var(--color-primary);
}

/* The intro's alignment is justified, and that is the legacy editor's own
 * inline style rather than a stylesheet rule — which is why reaching it needs
 * !important, the one place on this page that does.
 *
 * The same call the "Body copy in narrow columns" section above makes, applied
 * to a narrow VIEWPORT rather than a narrow column: at 350px the copy is all
 * rivers, and a justified heading that wraps is worse still — "We are College
 * Chambers" comes out as two lines with a hand's width between the words.
 * Live has both and they are the only part of this section not worth copying.
 * The heading is unjustified at every width because it wraps at several. */
.cc-intro .cms-content h2 {
    text-align: left !important;
}

@media (max-width: 767.98px) {
    .cc-intro .cms-content p {
        text-align: left !important;
    }
}

/* ── Home page: the sliders ───────────────────────────────────────────────────
 * Both carousels are core CONTENT FEEDS with a scroll-snap track laid over
 * them; the dots are built by frontend/chambers/partials/carousel.blade.php.
 * The track is CSS and the dots are JS, in that order deliberately: with
 * scripting off a visitor still gets a row they can scroll, which is more than
 * live's Swiper leaves behind.
 *
 * Slides per view lives HERE and nowhere else. The script measures the step
 * between two slides to decide the dot count, so the breakpoint ladder cannot
 * drift out of step with the pagination.
 */
.cc-carousel__track {
    display: flex;
    overflow-x: auto;
    scroll-snap-type: x mandatory;
    /* The dots are the affordance, as on live. The bar would otherwise sit
     * across the bottom of a navy card. */
    scrollbar-width: none;
    -ms-overflow-style: none;
}

.cc-carousel__track::-webkit-scrollbar { display: none; }

/* Auto-height (the quote band only — the expertise cards are all one square).
 * Live sizes its band to the LONGEST of the ten recommendations it drew, so a
 * one-line quotation is followed by half a screen of empty door and the dots
 * are a scroll away from what they page. The script sets the track's height
 * from the quotation actually on screen instead; these two are what make that
 * safe. flex-start stops the slides being stretched back to the track, and
 * hidden clips the ones taller than it — all of which are off screen sideways
 * anyway, and without it the browser resolves overflow-y to auto and puts a
 * vertical scrollbar on the band. */
.cc-carousel__track--auto-height {
    align-items: flex-start;
    overflow-y: hidden;
    transition: height 0.32s ease-in-out;
}

@media (prefers-reduced-motion: reduce) {
    .cc-carousel__track--auto-height { transition: none; }
}

.cc-carousel__controls {
    display: flex;
    padding-top: 42px;
}

/* The row WRAPS, which live's does not. Twelve practice areas on a phone is
 * twelve dots: 60px for the active lozenge plus eleven more at 12px and eleven
 * 16px gaps is 368px in a 350px column, and a nowrap row of them widens the
 * whole document — the page then scrolls sideways and the fixed cookie banner,
 * which sizes itself to the layout viewport, grows with it. */
.cc-carousel__dots {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 12px 16px;
}

@media (min-width: 768px) { .cc-carousel__dots { gap: 12px 32px; } }
@media (min-width: 992px) { .cc-carousel__dots { gap: 12px 40px; } }

/* Live's bullet: a 12px dot that stretches to a 60px lozenge where it is.
 * Width alone is animated, so the row does not reflow around it. */
.cc-carousel__dot {
    flex: 0 0 auto;
    width: 12px;
    height: 12px;
    padding: 0;
    border: 0;
    border-radius: 12px;
    background: var(--cc-pag, var(--color-primary));
    cursor: pointer;
    transition: width 0.32s ease-in-out, background-color 0.32s ease-in-out;
}

.cc-carousel__dot:hover { background: var(--color-secondary); }
.cc-carousel__dot.is-active { width: 60px; }

@media (prefers-reduced-motion: reduce) {
    .cc-carousel__dot { transition: none; }
}

/* ── Home page: Our Expertise ─────────────────────────────────────────────────
 * Live's includes/expertise.php: navy squares carrying the practice-area name
 * and one link, four across at 1200 and stepping down to one on a phone, with
 * the whole live services list in it — Direct Access included, which only the
 * NAV leaves out.
 *
 * The feed is `list` rather than `cards` because cards is the only style that
 * renders a thumbnail, and the legacy card has none: hiding a loaded image in
 * CSS would cost every visitor thirteen downloads to see nothing.
 */
.cc-expertise .builder-block__heading {
    margin-bottom: 25px;
}

/* The feed wraps itself in a second .container inside the page's own, and core
 * gives .content-section a rule above it that live has no counterpart for. */
.cc-expertise .content-section,
.cc-quote-band .content-section {
    padding: 0;
    border-top: 0;
}

/* THE TRACK MUST HAVE NO HORIZONTAL PADDING, on either carousel. An overflow
 * container clips at its PADDING box, not its content box, so a track that
 * keeps core's .container gutter shows 25px of the next slide down each side —
 * which on the quote band is a second, stray quotation mark against the right
 * edge. The inset the gutter provided is moved out to .content-section. */
.cc-expertise .content-section > .container,
.cc-quote-band .content-section > .container {
    max-width: none;
    padding: 0;
}

.cc-expertise .feed-list {
    --cc-cols: 1;
    --cc-gap: 16px;
    gap: var(--cc-gap);
}

/* Live's .our-expertise padding-bottom: under the dots, not between the cards
 * and the dots, which sit 42px below the cards on live. */
.cc-expertise .content-section > .container {
    padding-bottom: 72px;
}

@media (min-width: 768px) { .cc-expertise .feed-list { --cc-cols: 2; --cc-gap: 20px; } }
@media (min-width: 992px) { .cc-expertise .feed-list { --cc-cols: 3; --cc-gap: 24px; } }
@media (min-width: 1200px) { .cc-expertise .feed-list { --cc-cols: 4; --cc-gap: 30px; } }

/* A square, with the text sitting on its floor. aspect-ratio is live's own
 * `padding-bottom: 100%` strut said plainly; the card is emptied of core's list
 * rule (a hairline under every row) on the way past. */
.cc-expertise .feed-item {
    flex: 0 0 calc((100% - (var(--cc-cols) - 1) * var(--cc-gap)) / var(--cc-cols));
    display: flex;
    flex-direction: column;
    justify-content: flex-end;
    aspect-ratio: 1;
    padding: 24px;
    border-bottom: 0;
    background: var(--color-primary);
    color: #fff;
    scroll-snap-align: start;
}

@media (min-width: 1400px) { .cc-expertise .feed-item { padding: 30px; } }

/* The practice-area name, at the display face and far larger than core's list
 * heading. It steps DOWN at 1200, which is not a typo: that is where a fourth
 * card joins the row and each one loses a quarter of its width. */
.cc-expertise .feed-item h3 {
    margin-bottom: 8px;
    font-family: var(--font-h1, inherit);
    font-weight: 400;
    font-size: 34px;
    line-height: 1.2;
}

@media (min-width: 768px) { .cc-expertise .feed-item h3 { font-size: 38px; } }
@media (min-width: 1200px) { .cc-expertise .feed-item h3 { font-size: 34px; } }
@media (min-width: 1400px) { .cc-expertise .feed-item h3 { font-size: 38px; } }
@media (min-width: 1600px) { .cc-expertise .feed-item h3 { font-size: 42px; } }

.cc-expertise .feed-item h3 a {
    color: #fff;
    text-decoration: none;
}

.cc-expertise .feed-item h3 a:hover,
.cc-expertise .feed-item h3 a:focus {
    color: var(--color-secondary);
}

/* The excerpt. Live's card is the name and the link, nothing else, and two
 * services carry summary text that would otherwise appear here and nowhere
 * else on the site's front page. :not() keeps the button, which is also a <p>. */
.cc-expertise .feed-item > p:not(.card-actions) {
    display: none;
}

.cc-expertise .card-actions {
    margin: 0;
}

/* Live's `.link-small`: no button, just bold text on a gold rule. On hover the
 * two swap — the text goes gold and the rule goes white — which is the legacy
 * `--link-color` / `--link-hover-color` pair inverting on the card. */
.cc-expertise .card-actions .btn {
    display: inline-block;
    padding: 10px 0;
    border: 0;
    border-bottom: 2px solid var(--color-secondary);
    border-radius: 0;
    background: none;
    font-size: 16px;
    font-weight: 700;
    color: #fff;
}

.cc-expertise .card-actions .btn:hover,
.cc-expertise .card-actions .btn:focus {
    background: none;
    color: var(--color-secondary);
    border-bottom-color: #fff;
}

/* ── The quote band ───────────────────────────────────────────────────────────
 * Live's includes/testimonials.php: a full-bleed band over the blue-door
 * photograph, a gold label, then one recommendation at a time behind an
 * oversized serif quote mark.
 *
 * NOT home-only, though the home page is where it was built: live carries the
 * same include on its inner templates, so the class is the hook and anything
 * wearing it is the band — the home page's own feed, and the synced set an
 * Expertise page places. The class has to sit on the block INSIDE a synced set:
 * a `reusable` placement is replaced by the library's blocks before render, so
 * a class typed on the placement's Design tab never arrives.
 *
 * The photograph is the block's own Design-tab background, not a path in here,
 * so the picture stays the site owner's to change. The breakout is core's
 * u-full-bleed technique, the same one the Maps section uses and for the same
 * reason: live has no half-width version of this band.
 */
.cc-quote-band {
    box-sizing: border-box;
    width: 100vw;
    max-width: 100vw;
    margin-left: calc(50% - 50vw);
    margin-right: calc(50% - 50vw);
    padding: 56px 0 45px;
    color: #fff;
    --cc-pag: #fff;
}

@media (min-width: 768px) { .cc-quote-band { padding: 72px 0 58px; } }
@media (min-width: 1200px) { .cc-quote-band { padding: 100px 0 80px; } }

/* The band is bled, so both of its children need putting back on the page grid
 * by hand — core's own expression for a bled block's heading. It sits on
 * .content-section rather than on the track inside it for the reason given at
 * the track rule above. */
.cc-quote-band > .builder-block__eyebrow,
.cc-quote-band .content-section {
    padding-inline: max(12px, calc(50% - var(--cc-col) / 2));
}

/* Live's label is a plain sentence at body size in the body face. Core sets its
 * eyebrows small, uppercase and tracked out, which is a different device
 * entirely and the only place on this page it would appear. */
.cc-quote-band > .builder-block__eyebrow {
    margin-bottom: 48px;
    font-size: 1rem;
    text-transform: none;
    letter-spacing: normal;
    color: var(--color-secondary);
}

/* Core's card is a tinted box with a rule down its left edge. Here it is a
 * slide: no chrome at all, and the geometry is live's two columns — the mark,
 * then everything else. justify-self on the byline is what keeps its gold rule
 * under the name instead of across the whole column (a grid item set to
 * inline-block is blockified, so `display` cannot do it). */
.cc-quote-band .testimonial-card {
    flex: 0 0 100%;
    display: grid;
    grid-template-columns: auto minmax(0, 1fr);
    /* The rows take their content's height and no more. Without it they share
     * out the track's height instead, and on a band sized by its longest
     * quotation the byline is left floating hundreds of pixels under a short
     * one. */
    align-content: start;
    margin: 0;
    padding: 0;
    border: 0;
    border-radius: 0;
    background: none;
    scroll-snap-align: start;
}

/* Bootstrap's col-md-8 / col-lg-7 / col-xl-6, said as the space the column does
 * NOT take: the slide itself has to stay the full width or it cannot snap. */
@media (min-width: 768px) { .cc-quote-band .testimonial-card { padding-right: 33.333%; } }
@media (min-width: 992px) { .cc-quote-band .testimonial-card { padding-right: 41.667%; } }
@media (min-width: 1200px) { .cc-quote-band .testimonial-card { padding-right: 50%; } }

.cc-quote-band .testimonial-card > * {
    grid-column: 2;
}

.cc-quote-band .testimonial-card::before {
    content: "\201C";
    grid-column: 1;
    align-self: start;
    font-family: var(--font-h1, serif);
    font-size: 82px;
    line-height: 1;
    padding-right: 16px;
    margin-left: -0.1em;
}

@media (min-width: 1200px) { .cc-quote-band .testimonial-card::before { font-size: 102px; } }
@media (min-width: 1400px) { .cc-quote-band .testimonial-card::before { font-size: 182px; } }

/* Core wraps the quotation in curly quotes as BARE TEXT NODES either side of
 * the paragraph, and a text node cannot be selected. The mark above replaces
 * them, so they are collapsed by taking the size off their parent and giving it
 * back to the paragraph — which is the only handle those two characters have.
 * Removing the `font-size: 0` brings back two small quotes hanging off a large
 * one, so the pair belongs together. */
.cc-quote-band .quote {
    font-size: 0;
    font-style: normal;
    margin: 0;
}

.cc-quote-band .quote > * {
    font-family: var(--font-h1, inherit);
    font-size: 24px;
    line-height: 1.556;
    color: #fff;
    margin: 0 0 20px;
}

@media (min-width: 576px) { .cc-quote-band .quote > * { font-size: 28px; } }
@media (min-width: 1200px) { .cc-quote-band .quote > * { font-size: 30px; } }
@media (min-width: 1400px) { .cc-quote-band .quote > * { font-size: 32px; } }
@media (min-width: 1600px) { .cc-quote-band .quote > * { font-size: 36px; } }

.cc-quote-band .author {
    justify-self: start;
    padding: 10px 0;
    border-bottom: 2px solid var(--color-secondary);
    color: #fff;
}

/* Live's band prints the name alone; the firm or role behind it is kept because
 * it is published content with room on the line, and set lighter so the byline
 * still reads as one thing. */
.cc-quote-band .author .role {
    font-weight: 400;
    color: #fff;
}

/* Indented past the quote mark, as live indents its own — but only where the
 * dots fit beside it. On a phone the indent alone is a quarter of the column,
 * and live's own band overflows the screen because of it. */
.cc-quote-band .cc-carousel__controls {
    padding-top: 48px;
}

@media (min-width: 768px) {
    .cc-quote-band .cc-carousel__controls { padding-left: 89px; }
}

/* ── Home page: Our Legal Services Include ────────────────────────────────────
 * The legacy `.items-include` list: two columns of ruled rows, each opening on
 * a small gold disc, with the item itself set in the display face. The markup
 * is the editor's own <ul><li><span>, which is exactly what the legacy field
 * held, so this styles rich text rather than a block.
 */
.cc-services-list .builder-block__heading {
    margin-bottom: 24px;
}

.cc-services-list .cms-content ul {
    --cc-col: 100%;
    --cc-li-gap: 0px;
    display: flex;
    flex-wrap: wrap;
    gap: 0 var(--cc-li-gap);
    list-style: none;
    margin: 0;
    padding: 0;
}

@media (min-width: 768px) {
    .cc-services-list .cms-content ul { --cc-col: 50%; --cc-li-gap: 24px; }
}

@media (min-width: 992px) { .cc-services-list .cms-content ul { --cc-li-gap: 40px; } }
@media (min-width: 1200px) { .cc-services-list .cms-content ul { --cc-li-gap: 50px; } }
@media (min-width: 1400px) { .cc-services-list .cms-content ul { --cc-li-gap: 74px; } }

.cc-services-list .cms-content li {
    display: flex;
    width: calc(var(--cc-col) - var(--cc-li-gap) / 2);
    padding: 10px 12px;
    border-bottom: 2px solid var(--color-primary);
}

/* The disc is set on the first line of the item rather than centred on the row,
 * so a value that wraps to two lines keeps its mark beside the first. */
.cc-services-list .cms-content li::before {
    content: "";
    flex: 0 0 auto;
    width: 14px;
    height: 14px;
    margin-right: 20px;
    margin-top: calc(5px + 0.7em);
    border-radius: 50%;
    background: var(--color-secondary);
}

/* The rule above the first row of each column, so the set reads as a table. */
.cc-services-list .cms-content li:first-child {
    border-top: 2px solid var(--color-primary);
}

@media (min-width: 768px) {
    .cc-services-list .cms-content li:nth-child(2) {
        border-top: 2px solid var(--color-primary);
    }
}

.cc-services-list .cms-content li span {
    display: block;
    padding: 12px 0;
    font-family: var(--font-h1, inherit);
}

/* ── Memberships & Awards ──────────────────────────────────────────────
 * The legacy accreditations strip is a Swiper carousel, and its proportions come
 * entirely from the Swiper config, not from the old stylesheet: six slides in
 * view at desktop, stepping down to two on a phone, with the gap widening as the
 * count rises.
 *
 *     slides in view    2  ·  3 (≥576)  ·  4 (≥768)  ·  5 (≥992)  ·  6 (≥1200)
 *     gap between      20  · 20         · 24         · 24         · 30
 *
 * A slide is whatever is left of the container once the gaps are taken out,
 * divided by the count. That is what Swiper computes at run time and what the
 * calc() below reproduces, so the logos line up on the same columns as live.
 *
 * Core's strip is a continuous marquee rather than a stepped autoplay, so the
 * MOTION is not live's. The geometry is. Do not add flex-wrap, width or
 * justify-content to .builder-logo-strip here: the marquee script measures one
 * lap off that element and out-specifying its nowrap row leaves it nothing to
 * scroll.
 */
.cc-awards {
    --cc-awards-cols: 2;
    --cc-awards-gap: 20px;
    padding-top: 48px;
}

@media (min-width: 576px) {
    .cc-awards {
        --cc-awards-cols: 3;
    }
}

@media (min-width: 768px) {
    .cc-awards {
        --cc-awards-cols: 4;
        --cc-awards-gap: 24px;
        padding-top: 60px;
    }
}

@media (min-width: 992px) {
    .cc-awards {
        --cc-awards-cols: 5;
        padding-top: 70px;
    }
}

@media (min-width: 1200px) {
    .cc-awards {
        --cc-awards-cols: 6;
        --cc-awards-gap: 30px;
        padding-top: 80px;
    }
}

/* The box a slide width is measured against. It has to be a query container
 * rather than a percentage parent: the marquee script wraps the strip in a
 * max-content track, so a percentage on the item would resolve against a box
 * that is itself sized by the items. */
.cc-awards > .container {
    container-type: inline-size;
}

/* The synced set holds one block, so core's inter-block gap separates nothing,
 * and the scroller's own margin would double up with the padding above. */
.cc-awards .builder-block {
    margin-bottom: 0;
}

.cc-awards .builder-logo-strip-scroller {
    margin: 0;
}

.cc-awards .builder-block__heading {
    text-align: center;
    margin-bottom: 40px;
}

.cc-awards .builder-logo-strip {
    gap: var(--cc-awards-gap);
}

/* The plain width is the fallback for a browser without container query units
 * and must stay above the calc, which such a browser drops. */
.cc-awards .builder-logo-strip__item {
    flex: 0 0 auto;
    justify-content: center;
    width: 160px;
    width: calc((100cqw - (var(--cc-awards-cols) - 1) * var(--cc-awards-gap)) / var(--cc-awards-cols));
}

/* Bootstrap's .img-fluid, which is all the legacy slide gave these logos: fill
 * the slide, never upscale past the artwork's own size. Core's height cap has to
 * go rather than be raised: the Legal 500 badges are portrait, so any height cap
 * sets their width instead and the row stops landing on its columns. */
.cc-awards .builder-logo-strip__item img {
    width: auto;
    height: auto;
    max-width: 100%;
    max-height: none;
}

/* Core's pause control has no counterpart on live, which autoplays with no way
 * to stop it. It stays, on WCAG 2.2.2 grounds, but sits centred under the strip,
 * where it reads as a control rather than as a stray mark off the first logo.
 * The 44px target is core's and must not be shrunk. */
.cc-awards .builder-logo-strip__pause {
    display: block;
    margin: 10px auto -54px;
    color: var(--color-primary);
}

/* Live puts 120px between the last logo and the footer logo, where the rest of
 * the site's sections sit 4rem apart. The pause control above hangs into that
 * gap (its negative margin cancels its 54px) rather than adding to it, and
 * core's footer padding goes, or the gap is 224px. Scoped to the adjacency so
 * an install with the strip switched off keeps the ordinary gap. */
.cc-awards + .cc-footer {
    margin-top: 120px;
    padding-top: 0;
}

/* ── Footer ───────────────────────────────────────────────────────────────────
 * A single centred column, not core's three-column grid. Core's defaults assume
 * a dark footer (grey text, a dark hairline), so several of them have to be
 * unset rather than merely added to.
 *
 * Every measurement is live's (.footer in style.css): the logo at its own
 * 523px, the regulator line and the link rows at a fixed 16px, the contact
 * lines at body size with their links bold and underlined, 48px from the
 * regulator to the contact lines, 49 and 52px either side of the LinkedIn
 * square, link rows 10px apart, and 48px under the copyright.
 */
/* Live puts nothing under a page's last section: the next thing is the
 * accreditation strip's own top padding, or on a profile the footer's 120px. */
.page-body {
    padding-bottom: 0;
}

.cc-footer {
    text-align: center;
    margin-top: 0;
    padding-top: 120px;
    font-size: 1rem;
}

.cc-footer .agency-credit {
    margin-top: 0;
}

.cc-footer__brand img {
    display: block;
    width: 523px;
    max-width: 100%;
    height: auto;
    margin: 0 auto;
}

.cc-footer__regulator {
    font-size: 16px;
    margin: 0 0 48px;
}

.cc-footer__contact p {
    margin: 0 0 16px;
}

.cc-footer__contact a {
    font-weight: 700;
    text-decoration: underline;
}

.cc-footer__contact a:hover {
    text-decoration: none;
}

/* 49px, not the 33px of live's padding: the address paragraph's 16px margin
 * collapses into this one rather than adding to it. */
.cc-footer__social {
    margin: 49px 0 52px;
    line-height: 0;
}

.cc-footer__social a {
    display: inline-block;
    color: var(--color-dark, var(--color-primary));
}

/* News & Events sits on a row of its own above the policy links, as live's
 * footer has it in a list of its own. It is the menu's first item, so the
 * split follows the item: reorder the footer menu and the row goes with it. */
.cc-footer__nav ul {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-wrap: wrap;
    justify-content: center;
    gap: 20px;
}

.cc-footer__nav li:first-child {
    flex-basis: 100%;
}

.cc-footer__nav a {
    display: block;
    padding: 4px 0;
    color: var(--footer-link-color, var(--color-primary));
    font-size: 16px;
}

/* Core's .footer-bottom draws a dark-footer hairline and a grey that is
 * invisible on white. Live has no rule there at all. */
.cc-footer__copyright {
    border-top: 0;
    color: var(--footer-color, var(--color-primary));
    margin-top: 10px;
    padding: 0 0 48px;
    font-size: 16px;
}

/* Core colours the Cookie settings link with the brand gold (--color-secondary,
 * #bea154), which is 2.5:1 on this white footer and fails WCAG AA's 4.5:1.
 * #8a7234 is the same hue and saturation darkened just past the line (4.63:1);
 * any lighter fails. site.css loads after frontend.css, so this wins at equal
 * specificity. */
.cc-footer__copyright .cms-cookie-settings {
    color: #8a7234;
}

/* ── The credit strip ─────────────────────────────────────────────────────────
 * Core's shared agency credit bar (colours and position: Site Settings →
 * Agency Credit; black, #d9d9d9 mark and words, centred). The legacy strip was
 * measured at 77px tall with tracked lettering, kept here so it still matches.
 */
.cc-footer .agency-credit__inner {
    min-height: 77px;
}

.cc-footer .agency-credit__link {
    letter-spacing: 0.04em;
}

/* Post-nominals (KC, MCIArb) sit inside the name, on the people cards and on
 * the profile banner alike, so they are sized against whatever heading holds
 * them rather than to a step of their own. */
.cc-post-nominals {
    font-size: 0.6em;
    letter-spacing: 0.04em;
}

/* ── Barrister profile: the banner ────────────────────────────────────────────
 * Live's .inner-banner.detail-banner: the portrait beside the name, on the
 * same wash the header and the page title band wear, so the three read as one
 * block. This page carries no title band, which is why the wash is repeated
 * here rather than inherited: live's staff pages drop the chambers-name
 * eyebrow and give the space to the photo.
 *
 * The photo column is capped at live's 400px rather than left to the grid: a
 * portrait stretched to a third of a 1600px viewport is a different picture.
 *
 * No bottom padding: live's banner ends where the portrait does, so the photo
 * stands on the edge of the wash. The columns are Bootstrap's col-lg-4 and
 * col-lg-8 with the 24px gutter, stacking below 992 as live's do, and the gap
 * under the band is live's section step plus the 50px its markup adds inline.
 */
.cc-profile-banner {
    background: var(--cc-banner-wash);
    padding: var(--cc-banner-top) 0 0;
    margin-bottom: calc(var(--cc-band, 100px) + 50px);
}

/* The gap above is the whole of it: core's page body would add 2rem more. */
.cc-profile-banner + .page-body {
    padding-top: 0;
}

.cc-profile-banner__grid {
    display: grid;
    grid-template-columns: minmax(0, 4fr) minmax(0, 8fr);
    gap: 24px;
    align-items: center;
}

.cc-profile-banner__photo img {
    display: block;
    width: 100%;
    max-width: 400px;
    height: auto;
}

/* Name and year of call share a baseline, as on live. flex-end rather than
 * baseline: the two have different line heights and baseline alignment leaves
 * the year floating above the name's descenders. */
.cc-profile-banner__title {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-end;
    gap: 12px;
    line-height: 1;
    margin-bottom: 20px;
}

.cc-profile-banner__title h1 {
    margin: 0;
}

/* Live's own 0.8em lift. Without it flex-end sets the year against the h1's
 * descender space and it drops half a line below the name. */
.cc-profile-banner__called {
    margin: 0 0 0.8em;
}

/* Two halves, not space-between: live puts the contact details in one col-md-6
 * and the social links in the next, so the icons start at the midpoint of the
 * detail column rather than at its right edge. */
.cc-profile-banner__row {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(240px, 1fr));
    align-items: end;
    gap: 12px 24px;
}

.cc-profile-banner__facts p {
    margin: 0 0 10px;
}

/* Underlined on live, where they are the only two links in the band and the
 * body link colour alone would not mark them out against the wash. */
.cc-profile-banner__facts a {
    text-decoration: underline;
}

.cc-profile-banner__social {
    display: flex;
    align-items: center;
    gap: 12px 40px;
}

/* Live's icon is a 52px glyph in a line box 1.636 times as tall, and that box
 * is what the row and the pdf button line up against, so it is kept: the
 * padding makes the 52px mark an 85px box with the mark at its centre. */
.cc-profile-banner__icon {
    display: block;
    padding-block: calc(52px * 0.318);
    color: var(--color-primary);
}

.cc-profile-banner__icon svg {
    display: block;
}

/* Live's CV button: a pill outline in the primary that fills on hover, the
 * same shape the people search wears. Measured off live at 12px/40px, opening
 * to 14px/60px above 1600 where its own type ladder steps up. Line height 1.2,
 * not live's declared 1: live's link is inline, so its box is the font's own
 * content area, about 1.2em, and that is the 52px pill a visitor sees. */
.cc-profile-banner__cv {
    display: inline-block;
    padding: 12px 40px;
    border: 2px solid var(--color-primary);
    border-radius: 32px;
    background-color: transparent;
    color: var(--color-primary);
    font-weight: 700;
    line-height: 1.2;
    text-decoration: none;
    white-space: nowrap;
    transition: background-color 0.32s ease-in-out, color 0.32s ease-in-out;
}

.cc-profile-banner__cv:hover,
.cc-profile-banner__cv:focus-visible {
    background-color: var(--color-primary);
    color: #fff;
}

@media (min-width: 1600px) {
    .cc-profile-banner__cv { padding: 14px 60px; }
}

@media (max-width: 991.98px) {
    .cc-profile-banner__grid {
        grid-template-columns: 1fr;
        gap: 16px;
    }

    .cc-profile-banner__detail {
        padding-bottom: 16px;
    }
}

/* ── Barrister profile: bio and lead recommendation ───────────────────────────
 * Live gives the bio the full width and drops to two thirds only when there is
 * a recommendation to set beside it, so the modifier carries the split rather
 * than the base class.
 */
/* pb-4 on live's bio column: the 24px before "Find out more". */
.cc-profile-lead {
    padding-bottom: 24px;
}

.cc-profile-lead--with-quote {
    display: grid;
    grid-template-columns: minmax(0, 7fr) minmax(0, 5fr);
    gap: 24px;
    align-items: start;
}

@media (max-width: 991px) {
    .cc-profile-lead--with-quote {
        grid-template-columns: 1fr;
        gap: 2rem;
    }
}

.cc-profile-quote {
    display: flex;
    margin: 0;
}

/* The serif glyph is live's, at the display face rather than the body one. */
.cc-profile-quote__mark {
    font-family: var(--font-h1, serif);
    font-size: 72px;
    line-height: 1;
    padding-right: 16px;
    margin-left: -0.1em;
    color: var(--color-primary);
}

.cc-profile-quote__body {
    min-width: 0;
}

/* Live's .quote-text h4: the display face on the quotation ramp. */
.cc-profile-quote__text {
    font-family: var(--font-h1, inherit);
    font-size: var(--cc-quote-size);
    line-height: 1.556;
    margin: 0 0 20px;
}

/* The gold underline sits under the name only, so it has to be on an
 * inline-block: on the block <p> it would rule the whole column. */
.cc-profile-quote__cite {
    display: inline-block;
    margin: 0;
    padding: 10px 0;
    border-bottom: 2px solid var(--color-secondary);
}

.cc-profile-quote__cite cite {
    font-style: normal;
    font-weight: 700;
}

/* Bootstrap's ps-xl-4 and ps-xxl-5 on live's quote column. */
@media (min-width: 1200px) { .cc-profile-lead__aside { padding-left: 24px; } }
@media (min-width: 1400px) { .cc-profile-lead__aside { padding-left: 48px; } }

@media (min-width: 992px) {
    .cc-profile-quote__mark {
        font-size: 102px;
    }
}

/* ── Barrister profile: accreditation badges ──────────────────────────────────
 * The barrister's own, distinct from the strip every page carries above the
 * footer. Capped at two across beside the quote, as live's .two-awards is.
 */
.cc-profile-badges {
    display: flex;
    flex-wrap: wrap;
    gap: 16px 24px;
    align-items: flex-start;
}

/* Live's .two-awards: two badges across, each at most half the column. Written
 * as a grid rather than as a percentage max-width on a flex child, because that
 * percentage resolves against the flex base size and lands nowhere near half.
 * The cell carries the halving; the badge only has to fit its cell. */
.cc-profile-badges--aside {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    justify-items: start;
    margin-top: 2rem;
}

/* Sized by width alone. A height cap as well would fight it: the badges are
 * portrait crops, so capping the height sets the width and the badge collapses
 * to a thumbnail. */
.cc-profile-badges--aside .cc-profile-badges__logo {
    width: auto;
    height: auto;
    max-width: 100%;
    max-height: none;
}

.cc-profile-badges__item {
    margin: 0;
    max-width: 200px;
}

.cc-profile-badges__item figcaption {
    margin-top: 0.5rem;
    font-size: 0.8rem;
}

/* In the accordion panel the badges sit in a row with their names under them,
 * so they are capped by height (live's own 80px) and left to find their width. */
.cc-profile-badges__item .cc-profile-badges__logo {
    width: auto;
    height: auto;
    max-width: 100%;
    max-height: 80px;
}

/* ── Accordions ──────────────────────────────────────────────────────────────
 * Live draws every accordion the same way from one `.accordion` rule, and it
 * has exactly three: the Direct Access FAQ, the contact page's directions and
 * the profile's "Find out more". Core renders all three as details.faq-item,
 * so this is that rule once, unscoped, rather than the same block per page.
 *
 * Every measurement is the legacy stylesheet's own (_pages.scss `.accordion`):
 * 2px primary rules above and below each row rather than core's grey hairline,
 * the label the display face at 26px rather than bold body copy, 26px/16px
 * around it, and the answer 10px under the label with 30px beneath.
 *
 * The disclosure behaviour, the open animation and the ARIA all stay core's;
 * only the drawing is live's. The colours come from the accordion theme tokens
 * (see CollegeChambersThemeSeeder), so nothing here restates a brand value.
 */
.faq-item {
    border-bottom: 2px solid var(--color-primary);
}

/* Every run of questions opens on a rule, not just the first on the page: the
   FAQ page groups its questions under category headings, and a group that
   started bare would read as a continuation of the one above it. */
.faq-item:first-of-type,
.faq-category + .faq-item {
    border-top: 2px solid var(--color-primary);
}

/* The right padding is the chevron's 16px inset and 20px width and no more:
 * live's question text runs up to the icon, and a wider gutter rewraps the
 * longer questions onto a second line on a phone. */
.faq-item > summary {
    font-family: var(--font-h2, var(--font-h1, inherit));
    font-size: 26px;
    font-weight: 400;
    line-height: 1.2;
    padding: 26px 40px 26px 16px;
}

/* Live's own chevron, its path traced into a clip-path so the shape is exact
   and the gold still comes from the token. A rotated square is the cheaper
   trick and is what stood here, but it can only ever open at 90 degrees and
   live's V is far sharper. The box is Bootstrap's 1.25rem icon width at live's
   16px root; the height holds the source SVG's 9.143:8.143 ratio. */
.faq-item > summary::after,
.faq-item[open] > summary::after {
    content: "";
    right: 16px;
    width: 20px;
    height: 17.8px;
    background-color: var(--accordion-icon, var(--color-secondary));
    clip-path: polygon(50.45% 100%, 0 9.75%, 14.57% 0, 50.34% 63.94%, 85.34% 0.09%, 100% 9.7%);
    transform: translateY(-50%);
}

.faq-item[open] > summary::after {
    transform: translateY(-50%) rotate(180deg);
}

/* 16px rather than the 20px Bootstrap gives the body, so the answer lines up
   under its question. Live inherits that mismatch and indents by 4px. */
.faq-answer {
    padding: 10px 16px 30px;
}

/* Live's rows butt together, so the 2px rules read as one continuous set.
   Core spaces them, which leaves every rule floating on its own. */
.builder-accordion {
    gap: 0;
}

/* Live's arrangement is two equal Bootstrap columns with the standard 24px
   gutter, not core's 40/60 split. Gated on the breakpoint rather than left
   flat: core stacks the row below 769px from a media query in frontend.css,
   and site.css loads after it, so an unconditional rule here would outrank
   that one and the intro would sit in a half-width column on a phone. */
@media (min-width: 769px) {
    .builder-accordion-row,
    .builder-accordion-row--intro-right {
        grid-template-columns: 1fr 1fr;
        gap: 24px;
    }
}

/* ── Barrister profile: "Find out more" ──────────────────────────────────────
 * The rows themselves are core's .faq-item, drawn by the accordion rules
 * above. Only the section around them is this page's.
 */
/* Bootstrap's pt-5: 48px at every width. */
.cc-profile-more {
    margin-top: 48px;
}

/* Live's label is a bold paragraph in the body face, not a heading: the
 * serif would make it read as a section title over the accordion. */
.cc-profile-more__title {
    font-family: var(--font-family, inherit);
    font-size: 1rem;
    font-weight: 700;
    letter-spacing: normal;
    line-height: var(--lh-body, 1.64);
    margin: 0 0 24px;
}

/* Practice areas: live's navy squares, in a wrapping grid rather than its
 * Swiper carousel, with the carousel's own column ladder (expertiseSwiperTwo in
 * live's custom.js): 2 across from 480 with a 16px gap, 3 at 768 / 20, 4 at
 * 992 / 24, 5 at 1200 / 30, 6 at 1400 / 30. Under 480 live shows one card per
 * view and swipes, and a wrap there would stack every area into a column
 * thousands of pixels long, so it stays a swiped row, the next card showing
 * at the edge so the row reads as one that moves. aspect-ratio holds the
 * square live gets from a padding hack, and the title sits on the card's foot.
 * The space above and below is live's section step (pt-100) and its 72px. */
.cc-practice-grid {
    --cc-cols: 2;
    --cc-gap: 16px;
    list-style: none;
    margin: 0;
    padding: var(--cc-band, 100px) 0 72px;
    display: grid;
    grid-template-columns: repeat(var(--cc-cols), minmax(0, 1fr));
    gap: var(--cc-gap);
}

@media (min-width: 768px)  { .cc-practice-grid { --cc-cols: 3; --cc-gap: 20px; } }
@media (min-width: 992px)  { .cc-practice-grid { --cc-cols: 4; --cc-gap: 24px; } }
@media (min-width: 1200px) { .cc-practice-grid { --cc-cols: 5; --cc-gap: 30px; } }
@media (min-width: 1400px) { .cc-practice-grid { --cc-cols: 6; } }

@media (max-width: 479.98px) {
    .cc-practice-grid {
        grid-template-columns: none;
        grid-auto-flow: column;
        grid-auto-columns: 85%;
        overflow-x: auto;
        scroll-snap-type: x mandatory;
        overscroll-behavior-x: contain;
    }

    .cc-practice-grid > * {
        scroll-snap-align: start;
    }
}

.cc-practice-card {
    display: flex;
    flex-direction: column;
    justify-content: flex-end;
    aspect-ratio: 1;
    padding: 24px;
    background-color: var(--color-primary);
    color: #fff;
}

@media (min-width: 1400px) { .cc-practice-card { padding: 30px; } }

/* live's .t-small: a fixed 24px at every width, unlike the home cards. */
.cc-practice-card__title {
    font-size: 24px;
    line-height: 1.2;
    margin: 0;
    color: inherit;
}

/* live's .link-small: bold 16px on a gold rule with 10px above and below. The
 * rule is the only warm mark on the tile and it is what carries the click. */
.cc-practice-card__link {
    align-self: flex-start;
    padding: 10px 0;
    border-bottom: 2px solid var(--color-secondary);
    color: inherit;
    font-size: 16px;
    font-weight: 700;
    text-decoration: none;
}

.cc-practice-card__link:hover,
.cc-practice-card__link:focus-visible {
    color: var(--color-secondary);
    border-bottom-color: #fff;
}

/* Qualifications and Memberships share one panel in two columns, as on live. */
.cc-profile-columns {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(260px, 1fr));
    gap: 1rem 2.5rem;
}

.cc-profile-columns h3 {
    font-size: 1.25rem;
    margin: 0 0 0.5rem;
}

/* Legacy semicolon lists. Marked up as lists, drawn as the stacked lines live
 * gets from <br>: the entries are a set, but they are not bulleted there. */
.cc-profile-list {
    list-style: none;
    margin: 0;
    padding: 0;
}

.cc-profile-list li {
    padding: 0.15rem 0;
}

.cc-profile-posts,
.cc-profile-quotes {
    list-style: none;
    margin: 0;
    padding: 0;
}

.cc-profile-posts__item,
.cc-profile-quotes__item {
    padding: 0.75rem 0;
    border-bottom: 1px solid var(--color-border);
}

.cc-profile-posts__item:last-child,
.cc-profile-quotes__item:last-child {
    border-bottom: 0;
}

.cc-profile-posts__title {
    font-size: 1.1rem;
    margin: 0 0 0.25rem;
}

.cc-profile-posts__summary {
    margin: 0;
    font-size: 0.95rem;
}

.cc-profile-quotes__item p {
    margin: 0;
}

/* The read-more disclosure: the cue is the marker, so the native triangle goes
 * and the excerpt is swapped for the full quote on open rather than stacked
 * above it. The summary itself stays visible either way, or opening it would
 * take the control away and the quote could never be collapsed again. */
.cc-profile-quotes__more > summary {
    cursor: pointer;
    list-style: none;
}

.cc-profile-quotes__more > summary::-webkit-details-marker {
    display: none;
}

.cc-profile-quotes__more[open] .cc-profile-quotes__excerpt,
.cc-profile-quotes__more[open] .cc-profile-quotes__cue--more,
.cc-profile-quotes__more:not([open]) .cc-profile-quotes__cue--less {
    display: none;
}

.cc-profile-quotes__cue {
    white-space: nowrap;
    text-decoration: underline;
    color: var(--color-primary);
}

.cc-profile-quotes__cite {
    margin-top: 0.4rem !important;
    font-size: 0.9rem;
}

.cc-profile-quotes__cite cite {
    font-style: normal;
}
/* ── Nav: dropdown carets ─────────────────────────────────────────────────────
 * The legacy nav marks every dropdown parent with a chevron. Only a parent
 * that owns a submenu carries aria-expanded (core sets it on the link, or on
 * the button a heading parent renders as), so that attribute IS the "has a
 * dropdown" signal and no markup change is needed. Drawn with borders in
 * currentColor so it follows the nav link colour, and flipped when the
 * disclosure is open. Desktop only: below 768px core draws its own mobile
 * affordance on the same ::after, and two writers there would fight.
 */
@media (min-width: 769px) {
    .nav-main > li > a[aria-expanded]::after,
    .nav-main > li > button.nav-label[aria-expanded]::after {
        content: "";
        display: inline-block;
        width: 0.33em;
        height: 0.33em;
        margin-left: 0.3em;
        border-right: 1.5px solid currentColor;
        border-bottom: 1.5px solid currentColor;
        transform: rotate(45deg) translateY(-0.2em);
        transition: transform 0.15s ease;
    }

    .nav-main > li > a[aria-expanded="true"]::after,
    .nav-main > li > button.nav-label[aria-expanded="true"]::after {
        transform: rotate(225deg) translateY(0.05em);
    }
}

/* ── Smooth disclosures ───────────────────────────────────────────────────────
 * Core reveals nav dropdowns and accordions by toggling display, which cannot
 * animate. These rules take over ONLY the presentation of the reveal; the
 * trigger logic (hover, :focus-within, .sub-open, [open]) stays core's.
 *
 * Keyboard/AT behaviour is preserved deliberately: hidden submenus use
 * visibility:hidden, which removes their links from the tab order exactly as
 * display:none did — :focus-within on the parent still reveals them for
 * keyboard users. Selectors are kept separate, not grouped with :is(), for
 * the same reason core's are.
 */

/* Desktop dropdowns: fade + rise. Core's reveal rules only ever set
 * display:block, which now matches the resting state, so visibility/opacity
 * below are the single mechanism. */
@media (min-width: 769px) {
    .nav-item > .nav-sub,
    .nav-heading > .nav-sub {
        display: block;
        visibility: hidden;
        opacity: 0;
        transform: translateY(8px);
        transition: opacity 0.18s ease, transform 0.18s ease, visibility 0s linear 0.18s;
    }

    .nav-item:hover > .nav-sub { visibility: visible; opacity: 1; transform: none; transition: opacity 0.18s ease, transform 0.18s ease; }
    .nav-item:focus-within > .nav-sub { visibility: visible; opacity: 1; transform: none; transition: opacity 0.18s ease, transform 0.18s ease; }
    .nav-heading:hover > .nav-sub { visibility: visible; opacity: 1; transform: none; transition: opacity 0.18s ease, transform 0.18s ease; }
    .nav-heading:focus-within > .nav-sub { visibility: visible; opacity: 1; transform: none; transition: opacity 0.18s ease, transform 0.18s ease; }
    .nav-preview-open > .nav-sub { visibility: visible; opacity: 1; transform: none; transition: opacity 0.18s ease, transform 0.18s ease; }
}

/* Mobile submenus: slide open under the parent. height:auto only animates
 * where interpolate-size is supported (declared below); elsewhere the toggle
 * is instant, exactly as before. */
@media (max-width: 768px) {
    .nav-item > .nav-sub,
    .nav-heading > .nav-sub {
        display: block;
        height: 0;
        overflow: hidden;
        visibility: hidden;
        transition: height 0.25s ease, visibility 0s linear 0.25s;
    }

    .nav-item.sub-open > .nav-sub,
    .nav-heading.sub-open > .nav-sub {
        height: auto;
        visibility: visible;
        transition: height 0.25s ease;
    }
}

/* Lets height/block-size transition to auto in supporting browsers
 * (progressive: unsupported browsers simply toggle instantly). */
:root {
    interpolate-size: allow-keywords;
}

/* Accordions — the FAQ page, the accordion block (same .faq-item markup) and
 * the profile's collapsible sections are all native <details>: animate the
 * content panel sliding open, and ease the +/− marker. */
details.faq-item::details-content,
details.cc-profile-quotes__more::details-content {
    block-size: 0;
    overflow-y: clip;
    transition: block-size 0.25s ease, content-visibility 0.25s allow-discrete;
}

details.faq-item[open]::details-content,
details.cc-profile-quotes__more[open]::details-content {
    block-size: auto;
}

.faq-item > summary::after {
    transition: transform 0.2s ease, color 0.2s ease;
}

/* ── People index ─────────────────────────────────────────────────────────────
 * Live's people.php results, replicated: the filter row (expertise select,
 * "or", name box, two pill buttons), then a Bootstrap row of cards — one
 * column, two from 768px, three from 1200px, 24px gutters, 50px above and
 * below each card — each card a photo and a text column of equal width with
 * 24px between them, and the circular pagination under it. Every number is
 * the legacy stylesheet's own (#filter, #team-member, .team-member,
 * .link-small, .paginationLink); the class names are this site's, so nothing
 * here collides with core's .card and .staff-card rules. The request side
 * (the views, the filters, twelve a page) is App\Support\ChambersPeople.
 */
.cc-people__filter {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 10px 20px;
}

@media (min-width: 992px) { .cc-people__filter { flex-wrap: nowrap; } }
@media (min-width: 1600px) { .cc-people__filter { gap: 10px 30px; } }

.cc-people__filter > label {
    width: 100%;
    margin: 0;
    font-weight: 700;
}

@media (min-width: 992px) { .cc-people__filter > label { width: auto; white-space: nowrap; } }

.cc-people__or {
    width: 100%;
    padding: 0 16px;
}

@media (min-width: 576px) { .cc-people__or { width: auto; padding: 0; } }

.cc-people__field {
    flex: 1 1 auto;
    width: 100%;
}

@media (min-width: 576px) { .cc-people__field { width: auto; } }
@media (min-width: 768px) { .cc-people__field { width: calc(50% - 40px); } }
@media (min-width: 992px) { .cc-people__field { width: auto; } }

/* A gold rule under each control and nothing else: no box, no fill, no
 * radius. Live also removes the focus outline; not reproduced (see the focus
 * rule above). */
.cc-people__field select,
.cc-people__field input {
    width: 100%;
    padding: 10px 16px;
    border: 0;
    border-bottom: 2px solid var(--color-secondary);
    border-radius: 0;
    background: transparent;
    box-shadow: none;
    font: inherit;
    color: inherit;
}

.cc-people__action { padding-top: 10px; }

@media (min-width: 768px) { .cc-people__action { padding-top: 0; } }

/* The pill buttons. "clear" is a link on live too (a button inside an
 * anchor); here it is the anchor alone, dressed the same. */
.cc-people__button {
    display: inline-block;
    padding: 12px 40px;
    border: 2px solid var(--color-primary);
    border-radius: 32px;
    background: transparent;
    color: var(--color-primary);
    font: inherit;
    font-weight: 700;
    line-height: 1;
    text-decoration: none;
    cursor: pointer;
    transition: background-color 0.32s ease-in-out, color 0.32s ease-in-out;
}

@media (min-width: 1600px) { .cc-people__button { padding: 14px 60px; } }

.cc-people__button:hover,
.cc-people__button:focus-visible {
    background: var(--color-primary);
    color: #fff;
    text-decoration: none;
}

.cc-people__grid {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 0 24px;
    margin: 0;
    padding: 0;
    list-style: none;
}

@media (min-width: 768px) { .cc-people__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 1200px) { .cc-people__grid { grid-template-columns: repeat(3, minmax(0, 1fr)); } }

.cc-people__item { padding: 50px 0; }

.cc-person {
    display: flex;
    gap: 24px;
}

.cc-person__image,
.cc-person__content {
    flex: 1 1 0;
    min-width: 0;
}

/* Natural size capped at the column, exactly live's img-fluid: the portraits
 * are all wider than the column, so each fills it at its own proportions. */
.cc-person__image a { display: block; }

.cc-person__image img {
    max-width: 100%;
    height: auto;
}

.cc-person__content {
    font-size: calc(var(--font-size-base, 20px) * 0.8);
}

/* The name is live's h2 ladder (32 / 38 / 42px) off the h2 size token. */
.cc-person__name {
    margin: 0 0 8px;
    font-size: calc(var(--font-size-h2, 42px) * 0.762);
}

@media (min-width: 768px) { .cc-person__name { font-size: calc(var(--font-size-h2, 42px) * 0.905); } }
@media (min-width: 1200px) { .cc-person__name { font-size: var(--font-size-h2, 42px); } }

.cc-person__name a {
    color: inherit;
    text-decoration: none;
    transition: color 0.32s ease-in-out;
}

.cc-person__name a:hover,
.cc-person__name a:focus-visible {
    color: var(--color-secondary);
    text-decoration: none;
}

.cc-person__role { margin: 0; }

.cc-person__detail { margin: 0 0 16px; }

.cc-person__more a {
    display: inline-block;
    padding: 10px 0;
    border-bottom: 2px solid var(--color-secondary);
    color: var(--color-primary);
    font-weight: 700;
    text-decoration: none;
    transition: color 0.32s ease-in-out, border-color 0.32s ease-in-out;
}

.cc-person__more a:hover,
.cc-person__more a:focus-visible {
    color: var(--color-secondary);
    border-bottom-color: var(--color-primary);
    text-decoration: none;
}

.cc-people__empty { padding-top: 50px; }

/* ── Practice area: the barristers who work in it ─────────────────────────────
 * Legacy people_ADR_Expertise.php, which is people.php's grid with the filter
 * row and the pagination taken off — the same .team-member cards off the same
 * block of CSS, which is why this section adds a wrapper and nothing else.
 *
 * Live measures its 80px from where the page copy stops, and the page body
 * carries its own bottom padding, so the two have to be resolved or the band
 * sits a third lower than live's. The band owns the gap; the body gives it up.
 * A browser without :has() keeps both and lands 48px low, which is a slightly
 * roomier page and not a broken one.
 */
.page-body:has(+ .cc-service-people) {
    padding-bottom: 0;
}

.cc-service-people {
    padding-top: 80px;
}

/* Pagination: 52px circles 15px apart, the current page and a hovered one
 * ringed in the brand colour, the arrows a size up. */
.cc-people__pagination ul {
    display: flex;
    flex-wrap: wrap;
    justify-content: center;
    gap: 15px;
    margin: 0;
    padding: 0;
    list-style: none;
}

.cc-people__page,
.cc-people__gap {
    display: flex;
    align-items: center;
    justify-content: center;
    height: 52px;
    font-size: 24px;
    color: var(--color-primary);
}

.cc-people__page {
    width: 52px;
    border: 2px solid transparent;
    border-radius: 50%;
    text-decoration: none;
    transition: border-color 0.32s ease-in-out;
}

.cc-people__page:hover,
.cc-people__page:focus-visible,
.cc-people__page[aria-current] {
    border-color: var(--color-primary);
    text-decoration: none;
}

.cc-people__page--nav { font-size: 32px; }

.cc-people__page svg {
    width: 1em;
    height: 1em;
}

/* ── Maps ──────────────────────────────────────────────────────────────────────────
 * Live's contact.php puts the map OUTSIDE its container
 * (`section.map-sec.pt-100 > div.map.ratio.ratio-21x9`), so it runs the whole
 * viewport width as a 21:9 letterbox, floored at 280px so a phone still gets a
 * map rather than a strip. Core's block sits on the container grid at a fixed
 * height instead, and that is the whole of the difference this section closes.
 *
 * Scoped to the full-width Map block alone. `builder-block--map_text` and
 * `--map_image` are separate class names, so the two side-by-side layouts keep
 * the container grid: a half-width map is the only place their copy column
 * reads.
 *
 * The breakout is core's own u-full-bleed technique, absorbed by the
 * `body { overflow-x: clip }` that helper relies on. It is repeated here rather
 * than ticked on the block's Design tab because live has no map that is not
 * full width, and the helper's 20px gutter would inset one that is.
 */
.builder-block--map {
    box-sizing: border-box;
    width: 100vw;
    max-width: 100vw;
    margin-left: calc(50% - 50vw);
    margin-right: calc(50% - 50vw);
    margin-top: 56px;
}

/* Live's .pt-100 scale. It collapses with the preceding block's --block-gap
   rather than adding to it, which is why this reads as a plain margin. */
@media screen and (min-width: 768px) {
    .builder-block--map { margin-top: 80px; }
}

@media screen and (min-width: 1200px) {
    .builder-block--map { margin-top: 100px; }
}

/* An editor's heading on a bled block would otherwise start at the screen edge.
   Core's own expression for putting a bled carousel's heading back on the
   container grid, reused so the two behave alike. */
.builder-block--map > .builder-block__heading,
.builder-block--map > .builder-block__eyebrow {
    padding-inline: max(12px, calc(50% - var(--cc-col) / 2));
}

/* 42.857vw is 9/21 of the viewport, which at this width is the block's own
   width: live's ratio expressed as a definite height, so the iframe's
   height:100% still resolves against it. The !important is load-bearing. It
   beats the inline height the block's Height select writes, and without it a
   400px band is stretched across the full screen. That select is therefore
   inert on this site, deliberately: a fixed height at viewport width is a
   different picture on every screen, which is why live chose a ratio. The
   radius goes with the gutter, an edge-to-edge band having no corners to
   round. */
.builder-block--map .builder-map {
    height: max(280px, 42.857vw) !important;
    border-radius: 0;
}

/* ── Forms ────────────────────────────────────────────────────────────────────
 * None of this could be read off the legacy stylesheet: live's forms are a
 * hosted FormNX embed and carry their own CSS. The values are that form's own
 * Design tab and custom-CSS box, recorded verbatim in
 * `Documents/legacy-migration/FORMNX-DIRECT-ACCESS-REBUILD.md` §4 and §5 —
 * pill fields with a 2px navy edge and no other chrome, 18px field text, the
 * placeholder doing the labelling, and a large navy pill Send that turns gold.
 *
 * The chrome is site-wide because it is the site's form look, not one page's.
 * Only the Direct Access layout further down is scoped to that form.
 *
 * Navy and gold stay in the theme. The two values below are field chrome and
 * not brand — FormNX's own neutrals — so they are named once here and read
 * everywhere else, which is the same bargain the rest of this file makes.
 */
:root {
    --cc-field-ink: #525760;
    --cc-field-rule: rgba(82, 87, 96, 0.25);
}

/* Live's embed is transparent and sits directly on the page. Core's warm panel
   and its 2rem of padding would box a form that is meant to be the page. */
.cms-form-wrap {
    margin-top: 0;
    padding: 0;
    background: none;
    border-radius: 0;
}

/* A twelve-column track with live's 24px gutter, so a half-width field is
   Bootstrap's col-md-6 to the pixel and an odd one out (Post Code, Company
   Name) lands alone on the left rather than stretching. */
.cms-form-wrap .form-row {
    grid-template-columns: repeat(12, 1fr);
    column-gap: 24px;
    row-gap: 16px;
}

.cms-form-wrap .form-row > .form-group {
    grid-column: span 6;
    margin-bottom: 0;
}

.cms-form-wrap .form-group {
    margin-bottom: 16px;
}

.cms-form-wrap .form-group > label,
.cms-form-wrap .form-fieldset > legend {
    margin-bottom: 0.35rem;
    font-family: var(--font-family);
    font-size: 15px;
    font-weight: 700;
    line-height: 1.35;
    color: var(--color-primary);
}

/* Checkboxes, radios and file inputs are deliberately outside this: a pill
   border and 1.1rem of side padding on a checkbox draws a navy lozenge with a
   tick lost in the middle of it. */
.cms-form-wrap .form-group input:not([type="checkbox"]):not([type="radio"]):not([type="file"]),
.cms-form-wrap .form-group select,
.cms-form-wrap .form-group textarea {
    padding: 0.5rem 1.1rem;
    font-size: 18px;
    color: var(--cc-field-ink);
    background-color: var(--color-page-bg, #fff);
    border: 2px solid var(--color-primary);
    border-radius: 2rem;
}

/* A pill is wrong on a box six lines deep; live rounds it and leaves it. */
.cms-form-wrap .form-group textarea {
    border-radius: 1.25rem;
    resize: vertical;
}

/* The placeholder is the label on most of these fields, so it cannot be left to
   the browser default, which ranges from near-black to barely there. Mixed off
   the field ink rather than named separately: the two must stay related, and at
   72% this still clears 4.5:1 on white. Firefox dims placeholders on top of the
   colour, which is what opacity is undoing. */
.cms-form-wrap .form-group ::placeholder {
    color: color-mix(in srgb, var(--cc-field-ink) 72%, #fff);
    opacity: 1;
}

/* Live's chevron: a 2px open V, not core's filled caret. The stroke repeats
   --cc-field-ink because a data URI cannot read a custom property; if that
   value ever moves, move it here too. */
.cms-form-wrap .form-group select {
    background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' width='14' height='9'%3E%3Cpath d='M1 1l6 6 6-6' fill='none' stroke='%23525760' stroke-width='2'/%3E%3C/svg%3E");
    background-position: right 1.1rem center;
    background-size: 14px 9px;
    padding-right: 2.6rem;
}

/* Live's error: a pink lozenge under the field rather than loose red text. The
   tint is mixed from the theme's error colour so the two can never disagree. */
.cms-form-wrap .form-error {
    display: inline-block;
    margin-top: 8px;
    padding: 4px 10px;
    font-size: 12px;
    font-weight: 500;
    border-radius: 5px;
    color: var(--color-error);
    background: color-mix(in srgb, var(--color-error) 12%, #fff);
}

.cms-form-wrap .form-actions {
    margin-top: 1.5rem;
}

/* Live's `.btn-dark`, verbatim from the custom-CSS box: 315px wide whatever the
   label, 30px text, 30/40 padding. Scoped to the form rather than written over
   `.btn`, which would resize every button on the site. */
.cms-form-wrap .form-actions .btn {
    width: 315px;
    max-width: 100%;
    padding: 30px 40px;
    font-size: 30px;
    font-weight: 700;
    line-height: 1;
    color: #fff;
    background: var(--color-primary);
    border: 2px solid var(--color-primary);
    border-radius: 100px;
    transition: background 0.32s ease-in-out, border-color 0.32s ease-in-out;
}

.cms-form-wrap .form-actions .btn:hover,
.cms-form-wrap .form-actions .btn:focus-visible {
    color: #fff;
    background: var(--color-secondary);
    border-color: var(--color-secondary);
}

@media (max-width: 767px) {
    .cms-form-wrap .form-row { grid-template-columns: 1fr; }
    .cms-form-wrap .form-row > .form-group { grid-column: auto; }
}

/* ── Direct Access: the form's own layout ─────────────────────────────────────
 * Live labels every text field with its placeholder and shows the question only
 * where it is a question: beside the six dropdowns and the case description, in
 * the left three of twelve columns. The labels stay in the markup and stay
 * announced. Live hides them with `visibility: hidden`, which takes them out of
 * the accessibility tree as well and leaves a screen reader with placeholder
 * text and nothing else; this hides them from sight only.
 */
.cc-direct-access__form {
    margin-top: 3rem;
}

.cc-direct-access__form .form-group > label {
    position: absolute;
    width: 1px;
    height: 1px;
    margin: -1px;
    padding: 0;
    overflow: hidden;
    clip-path: inset(50%);
    white-space: nowrap;
    border: 0;
}

/* The three that keep a visible question. The case description is named because
   nothing in the markup separates it from the five conditional "details" boxes,
   whose labels are admin-side names live never shows — if the seeder renames
   the field, rename it here. The file input keeps its label because a native
   file control has no placeholder to carry one. */
.cc-direct-access__form .form-group:has(> select) > label,
.cc-direct-access__form .form-group:has(> input[type="file"]) > label,
.cc-direct-access__form .form-group:has(> #form-direct-access-case_description) > label {
    position: static;
    width: auto;
    height: auto;
    margin: 0 0 0.35rem;
    overflow: visible;
    clip-path: none;
    white-space: normal;
    border: 0;
}

@media (min-width: 768px) {
    .cc-direct-access__form .form-group:has(> select),
    .cc-direct-access__form .form-group:has(> #form-direct-access-case_description) {
        display: grid;
        grid-template-columns: repeat(12, 1fr);
        column-gap: 24px;
        align-items: start;
    }

    .cc-direct-access__form .form-group:has(> select) > label,
    .cc-direct-access__form .form-group:has(> #form-direct-access-case_description) > label {
        grid-column: span 3;
        margin-bottom: 0;
    }

    .cc-direct-access__form .form-group > select { grid-column: span 4; }
    .cc-direct-access__form .form-group > #form-direct-access-case_description { grid-column: span 9; }

    /* Under its own control, not adrift in the empty column after it. */
    .cc-direct-access__form .form-group:has(> select) > .form-error { grid-column: 4 / span 4; }
    .cc-direct-access__form .form-group:has(> #form-direct-access-case_description) > .form-error { grid-column: 4 / span 9; }
}

.cc-direct-access__form .form-html h2 {
    font-family: var(--font-family);
    font-size: 20px;
    font-weight: 700;
    line-height: 1.35;
    letter-spacing: 0;
    color: var(--color-primary);
}

/* The rule under a section heading belongs to it and sits close. The standalone
   dividers between question groups keep live's 20px on both sides. */
.cc-direct-access__form .form-html hr {
    margin: 20px 0;
    border: 0;
    border-top: 1px solid var(--cc-field-rule);
}

.cc-direct-access__form .form-html h2 + hr {
    margin-top: 10px;
}

/* The legal-aid note. Live carries it inside the question's own column, under
   the label; the seeder note says why ours follows the field instead. The width
   is three of twelve columns plus the two 24px gutters they span, so it lines up
   with the label above it, and the negative margin closes the gap the field
   below would otherwise leave. */
.cc-direct-access__form .cc-form-note {
    max-width: calc(25% - 18px);
    margin: -8px 0 16px;
    font-size: 15px;
    line-height: 1.45;
    color: var(--color-primary);
    overflow-wrap: anywhere;
}

/* Our file control is the native one, not live's FormNX dropzone: a dashed edge
   says "drop or browse" where the pill would say "type here". */
.cc-direct-access__form .form-group > input[type="file"] {
    width: 100%;
    padding: 0.9rem 1.1rem;
    font-size: 15px;
    color: var(--cc-field-ink);
    background-color: var(--color-page-bg, #fff);
    border: 2px dashed color-mix(in srgb, var(--color-primary) 45%, #fff);
    border-radius: 2rem;
}

@media (max-width: 767px) {
    .cc-direct-access__form .cc-form-note { max-width: none; }
}
